I don't understand this, because it seems from the `udevadm monitor` output that my adapter (c70[bc]) really was a hidraw device. However, the results speak for themselves and this change has fixed the problem for me, while maintaining a fairly tight KERNEL condition. I suspect that if other people's Logitech USB Bluetooth dongles are still not working with this patch, then they may want to make a similar change to the previous line in 70-hid2hci.rules, but I am not touching that for now, because it does not affect me.
I remember a while ago, there was only one Logitech rule, and it used the | (or) operator for the KERNEL condition, just like my fix does. Does anyone know why they were separated into different rules? Because, obviously, they were under-matching by doing so.
I have attached a proper diff patch for those who are interested.
I made the following change in /lib/udev/ rules.d/ 70-hid2hci. rules and now it works.
KERNEL=="hidraw*", ATTRS{idVendor} =="046d" , ATTRS{idProduct }=="c70[ 4abc]|c71[ 34bc]", \
changed to:
KERNEL= ="hiddev* |hidraw* ", ATTRS{idVendor} =="046d" , ATTRS{idProduct }=="c70[ 4abc]|c71[ 34bc]", \
I don't understand this, because it seems from the `udevadm monitor` output that my adapter (c70[bc]) really was a hidraw device. However, the results speak for themselves and this change has fixed the problem for me, while maintaining a fairly tight KERNEL condition. I suspect that if other people's Logitech USB Bluetooth dongles are still not working with this patch, then they may want to make a similar change to the previous line in 70-hid2hci.rules, but I am not touching that for now, because it does not affect me.
I remember a while ago, there was only one Logitech rule, and it used the | (or) operator for the KERNEL condition, just like my fix does. Does anyone know why they were separated into different rules? Because, obviously, they were under-matching by doing so.
I have attached a proper diff patch for those who are interested.