Description of problem: With 2.6.7-1.492 and above the forcedeth network driver does not detect a link on boot. 2.6.7-1.488 works fine. Version-Release number of selected component (if applicable): 2.6.7-1.492, 2.6.7-1.494 How reproducible: 100% Steps to Reproduce: 1. Boot. Actual results: kernel: eth0: forcedeth.c: subsystem: 01043:80c5 bound to 0000:00:05.0 kernel: eth0: no link during initialization. (followed by lack of network connectivity) Expected results: kernel: eth0: forcedeth.c: subsystem: 01043:80c5 bound to 0000:00:05.0 (followed by working Ethernet)
Seems fixed.
No, spoke too soon. I thought that it worked once with 2.6.7-1.499, but I certainly can't get it to work now. I tried booting with acpi=off but that didn't help. The version of forcedeth in 2.6.7-1.488 works fine, so I'm sticking to that for the time being.
Just a me too here with the erratta kernel 2.6.7-1.494.2.2. Same behaviour with forcedeth on my x86_64 nvidia chipset system. After the system is booted I have to run dhclient again (or rerun the init.d/network script) to configure the interface.
Manfred Spraul sent a patch (against 0.29) to netdev which fixes this. Hopefully it will show up in the upstream kernel before too long.
Created attachment 103158 [details] patch-forcedeth-timer Here is Manfred's patch, which works for me.
This seems to be working fine nowadays.