Arch Linux

eImTea

Member

Registered: 2025-02-05

Posts: 3

Bluetooth LE Keyboard no longer working after kernel update

Hello user. First time forum user here. I did search for similar Posts.
When trying to upgrade from Arch 6.6.72-1-lts to 6.12.12-1-lts my ProtoArc XK03 LowEnergyDevice Keyboard stops working.
It took me a long time to get it to work in the past because it just wouldn't show up when scanning in bluetoothctl but then suddenly it did and I quickly registered it.
The keyboard always worked without a problem right after booting but one time it stopped working after an update which I solved by switching to the lts branch which isn't an option anymore.

The keyboard still gets displayed as connected in bluetoothctl but seems to repeadetly connect and instantly disconnect and at no point is input possible.
Using blueman I get the output that the power level of device cant be read with each disconnect so I tried enabling experimental mode in the /bluetooth/main.conf which didnt help.
I obviously tried restarting the bluetooth service and all the simple solutions that get recommended.

The fact that my keyboard still appears and is continuously displayed in bluetoothctl lets me think the problem is elsewhere. I have updated my system in the past without issue.

When I setup my keyboard the first time I remember that I might have created a config file specifically for my keyboard according to some tutorial. Two config files contradicting each other is the only problem I can think of as of rn.
I can not remember the location of this config file nor find the tutorial I have followed but I will update this post if I do in my attempts of troubleshooting this issue.
That would still not explain what changed to cause this issue now tho so if anyone knows I'd appreciate it. I am an Arch novice but I feel like this problem isn't really my fault so I put it here.
If it's really necessary I will try to forget and reconnect the keyboard but as I mentioned it took me an entire day of trying to get it to show up under bluetoothctl and I don't know why it suddenly appeared.
I'm currently on my 6.6 backup and it works fine. I did follow the arch bluetooth manual for this and set the agent for LE devices, all that remains untouched.
The keyboard has only ever been connected to this linux system and nowhere else.

This is the output of journalctl -b | grep blue incase it means anything to you. I apologize for any formatting or spelling errors as I had to use an image to text converter because Im currently working with the downgraded system.

bluetoothd[419]: Bluetooth daemon 5.79
bluetoothd[419]: Starting SDP server
bluetoothd[419]: src/plugin.c:init_plugin() System does not support ccp plugin
bluetoothd[419]: Bluetooth management interface 1.23 initialized
bluetoothd[419]: Battery Provider Manager created
bluetoothd[419]: profilessaudiosbap.c:bap_adapter_probe() BAP requires ISO Socket which is not enabled
bluetoothd[419]: bap: Operation mot supported (95)
bluetoothd[419]: srcsdevice.c:device_set_wake_support() Unable to set wake_support without RPA resolution
bluetoothd[419]: Adv Monitor Manager created with supported features:0x00000001, enabled features :0x00000001, max number of supported monitors:32, max number of supported patterns:16
bluetoothd[419]: profiles/input/hog-1ib.c:proto_mode_read_cb() Protocol Mode characteristic read failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profiles/input/hog-1ib.c:report_read_cb() Error reading Report value: Request attribute has encountered an unlikely error
bluetoothd[419]: profiles/input/hog-lib.c:report_reference_ch() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profiles/input/hog-lib.c:report_read_cbh() Error reading Report value: Request attribute has encountered an unlikely error
bluetoothd[419]: profiles/input/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profilessinput/hog-1ib.c:report_read_cb() Error reading Report value: Request attribute has encountered an unlikely error
bluetoothd[419]: profiles/input/hog-1ib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profiles/input/hog-1ib.c:info_read _cb() HID Information read failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profilessdeviceinfosdeviceinfo.c:read pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error
bluetoothd[419]: profiles/inputshog-1ib.c:proto_node_read_cb() Protocol Mode characteristic read failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profiles/input/hog-1ib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profilessinput/hog-lib.c:report_reference_ch() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profilessinput/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profiless/input/hog-lib.c:info_read_cb() HID Information read failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profilessdeviceinfosdeviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error
bluetoothd[419]: profiles/input/hog-lib.c:proto_node_read ch() Protocol Mode characteristic read failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profiles/inputshog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profiles/input/hog-1ib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profilesszinput/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profilesvinput/hog-lib.c:info_read_cb() HID Information read failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profilesszdeviceinfosdeviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error
bluetoothd[419]: Path / reserved for Adv Monitor app 1.12
bluetoothd[419]: profilesvinputshog-lib.c:proto_rode_read _cb() Protocol Mode characteristic read failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profilesvzinputs/hog-lib.c:report reference _cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profileszinput/hog-lib.cireport_ reference _cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profilesszinput/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profiles/zinput/hog-lib.c:info_read cb() HID Information read failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profilesszdeviceinfosdeviceinfo.c:read _pnpid_cb() Error reading PNP_ID value! Request attribute has encountered an unlikely error
bluetoothd[419]: profilesszinput/hog-lib.c:proto_node_read cb() Protocol Mode characteristic read failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profilesszinput/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profilesszinput/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profilesszinput/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profilesszinput/hog-lib.c:info_read_cb() HID Information read failed: Request attribute has encountered an unlikely error
bluetoothd[419]: profilessdeviceinfoszdeviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error
bluetoothd[419]: Adv Monitor app 31.12 disconnected fron D-Bus

