[GH-ISSUE #49] [Bug]: compiling/building the driver fails on Arch 6.13.1-arch1-1 at os_dep/linux/os_intfs.o: error: expected ‘,’ or ‘;’ before ‘VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver’ #45

Open
opened 2026-10-13 19:33:25 +00:00 by bsakaguchi · 11 comments
Owner

Originally created by @BusterLundgaard on GitHub (Feb 4, 2025).
Original GitHub issue: https://github.com/morrownr/8812au-20210820/issues/49

Checklist

  • I am not using this driver from inside a Virtual Machine.
  • I performed all of the installation steps as written.
  • I have read the FAQ and my question is not answered there.

Is Secure Boot enabled?

No

uname

Linux buster 6.13.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 02 Feb 2025 01:02:29 +0000 x86_64 GNU/Linux

lsusb

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 
Bus 001 Device 003: ID 046d:c08b Logitech, Inc. G502 SE HERO Gaming Mouse 
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) 
Bus 001 Device 005: ID 2357:0101 TP-Link RTL8812AU Archer T4U 802.11ac 
Bus 001 Device 006: ID 1a2c:497a China Resource Semico Co., Ltd AFFFA0319 
Bus 001 Device 008: ID 2717:ff80 Xiaomi Inc. Mi/Redmi series (RNDIS) 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

rfkill

0: hci0: Bluetooth Soft blocked: no Hard blocked: no

dkms

(none, i have nothing installed)

iw

(none)

git status

Your branch is up to date with 'origin/main'.

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	.8812au.mod.cmd
	8812au.mod
	core/.rtw_ap.o.cmd
	core/.rtw_beamforming.o.cmd
	core/.rtw_br_ext.o.cmd
	core/.rtw_btcoex.o.cmd
	core/.rtw_btcoex_wifionly.o.cmd
	core/.rtw_chplan.o.cmd
	core/.rtw_cmd.o.cmd
	core/.rtw_debug.o.cmd
	core/.rtw_ft.o.cmd
	core/.rtw_ieee80211.o.cmd
	core/.rtw_io.o.cmd
	core/.rtw_ioctl_query.o.cmd
	core/.rtw_ioctl_set.o.cmd
	core/.rtw_iol.o.cmd
	core/.rtw_mbo.o.cmd
	core/.rtw_mi.o.cmd
	core/.rtw_mlme.o.cmd
	core/.rtw_mlme_ext.o.cmd
	core/.rtw_odm.o.cmd
	core/.rtw_p2p.o.cmd
	core/.rtw_pwrctrl.o.cmd
	core/.rtw_recv.o.cmd
	core/.rtw_rf.o.cmd
	core/.rtw_rm.o.cmd
	core/.rtw_rm_fsm.o.cmd
	core/.rtw_rm_util.o.cmd
	core/.rtw_roch.o.cmd
	core/.rtw_rson.o.cmd
	core/.rtw_security.o.cmd
	core/.rtw_sreset.o.cmd
	core/.rtw_sta_mgt.o.cmd
	core/.rtw_swcrypto.o.cmd
	core/.rtw_tdls.o.cmd
	core/.rtw_vht.o.cmd
	core/.rtw_wlan_util.o.cmd
	core/.rtw_wnm.o.cmd
	core/.rtw_xmit.o.cmd
	core/crypto/.aes-ccm.o.cmd
	core/crypto/.aes-ctr.o.cmd
	core/crypto/.aes-gcm.o.cmd
	core/crypto/.aes-internal-enc.o.cmd
	core/crypto/.aes-internal.o.cmd
	core/crypto/.aes-omac1.o.cmd
	core/crypto/.aes-siv.o.cmd
	core/crypto/.ccmp.o.cmd
	core/crypto/.gcmp.o.cmd
	core/crypto/.rtw_crypto_wrap.o.cmd
	core/crypto/.sha256-internal.o.cmd
	core/crypto/.sha256-prf.o.cmd
	core/crypto/.sha256.o.cmd
	core/crypto/aes-ccm.o
	core/crypto/aes-ctr.o
	core/crypto/aes-gcm.o
	core/crypto/aes-internal-enc.o
	core/crypto/aes-internal.o
	core/crypto/aes-omac1.o
	core/crypto/aes-siv.o
	core/crypto/ccmp.o
	core/crypto/gcmp.o
	core/crypto/rtw_crypto_wrap.o
	core/crypto/sha256-internal.o
	core/crypto/sha256-prf.o
	core/crypto/sha256.o
	core/efuse/.rtw_efuse.o.cmd
	core/efuse/rtw_efuse.o
	core/mesh/.rtw_mesh.o.cmd
	core/mesh/.rtw_mesh_hwmp.o.cmd
	core/mesh/.rtw_mesh_pathtbl.o.cmd
	core/mesh/rtw_mesh.o
	core/mesh/rtw_mesh_hwmp.o
	core/mesh/rtw_mesh_pathtbl.o
	core/monitor/.rtw_radiotap.o.cmd
	core/monitor/rtw_radiotap.o
	core/rtw_ap.o
	core/rtw_beamforming.o
	core/rtw_br_ext.o
	core/rtw_btcoex.o
	core/rtw_btcoex_wifionly.o
	core/rtw_chplan.o
	core/rtw_cmd.o
	core/rtw_debug.o
	core/rtw_ft.o
	core/rtw_ieee80211.o
	core/rtw_io.o
	core/rtw_ioctl_query.o
	core/rtw_ioctl_set.o
	core/rtw_iol.o
	core/rtw_mbo.o
	core/rtw_mi.o
	core/rtw_mlme.o
	core/rtw_mlme_ext.o
	core/rtw_odm.o
	core/rtw_p2p.o
	core/rtw_pwrctrl.o
	core/rtw_recv.o
	core/rtw_rf.o
	core/rtw_rm.o
	core/rtw_rm_fsm.o
	core/rtw_rm_util.o
	core/rtw_roch.o
	core/rtw_rson.o
	core/rtw_security.o
	core/rtw_sreset.o
	core/rtw_sta_mgt.o
	core/rtw_swcrypto.o
	core/rtw_tdls.o
	core/rtw_vht.o
	core/rtw_wlan_util.o
	core/rtw_wnm.o
	core/rtw_xmit.o
	core/wds/.rtw_wds.o.cmd
	core/wds/rtw_wds.o
	os_dep/.osdep_service.o.cmd
	os_dep/linux/.os_intfs.o.d
	os_dep/osdep_service.o

