Find the answer to your Linux question:
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.
  1. #1
    Just 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&#58;21&#58;18 localhost network&#58; Setting network parameters&#58;  succeeded
    Dec 30 17&#58;21&#58;19 localhost network&#58; Bringing up loopback interface&#58;  succeeded
    Dec 30 17&#58;21&#58;19 localhost ifplugd&#40;eth0&#41;&#91;1272&#93;&#58; ifplugd 0.21b initializing.
    Dec 30 17&#58;21&#58;19 localhost ifplugd&#40;eth0&#41;&#91;1272&#93;&#58; Using interface eth0/08&#58;00&#58;1F&#58;01&#58;00&#58;32 with driver <ip1394> &#40;version&#58; $Rev&#58; 1198 $&#41;
    Dec 30 17&#58;21&#58;19 localhost ifplugd&#40;eth0&#41;&#91;1272&#93;&#58; Failed to detect plug status of eth0
    Dec 30 17&#58;21&#58;19 localhost ifplugd&#40;eth0&#41;&#91;1272&#93;&#58; Executing '/etc/ifplugd/ifplugd.action eth0 up'.
    Dec 30 17&#58;21&#58;19 localhost dhclient&#58; eth0&#58; unknown hardware address type 24
    Dec 30 17&#58;21&#58;22 localhost dhclient&#58; DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
    Dec 30 17&#58;21&#58;41 localhost dhclient&#58; DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
    Dec 30 17&#58;22&#58;13 localhost dhclient&#58; DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
    Dec 30 17&#58;22&#58;19 localhost ifplugd&#40;eth0&#41;&#91;1272&#93;&#58; Killing child.
    Dec 30 17&#58;22&#58;19 localhost network&#58; Bringing up interface eth0&#58;  failed
    Dec 30 17&#58;22&#58;19 localhost ifplugd&#40;eth1&#41;&#91;1333&#93;&#58; ifplugd 0.21b initializing.
    Dec 30 17&#58;22&#58;19 localhost ifplugd&#40;eth1&#41;&#91;1333&#93;&#58; Using interface eth1/08&#58;00&#58;1F&#58;B1&#58;01&#58;F4 with driver <8139too> &#40;version&#58; 0.9.27&#41;
    Dec 30 17&#58;22&#58;19 localhost ifplugd&#40;eth1&#41;&#91;1333&#93;&#58; Using detection mode&#58; SIOCGMIIPHY
    Dec 30 17&#58;22&#58;19 localhost ifplugd&#40;eth1&#41;&#91;1333&#93;&#58; Initialization complete, link beat detected.
    Dec 30 17&#58;22&#58;19 localhost ifplugd&#40;eth1&#41;&#91;1333&#93;&#58; Executing '/etc/ifplugd/ifplugd.action eth1 up'.
    Dec 30 17&#58;22&#58;19 localhost dhclient&#58; eth0&#58; unknown hardware address type 24
    Dec 30 17&#58;22&#58;22 localhost dhclient&#58; DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
    Dec 30 17&#58;22&#58;22 localhost dhclient&#58; DHCPREQUEST on eth1 to 255.255.255.255 port 67
    Dec 30 17&#58;22&#58;23 localhost dhclient&#58; No DHCPOFFERS received.
    Dec 30 17&#58;22&#58;23 localhost ifplugd&#40;eth0&#41;&#91;1272&#93;&#58; client&#58; Determining IP information for eth0...
    Dec 30 17&#58;22&#58;23 localhost ifplugd&#40;eth0&#41;&#91;1272&#93;&#58; Program execution failed, return value is 0.
    Dec 30 17&#58;22&#58;23 localhost ifplugd&#40;eth0&#41;&#91;1272&#93;&#58; Exiting.
    Dec 30 17&#58;22&#58;23 localhost dhclient&#58; bound to 192.168.10.111 -- renewal in 42239 seconds.
    Dec 30 17&#58;22&#58;23 localhost ifplugd&#40;eth1&#41;&#91;1333&#93;&#58; client&#58; Determining IP information for eth1... done.
    Dec 30 17&#58;22&#58;23 localhost ifplugd&#40;eth1&#41;&#91;1333&#93;&#58; Program executed successfully.
    Dec 30 17&#58;22&#58;23 localhost network&#58; Bringing up interface eth1&#58;  succeeded

  2. #2
    Just 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

  3. #3
    Just 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

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •