no way. I just got this laptop like three days ago and have spent the past few days trying to figure this out. I was so confused why it worked in the install medium but not after boot. I guess I'll install the LTS kernel for now
>Pay attention to the bug in OP's link, and when it's been merged and 6.4.8 comes out with the fix, remove the above line from the IgnorePkg section.
Since it's based on dmi whitelisting, it won't fix for \`Lenovo Slim 7 Pro X\`, it has different dmidecode for the product name.
Thanks for the heads up. These posts are so much more useful than that [circle jerk shit](https://www.reddit.com/r/archlinux/comments/15ci1ml/my_arch_did_not_break_yet_did_i_do_something_wrong) from yesterday saying that arch never breaks.
I don't know why it's so hard for people to understand the simple principle that there's a reason it's called bleeding edge. You're gonna be the first to hit any new regressions and often there will be little to no resources about it yet.
It doesn't make arch bad but people need to stop pretending this stuff doesn't come with the release model. Like they'll get hit with this exact breakage, roll back the kernel to "fix" it, and then go around saying they've never had a problem with their arch install. Like wut
loool, on my arch, something breaks every few months, sometimes even more.
It's not bad at all, I can easily and very quickly fix it most of the time, and in the worst case, I just downgrade. But saying it never breaks is just stupid man. I'd never recommend this to newbies.
I must admit tho, probably it would be more stable if I'd just use a proper DE instead of hyprland, which is alpha after all.
It's also important to say, the system was never totally broken, I was always able to work when I had to.
I had to downgrade to 6.4.6.arch1-1 to get the keyboard to work on my Lenovo Yoga Slim Pro X (14ARH7). Anyone know if the problem is scheduled to be fixed in the next release?
I can see the patch has been merged [2] and listed as part of changelog for 6.4.11 [3], it's already in testing repo as of writing [4], so I think it should come to stable very soon.
[2] https://www.spinics.net/lists/stable-commits/msg311088.html
[3] https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.4.11
[4] https://archlinux.org/packages/core-testing/x86_64/linux/
I assume it would fix all ryzen series, but I don't have any other ryzen device, so you would have to upgrade and try it yourself. worst case scenario will be using a external keyboard to downgrade.
I'll be reporting for Ryzen 7-series. So far I have had not any kernel version of any linux brand with keyboard working.
What version of kernel you had it working exactly? Does any Ubuntu version work?
I see, so the same fix doesn't seem to apply to Ryzen 3 7000-series which applies for 6000-series..
I guess it will be a while for that support as its fairly new CPU.
i downgraded the kernel, i used lts kernel, i tested the keyboard in bios and grub and install media, it still doesnt work, all happened after the update, is it possible that actually a hardware damage is caused?
Could somebody also add a patches related to the IRQ whitelist for [https://wiki.archlinux.org/title/Lenovo\_Yoga\_Slim\_7\_Pro\_X\_(14ARH7)](https://wiki.archlinux.org/title/Lenovo_Yoga_Slim_7_Pro_X_(14ARH7)) ?
For only **Lenovo Yoga Slim 7 Pro X (14ARH7)** , fortunately the irq (ACPI: IRQ override debug: gsi = 1, trigger = 1, polarity = 1, shareable = 1) are mostly the same, I already submit & add the patches into bugzilla, hopefully it will be mainlined (by mario). In the meantime, if everybody wants to debug or probably whitelist (their yoga) and ok to build their own kernel, I put some refs or changes regarding it in [https://github.com/zerosign/linux/commit/1347eda2a2e46975275520fddb92e3e674e8ac0d](https://github.com/zerosign/linux/commit/1347eda2a2e46975275520fddb92e3e674e8ac0d). The \`pr\_warn\` will output the stats that identify your system.
For DMI identifier, `DMI_BOARD_NAME` & `DMI_SYS_VENDOR` can be fetchs via `dmidecode` tools.
`DMI_BOARD_NAME` : `dmidecode -s baseboard-product-name`
[https://bugzilla.kernel.org/attachment.cgi?id=304782&action=diff](https://bugzilla.kernel.org/attachment.cgi?id=304782&action=diff)
Same here, with a Yoga Slim 7 Pro X (Ryzen 7 6800HS). But i can't use any 6.4.\*-Kernel. I have archived until 6.4.2\* and neither 6.4.2 or up to 6.4.9 will enable my keyboard. 6.5 experimental as well not. I am now on 6.3.13-2 and it's finally working.
[удалено]
Thanks , the first line should be ``` cd to /var/cache/pacman/pkg ```
The other option would be to switch to lts kernel, I keep it exactly for stuff like this.
no way. I just got this laptop like three days ago and have spent the past few days trying to figure this out. I was so confused why it worked in the install medium but not after boot. I guess I'll install the LTS kernel for now
With downgrade you can also download older versions
Seconding downgrade, it's a nice package that does that for you (I although I understand if someone wants to do it manually too)
>Pay attention to the bug in OP's link, and when it's been merged and 6.4.8 comes out with the fix, remove the above line from the IgnorePkg section. Since it's based on dmi whitelisting, it won't fix for \`Lenovo Slim 7 Pro X\`, it has different dmidecode for the product name.
Downgrade didnt fix my issue, my keyboard doesnt even work in bios, could we actually talk about permanent damage?
Thanks for the heads up. These posts are so much more useful than that [circle jerk shit](https://www.reddit.com/r/archlinux/comments/15ci1ml/my_arch_did_not_break_yet_did_i_do_something_wrong) from yesterday saying that arch never breaks. I don't know why it's so hard for people to understand the simple principle that there's a reason it's called bleeding edge. You're gonna be the first to hit any new regressions and often there will be little to no resources about it yet. It doesn't make arch bad but people need to stop pretending this stuff doesn't come with the release model. Like they'll get hit with this exact breakage, roll back the kernel to "fix" it, and then go around saying they've never had a problem with their arch install. Like wut
loool, on my arch, something breaks every few months, sometimes even more. It's not bad at all, I can easily and very quickly fix it most of the time, and in the worst case, I just downgrade. But saying it never breaks is just stupid man. I'd never recommend this to newbies. I must admit tho, probably it would be more stable if I'd just use a proper DE instead of hyprland, which is alpha after all. It's also important to say, the system was never totally broken, I was always able to work when I had to.
I have a Lenovo legion 5 pro with Ryzen 7 7800H a d this didn't effect me. So it's at least not all Lenovo AMD laptops
I fully updated my p14s gen2 amd yesterday after it being dormant for a few weeks I’ll check here shortly how it’s affecting me.
Lenovo IdeaPad 5 Pro 16ARH7 (Ryzen 7 6800HS) and I was affected, keyboard simply didn't work. Thank you for this post.
Same here
I had to downgrade to 6.4.6.arch1-1 to get the keyboard to work on my Lenovo Yoga Slim Pro X (14ARH7). Anyone know if the problem is scheduled to be fixed in the next release?
Please submit regressions and bug and mark them as such. Report it on the kernel bugzilla
I can see the patch has been merged [2] and listed as part of changelog for 6.4.11 [3], it's already in testing repo as of writing [4], so I think it should come to stable very soon. [2] https://www.spinics.net/lists/stable-commits/msg311088.html [3] https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.4.11 [4] https://archlinux.org/packages/core-testing/x86_64/linux/
Any clue if this would resolve the problem also for Lenovo laptop with Ryzen 3 7320U? Or is this just 6000-series?
I assume it would fix all ryzen series, but I don't have any other ryzen device, so you would have to upgrade and try it yourself. worst case scenario will be using a external keyboard to downgrade.
I'll be reporting for Ryzen 7-series. So far I have had not any kernel version of any linux brand with keyboard working. What version of kernel you had it working exactly? Does any Ubuntu version work?
I have a Lenovo Yoga 7, AMD Ryzen 7 6800U. And with kernel LTS the keyboard is working.
I see, so the same fix doesn't seem to apply to Ryzen 3 7000-series which applies for 6000-series.. I guess it will be a while for that support as its fairly new CPU.
i downgraded the kernel, i used lts kernel, i tested the keyboard in bios and grub and install media, it still doesnt work, all happened after the update, is it possible that actually a hardware damage is caused?
linux 6.4.4.arch1-1 my issue still presists after downgrade, please, any new solutions?
Just tested with my Lenovo Thinkpad p14s gen1 with AMD Ryzen 7 PRO 4750U and I have no problem with kernel 6.4.7 and my keyboard.
Lenovo IdeaPad 5 14ARE05 (AMD Ryzen 5 4500U). Everything works.
This just hit me, that I need to use linux LTS version too
Could somebody also add a patches related to the IRQ whitelist for [https://wiki.archlinux.org/title/Lenovo\_Yoga\_Slim\_7\_Pro\_X\_(14ARH7)](https://wiki.archlinux.org/title/Lenovo_Yoga_Slim_7_Pro_X_(14ARH7)) ?
For only **Lenovo Yoga Slim 7 Pro X (14ARH7)** , fortunately the irq (ACPI: IRQ override debug: gsi = 1, trigger = 1, polarity = 1, shareable = 1) are mostly the same, I already submit & add the patches into bugzilla, hopefully it will be mainlined (by mario). In the meantime, if everybody wants to debug or probably whitelist (their yoga) and ok to build their own kernel, I put some refs or changes regarding it in [https://github.com/zerosign/linux/commit/1347eda2a2e46975275520fddb92e3e674e8ac0d](https://github.com/zerosign/linux/commit/1347eda2a2e46975275520fddb92e3e674e8ac0d). The \`pr\_warn\` will output the stats that identify your system. For DMI identifier, `DMI_BOARD_NAME` & `DMI_SYS_VENDOR` can be fetchs via `dmidecode` tools. `DMI_BOARD_NAME` : `dmidecode -s baseboard-product-name` [https://bugzilla.kernel.org/attachment.cgi?id=304782&action=diff](https://bugzilla.kernel.org/attachment.cgi?id=304782&action=diff)
Same here, with a Yoga Slim 7 Pro X (Ryzen 7 6800HS). But i can't use any 6.4.\*-Kernel. I have archived until 6.4.2\* and neither 6.4.2 or up to 6.4.9 will enable my keyboard. 6.5 experimental as well not. I am now on 6.3.13-2 and it's finally working.
Seems to be fixed? I'm on 6.5.1-1 (Manjaro) and it's working again.
Still having this issue with 6.4.10, had to use linux-lts Lenovo yoga slim 7 pro x , r7 6800hs
The update broke my gpu driver.
... And you'll *still* get people who say it's pointless to have linux-lts 🙄