Luiz, thanks for having a go.
what you say is correct:
from the recent package update that file was reinstalled as:-
KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \
RUN+="hid2hci --method=logitech-hid --devpath=%p"
And I have changed it to:
KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[3]", \
RUN+="hid2hci --method=logitech-hid --devpath=%p"
which works again.
This has been wrong for quite some time (many years) but was correct at some stage prior (distant past) but I believe it was put back in when the --method=logitech-hid switch was added (incorrectly). That switch does not work for this device.
As previously mentioned I have been on the Debian forums several times but it has been effectively ignored. So have been working around it ever since I installed bluez package for other things. The recent update gave me the impetus to give this another go more directly.
Alex
On Wednesday, July 3rd, 2024 at 03:17, Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx> wrote:
> Hi Alex,
>
> On Tue, Jul 2, 2024 at 9:25 AM lexicdark@xxxxxxxxx wrote:
>
> > Solution requested: Please remove the entries for the logitech MX5500 in /lib/udev/rules.d/97-hid2hci.rules again (and please don't put them back in later)
> > This issue now keeps coming back every time a bluez update is pushed. And it has been going on since I have had it and reported to the Debian forums several times (but that has been useless, at best). It had been removed from configs. about a decade ago then it regressed when someone put it back.
> > Any self respecting Logitech MX5500 user wouldn't install bluez unless they had to (for other devices).
> > If I edit out the c71[bc] entries for the 046d device and the keyboard and mouse work again. These devices never have (and likely never will) work with this forced mode switch. The devices only appear to work in the raw mode. hid2hci --method=logitech-hid only stops the device from working because the hardware doesn't actually support it (supplementary: likely a too early BT implementation, it has it's own bluetooth usb device which is to talk with the mouse and keyboard but it seems you can't use it with other devices, and the mouse and keyboard don't work with other BT dongles, at least as far as I have tried).
> >
> > lsusb
> > Bus 007 Device 004: ID 046d:c71c Logitech, Inc. Logitech BT Mini-Receiver
> > Bus 007 Device 003: ID 046d:c71b Logitech, Inc. Logitech BT Mini-Receiver
> > Bus 007 Device 005: ID 046d:c709 Logitech, Inc. BT Mini-Receiver (HCI mode)/lib/udev/rules.d/97-hid2hci.rules
> > first two are mouse and keyboard, c709 is the dongle.
>
>
> Are you talking about the following rules:
>
> # Logitech devices
> KERNEL=="hiddev*", ATTRS{idVendor}=="046d",
> ATTRS{idProduct}=="c70[345abce]|c71[34bc]", \
> RUN+="hid2hci --method=logitech-hid --devpath=%p"
>
> I don't know who came up with these rules but it definitely hasn't
> changed in a long long time:
>
> commit 7ca701a6120778fb65905f02305963b79ff6d8de
> Author: Marcel Holtmann marcel@xxxxxxxxxxxx
>
> Date: Mon Dec 10 22:56:05 2012 +0100
>
> build: Put hid2hci udev rules next to the source code
>
> > Thanks,
> > Alex
>
>
>
> --
> Luiz Augusto von Dentz
