What's bring eth0 up?

[Bill Moseley <moseley@hank.org>]

I just (finally) replaced a hard drive in an older Toshiba laptop
(2805-S302) and went from a few-month-old sid install to Sarge.

My wireless connection now takes much longer, and it seems that might be
due to trying to bring up eth0 first instead of eth1.  I boot with the
wireless card in the laptop.


    $ fgrep eth0 /etc/network/interfaces 
    #auto eth0
    iface eth0 inet dhcp

eth0 shouldn't come up.  But I see this in syslog:


# The module for the wireless card is loaded:
Dec 22 06:28:13 localhost kernel: Loaded prism54 driver, version 1.2

# Then the eth0 is attempted:
Dec 22 06:28:18 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12

# Then I can see eth1 start:

Dec 22 06:29:11 localhost dhclient: sit0: unknown hardware address type 776
Dec 22 06:29:11 localhost kernel: eth1: islpci_open()
Dec 22 06:29:11 localhost kernel: eth1: resetting device...
Dec 22 06:29:11 localhost kernel: eth1: uploading firmware...
Dec 22 06:29:11 localhost kernel: eth1: firmware uploaded done, now triggering reset...
Dec 22 06:29:12 localhost dhclient: sit0: unknown hardware address type 776
Dec 22 06:29:12 localhost dhclient: Listening on LPF/eth1/00:09:5b:e6:c8:a5
Dec 22 06:29:12 localhost dhclient: Sending on   LPF/eth1/00:09:5b:e6:c8:a5
Dec 22 06:29:12 localhost dhclient: Sending on   Socket/fallback/fallback-net
Dec 22 06:29:12 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
Dec 22 06:29:15 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
Dec 22 06:29:15 localhost dhclient: DHCPOFFER from 192.168.1.1


What's trying to bring up eth0?  This is a very trimmed down Sarge
install, and I'm not running anything (like if ifplugd), just the
default hotplug installation.


-- 
Bill Moseley
moseley@hank.org