On Tue, 5 Sep 2000, Larry D. Weiner wrote:
> >The first step in debugging this problem would be to check and see if the
> >network module has been loaded. Do this by issuing the command (as root)
> >'lsmod'. Check the output of this command for the network module that
> >drives the card. If it's not loaded, try loading it with
> >"depmod -a (module_name)".
>
> invoked it as either:
>
> depmod -a lne390.o
> -or-
> depmod -a 2.2.14-storm/net/lne390.o
>
Sorry for this confusion...it's a common mistake. When using depmod, you
omit the trailing ".o" So you might try just "depmod -a lne390" The
reason why it's so confusing, is because you might also use "insmod"
to load the module, which takes the ".o" extension to the module name.
The cards that I use are 3Com, D-Link and NetGear, so I don't know which
module to direct you to or to affirm that the lne390 is appropriate
(sorry). Others on this list should be able to jump on that though.
Are you using DHCP or static IP assignments? The gateway that you
reported was not set (0.0.0.0). If you're using DHCP, then perhaps
Mircea's suggestion is best: Start up sas and re-start the network from
there. If you're command-line oriented, you may want to try "ifup eth0"
(do a "man ifup" for the complete picture) or perhaps
"pump -i eth0 --status" to see what's up with the card.
Another thing to try would be to manually restart the network:
/etc/init.d/networking stop
/etc/init.d/networking start
If you're using DHCP, is your MAC address in the DHCP server's tables?
--
Paul Gray
[EMAIL PROTECTED]
Dept. of Mathematics
University of Northern Iowa
Wright Hall
Cedar Falls, IA 50614-0506
_______________________________________________
Stormlinux-users-list mailing list
[EMAIL PROTECTED]
http://www.stormix.com/community/lists/listinfo/stormlinux-users-list
