[SOLVED] eth0 not found after upgrading to slack 14
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i've just updated my distro to the version 14, but after the reboot it doesn't seem to find the eth0 interface: #ifconfig -a return the presence of only loopback interface. I've run netconfig but it didn't work.
lsmod return:
We need to know which is your network adapter and which kernel module(s) are supposed to support it. To provide that information please send out output of following command:
Code:
lspci -knn|grep -iA3 network
Also, which kernel are you using? Is it a stock Slackware kernel or did you compile it yourself?
I ask that because lsmod's output looks really short.
Last edited by Didier Spaier; 10-04-2012 at 11:58 AM.
We need to know which is your network adapter and which kernel module(s) are supposed to support it. To provide that information please send out output of following command:
Code:
lspci -knn|grep -iA3 network
Also, which kernel are you using? Is it a stock Slackware kernel or did you compile it yourself?
I ask that because lsmod's output looks really short.
Looks same to me when i see it. Before the upgrading i was using a self-compiled kernel, now the one there's in the stock. However the command doesn't retunr anything, but I remember that i use a Realtek ethernet controller which use the r8169 kernel module
EDIT. I launched modprobe r8169 and now eth0 appear in the ifconfig -a. But dhcpcd don't want to work. It only show "version etc.etc. starting" and then "no interfaces have a carrier"
RE EDIT: using dhcpcd eth0 the system get the Ip from the system, but now i can't use the mouse. Rebooting the computer i've seen that it can't find /dev/mouse. Also when i reboot the system, i have to re-probe the module and rerun dhcpcd
I guess something went wrong during the upgrade. I suggest you reinstall the kernel from Slackware and the associated modules. Then please send the output of "uname -r" and the command's output I requested in my previous post.
I guess something went wrong during the upgrade. I suggest you reinstall the kernel from Slackware and the associated modules. Then please send the output of "uname -r" and the command's output I requested in my previous post.
upgradepkg -- install-new --reinstall </path/to/the/package>
or
slackpkg reinstall <package name>
The latter won't work if the package was not installed. Then type instead:
slackpkg install <package name>
So i have to launch something like slackpkg kernel-modules and slackpkg kernel. Bu there's lots of kernel (huge, generic) and i dont' kknow which installing
Did you run lilo after upgrading and before rebooting? I'm kind of wondering if the system is booting with your old kernel left behind in /boot and it's failing to load the modules now under /lib/modules (because they are for the new kernel). Seems like in that scenario it wouldn't be able to load *any* modules, but maybe a handful are compatible.
"uname -r" will tell you which is in use. Reinstall the same. But if this is a generic one don't forget to make an initrd and run lilo. In any case edit /etc/lilo.conf to update the "image=..." name then run lilo.
Last edited by Didier Spaier; 10-04-2012 at 12:46 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.