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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have my head down with exams atm and suddenly find myself embarrassed for this card. The module r8169 finds it and loads, but doesn't talk to anything.
I have kernel 3-8-8. I heard it was fixed in kernel 3.11, and also that it wasn't for some cards anyhow.
@ponce: Duly noted about kernel 3.12.6. It seems you have rev 06, and I have rev09 of the card (lcpci -n reports 10ec:8168) I'll go there asap.
@Didier I tried that driver this morning. It wants asm/system.h and is very insistent about it. I even tried fooling it with some other system.h but it wouldn't have it. I gather I have to go back to 2.x kernels for that. Somebody needs to tell Realtek. Thanks for the post, though. It was worth checking.
I can probably load the system with a fedora kernel if I get desperate. I ran fedora on the slackware kernel often.
@Didier I tried that driver this morning. It wants asm/system.h and is very insistent about it. I even tried fooling it with some other system.h but it wouldn't have it. I gather I have to go back to 2.x kernels for that.
You tried the wrong Realtek driver: r8169 6.017.00. That thing is unmaintained and for a different very old PCI NIC controller and doesn't support your PCIe NIC.
You need r8168 8.037. It compiles without modifications on Linux 3.10.17 included with Slackware 14.1. You also need to blacklist and remove the preinstalled r8169.ko from /lib/modules.
Long story short:
r8169 (from Linux 3.x) doesn't work with RTL8168/8111. It tries to, but fails. I think it's maintained by someone, who doesn't have the real thing (hardware) available for driver development and testing. It mostly works with a RTL8169 PCI card (I have one for testing), but's also slow and network throughput isn't great.
r8169 (from Realtek) doesn't work in your case. It is for RTL8169 and won't even detect you NIC, it's for the PCI card. (I attached a patch to make that driver compile on Linux 3.10 for the case someone needs that.)
r8168 (from Realtek) should work flawlessly and deliver wire-speed.
I built the module (which built painlessly - thx Didier) and installed it umpteen times. It transpires that somehow I had _compiled_in_ the r8169 module :-//.
Kernel rebuilds are less painful on SSD. Now I'm going. The module is r8168.ko but identifies as r8169.ko in lspci anyhow which is unnerving.
There _is_no_r8169.ko. I had to recompile the kernel (because it was compiled in) and I left it out.
The situation is tetotally weird. r8168 is in place, and the card now works, which is powerful evidence for that.
lsmod |grep r816* shows a blank - no r8168 or r8169 :-O. Even just 'lsmod' and picking through draws a blank.
grepping modules.dep only shows the r8168
Yet lspci-v reports (with or without a connection on it)
Code:
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 09)
Subsystem: Samsung Electronics Co Ltd Device c0d8
Flags: bus master, fast devsel, latency 0, IRQ 41
I/O ports at 2000 [size=256]
Memory at c0104000 (64-bit, prefetchable) [size=4K]
Memory at c0100000 (64-bit, prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: r8169
The Slackware kernel doesn't have r8169 compiled in. You're still using the compiled-in r8169 and for whatever reason it now works. lspci doesn't lie about that. Just look at /sys/module/r8169/version.
As I mentioned, lsmod draws a blank on it also. I think r8169 isn't there, jtsn. The output of lspci -v is strange, I'll admit. The card never worked with r8169, and it works now. Can we leave this one here?
Last edited by business_kid; 01-11-2014 at 04:10 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.