Jovan 0 Posted December 8, 2023 Hello, When we put "intf:fiq_debugger=off" line to config.txt and removed WiFi card (as the device we're sending to our customers does not require WiFi/BT, TInkerBoard simply won't boot. It's stuck after the messages about cfg80211 loading certificates (as shown in the attached photo). Do you have maybe any solution or workaround for this issue? Best regards, Jovan Share this post Link to post Share on other sites
tooz 52 Posted December 12, 2023 hello @Jovan, wifi uses pcie interface instead of uart console, and cfg80211 is one of the build-in kernel modules so it's expected to see logs like [ 10.023354] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 10.026024] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 10.026366] cfg80211: failed to load regulatory.db what's the setup? is there anything modified apart from adding intf:fiq_debugger=off to the /config.txt? Share this post Link to post Share on other sites
Jovan 0 Posted December 12, 2023 Thanks for the response. These are exact steps for reproduction: 1) burn official 3.0.11 image (Tinker_Board_2-Debian-Bullseye-v3.0.11-20231024-release.img) 2) change intf:fiq_debugger to OFF 3) change intf:uart0 to ON 4) remove wifi/bt card that was shipped with the TinkerBoard 5) Reboot When I put back the WiFi/BT card in, then I can see the line: cfg80211: failed to load regulatory.db but without wireless card, it's stuck on boot just before that line (as shown on photo). Best regards Share this post Link to post Share on other sites
tooz 52 Posted December 13, 2023 hello @Jovan, we've made some changes for uboot, please download it and have a try: https://www.asuswebstorage.com/navigate/a/#/s/78E2E316F9754A788E254369757136FD4 to update uboot: 1. download and unzip the file (uboot.img) 2. use the following commands to replace uboot sudo dd if=uboot.img of=/dev/mmcblk1p1 status=progress && sync sudo reboot Share this post Link to post Share on other sites
Jovan 0 Posted December 13, 2023 Thanks for prompt reply. I'll check the fix and get back here with the result. Hopefully we will have this fix included in next official Debian11 image too. Share this post Link to post Share on other sites