[eepro100] Intel D815EEAL + RH7 + newest eepro100.c = eth0, eth1, eth2... eth7 all initialize?
Alvin Oga
aoga@Mail.Linux-Consulting.com
Fri, 27 Oct 2000 21:42:56 -0700 (PDT)
hi ya dan...
donno what you are doing wrong per se...seems reasonable to little ol
me...
i use and shipped a few D815EEAAL + rh-7 + my patched eepro100.c
( same as that for the rh-6.2 distro ) but with the extra defines
for the onboard NIC chips
i do not get the problem you're getting eth1...eth-n..
to turn off the silly dhchp thingie during bootup... go into
the kernel config and turn it off...( its a new option i guess
that defaults to on...when it should default to be off )
c ya
alvin
On Fri, 27 Oct 2000, Dan Browning wrote:
> Please CC danb@cyclonecomputers.com, since I'm not subscribed.
>
> When I compile the newest eepro100.c into my kernel on a RH7 system
> (yes, with pci-scan.[ch] and kern_compat.h, and using kgcc), and I
> boot the new kernel, for some reason it shows 8 ethX devices: eth0
> through eth7. Even though all I have is the single onboard NIC that
> comes with the D815EEAL motherboard. eth0 initializes fine (and works
> after bootup), but the rest of them go through a long process of
> DHCP/RARP requests and timeouts that take up bootup time, and dirty
> the boot log.
>
> What am I doing wrong?
>
> Thanks,
>
>
> Dan Browning
> Network & Database Administrator
> Cyclone Computer Systems
>
>
> _______________________________________________
> eepro100 mailing list
> eepro100@scyld.com
> http://www.scyld.com/mailman/listinfo/eepro100
>