On 2023-02-08 00:55, Alexander V. Makartsev wrote:
Thanks Alexander, but installing firmware-realtek doesn't work. It was the first thing I tried. Secondly, the ASUS driver fails to compile under Bullseye & later. It throws an error:On 08.02.2023 09:07, Gary Dale wrote:
Your device should be based on "RTL8822B" chip from Realtek, so you need to install "firmware-realtek" package.I thought this would be easier than it's turned out to be. There are Internet posts going back years about support for this device but nothing recent - including a 5 year old Ubuntu post saying it works. Other wifi devices seem to be recognized out of the box or with a simple install of non-free firmware but not this one - at least not in Bullseye or Bookworm.
The adapter itself seems to be quite popular so I'm hoping someone can provide some clues on how to make it work
Thanks.
If after doing that you still didn't get a functioning network wifi adapter you might need to build driver kernel module. [1]
This is what I had to do to get USB Bluetooth adapter from Asus to work without issues, even though it is supported by kernel in "bullseye".
It is always the best to include extra information about your setup when you asking for help.
At least output from these commands would be a start:
$ uname -a
$ lsusb -v -t
# journalctl -b 0 --no-pager | grep -iE "rtl|rtk_|firmware"
If the output is long you can use "paste" service [2] and send us a link.
[1] https://www.asus.com/ca-en/networking-iot-servers/adapters/all-series/usb-ac53-nano/helpdesk_download/?model2Name=USB-AC53-Nano
[2] https://paste.debian.net/
--
1.5_33902.20190604_COEX20180928-6a6a/include/rtw_security.h:255:8: error: redefinition of ‘struct sha256_state’
255 | struct sha256_state {
| ^~~~~~~~~~~~
This is the same error I find in various drivers from GitHub. They all seem to be for older kernels and no longer compile. The fact that drivers have existed for so long was one reason I thought the device should be reasonably supported by now.
I had considered posting the output of lsusb but it simply shows that the device is recognized. Making it verbose returns a lot of capabilities information but not much else. Here it is:
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 480M
ID 0b05:184c ASUSTek Computer, Inc.
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
|__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
ID 0080:a001 Unknown JMS578 based SATA bridge
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 10000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 13: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M
ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
The journalctl command returns nothing.
Found a github repository that compiles on Bullseye at
https://github.com/morrownr/88x2bu. Then it's a matter of doing
the following as root
git clone https://github.com/morrownr/88x2bu
cd 88x2bu-20210702
## date string may different
make clean
make
make install
then
rebooting. The wifi dongle now shows in "ip addr".