Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working.
Piotr <zaxonxp45@gmail.com> writes:
> dmesg gave me this (relevant lines when BT mouse was connected)
>
> [ 4218.671838] hid-generic 0005:0A5C:0001.0004: unknown main item tag 0x0
> [ 4218.676386] input: Bluetooth 3.0 Mouse as
> /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/bluetooth/hci0/hci0:3/0005:0A5C:0001.0004/input/input21
> [ 4218.679232] hid-generic 0005:0A5C:0001.0004: input,hidraw1: BLUETOOTH
> HID v1.29 Mouse [Bluetooth 3.0 Mouse] on 00:15:83:0c:bf:eb
> [ 4245.882600] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0
> [ 4245.885751] input: Bluetooth 3.0 Mouse as
> /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/bluetooth/hci0/hci0:4/0005:0A5C:0001.0005/input/input22
> [ 4245.887779] hid-generic 0005:0A5C:0001.0005: input,hidraw1: BLUETOOTH
> HID v1.29 Mouse [Bluetooth 3.0 Mouse] on 00:15:83:0c:bf:eb
> [ 4276.111082] hid-generic 0005:0A5C:0001.0006: unknown main item tag 0x0
> [ 4276.115032] input: Bluetooth 3.0 Mouse as
> /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/bluetooth/hci0/hci0:5/0005:0A5C:0001.0006/input/input23
> [ 4276.118450] hid-generic 0005:0A5C:0001.0006: input,hidraw1:
> BLUETOOTH HID v1.29 Mouse [Bluetooth 3.0 Mouse] on 00:15:83:0c:bf:eb
>
> But I do not know what should I do with this.
It is basically an accident report stating that this
mouse won't work with that module.
You might search web archives and internet discussion
groups to see if there is a replacement driver for the mouse
which is a real shame since it used to work but that particular
module doesn't work which is valuable information but not, of
course, what you wanted to know.
If you do find out that another kernel module or driver
does exist, that is the time to use /etc/modules to load it first
since the automatic detection is getting your the wrong one.
I used to have an 8-port serial converter box with 8
RS-232 ports and a usb connector going to the computer. It
needed a proprietary driver that the company did provide to
Linux users for free but no kernel modules loaded at all when you
connected the device without the driver.
It worked fine until we had a gigantic electrical storm
one day and all 8 ports went deaf and mute forever even though it
appeared as though they were okay and just waiting to be
connected to something.
The replacement 8-port box loads kernel modules and works
without any proprietary drivers.
Can you get any other bluetooth device to pair and
actually work with the dongle such as a headset or keyboard?
There are a lot of moving parts here such as the usb
driver for the dongle and then there is the communication between
the bluetooth device and the dongle.
dmesg and syslog are very good tools in cases like this
but the messages you will read aren't always the answers to the
question of why this or that is happening. They certainly do
help you ask new questions and sometimes rule out rabbit holes
you don't need to waste your time going down which is a blessing
as the world of making the technology work for you is a regular
warren of rabbit holes and anything that narrows down the
solution is a force multiplier.
One guess is that the driver for the bluetooth dongle is
causing the grief because it sees events that it doesn't
understand from the mouse. It should understand every mouse move
and button press so they can be passed on to the appropriate
function calls related to mouse activity. The OS has mouse
function calls and the driver translates mouse movement data in
to steps that are either along the X or Y axese. It doesn't have
to do anything but feed those steps to the OS by making the
appropriate function calls for movement and clicks. It
apparently can't do that so you need a different driver.
It might also be that another bluetooth mouse speaks a
different language and the driver understands it and works
properly so I hope this gives you more food for thought.
I don't really know anything specific to your problem so
I am speaking in generalities as I have seen a number of usb
devices such as a usb apple modem that shows activity in syslog
when you plug it in to a usb port but due to a lack of a driver,
it does absolutely nothing under Linux but get slightly warm to
the touch. Plug it in to a Mac and you're in to the dialup
business.
Martin McCormick
Reply to: