Sometimes & only sometimes I have this issue. Bluetooth at boot will not be turned on. I then open Bluetooth Devices. Of course it is off but also it is empty. No devices show up either. Turning it on it turns on but that’s it, no devices.
I reboot. Bluetooth is off again. This time when I open Bluetooth Devices the devices are there. Turning bluetooth on it will then be OK.
Running journalctl --priority=warning..crit --no-pager --boot=-1 I can see this>
When I do boot & it is working as expected I get this from journalctl --priority=warning..crit --no-pager --boot=-1.
Sep 28 08:49:01 hipster-rig kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02 Sep 28 08:49:01 hipster-rig kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
Any ideas?
Should also mention that recently all my devices had to be repaired as they themselves stopped being picked up even though they were in Bluetooth Devices.
Well, updating the kernel certainly would have been my first suggestion after realising you were on 6.9 (as it’s EOL).
I asked about Immutable because I noticed a few days ago (in the respective thread) that you were testing it; and bouncing through Manjaro editions as if they were trampolines.
Ah. Yes I did. This thread was marked with a solution. What happened to that solution tick I do not know. If I knew myself how to unmark it I would have. I used all caps so people could easily see that it was a recurring problem that is not solved. No ‘yelling’ intended.
Well, you marked a question from me (above) as the solution, apparently because it prompted you to try switching to another kernel.
This was what I was about to suggest in any case, but at the time I hadn’t; so, my post (the one you marked as the solution) actually didn’t contain a solution.
I’m guessing someone saw that the marked solution actually wasn’t a solution, and unmarked it.
You can mark a post as the solution, or unmark it, by clicking the (tick) under the post in question.
That seems to be an old bug, it happened to me too with older kernels. The workaround for me was to use tlp-ui to remember the last state of Bluetooth.
That’s seems to have made it 50% better. Now ever now & then when I boot bluetooth is off but my devices are there & all I have to do is turn it on. Much better than what it was. I’m happy with it now as is.
edit: Had another look at tlpui & changed some of the setting again. Will see how that goes.
(tick) under the post in question.