Bug 90718
Summary: | (NET TG3)TG3 does not support Dell PowerVault 725N (bcm5704) | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Pieter de Boer <padeboer> |
Component: | kernel | Assignee: | David Miller <davem> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | amb, ispsysop, jgarzik, omlex, ronny-rhbugzilla |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:40:54 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Pieter de Boer
2003-05-12 20:31:36 UTC
tg3 don't understand all pci IDs and it is necessary to add more from broadcom driver: 0x14e4,0x1653 - BCM5705/NC7761 0x14e4,0x1654 - BCM5705/NC7761 0x14e4,0x165d - BCM5705M 0x14e4,0x165e - BCM5705M 0x14e4,0x1696 - BCM5782 and one more from Syskonnect driver http://www.syskonnect.de/syskonnect/support/driver/zip/sk9dlin_2_4_17_patch.gz : 0x1148,0x4600 - SK9MXX I am sorry, 4500 not 4600(this is SK9SXX series) 0x1148,0x4500 - SK9MXX I have the same problem (and solution) for an HP workstation xw4100. More info (sorry): This is the "Broadcom NetXtreme Gigabit Ethernet for hp" device, the BCM5782 with the 5702 chipset (rev 03). try latest kernel 2.4.20-19.x, it has tg3 1.5 version. If it doesn't work then you need to use insmod&pray bcm5700_driver from -> http://www.broadcom.com/docs/driver-download.html Yes, please try the latest kernel and report whether the problem is gone. Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |