R8168 Ethernet - why isnt this working?

Technical Issues and Assistance Networking
#1

~ >>> echo "blacklist r8169" > /etc/modprobe.d/r8169_blacklist.conf
zsh: permission denied: /etc/modprobe.d/r8169_blacklist.conf
~ >>> sudo echo "blacklist r8169" > /etc/modprobe.d/r8169_blacklist.conf [1]
zsh: permission denied: /etc/modprobe.d/r8169_blacklist.conf
~ >>> sudo echo "blacklist r8169" > /etc/modprobe.d/r8169_blacklist.conf [1]
zsh: permission denied: /etc/modprobe.d/r8169_blacklist.conf
~ >>> echo "blacklist r8169" > /etc/modprobe.d/r8169_blacklist.conf [1]
zsh: permission denied: /etc/modprobe.d/r8169_blacklist.conf
~ >>>

Writing Systemd Service Units
internet / Network problems + printer not found
internet / Network problems + printer not found
#2

Try this:
echo -e "blacklist r8169" | sudo tee -a /etc/modprobe.d/r8169_blacklist.conf
I guess you will get an explanation soon. :slight_smile:

3 Likes
#3

This one fails because it's a root-owned file and you didn't use sudo.

Where does that [1] come from at the end of the line? Did you type that as (supposedly) part of the filename?

What is the output of... :arrow_lower_left:

ls -l /etc/modprobe.d/r8169*
2 Likes
#4

This one should normally work, but it'll ask you for the root password, not your own password... :arrow_lower_left:

su -c 'echo "blacklist r8169" > /etc/modprobe.d/r8169_blacklist.conf'
1 Like
#5

All great answers truly... ty. my wired still doesnt work even with r8168 installed and 89 blacklisted... oh well... craziest thing. device is still listed as up and still doesnt connect to the internet and i did reboot and watch the thing time out on boot up

1 Like
#6

I'd skip the "-a", I don't think appending is what you'd want.

Simply:

echo -e "blacklist r8169" | sudo tee /etc/modprobe.d/r8169_blacklist.conf

Nitpickicking of course.

3 Likes
#7

DNS issue?

2 Likes
#8

how would i know? i got an error there were no ip adresses available.. i remember that

#9

ls -l /etc/modprobe.d/r8169*

-rw-r--r-- 1 root root 32 May 24 00:41 /etc/modprobe.d/r8169_blacklist.conf

but i did get it to run the first one offered so it should be showing as it does now.

1 Like
#10

Ping google

ping -c5 8.8.8.8                                                                              
ping -c5 google.com

post

2 Likes
#11

ok but i am on that machine with wifi working but not etherent so should i ping with wifi on or off?

#12

Did you reboot after installing r8168? It's a kernel module, so you need to either load it with modprobe or reboot the system. And even though you've blacklisted r8169 now, it may still be loaded into the kernel, in which case it'll prevent the r8168 from accessing your NIC.

1 Like
#13

i did reboot the system

i also dont see it loaded

how to tell if it is loaded?

#14 
~ >>> ping -c5 8.8.8.8                                                                                                                                                                                                                        
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=53 time=18.9 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=53 time=15.4 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=53 time=16.6 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=53 time=17.4 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=53 time=15.7 ms

--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms
rtt min/avg/max/mdev = 15.422/16.800/18.881/1.242 ms
~ >>> ping -c5 google.com                                                                                                                                                                                                                     
PING google.com(iad23s69-in-x0e.1e100.net (2607:f8b0:4004:815::200e)) 56 data bytes
64 bytes from iad23s69-in-x0e.1e100.net (2607:f8b0:4004:815::200e): icmp_seq=1 ttl=53 time=19.4 ms
64 bytes from iad23s69-in-x0e.1e100.net (2607:f8b0:4004:815::200e): icmp_seq=2 ttl=53 time=12.2 ms
64 bytes from iad23s69-in-x0e.1e100.net (2607:f8b0:4004:815::200e): icmp_seq=3 ttl=53 time=16.0 ms
64 bytes from iad23s69-in-x0e.1e100.net (2607:f8b0:4004:815::200e): icmp_seq=4 ttl=53 time=15.5 ms
64 bytes from iad23s69-in-x0e.1e100.net (2607:f8b0:4004:815::200e): icmp_seq=5 ttl=53 time=14.9 ms

--- google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 12.165/15.620/19.443/2.331 ms

~ >>> ping -c5 8.8.8.8                                                                                                                                                                                                                        
ping: connect: Network is unreachable
~ >>> ping -c5 google.com                                                                                                                                                                                                                  [2]
ping: google.com: Name or service not known
~ >>>
#15 
lsmod | grep r81
1 Like
#16

You must ping with wifi off.

2 Likes
#17

lsmod | grep r81
~ >>> [1]

#18

well i did ping with wifi off and you can see what happens when i do.

#19

Then you have a connection, the pings were successful.

1 Like
#20

lspci -k abbreviated

05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet
Kernel modules: r8169
06:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter
Subsystem: AzureWave RTL8821AE 802.11ac PCIe Wireless Network Adapter
Kernel driver in use: rtl8821ae
Kernel modules: rtl8821ae

but maybe iu have r8169 anyway? i black listed 89 but it still shows and 88 doesnt. i used the dkms version and installed kernel headers. i rebooted 2 times.

Forum kindly sponsored by