On Wed, 2004-07-21 at 19:25, Mark wrote: > It looks like I got it: > Calling "modprobe sk98lin" gave me a bunch of lines about eth0 > Calling it again returned nothing any more, so I guess the first call loaded > the driver. > Calling "ifconfig eth0 up <IPADDR>" started it up and I was able to actually > ping my gateway. > > So I added a new line into /etc/modprobe.conf: > alias eth0 sk98lin > > I also added a new ifcfg-eth0 with the ususal content. > > After rebooting worked without problems, but still no eth0 when running > ifconfig > > "modprobe -c" does not list the sk98lin driver. Searching for eth0 in the > output shows: > alias eth0 off > > Then I found that there is another file called /etc/modules.conf > Adding "alias eth0 sk98lin" in there as well does the trick. > After rebooting my eth0 is there and working. > > So now the last question: > What is the difference between modules.conf and modprobe.conf and what do I > need the second one for? > > Thanks, > > MARK > It appears you upgraded from an FC1 or earlier install and did not do a clean install. The modules for the 2.4 and earlier kernels used modules.conf but the 2.6 kernel uses modprobe.conf. I don't really know why you would have needed to put that line in modules.conf since with FC2 it ignores that file and uses AFAIK only the modprobe.conf file. Maybe you are booting to a 2.4 kernel which would explain the use of modules.conf. What kernel are you actually running ( uname -r )? and what version of fedora? HTH Jeff
