88x2bu driver for 8822cu? #102

marc8822 · 2021-11-24T11:08:46Z

marc8822
Nov 24, 2021

Why is the 88x2bu driver not available for the 8822cu module (0bda:c82c)?
What is the difference between the cu and the bu?
Is it possible to make the 8822cu work with the 88x2bu driver?

Thanks for your support.

morrownr · 2021-11-24T16:39:18Z

morrownr
Nov 24, 2021
Maintainer

Why is the 88x2bu driver not available for the 8822cu module (0bda:c82c)?

The 88x2bu driver is for adapters that use the 8812bu abd 8822bu chipsets.

What is the difference between the cu and the bu?

Different chipsets. Reaktek has a history of creating a lot of different chipsets... unnecessarily in my opinion.

Is it possible to make the 8822cu work with the 88x2bu driver?

That is not practical. What you need is the correct driver:

https://github.com/morrownr/8821cu

Let me know if this driver works and don't forget to uninstall any drivers you have already installed.

Also, to avoid this kind of confusion, you can use adapters that use in-kernel drivers:

https://github.com/morrownr/USB-WiFi

Nick

1 reply

marc8822 Nov 25, 2021
Author

Thank you verry much for this answer.

I have a NanoPi NEO3 and I used a new image of dietpi, installed the 8821cu driver with the install guide in the README.md but the modul does not work with this driver.
After the installation, the comand lsusb does not work amnymore

root@DietPi:~# lsusb
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 0bda:c82c Realtek Semiconductor Corp. 802.11ac NIC
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

root@DietPi:~/src/8821cu# uname -a
Linux DietPi 5.10.63-rockchip64 #21.08.2 SMP PREEMPT Wed Sep 8 10:57:23 UTC 2021 aarch64 GNU/Linux

root@DietPi:~/src/8821cu# rfkill list all
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

root@DietPi:~/src/8821cu# dkms status
rtl8821cu, 5.8.1.7, 5.10.63-rockchip64, aarch64: installed

root@DietPi:~/src/8821cu# iw dev
root@DietPi:~/src/8821cu#

root@DietPi:~/src/8821cu# mokutil --sb-state
EFI variables are not supported on this system


Running install-driver.sh version 20210725
Starting installation.
Copying source files to: /usr/src/rtl8821cu-5.8.1.7
Copying 8821cu.conf to: /etc/modprobe.d

Creating symlink /var/lib/dkms/rtl8821cu/5.8.1.7/source ->
                 /usr/src/rtl8821cu-5.8.1.7

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
'make' -j4 KVER=5.10.63-rockchip64 KSRC=/lib/modules/5.10.63-rockchip64/build.............................................................................................................
cleaning build area...

DKMS: build completed.

8821cu.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/5.10.63-rockchip64/updates/dkms/

depmod.......

DKMS: install completed.
The driver was installed successfully.

root@DietPi:~# dmesg | grep usb
[    0.000000] Kernel command line: root=UUID=7f26bae3-11cc-4a08-bcc6-df7f80c7d91b rootwait rootfstype=ext4 console=ttyS2,1500000  consoleblank=0 loglevel=4 ubootpart=5bca314d-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u "net.ifnames=0"
[    1.278310] usbcore: registered new interface driver usbfs
[    1.278407] usbcore: registered new interface driver hub
[    1.278488] usbcore: registered new device driver usb
[    3.223463] dwc2 ff580000.usb: supply vusb_d not found, using dummy regulator
[    3.223763] dwc2 ff580000.usb: supply vusb_a not found, using dummy regulator
[    3.351213] dwc2 ff580000.usb: EPs: 10, dedicated fifos, 972 entries in SPRAM
[    3.351774] dwc2 ff580000.usb: DWC OTG Controller
[    3.351823] dwc2 ff580000.usb: new USB bus registered, assigned bus number 1
[    3.351890] dwc2 ff580000.usb: irq 36, io mem 0xff580000
[    3.352249] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    3.352268] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.352282] usb usb1: Product: DWC OTG Controller
[    3.352296] usb usb1: Manufacturer: Linux 5.10.63-rockchip64 dwc2_hsotg
[    3.352312] usb usb1: SerialNumber: ff580000.usb
[    3.359375] ehci-platform ff5c0000.usb: EHCI Host Controller
[    3.386323] ehci-platform ff5c0000.usb: new USB bus registered, assigned bus number 2
[    3.359701] ehci-platform ff5c0000.usb: irq 37, io mem 0xff5c0000
[    3.375126] ehci-platform ff5c0000.usb: USB 2.0 started, EHCI 1.00
[    3.375616] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    3.375630] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.375647] usb usb2: Product: EHCI Host Controller
[    3.375661] usb usb2: Manufacturer: Linux 5.10.63-rockchip64 ehci_hcd
[    3.375677] usb usb2: SerialNumber: ff5c0000.usb
[    3.378813] ohci-platform ff5d0000.usb: Generic Platform OHCI controller
[    3.378853] ohci-platform ff5d0000.usb: new USB bus registered, assigned bus number 3
[    3.379189] ohci-platform ff5d0000.usb: irq 38, io mem 0xff5d0000
[    3.443432] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.10
[    3.443450] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.443470] usb usb3: Product: Generic Platform OHCI controller
[    3.443484] usb usb3: Manufacturer: Linux 5.10.63-rockchip64 ohci_hcd
[    3.443500] usb usb3: SerialNumber: ff5d0000.usb
[    3.448075] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    3.448092] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.448112] usb usb4: Product: xHCI Host Controller
[    3.448126] usb usb4: Manufacturer: Linux 5.10.63-rockchip64 xhci-hcd
[    3.448143] usb usb4: SerialNumber: xhci-hcd.0.auto
[    3.450249] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM.
[    3.450522] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[    3.450535] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.450553] usb usb5: Product: xHCI Host Controller
[    3.450566] usb usb5: Manufacturer: Linux 5.10.63-rockchip64 xhci-hcd
[    3.450579] usb usb5: SerialNumber: xhci-hcd.0.auto
[    3.452808] usbcore: registered new interface driver usb-storage
[    3.525758] usbcore: registered new interface driver usbhid
[    3.525767] usbhid: USB HID core driver
[    3.707217] usb 4-1: new high-speed USB device number 2 using xhci-hcd
[    3.856033] usb 4-1: New USB device found, idVendor=0bda, idProduct=c82c, bcdDevice= 0.00
[    3.856061] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.856073] usb 4-1: Product: 802.11ac NIC
[    3.856084] usb 4-1: Manufacturer: Realtek
[    3.856095] usb 4-1: SerialNumber: 123456
[    7.451709] dwc2 ff580000.usb: bound driver g_serial
[   10.108566] usbcore: registered new interface driver btusb
[   10.344032] Modules linked in: 8821cu(OE ) btusb cfg80211 btrtl btbcm btintel bluetooth rfkill hantro_vpu(C) v4l2_h264 videobuf2_dma_contig v4l2_mem2mem videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc cpufreq_dt usb_f_acm u_serial g_serial libcomposite ip_tables x_tables autofs4 realtek dwmac_rk stmmac_platform stmmac pcs_xpcs gpio_syscon
[   10.345415]  rtw_usb_primary_adapter_init 0xc0/0x294 [8821cu]
[   10.364263]  usb_probe_interface 0xd8/0x2b8
[   10.367437]  usb_register_driver 0x80/0x158

