[lkml]   [2001]   [Nov]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectip autoconfig and e100

I've posted previously about my ongoing pains with a diskless cluster of
dual cpu serverworks boards that use on-board Intel eepro100 chips.

Basically the nodes randomly reboot themselves. See previous posts by me
for more thorough description.

After reading some more of the posts recently regarding the eepro/100 on
board nics, and the various drivers available, I think that my symptoms
are possibly consistent with the problem where the card flakes out. We
are using the eepro100.c compiled statically.

I'd like to try the e100 module from Intel, but I can't get it to work
with nfsroot.

The Intel e100 driver is only available as a module.

IP autoconfig (which does not appear to be available as a module) attempts
to set the address before the module is loaded and the card is detected,
thus by the time the module is loaded from my initrd the system has
already given up on ip autoconfig and thus cannot mount its nfsroot

Is there a way to make the intel driver static? or perhaps to make ip
autoconfig a module, or to configure the network in another way in
combination with nfsroot?


Ryan Sweet <>
Atos Origin Engineering Services

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:12    [W:0.110 / U:0.188 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site