lwfinger
commented
11 months ago I did nto see any kernel oops, just warnings. Your first one is at [ 209.504899] ------------[ cut here ]------------ [ 209.509563] WARNING: CPU: 1 PID: 3497 at ../backports-6.5/net/wireless/core.c:456 wiphy_new_nm+0x51c/0x570 [cfg80211]
I do not support backports, and I have no source to see what that warning is about. My guess would be that the call to wiphy_new_nm is not properly supported.
KSofen
Hi @lwfinger, thanks for your work.
I am trying to package this driver into OpenWRT in my repo. To use it, one has to add this to feeds.conf.default:
src-git rtl8852au_feed https://github.com/andrey-utkin/rtl8852au-feedHere's the existing OpenWRT forum discussion, which for now doesn't have much info: https://forum.openwrt.org/t/add-rtl8852au-driver-to-kernel-module-but-ignored-when-building/156135/10The driver builds and loads, but when it initializes the device, it causes a few warnings, apparently fails to register it, and a kernel oops happens. 2023-12-09_21:18:53.dmesg.txt
I wonder if the problem is because of definitions not quite working due to build system being used differently. On my laptop, I built it like
make KSRC=/usr/src/kernel/version/ modules, while in OpenWRT it's more complicated so that I even ended up hardcoding-DCONFIG_LITTLE_ENDIANfor now, which let me to build it. Facing the current situation with the warnings and a crash, I tried adding hardcode of-DCONFIG_RADIO_WORK -DCONFIG_CONCURRENT_MODEto no effect.I am writing here in hope that you may recognize the problem (and perhaps some other which will follow) and give advice.
Thanks in advance.