You are not logged in.
smitropoulos wrote:Just tried the fixed kernel and will not reverse the breakage of my G502X. Should I open a new thread for it? I think it was speculated that the same thing broke mice and keyboards
I noticed in `lsusb -tvv` I am getting the same ID (046d:c547) as discussed in the ticket https://bugzilla.kernel.org/show_bug.cgi?id=218094
Which fixed kernel did you try linux-6.6.1.arch1-1.4-x86_64.pkg.tar.zst from post #71 or linux-6.6.1.arch1-1.1-x86_64.pkg.tar.zst from post #6 or did both of them fail to reverse the breakage?
I only tried the one in #71. Will try #6 as well and post back
EDIT:
linux-6.6.1.arch1-1.1-x86_64.pkg.tar.zst from post #6 did actually fix my issue! Thank you so much!
P.S. Do you build these kernels yourself?
Last edited by smitropoulos (2023-11-20 22:56:09)
Offline
linux-6.6.1.arch1-1.1-x86_64.pkg.tar.zst from post #6 did actually fix my issue! Thank you so much!
You might want to report on https://bugzilla.kernel.org/show_bug.cgi?id=218094 that reverting 9d1bd9346241cd6963b58da7ffb7ed303285f684 restored the functionality of your G502X. Might also if you were feeling generous reply to [1] with the same information and it is the same issue as https://bugzilla.kernel.org/show_bug.cgi?id=218094
P.S. Do you build these kernels yourself?
Yes.
Offline
Hi everyone; I am new to arch and I have the same problem as the first guy (G915 keyboard presses random keys after upgrading to 6.6.1 kernel). I downgraded the kernel waiting to have this bug fixed.
Today the new version of the kernel has been released (6.6.2) and after installing it the keyboard problem persists; now my question is: will this problem be fixed in the future with the next kernel upgrade or must I fix it manually?
I am new so i don't know how the "rolling release philosophy" works.
Thanks to everyone.
Offline
@skarm it is unlikely that a fix will come from upstream in time for 6.6.3, the lack of response from the commits author is starting to be followed up [1] but it will still take time for a consensus to be reached on what the correct fix will is, implement the fix then have the fix back-ported to stable. The Arch kernel maintainers could apply a fix locally however the current fix (reverting 9d1bd9346241cd6963b58da7ffb7ed303285f684) would remove support for the logitech G Pro X Wireless Superlight that commit added.
Offline
...
The Arch kernel maintainers could apply a fix locally however the current fix (reverting 9d1bd9346241cd6963b58da7ffb7ed303285f684) would remove support for the logitech G Pro X Wireless Superlight that commit added.
...
There are over 4500 views on this thread... the interest alone
would suggest your proposition would have a Big following.
And the nature of the bug suggests someone needs to be very
careful about accepting patches for new H/W ... especially, where
we see a good deal more items getting taken off line than there is
new H/W likely to have been sold into the Linux market space... ![]()
Last edited by W54J04S07T (2023-11-21 19:31:07)
Offline
loqs wrote:...
The Arch kernel maintainers could apply a fix locally however the current fix (reverting 9d1bd9346241cd6963b58da7ffb7ed303285f684) would remove support for the logitech G Pro X Wireless Superlight that commit added.
...There are over 4500 views on this thread... the interest alone
would suggest your proposition would have a Big following.
Upstream intends to revert 9d1bd9346241cd6963b58da7ffb7ed303285f684 as its author is unresponsive [1][2]. The author of 9d1bd9346241cd6963b58da7ffb7ed303285f684 agrees with the revert [3].
I have posted the same information on the Arch bug report [4].
[1]: https://lore.kernel.org/regressions/nyc … k.fhfr.pm/
[2]: https://git.kernel.org/pub/scm/linux/ke … e433335e00
[3]: https://lore.kernel.org/regressions/407 … nmail.com/
[4]: https://bugs.archlinux.org/task/80133#comment223868
Offline
@skarm it is unlikely that a fix will come from upstream in time for 6.6.3, the lack of response from the commits author is starting to be followed up [1] but it will still take time for a consensus to be reached on what the correct fix will is, implement the fix then have the fix back-ported to stable. The Arch kernel maintainers could apply a fix locally however the current fix (reverting 9d1bd9346241cd6963b58da7ffb7ed303285f684) would remove support for the logitech G Pro X Wireless Superlight that commit added.
Sorry for my ignorance, what is 9d1bd9346241cd6963b58da7ffb7ed303285f684?
Offline
Sorry for my ignorance, what is 9d1bd9346241cd6963b58da7ffb7ed303285f684?
9d1bd9346241cd6963b58da7ffb7ed303285f684 [1] is the commit identified as causing the issue.
Offline
skarm wrote:Sorry for my ignorance, what is 9d1bd9346241cd6963b58da7ffb7ed303285f684?
9d1bd9346241cd6963b58da7ffb7ed303285f684 [1] is the commit identified as causing the issue.
Oh ok, so (please correct me if I'm wrong): they added the code that has been posted in https://git.kernel.org/pub/scm/linux/ke … 303285f684 into a modified 6.6.1 kernel, and this modified kernel should solve the problem.
This will work until the release of the new official kernel which will erase the modified code.
Am I right?
I'm really sorry for all these stupid questions
Last edited by skarm (2023-11-22 11:47:06)
Offline
Oh ok, so (please correct me if I'm wrong): they added the code that has been posted in https://git.kernel.org/pub/scm/linux/ke … 303285f684 into a modified 6.6.1 kernel, and this modified kernel should solve the problem.
Almost 9d1bd9346241cd6963b58da7ffb7ed303285f684 introduced the issue. The kernel I built linux-6.6.1.arch1-1.1-x86_64.pkg.tar.zst reverted 9d1bd9346241cd6963b58da7ffb7ed303285f684 erasing the changes 9d1bd9346241cd6963b58da7ffb7ed303285f684 had introduced to the kernel.
This will work until the release of the new official kernel which will erase the modified code.
Yes. I do now know which new official kernel will include the revert of 9d1bd9346241cd6963b58da7ffb7ed303285f684.
Offline
6.6.2.arch1-1 was released. anyone knows whether the fix is shipped or not?
Offline
6.6.2.arch1-1 was released. anyone knows whether the fix is shipped or not?
https://github.com/archlinux/linux/commits/v6.6.2-arch1 does not contain either fix.
Offline
Does not work for me either. I reverted back to 6.5.9
Offline
...
Yes. I do now know which new official kernel will include the revert
...
The suspense is killing us here loqs... ![]()
So which kernel is it??? ![]()
Offline
Just wanna ask if we have an update on this? Thanks! :
Offline
Revert "HID: logitech-dj: Add support for a new lightspeed receiver iteration" queued for 6.3.3 [1]. 6.6.3 is expected some time after Sun, 26 Nov 2023 17:19:17 +0000 [2].
G510s fix [3] is waiting for a pull request to mainline before it can be added to stable. Arch kernel maintainers could choose to pick up the fix sooner.
[1]: https://git.kernel.org/pub/scm/linux/ke … e433335e00
[2]: https://lore.kernel.org/stable/20231124 … ation.org/
[3]: https://lore.kernel.org/linux-leds/2023 … 40suse.de/
Offline
Revert "HID: logitech-dj: Add support for a new lightspeed receiver iteration" queued for 6.3.3 [1]. 6.6.3 is expected some time after Sun, 26 Nov 2023 17:19:17 +0000 [2].
G510s fix [3] is waiting for a pull request to mainline before it can be added to stable. Arch kernel maintainers could choose to pick up the fix sooner.[1]: https://git.kernel.org/pub/scm/linux/ke … e433335e00
[2]: https://lore.kernel.org/stable/20231124 … ation.org/
[3]: https://lore.kernel.org/linux-leds/2023 … 40suse.de/
Thanks! Looking forward!
Offline
Thanks! Looking forward!
6.6.3 is now up to its 4th release candidate [1] so the expected release will be no sooner than Tue, 28 Nov 2023 15:43:06 +0000.
Edit:
6.6.3.arch1-1 containing Revert "HID: logitech-dj: Add support for a new lightspeed receiver iteration" is now in core testing.
[1] https://lore.kernel.org/stable/20231126 … ation.org/
Last edited by loqs (2023-11-29 08:12:51)
Offline
Updated to 6.6.3, and it's working now. Gonna wait for it to be released for linux-g14. Thanks!
Offline
Revert "HID: logitech-dj: Add support for a new lightspeed receiver iteration" queued for 6.3.3 [1]. 6.6.3 is expected some time after Sun, 26 Nov 2023 17:19:17 +0000 [2].
G510s fix [3] is waiting for a pull request to mainline before it can be added to stable. Arch kernel maintainers could choose to pick up the fix sooner.[1]: https://git.kernel.org/pub/scm/linux/ke … e433335e00
[2]: https://lore.kernel.org/stable/20231124 … ation.org/
[3]: https://lore.kernel.org/linux-leds/2023 … 40suse.de/
I got interested in making kernel packages from your bisection excercise.
So I compiled a kernel... no problems.
But when I did "git revert 9d1bd9346241cd6963b58da7ffb7ed303285f684"
I got a not found type of error.
Are You using the Arch git repo or the Kernel.org git repo?
Last edited by W54J04S07T (2023-11-29 19:30:34)
Offline
But when I did "git revert 9d1bd9346241cd6963b58da7ffb7ed303285f684"
I got a not found type of error.Are You using the Arch git repo or the Kernel.org git repo?
Strange both git repos contain 9d1bd9346241cd6963b58da7ffb7ed303285f684
Arch github
$ git remote -v
origin https://github.com/archlinux/linux (fetch)
origin https://github.com/archlinux/linux (push)
$ git tag --contains 9d1bd9346241cd6963b58da7ffb7ed303285f684
v6.6-arch1
v6.6.1-arch1
v6.6.2-arch1
v6.6.3-arch1mainline kernel.org
$ git remote -v
origin https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git (fetch)
origin https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git (push)
$ git tag --contains 9d1bd9346241cd6963b58da7ffb7ed303285f684
v6.6
v6.6-rc1
v6.6-rc2
v6.6-rc3
v6.6-rc4
v6.6-rc5
v6.6-rc6
v6.6-rc7
v6.7-rc1
v6.7-rc2
v6.7-rc3stable kernel.org
$ git remote -v
origin https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git (fetch)
origin https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git (push)
$ git tag --contains 9d1bd9346241cd6963b58da7ffb7ed303285f684
v6.6
v6.6-rc1
v6.6-rc2
v6.6-rc3
v6.6-rc4
v6.6-rc5
v6.6-rc6
v6.6-rc7
v6.6.1
v6.6.2
v6.6.3
v6.7-rc1
v6.7-rc2
v6.7-rc3Offline
Strange indeed.
I'll just redo this and see if I can't find my mistake.
Offline
Relating to G510s fix; pull request for 6.7-rc4 "LEDs fixes for v6.7" [1] containing "leds: class: Don't expose color sysfs entry" has been opened.
Edit:
The pull has been accepted to mainline [3] unfortunately too late for 6.6.4-rc1 [4].
Edit2:
Queued for 6.6.5 [5].
[1] https://lore.kernel.org/lkml/2023113014 … oogle.com/
[2]: https://git.kernel.org/pub/scm/linux/ke … 5ee6b2d1a5
[3]: https://git.kernel.org/pub/scm/linux/ke … e32370aa7c
[4]: https://git.kernel.org/pub/scm/linux/ke … inux-6.6.y
[5]: https://git.kernel.org/pub/scm/linux/ke … 10c1121230
Last edited by loqs (2023-12-04 07:59:40)
Offline
Relating to G510s fix; ...
Queued for 6.6.5 [5].
...
[5]: https://git.kernel.org/pub/scm/linux/ke … 10c1121230
Missed 6.6.5.
Can confirm fix in 6.6.6 works with no anomalies that I've seen so far.
Thank You.
Offline
meanwhile I had issue with mine logitech g915 tkl keyboard after installing Manjaro. F1 to F12 keys were not working. I fixed it from switching keyboard layout from "Generic 104" to "Logitech cordless desktop".
P.S. kernel was version 6.9
Offline