From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Description of problem:
When installing Redhat 8.0 on a Dell Powervault 725N,
which has two Gb NICs with Broadcom 5704, the eth0 and eth1
are not recognized by both tg3 and bcm5700.
After an upgrade to Redhat 9.0 the tg3 module is loaded for
eth0 and eth1, but the ethernet interface does not work
(no traffic received).
The bcm5700 is no longer available in RedHat 9.0, so could not
Solution is to use the bcm5700-6.0.2a-1.src.rpm from Broadcom,
if this is build for RedHat 8.0 the interfaces are recognized
after loading the bcm5700.o module.
Only problem is the long time it takes to bring the interface up.
Please add bcm5700 back to RedHat 9.0 or update tg3 to include
the latest changes from bcm5700-6.0.2a-1.
Also the pxeboot.img should include this driver, as the powervault 725N does
not have a boot cdrom or floppy.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install redhat 9.0 on powervault 725N using PXE boot
2. connect network cable
Actual Results: no network connection
Expected Results: working network connection
tg3 don't understand all pci IDs and it is necessary to add more from broadcom
0x14e4,0x1653 - BCM5705/NC7761
0x14e4,0x1654 - BCM5705/NC7761
0x14e4,0x165d - BCM5705M
0x14e4,0x165e - BCM5705M
0x14e4,0x1696 - BCM5782
and one more from Syskonnect driver
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 ->
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
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/