On 1/1/2015 12:49, Cezar Rangel wrote:
Bryan, I changed and chose "m" instead of "y" and there has been a little progress as after the change the output of #lspci -v concerning the ethernet controller shows the Kernel modules: e1000e.
however, there is not a kernel drive in use yet
I have tried #modprobe e1000e and the result was the same a got before #modprobe:ERROR: could not insert 'e1000e' unknown symbol in mocule, or unknown parameter (see dmesg)
First, for clarification: For the vast majority of network drivers, it matters not at all whether you select module <M> or builtin <*> in the kernel config. An exception would be a wifi NIC that needs to load firmware. In that case the driver should be a module rather than builtin so that the appropriate filesystem is mounted and firmware files are available *before* the NIC driver is loaded. Some wired NICs also load firmware files (r8169 might be one of these). If you're not sure, use module <M>. If you're booting from a network or running a diskless install this gets more complicated but that's a different scope and conversation. initrd/initramfs usage is also more complicated and out of scope here. Next, the "unknown symbol in module or unknown parameter" message might indicate that there's some kind of incompatibility between your kernel and its modules. This can happen if you update your kernel but forget to recompile/reinstall the modules or something similar. The "see dmesg" part is good advice, you might be able to spot the problem in dmesg's output. With that said, I'd recommend the following: 1) Build your kernel with E1000E and R8169 set to module <M> 2) Remove the old modules dir (/lib/modules/3.14.27 or whatever version) 3) Build and install new modules 4) Install the new kernel 5) Update boot loader if needed 6) Reboot If you do all this you should theoretically have everything in the proper state. If the NIC *still* doesn't work after that, I'd like to see the outputs from: lspci -k, ip a, ifconfig -a, and dmesg. I know you've posted some of these before but this is only if you still have problems after cleaning up the kernel. Cheers, Matt