Jonathan Fournier wrote: >> Sep 19 08:14:43 localhost kernel: ADDRCONF(NETDEV_UP): eth3: link is >> not ready Sep 19 08:16:54 localhost kernel: ADDRCONF(NETDEV_UP): >> eth2: link is not ready >> >> I'll retry with bare 2.6.27.11 (7.3.20-k3-NAPI), I think the link was >> at least coming up. > > Yeah, my memory from yesterday was right with bare 2.6.27.11 (without > that hack patch) link at least comes up: > > Sep 19 09:14:35 localhost kernel: ADDRCONF(NETDEV_UP): eth3: link is > not ready Sep 19 09:14:35 localhost kernel: e1000: eth3: > e1000_watchdog: NIC > Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX > Sep 19 09:14:35 localhost kernel: ADDRCONF(NETDEV_CHANGE): eth3: link > becomes ready > > It no longer comes up in 8.0.9, but again the eeprom must be wrong ;)
hm, well bummer that there is a difference but I wouldn't expect it to work anyway. you can use ethtool to change the device ID in your eeprom, but its maybe safer to use a driver change to make the 8.0.9 driver think 1079 is serdes, you'll have to change a bunch of little switch statements in the code I think, but not too many Jesse ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel
