Possible conflict between iwlwifi and r8168 network drivers
0
nice people!
I have two network adapters in my desktop. One built into the motherbord that uses the wlp5s0 interface and the iwlwifi driver, and another, a pci one, that uses enp6s0 interface and r8168 driver.
Currently i can't use the enp6s0 interface and r8168 driver as my main wifi interface.
joao@SERVER:~$ ifconfig
enp6s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether e0:d5:5e:f4:6d:39 txqueuelen 1000 (Ethernet)
RX packets 138690 bytes 115736633 (115.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 170043 bytes 126741535 (126.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 43 base 0x9000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Loopback Local)
RX packets 5613 bytes 572319 (572.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5613 bytes 572319 (572.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.103 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::30f6:f123:2e8a:4c92 prefixlen 64 scopeid 0x20<link>
ether a4:c4:94:83:05:c2 txqueuelen 1000 (Ethernet)
RX packets 3814 bytes 2759380 (2.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4201 bytes 682605 (682.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
More info:
joao@SERVER:~$ #!/bin/bash
joao@SERVER:~$ for f in /sys/class/net/*; do
> dev=$(basename $f)
> driver=$(readlink $f/device/driver/module)
> if [ $driver ]; then
> driver=$(basename $driver)
> fi
> addr=$(cat $f/address)
> operstate=$(cat $f/operstate)
> printf "%10s [%s]: %10s (%s)n" "$dev" "$addr" "$driver" "$operstate"
> done
enp6s0 [e0:d5:5e:f4:6d:39]: r8168 (down)
lo [00:00:00:00:00:00]: (unknown)
wlp5s0 [a4:c4:94:83:05:c2]: iwlwifi (up)
Even when i do:
root@SERVER:/home/joao# sudo ifconfig enp6s0 up
The results remain.
The pci board is recognized by the system:
joao@SERVER:~$ lspci -nk
05:00.0 0280: 8086:08b1 (rev bb)
Subsystem: 8086:c070
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
06:00.0 0200: 10ec:8168 (rev 0c)
Subsystem: 1458:e000
Kernel driver in use: r8168
Kernel modules: r8168
And the driver seems right:
joao@SERVER:~$ modprobe -c | grep r8168
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
alias pci:v000010ECd00008161sv*sd*bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
Dependencies:
joao@SERVER:~$ modprobe --show-depends r8168
insmod /lib/modules/4.18.0-13-lowlatency/updates/dkms/r8168.ko
Authorization at boot:
joao@SERVER:~$ modprobe -R r8168
r8168
joao@SERVER:~$ modprobe -c | grep r8168
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
alias pci:v000010ECd00008161sv*sd*bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
This wierd result appears:
joao@SERVER:~$ sudo ethtool -i enp6s0
driver: r8168
version: 8.046.00-NAPI
firmware-version:
expansion-rom-version:
bus-info: 0000:06:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
And:
joao@SERVER:~$ sudo ethtool -i wlp5s0
driver: iwlwifi
version: 4.18.0-13-lowlatency
firmware-version: 17.948900127.0
expansion-rom-version:
bus-info: 0000:05:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
When i ping:
ping 192.168.0.1 -I wlp5s0
PING 192.168.0.1 (192.168.0.1) from 192.168.0.103 wlp5s0: 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=128 time=1.64 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=128 time=2.51 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=128 time=2.62 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=128 time=2.62 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=128 time=2.98 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=128 time=2.21 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=128 time=4.31 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=128 time=2.05 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=128 time=4.61 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=128 time=3.34 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=128 time=1.97 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=128 time=2.04 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=128 time=2.06 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=128 time=3.96 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=128 time=2.06 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=128 time=2.44 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=128 time=1.88 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=128 time=1.67 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=128 time=1.85 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=128 time=1.68 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=128 time=1.66 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=128 time=1.62 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=128 time=1.77 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=128 time=1.49 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=128 time=1.49 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=128 time=1.66 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=128 time=1.12 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=128 time=1.45 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=128 time=1.38 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=128 time=4.26 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=128 time=1.39 ms
^C
--- 192.168.0.1 ping statistics ---
31 packets transmitted, 31 received, 0% packet loss, time 83ms
rtt min/avg/max/mdev = 1.115/2.251/4.614/0.923 ms
joao@SERVER:~$ ping 192.168.0.1 -I enp6s0
ping: Warning: source address might be selected on device other than enp6s0.
PING 192.168.0.1 (192.168.0.1) from 192.168.0.103 enp6s0: 56(84) bytes of data.
^C
--- 192.168.0.1 ping statistics ---
17 packets transmitted, 0 received, 100% packet loss, time 394ms
joao@SERVER:~$ ping 151.101.1.69 -I enp6s0
ping: Warning: source address might be selected on device other than enp6s0.
PING 151.101.1.69 (151.101.1.69) from 192.168.0.103 enp6s0: 56(84) bytes of data.
^C
--- 151.101.1.69 ping statistics ---
13 packets transmitted, 0 received, 100% packet loss, time 301ms
How to solve it? I want my pci, that one that uses enp6s0 interface and r8168 driver as my only device comunicating thru wifi. How?
My system:
joao@SERVER:~$ uname -a
Linux SERVER 4.18.0-13-lowlatency #14-Ubuntu SMP PREEMPT Wed Dec 5 12:12:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
UPDATE! Still no good signal on wi-fi, usually 30% or more of packages lost.
More infos:
joao@SERVER:/$ cat /etc/netplan/*.yaml
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
networking drivers iwlwifi
asked Jan 10 at 19:45
Joao Henrique da SilvaJoao Henrique da Silva
11
New contributor
Joao Henrique da Silva is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
0
nice people!
I have two network adapters in my desktop. One built into the motherbord that uses the wlp5s0 interface and the iwlwifi driver, and another, a pci one, that uses enp6s0 interface and r8168 driver.
Currently i can't use the enp6s0 interface and r8168 driver as my main wifi interface.
joao@SERVER:~$ ifconfig
enp6s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether e0:d5:5e:f4:6d:39 txqueuelen 1000 (Ethernet)
RX packets 138690 bytes 115736633 (115.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 170043 bytes 126741535 (126.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 43 base 0x9000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Loopback Local)
RX packets 5613 bytes 572319 (572.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5613 bytes 572319 (572.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.103 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::30f6:f123:2e8a:4c92 prefixlen 64 scopeid 0x20<link>
ether a4:c4:94:83:05:c2 txqueuelen 1000 (Ethernet)
RX packets 3814 bytes 2759380 (2.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4201 bytes 682605 (682.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
More info:
joao@SERVER:~$ #!/bin/bash
joao@SERVER:~$ for f in /sys/class/net/*; do
> dev=$(basename $f)
> driver=$(readlink $f/device/driver/module)
> if [ $driver ]; then
> driver=$(basename $driver)
> fi
> addr=$(cat $f/address)
> operstate=$(cat $f/operstate)
> printf "%10s [%s]: %10s (%s)n" "$dev" "$addr" "$driver" "$operstate"
> done
enp6s0 [e0:d5:5e:f4:6d:39]: r8168 (down)
lo [00:00:00:00:00:00]: (unknown)
wlp5s0 [a4:c4:94:83:05:c2]: iwlwifi (up)
Even when i do:
root@SERVER:/home/joao# sudo ifconfig enp6s0 up
The results remain.
The pci board is recognized by the system:
joao@SERVER:~$ lspci -nk
05:00.0 0280: 8086:08b1 (rev bb)
Subsystem: 8086:c070
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
06:00.0 0200: 10ec:8168 (rev 0c)
Subsystem: 1458:e000
Kernel driver in use: r8168
Kernel modules: r8168
And the driver seems right:
joao@SERVER:~$ modprobe -c | grep r8168
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
alias pci:v000010ECd00008161sv*sd*bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
Dependencies:
joao@SERVER:~$ modprobe --show-depends r8168
insmod /lib/modules/4.18.0-13-lowlatency/updates/dkms/r8168.ko
Authorization at boot:
joao@SERVER:~$ modprobe -R r8168
r8168
joao@SERVER:~$ modprobe -c | grep r8168
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
alias pci:v000010ECd00008161sv*sd*bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
This wierd result appears:
joao@SERVER:~$ sudo ethtool -i enp6s0
driver: r8168
version: 8.046.00-NAPI
firmware-version:
expansion-rom-version:
bus-info: 0000:06:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
And:
joao@SERVER:~$ sudo ethtool -i wlp5s0
driver: iwlwifi
version: 4.18.0-13-lowlatency
firmware-version: 17.948900127.0
expansion-rom-version:
bus-info: 0000:05:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
When i ping:
ping 192.168.0.1 -I wlp5s0
PING 192.168.0.1 (192.168.0.1) from 192.168.0.103 wlp5s0: 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=128 time=1.64 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=128 time=2.51 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=128 time=2.62 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=128 time=2.62 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=128 time=2.98 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=128 time=2.21 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=128 time=4.31 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=128 time=2.05 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=128 time=4.61 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=128 time=3.34 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=128 time=1.97 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=128 time=2.04 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=128 time=2.06 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=128 time=3.96 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=128 time=2.06 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=128 time=2.44 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=128 time=1.88 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=128 time=1.67 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=128 time=1.85 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=128 time=1.68 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=128 time=1.66 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=128 time=1.62 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=128 time=1.77 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=128 time=1.49 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=128 time=1.49 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=128 time=1.66 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=128 time=1.12 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=128 time=1.45 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=128 time=1.38 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=128 time=4.26 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=128 time=1.39 ms
^C
--- 192.168.0.1 ping statistics ---
31 packets transmitted, 31 received, 0% packet loss, time 83ms
rtt min/avg/max/mdev = 1.115/2.251/4.614/0.923 ms
joao@SERVER:~$ ping 192.168.0.1 -I enp6s0
ping: Warning: source address might be selected on device other than enp6s0.
PING 192.168.0.1 (192.168.0.1) from 192.168.0.103 enp6s0: 56(84) bytes of data.
^C
--- 192.168.0.1 ping statistics ---
17 packets transmitted, 0 received, 100% packet loss, time 394ms
joao@SERVER:~$ ping 151.101.1.69 -I enp6s0
ping: Warning: source address might be selected on device other than enp6s0.
PING 151.101.1.69 (151.101.1.69) from 192.168.0.103 enp6s0: 56(84) bytes of data.
^C
--- 151.101.1.69 ping statistics ---
13 packets transmitted, 0 received, 100% packet loss, time 301ms
How to solve it? I want my pci, that one that uses enp6s0 interface and r8168 driver as my only device comunicating thru wifi. How?
My system:
joao@SERVER:~$ uname -a
Linux SERVER 4.18.0-13-lowlatency #14-Ubuntu SMP PREEMPT Wed Dec 5 12:12:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
UPDATE! Still no good signal on wi-fi, usually 30% or more of packages lost.
More infos:
joao@SERVER:/$ cat /etc/netplan/*.yaml
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
networking drivers iwlwifi
asked Jan 10 at 19:45
Joao Henrique da SilvaJoao Henrique da Silva
11
New contributor
Joao Henrique da Silva is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
"Currently i can't use the enp6s0 interface and r8168 driver as my main wifi interface." That's because the device in question is not a wifi device. It is an ethernet device,
– chili555
Jan 10 at 19:59
But the device has two antennas and says 2.4 Ghz and 5Ghz in it?
– Joao Henrique da Silva
Jan 10 at 20:12
The Intel wireless does, I'm sure. The Realtek ethernet does not, I'm sure. Please check again.
– chili555
Jan 10 at 20:28
You were right. i was really that lost. Thanks! lol
– Joao Henrique da Silva
Jan 10 at 20:40
Are you using netplan on this server? Edit your question and show mecat /etc/netplan/*.yaml. Report back to @heynnema
– heynnema
Jan 11 at 2:24
add a comment |
0
0
0
nice people!
I have two network adapters in my desktop. One built into the motherbord that uses the wlp5s0 interface and the iwlwifi driver, and another, a pci one, that uses enp6s0 interface and r8168 driver.
Currently i can't use the enp6s0 interface and r8168 driver as my main wifi interface.
joao@SERVER:~$ ifconfig
enp6s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether e0:d5:5e:f4:6d:39 txqueuelen 1000 (Ethernet)
RX packets 138690 bytes 115736633 (115.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 170043 bytes 126741535 (126.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 43 base 0x9000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Loopback Local)
RX packets 5613 bytes 572319 (572.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5613 bytes 572319 (572.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.103 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::30f6:f123:2e8a:4c92 prefixlen 64 scopeid 0x20<link>
ether a4:c4:94:83:05:c2 txqueuelen 1000 (Ethernet)
RX packets 3814 bytes 2759380 (2.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4201 bytes 682605 (682.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
More info:
joao@SERVER:~$ #!/bin/bash
joao@SERVER:~$ for f in /sys/class/net/*; do
> dev=$(basename $f)
> driver=$(readlink $f/device/driver/module)
> if [ $driver ]; then
> driver=$(basename $driver)
> fi
> addr=$(cat $f/address)
> operstate=$(cat $f/operstate)
> printf "%10s [%s]: %10s (%s)n" "$dev" "$addr" "$driver" "$operstate"
> done
enp6s0 [e0:d5:5e:f4:6d:39]: r8168 (down)
lo [00:00:00:00:00:00]: (unknown)
wlp5s0 [a4:c4:94:83:05:c2]: iwlwifi (up)
Even when i do:
root@SERVER:/home/joao# sudo ifconfig enp6s0 up
The results remain.
The pci board is recognized by the system:
joao@SERVER:~$ lspci -nk
05:00.0 0280: 8086:08b1 (rev bb)
Subsystem: 8086:c070
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
06:00.0 0200: 10ec:8168 (rev 0c)
Subsystem: 1458:e000
Kernel driver in use: r8168
Kernel modules: r8168
And the driver seems right:
joao@SERVER:~$ modprobe -c | grep r8168
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
alias pci:v000010ECd00008161sv*sd*bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
Dependencies:
joao@SERVER:~$ modprobe --show-depends r8168
insmod /lib/modules/4.18.0-13-lowlatency/updates/dkms/r8168.ko
Authorization at boot:
joao@SERVER:~$ modprobe -R r8168
r8168
joao@SERVER:~$ modprobe -c | grep r8168
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
alias pci:v000010ECd00008161sv*sd*bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
This wierd result appears:
joao@SERVER:~$ sudo ethtool -i enp6s0
driver: r8168
version: 8.046.00-NAPI
firmware-version:
expansion-rom-version:
bus-info: 0000:06:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
And:
joao@SERVER:~$ sudo ethtool -i wlp5s0
driver: iwlwifi
version: 4.18.0-13-lowlatency
firmware-version: 17.948900127.0
expansion-rom-version:
bus-info: 0000:05:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
When i ping:
ping 192.168.0.1 -I wlp5s0
PING 192.168.0.1 (192.168.0.1) from 192.168.0.103 wlp5s0: 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=128 time=1.64 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=128 time=2.51 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=128 time=2.62 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=128 time=2.62 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=128 time=2.98 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=128 time=2.21 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=128 time=4.31 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=128 time=2.05 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=128 time=4.61 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=128 time=3.34 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=128 time=1.97 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=128 time=2.04 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=128 time=2.06 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=128 time=3.96 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=128 time=2.06 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=128 time=2.44 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=128 time=1.88 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=128 time=1.67 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=128 time=1.85 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=128 time=1.68 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=128 time=1.66 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=128 time=1.62 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=128 time=1.77 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=128 time=1.49 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=128 time=1.49 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=128 time=1.66 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=128 time=1.12 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=128 time=1.45 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=128 time=1.38 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=128 time=4.26 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=128 time=1.39 ms
^C
--- 192.168.0.1 ping statistics ---
31 packets transmitted, 31 received, 0% packet loss, time 83ms
rtt min/avg/max/mdev = 1.115/2.251/4.614/0.923 ms
joao@SERVER:~$ ping 192.168.0.1 -I enp6s0
ping: Warning: source address might be selected on device other than enp6s0.
PING 192.168.0.1 (192.168.0.1) from 192.168.0.103 enp6s0: 56(84) bytes of data.
^C
--- 192.168.0.1 ping statistics ---
17 packets transmitted, 0 received, 100% packet loss, time 394ms
joao@SERVER:~$ ping 151.101.1.69 -I enp6s0
ping: Warning: source address might be selected on device other than enp6s0.
PING 151.101.1.69 (151.101.1.69) from 192.168.0.103 enp6s0: 56(84) bytes of data.
^C
--- 151.101.1.69 ping statistics ---
13 packets transmitted, 0 received, 100% packet loss, time 301ms
How to solve it? I want my pci, that one that uses enp6s0 interface and r8168 driver as my only device comunicating thru wifi. How?
My system:
joao@SERVER:~$ uname -a
Linux SERVER 4.18.0-13-lowlatency #14-Ubuntu SMP PREEMPT Wed Dec 5 12:12:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
UPDATE! Still no good signal on wi-fi, usually 30% or more of packages lost.
More infos:
joao@SERVER:/$ cat /etc/netplan/*.yaml
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
networking drivers iwlwifi
asked Jan 10 at 19:45
Joao Henrique da SilvaJoao Henrique da Silva
11
New contributor
Joao Henrique da Silva is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
nice people!
I have two network adapters in my desktop. One built into the motherbord that uses the wlp5s0 interface and the iwlwifi driver, and another, a pci one, that uses enp6s0 interface and r8168 driver.
Currently i can't use the enp6s0 interface and r8168 driver as my main wifi interface.
joao@SERVER:~$ ifconfig
enp6s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether e0:d5:5e:f4:6d:39 txqueuelen 1000 (Ethernet)
RX packets 138690 bytes 115736633 (115.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 170043 bytes 126741535 (126.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 43 base 0x9000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Loopback Local)
RX packets 5613 bytes 572319 (572.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5613 bytes 572319 (572.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.103 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::30f6:f123:2e8a:4c92 prefixlen 64 scopeid 0x20<link>
ether a4:c4:94:83:05:c2 txqueuelen 1000 (Ethernet)
RX packets 3814 bytes 2759380 (2.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4201 bytes 682605 (682.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
More info:
joao@SERVER:~$ #!/bin/bash
joao@SERVER:~$ for f in /sys/class/net/*; do
> dev=$(basename $f)
> driver=$(readlink $f/device/driver/module)
> if [ $driver ]; then
> driver=$(basename $driver)
> fi
> addr=$(cat $f/address)
> operstate=$(cat $f/operstate)
> printf "%10s [%s]: %10s (%s)n" "$dev" "$addr" "$driver" "$operstate"
> done
enp6s0 [e0:d5:5e:f4:6d:39]: r8168 (down)
lo [00:00:00:00:00:00]: (unknown)
wlp5s0 [a4:c4:94:83:05:c2]: iwlwifi (up)
Even when i do:
root@SERVER:/home/joao# sudo ifconfig enp6s0 up
The results remain.
The pci board is recognized by the system:
joao@SERVER:~$ lspci -nk
05:00.0 0280: 8086:08b1 (rev bb)
Subsystem: 8086:c070
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
06:00.0 0200: 10ec:8168 (rev 0c)
Subsystem: 1458:e000
Kernel driver in use: r8168
Kernel modules: r8168
And the driver seems right:
joao@SERVER:~$ modprobe -c | grep r8168
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
alias pci:v000010ECd00008161sv*sd*bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
Dependencies:
joao@SERVER:~$ modprobe --show-depends r8168
insmod /lib/modules/4.18.0-13-lowlatency/updates/dkms/r8168.ko
Authorization at boot:
joao@SERVER:~$ modprobe -R r8168
r8168
joao@SERVER:~$ modprobe -c | grep r8168
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
alias pci:v000010ECd00008161sv*sd*bc*sc*i* r8168
alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8168
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168
This wierd result appears:
joao@SERVER:~$ sudo ethtool -i enp6s0
driver: r8168
version: 8.046.00-NAPI
firmware-version:
expansion-rom-version:
bus-info: 0000:06:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
And:
joao@SERVER:~$ sudo ethtool -i wlp5s0
driver: iwlwifi
version: 4.18.0-13-lowlatency
firmware-version: 17.948900127.0
expansion-rom-version:
bus-info: 0000:05:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
When i ping:
ping 192.168.0.1 -I wlp5s0
PING 192.168.0.1 (192.168.0.1) from 192.168.0.103 wlp5s0: 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=128 time=1.64 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=128 time=2.51 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=128 time=2.62 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=128 time=2.62 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=128 time=2.98 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=128 time=2.21 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=128 time=4.31 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=128 time=2.05 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=128 time=4.61 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=128 time=3.34 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=128 time=1.97 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=128 time=2.04 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=128 time=2.06 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=128 time=3.96 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=128 time=2.06 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=128 time=2.44 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=128 time=1.88 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=128 time=1.67 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=128 time=1.85 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=128 time=1.68 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=128 time=1.66 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=128 time=1.62 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=128 time=1.77 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=128 time=1.49 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=128 time=1.49 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=128 time=1.66 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=128 time=1.12 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=128 time=1.45 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=128 time=1.38 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=128 time=4.26 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=128 time=1.39 ms
^C
--- 192.168.0.1 ping statistics ---
31 packets transmitted, 31 received, 0% packet loss, time 83ms
rtt min/avg/max/mdev = 1.115/2.251/4.614/0.923 ms
joao@SERVER:~$ ping 192.168.0.1 -I enp6s0
ping: Warning: source address might be selected on device other than enp6s0.
PING 192.168.0.1 (192.168.0.1) from 192.168.0.103 enp6s0: 56(84) bytes of data.
^C
--- 192.168.0.1 ping statistics ---
17 packets transmitted, 0 received, 100% packet loss, time 394ms
joao@SERVER:~$ ping 151.101.1.69 -I enp6s0
ping: Warning: source address might be selected on device other than enp6s0.
PING 151.101.1.69 (151.101.1.69) from 192.168.0.103 enp6s0: 56(84) bytes of data.
^C
--- 151.101.1.69 ping statistics ---
13 packets transmitted, 0 received, 100% packet loss, time 301ms
How to solve it? I want my pci, that one that uses enp6s0 interface and r8168 driver as my only device comunicating thru wifi. How?
My system:
joao@SERVER:~$ uname -a
Linux SERVER 4.18.0-13-lowlatency #14-Ubuntu SMP PREEMPT Wed Dec 5 12:12:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
UPDATE! Still no good signal on wi-fi, usually 30% or more of packages lost.
More infos:
joao@SERVER:/$ cat /etc/netplan/*.yaml
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
networking drivers iwlwifi
networking drivers iwlwifi
asked Jan 10 at 19:45
Joao Henrique da SilvaJoao Henrique da Silva
11
New contributor
Joao Henrique da Silva is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 10 at 19:45
Joao Henrique da SilvaJoao Henrique da Silva
11
New contributor
Joao Henrique da Silva is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 10 hours ago
Joao Henrique da Silva
asked Jan 10 at 19:45
Joao Henrique da SilvaJoao Henrique da Silva
11
New contributor
Joao Henrique da Silva is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 10 at 19:45
Joao Henrique da SilvaJoao Henrique da Silva
11
asked Jan 10 at 19:45
Joao Henrique da SilvaJoao Henrique da Silva
11
11
New contributor
Joao Henrique da Silva is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Joao Henrique da Silva is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Joao Henrique da Silva is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
"Currently i can't use the enp6s0 interface and r8168 driver as my main wifi interface." That's because the device in question is not a wifi device. It is an ethernet device,
– chili555
Jan 10 at 19:59
But the device has two antennas and says 2.4 Ghz and 5Ghz in it?
– Joao Henrique da Silva
Jan 10 at 20:12
The Intel wireless does, I'm sure. The Realtek ethernet does not, I'm sure. Please check again.
– chili555
Jan 10 at 20:28
You were right. i was really that lost. Thanks! lol
– Joao Henrique da Silva
Jan 10 at 20:40
Are you using netplan on this server? Edit your question and show mecat /etc/netplan/*.yaml. Report back to @heynnema
– heynnema
Jan 11 at 2:24
add a comment |
"Currently i can't use the enp6s0 interface and r8168 driver as my main wifi interface." That's because the device in question is not a wifi device. It is an ethernet device,
– chili555
Jan 10 at 19:59
But the device has two antennas and says 2.4 Ghz and 5Ghz in it?
– Joao Henrique da Silva
Jan 10 at 20:12
The Intel wireless does, I'm sure. The Realtek ethernet does not, I'm sure. Please check again.
– chili555
Jan 10 at 20:28
You were right. i was really that lost. Thanks! lol
– Joao Henrique da Silva
Jan 10 at 20:40
Are you using netplan on this server? Edit your question and show mecat /etc/netplan/*.yaml. Report back to @heynnema
– heynnema
Jan 11 at 2:24
"Currently i can't use the enp6s0 interface and r8168 driver as my main wifi interface." That's because the device in question is not a wifi device. It is an ethernet device,
– chili555
Jan 10 at 19:59
"Currently i can't use the enp6s0 interface and r8168 driver as my main wifi interface." That's because the device in question is not a wifi device. It is an ethernet device,
– chili555
Jan 10 at 19:59
But the device has two antennas and says 2.4 Ghz and 5Ghz in it?
– Joao Henrique da Silva
Jan 10 at 20:12
But the device has two antennas and says 2.4 Ghz and 5Ghz in it?
– Joao Henrique da Silva
Jan 10 at 20:12
The Intel wireless does, I'm sure. The Realtek ethernet does not, I'm sure. Please check again.
– chili555
Jan 10 at 20:28
The Intel wireless does, I'm sure. The Realtek ethernet does not, I'm sure. Please check again.
– chili555
Jan 10 at 20:28
You were right. i was really that lost. Thanks! lol
– Joao Henrique da Silva
Jan 10 at 20:40
You were right. i was really that lost. Thanks! lol
– Joao Henrique da Silva
Jan 10 at 20:40
Are you using netplan on this server? Edit your question and show me
cat /etc/netplan/*.yaml. Report back to @heynnema– heynnema
Jan 11 at 2:24
Are you using netplan on this server? Edit your question and show me
cat /etc/netplan/*.yaml. Report back to @heynnema– heynnema
Jan 11 at 2:24
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Joao Henrique da Silva is a new contributor. Be nice, and check out our Code of Conduct.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1108680%2fpossible-conflict-between-iwlwifi-and-r8168-network-drivers%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Joao Henrique da Silva is a new contributor. Be nice, and check out our Code of Conduct.
draft saved
draft discarded
Joao Henrique da Silva is a new contributor. Be nice, and check out our Code of Conduct.
Joao Henrique da Silva is a new contributor. Be nice, and check out our Code of Conduct.
Joao Henrique da Silva is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1108680%2fpossible-conflict-between-iwlwifi-and-r8168-network-drivers%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
"Currently i can't use the enp6s0 interface and r8168 driver as my main wifi interface." That's because the device in question is not a wifi device. It is an ethernet device,
– chili555
Jan 10 at 19:59
But the device has two antennas and says 2.4 Ghz and 5Ghz in it?
– Joao Henrique da Silva
Jan 10 at 20:12
The Intel wireless does, I'm sure. The Realtek ethernet does not, I'm sure. Please check again.
– chili555
Jan 10 at 20:28
You were right. i was really that lost. Thanks! lol
– Joao Henrique da Silva
Jan 10 at 20:40
Are you using netplan on this server? Edit your question and show me
cat /etc/netplan/*.yaml. Report back to @heynnema– heynnema
Jan 11 at 2:24