Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

New Cluster...problems recognizing ethernet adapter



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 15 Apr 2002, kgleason at ma.ultranet.com wrote:

> No NIC was detected at startup.
> Tried to do modprobe sis900 then ifup eth0 but that didn't work either.

   Hmmm, next time check the end of /var/log/messages or the output of the 
"dmesg" command for clues.  If the module has failed to load you'll 
usually get errors at the terminal.  Otherwise, any abnormalities will 
probably only show up in the logs.
   Has eth0 been configured on this machine?  If the appropriate 
information doesn't exist in "/etc/sysconfig/network-scripts/ifcfg-eth0" 
then ifup won't work.  You can either use ifconfig to manually configure 
the interface, or run netconfig to create the config file for you.


> Do you have to move the object file sis900.o to another directory before
> it can be recognized at startup. Isn't there a way that I can assign
> that file at startup after Lilo? If so, then I don't know how.

   The module file should live in /lib/modules/[kernel-version], where the 
version is exactly what 'uname -r' returns on that system.  Network 
modules should be in a subdirectory called 'net'.  On a fully updated 
RH6.2 system sis900.o is in:
/lib/modules/2.2.19-6.2.16/net
   I *think* you're asking how to associate the sis900 module with the 
interface eth0, so that when the init scripts bring up networking the 
module gets loaded automagically.  In that case you'll need the following 
line in "/etc/modules.conf":
alias eth0 sis900

   This is assuming that the sis900 driver is the correct one, and 
actually works.  If it turns out to be a different module, just use that 
name instead on the alias line.  Don't forget the "lspci" command if 
you're still stumped on which driver to use.  That should tell you what 
the NIC is calling itself, which someone (hopefully) can translate into an 
appropriate module name.


- -- 
     -Matt

Facts are stubborn, but statistics are more pliable.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8vBxmc8/WFSz+GKMRAsh5AJ9vQs9wAPp4ShIzjTZsm77nT/qPNACbBHMl
ErtRn/enzAz6Tufc9robYz0=
=2QTv
-----END PGP SIGNATURE-----





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org