Network interface not active after install of 14.1
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.
Distribution: Slackware 14 on a Dell Inspiron 1420
Posts: 30
Rep:
Network interface not active after install of 14.1
Hello,
I just finished installing slackware 64 bit on an old box with a new asus motherboard in it, with all new hardware as well, I have been trying to figure out how to get the network interface to startup. I would post some results of some commands likr lsmod but I can't get them online to paste them in here. but at the bottom of the results is
"ADDRCONF (NETDEV_UP):eth0 :link is not ready"
r8l69 0000:03:00.0:eth0:link down
I'm not sure if I need to install a driver or not, but I sure could use some help. I have a disk that came with the motherboard that has a Linux folder on it with drivers inside, the file is r8l68-8.026.00.tar.bz2 and I'm not sure what to do with that file. I'm not very good with Linux and am just starting out, this is my 3rd install the other 2 went fairly well. thanks for any help you can give me,
This is most likely a missing driver, which in turn is most likely a kernel issue. The (now slightly old) kernel shipped with Slackware 14.1 may not support the revision of the RealTek 8168/8169 chip on your brand new motherboard.
If you run the following command:
Code:
lspci -vn | grep 03:00\.0
...it should return a single line of text containing the PCI vendor and device IDs. Could you post that information here?
The .tar.bz2 package on the driver disk could be the source code for an updated version of the driver. If you installed the development tools from the "D" series and the kernel source code, you could try compiling the driver:
Code:
root@slackware:~# cd /usr/src
root@slackware:/usr/src# tar -xjf /mnt/path/to/driver/r8l68-8.026.00.tar.bz2
root@slackware:/usr/src# cd r8l68-8.026.00
root@slackware:/usr/src/r8l68-8.026.00# make
The exact directory name in that last cd command is just an (un)educated guess on my part. The point is, the tar command should unpack a number of files, creating a subdirectory in the process. That's the directory you need to cd into.
If this works, make install should install the newly compiled driver. Please do post the results in this thread regardless of what they might be.
Distribution: Slackware 14 on a Dell Inspiron 1420
Posts: 30
Original Poster
Rep:
Quote:
Originally Posted by Ser Olmy
This is most likely a missing driver, which in turn is most likely a kernel issue. The (now slightly old) kernel shipped with Slackware 14.1 may not support the revision of the RealTek 8168/8169 chip on your brand new motherboard.
If you run the following command:
Code:
lspci -vn | grep 03:00\.0
...it should return a single line of text containing the PCI vendor and device IDs. Could you post that information here?
The .tar.bz2 package on the driver disk could be the source code for an updated version of the driver. If you installed the development tools from the "D" series and the kernel source code, you could try compiling the driver:
Code:
root@slackware:~# cd /usr/src
root@slackware:/usr/src# tar -xjf /mnt/path/to/driver/r8l68-8.026.00.tar.bz2
root@slackware:/usr/src# cd r8l68-8.026.00
root@slackware:/usr/src/r8l68-8.026.00# make
The exact directory name in that last cd command is just an (un)educated guess on my part. The point is, the tar command should unpack a number of files, creating a subdirectory in the process. That's the directory you need to cd into.
If this works, make install should install the newly compiled driver. Please do post the results in this thread regardless of what they might be.
Hello,
I didn't install anything other than the operating system, I don't know how to install the tools and source code, but I do have the dvd for it I think, I created it from the iso file. I also already extracted the file to a folder of the same name in /tmp/LinuxDrivers/LAN/r8l68-8.026.00 and there is several files in there. So I'm guessing I need to install a few things from the source dvd and try to run the command to compile the drivers? Let me know if that's correct and I will try it tomorrow when I go to work. Thanks again,
If you performed a full/complete installation, then you already have everything you need.
If not, the development tools are in the "slackware/d" subdiractory on the DVD (or "slackware64/d" for 64-bit Slackware). The kernel source is in the "slackware[64]/k" subdirectory.
Distribution: Slackware 14 on a Dell Inspiron 1420
Posts: 30
Original Poster
Rep:
Quote:
Originally Posted by Ser Olmy
If you performed a full/complete installation, then you already have everything you need.
If not, the development tools are in the "slackware/d" subdiractory on the DVD (or "slackware64/d" for 64-bit Slackware). The kernel source is in the "slackware[64]/k" subdirectory.
OK great, I just came across this post while searching and it looks like the exact same problem I'm having. check it out
I did do some checking on the device earlier and the info that came back was
RTL 8111/8168 PCI Express Gigabit Ethernet Controller (Rev. 0c)
I/O Ports at e000 IRQ42
Kernel driver in use r8169
Modules = r8169
I guess all I need to do is blacklist the r8169 driver so it will use the correct one as I already ran the file from the asus disk, I ran the autorun.sh file in the r8l68-8.026.00.tar.bz2 extracted file I created earlier. Is this correct? Thanks again,
I ran into an issue with this driver with my freshly upgraded 3.18 kernel. I kept having dropouts, where I didn't have them on the stock Slackware kernel. I ended up downloading the latest driver directly from realtek and built that. It will back up the original driver and then install the new one in its place so no blacklisting is needed. You could just download it with another computer and then copy it with a thumbdrive. It's the LINUX driver for kernel 3.x and 2.6.x and 2.4.x download. Just untar it and then run the autorun.sh script.
Distribution: Slackware 14 on a Dell Inspiron 1420
Posts: 30
Original Poster
Rep:
Quote:
Originally Posted by Ser Olmy
Yes, that sounds 100% correct.
Hello,
I loaded the drivers as shown on the tread that I linked to and the link is up, but I can't browse the internet with firefox, it says no connection, if I ping the gateway it comes back as if it's connected. Thanks for your help so far.
Distribution: Slackware 14 on a Dell Inspiron 1420
Posts: 30
Original Poster
Rep:
Quote:
Originally Posted by Rockitglider7
Hello,
I loaded the drivers as shown on the tread that I linked to and the link is up, but I can't browse the internet with firefox, it says no connection, if I ping the gateway it comes back as if it's connected. Thanks for your help so far.
Sincerely, Kit O.
Hello again,
Actually I have it working now, seems like all is good, thanks very much,
Distribution: Slackware 14 on a Dell Inspiron 1420
Posts: 30
Original Poster
Rep:
Hello again,
I guess I have the issue that I've been reading about where the card works sometimes and sometimes it doesn't. I had it working and then it just stopped working. I've tried all the things I know how to do, but some of the fixes I don't know how to complete, like making it so it chooses an certain irq on startup, or at least I think that's what they are trying to do. Here is a couple of links to some fixes:
Thanks for ant help you can provide. When it connects I can get a clean ping of the gateway, when it doesn't I get "RX packets sent=0" returned from the ifconfig.
I realize that this may be off the track, but have the udev rules has been set for the network interfaces?
The fact that the issue is on-again / off-again seems to point to missing udev rules: /etc/udev/rules/70-persistent-net.rules.
It can be set using the script /lib/udev/write_net_rules, like this (change INTERFACE and MATCH values):
There are also options to match on different values: MATCHDRV, MATCHDEVID, MATCHID, MATCHIFTYPE.
Take a look inside the write_net_rules script for better understanding. The data used by the MATCH variables should
be available under the /sys/class/net/${INTERFACE}/ directory.
This can be done for each network interface.
My apologies in advance if this is not the issue or this is too much stating the obvious.
Distribution: Slackware 14 on a Dell Inspiron 1420
Posts: 30
Original Poster
Rep:
Quote:
Originally Posted by j_v
I realize that this may be off the track, but have the udev rules has been set for the network interfaces?
The fact that the issue is on-again / off-again seems to point to missing udev rules: /etc/udev/rules/70-persistent-net.rules.
It can be set using the script /lib/udev/write_net_rules, like this (change INTERFACE and MATCH values):
There are also options to match on different values: MATCHDRV, MATCHDEVID, MATCHID, MATCHIFTYPE.
Take a look inside the write_net_rules script for better understanding. The data used by the MATCH variables should
be available under the /sys/class/net/${INTERFACE}/ directory.
This can be done for each network interface.
My apologies in advance if this is not the issue or this is too much stating the obvious.
Hello, no, any help is appreciated. I will have a look at that. Thanks for the help
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
