I am running openSUSE 12.3 on a Toshiba satellite z930. I have a logitech m570 wireless mouse. When I boot into openSUSE the mouse wont work, if I unplug the receiver and plug it back in then the mouse works perfectly until the next reboot. It works fine on windows 8. I not sure were to start troubleshooting this. Any help would be appreciated.
Hi
Before it works, do you see any output from the following command;
lsmod|grep logitech
If not, does replugging the receiver create output?
Is this a unifying device?
Hello and welcome to the OpenSuse forum.
I’m just going to guess here that the issue is that the hid_logitech.ko or hid-logitech-dj.ko kernel module is not being loaded at reboot. When you re-plug the receiever, it loads the kernel module for you.
To verify: After reboot (when it is not working) do an
#lsmod | grep logitech
and see if there are any logitech modules loaded. Then replug the receiver and run that command again to see if the module is now loaded. (You can also run tail /var/log/messages after replugging to see what got loaded.)
To make have the module loaded automatically on reboot add it to /etc/sysconfig/kernel, variable MODULES_LOADED_ON_BOOT (you can use the sysconfig graphical editor system => kernel or via editing the file (as root) directly)
Unfortunately that was not the problem. The output was the same both before and after replugging the receiver.
The output was:
hid_logitech_dj 18605 0
Unplug it, then replug it and post the output to
# dmesg | tail -n 20
6859.154030] usb 3-2: USB disconnect, device number 3
6863.524032] usb 3-2: new full-speed USB device number 4 using xhci_hcd
6863.537984] usb 3-2: New USB device found, idVendor=046d, idProduct=c52b
6863.537995] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
6863.538001] usb 3-2: Product: USB Receiver
6863.538006] usb 3-2: Manufacturer: Logitech
6863.545470] logitech-djreceiver 0003:046D:C52B.000B: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-2/input2
6863.548204] input: Logitech Unifying Device. Wireless PID:1028 as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.2/0003:046D:C52B.000B/input/input16
6863.548347] logitech-djdevice 0003:046D:C52B.000C: input,hidraw1: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:1028] on usb-0000:00:14.0-2:1
6863.550257] input: Logitech Unifying Device. Wireless PID:400e as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.2/0003:046D:C52B.000B/input/input17
6863.550400] logitech-djdevice 0003:046D:C52B.000D: input,hidraw2: USB HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:400e] on usb-0000:00:14.0-2:2
On Fri 16 Aug 2013 03:36:02 AM CDT, Biozenunity wrote:
6863.524032] usb 3-2: new full-speed USB device number 4 using xhci_hcd
Hi
So when I plug my receiver in I get the same output with regard to the
mouse, I don’t have a keyboard connected. But I load the ohci_hcd, your
system is loading xhci_hcd which AFAIK is USB 3.0;
Here is mine;
[135849.069548] usb 3-3: new full-speed USB device number 3 using ohci_hcd
[135849.225516] usb 3-3: New USB device found, idVendor=046d, idProduct=c52b
[135849.225531] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[135849.225540] usb 3-3: Product: USB Receiver
[135849.225547] usb 3-3: Manufacturer: Logitech
[135849.250659] logitech-djreceiver 0003:046D:C52B.0007: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:12.0-3/input2
[135849.257387] input: Logitech Unifying Device. Wireless PID:400a as /devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0007/input/input13
[135849.257930] logitech-djdevice 0003:046D:C52B.0008: input,hidraw1: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:400a] on usb-0000:00:12.0-3:1
Is there a USB 2.0 port you can plug the receiver into or is the system all USB 3.0?
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.3 (x86_64) Kernel 3.7.10-1.16-desktop
up 1 day 13:47, 4 users, load average: 0.33, 0.70, 0.73
CPU AMD E2-1800@1.70GHz | GPU Radeon HD 7340
MalcomLewis is correct, xhci_hcd is USB3.0. If you can use a USB 2 port try that on boot. If they are all USB3, try adding xhci_hcd to /etc/sysconfig/kernel, variable MODULES_LOADED_ON_BOOT
No joy. The problem persists on the USB3 as well as both USB2 ports however xhci_hcd is loaded on all 3 of them. I was poking around the hardware information and the USB2 controllers are both using ehci_hcd driver.
USB3 Controller
18: PCI 14.0: 0c03 USB Controller
[Created at pci.319]
Unique ID: MZfG.+tSmq9tQNw9
SysFS ID: /devices/pci0000:00/0000:00:14.0
SysFS BusID: 0000:00:14.0
Hardware Class: usb controller
Model: "Intel USB Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x1e31
SubVendor: pci 0x1179 "Toshiba America Info Systems"
SubDevice: pci 0x0001
Revision: 0x04
Driver: "xhci_hcd"
Driver Modules: "xhci_hcd"
Memory Range: 0xe0620000-0xe062ffff (rw,non-prefetchable)
IRQ: 41 (10925 events)
Module Alias: "pci:v00008086d00001E31sv00001179sd00000001bc0Csc03i30"
Driver Info #0:
Driver Status: xhci_hcd is active
Driver Activation Cmd: "modprobe xhci_hcd"
Config Status: cfg=no, avail=yes, need=no, active=unknown
USB2 Controller
21: PCI 1a.0: 0c03 USB Controller (EHCI)
[Created at pci.319]
Unique ID: pwJ7.hDugmJn+Mi9
SysFS ID: /devices/pci0000:00/0000:00:1a.0
SysFS BusID: 0000:00:1a.0
Hardware Class: usb controller
Model: "Intel USB Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x1e2d
SubVendor: pci 0x1179 "Toshiba America Info Systems"
SubDevice: pci 0x0001
Revision: 0x04
Driver: "ehci_hcd"
Driver Modules: "ehci_hcd"
Memory Range: 0xe063a000-0xe063a3ff (rw,non-prefetchable)
IRQ: 16 (238 events)
Module Alias: "pci:v00008086d00001E2Dsv00001179sd00000001bc0Csc03i20"
Driver Info #0:
Driver Status: ehci-hcd is not active
Driver Activation Cmd: "modprobe ehci-hcd"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Hummm . . . weird.
Rather than unplug / re-plug it, does it work if you unload and then reload the kernel module (modprobe -r xhci_hcd and then modprobe xhci_hcd or the same with hid_logitech_dj )
I think there is a good chance that will work and if so you could add a boot script to do automatically. Kind of cheesy, yes - but at least it might be a work around.
Also see: https://bugzilla.kernel.org/show_bug.cgi?id=43631 looks like perhaps you are seeing this issue?
Unloading and reloading the xhci_hcd module worked. Thanks for all the help guys.
That is good news. You might want to automate this workaround with a udev rule and a simple script runs when the wireless mouse dongle is inserted eg create a custom rule called /etc/udev/rules.d/30-logitech.rules with something like
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="046d", ATTR{idProduct}=="c52b", RUN+="/usr/bin/yourscriptname"
The script
#!/bin/sh
exec /sbin/modprobe -r xhci_hcd > /dev/null 2>&1
exec /sbin/modprobe xhci_hcd > /dev/null 2>&1
Great! I’m glad we isolated it and you have a work around at least, and Deano’s udev tip looks great.
On Sun 18 Aug 2013 12:46:02 PM CDT, LewsTherinTelemon wrote:
Great! I’m glad we isolated it and you have a work around at least, and
Deano’s udev tip looks great.
Hi
If you want more info on the device I did package up solaar a while
back;
http://software.opensuse.org/package/solaar
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.3 (x86_64) Kernel 3.7.10-1.16-desktop
up 9:57, 3 users, load average: 0.09, 0.09, 0.20
CPU AMD E2-1800@1.70GHz | GPU Radeon HD 7340