Results 1 to 3 of 3
Laptop with drake 10.0 with built in ethernet controller.
Network connections is reporting two interfaces, eth0 and eth1, (there is only 1 nic) eth0 does not work, eth1 works.
eth0 ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 12-30-2004 #1Just Joined!
- Join Date
- Dec 2004
- Posts
- 10
1 nic, but 2 interfaces show up
Laptop with drake 10.0 with built in ethernet controller.
Network connections is reporting two interfaces, eth0 and eth1, (there is only 1 nic) eth0 does not work, eth1 works.
eth0 tries to load driver <ip1394> (which is the wrong one)
eth1 loads driver <8139too> (which is the correct driver)
how do I get my ethernet eth0 to load the proper driver, and get rid of eth1. I tried removing connections and all sorts of stuff.
any help would be appreciated.
A clip from /var/log/messages
Code:Dec 30 17:21:18 localhost network: Setting network parameters: succeeded Dec 30 17:21:19 localhost network: Bringing up loopback interface: succeeded Dec 30 17:21:19 localhost ifplugd(eth0)[1272]: ifplugd 0.21b initializing. Dec 30 17:21:19 localhost ifplugd(eth0)[1272]: Using interface eth0/08:00:1F:01:00:32 with driver <ip1394> (version: $Rev: 1198 $) Dec 30 17:21:19 localhost ifplugd(eth0)[1272]: Failed to detect plug status of eth0 Dec 30 17:21:19 localhost ifplugd(eth0)[1272]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. Dec 30 17:21:19 localhost dhclient: eth0: unknown hardware address type 24 Dec 30 17:21:22 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 Dec 30 17:21:41 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17 Dec 30 17:22:13 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 Dec 30 17:22:19 localhost ifplugd(eth0)[1272]: Killing child. Dec 30 17:22:19 localhost network: Bringing up interface eth0: failed Dec 30 17:22:19 localhost ifplugd(eth1)[1333]: ifplugd 0.21b initializing. Dec 30 17:22:19 localhost ifplugd(eth1)[1333]: Using interface eth1/08:00:1F:B1:01:F4 with driver <8139too> (version: 0.9.27) Dec 30 17:22:19 localhost ifplugd(eth1)[1333]: Using detection mode: SIOCGMIIPHY Dec 30 17:22:19 localhost ifplugd(eth1)[1333]: Initialization complete, link beat detected. Dec 30 17:22:19 localhost ifplugd(eth1)[1333]: Executing '/etc/ifplugd/ifplugd.action eth1 up'. Dec 30 17:22:19 localhost dhclient: eth0: unknown hardware address type 24 Dec 30 17:22:22 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8 Dec 30 17:22:22 localhost dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67 Dec 30 17:22:23 localhost dhclient: No DHCPOFFERS received. Dec 30 17:22:23 localhost ifplugd(eth0)[1272]: client: Determining IP information for eth0... Dec 30 17:22:23 localhost ifplugd(eth0)[1272]: Program execution failed, return value is 0. Dec 30 17:22:23 localhost ifplugd(eth0)[1272]: Exiting. Dec 30 17:22:23 localhost dhclient: bound to 192.168.10.111 -- renewal in 42239 seconds. Dec 30 17:22:23 localhost ifplugd(eth1)[1333]: client: Determining IP information for eth1... done. Dec 30 17:22:23 localhost ifplugd(eth1)[1333]: Program executed successfully. Dec 30 17:22:23 localhost network: Bringing up interface eth1: succeeded
- 12-31-2004 #2Just Joined!
- Join Date
- Dec 2004
- Posts
- 5
Is it a gigabye lan ? (not sure if this is relevant)
I've seen windows xp load up 2 interfaces for the same onboard nic ...with diffrent drivers
I'm guessing that they needed to ad another chip to the nic that /takes over/ and that they couldn't create a single schip (and so , one driver) nic for both 100/10 and 1000 mbps comunication
- 01-02-2005 #3Just Joined!
- Join Date
- Dec 2004
- Posts
- 10
Found out (like many others) that eth0 now is the defacto standard for firewire netowrking. I dont use firewire, so I just changed all the scripts to use eth1 instead of eth0 and all is well.
This all began after a recompile of the kernel to fix an issue with cardbus, I guess it fixed the firewire too (and installed drivers for it).
g


Reply With Quote
