You are not logged in.
After the latest update, my keyboard is not functioning correctly.
Half of the buttons do not work, and the other half perform unexpected actions.
Moreover, this behavior occurs only when using the special "Logitech Lightspeed" receiver, but not when using Bluetooth.
Offline
Offline
ok tnx.. i'll solve this just by downgrading linux kernel package
Offline
Possibly related: Logitech G510s keyboard not working on kernel 6.6.1.
[ 7.990759] sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:08.0/0000:07:00.0/0000:08:0c.0/0000:0c:00.0/usb1/1-3/1-3:1.1/0003:046D:C22D.000B/leds/g15::kbd_backlight/color'
[ 7.990762] CPU: 4 PID: 451 Comm: (udev-worker) Tainted: G OE 6.6.1-arch1-1 #1 be166a630cd909acf8820643140e9106c6ea80e6
[ 7.990766] Hardware name: ASUS System Product Name/TUF GAMING X670E-PLUS WIFI, BIOS 1813 10/13/2023
[ 7.990767] Call Trace:
[ 7.990769] <TASK>
[ 7.990771] dump_stack_lvl+0x47/0x60
[ 7.990778] sysfs_warn_dup+0x5a/0x70
[ 7.990783] sysfs_add_file_mode_ns+0x11a/0x130
[ 7.990786] internal_create_group+0x125/0x3b0
[ 7.990789] internal_create_groups+0x42/0xa0
[ 7.990791] device_add+0x5ad/0x8a0
[ 7.990794] ? srso_alias_return_thunk+0x5/0x7f
[ 7.990798] ? kstrdup+0x4c/0x70
[ 7.990802] device_create_groups_vargs+0xce/0xf0
[ 7.990805] device_create_with_groups+0x4b/0x70
[ 7.990808] led_classdev_register_ext+0x1d2/0x470
[ 7.990812] ? devm_led_classdev_register_ext+0x3a/0x90
[ 7.990817] devm_led_classdev_register_ext+0x50/0x90
[ 7.990820] lg_g15_probe+0x667/0x770 [hid_lg_g15 4a43fb61ec72c8e966287bea16924535918cb678]
[ 7.990826] hid_device_probe+0x10e/0x1a0
[ 7.990829] really_probe+0x19b/0x3e0
[ 7.990833] ? __pfx___device_attach_driver+0x10/0x10
[ 7.990835] __driver_probe_device+0x78/0x160
[ 7.990838] driver_probe_device+0x1f/0x90
[ 7.990841] __device_attach_driver+0x89/0x110
[ 7.990844] bus_for_each_drv+0x92/0xf0
[ 7.990847] __device_attach+0xb2/0x1b0
[ 7.990850] ? __pfx___hid_bus_reprobe_drivers+0x10/0x10
[ 7.990853] device_reprobe+0x4e/0x90
[ 7.990855] ? __hid_bus_reprobe_drivers+0x39/0x60
[ 7.990857] bus_for_each_dev+0x85/0xd0
[ 7.990860] ? __pfx___hid_bus_driver_added+0x10/0x10
[ 7.990862] __hid_bus_driver_added+0x2c/0x40
[ 7.990865] bus_for_each_drv+0x92/0xf0
[ 7.990868] __hid_register_driver+0x74/0x80
[ 7.990871] ? __pfx_ms_driver_init+0x10/0x10 [hid_microsoft a9a7eb35e2e5d1c3f68fd046c8c3a94730fe7fdb]
[ 7.990876] do_one_initcall+0x5a/0x320
[ 7.990883] do_init_module+0x60/0x240
[ 7.990888] init_module_from_file+0x89/0xe0
[ 7.990894] idempotent_init_module+0x120/0x2b0
[ 7.990898] __x64_sys_finit_module+0x5e/0xb0
[ 7.990901] do_syscall_64+0x5d/0x90
[ 7.990904] ? do_syscall_64+0x6c/0x90
[ 7.990906] ? srso_alias_return_thunk+0x5/0x7f
[ 7.990908] ? exit_to_user_mode_prepare+0x132/0x1f0
[ 7.990911] ? srso_alias_return_thunk+0x5/0x7f
[ 7.990914] ? syscall_exit_to_user_mode+0x2b/0x40
[ 7.990916] ? srso_alias_return_thunk+0x5/0x7f
[ 7.990918] ? do_syscall_64+0x6c/0x90
[ 7.990920] ? syscall_exit_to_user_mode+0x2b/0x40
[ 7.990922] ? srso_alias_return_thunk+0x5/0x7f
[ 7.990924] ? do_syscall_64+0x6c/0x90
[ 7.990927] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 7.990930] RIP: 0033:0x7f4ef790773d
[ 7.990947] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 95 0c 00 f7 d8 64 89 01 48
[ 7.990948] RSP: 002b:00007ffe65533e38 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[ 7.990951] RAX: ffffffffffffffda RBX: 000056078c53f520 RCX: 00007f4ef790773d
[ 7.990952] RDX: 0000000000000004 RSI: 00007f4ef7e05376 RDI: 000000000000000e
[ 7.990953] RBP: 00007f4ef7e05376 R08: 00005602ec2c7357 R09: fffffffffffffe90
[ 7.990954] R10: 0000000000000050 R11: 0000000000000246 R12: 0000000000020000
[ 7.990956] R13: 000056078c52e2f0 R14: 0000000000000000 R15: 000056078c527640
[ 7.990960] </TASK>
Offline
Possibly related: Logitech G510s keyboard not working on kernel 6.6.1.
Same kybd same issue.
Odd, it seems like we're deleting old tech drivers
from the stream. G510 is at least 11 years old and is usually
compatible with basic kybd drivers.
Offline
Same kybd same issue.
Have you tried reverting 9d1bd9346241cd6963b58da7ffb7ed303285f684 ? The kernel linked below has been built with 9d1bd9346241cd6963b58da7ffb7ed303285f684 reverted.
https://drive.google.com/file/d/14NRwH3 … sp=sharing linux-6.6.1.arch1-1.1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/16zbMZy … sp=sharing linux-headers-6.6.1.arch1-1.1-x86_64.pkg.tar.zst
Offline
W54J04S07T wrote:Same kybd same issue.
Have you tried reverting 9d1bd9346241cd6963b58da7ffb7ed303285f684 ? The kernel linked below has been built with 9d1bd9346241cd6963b58da7ffb7ed303285f684 reverted.
https://drive.google.com/file/d/14NRwH3 … sp=sharing linux-6.6.1.arch1-1.1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/16zbMZy … sp=sharing linux-headers-6.6.1.arch1-1.1-x86_64.pkg.tar.zst
Thanks loqs , but the kybd ( G510 ) still hangs.
Had my hopes up there...
Offline
Thanks loqs , but the kybd ( G510 ) still hangs.
Had my hopes up there...
At least you found out now.
This is the first bisection point:
https://drive.google.com/file/d/1g4DV9D … sp=sharing linux-6.5.r7406.ga1c19328a160-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1EULZz9 … sp=sharing linux-headers-6.5.r7406.ga1c19328a160-1-x86_64.pkg.tar.zst
Offline
W54J04S07T wrote:Thanks loqs , but the kybd ( G510 ) still hangs.
Had my hopes up there...
At least you found out now.
This is the first bisection point:
https://drive.google.com/file/d/1g4DV9D … sp=sharing linux-6.5.r7406.ga1c19328a160-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1EULZz9 … sp=sharing linux-headers-6.5.r7406.ga1c19328a160-1-x86_64.pkg.tar.zst
That works...
But it is the 6.5.0 kernel and the kybd worked up to 6.5.9 ... ( its the 6.6.1 branch release that messed up),
although I see the 6.5.0 build date was yesterday afternoon.
Your previous 6.6.1 release was built yesterday morning... (???).
Last edited by W54J04S07T (2023-11-11 15:52:34)
Offline
But it is the 6.5.0 kernel and the kybd worked up to 6.5.9 ... ( its the 6.6.1 branch release that messed up),
I missed testing 6.6, assuming the issue was between 6.5 and 6.6 not 6.6 and 6.6.1. If the issue is between 6.5 and 6.6 then knowing 6.5.9 does not have the issue does not help as the stable kernel branched off from mainline at 6.5.
https://drive.google.com/file/d/15mJh1s … drive_link linux-6.6-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1FYdsg1 … drive_link linux-headers-6.6-1-x86_64.pkg.tar.zst
although I see the 6.5.0 build date was yesterday afternoon.
Your previous 6.6.1 release was built yesterday morning... (???).
I built it for https://bbs.archlinux.org/viewtopic.php … 5#p2130725
Edit:
If 6.6 is good:
That works...
git bisect good
Bisecting: 3935 revisions left to test after this (roughly 12 steps)
[e4f1b8202fb59c56a3de7642d50326923670513f] Merge tag 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost
https://drive.google.com/file/d/14FYlnw … sp=sharing linux-6.5.r11353.ge4f1b8202fb5-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1qpWc1s … sp=sharing linux-headers-6.5.r11353.ge4f1b8202fb5-1-x86_64.pkg.tar.zst
Last edited by loqs (2023-11-11 16:36:28)
Offline
[
I missed testing 6.6, assuming the issue was between 6.5 and 6.6 not 6.6 and 6.6.1. If the issue is between 6.5 and 6.6 then knowing 6.5.9 does not have the issue does not help as the stable kernel branched off from mainline at 6.5....
If 6.6 is good:
I'm only using official arch released kernels. AFAIK 6.6.0 was never released. And if upstream branched from
6.5.0 then likely the problem inserted itself somewhere in 6.6.0 and above if I'm following you right.
Offline
AFAIK 6.6.0 was never released.
6.6 was packaged but never left core-testing. You can obtain it from the ALA.
Sudo pacman -U https://archive.archlinux.org/packages/l/linux/linux-6.6.arch1-1-x86_64.pkg.tar.zst
Edit:
Perhaps showing you the output from git would explain why I wanted to test between 6.5 and 6.6. Bisecting between 6.5.9 and 6.6.1
$ git bisect start
status: waiting for both good and bad commits
$ git bisect good v6.5.9
status: waiting for bad commit, 1 good commit known
$ git bisect bad v6.6.1
Bisecting: a merge base must be tested
[2dde18cd1d8fac735875f2e4987f11817cc0bc2c] Linux 6.5
$ git bisect good v6.5
Bisecting: 7913 revisions left to test after this (roughly 13 steps)
[a1c19328a160c80251868dbd80066dce23d07995] Merge tag 'soc-arm-6.6' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
Bisecting between 6.5 and 6.6
$ git bisect start
status: waiting for both good and bad commits
$ git bisect good v6.5
status: waiting for bad commit, 1 good commit known
$ git bisect bad v6.6
Bisecting: 7882 revisions left to test after this (roughly 13 steps)
[a1c19328a160c80251868dbd80066dce23d07995] Merge tag 'soc-arm-6.6' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
The first commit git wants to check assuming you tell git 6.5 is good is in both cases a1c19328a160c80251868dbd80066dce23d07995 which corresponds to linux-6.5.r7406.ga1c19328a160-1-x86_64.pkg.tar.zst which you already tested as good. The only difference is 7913 vs 7882 revisions the 32 commits 6.1.1 introduced are covered by less than one bisection step so did not cause git to change its bisection plan.
Last edited by loqs (2023-11-11 19:24:20)
Offline
Boy is ALA slow today...
Tested 6.6.0, and kybd didn't work.
So, I guess whatever was inserted into 6.6.0 after branching from 6.5.0
must be the culprit.
Last edited by W54J04S07T (2023-11-11 19:44:51)
Offline
Boy is ALA slow today...
Tested 6.6.0, and kybd didn't work.
So, I guess whatever was inserted into 6.6.0 after branching from 6.5.0
must be the culprit.
Offline
Please test linux-6.5.r11353.ge4f1b8202fb5-1-x86_64.pkg.tar.zst from my edit to post 10.
Offline
Please test linux-6.5.r11353.ge4f1b8202fb5-1-x86_64.pkg.tar.zst from my edit to post 10.
That works
Offline
$ git bisect good
Bisecting: 1966 revisions left to test after this (roughly 11 steps)
[9608c7b729e29c177525006711966ae0fd399b11] Merge tag 'drm-fixes-2023-09-15' of git://anongit.freedesktop.org/drm/drm
https://drive.google.com/file/d/1snp8je … sp=sharing linux-6.6rc1.r161.g9608c7b729e2-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1RNmp4- … sp=sharing linux-headers-6.6rc1.r161.g9608c7b729e2-1-x86_64.pkg.tar.zst
Offline
$ git bisect good Bisecting: 1966 revisions left to test after this (roughly 11 steps) [9608c7b729e29c177525006711966ae0fd399b11] Merge tag 'drm-fixes-2023-09-15' of git://anongit.freedesktop.org/drm/drm
https://drive.google.com/file/d/1snp8je … sp=sharing linux-6.6rc1.r161.g9608c7b729e2-1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1RNmp4- … sp=sharing linux-headers-6.6rc1.r161.g9608c7b729e2-1-x86_64.pkg.tar.zst
These failed.
Fascinating how whatever they did, not only fails with plasma,
but you can't even get a CTRL-ALT-Fn to switch to a console,
when it fails.
Offline
If you add the kernel parameters below to disable KMS and not start a display manager?
nomodeset i915.modeset=0 nouveau.modeset=0 nvidia-drm.modeset=0 systemd.unit=multi-user.target
Last edited by loqs (2023-11-12 14:21:35)
Offline
If you add the kernel parameters below to disable KMS and not start a display manager?
nomodeset i915.modeset=0 nouveau.modeset=0 nvidia-drm.modeset=0 systemd.unit=multi-user.target
???
This particular machine uses AMDGPU, not Nouvaeu.
Also, should this line go in linux.preset ?
Offline
The aim was to boot the system to a console. You might be able to check the journal for the linux-6.6rc1.r161.g9608c7b729e2-1 boot and see if it has the same backtrace.
Offline
The aim was to boot the system to a console. You might be able to check the journal for the linux-6.6rc1.r161.g9608c7b729e2-1 boot and see if it has the same backtrace.
oh... sorry, when I posted that comment, I was merely pointing out that
the G915 kybd used by the O.P. had the same problems as
the G510 kybd I'm using and the G510 is much older that the O.P.s kybd.
Is someone purging old tech support from the 6.5+ kernels ( maybe ) and
the G series kybds got caught in the wash?
I'm not clear, on exactly where I should put that KMS line as I have both Linux and Linux-LTS kernels and the link
on kernel parameters was not entirely helpful.
Last edited by W54J04S07T (2023-11-12 17:54:55)
Offline
Post #4 by ArthurBorsboom was with a G510 and included a backtrace. Does the journal for your affected system show the same backtrace? If such a trace is always present then you can avoid having to work around the display issue.
Offline
Post #4 by ArthurBorsboom was with a G510 and included a backtrace. Does the journal for your affected system show the same backtrace? If such a trace is always present then you can avoid having to work around the display issue.
If I use journalctl, I don't see anything like that as I don't know what he used ( grep ??? ) and what he searched for...
Offline
Please post the full system journal for a boot with the issue.
journalctl -b #
Where # is the number of the boot for example -1 would be the last boot, -2 would be two boots ago e.t.c..
Offline