Open jmranger opened 1 year ago
I imagine CONFIG_MODULES=n is causing your problem, because you don't have any firmware files present in CONFIG_EXTRA_FIRMWARE. In module-less builds, the kernel refuses to load firmware blobs from /lib/firmware and friends, and will only load blobs explicitly listed in CONFIG_EXTRA_FIRMWARE. This means that your wifi, bluetooth, webcam, (and more?) things aren't going to work, and the kernel might be crashing because the ISP hasn't been properly initialized with firmware.
I imagine CONFIG_MODULES=n is causing your problem, because you don't have any firmware files present in CONFIG_EXTRA_FIRMWARE. In module-less builds, the kernel refuses to load firmware blobs from /lib/firmware and friends, and will only load blobs explicitly listed in CONFIG_EXTRA_FIRMWARE. This means that your wifi, bluetooth, webcam, (and more?) things aren't going to work, and the kernel might be crashing because the ISP hasn't been properly initialized with firmware.
Thanks for chiming in. The wifi adapter works perfectly, and as I wrote, I'm aware that I'm not providing the ISP files to the kernel. I'm not reporting that the webcam isn't working, only the "Invalid wait context" error.
Please see the attached log. Boot is successful nonetheless.
This is with a custom kernel config (attached), which most notably has CONFIG_MODULES=n kernel & dtbs: asahi-6.5-15 u-boot: asahi-v2023.07.02-3 mini stage 2: v1.4.2 rootfs and build toolchain from Debian Testing initrd only contain wireless files, the ISP calibrations haven't been extracted yet.
Please let me know if you need other info. boot.log kernelconfig.txt