Ethernet modules not found at boot [Solved]

[Tefrem34]

Tony0945,

[Tefrem34]

I am wondering if I try a newer kernel that it will have the e1000e module that I need in it?
This is strange, because I have other distros installed and it is only gentoo that can not load the Ethernet driver.

[Jaglover]

e1000e driver has been in kernel for ages. You are doing something wrong. Maybe not mounting /boot before installing a new kernel. Maybe not installing modules. It is hard to tell, too much controversial and confusing information.
_________________
My Gentoo installation notes.
Please learn how to denote units correctly!

[John R. Graham]

[Hu]

At the risk of causing more confusion:

There are several stages to getting a working network. You need the appropriate driver to be compiled and available, you need it to load (happens automatically for =y, happens in response to module loading for =m), you need it to recognize the card, and you need the card to be configured.

If the driver is built in, it should initialize at boot and bind to the network card. If bound, ifconfig -a should show it. lspci -k should show that the driver is in use. ifconfig without arguments will not show the device if it has not been configured. When troubleshooting early problems like this, you need to be careful to use -a (or better, don't use ifconfig at all; use ip link (from sys-apps/iproute2) instead). We haven't even begun discussing whether your device has been configured. We're still focused on getting the driver to initialize and bind the device.

You said you hand-copied the output out. Don't do that. It makes mistakes more likely and it's more trouble for you. It will only become a bigger burden as we move to commands that produce more output. Instead, save the output to a file, then transport that file via sneakernet to a working system or, if your only working system is the LiveCD, reboot into the LiveCD, cat the file from the chroot, and post it that way.

At this point, I think the best option would be:

1. On the installed system, run lspci -k ; ifconfig -a and redirect the output to a file.
2. On the installed system, run zcat /proc/config.gz and redirect the output to a file (separate from the file above).
3. On the installed system, run find "/lib/modules/$(uname -r)/kernel/drivers/" -name \*.ko -ls and redirect the output to a file.
4. Reboot to the LiveCD. Install app-text/wgetpaste (if not already installed).
5. Pastebin the files from steps 1-3 and give us the link.

[Tony0945]

[Tefrem34]

Hu,
I booted into my gentoo installation and these are the outputs:

[Tefrem34]

I ran "genkernel --install kernel" then

[Tefrem34]

[/code]Alright, this looks promising.
I upgraded my genkernel to 3.5.2.5 and ran (chrooted) "genkernel --menuconfig all" in my

[Tefrem34]

So, sadly it did not work.
However, I did notice that the modprobe error points to "/lib/modules/4/14/12-2", but the modules are listed in "/lib*/modules/4.9.76-gentoo-r1/...". Should it be this way?

[grumblebear]

It seems, before solving your network problem, you should learn, how to configure and use your bootloader. The kernel you are booting will only use the modules that were specifically compiled for that kernel. That means, the output of 'uname -r' is the directory in /lib/modules where the kernel will look for its modules.

[NeddySeagoon]

Tefrem34,

It appears you are building one kernel and running another.
Boot your gentoo
Mount /boot
Run

[Tefrem34]

NeddySeagoon,

[Jaglover]

eslect kernel does not manage kernels, it manages only the symlink to the kernel sources.
_________________
My Gentoo installation notes.
Please learn how to denote units correctly!

[krinn]

[quote="Tefrem34"]

[Tefrem34]

I want to thank all of you for helping me getting this all sorted, I really appreciate it!