And here the out of output of journalctl -b | grep blue on my working setup:

bluetoothd[399]: Bluetooth daemon 5.79
bluetoothd[399]: Starting SDP server
bluetoothd[399]: sresplugin.c:init_plugin() System does not support bap plugin
bluetoothd[399]: sresplugin.c:init_plugint) System does not support bass plugin
bluetoothd[399]: sresplugin.c:init_plugin() System does not support mcp plugin
bluetoothd[399]: srcsplugin.c:init_plugin() System does not support uvcp plugin
bluetoothd[399]: profilesrsaudiosmicp.cimicp_init() D-Bus experimental not enabled
bluetoothd[399]: srcoplugin.c:init_plugin() System does not support micp plugin
bluetoothd[399]: srceplugin.c:init_plugin() System does not support ccp plugin
bluetoothd[399]: srceplugin.c:init_plugin() System does not support csip plugin
bluetoothd[399]: srcsplugin.c:init_plugin() System does not support asha plugin
bluetoothd[399]: Bluetooth management interface 1.22 initialized
bluetoothdI399]: Battery Provider Manager created Sl
bluetoothd[399]: src/device.c:device set wake support() Unable to set wake_support without RPA resolution
bluetoothd[399]: src/device.c:device set wake support() Unable to set wake_support without RPA resolution

Any help is appreciated. I'm hoping that this has to do with any recent changes in the arch architecture and can be explained easily. Worst case it doesn't get fixed and I have to struggle to set up the keyboard over again. I'm using a mini pc with only 2 USB ports so a bluetooth keyboard is a must and this one is very nice.

Edit:
I did notice whilst upgrading some warnings of potentially missing files but I don't know why that might be. I assume that they are reffering to firmware I dont use on my system. I really didn't alter anything about my system because I'm mostly using it to work with Xorg and I'm just happy that it works the way it does. I'm really happy with my system besides this issue rn.
I use timeshift to backup my system and to revert it to its working stage. I do choose the option of reinstalling grub2 when prompted.
The keyboard works unitl I reboot after the update.

Update:
I have tried some more things and actually found out what the configs were that I was look for. I was actually following the standard Arch Keyboard Manual and created the files in /etc/btkbd.conf and /etc/systemd/system/btkbd.service as instructed and also did systemctl deamon-reload and enable and start btkbd. I realised that in those files I actually referred to a different MAC adress than is connected in bluetoothctl because my keyboard can connect up to three devices which you can alternate between. After correcting the MAC Adress in the config file and removing the unused address from bluetoothctl I tried updating the system again to see if this had caused the issue. I ended up finding out that the btkbd doesn't actually do anything so I deleted it and on my backup the keyboard continued to connect right after booting as it used to. So I have to assume that bluetoothctl handles all the connecting once a device is trusted.

