Logitech G602 stopped working after Kernel 5.10.11 update #1124
Assignees
Labels
Comments
|
Uh, I had tried here and it worked. Can you start |
|
Thank you for the reply |
|
|
|
|
Hello Filipe |
|
What I don't understand, My mouse was working fine.I wasn't using piper to bind the keys, instead I was using the default logitech application on virtual machine running windows 10. |
|
Sorry for the delay. The kernel is receiving the events, it just isn't redirecting them to userspace. It broke with this patch, I wish I seem to not have tested as good enough as I thought. |
|
Thank you for the replay Filipe |
|
Okay, I sent a patch to the mailing lists that should fix this. Sorry for the trouble. Hopefully, we will be able to get it out on the next release 🤞 |
|
Thank you Filipe |
fengguang
pushed a commit
to 0day-ci/linux
that referenced
this issue
Feb 1, 2021
In e400071 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Signed-off-by: Filipe Laíns <lains@riseup.net>
fengguang
pushed a commit
to 0day-ci/linux
that referenced
this issue
Feb 5, 2021
In e400071 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net>
FFY00
added a commit
to FFY00/linux
that referenced
this issue
Feb 7, 2021
In e400071 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net>
ColinIanKing
pushed a commit
to ColinIanKing/linux-next
that referenced
this issue
Feb 8, 2021
In e400071 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
|
What was wrong with this mouse that it was even touched? Just curious as I've been using it for years with no problems. Just seems a bit random that this update decided to touch this old mouse. I'm still a bit new to this, and I've been unable to find where it details the reasoning. Thanks. |
nareshkamboju
pushed a commit
to nareshkamboju/linux
that referenced
this issue
Mar 2, 2021
commit ef07c11 upstream. In e400071 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
woodsts
pushed a commit
to woodsts/linux-stable
that referenced
this issue
Mar 4, 2021
commit ef07c11 upstream. In e400071 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
woodsts
pushed a commit
to woodsts/linux-stable
that referenced
this issue
Mar 4, 2021
commit ef07c11 upstream. In e400071 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
gregkh
pushed a commit
to gregkh/linux
that referenced
this issue
Mar 4, 2021
commit ef07c11 upstream. In e400071 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
@FFY00 logitech-djreceiver 0003:046D:C537.0002: Unexpected input report number 128
|
kaixuxiakx
pushed a commit
to Tencent/TencentOS-kernel
that referenced
this issue
Mar 30, 2021
commit ef07c116d98772952807492bd32a61f5af172a94 upstream. In e400071a805d6229223a98899e9da8c6233704a1 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071a805d6 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
gibsson
pushed a commit
to boundarydevices/linux
that referenced
this issue
Apr 8, 2021
commit ef07c11 upstream. In e400071 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
gibsson
pushed a commit
to boundarydevices/linux
that referenced
this issue
Apr 8, 2021
commit ef07c11 upstream. In e400071 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
gibsson
pushed a commit
to boundarydevices/linux
that referenced
this issue
Apr 8, 2021
commit ef07c11 upstream. In e400071 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
it-is-a-robot
pushed a commit
to openeuler-mirror/kernel
that referenced
this issue
Apr 10, 2021
stable inclusion from stable-5.10.20 commit eb6a537479b4e62be75b7eb98613b6b0595d9c6d bugzilla: 50608 -------------------------------- commit ef07c11 upstream. In e400071 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Chen Jun <chenjun102@huawei.com> Acked-by: Xie XiuQi <xiexiuqi@huawei.com> Signed-off-by: Zheng Zengkai <zhengzengkai@huawei.com>
kaixuxiakx
pushed a commit
to Tencent/TencentOS-kernel
that referenced
this issue
Apr 12, 2021
commit ef07c116d98772952807492bd32a61f5af172a94 upstream. In e400071a805d6229223a98899e9da8c6233704a1 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071a805d6 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
Hi @FFY00 , your patch https://lkml.org/lkml/2021/1/30/382 ended up in the mainline kernel as of 5.11.3, however, as of 5.11.15 (also Ubuntu 5.11.0.14) we're not out of the water. The situation anonymouspetdo reports is still valid, i.e., it works but with plenty of errors in kern.log. |
|
What exactly doesn't work? The messages that show up in dmesg are not really worrying if everything works fine. I am pretty sure it is just an alternative channel the receiver uses to report input events directly to the windows driver. In which case, we should silence those messages in the kernel driver. |
|
It seems that the functionality is fine - thanks on that front! |
wataash
pushed a commit
to wataash/linux
that referenced
this issue
Apr 29, 2021
BugLink: https://bugs.launchpad.net/bugs/1921960 commit ef07c11 upstream. In e400071 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Kamal Mostafa <kamal@canonical.com> Signed-off-by: Kelsey Skunberg <kelsey.skunberg@canonical.com>
jpuhlman
pushed a commit
to MontaVista-OpenSourceTechnology/linux-mvista
that referenced
this issue
Apr 30, 2021
Source: Kernel.org MR: 109783 Type: Integration Disposition: Backport from git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable linux-5.4.y ChangeID: 394f2b794310f48abde38dbed33aae7ae98db6a2 Description: commit ef07c11 upstream. In e400071 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster@mvista.com>
|
When my Ubuntu laptop goes to sleep while the G602 receiver is plugged in, when I wake it up, I get a black screen with the "Unexpected input report number" message and I have to restart. |
delphix-devops-bot
pushed a commit
to delphix/linux-kernel-gcp
that referenced
this issue
May 12, 2021
BugLink: https://bugs.launchpad.net/bugs/1918974 commit ef07c11 upstream. In e400071 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Kamal Mostafa <kamal@canonical.com> Signed-off-by: Kelsey Skunberg <kelsey.skunberg@canonical.com>
gregmarsden
pushed a commit
to oracle/linux-uek
that referenced
this issue
Jun 18, 2021
commit ef07c11 upstream. In e400071 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 394f2b7) Signed-off-by: Jack Vogel <jack.vogel@oracle.com>
|
Running pop-os, every time I press any mouse button or unpress the button (G602), I get the following message in The following is my uname: More severely, the mouse often stutters and rubberbands, reporting the same report 128 every time it does so. |
|
I don't have any other problem with my G602 using hid-logitech-dj module except that it keeps create a false kernel error message [Unexpected input report number 128] It seems that the original author has no interest of fixing this false error message because everything else works (we just need to deal with a bloated kernel error messages). @eiis1000 How to blacklist module: https://wiki.archlinux.org/title/Kernel_module#Blacklisting create file /etc/modprobe.d/blk-hid-logitech-dj.conf with following content |
freak07
pushed a commit
to freak07/Kirisakura_ANAKIN_ROG5
that referenced
this issue
Sep 11, 2021
commit ef07c116d98772952807492bd32a61f5af172a94 upstream. In e400071a805d6229223a98899e9da8c6233704a1 I added support for the receiver that comes with the G602 device, but unfortunately I screwed up during testing and it seems the keyboard events were actually not being sent to userspace. This resulted in keyboard events being broken in userspace, please backport the fix. The receiver uses the normal 0x01 Logitech keyboard report descriptor, as expected, so it is just a matter of flagging it as supported. Reported in libratbag/libratbag#1124 Fixes: e400071a805d6 ("HID: logitech-dj: add the G602 receiver") Cc: <stable@vger.kernel.org> Signed-off-by: Filipe Laíns <lains@riseup.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 394f2b7) (cherry picked from commit 81d83fd91b4747dabdecde26819329968bc77edc)
|
Please make sure you are running at least Linux 5.12. |
|
I am also seeing the errors when I press any mouse buttons on g602 |
|
How I got rid of G602 problems on linux:
Result: everything works including Solaar and system log is clean. |
|
The In the meantime, I'm just going to let the errors happen, as the mouse works fine for me, and I don't want to forget to un-blacklist the module when the issue is fixed. |
|
@token0 Thanks for this. I ended up doing something similar. I had desperately flashed my mouse to 4700.0012 and I think that broke compatibility with LGS, as it silently fails to get or set any buttons on the on-board profile. G Hub works great, thankfully, so I used that to configure the buttons and copy it to the on-board profile. I didn't need to blacklist the logitech dj module, compile a custom kernel, or remove libratbag or piper. Pressing the buttons just sends normal F13-F18 events on the /dev/input device. I prefer to keep using the dj module in spite of the dmesg spam, because the mouse is rolled into 1 named input device, in contrast to the generic driver which exposes 3 "Logitech Receiver" devices each with their own slice of events. |
|
[edit] After swearing at GHUB for several minutes, i restarted it, and now its showing me the stuff i want to actually see, @libjared Can you expand on this? I have been trying to do exactly the same thing, by temporarily xmodmap'ing F13 to keycode 148 ( XF86Calculator), so theres actually a key to press in 'Logitech Gaming Software' inside a qemu win10 VM to do the binding, but LGS doesnt see F13 when i push the key, nor if i |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello guys
I have a Logitech G602 gaming mouse with 8 extras buttons which are bound to different keyboard shortcuts! Everything was working fine since yesterday after a kernel update to 5.10.11. All the extra buttons stopped working (no event in XEV)and after some digging, I found out there was a commit regarding this mouse in the kernel update :
commit 1e6fc9768ed2c3917e1fd7af26cb194dfe14f7da
I downgraded the LTS kernel and I have the same issue.
Can someone help me please!
Information
ratbagdversion (ratbagd --version):ArchLinux
uname -srmo):KERNEL VERSION HERE5.10.11
Device info (if applicable):
$ ratbagd --verbose=raw
OUTPUT HERE
The text was updated successfully, but these errors were encountered: