WiFi adapter dead after latest update

I’ve seen an epidemic of posts with the same pattern, it seems like the last update was troublesome for many.

Well, my turn:

This is the error I get when trying to compile:

Building module(s).....(bad exit status: 2)
Failed command:
arch='x86_64' kernelver='6.13.1-arch1-1' ./driverctl make all

Error! Bad return status for module build on kernel: 6.13.1-arch1-1 (x86_64)
Consult /var/lib/dkms/rtl88x2bu/5.13.1/build/make.log for more information.

and this is the log:

DKMS (dkms-3.1.5) make.log for rtl88x2bu/5.13.1 for kernel 6.13.1-arch1-1 (x86_64)

Cleaning build area
# command: make clean
#make -C /lib/modules/6.13.1-arch1-1/build M=/var/lib/dkms/rtl88x2bu/5.13.1/build 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

# exit code: 0
# elapsed time: 00:00:00
Building module(s)
# command: arch='x86_64' kernelver='6.13.1-arch1-1' ./driverctl make all
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/6.13.1-arch1-1/build M=/var/lib/dkms/rtl88x2bu/5.13.1/build  modules
make[1]: Entering directory '/usr/lib/modules/6.13.1-arch1-1/build'
make[2]: Entering directory '/var/lib/dkms/rtl88x2bu/5.13.1/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
  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
  CC [M]  os_dep/linux/usb_intf.o
  CC [M]  os_dep/linux/usb_ops_linux.o
  CC [M]  os_dep/linux/ioctl_linux.o
  CC [M]  os_dep/linux/xmit_linux.o
  CC [M]  os_dep/linux/mlme_linux.o
  CC [M]  os_dep/linux/recv_linux.o
  CC [M]  os_dep/linux/ioctl_cfg80211.o
  CC [M]  os_dep/linux/rtw_cfgvendor.o
  CC [M]  os_dep/linux/wifi_regd.o
  CC [M]  os_dep/linux/rtw_android.o
  CC [M]  os_dep/linux/rtw_proc.o
  CC [M]  os_dep/linux/nlrtw.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);
      |         ^~~~~~~~~~~~~~~~
  CC [M]  os_dep/linux/rtw_rhashtable.o
make[4]: *** [/usr/lib/modules/6.13.1-arch1-1/build/scripts/Makefile.build:194: os_dep/linux/os_intfs.o] Error 1
make[4]: *** Waiting for unfinished jobs....
os_dep/linux/ioctl_cfg80211.c:10524:32: error: initialization of ‘int (*)(struct wiphy *, struct net_device *, struct cfg80211_chan_def *)’ from incompatible pointer type ‘int (*)(struct wiphy *, struct cfg80211_chan_def *)’ [-Wincompatible-pointer-types]
10524 |         .set_monitor_channel = cfg80211_rtw_set_monitor_channel,
      |                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
os_dep/linux/ioctl_cfg80211.c:10524:32: note: (near initialization for ‘rtw_cfg80211_ops.set_monitor_channel’)
make[4]: *** [/usr/lib/modules/6.13.1-arch1-1/build/scripts/Makefile.build:194: os_dep/linux/ioctl_cfg80211.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 '/var/lib/dkms/rtl88x2bu/5.13.1/build'
make[1]: *** [Makefile:251: __sub-make] Error 2
make[1]: Leaving directory '/usr/lib/modules/6.13.1-arch1-1/build'
make: *** [Makefile:2530: modules] Error 2

# exit code: 2
# elapsed time: 00:00:09

Any idea is welcome, thank you :slight_smile:

quick update for those experiencing the same issue: it seems like in Kernel 6.13.1 they “forgot” to add the rtl88x2bu module. Downgrading to any 6.12 version “fixes” that.

sudo pacman -U https://archive.archlinux.org/packages/l/linux/linux-6.12.9.arch1-1-x86_64.pkg.tar.zst
sudo pacman -U https://archive.archlinux.org/packages/l/linux-headers/linux-headers-6.12.9.arch1-1-x86_64.pkg.tar.zst.sig

then reboot, and you’re good to go.

Since I don’t want to be bothered by 6.13 anymore, unless they implement the rtl88x2bu module back again, I also flagged the kernel to prevent unwanted upgrades:

sudo sed -i '/#IgnorePkg/a IgnorePkg=linux linux-headers' /etc/pacman.conf

hth

Maybe you can simply install also linux-lts (with its headers) and use that until 6.13 gets a fix?

1 Like

that’s also an option, yes

https://aur.archlinux.org/packages/rtl88x2bu-dkms-git

If i strongly focus my :crystal_ball: this one is the AUR build?
The first thing to do in case using AUR builds is to check the sources. https://github.com/RinCat/RTL88x2BU-Linux-Driver
May be asking there about the issue too…

Archlinux is not supporting partly updates, and that’s what downgrading only the kernel packages will do. On the long or short, blacklisting the kernel to get updated will cause other issues. The best way is to use LTS kernel and wait for a fix (or help on getting the issue fixed at the source)

You are right, that is the best approach. I just needed a quick-fix though because I had to send huge amounts of data with a short deadline.

During the weekend I’ll switch to LTS.

I contacted the involved parties btw, and “rumours” say “ArchLinux is unsupported because Realtek can’t keep up with all the kernel releases”.

Well, thanks for the help :slight_smile:

Realtek… is a story on its own anyway…

1 Like