[EMAIL PROTECTED] wrote:
> > This may seem like a silly question, but does eth0 have to be initialized
> > before eth1?
[...]
> > 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.
Interesting you should say that. These are D-Link DFE-500TX cards, but
that's the 21140 "tulip" chip. I've had no problem otherwise, and
previously eth0 would initialize as the 1st device. For now, I'll switch
off automatic initialization and add an rc script to bring it up at the
right place, or try aliasing eth0 and eth1 at boot.
-W-
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
