Description of problem:
the forcedeth driver you are using in rhel4 fails to
setup link on most gigabit switches
Version-Release number of selected component (if applicable):
2.6.9-42 with forcedeth 0.41
Connect for example a hp xw9400 on a hp procurve switch
the link light will go on, but the
RX counter remains on zero
the current driver aviable from nvidia
or plain vamilla kernel works.
I have an xw9300 and tested it today without any problems. Can you send output
from 'ethtool ethX' for that interface?
A sysreport might be nice as well, but we can start with the ethtool output if
I am sorry i have installed the driver provided from nvidia because we need this
machine working. With this driver or attached on a 100 MBit ethernet i did never
see any problems for now. The problem for me is that i have to hack the
redhat.initrd for pxe-installation of this workstation (i have to unpack the
initrd and to replace forcedeth module). The problem is known to nvidia and hp
(xw9400 and maybe also fujtsu-siemens v840) - please ask anybody there if you
dont trust me, i can provide you a contact person if you like.
The output of ethtool (eth0 is a nvidia interface but the driver is the on from
nvidia webside, forcedeth 0.59 !! ):
[root@fsc-amd-2 ~]# ethtool eth0
Settings for eth0:
Supported ports: [ MII ]
Supported link modes: 10baseT/Half 10baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
Advertised auto-negotiation: Yes
Supports Wake-on: g
Link detected: yes
Thanks for the feedback. Please send me your contact person at HP, so I can get
more detail about which switches have this problem.
I have not heard complaints about the xw9400 and forcedeth on 4.4 and I've not
personally experienced and problems with my xw9400 and an unmanaged D-Link
gigabit switch, so I would like to understand what devices won't link up with
Good news. I played around some more and noticed that eth0 does have problems
linking up at gigabit speeds and confirmed that this is fixed in our latest
development kernels (though I did find another problem).
Closing this as a duplicate of BZ 197797.
*** This bug has been marked as a duplicate of 197797 ***