Jerry Geis spake the following on 8/30/2007 1:46 PM: > I am using centos 5 x86_64 AMD64 X2 4200+. I am current on yum update. > > My machine has two ethernet cards. e1000 (eth0) and forcedeth (eth1) > > [root at fsdsigns2 ~]# more /etc/modprobe.conf > alias eth0 e1000 > alias eth1 forcedeth > > > > sometimes on boot the forcedeth driver thinks it is eth0: > [root at fsdsigns2 ~]# dmesg | grep eth > forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60. > forcedeth: using HIGHDMA > eth0: forcedeth.c: subsystem: 01458:e000 bound to 0000:00:07.0 > e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection > ADDRCONF(NETDEV_UP): eth1: link is not ready > e1000: eth1: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow > Control: RX/TX > ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready > eth0: no IPv6 routers present > eth1: no IPv6 routers present > > > > > however, sometimes it starts up correctly: > [root at fsdsigns2 ~]# dmesg | grep eth > forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60. > e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection > forcedeth: using HIGHDMA > eth1: forcedeth.c: subsystem: 01458:e000 bound to 0000:00:07.0 > e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow > Control: RX/TX > > > How can I get this connection to RELIABLY come up > each time as eth0 is e1000 and eth1 is forcedeth > This is a known problem with the forcedeth driver and some of the newer ethernet controllers it is used on. There is supposed to be a patch coming in the latest 2.6 kernel, but who knows how long it might take to be backported by upstream. Does your board manufacturer supply a linux driver? -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!