| View previous topic :: View next topic |
| Author |
Message |
Fran
Guru
Joined: 29 Feb 2004
Posts: 455
Location: Coruña (Spain)
|
 Posted: Thu Jan 05, 2012 8:17 pm Post subject: Logitech wireless mouse doesn't work w/ gentoo-sources-3.2.0 |
 |
|
Since I updated to 3.2.0 from 3.1.6, my Logitech Anywhere MX stopped working. I have selected the new logitech universal receiver module, but I get this when I connect the receiver:
| Code: | logitech-djreceiver 0003:046D:C52B.0003: claimed by neither input, hiddev nor hidraw
logitech-djreceiver 0003:046D:C52B.0003: logi_dj_probe:hid_hw_start returned error
|
The module hid_logitech_dj is loaded.
Anyone else with similar problems?
(edit) Solved, obvious solution is obvious. I had to enable /dev/hidraw.
_________________
~amd64 10.0 // linux-3.4 // gcc-4.7 // glibc-2.15 // xorg-server-1.12 // openbox-3.5 |
|
| Back to top |
|
 |
SigHunter
n00b
Joined: 24 Mar 2010
Posts: 25
|
| Posted: Tue Jan 10, 2012 9:54 am Post subject: |
|
|
| had the same problem, your solution fixed it, thanks |
|
| Back to top |
|
|
*zensiert*
n00b
Joined: 10 Oct 2004
Posts: 9
Location: Germany
|
| Posted: Fri Jan 27, 2012 11:59 am Post subject: |
|
|
Also had the same problem, worked for me as well. Thanks  |
|
| Back to top |
|
|
xtx
Tux's lil' helper
Joined: 27 Dec 2011
Posts: 99
|
| Posted: Fri Jan 27, 2012 4:18 pm Post subject: |
|
|
| sorry if i'm being dumb... but what do you mean you had to enable it? my logitech dinovo edge keyboard stopped working. in /dev/ i see hidraw0-hidraw5 but i don't understand how to enable any of them. |
|
| Back to top |
|
|
*zensiert*
n00b
Joined: 10 Oct 2004
Posts: 9
Location: Germany
|
| Posted: Fri Jan 27, 2012 4:22 pm Post subject: |
|
|
You have to enable it in your kernel configuration. The flag is called . You can find it in menuconfig under | Code: | | Device Drivers -> HID Devices -> Generic HID support -> /dev/hidraw raw HID device support |
|
|
| Back to top |
|
|
xtx
Tux's lil' helper
Joined: 27 Dec 2011
Posts: 99
|
| Posted: Fri Jan 27, 2012 4:33 pm Post subject: |
|
|
ah. that was already enabled for me. not sure what's going on but my keyboard stopped connecting to the dongle it came with. it connects at boot but it disconnects as soon as xorg starts.
weird thing is that i figured out i can connect it to a third party bluetooth dongle using bluez... which i guess is fine... just don't know why it stopped connecting to the dongle it was made for |
|
| Back to top |
|
|
xtx
Tux's lil' helper
Joined: 27 Dec 2011
Posts: 99
|
| Posted: Fri Jan 27, 2012 6:59 pm Post subject: |
|
|
using the third party bluetooth adapter doesn't quite cut it for me. in order to use bluez you need one of two things: a gui to use a mouse and click on the bluetooth icon to connect, or a keyboard to do it via command line.
since i do not have a keyboard at this point to login to my gui or to use the command line, i cannot connect it. meaning that every time i reboot my computer i would have to connect a wired keyboard to login before being able to connect my wireless keyboard.
this is obviously not acceptable and i would appreciate any and all advice |
|
| Back to top |
|
|
wrdaniel
n00b
Joined: 30 Dec 2006
Posts: 37
|
| Posted: Fri Jan 27, 2012 9:23 pm Post subject: |
|
|
For those using logitech unifying receivers, check for
-> Device Drivers -> HID Devices (HID_SUPPORT [=y]) -> Special HID drivers -> Logitech devices (HID_LOGITECH [=y]) |
|
| Back to top |
|
|
xtx
Tux's lil' helper
Joined: 27 Dec 2011
Posts: 99
|
| Posted: Fri Jan 27, 2012 9:54 pm Post subject: |
|
|
that was enabled as a module before, set it to yes now, no change.
i'm fairly sure that it is not a kernel issue for me. it randomly stopped working after an update. i'm assuming a config file is incorrect but i have no idea which one or how to fix it. |
|
| Back to top |
|
|
tomatopi
Tux's lil' helper
Joined: 18 Sep 2005
Posts: 127
Location: Ottawa
|
| Posted: Mon Jan 30, 2012 1:46 pm Post subject: |
|
|
| Same problems here. However, I downgraded bluez to 4.96 and udev to 164-r2 and everything works. Looks like a problem with udev/bluez and not the kernel. |
|
| Back to top |
|
|
FreakNigh
n00b
Joined: 20 Aug 2006
Posts: 24
|
| Posted: Tue Feb 07, 2012 5:56 pm Post subject: |
|
|
I have a fresh gentoo install with 3.2.0 and the logitech M570 mouse will sometimes work with an initial turn on of the mouse but then becomes unresponsive.
This is a dmesg | tail
| Quote: | [27455.885558] usbtest 7-1:1.2: usb_probe_interface
[27455.885560] usbtest 7-1:1.2: usb_probe_interface - got id
[27455.885565] usbhid 7-1:1.2: usb_probe_interface
[27455.885567] usbhid 7-1:1.2: usb_probe_interface - got id
[27455.891139] usbhid 7-1:1.2: looking for a minor, starting at 96
[27455.891218] logitech-djreceiver 0003:046D:C52B.0016: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.1-1/input2
[27455.892113] uhci_hcd 0000:00:1d.1: reserve dev 6 ep83-INT, period 2, phase 1, 36 us
[27455.893137] drivers/usb/core/inode.c: creating file '006'
[27455.894435] input: Logitech Unifying Device. Wireless PID:1028 as /devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1:1.2/0003:046D:C52B.0016/input/input14
[27455.894501] logitech-djdevice 0003:046D:C52B.0017: input,hidraw3: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:1028] on usb-0000:00:1d.1-1:1 |
|
|
| Back to top |
|
|
xtx
Tux's lil' helper
Joined: 27 Dec 2011
Posts: 99
|
| Posted: Thu Feb 09, 2012 5:36 pm Post subject: |
|
|
^same here. dinovo edge occasionally syncs before kernel loads but afterward it is unresponsive. it WILL work if i use a wired keyboard to login and then sync my dinovo edge to my rocketfish bt adapter.
why is this happening with logitech devices? maybe it's just me but that's kind of an absolute necessity to have working properly if the open source community wants to be taken seriously with average users. |
|
| Back to top |
|
|
platojones
Veteran
Joined: 23 Oct 2002
Posts: 1430
Location: Just over the horizon
|
| Posted: Thu Feb 09, 2012 5:39 pm Post subject: |
|
|
| tomatopi wrote: | | Same problems here. However, I downgraded bluez to 4.96 and udev to 164-r2 and everything works. Looks like a problem with udev/bluez and not the kernel. |
I have the MX5500 and for me, just downgrading bluez was enough. udev 171-r5 works fine. |
|
| Back to top |
|
|
xtx
Tux's lil' helper
Joined: 27 Dec 2011
Posts: 99
|
| Posted: Thu Feb 09, 2012 6:23 pm Post subject: |
|
|
| ^confirmed. downgrading bluez works, udev is fine as is. |
|
| Back to top |
|
|
Winz
n00b
Joined: 21 Aug 2009
Posts: 3
Location: France
|
| Posted: Sun Feb 26, 2012 1:04 pm Post subject: |
|
|
I have the MX5500 and the same problem too.
Downgrading bluez works for me too.
The problem is due to hid2hci (tools that turn the Logitech dongle from embedded mode to Bluetooth mode). On Bluetooth mode 'lsusb' have an additional entry : Bus 008 Device 004: ID 046d:c704 Logitech, Inc. (HCI mode)
hci2hid seems not work to revert to embedded mode. So my first test to activate hid mode on boot failed :
| Code: | vim /etc/udev/rules.d/20-logitech-hid2hci.rules
# Logitech devices
KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[34bc]", \
RUN+="hid2hci --mode=hid --method=logitech-hid --devpath=%p" |
Another workaround (which works) is to comment hid2hid udev rules (which are installed with bluez).
| Code: | vim /lib/udev/rules.d/97-bluetooth-hid2hci.rules
# Logitech devices
#KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[34bc]", \
# RUN+="hid2hci --method=logitech-hid --devpath=%p" |
And then reboot !
This solution is not good because this file will be overwritten on each bluez update. So if someone had better solution ... |
|
| Back to top |
|
|
|
Kernel & Hardware
