>
Blah blah blah. . .
> > I rebooted my linux box but unfortunately I still get the same thing at
> > start-up:
> > Delaying eth0 initialization FAILED
> >
> > What does this mean?
>
> It means that kmod or kerneld (call it what you want), cannot
> load the module with modprobe because it does NOT know which one to load,
> you have to tell modprobe which kernel driver to load, this is done in
> /etc/conf.modules you need to add the following;
>
OK, let me try it.
>
> alias eth0 tulip
>
> Save the file and then type;
>
> modprobe eth0 or
> modprobe tulip
>
OK, no errors so far
>
> Now that should load the proper driver IF and only IF there are no "unresolved
> sysbols" which you might get considering you insisted on compiling another
> version of the driver when it was NOT nessasary.
>
I guess its just the polish in me ;P Anyways the new driver doesn't give me
warnings.
>
> If it gets loaded, you can see with 'lsmod' then you can configure the card on
> the command line with 'ifconfig' an example would be;
>
ohboy.....
>
> ifconfig eth0 up
OHboy ....
>
> Now type ifcofig eth0
>
OHBOY....
>
> That should return the complet configuration of the card, the next thing you
> will have to do is assign an IP address for the network if that is to be on a
> local basis then the following should do;
>
> ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up
>
OHBOY.... Its WORKS!!!!
>
> The networking documentation to read is /usr/doc/HOWTO/NET-3-HOWTO
>
> Get back to us here if that all works, we can then advise HOWTO configure the
> networking files for automatic loading at boottime.
> If that has not been done already.
>
Hum, well I guess you really do learn something new everyday. Thank you for
getting this to work. I think I have the netowkr card set to load automatically
when i boot, but I will check later and get back to you :)
John Marr
