Why are you on 3.8.8? Why not on 3.8.13? Or 3.10.17 - the official Slackware kernel?

So the module is loaded.

Of course there is nothing there, you must use CONFIG_R8169 (in uppercase).

Of course, it is. Try No, someday someone will stumble over this thread and get completely confused by your posts. So let's make things completely clear. I know, you now are not interested in this topic anymore, because it works for you, but this is a public forum and not your personal support system.

I don't know why I'm on 3.8.8 - it was the slackware source at some point. I built it, and don't use the standard kernels for long because
1. The generic needs an initrd which is a PITA
2. The huge kernel is just that - huge.
3. Usually there's some modules I want in, or some I want out, from the slackware selection.
4. I get to profile the cpu/chipset for what this particular box is. This is running an I3 and intel chipset, sony sdcard reader, realtek & atheros cards. It's not going to need chipset bugfixes, modules for cards from the last millenium, etc. etc.
5. Adittionally, this is running on a a 60gb ssd, sp space is an issue.

I take your point about the public support forum. I left off cramming for exams to get to the bottom of it. I was getting very mysteriouys behaviour. I had compiled, and installed 3.8.8-6, but had failed to execute the lilo command, so 3.8.8-5 still booted. My bad. I had installed the module to 3.8.8-5 well, of course, and it came up on that reboot.

Now I am on 3.8.8-6. /sys/module/r8168 exists, not r8169. modinfo only returns blurb on r8168, as does lsmod. And the card is tested and working.

I'll leave you to ponder why the box chose that of all reboots to stop listening to the compiled in code and start listening to the module. Next post after next Friday.

I have a rev 6 card like those above, but it refuses to work on kernels 3.10.x or 3.12.x, with either r8169 or r8168 from the realtek site. BIOS has been updated to the latest available for this board.
http://www.gigabyte.us/products/prod...px?pid=4492#dl

I am giving up and using a PCI ethernet card I have handy for such cases.

Nevermind, it does work with the r8168 module. My network switch just died, and after replacing it, it works.

i too get that problem - today install slackware64 14.1, and get not working ethernet


03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
it is build in inteld945gcnl motherboard.
on slackware 13.37 with default kernel it works beautiful from box with r8169 driver.
now there, in slack 14.1 also i r8169 driver loaded, but it not work - try to read this topic and looks, what i can do. for a hard case i have 3com 3c905b NIC, who's driver, i hope, not ruined in 3.10 kernels...

it is fantastic stream - broke many things, who earlier work good, in newest soft ( kernel)...

rmmod and blacklist r8169, install r8168 from the realtek website and you should be good to go.

To blacklist modules, add:
to one of the .conf files at '/lib/modprobe.d', or create your own, but it must end in .conf

sorry, in my case there is another problem, i ve sorted out - udev for unknown to me reason, add a string in /etc/udev/rules.d/70-persistent-net.rules

# PCI device 0x8086:/sys/devices/pci0000:00/0000:00:19.0 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:16:41:3a:3b:b8", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

as so my realtek 8169 has be eth1, not eth0.
i do not -oh yes, remember! there is a very big problems with trying to install slack64 14.1 in that machine, and i do installation on another machine, where, looks like, ethernet adapter is be e1000...
ok, i comment that "subsystem" string, and all works ok now.

btw, maybe anyone can tell, how i can see a module - hardware - device dependancies in linux?
i mean do a command, and he show you - you have intel pro 1000 NIC, who was hooked by e1000e module, and will be eth4 ...?

Quote from ../slackware64-14.1/CHANGES_AND_HINTS.TXT:lspci -vnn # won't tell that it will be eth4, though.

1 members found this post helpful.