Hi there,
I have a weird problem constellation with my Framework 16 Laptop:
Using Kernel 6.19.6 or 6.19.6-zen, my bluetooth doesnt work at all.
I already dug through all the troubleshooting steps on the arch wiki but nothing helped. The error I get is
$ bluetoothctl power on
No default controller available
Then I thought: “Maybe I should try the LTS kernel”
But with the LTS Kernel (6.18.18) my keyboard stops working once SDDM starts. I can navigate the boot menu (systemd boot) and enter the LUKS password just fine, but as soon as SDDM starts, I can’t even switch to a TTY. The keyboard is just off?!
And now I have no clue on how to bring back bluetooth functionality at all…
Any ideas and help really appreciated 
Well, if both previously worked (and no other changes have been made), one has to assume the devices don’t work on those specific kernels, right?
Since given those two choices you have to choose (as I read it) between one of the devices functioning or not, I would recommend you look for an older kernel in which both work (it did before 6.19.6, right?) and keep the functional kernel around till your devices both work again.
Of you can delve into kernel and try to find patches and compile your own, etc.
Sorry I can’t help directly, but it might help to share a few more details in case others are facing similar issues.
Since it’s a laptop, the keyboard is integral, correct? Does another keyboard alternative work (e.g., USB keyboard plugged in)?
Presumably there is no Bluetooth at all, not just with restrict to one particular device?
Any other model/unit specs you can share might help folks track things down. 
Yes, I think Bluetooth last worked on 6.19.4.
I’ll give 6.19.4 a try later today!
That’s a good idea!
Keyboard is integrated, reseating didnt help. (The laptop allows to reseat the keyboard)
Bluetooth doesnt work at all (cant turn it on)
I am running KDE Plasma 6.6.2 and sddm 0.21.0-6.
EDIT:
Somehow the keyboard just worked in SDDM with the LTS kernel. Bluetooth does indeed just work for the LTS kernel as well.
The only thing I changed between the working and non-working state was
removed laptop-mode-tools (1.74-1)
installed game-devices-udev (0.25-0.1)
Now I kinda want to know if one of these packages had anything to do with the problem. I’ll start by installing laptop-mode-tools again and report back.
Hah, yes, it’s (in a weird way) fun to test till it breaks…then you might be able to do a bug report to the package developers.
1 Like
Allright, the culprit was laptop-mode-tools (at least for the bluetooth problem).
I still have no clue why the keyboard didnt work with the LTS kernel, the only possibility is that game-devices-udev fixed it…
EDIT:
It wasnt game-devices-udev that fixed the keyboard. I dont know what else it could be, the only package changes today were the following
upgraded ell (0.82-1 -> 0.83-1)
upgraded foomatic-db (3:20251122-1 -> 3:20260209-1)
upgraded foomatic-db-nonfree (3:20251122-1 -> 3:20260209-1)
upgraded foomatic-db-nonfree-ppds (3:20251122-1 -> 3:20260209-1)
upgraded foomatic-db-ppds (3:20251122-1 -> 3:20260209-1)
upgraded iwd (3.11-2 -> 3.12-1)
upgraded lib32-libldap (2.6.12-1 -> 2.6.13-1)
upgraded systemd-libs (259.4-1 -> 259.5-1)
upgraded lib32-systemd (259.4-1 -> 259.5-1)
upgraded libphonenumber (1:9.0.25-1 -> 1:9.0.26-1)
upgraded systemd (259.4-1 -> 259.5-1)
upgraded linux-lts (6.18.17-1 -> 6.18.18-1)
upgraded nfsidmap (2.8.6-2 -> 2.8.7-1)
upgraded nfs-utils (2.8.6-2 -> 2.8.7-1)
upgraded obs-studio (32.0.4-1 -> 32.1.0-1)
upgraded systemd-resolvconf (259.4-1 -> 259.5-1)
upgraded systemd-sysvcompat (259.4-1 -> 259.5-1)
My only idea would be that the keyboard didnt work on 6.18.17, but that makes no sense, as I updated it before checking ?!
EDIT: Ok, keyboard worked on 6.18.17, so it has to be something else.
Maybe I’ll roll back to a snapshot from before today and check, but as it works RN, I dont care that much.
1 Like