nothing added to commit but untracked files present (use "git add" to track)

install-driver.sh

: ---------------------------
: install-driver.sh v20241003
: x86_64 (kernel architecture)
: x86_64 (architecture to send to gcc)
: 12/12 (in-use/total processing units)
: 32714260 (total system memory)
: 6.13.1-arch1-1 (kernel version)
: gcc (version of gcc used to compile the kernel)
: gcc (GCC) 14.2.1 20250128
: dkms-3.1.5
: SecureBoot disabled
: ---------------------------

Checking for previously installed drivers...
Finished checking for and uninstalling previously installed drivers.
: ---------------------------

Starting installation.
Copying 8812au.conf to /etc/modprobe.d
The dkms installation routines are in use.
Copying source files to /usr/src/rtl8812au-5.13.6-23
Creating symlink /var/lib/dkms/rtl8812au/5.13.6-23/source -> /usr/src/rtl8812au-5.13.6-23
The driver was added to dkms successfully.
: ---------------------------

Sign command: /usr/lib/modules/6.13.1-arch1-1/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Cleaning build area... done.
Building module(s).....(bad exit status: 2)
Failed command:
kernelver=6.13.1-arch1-1 ./dkms-make.sh

Error! Bad return status for module build on kernel: 6.13.1-arch1-1 (x86_64)
Consult /var/lib/dkms/rtl8812au/5.13.6-23/build/make.log for more information.
An error occurred. dkms build error:  10
Please report this error.
Please copy all screen output and paste it into the problem report.
Run the following before reattempting installation.
$ sudo ./remove-driver.sh

What happened?

Hi! Since i couldn't connect to the internet after a recent update, i did what i usually do and:

-Tried to remove the rtl8812au driver using the uninstall script
-Uinstalled everything else in DKMS
-Updated everything with sudo pacman -Syu
-Reinstalled DKMS
-Tried to install rtl8812au with the install script again

But already when i was uninstalling i had issues. DKMS status said that the rtl8812au was "broken" and running the uninstall script i was told that it was missing the symbolic link. I then had to purge/remove rtl8812au.ko from /lib/modules/$(uname -r)/kernel/drivers/net/wireless/realtek/rtl8xxxu directly, and after running sudo depmod -a the driver seemed to be succesfully removed when i ran DKMS status.

As you can see, running the install-driver.sh script says that the build failed. I then ran make clean and make directly to have a more detailed look.

make clean gives me:

