Here is a more comprehensive solution. A note: these steps might not solve all your problems, as they did not solve mine, but they are the steps so far that the support team have walked me through before the devs decided that they need to look at this closer.
For starters, let’s log the current behavior of the phone before we make edits:
- Make sure your phone is up to date. Either open the terminal and use
sudo apt upgradeandsudo apt update, or go into the store and check for updates there. - Confirm the kill switch is not set to disable the Bluetooth and wifi
- Restart the phone.
- Attempt to turn on the Bluetooth by going into its settings.
- Open a terminal and log the dmesg text. I just stored it in
~/Documentsusingsudo dmesg > dmseg_default_firmware.txt. This can be useful for when you contact support@puri.sm
After contacting the support team, they may ask you to do steps similar to the following:
- Get a more modern firmware from a repo. We have listed here on this forum to use Librem5 / redpine-firmware-nonfree · GitLab, but the support team pointed me to a fork using the command
wget https://source.puri.sm/angus.ainslie/firmware-rs9116-nonfree/-/raw/debian/master/Firmware/RS9116_NLINK_WLAN_BT_IMAGE.rps. It might be beneficial to try one if the other doesn’t work. - Create a firmware folder on your phone if it doesn’t exist already:
sudo mkdir /lib/firmware. - Move the newly downloaded firmware, using
sudo mv -t /lib/firmware RS9116_NLINK_WLAN_BT_IMAGE.rps - Reboot the phone.
- Attempt to turn on Bluetooth in the settings.
- If trouble occurs, open a terminal, and save the
dmesgfor he support team: for example, I didsudo dmesg > dmesg_new_firmware.txt.
Finally, some people had luck changing a setting in /etc/modprobe.d/librem5-devkit.conf. Look for all occurrences of dev_oper_mode. If they are set to 5, try changing to 13, and vice-versa. I’m not sure of the significance of these modes, so be sure to document this change for future debugging, if you make it. See the changes here: