Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Jon <ghia at ccs.neu.edu> writes: > It currently has Redhat 7.2 with a home-brew 2.4.17 kernel and a linksys > USB nic. > > The kernel picks up the nic in the dmesg, but it doesn't assign the nic to > eth0 or start the networking services. If I try to restart the network > services after it has booted ifconfig complains that there is no such > thing as eth0. > > Once the computer has fully booted, if I unplug the nic and plug it back > in again, the network comes up and everything works like a champ. > > Anyone have a guess as to why this is happening? This is apparently a common problem with USB network devices. You should be able to get it working by loading the appropriate kernel modules in /etc/modules.conf. To figure out what modules you need, run "lsmod" both before and after you unplug and replug the nic, and compare the output. -- John Abreau / Executive Director, Boston Linux & Unix ICQ 28611923 / AIM abreauj / JABBER jabr at jabber.org / YAHOO abreauj Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9 PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 344 bytes Desc: not available URL: <http://lists.blu.org/pipermail/discuss/attachments/20020506/b0282494/attachment.sig>
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |