Hi David, I had the same problem with my ne2000 card when I tried to compile it in to the kernel. For some reason the kernel couldn't find it on boot up. I read that with the ne2000 cards you have to specify an I/O address to get them to modprobe (to insert them as a module) and I there is no way you can let the kernel know where it is...(Uh, I guess you might be able to put something in LILO to correct but I'm not sure exactly what). I fixed the problem by compiling the the ne2000 as a module and making sure that in /etc/rc.d/rc.modules that the ne card was called out with an io=<appropriate address i.e. 300>. Works great, lasts long time. You say it was starting as a module by default..you might want to go check out /etc/rc.d/rc.modules to see what else you are trying to start by default. For instance, I had been loading sound as a module but when I compiled a new kernel with sound included I commented out the line that added sound as a module so that it wouldn't try to load the sound module anymore. HTH Scott > -----Original Message----- > From: David A. Mason [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, September 16, 1998 12:16 PM > To: Linux Newbie > Subject: Compiling and Modules > > I have numerous times compiled my kernel and modules, and I remembered > to > make modules_install, but at least my network device does not > initialize > after that. > > It looks to me like my NE2000 is being initialized as a module by > default, > and I was trying to compile it into the kernel, among other things. I > also > noted that the kernel xconfig does not ask for any hardware parameters > for > the card. > > On boot, I see the message eth0 initialization delayed or something > similar. > > Given that I have followed the directions in the RedHat 4.1 manual > line-by-line, and I've looked for more in-depth info on the web, and > I'm > using RedHat 5.1, has anybody got any ideas?
