wearylantern15

The two firmware symlinks for Wi-Fi look like a clean workaround, especially with the shared-antenna detail confirmed from both the ini and kernel log. I’d still treat the Bluetooth part as “usable but not solved”, mainly because of the duplicated BD address and broken BLE. If someone has the Seekwave NV format documented, generating a board-specific sv6160lite.nvbin would be the next useful step. Also good warning about not unloading the SDIO driver — that one can save people from a confusing dead-end during testing.

Maybe, but I would not count on it as a drop-in fix. The Radxa aic8800 tree is for that chip family, while the K2B v2.2 reports this SWT6621S setup, and in the working case above the missing bit was firmware naming, not just driver source. It is still worth testing if the module actually binds to the SDIO device and loads cleanly, but I would first check dmesg for the exact firmware names and chip IDs it asks for. If Radxa’s driver really builds on newer kernels, it may help with the “old 6.12 only” problem, but someone with v2.2 hardware will need to verify it. Classic SBC fun: same board name, surprise silicon lottery.