There is supposed to be a package that automatically handles building a (presumably patched) version of the kernel module for this wifi/bt chip, called `aic8800-usb-dkms`, but for some reason, a kernel upgrade doesn't auto-trigger it. During the last kernel upgrade, I was able to get it working by manually doing `sudo dpkg-reconfigure aic8800-usb-dkms`, but that also does not work since 26.5.1, as it gives Deleting module aic8800-usb-4.0+git20250410.b99ca8b6-3 completely from the DKMS tree. Loading new aic8800-usb-4.0+git20250410.b99ca8b6-3 DKMS files... Building for 6.18.2-current-qcs6490 Building initial module for 6.18.2-current-qcs6490 Error! Bad return status for module build on kernel: 6.18.2-current-qcs6490 (aarch64) Consult /var/lib/dkms/aic8800-usb/4.0+git20250410.b99ca8b6-3/build/make.log for more information. And that file basically says (a bunch is redacted for brevity): DKMS make.log for aic8800-usb-4.0+git20250410.b99ca8b6-3 for kernel 6.18.2-current-qcs6490 (aarch64) Sat Jun 20 06:36:14 PM PDT 2026 make: Entering directory '/usr/src/linux-headers-6.18.2-current-qcs6490' make[1]: Entering directory '/var/lib/dkms/aic8800-usb/4.0+git20250410.b99ca8b6-3/build/USB/driver_fw/drivers/aic8800' warning: the compiler differs from the one used to build the kernel The kernel was built by: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0 You are using: gcc (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0 ... gcc: error: unrecognized command-line option ‘-fmin-function-alignment=8’; did you mean ‘-flimit-function-alignment’? gcc: error: unrecognized command-line option ‘-fmin-function-alignment=8’; did you mean ‘-flimit-function-alignment’? make[4]: *** [/usr/src/linux-headers-6.18.2-current-qcs6490/scripts/Makefile.build:287: aic_load_fw/aic_txrxif.o] Error 1 ... Apparently, the kernel is now built with gcc 14 (which matches the default in Debian Trixie images but not Ubuntu Noble images which have gcc 13). Not sure how to resolve that inconsistency. 1. Install & replace gcc 13 with gcc 14 (just installing won't work as this dkms module build doesn't respect CC env vars); not sure if this will break other things in Ubuntu 24.04 2. Rebuild the kernel with gcc 13; same issue will re-occur on the next kernel upgrade 3. Or something else Just out of curiosity, did you have to mess around with gcc versions to get it to compile (or are you using Debian Trixie images)?

I have checked .... true.... my fix 7.1 was creted for 7.1-rc1 here we have got 7.1-rc4 so not working... Problably it needs to fix dirver aic8800 as still not supported plus compilation... usb2/usb3/ethernet are working?

just as a statistics/stability report: the DTB with the NPU works very well. Uptime of the device is already a week, it's running armbian and immich on it. While immich lags sometimes because the board can be weak for video processing, but in general it already processed ~20k images with OCR and face detection based on RKNN. I consider it pretty good results.

I'm struggling to get the Pi Camera 3/IMX708 detected by the Zero 2W. It's an IMX708 sensor, and that is correctly showing in dmesg, but the V4L2 devices (/dev/video0, /dev/video1) for the camera are not set up. All the normal encoder devices are fine. I'm using a custom build but it's essentially minimal (and no desktop) current with trixie and no extensions, following the standard command for building an image. The dmesg log reads as follows: [ 10.719672] imx708 10-001a: camera module ID 0x0302 [ 10.719876] imx708 10-001a: ctrl(id:0x9f0902,val:0x232aaf80) is not handled [ 10.722275] imx708 10-001a: ctrl(id:0x9e0902,val:0x2b20) is not handled But I don't think this is problematic, as stock Raspbian shows precisely the same log messages, and it does correctly set up the devices. I've added the overlay and turned off (or tried to) the camera auto detection, but the imx708 messages were being logged even before I added the overlay, so I am not sure it was needed. In any event, nothing changed. Any thoughts on ways to get this up and running?

never heard of that kernel before