[SOLVED] my tplink wn722n wlan doesn’t working after updating manjaro

T_L_O_T_D

Distinguished
Dec 11, 2008
21
0
18,510
after updating my kernel to Kernel: 5.6.19-2-MANJARO x86_64 my wlan doesn't show any AP.
but if i boot with 5.4.52-1 its start working
here are my info
what should i do?
Code:
System:    Host: milad-Linux Kernel: 5.6.19-2-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.19.3 Distro: Manjaro Linux 
Machine:   Type: Desktop System: ASUS product: All Series v: N/A serial: <root required> 
           Mobo: ASUSTeK model: Z97-PRO GAMER v: Rev X.0x serial: <root required> UEFI: American Megatrends v: 2202 
           date: 12/08/2015 
CPU:       Topology: Quad Core model: Intel Core i5-4690K bits: 64 type: MCP L2 cache: 6144 KiB 
           Speed: 1086 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 999 2: 1000 3: 1000 4: 1000 
Graphics:  Device-1: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 440.100 
           Display: x11 server: X.Org 1.20.8 driver: nvidia resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 440.100 
Audio:     Device-1: Intel 9 Series Family HD Audio driver: snd_hda_intel 
           Device-2: NVIDIA GM204 High Definition Audio driver: snd_hda_intel 
           Device-3: Conexant Systems CX23880/1/2/3 PCI Video and Audio Decoder driver: cx8800 
           Device-4: Conexant Systems CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] driver: cx88-mpeg driver manager 
           Sound Server: ALSA v: k5.6.19-2-MANJARO 
Network:   Device-1: Intel Ethernet I218-V driver: e1000e 
           IF: eno1 state: up speed: 100 Mbps duplex: full mac: 08:62:66:2a:c0:a2 
           Device-2: Qualcomm Atheros AR9271 802.11n type: USB driver: usb-network 
Drives:    Local Storage: total: 2.96 TiB used: 69.78 GiB (2.3%) 
           ID-1: /dev/nvme0n1 vendor: PNY model: CS3030 500GB SSD size: 465.76 GiB 
           ID-2: /dev/sda vendor: Seagate model: ST3500418AS size: 465.76 GiB 
           ID-3: /dev/sdb vendor: Maxtor model: STM3250310AS size: 232.89 GiB 
           ID-4: /dev/sdc vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB 
Partition: ID-1: / size: 108.60 GiB used: 18.48 GiB (17.0%) fs: ext4 dev: /dev/nvme0n1p4 
           ID-2: swap-1 size: 4.10 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p5 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 46 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 0% 
Info:      Processes: 212 Uptime: 21m Memory: 7.72 GiB used: 1.72 GiB (22.3%) Shell: bash inxi: 3.0.37
 
Solution
So looks like you found the solution in the other forum, btw:

the driver you need seems an "out of tree" propertary driver. What does it mean ?
It means that is not compiled with the kernel itself, nor built-in [*] or as a loadable module [M], it is simply not in the upstream (or upstream distro patched) kernel.

So you probably had it already in the rootfs the propertary driver "driver.ko" but what is the fact: drivers out of tree compiled against a different kernel version will not be loaded from the new kernel (modprobe complains).

So you need to have re-installed an AUR package, that should be 8192eu-dkms.

bigendian

Reputable
Nov 10, 2019
20
3
4,525
So looks like you found the solution in the other forum, btw:

the driver you need seems an "out of tree" propertary driver. What does it mean ?
It means that is not compiled with the kernel itself, nor built-in [*] or as a loadable module [M], it is simply not in the upstream (or upstream distro patched) kernel.

So you probably had it already in the rootfs the propertary driver "driver.ko" but what is the fact: drivers out of tree compiled against a different kernel version will not be loaded from the new kernel (modprobe complains).

So you need to have re-installed an AUR package, that should be 8192eu-dkms.
 
Solution

T_L_O_T_D

Distinguished
Dec 11, 2008
21
0
18,510
So looks like you found the solution in the other forum, btw:

the driver you need seems an "out of tree" propertary driver. What does it mean ?
It means that is not compiled with the kernel itself, nor built-in [*] or as a loadable module [M], it is simply not in the upstream (or upstream distro patched) kernel.

So you probably had it already in the rootfs the propertary driver "driver.ko" but what is the fact: drivers out of tree compiled against a different kernel version will not be loaded from the new kernel (modprobe complains).

So you need to have re-installed an AUR package, that should be 8192eu-dkms.
I did this, tried to reinstall the package again but it was not working, but after updating kernel it starts to work again