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]

Add hardware later?



Today, David Kramer gleaned this insight:

> I'm putting together a 486-dx2 100mhz computer with Red Hat 6.2.  I
> finally got everything working, but originally I could not get the network
> card working.  Now I put the network card back in, and I would like to
> know how to tell the system to load the driver for it.
> 
> Note that this system only has a 400MB hard drive, so I did not install X
> on it, so no GUI programs will work.
> 
> The card is a Eagle NE2000T Plus, IRQ=3, IO=0x300.
> 
> Any ideas?  Thanks.

Assuming you have support built in as a module, AND that the card really
is 100% ne2000-compatible, (many older cheap clones aren't) the driver is
ne2000.o and you load it by doing:

  modprobe ne2000

To get it to autoload, add this line to your /etc/conf.modules (or
/etc/modules.conf -- whichever you have):

  alias eth0 ne2000

If you have support compiled directly in, you don't need to do anything.
The kernel will find the card.  If you have no support at all, you will
need to recompile with support for the ne2000 built in (or as a module).


-- 
---------------------------------------------------------------
Derek D. Martin              |  Unix/Linux Geek
ddm at MissionCriticalLinux.com |  derek at cerberus.ne.mediaone.net
---------------------------------------------------------------

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).




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