- This topic has 9 replies, 5 voices, and was last updated Sep 16-2:27 pm by olsztyn.
-
Posts
-
decode
Hello, I have two Bluetooth mice. Both have connected successfully, but the cursor does not respond to the mouse movements.
When connected via an external USB receiver, the mouse works and the touch-pad works too, but when connected wirelessly via Bluetooth, the cursor does not move.
What further settings do I need to adjust to get them working?Attachments:
olsztyn
Yes… Neither of my bluetooth mice work under antiX 26. Just as you described.
I reported this some time ago (a year ago) but it looks like it has not been resolved yet. At least I have not found a solution.Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parametersj0ta
Some laptops don’t have the circuit power to support both the wifi chip and the bluetooth chip connection at the same time ex: bluetooth mouse
Check if with the wifi off it works
🇳🇴🇸🇾🇸🇹🇪🇲🇩 🇺🇸🇪🇷
🇱🇮🇧🇷🇪🇧🇴🇴🇹 🇺🇸🇪🇷
🇦🇳🇹🇮🇽 🇺🇸🇪🇷
🇱🇮🇧🇷🇪🇼🇴🇱🇫 🇺🇸🇪🇷
Anti A.I userSome laptops don’t have the circuit power to support both the wifi chip and the bluetooth chip connection at the same time ex: bluetooth mouse
Not in my experience with my many laptops.
All my laptops that have bluetooth worked fine with bluetooth mice in antiX 23. Working WiFi as well,of course…- This reply was modified 1 week, 4 days ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersRobin
When connected via an external USB receiver, the mouse works and the touch-pad works too, but when connected wirelessly via Bluetooth, the cursor does not move.
I have run into similar bluetooth issues myself which I was unable to resolve until now (with a pair of BT-earphones). What I found out while researching on my issue was:
Please note, there is no single Bluetooth standard. There are many more recent devices, which can’t talk with older chips built into notebooks due to very limitied backward compatibility. And then, to be able to connect to most recent Bluetooth devices you have to install a recent 7.x kernel, since the changed hardware requirements resulted in changes of the kernel settings for the Bluetooth stack.My best guess is: disable the internal BT chip, and plug an external USB BT receiver, which precisely matches the BT protocol version your peripherals expect. And then install latest 7.x kernel, the latest BT Bluethooth tool set, and retry. That’s what I’m going to test myself with my earphones also, once I have a bit of time left for this.
Since you already have an external BT dongle, which works with your mouse on the installed kernel, I’d suggest using it that way. Never touch a running system…
Windows is like a submarine. Open a window and serious problems will start.
I have run into similar bluetooth issues myself which I was unable to resolve until now (with a pair of BT-earphones). What I found out while researching on my issue was:
Please note, there is no single Bluetooth standard. There are many more recent devices, which can’t talk with older chips built into notebooks due to very limitied backward compatibility. And then, to be able to connect to most recent Bluetooth devices you have to install a recent 7.x kernel, since the changed hardware requirements resulted in changes of the kernel settings for the Bluetooth stack.Yes, indeed. You are absolutely right on that.
However, to add some complexity in my observation:
– The same mice work fine on antiX 23 on the same hardware. So in my case there is no difference in bluetooth hardware, although there is in bluetooth software between Bookworm and Trixie apparently, in result the same tesst does not work on antiX 26. And not just one laptop but more than five, and three or four different mice, so it is consistent behavior.
– In my comparison while mice fail to move cursor, bluetooth audio seems working fine in my test cases.Since I am back to this mice issue, on which I gave up last year, I will try to do some more experimentation. I do not remember if I tested this behavior on MX, so perhaps results might shed some more light. Particularly a solution would be great for my three Macbook Pro laptops running antiX, between 2012 and 2015, since they have just two USB ports, so using a dongle further limits them to one USB port left…
Update:
Just for comparison I tested on my machine I am typing now, where a bluetooth mouse does not work on antiX 26, the same mouse works fine on MX 25 dated September 11, 2026.
Now this is a clue I was looking for… I may have to port some pieces from MX to antiX 26…
I just need to identify what pieces. Still strange such difference exists between MX and antiX in bluetooth stack, particularly I am comparing MX ahs to antiX ahs, so I thought there should be no difference in hardware support. On the other hand There is a difference in kernel level – on antiX it is 7.0 and on MX it is 7.1, so this might be something to look at…- This reply was modified 1 week, 4 days ago by olsztyn.
- This reply was modified 1 week, 4 days ago by olsztyn.
- This reply was modified 1 week, 4 days ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersThis bluetooth mice issue in antiX becomes interesting to resolve:
In MX ahs it works fine while in antiX it does not work using the same hardware, both laptop and mice. So what would be difference in bluetooth stack?
I have attached MX repository to antiX to help identify the difference and upgraded antiX 26 kernel to the same level – 7.1. I am comparing bluetooth components antiX vs. MX. Just to be clear, it is comparison of fully updated antiX 26 and MX version September 11 2026… Both running the same kernel, the only difference is init – my antiX is on dinit, while MX is systemd, but init should not be an issue here, I think…
Will update if I find the cause of this…Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersIn attempt to fix this issue in antiX:
– Replaced some pieces of bluetooth stack with components from MX. This incomplete replacement did not change behavior.
– Updated all components of bluetooth stack from antiX Testing. This was smooth and did not bring in libelogind0, of course, but dinit bluetoothd service failed to start.
– Replacement with Debian Unstable components brings in libelogind0, so not viable.Looks like it remains for me to wait for @anticapitalista when the updates-in-waiting for bluetooth stack are released. I am running out of options…
Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersSteve Doe
In attempt to fix this issue in antiX:
– Replaced some pieces of bluetooth stack with components from MX. This incomplete replacement did not change behavior.
– Updated all components of bluetooth stack from antiX Testing. This was smooth and did not bring in libelogind0, of course, but dinit bluetoothd service failed to start.
– Replacement with Debian Unstable components brings in libelogind0, so not viable.Looks like it remains for me to wait for @anticapitalista when the updates-in-waiting for bluetooth stack are released. I am running out of options…
I know someone who’s going to have a lot of work around here: a quick
sudo apt-get clone @anticapitalista @anticapitalista-2
and there you go! 🙂- This reply was modified 1 week, 3 days ago by Steve Doe.
- This reply was modified 1 week, 3 days ago by Steve Doe.
Two eggs are in the fridge. The first egg says: "Brrr...it's cold in here, isn't it ?" ...and the second egg goes: "AAAAAH ! A TALKING EGG !"
😮 antixforum.com/search-forumsI know someone who’s going to have a lot of work around here: a quick sudo apt-get clone @anticapitalista @anticapitalista-2
and there you go! 🙂I am not sure of this, I am just hoping the new versions waiting in Testing and Sid will be working as expected. I know @anticapitalista is busy with priorities and Bluetooth stack is not considered a priority, affecting small percentage of users.
I was able to get MX to just about size of antiX memory footprint so both are interchangeable and look the same in LXQT on Openbox, so on some my laptops I can run either of them.
However if this bluetooth stack gets fixed in antiX that would be a bonus…Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
- You must be logged in to reply to this topic.