morrownr · 2021-11-25T19:47:37Z

morrownr
Nov 25, 2021
Maintainer

Okay, I see the processor is a Rockchip and the os is DietPi. For future reference, that is VERY important information to pass on.

The best thing you can do right now is run

$ sudo ./remove-driver.sh
$ sudo reboot

That should clean things up and let us start over.

To solve this mystery, we need to figure out the exact Rockchip processor we are dealing with. In the Makefile I see references to the following:

RK2818
RK3188
RK3066

I need you to research the issue and figure out exactly what Rockchip processor you have. It could be one of the above or even a new one. Once that information is at hand, I can guide you though what needs to be done.

Different processors require different compiler flags. Step 8 of the Installation instructions as outlined in README.md, has a special script to run if you are running Raspberry Pi hardware. That is necessary because the Raspberry Pi runs an ARM processor. This driver defaults to x86/AMD64 processors and we have to make changes for other processors. I support Raspberry Pi's because I have a couple of them and folks from the community helped me put those scripts together.

Regards

1 reply

marc8822 Nov 26, 2021
Author

It is a RK3328 Quad-core 64-bit Cortex-A53 Rockchip processor

morrownr · 2021-11-26T16:53:09Z

morrownr
Nov 26, 2021
Maintainer

Okay, RK3328. The Rockchip configuration sections in the current Makefile are for earlier processors and are supporting Android. That means we have to figure it out.

My best guess at this point is that we need to add a section that looks something like this:

ifeq ($(CONFIG_PLATFORM_ARM64_RK3328), y)
EXTRA_CFLAGS = -DCONFIG_LITTLE_ENDIAN -DCONFIG_PLATFORM_ROCKCHIPS
EXTRA_CFLAGS = -DCONFIG_IOCTL_CFG80211 -DRTW_USE_CFG80211_STA_EVENT
EXTRA_CFLAGS = -fno-stack-protector
ARCH ?= arm64
CROSS_COMPILE ?=
KVER ?= $(shell uname -r)
KSRC := /lib/modules/$(KVER)/build
MODDESTDIR := /lib/modules/$(KVER)/kernel/drivers/net/wireless/
INSTALL_PREFIX :=
endif

This is as far as I can go for today as I will be busy for the next 2-3 days but maybe this gives you an idea. It might be a good idea to go to the support forum for the company that sells the hardware and see if you can get some information there.

Regards

1 reply

marc8822 Dec 6, 2021
Author

Hi Nick,
I didn't get any support from the manufactor of the chip. I tried the Flags you wrote above, but it still did not work.
Best regards
Marc

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

88x2bu driver for 8822cu? #102

{{title}}

Replies: 3 comments 3 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

88x2bu driver for 8822cu? #102

marc8822 Nov 24, 2021

Replies: 3 comments · 3 replies

morrownr Nov 24, 2021 Maintainer

marc8822 Nov 25, 2021 Author

morrownr Nov 25, 2021 Maintainer

marc8822 Nov 26, 2021 Author

morrownr Nov 26, 2021 Maintainer

marc8822 Dec 6, 2021 Author

marc8822
Nov 24, 2021

Replies: 3 comments 3 replies

morrownr
Nov 24, 2021
Maintainer

marc8822 Nov 25, 2021
Author

morrownr
Nov 25, 2021
Maintainer

marc8822 Nov 26, 2021
Author

morrownr
Nov 26, 2021
Maintainer

marc8822 Dec 6, 2021
Author