#make -C /lib/modules/6.13.1-arch1-1/build M=/home/buster/src/8812au-20210820 clean
cd hal ; rm -fr */*/*/*.mod.c */*/*/*.mod */*/*/*.o */*/*/.*.cmd */*/*/*.ko
cd hal ; rm -fr */*/*.mod.c */*/*.mod */*/*.o */*/.*.cmd */*/*.ko
cd hal ; rm -fr */*.mod.c */*.mod */*.o */.*.cmd */*.ko
cd hal ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd core ; rm -fr */*.mod.c */*.mod */*.o */.*.cmd */*.ko
cd core ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd os_dep/linux ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd os_dep ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd platform ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
rm -fr Module.symvers ; rm -fr Module.markers ; rm -fr modules.order
rm -fr *.mod.c *.mod *.o .*.cmd *.ko *~
rm -fr .tmp_versions
rm -fr MOK.der MOK.priv

make gives me:

make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/6.13.1-arch1-1/build M=/home/buster/src/8812au-20210820  modules
make[1]: Entering directory '/usr/lib/modules/6.13.1-arch1-1/build'
make[2]: Entering directory '/home/buster/src/8812au-20210820'
  CC [M]  core/rtw_cmd.o
  CC [M]  core/rtw_security.o
  CC [M]  core/rtw_debug.o
  CC [M]  core/rtw_io.o
  CC [M]  core/rtw_ioctl_query.o
  CC [M]  core/rtw_ioctl_set.o
  CC [M]  core/rtw_ieee80211.o
  CC [M]  core/rtw_mlme.o
  CC [M]  core/rtw_mlme_ext.o
  CC [M]  core/rtw_mi.o
  CC [M]  core/rtw_wlan_util.o
  CC [M]  core/rtw_vht.o
  CC [M]  core/rtw_pwrctrl.o
  CC [M]  core/rtw_rf.o
  CC [M]  core/rtw_chplan.o
  CC [M]  core/monitor/rtw_radiotap.o
  CC [M]  core/rtw_recv.o
  CC [M]  core/rtw_sta_mgt.o
  CC [M]  core/rtw_ap.o
  CC [M]  core/wds/rtw_wds.o
  CC [M]  core/mesh/rtw_mesh.o
  CC [M]  core/mesh/rtw_mesh_pathtbl.o
  CC [M]  core/mesh/rtw_mesh_hwmp.o
  CC [M]  core/rtw_xmit.o
  CC [M]  core/rtw_p2p.o
  CC [M]  core/rtw_rson.o
  CC [M]  core/rtw_tdls.o
  CC [M]  core/rtw_br_ext.o
  CC [M]  core/rtw_iol.o
  CC [M]  core/rtw_sreset.o
  CC [M]  core/rtw_btcoex_wifionly.o
  CC [M]  core/rtw_btcoex.o
  CC [M]  core/rtw_beamforming.o
  CC [M]  core/rtw_odm.o
  CC [M]  core/rtw_rm.o
  CC [M]  core/rtw_rm_fsm.o
  CC [M]  core/rtw_ft.o
  CC [M]  core/rtw_wnm.o
  CC [M]  core/rtw_mbo.o
  CC [M]  core/rtw_rm_util.o
  CC [M]  core/efuse/rtw_efuse.o
  CC [M]  core/rtw_roch.o
  CC [M]  core/crypto/aes-internal.o
  CC [M]  core/crypto/aes-internal-enc.o
  CC [M]  core/crypto/aes-gcm.o
  CC [M]  core/crypto/aes-ccm.o
  CC [M]  core/crypto/aes-omac1.o
  CC [M]  core/crypto/ccmp.o
  CC [M]  core/crypto/gcmp.o
  CC [M]  core/crypto/aes-siv.o
  CC [M]  core/crypto/aes-ctr.o
  CC [M]  core/crypto/sha256-internal.o
  CC [M]  core/crypto/sha256.o
  CC [M]  core/crypto/sha256-prf.o
  CC [M]  core/crypto/rtw_crypto_wrap.o
  CC [M]  core/rtw_swcrypto.o
  CC [M]  os_dep/osdep_service.o
  CC [M]  os_dep/linux/os_intfs.o
In file included from /usr/lib/modules/6.13.1-arch1-1/build/include/linux/module.h:22,
                 from ././include/basic_types.h:76,
                 from ././include/drv_types.h:26,
                 from os_dep/linux/os_intfs.c:17:
os_dep/linux/os_intfs.c:35:26: error: expected ‘,’ or ‘;’ before ‘VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver’
   35 |         MODULE_IMPORT_NS(VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver);
      |                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/lib/modules/6.13.1-arch1-1/build/include/linux/moduleparam.h:26:61: note: in definition of macro ‘__MODULE_INFO’
   26 |                 = __MODULE_INFO_PREFIX __stringify(tag) "=" info
      |                                                             ^~~~
/usr/lib/modules/6.13.1-arch1-1/build/include/linux/module.h:299:33: note: in expansion of macro ‘MODULE_INFO’
  299 | #define MODULE_IMPORT_NS(ns)    MODULE_INFO(import_ns, ns)
      |                                 ^~~~~~~~~~~
os_dep/linux/os_intfs.c:35:9: note: in expansion of macro ‘MODULE_IMPORT_NS’
   35 |         MODULE_IMPORT_NS(VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver);
      |         ^~~~~~~~~~~~~~~~
make[4]: *** [/usr/lib/modules/6.13.1-arch1-1/build/scripts/Makefile.build:194: os_dep/linux/os_intfs.o] Error 1
make[3]: *** [/usr/lib/modules/6.13.1-arch1-1/build/Makefile:1989: .] Error 2
make[2]: *** [/usr/lib/modules/6.13.1-arch1-1/build/Makefile:251: __sub-make] Error 2
make[2]: Leaving directory '/home/buster/src/8812au-20210820'
make[1]: *** [Makefile:251: __sub-make] Error 2
make[1]: Leaving directory '/usr/lib/modules/6.13.1-arch1-1/build'
make: *** [Makefile:2516: modules] Error 2

This seems like a bug no? But maybe i messed something up by trying to uninstall directly. I don't quite know where to go from here though.

Kind regards, and thanks for the amazing work!

Originally created by @BusterLundgaard on GitHub (Feb 4, 2025). Original GitHub issue: https://github.com/morrownr/8812au-20210820/issues/49 ### Checklist - [x] I am not using this driver from inside a Virtual Machine. - [x] I performed all of the [installation steps](/README.md#installation-steps) as written. - [x] I have read the [FAQ](/FAQ.md) and my question is not answered there. ### Is Secure Boot enabled? No ### uname Linux buster 6.13.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 02 Feb 2025 01:02:29 +0000 x86_64 GNU/Linux ### lsusb ``` Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 046d:c08b Logitech, Inc. G502 SE HERO Gaming Mouse Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 005: ID 2357:0101 TP-Link RTL8812AU Archer T4U 802.11ac Bus 001 Device 006: ID 1a2c:497a China Resource Semico Co., Ltd AFFFA0319 Bus 001 Device 008: ID 2717:ff80 Xiaomi Inc. Mi/Redmi series (RNDIS) Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub ``` ### rfkill 0: hci0: Bluetooth Soft blocked: no Hard blocked: no ### dkms ```text (none, i have nothing installed) ``` ### iw ```text (none) ``` ### git status ```text Your branch is up to date with 'origin/main'. Untracked files: (use "git add <file>..." to include in what will be committed) .8812au.mod.cmd 8812au.mod core/.rtw_ap.o.cmd core/.rtw_beamforming.o.cmd core/.rtw_br_ext.o.cmd core/.rtw_btcoex.o.cmd core/.rtw_btcoex_wifionly.o.cmd core/.rtw_chplan.o.cmd core/.rtw_cmd.o.cmd core/.rtw_debug.o.cmd core/.rtw_ft.o.cmd core/.rtw_ieee80211.o.cmd core/.rtw_io.o.cmd core/.rtw_ioctl_query.o.cmd core/.rtw_ioctl_set.o.cmd core/.rtw_iol.o.cmd core/.rtw_mbo.o.cmd core/.rtw_mi.o.cmd core/.rtw_mlme.o.cmd core/.rtw_mlme_ext.o.cmd core/.rtw_odm.o.cmd core/.rtw_p2p.o.cmd core/.rtw_pwrctrl.o.cmd core/.rtw_recv.o.cmd core/.rtw_rf.o.cmd core/.rtw_rm.o.cmd core/.rtw_rm_fsm.o.cmd core/.rtw_rm_util.o.cmd core/.rtw_roch.o.cmd core/.rtw_rson.o.cmd core/.rtw_security.o.cmd core/.rtw_sreset.o.cmd core/.rtw_sta_mgt.o.cmd core/.rtw_swcrypto.o.cmd core/.rtw_tdls.o.cmd core/.rtw_vht.o.cmd core/.rtw_wlan_util.o.cmd core/.rtw_wnm.o.cmd core/.rtw_xmit.o.cmd core/crypto/.aes-ccm.o.cmd core/crypto/.aes-ctr.o.cmd core/crypto/.aes-gcm.o.cmd core/crypto/.aes-internal-enc.o.cmd core/crypto/.aes-internal.o.cmd core/crypto/.aes-omac1.o.cmd core/crypto/.aes-siv.o.cmd core/crypto/.ccmp.o.cmd core/crypto/.gcmp.o.cmd core/crypto/.rtw_crypto_wrap.o.cmd core/crypto/.sha256-internal.o.cmd core/crypto/.sha256-prf.o.cmd core/crypto/.sha256.o.cmd core/crypto/aes-ccm.o core/crypto/aes-ctr.o core/crypto/aes-gcm.o core/crypto/aes-internal-enc.o core/crypto/aes-internal.o core/crypto/aes-omac1.o core/crypto/aes-siv.o core/crypto/ccmp.o core/crypto/gcmp.o core/crypto/rtw_crypto_wrap.o core/crypto/sha256-internal.o core/crypto/sha256-prf.o core/crypto/sha256.o core/efuse/.rtw_efuse.o.cmd core/efuse/rtw_efuse.o core/mesh/.rtw_mesh.o.cmd core/mesh/.rtw_mesh_hwmp.o.cmd core/mesh/.rtw_mesh_pathtbl.o.cmd core/mesh/rtw_mesh.o core/mesh/rtw_mesh_hwmp.o core/mesh/rtw_mesh_pathtbl.o core/monitor/.rtw_radiotap.o.cmd core/monitor/rtw_radiotap.o core/rtw_ap.o core/rtw_beamforming.o core/rtw_br_ext.o core/rtw_btcoex.o core/rtw_btcoex_wifionly.o core/rtw_chplan.o core/rtw_cmd.o core/rtw_debug.o core/rtw_ft.o core/rtw_ieee80211.o core/rtw_io.o core/rtw_ioctl_query.o core/rtw_ioctl_set.o core/rtw_iol.o core/rtw_mbo.o core/rtw_mi.o core/rtw_mlme.o core/rtw_mlme_ext.o core/rtw_odm.o core/rtw_p2p.o core/rtw_pwrctrl.o core/rtw_recv.o core/rtw_rf.o core/rtw_rm.o core/rtw_rm_fsm.o core/rtw_rm_util.o core/rtw_roch.o core/rtw_rson.o core/rtw_security.o core/rtw_sreset.o core/rtw_sta_mgt.o core/rtw_swcrypto.o core/rtw_tdls.o core/rtw_vht.o core/rtw_wlan_util.o core/rtw_wnm.o core/rtw_xmit.o core/wds/.rtw_wds.o.cmd core/wds/rtw_wds.o os_dep/.osdep_service.o.cmd os_dep/linux/.os_intfs.o.d os_dep/osdep_service.o nothing added to commit but untracked files present (use "git add" to track) ``` ### install-driver.sh ```text : --------------------------- : install-driver.sh v20241003 : x86_64 (kernel architecture) : x86_64 (architecture to send to gcc) : 12/12 (in-use/total processing units) : 32714260 (total system memory) : 6.13.1-arch1-1 (kernel version) : gcc (version of gcc used to compile the kernel) : gcc (GCC) 14.2.1 20250128 : dkms-3.1.5 : SecureBoot disabled : --------------------------- Checking for previously installed drivers... Finished checking for and uninstalling previously installed drivers. : --------------------------- Starting installation. Copying 8812au.conf to /etc/modprobe.d The dkms installation routines are in use. Copying source files to /usr/src/rtl8812au-5.13.6-23 Creating symlink /var/lib/dkms/rtl8812au/5.13.6-23/source -> /usr/src/rtl8812au-5.13.6-23 The driver was added to dkms successfully. : --------------------------- Sign command: /usr/lib/modules/6.13.1-arch1-1/build/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Cleaning build area... done. Building module(s).....(bad exit status: 2) Failed command: kernelver=6.13.1-arch1-1 ./dkms-make.sh Error! Bad return status for module build on kernel: 6.13.1-arch1-1 (x86_64) Consult /var/lib/dkms/rtl8812au/5.13.6-23/build/make.log for more information. An error occurred. dkms build error: 10 Please report this error. Please copy all screen output and paste it into the problem report. Run the following before reattempting installation. $ sudo ./remove-driver.sh ``` ### What happened? Hi! Since i couldn't connect to the internet after a recent update, i did what i usually do and: -Tried to remove the rtl8812au driver using the uninstall script -Uinstalled everything else in DKMS -Updated everything with `sudo pacman -Syu` -Reinstalled DKMS -Tried to install rtl8812au with the install script again But already when i was uninstalling i had issues. DKMS status said that the rtl8812au was "broken" and running the uninstall script i was told that it was missing the symbolic link. I then had to purge/remove rtl8812au.ko from `/lib/modules/$(uname -r)/kernel/drivers/net/wireless/realtek/rtl8xxxu` directly, and after running `sudo depmod -a` the driver seemed to be succesfully removed when i ran `DKMS status`. As you can see, running the install-driver.sh script says that the build failed. I then ran make clean and make directly to have a more detailed look. `make clean` gives me: ``` #make -C /lib/modules/6.13.1-arch1-1/build M=/home/buster/src/8812au-20210820 clean cd hal ; rm -fr */*/*/*.mod.c */*/*/*.mod */*/*/*.o */*/*/.*.cmd */*/*/*.ko cd hal ; rm -fr */*/*.mod.c */*/*.mod */*/*.o */*/.*.cmd */*/*.ko cd hal ; rm -fr */*.mod.c */*.mod */*.o */.*.cmd */*.ko cd hal ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko cd core ; rm -fr */*.mod.c */*.mod */*.o */.*.cmd */*.ko cd core ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko cd os_dep/linux ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko cd os_dep ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko cd platform ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko rm -fr Module.symvers ; rm -fr Module.markers ; rm -fr modules.order rm -fr *.mod.c *.mod *.o .*.cmd *.ko *~ rm -fr .tmp_versions rm -fr MOK.der MOK.priv ``` `make` gives me: ``` make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/6.13.1-arch1-1/build M=/home/buster/src/8812au-20210820 modules make[1]: Entering directory '/usr/lib/modules/6.13.1-arch1-1/build' make[2]: Entering directory '/home/buster/src/8812au-20210820' CC [M] core/rtw_cmd.o CC [M] core/rtw_security.o CC [M] core/rtw_debug.o CC [M] core/rtw_io.o CC [M] core/rtw_ioctl_query.o CC [M] core/rtw_ioctl_set.o CC [M] core/rtw_ieee80211.o CC [M] core/rtw_mlme.o CC [M] core/rtw_mlme_ext.o CC [M] core/rtw_mi.o CC [M] core/rtw_wlan_util.o CC [M] core/rtw_vht.o CC [M] core/rtw_pwrctrl.o CC [M] core/rtw_rf.o CC [M] core/rtw_chplan.o CC [M] core/monitor/rtw_radiotap.o CC [M] core/rtw_recv.o CC [M] core/rtw_sta_mgt.o CC [M] core/rtw_ap.o CC [M] core/wds/rtw_wds.o CC [M] core/mesh/rtw_mesh.o CC [M] core/mesh/rtw_mesh_pathtbl.o CC [M] core/mesh/rtw_mesh_hwmp.o CC [M] core/rtw_xmit.o CC [M] core/rtw_p2p.o CC [M] core/rtw_rson.o CC [M] core/rtw_tdls.o CC [M] core/rtw_br_ext.o CC [M] core/rtw_iol.o CC [M] core/rtw_sreset.o CC [M] core/rtw_btcoex_wifionly.o CC [M] core/rtw_btcoex.o CC [M] core/rtw_beamforming.o CC [M] core/rtw_odm.o CC [M] core/rtw_rm.o CC [M] core/rtw_rm_fsm.o CC [M] core/rtw_ft.o CC [M] core/rtw_wnm.o CC [M] core/rtw_mbo.o CC [M] core/rtw_rm_util.o CC [M] core/efuse/rtw_efuse.o CC [M] core/rtw_roch.o CC [M] core/crypto/aes-internal.o CC [M] core/crypto/aes-internal-enc.o CC [M] core/crypto/aes-gcm.o CC [M] core/crypto/aes-ccm.o CC [M] core/crypto/aes-omac1.o CC [M] core/crypto/ccmp.o CC [M] core/crypto/gcmp.o CC [M] core/crypto/aes-siv.o CC [M] core/crypto/aes-ctr.o CC [M] core/crypto/sha256-internal.o CC [M] core/crypto/sha256.o CC [M] core/crypto/sha256-prf.o CC [M] core/crypto/rtw_crypto_wrap.o CC [M] core/rtw_swcrypto.o CC [M] os_dep/osdep_service.o CC [M] os_dep/linux/os_intfs.o In file included from /usr/lib/modules/6.13.1-arch1-1/build/include/linux/module.h:22, from ././include/basic_types.h:76, from ././include/drv_types.h:26, from os_dep/linux/os_intfs.c:17: os_dep/linux/os_intfs.c:35:26: error: expected ‘,’ or ‘;’ before ‘VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver’ 35 | MODULE_IMPORT_NS(VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /usr/lib/modules/6.13.1-arch1-1/build/include/linux/moduleparam.h:26:61: note: in definition of macro ‘__MODULE_INFO’ 26 | = __MODULE_INFO_PREFIX __stringify(tag) "=" info | ^~~~ /usr/lib/modules/6.13.1-arch1-1/build/include/linux/module.h:299:33: note: in expansion of macro ‘MODULE_INFO’ 299 | #define MODULE_IMPORT_NS(ns) MODULE_INFO(import_ns, ns) | ^~~~~~~~~~~ os_dep/linux/os_intfs.c:35:9: note: in expansion of macro ‘MODULE_IMPORT_NS’ 35 | MODULE_IMPORT_NS(VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver); | ^~~~~~~~~~~~~~~~ make[4]: *** [/usr/lib/modules/6.13.1-arch1-1/build/scripts/Makefile.build:194: os_dep/linux/os_intfs.o] Error 1 make[3]: *** [/usr/lib/modules/6.13.1-arch1-1/build/Makefile:1989: .] Error 2 make[2]: *** [/usr/lib/modules/6.13.1-arch1-1/build/Makefile:251: __sub-make] Error 2 make[2]: Leaving directory '/home/buster/src/8812au-20210820' make[1]: *** [Makefile:251: __sub-make] Error 2 make[1]: Leaving directory '/usr/lib/modules/6.13.1-arch1-1/build' make: *** [Makefile:2516: modules] Error 2 ``` This seems like a bug no? But maybe i messed something up by trying to uninstall directly. I don't quite know where to go from here though. Kind regards, and thanks for the amazing work!
Author
Owner

@morrownr commented on GitHub (Feb 4, 2025):

Hi @BusterLundgaard

This seems like a bug no?

We can call it a bug. It is just the periodic updates to kernel APIs that require maintenance to this driver to continue to work. You are out on the bleeding edge I see.

I have merged a patch that should take care of the problem but I need you to test and report back.

To apply the changes:

$ git pull

$ sudo sh install-driver.sh

FYI: When you get to kernel 6.14, a new in-kernel driver will be there so your adapter should be plug and play. Hopefully your distro adds the firmware and turns on the compilation of the driver. If you have problems, let me know.

<!-- gh-comment-id:2634312966 --> @morrownr commented on GitHub (Feb 4, 2025): Hi @BusterLundgaard > This seems like a bug no? We can call it a bug. It is just the periodic updates to kernel APIs that require maintenance to this driver to continue to work. You are out on the bleeding edge I see. I have merged a patch that should take care of the problem but I need you to test and report back. To apply the changes: $ git pull $ sudo sh install-driver.sh FYI: When you get to kernel 6.14, a new in-kernel driver will be there so your adapter should be plug and play. Hopefully your distro adds the firmware and turns on the compilation of the driver. If you have problems, let me know.
Author
Owner

@BusterLundgaard commented on GitHub (Feb 4, 2025):

It works! Thanks so much!
Also, the plug and play sounds like a great thing to look forward to haha.

<!-- gh-comment-id:2634701539 --> @BusterLundgaard commented on GitHub (Feb 4, 2025): It works! Thanks so much! Also, the plug and play sounds like a great thing to look forward to haha.
Author
Owner

@morrownr commented on GitHub (Feb 4, 2025):

Thanks for the report.

Also, the plug and play sounds like a great thing to look forward to haha.

It is a very good thing. The new driver is much better than this one.

<!-- gh-comment-id:2634835972 --> @morrownr commented on GitHub (Feb 4, 2025): Thanks for the report. > Also, the plug and play sounds like a great thing to look forward to haha. It is a very good thing. The new driver is much better than this one.
Author
Owner

@BusterLundgaard commented on GitHub (Jun 13, 2025):

Thanks for the report.

Also, the plug and play sounds like a great thing to look forward to haha.

It is a very good thing. The new driver is much better than this one.

Hi. I am unfortunately having issues once again with compiling/building the driver after a new update. Before I make an issue though, I just wanna ask how one uses this new plug n play driver? I've updated everything on arch, but I still seem to need this unofficial one.

Plug n play means: "Just put in your wifi adapter and the drivers should already be there in the kernel, no?"

<!-- gh-comment-id:2969735397 --> @BusterLundgaard commented on GitHub (Jun 13, 2025): > Thanks for the report. > > > Also, the plug and play sounds like a great thing to look forward to haha. > > It is a very good thing. The new driver is much better than this one. Hi. I am unfortunately having issues once again with compiling/building the driver after a new update. Before I make an issue though, I just wanna ask how one uses this new plug n play driver? I've updated everything on arch, but I still seem to need this unofficial one. Plug n play means: "Just put in your wifi adapter and the drivers should already be there in the kernel, no?"
Author
Owner

@morrownr commented on GitHub (Jun 13, 2025):

Hi @BusterLundgaard

Plug n play means: "Just put in your wifi adapter and the drivers should already be there in the kernel, no?"

That is correct. However, the various distros do things differently and some are slow to get things in place even if the firmware and driver are available.

The first thing you should do is make this sure the driver in this repo is fully uninstalled:

$ sudo sh remove-driver.sh

Once that is complete and you have rebooted, check to see if the in-kernel driver is working.

If it is not working, we need to see if Arch has turned on the new driver in their kernel 6.13 and we need to see if the appropriate firmware file is in place.

Go ahead and remove this driver and see what you get.

<!-- gh-comment-id:2971480308 --> @morrownr commented on GitHub (Jun 13, 2025): Hi @BusterLundgaard > Plug n play means: "Just put in your wifi adapter and the drivers should already be there in the kernel, no?" That is correct. However, the various distros do things differently and some are slow to get things in place even if the firmware and driver are available. The first thing you should do is make this sure the driver in this repo is fully uninstalled: $ sudo sh remove-driver.sh Once that is complete and you have rebooted, check to see if the in-kernel driver is working. If it is not working, we need to see if Arch has turned on the new driver in their kernel 6.13 and we need to see if the appropriate firmware file is in place. Go ahead and remove this driver and see what you get.
Author
Owner

@BusterLundgaard commented on GitHub (Jun 14, 2025):

Hi. I removed the driver with the uninstall script, rebooted and did a full system update with Pacman. Unfortunately, it seems my wifi adapter isn't being recognized. Running

ip addr

with the adapter in gives me the same as running it without the adapter in.

Regarding this custom driver, i get the following build error:

> cat /var/lib/dkms/rtl8812au/5.13.6-23/build/make.log

DKMS (dkms-3.2.1) make.log for rtl8812au/5.13.6-23 for kernel 6.15.2-arch1-1 (x86_64)
Sat Jun 14 12:19:06 PM CEST 2025

Building module(s)
# command: kernelver=6.15.2-arch1-1 ./dkms-make.sh
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/6.15.2-arch1-1/build M=/var/lib/dkms/rtl8812au/5.13.6-23/build  modules
make[1]: Entering directory '/usr/lib/modules/6.15.2-arch1-1/build'
make[2]: Entering directory '/var/lib/dkms/rtl8812au/5.13.6-23/build'
  CC [M]  core/rtw_cmd.o
  CC [M]  core/rtw_security.o
  CC [M]  core/rtw_debug.o
  CC [M]  core/rtw_io.o
  CC [M]  core/rtw_ioctl_query.o
  CC [M]  core/rtw_ioctl_set.o
core/rtw_debug.c:17:10: fatal error: drv_types.h: No such file or directory
   17 | #include <drv_types.h>
      |          ^~~~~~~~~~~~~
compilation terminated.
core/rtw_security.c:17:10: fatal error: drv_types.h: No such file or directory
   17 | #include <drv_types.h>
      |          ^~~~~~~~~~~~~
compilation terminated.
core/rtw_cmd.c:17:10: fatal error: drv_types.h: No such file or directory
   17 | #include <drv_types.h>
      |          ^~~~~~~~~~~~~
compilation terminated.
  CC [M]  core/rtw_ieee80211.o
make[4]: *** [/usr/lib/modules/6.15.2-arch1-1/build/scripts/Makefile.build:203: core/rtw_debug.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[4]: *** [/usr/lib/modules/6.15.2-arch1-1/build/scripts/Makefile.build:203: core/rtw_security.o] Error 1
make[4]: *** [/usr/lib/modules/6.15.2-arch1-1/build/scripts/Makefile.build:203: core/rtw_cmd.o] Error 1
core/rtw_io.c:47:10: fatal error: drv_types.h: No such file or directory
   47 | #include <drv_types.h>
      |          ^~~~~~~~~~~~~
compilation terminated.
make[4]: *** [/usr/lib/modules/6.15.2-arch1-1/build/scripts/Makefile.build:203: core/rtw_io.o] Error 1
core/rtw_ioctl_query.c:17:10: fatal error: drv_types.h: No such file or directory
   17 | #include <drv_types.h>
      |          ^~~~~~~~~~~~~
compilation terminated.
make[4]: *** [/usr/lib/modules/6.15.2-arch1-1/build/scripts/Makefile.build:203: core/rtw_ioctl_query.o] Error 1
core/rtw_ioctl_set.c:17:10: fatal error: drv_types.h: No such file or directory
   17 | #include <drv_types.h>
      |          ^~~~~~~~~~~~~
compilation terminated.
make[4]: *** [/usr/lib/modules/6.15.2-arch1-1/build/scripts/Makefile.build:203: core/rtw_ioctl_set.o] Error 1
core/rtw_ieee80211.c:20:10: fatal error: drv_types.h: No such file or directory
   20 | #include <drv_types.h>
      |          ^~~~~~~~~~~~~
compilation terminated.
make[4]: *** [/usr/lib/modules/6.15.2-arch1-1/build/scripts/Makefile.build:203: core/rtw_ieee80211.o] Error 1
make[3]: *** [/usr/lib/modules/6.15.2-arch1-1/build/Makefile:2003: .] Error 2
make[2]: *** [/usr/lib/modules/6.15.2-arch1-1/build/Makefile:248: __sub-make] Error 2
make[2]: Leaving directory '/var/lib/dkms/rtl8812au/5.13.6-23/build'
make[1]: *** [Makefile:248: __sub-make] Error 2
make[1]: Leaving directory '/usr/lib/modules/6.15.2-arch1-1/build'
make: *** [Makefile:2516: modules] Error 2

# exit code: 2
# elapsed time: 00:00:01
----------------------------------------------------------------

Kind regards.

<!-- gh-comment-id:2972590183 --> @BusterLundgaard commented on GitHub (Jun 14, 2025): Hi. I removed the driver with the uninstall script, rebooted and did a full system update with Pacman. Unfortunately, it seems my wifi adapter isn't being recognized. Running `ip addr` with the adapter in gives me the same as running it without the adapter in. Regarding this custom driver, i get the following build error: ``` > cat /var/lib/dkms/rtl8812au/5.13.6-23/build/make.log DKMS (dkms-3.2.1) make.log for rtl8812au/5.13.6-23 for kernel 6.15.2-arch1-1 (x86_64) Sat Jun 14 12:19:06 PM CEST 2025 Building module(s) # command: kernelver=6.15.2-arch1-1 ./dkms-make.sh make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/6.15.2-arch1-1/build M=/var/lib/dkms/rtl8812au/5.13.6-23/build modules make[1]: Entering directory '/usr/lib/modules/6.15.2-arch1-1/build' make[2]: Entering directory '/var/lib/dkms/rtl8812au/5.13.6-23/build' CC [M] core/rtw_cmd.o CC [M] core/rtw_security.o CC [M] core/rtw_debug.o CC [M] core/rtw_io.o CC [M] core/rtw_ioctl_query.o CC [M] core/rtw_ioctl_set.o core/rtw_debug.c:17:10: fatal error: drv_types.h: No such file or directory 17 | #include <drv_types.h> | ^~~~~~~~~~~~~ compilation terminated. core/rtw_security.c:17:10: fatal error: drv_types.h: No such file or directory 17 | #include <drv_types.h> | ^~~~~~~~~~~~~ compilation terminated. core/rtw_cmd.c:17:10: fatal error: drv_types.h: No such file or directory 17 | #include <drv_types.h> | ^~~~~~~~~~~~~ compilation terminated. CC [M] core/rtw_ieee80211.o make[4]: *** [/usr/lib/modules/6.15.2-arch1-1/build/scripts/Makefile.build:203: core/rtw_debug.o] Error 1 make[4]: *** Waiting for unfinished jobs.... make[4]: *** [/usr/lib/modules/6.15.2-arch1-1/build/scripts/Makefile.build:203: core/rtw_security.o] Error 1 make[4]: *** [/usr/lib/modules/6.15.2-arch1-1/build/scripts/Makefile.build:203: core/rtw_cmd.o] Error 1 core/rtw_io.c:47:10: fatal error: drv_types.h: No such file or directory 47 | #include <drv_types.h> | ^~~~~~~~~~~~~ compilation terminated. make[4]: *** [/usr/lib/modules/6.15.2-arch1-1/build/scripts/Makefile.build:203: core/rtw_io.o] Error 1 core/rtw_ioctl_query.c:17:10: fatal error: drv_types.h: No such file or directory 17 | #include <drv_types.h> | ^~~~~~~~~~~~~ compilation terminated. make[4]: *** [/usr/lib/modules/6.15.2-arch1-1/build/scripts/Makefile.build:203: core/rtw_ioctl_query.o] Error 1 core/rtw_ioctl_set.c:17:10: fatal error: drv_types.h: No such file or directory 17 | #include <drv_types.h> | ^~~~~~~~~~~~~ compilation terminated. make[4]: *** [/usr/lib/modules/6.15.2-arch1-1/build/scripts/Makefile.build:203: core/rtw_ioctl_set.o] Error 1 core/rtw_ieee80211.c:20:10: fatal error: drv_types.h: No such file or directory 20 | #include <drv_types.h> | ^~~~~~~~~~~~~ compilation terminated. make[4]: *** [/usr/lib/modules/6.15.2-arch1-1/build/scripts/Makefile.build:203: core/rtw_ieee80211.o] Error 1 make[3]: *** [/usr/lib/modules/6.15.2-arch1-1/build/Makefile:2003: .] Error 2 make[2]: *** [/usr/lib/modules/6.15.2-arch1-1/build/Makefile:248: __sub-make] Error 2 make[2]: Leaving directory '/var/lib/dkms/rtl8812au/5.13.6-23/build' make[1]: *** [Makefile:248: __sub-make] Error 2 make[1]: Leaving directory '/usr/lib/modules/6.15.2-arch1-1/build' make: *** [Makefile:2516: modules] Error 2 # exit code: 2 # elapsed time: 00:00:01 ---------------------------------------------------------------- ``` Kind regards.
Author
Owner

@morrownr commented on GitHub (Jun 15, 2025):

I just tried to duplicate the error here and was unable to do so. This system has Ubuntu 25.04 with kernel 6.14.

Let's concentrate on the new driver please.

Please post the results of the following command:

$ sudo ls -l /lib/firmware/rtw88

<!-- gh-comment-id:2973493594 --> @morrownr commented on GitHub (Jun 15, 2025): I just tried to duplicate the error here and was unable to do so. This system has Ubuntu 25.04 with kernel 6.14. Let's concentrate on the new driver please. Please post the results of the following command: $ sudo ls -l /lib/firmware/rtw88
Author
Owner

@BusterLundgaard commented on GitHub (Jun 15, 2025):

> sudo ls -l /lib/firmware/rtw88
total 412
-rw-r--r-- 1 root root   610 May 22 20:06 README.zst
-rw-r--r-- 1 root root 13117 May 22 20:06 rtw8703b_fw.bin.zst
-rw-r--r-- 1 root root 14647 May 22 20:06 rtw8703b_wow_fw.bin.zst
-rw-r--r-- 1 root root 17918 May 22 20:06 rtw8723d_fw.bin.zst
-rw-r--r-- 1 root root 16756 May 22 20:06 rtw8812a_fw.bin.zst
-rw-r--r-- 1 root root 36290 May 22 20:06 rtw8814a_fw.bin.zst
-rw-r--r-- 1 root root 19570 May 22 20:06 rtw8821a_fw.bin.zst
-rw-r--r-- 1 root root 53954 May 22 20:06 rtw8821c_fw.bin.zst
-rw-r--r-- 1 root root 77712 May 22 20:06 rtw8822b_fw.bin.zst
-rw-r--r-- 1 root root 85925 May 22 20:06 rtw8822c_fw.bin.zst
-rw-r--r-- 1 root root 64058 May 22 20:06 rtw8822c_wow_fw.bin.zst
<!-- gh-comment-id:2973841669 --> @BusterLundgaard commented on GitHub (Jun 15, 2025): ``` > sudo ls -l /lib/firmware/rtw88 total 412 -rw-r--r-- 1 root root 610 May 22 20:06 README.zst -rw-r--r-- 1 root root 13117 May 22 20:06 rtw8703b_fw.bin.zst -rw-r--r-- 1 root root 14647 May 22 20:06 rtw8703b_wow_fw.bin.zst -rw-r--r-- 1 root root 17918 May 22 20:06 rtw8723d_fw.bin.zst -rw-r--r-- 1 root root 16756 May 22 20:06 rtw8812a_fw.bin.zst -rw-r--r-- 1 root root 36290 May 22 20:06 rtw8814a_fw.bin.zst -rw-r--r-- 1 root root 19570 May 22 20:06 rtw8821a_fw.bin.zst -rw-r--r-- 1 root root 53954 May 22 20:06 rtw8821c_fw.bin.zst -rw-r--r-- 1 root root 77712 May 22 20:06 rtw8822b_fw.bin.zst -rw-r--r-- 1 root root 85925 May 22 20:06 rtw8822c_fw.bin.zst -rw-r--r-- 1 root root 64058 May 22 20:06 rtw8822c_wow_fw.bin.zst ```
Author
Owner

@morrownr commented on GitHub (Jun 16, 2025):

@BusterLundgaard

-rw-r--r-- 1 root root 16756 May 22 20:06 rtw8812a_fw.bin.zst

That is the firmware file that is needed by the in-kernel driver. So we are good in that regard.

If the driver in this repo is not properly uninstalled, the in-kernel driver will be blacklisted. Try running the following in the directory on your system that contains the driver in this repo:

$ git pull
$ sudo sh install-driver.sh

If, after reboot, you do not see a wireless interface:

$ iw dev

...then, run

$ sudo sh remove-driver.sh

...and reboot.

With all of that said, in looking over the information you have reported above, it appears there is something wrong in the header files. I can't fix that. In fact, I have seen several reports from Arch users that just upgraded to kernel 6.13 that are reporting problems.

Another alternative is to compile and install the in-kernel driver:

https://github.com/lwfinger/rtw88

If it also blows up, I am no longer any help. I suspect Arch has released faulty header files and that is something Arch has to fix.

<!-- gh-comment-id:2974913510 --> @morrownr commented on GitHub (Jun 16, 2025): @BusterLundgaard > -rw-r--r-- 1 root root 16756 May 22 20:06 rtw8812a_fw.bin.zst That is the firmware file that is needed by the in-kernel driver. So we are good in that regard. If the driver in this repo is not properly uninstalled, the in-kernel driver will be blacklisted. Try running the following in the directory on your system that contains the driver in this repo: $ git pull $ sudo sh install-driver.sh If, after reboot, you do not see a wireless interface: $ iw dev ...then, run $ sudo sh remove-driver.sh ...and reboot. With all of that said, in looking over the information you have reported above, it appears there is something wrong in the header files. I can't fix that. In fact, I have seen several reports from Arch users that just upgraded to kernel 6.13 that are reporting problems. Another alternative is to compile and install the in-kernel driver: https://github.com/lwfinger/rtw88 If it also blows up, I am no longer any help. I suspect Arch has released faulty header files and that is something Arch has to fix.
Author
Owner

@BusterLundgaard commented on GitHub (Jun 16, 2025):

Unfortunately still no wireless interface after following the instructions, so ill try to create an issue on Arch Linux.

Thanks a lot for the help!

<!-- gh-comment-id:2975271266 --> @BusterLundgaard commented on GitHub (Jun 16, 2025): Unfortunately still no wireless interface after following the instructions, so ill try to create an issue on Arch Linux. Thanks a lot for the help!
Author
Owner

@dubhater commented on GitHub (Jun 16, 2025):

Unfortunately still no wireless interface

The reason can be found in dmesg. But please create a new issue here: https://github.com/lwfinger/rtw88/issues

<!-- gh-comment-id:2976775269 --> @dubhater commented on GitHub (Jun 16, 2025): > Unfortunately still no wireless interface The reason can be found in dmesg. But please create a new issue here: https://github.com/lwfinger/rtw88/issues
Sign in to join this conversation.
No labels
bug
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morrownr/8812au-20210820#45
No description provided.