Q1: When connecting to WiFi, a pop‑up says "An application wants access to the keyring 'Default keyring', but it is locked". How to handle the password prompt?¶
The first WiFi connection creates a keyring. Setting the password to empty avoids this. If the issue already appears, delete the keyring files: rm -rf ~/.local/share/keyrings.
Ubuntu Desktop uses the Keyring to manage WiFi passwords. When the keyring is created for the first time, a pop‑up asks you to set a keyring password. This keyring password is different from the WiFi password, and you will be prompted for it every time you connect to WiFi.
Run rm -rf ~/.local/share/keyrings to delete all keyring files → reconnect to WiFi → when the keyring setup pop‑up appears, leave the keyring password blank → click "Continue". The password prompt will not appear again.
Q2: Where are the WiFi / Bluetooth driver loading scripts located?¶
wifibt-init.sh is responsible for initialising the WiFi/Bluetooth module at system boot (loading firmware, setting the BT address, starting RFKILL, etc.). wifibt-util.sh provides command‑line utility functions, such as diagnostic tools like bt_pcba_test and wifi_pcba_test.
The WiFi/BT firmware in the SDK is stored in the external/rkwifibt/firmware/ directory, with corresponding firmware binaries for different modules (AP6255 / AP6275 / AIC8800, etc.). A copy is also placed in /lib/firmware/ on the Linux system.
Q3: Bluetooth fails to start with a "tx timeout" error?¶
Run /usr/bin/bt_pcba_test. This issue may occur when Bluetooth initialises before the graphical interface is ready.
The Bluetooth module communicates with the main SoC via UART. If the ttyS device driver loads later than Bluetooth initialisation, the UART may not be ready when Bluetooth starts, causing a handshake timeout error.
Q4: The WiFi module logs too much information. How can I reduce it?¶
Run dmesg -n 1 to lower the kernel log level and reduce the frequent logging from the WiFi module.
dmesg -n 1 sets the console log level to 1 (showing only kernel panics). The level range is 0–7; lower values mean fewer logs. This change is temporary and resets after reboot.
To make it permanent, add kernel.printk = 1 4 1 7 to /etc/sysctl.conf (the first value controls the console log level; setting it to 1 shows only fatal errors). Alternatively, edit the logging configuration in /etc/systemd/system/systemd-logind.service.d/.
Q5: WiFi disconnects frequently or the signal is weak?¶
Check that the antenna is securely connected and not touching the board's metal areas. Use iwconfig wlan0 to check signal quality (a Link Quality > 70% is good). Check for channel interference; switching to the 5 GHz band (if your router supports it) can reduce interference. The antenna connectors on the board are labelled MAIN and AUX — ensure the antenna is connected to the MAIN port.
The WiFi module's antenna connector on the board is typically labelled ANT. It is best to route the antenna outside the enclosure, away from metal panels and large copper‑pour areas. Do not knot or excessively bend the antenna cable.
Compare the WiFi signal strength at the same location using a mobile phone. If the phone has a good signal but the board does not, the board's antenna or WiFi module hardware may be faulty. Try reconnecting the antenna connector.