Please Help: eth0 won't start on boot.

Bangz

I'm having a very weird problem on my relatively new Gentoo Install, and because Im new to gentoo Im hoping someone with a bit more experience can help me.

I'm trying to get the onboard LAN workiing for my Epox 8RDA+ motherboard. During the install I setup the net (dhcp) and it worked fine, that is, "dhcpcd eth0" immediately worked, I didn't need to manually modprobe the NIC.

However, now when the OS boots, it's not loading eth0.

Showing this during bootstrap

pjp · Administrator Joined: 16 Apr 2002 Posts: 20067

I would try compiling support for the NIC into the kernel instead of a module.

Moved from Other Things Gentoo.
_________________
Quis separabit? Quo animo?

PT_LAmb · Posted: Thu Feb 20, 2003 6:58 pm Post subject:

Have you configured the the kernel to compile the driver as a module?
And are you sure that that's the appropriate one?
Is the driver name correct?

If...

TwoTired · n00b Joined: 08 Feb 2003 Posts: 42

dsegel · Tux's lil' helper Joined: 31 Jan 2003 Posts: 127

There are two ways you can load the nvnet driver at boot up:

1. In /etc/modules.d/nvidia (or /etc/modules.d/aliases) put the following line:

alias eth0 nvnet

and then run the update-modules command, which will copy the information into the /etc/modules.conf file.

2. In /etc/modules.autoload add one line that simply says:

nvnet

The problem with both of these is that you must have the nvnet driver installed on your system somewhere. It's on the boot CD, but I don't think it gets installed when you build your system. In my case I downloaded the appropriate tar file from nVidia's web site and did a 'make' and 'make install' on it. After that either method above should work.

You'll get warnings about a tainted kernel if you do method 1, but you can safely ignore them. Method two gives no warnings.

The errors you're getting at boot up are becuase you have the wrong kind of line in modules.autoload.

You can check to see if you have it on your system already by doing a:

modprobe nvnet

if that works then just do one of the two methods above. If it doesn't work you'll have to get a copy of the driver and install it.

Bangz · Posted: Fri Feb 21, 2003 5:59 am Post subject:

Thanks guys, All I needed to do was change my modules.autoload from "alias eth0 nvnet" to just "nvnet" and it works fine.

Cheers!