> This may seem like a silly question, but does eth0 have to be initialized
> before eth1?
>
> In order to work around Roadrunner's brain-dead DHCP server, which would
> NOT respond to my bootp requests for some reason, I switched connections.
> Formerly I had eth0 on the internal network, set to come up at boot, and
> eth1 conencted to the cable modem, set to come up manually (it's a hostname
> thing). So I change my scripts, swap the cables, and everything worked
> fine, but on a reboot, I found that eth1's initialization was being
> deferred. Doublechecked, all looks well, and I can bring it up manually
> after eth0 is up.
I get this problem with some cards using the Intel "tulip" 21143 chip.
They don't want the tulip driver, they really want the de4x5 driver. The
cards won't initialise on startup if the tulip driver is used, but can
be started manually. They also often crap out after doing a couple of
pings if the wrong driver is used.
Vik :v)
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
