![]() |
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 |
On 05 Jun 2003 15:13:33 -0400 Stephen Anthony <steve at stephencanthony.com> wrote: > What a day.... > > I spent most of it trying to get the 2.4.18 kernel to recognize and > configure my eth0 device. It would see it, but not configure it. > Grumble. I was doing this from the kernel-source-2.4.18-686 package. > > So I thru up my hands and did apt-get install kernel-image-2.4.18-686 > > Now, it doesn't even *see* the eth0 device. Did I do something in the > build from sources that would break the image package itself? Or is > there some other magic I need to supply? Once you identify the hardware, then you might want to locate the appropriate driver. http://www.scyld.com. This is Donald Becker's site. Click on Linux Network Drivers. Normally, you configure the network driver as a loadable module rather than a kernel driver. Most network devices are supported today, but new stuff sometiomes takes a while to find its way into the distros. -- Jerry Feldman <gaf at blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.blu.org/pipermail/discuss/attachments/20030605/2c077eed/attachment.sig>
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |