search

cilynx / rtl88x2bu

rtl88x2bu driver updated for current kernels.
http://www.wolfteck.com/2018/02/22/wsky_1200mbps_wireless_usb_wifi_adapter/
GNU General Public License v2.0
1.61k stars 316 forks source link

Upgrade to ubuntu 23.04 and recompilation of rtl88x2bu driver causes driver to not work properly. #243

Closed Mk-arc closed 1 year ago

Mk-arc commented 1 year ago

Pretty much what is described in the headline.

Yesterday I upgraded my ubuntu from 22.10 to 23.04. Reboot directly after install caused kernel panics because of the rtl88x2bu package. had to boot with old kernel. pull the latest rtl88x2bu changes and rebuild the module (last commit: c866ad26b6ff58ee76cc13c71a28209366a75fee)

Now I can boot in the 6.2.0-20-generic kernel. However, the connection is suddenly very unrealiable. It worked perfectly fine before.

How can we debug this further? whats the matter?

ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.178.24 icmp_seq=1 Destination Host Unreachable
From 192.168.178.24 icmp_seq=2 Destination Host Unreachable
From 192.168.178.24 icmp_seq=3 Destination Host Unreachable
From 192.168.178.24 icmp_seq=4 Destination Host Unreachable
From 192.168.178.24 icmp_seq=5 Destination Host Unreachable
From 192.168.178.24 icmp_seq=6 Destination Host Unreachable
From 192.168.178.24 icmp_seq=7 Destination Host Unreachable
From 192.168.178.24 icmp_seq=8 Destination Host Unreachable
From 192.168.178.24 icmp_seq=10 Destination Host Unreachable
From 192.168.178.24 icmp_seq=11 Destination Host Unreachable
From 192.168.178.24 icmp_seq=12 Destination Host Unreachable
From 192.168.178.24 icmp_seq=13 Destination Host Unreachable
From 192.168.178.24 icmp_seq=14 Destination Host Unreachable
From 192.168.178.24 icmp_seq=15 Destination Host Unreachable
From 192.168.178.24 icmp_seq=16 Destination Host Unreachable
From 192.168.178.24 icmp_seq=17 Destination Host Unreachable
From 192.168.178.24 icmp_seq=18 Destination Host Unreachable
64 bytes from 8.8.8.8: icmp_seq=19 ttl=119 time=365 ms
64 bytes from 8.8.8.8: icmp_seq=20 ttl=119 time=9.56 ms
From 192.168.178.24 icmp_seq=21 Destination Host Unreachable
From 192.168.178.24 icmp_seq=22 Destination Host Unreachable
From 192.168.178.24 icmp_seq=23 Destination Host Unreachable
From 192.168.178.24 icmp_seq=24 Destination Host Unreachable
From 192.168.178.24 icmp_seq=25 Destination Host Unreachable
From 192.168.178.24 icmp_seq=26 Destination Host Unreachable
From 192.168.178.24 icmp_seq=27 Destination Host Unreachable
From 192.168.178.24 icmp_seq=28 Destination Host Unreachable
From 192.168.178.24 icmp_seq=29 Destination Host Unreachable
From 192.168.178.24 icmp_seq=30 Destination Host Unreachable
From 192.168.178.24 icmp_seq=31 Destination Host Unreachable
From 192.168.178.24 icmp_seq=32 Destination Host Unreachable
From 192.168.178.24 icmp_seq=33 Destination Host Unreachable
From 192.168.178.24 icmp_seq=34 Destination Host Unreachable
From 192.168.178.24 icmp_seq=35 Destination Host Unreachable
From 192.168.178.24 icmp_seq=36 Destination Host Unreachable
From 192.168.178.24 icmp_seq=37 Destination Host Unreachable
From 192.168.178.24 icmp_seq=38 Destination Host Unreachable
64 bytes from 8.8.8.8: icmp_seq=39 ttl=119 time=16.4 ms
64 bytes from 8.8.8.8: icmp_seq=40 ttl=119 time=16.0 ms
Mk-arc commented 1 year ago

It seems another pull from the latest sources and recompilation + dkms deploy fixed the issue.