How to activate proper NIC driver?

Mark msalists at
Thu Jul 22 00:25:05 UTC 2004

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

"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?



> -----Original Message-----
> From: fedora-list-bounces at 
> [mailto:fedora-list-bounces at] On Behalf Of Mark
> Sent: Wednesday, July 21, 2004 5:02 PM
> To: 'For users of Fedora Core releases'
> Subject: How to activate proper NIC driver?
> Hello again,
> I just searched the web to find a driver for the Marvel Yukon 
> SysKonnect
> SK-98xx Gigabit card 
> The driver that comes with the mainboard is called sk98lin - 
> however I can
> not get it compiled and installed.
> At 
> I found
> this:
> Summary of changes from v2.4.21-pre4 to v2.4.21-pre5:
> o sk98 driver vendor update
> o [netdrvr] zap PCI_VPD_ADDR constants from skfp, sk98lin drivers
> This sounds to me like the driver has been included in 2.4.21 or even
> earlier. The FC1 CD I use installs kernel 2.4.22 Doesn't this 
> mean that the
> driver I need should be part of the FC1 kernel I install? Why 
> does it not
> find it? How can I point it to the right driver manually?
> Thanks,
> -- 
> fedora-list mailing list
> fedora-list at
> To unsubscribe:

More information about the users mailing list