All this leads me to believe that I can't have possibly done anything wrong to cause this and all I can do now is wait for a fix to be released that might never come or possibly try troubleshooting with wireshark but for this I would need some help.
I'd also like to point out that with the release gromit has provided I was no longer able to connect to the internet but that might have been intentional.
I really hope I didn't say anything unintelligent because I'm genuinely invested in my system and would feel quiet discouraged if I couldn't even setup my keyboard.
It's not impossible that I forgot to run some command I'm unaware of, so far I have focused on the bluetooth operations but maybe I'm doing something wrong on kernel level.

If I have both linux and linux-lts on my system, can they interfere? Or is it purely preference which one I use at launch.
Any help to keep me going would be appreciated.

Last edited by eImTea (2025-02-07 13:27:16)

gromit

Administrator

From: Germany

Registered: 2024-02-10

Posts: 1,523

Website

Re: Bluetooth LE Keyboard no longer working after kernel update

Did you reboot after the update? Please post the outputs of "pacman -Q linux-lts" and "uname -a"

Does the issue go away when you switch to the "linux" package  which is version 6.13.1?

Additionally please test the release candidate for the next mainline kernel:

sudo pacman -U https://pkgbuild.com//\~gromit/linux-bisection-kernels/linux-mainline-6.14rc1-1-x86_64.pkg.tar.zst

This way we don't start investigating a bug in detail which may already be fixed in a newer version ..

Last edited by gromit (2025-02-05 13:53:59)

eImTea

Member

Registered: 2025-02-05

Posts: 3

Re: Bluetooth LE Keyboard no longer working after kernel update

Hello, thank you for your reply.
First of all sorry if I mixed up the linux/arch terminology.
I added now that the keyboard stopped working after the reboot.
Here is what I did:

I reverted to the backup where the keyboard was working:
pacman -Q linux-lts >> linux-lts 6.6.72-11
pacman -Q linux >> linux 6.12.10.arch1-1
uname -a >> Linux (SystemName) 6.6.72-1-lts #1 SMP PREEMPT_DYNAMIC Fri, 17 Jan 2025 14:04:26 +0000 x86_64 GNU/Linux

I then removed the LTS kernel as root using pacman -R linux-lts linux-lts-headers (apparently I dont have headers installed or that doesn't exist, not sure)

Then I installed your release using sudo pacman -U https://pkgbuild.com//\~gromit/linux-bi … kg.tar.zst

Updated the system to use that using grub-mkconfig -o /boot/grub/grub.cfg

reboot

Now it isplays Arch Linux 6.14.0-rc1-1-mainline and I get:
pacman -Q linux-lts >> not found
pacman -Q linux >> 6.12.10.arch1-1
uname -a >> Linux (SystemName) 6.14.0-rc1-1-mainline #1 SMP PREEMPT_DYNAMIC Mon, 03 Feb 2025 12:52:24 +0000 x86_64 GNU/Linux

And the keyboard no longer works

I did this twice and accidentally forgot to grub-mkconfig the second time but ig the arch kernel I selected in the grub was just the one I just installed. It does seem like both linux-lts and linux are installed at the beginning tho, could this cause any issues or does it simply depend on which one you choose to use?
Also was I behind on updates or was that just because I was using the lts branch because I would always pacman -Syu to stay up to date assuming that is all I need to do.

Last edited by eImTea (2025-02-05 14:59:49)

eImTea

Member

Registered: 2025-02-05

Posts: 3

Re: Bluetooth LE Keyboard no longer working after kernel update

Did you reboot after the update? Please post the outputs of "pacman -Q linux-lts" and "uname -a"

Does the issue go away when you switch to the "linux" package  which is version 6.13.1?

Additionally please test the release candidate for the next mainline kernel:

sudo pacman -U https://pkgbuild.com//\~gromit/linux-bisection-kernels/linux-mainline-6.14rc1-1-x86_64.pkg.tar.zst

This way we don't start investigating a bug in detail which may already be fixed in a newer version ..

I think I messed up the reply so Im replying here so you get notified, unless you subscribed to the topic Im not sure how this is supposed to work. I couldn't find a forum post about thread etiquette. If you do take the time to come back to this issue please read the update I added to my post.

Last edited by eImTea (2025-02-07 13:31:43)