[Bug 1182259] New: Logitech G602 mouse ID 046d:c537 not working after upgrade from Leap 15.1
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 Bug ID: 1182259 Summary: Logitech G602 mouse ID 046d:c537 not working after upgrade from Leap 15.1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: rolandjanssen@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- My Logitech G602 mouse is not working anymore after updating from Leap 15.1 to 15.2. The usb device ID is 046d:c537 It was working on openSuse Leap 15.1 without issues or configuring and I am still using the same usb port. But stopped working after I upgraded my laptop to openSuse 15.2. I tried other usb ports, als via an usb-c dock, but no luck. I verified the mouse is still working on another laptop. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rolandjanssen@gmail.com, | |tiwai@suse.com Flags| |needinfo?(rolandjanssen@gma | |il.com) --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- Could you give hwinfo output and the output of dmesg? Also do you still have Leap 15.1 kernel on the system? You can likely install the older kernel on the existing Leap 15.2 system, e.g. zypper in --oldpackage --force option. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c2 --- Comment #2 from Roland Janssen <rolandjanssen@gmail.com> --- roland@linux-ihhy:~> dmesg | grep logitech [ 8.582983] logitech-djreceiver 0003:046D:C537.0002: hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-2/input0 [ 8.902923] logitech-djreceiver 0003:046D:C537.0003: hiddev96,hidraw2: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-2/input1 [ 8.963185] logitech-djreceiver 0003:046D:C537.0003: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 9.014923] logitech-djreceiver 0003:046D:C52F.0008: hidraw7: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-1.2/input0 [ 9.110964] logitech-djreceiver 0003:046D:C52F.0009: hiddev100,hidraw8: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-1.2/input1 [ 9.171241] logitech-djreceiver 0003:046D:C52F.0009: device of type eQUAD step 4 DJ (0x04) connected on slot 1 [ 9.333467] logitech-hidpp-device 0003:046D:4008.000A: input,hidraw9: USB HID v1.11 Mouse [Logitech M185] on usb-0000:00:14.0-1.2/input1:1 [ 28.423435] logitech-hidpp-device 0003:046D:4008.000A: HID++ 2.0 device connected. [ 6617.257532] logitech-djreceiver 0003:046D:C537.000B: hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-2/input0 [ 6617.318592] logitech-djreceiver 0003:046D:C537.000C: hiddev96,hidraw2: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-2/input1 [ 6617.376219] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6617.843227] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6617.880217] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6618.383220] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6618.886223] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6619.389224] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6619.891227] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6620.394232] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6620.537225] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6620.752234] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6620.897230] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6621.119229] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6621.231228] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6621.400231] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6621.902215] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6622.405234] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6622.908235] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6623.410237] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6623.913248] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6624.759241] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6627.855253] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6628.181255] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6628.373261] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6628.374257] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6628.740254] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6628.876254] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6628.923253] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6629.106246] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6629.314259] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6629.379255] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6629.386254] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6629.617270] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6629.825259] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6629.882263] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6630.001258] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6630.384260] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6630.887262] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6630.918260] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6630.950260] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6630.958268] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6631.110268] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6631.150266] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6631.158260] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6631.245266] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6631.285261] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6631.325263] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6631.389267] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6631.390267] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6631.413261] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6631.453262] logitech-djreceiver 0003:046D:C537.000C: Unexpected input report number 128 [ 6632.116266] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6650.599328] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 [ 6651.101330] logitech-djreceiver 0003:046D:C537.000C: unusable device of type eQUAD step 4 Gaming (0x07) connected on slot 1 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c3 --- Comment #3 from Roland Janssen <rolandjanssen@gmail.com> --- hwinfo (this specific device) 51: USB 00.1: 0000 Unclassified device [Created at usb.122] Unique ID: 3X50.xTgLyecYco7 Parent ID: k4bc.2DFUsyrieMD SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1 SysFS BusID: 1-2:1.1 Hardware Class: unknown Model: "Logitech Cordless Mouse Receiver" Hotplug: USB Vendor: usb 0x046d "Logitech, Inc." Device: usb 0xc537 "Cordless Mouse Receiver" Revision: "34.00" Driver: "usbhid" Driver Modules: "usbhid" Speed: 12 Mbps Module Alias: "usb:v046DpC537d3400dc00dsc00dp00ic03isc00ip00in01" Driver Info #0: Driver Status: usbhid is active Driver Activation Cmd: "modprobe usbhid" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #53 (Hub) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c4 --- Comment #4 from Roland Janssen <rolandjanssen@gmail.com> --- I missed one in the hwinfo, I found this usb 0xc537 device twice in hwinfo 45: USB 00.0: 10503 USB Mouse [Created at usb.122] Unique ID: cLrx.71gbFDyxFH2 Parent ID: k4bc.2DFUsyrieMD SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0 SysFS BusID: 1-2:1.0 Hardware Class: mouse Model: "Logitech Cordless Mouse Receiver" Hotplug: USB Vendor: usb 0x046d "Logitech, Inc." Device: usb 0xc537 "Cordless Mouse Receiver" Revision: "34.00" Compatible to: int 0x0200 0x0001 "Generic USB Mouse" Driver: "usbhid" Driver Modules: "usbhid" Speed: 12 Mbps Module Alias: "usb:v046DpC537d3400dc00dsc00dp00ic03isc01ip02in00" Driver Info #0: XFree86 Protocol: explorerps/2 GPM Protocol: exps2 Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #53 (Hub) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c5 --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- Could you give the full outputs of hwinfo and dmesg, not the snippet? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c6 --- Comment #6 from Takashi Iwai <tiwai@suse.com> --- Also, could you try the previous kernel, 5.3.18-lp152.60.1? This could be an issue of the recent backport of the upstream fix that caused a regression. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c7 --- Comment #7 from Roland Janssen <rolandjanssen@gmail.com> --- Created attachment 846136 --> http://bugzilla.opensuse.org/attachment.cgi?id=846136&action=edit hwinfo full hwinfo as requested -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c8 --- Comment #8 from Roland Janssen <rolandjanssen@gmail.com> --- Created attachment 846137 --> http://bugzilla.opensuse.org/attachment.cgi?id=846137&action=edit dmesg full dmesg as requested -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c9 --- Comment #9 from Roland Janssen <rolandjanssen@gmail.com> --- I booted the system with Grub from the Leap 15.1 kernel, a much older one, 4.12.14-lp151.28.91 and the mouse was working as it should be. :-) Now i have to try with the kernel version you suggested. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c10 --- Comment #10 from Roland Janssen <rolandjanssen@gmail.com> --- The mouse is working correctly with the 5.3.18-lp152.60 kernel ! Thanks! You made a friend today :-) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c11 --- Comment #11 from Takashi Iwai <tiwai@suse.com> --- Thanks for quick testing! Then it's indeed a regression in the recent backport. I'm going to revert it for the next update. Meanwhile, you can still use the latest release kernel just by copying the hid-logitech-dj.ko file. That is, # mkdir /lib/modules/5.3.18-lp152.63-default/updates # cp /lib/modules/5.3.18-lp152.60-default/kernel/drivers/hid/hid-logitech-dj.ko /lib/modules/5.3.18-lp152.63-default/updates # depmod 5.3.18-lp152.63-default # mkinitrd -k vmlinuz-5.3.18-lp152.63-default -i initrd-5.3.18-lp152.63-default Then reboot to 5.3.18-lp152.63 and retest. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c12 --- Comment #12 from Roland Janssen <rolandjanssen@gmail.com> --- Thanks I followed your inststructions and the G602 mouse is working correctly with my laptop running at the 5.3.18-lp152.63 kernel with the previous hid-logitech-dj.ko. Do i need to change the status of this ticket, or will you do ? because for me it's resolved. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c13 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(rolandjanssen@gma | |il.com) | --- Comment #13 from Takashi Iwai <tiwai@suse.com> --- Thanks for confirmation. I pushed the fix to our git branch, so that it'll be included in the next update. So let's close this bug now. Happy to hear that the issue got fixed quickly, too :) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c16 --- Comment #16 from Roland Janssen <rolandjanssen@gmail.com> --- I tried to install your kernel, but after reboot an for me unknown message popped up about UEFI Shim signature. when I proceed and selected the specified kernel, it was giving an error, "Bad shim signature" after I booted the default kernel, and rebooted again, your kernel version disappeared from Grub... So I guess something else was going wrong here. But something else happened in the meantime, I already updated my laptop, and there were some days the mouse stopped working again, at those moments I just rebooted and it was working again, but I will harvest the 2 logs next time when the mouse stopped working. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c17 --- Comment #17 from Takashi Iwai <tiwai@suse.com> --- It must be because of Secure Boot. The kernel is not signed with an official key, hence Secure Boot would block booting. Please try to disable Secure Boot on your BIOS setup at first. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c18 Jonathan Carroll <iamjtestdev@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iamjtestdev@gmail.com --- Comment #18 from Jonathan Carroll <iamjtestdev@gmail.com> --- (In reply to Takashi Iwai from comment #15)
Now the upstream took an additional fix for the buggy change, and it's worth to try for Leap 15.2, too.
I'm building a new test kernel in the same OBS project home:tiwai:bsc1182259. It'll be kernel-default-5.3.18-lp152.*.g35527d7*.rpm. Please give it a try later whether this kernel works. Once when confirmed, I'll merge those to Leap 15.2 branch. Thanks!
Hello. I'm a Leap 15.2 user and the mouse stopped working entirely for kernel 5.3.18-lp152.63-preempt. I ran your commands, and grabbed the old driver, and everything is back to normal. Is there anything you might need that can help? I believe hwinfo was saying the receiver was pointing to an address that didn't exist. I'm a newbie, so just let me know if you need the full snippet of hwinfo. I think I still have a rollback with the broken driver. But seriously thank you so much. These commands worked perfectly. I'm still not the best navigating without a mouse lol. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182259 http://bugzilla.opensuse.org/show_bug.cgi?id=1182259#c19 --- Comment #19 from Takashi Iwai <tiwai@suse.com> --- It'd be great if you can test my test kernel available at: http://download.opensuse.org/repositories/home:/tiwai:/bsc1182259/standard/ It has only kernel-default, but you can install both kernel-preempt and kernel-default at the same time without problems. Note that it's signed with an unofficial key, so Secure Boot won't work; disable Secure Boot on BIOS beforehand if it's been enabled. The kernel above contains the additional upstream fix instead of reverting the patch that introduced a bug. I'm reluctant to merge those fixes to Leap at this time unless it's tested on the actual hardware... -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com