[Bug 1217750] New: Nonfunctional brightness keys on Lenovo Slim 7 16" AMD
https://bugzilla.suse.com/show_bug.cgi?id=1217750 Bug ID: 1217750 Summary: Nonfunctional brightness keys on Lenovo Slim 7 16" AMD Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs@suse.de Reporter: variable_valuables761@simplelogin.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871117 --> https://bugzilla.suse.com/attachment.cgi?id=871117&action=edit Output of "brightnessctl -l" for Lenovo 16ARH7 It seems the brightness keys (Fn+F5,Fn+F6) do not work in the latest Tumbleweed KDE snapshot on the Lenovo Slim 7 16" AMD, 16ARH7, 82UX0001US (and this same model is called Yoga outside the United States). It seems the internal display's brightness values are bugged and show up as 0 and "0 (-2147483648%)" in brightnessctl rather than something within the expected range. I've attached the output of "brightnessctl -l", which shows the display and some of the keyboard/charging LEDs on the laptop. Glad to provide any other logs that could be helpful. Hope this is the right place to report this. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217750 Andreas Stieger <Andreas.Stieger@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |1217716 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217750 https://bugzilla.suse.com/show_bug.cgi?id=1217750#c2 --- Comment #2 from varval761 <variable_valuables761@simplelogin.com> --- Ah, I tried that before but I tried again and it worked! Setting "video" made the brightness value changeable in KDE (and the keys worked) but no actual change in the display. Setting "native" made it all work fully, with the display reading as 'amdgpu_bl2'. Out of curiosity, what is the actual issue here? Is it just a matter of defaults chosen by Kernel, distro, etc? Or is there something Lenovo should have done to make this work out of the box? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217750 https://bugzilla.suse.com/show_bug.cgi?id=1217750#c4 --- Comment #4 from varval761 <variable_valuables761@simplelogin.com> --- Created attachment 871309 --> https://bugzilla.suse.com/attachment.cgi?id=871309&action=edit Output of "hwinfo" for Lenovo 16ARH7 Ooh thank you! Here's the hwinfo output. I should note that this is on a live USB of Tumbleweed KDE, in case that's relevant for drivers etc (and so I don't have Nvidia proprietary drivers installed either). And there are a few other laptops that carry the same "16ARH7" name, but not sure how similar their internals would be. And yeah, this is a really nice machine but it seems Lenovo only supports Thinkpads for Linux. Though with how much Linux is growing these days, hopefully hardware vendors can expand their support one day soon :) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217750 https://bugzilla.suse.com/show_bug.cgi?id=1217750#c6 --- Comment #6 from varval761 <variable_valuables761@simplelogin.com> --- Ok, I'm currently unable to fully install Tumbleweed on this machine, so I wouldn't be able to reboot after installing Nvidia drivers. Unless you know of a way to have persistent storage with a live USB? I assume a VM wouldn't let me test this backlight support correctly, right? Is Prime important to install for this test as well? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217750 https://bugzilla.suse.com/show_bug.cgi?id=1217750#c7 --- Comment #7 from varval761 <variable_valuables761@simplelogin.com> --- I still plan to test the proprietary Nvidia driver and some other things, but I just wanted to check whether there's any new info since I last looked into this that I should be aware of before testing again? I was also wondering if it's possible to completely disable the Nvidia dGPU and just use the AMD iGPU (with the open source AMD drivers)? How do I know which GPU the built-in laptop screen is "connected to"? And how can I know which GPU is being used by KDE/KWin and other programs? I can also test the new HDR functionality in KDE and see how it looks with different drivers etc, if that could give any more clues. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217750 https://bugzilla.suse.com/show_bug.cgi?id=1217750#c9 --- Comment #9 from varval761 <variable_valuables761@simplelogin.com> --- Ok thanks! Without setting acpi_backlight, only nvidia_wmi_ec_backlight shows up in /sys/class/backlight/ With acpi_backlight=native, only amdgpu_bl2 shows up in /sys/class/backlight/ (This is still on nouveau/amdgpu; will test out proprietary Nvidia soon.) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217750 https://bugzilla.suse.com/show_bug.cgi?id=1217750#c11 --- Comment #11 from varval761 <variable_valuables761@simplelogin.com> --- Created attachment 874096 --> https://bugzilla.suse.com/attachment.cgi?id=874096&action=edit Output of "hwinfo" for Lenovo 16ARH7 (without setting acpi_backlight) I realized my previous hwinfo was with acpi_backlight=native, so here's the hwinfo without setting any acpi_backlight kernel parameter, just in case it could be useful. Without setting acpi_backlight, "echo 100 > /sys/class/backlight/nvidia_wmi_ec_backlight/brightness" gives an invalid argument error. With acpi_backlight=native, "echo 100 > /sys/class/backlight/amdgpu_bl2/brightness" does change the brightness. The brightness keys and sliders in KDE also work (as I mentioned before). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217750 https://bugzilla.suse.com/show_bug.cgi?id=1217750#c13 --- Comment #13 from varval761 <variable_valuables761@simplelogin.com> --- No worries! I actually was just now able to try the proprietary Nvidia driver. It actually has the same issue as nouveau, with the brightness keys not working and trying to set it in "/sys/class/backlight/nvidia_wmi_ec_backlight" gives the same invalid argument error. In fact, max_brightness is 0 and brightness is stuck at 145. I even tested it on different OS's (Pop!_OS and Nobara, which have pre-installed Nvidia ISO's) and same issue with both. Unless I'm missing extra steps to try after installing Nvidia driver? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217750 https://bugzilla.suse.com/show_bug.cgi?id=1217750#c16 --- Comment #16 from varval761 <variable_valuables761@simplelogin.com> --- I tried setting nvidia.NVreg_RegistryDwords=EnableBrightnessControl=1 for both nouveau and nvidia, and behavior didn't change. I also tried setting amdgpu.backlight=0 alongside this parameter, and no change with that either. I also tried setting amdgpu.backlight=1 with no other parameters, and no change either (still only showed nvidia_wmi_ec_backlight). While testing all these different configurations, I also suspended and resumed, and no change in behavior with that either. I also found this thread of info which might be related? https://lore.kernel.org/all/Y785lBG%2FAIdHBB0C@lenny/ My GPU is indeed the 3050 mobile, but in my BIOS there's only one dropdown to choose between hybrid and UMA, so I guess my machine doesn't have a proper mux switch? I also checked in Windows 11's control panel and the Nvidia control panel and both indicate the display is connected to the AMD GPU. So, overall, the only thing that's worked so far is acpi_backlight=native, which switches the device to amdgpu_bl2 which can be changed. But let me know if there's anything else we should try! (Or if there's a more "proper" fix we can attempt) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217750 https://bugzilla.suse.com/show_bug.cgi?id=1217750#c17 --- Comment #17 from varval761 <variable_valuables761@simplelogin.com> --- Oops, correction: my BIOS dropdown says "switchable" or "UMA", not hybrid. I also read some systems' backlight controls were fixed with a BIOS update, but I'm typically wary of BIOS updates, especially since I use this machine for sensitive work. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217750 https://bugzilla.suse.com/show_bug.cgi?id=1217750#c19 --- Comment #19 from varval761 <variable_valuables761@simplelogin.com> --- Yes, acpi_backlight=native seems to be the only thing that works so far. Kernel patch sounds great! If there's any way I could help let me know. I think I am unable to test a patched kernel outside the usual TW snapshots for the time being. I can report back once it lands in 6.9 or 6.10 though of course. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217750 Ilgaz Öcal <ilgaz@ilgaz.gen.tr> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1223838 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217750 https://bugzilla.suse.com/show_bug.cgi?id=1217750#c22 --- Comment #22 from varval761 <variable_valuables761@simplelogin.com> --- Thank you very much! I will test when it lands in TW and report back. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1217750 https://bugzilla.suse.com/show_bug.cgi?id=1217750#c23 --- Comment #23 from varval761 <variable_valuables761@simplelogin.com> --- It worked! Snapshot 20240512 still had same behavior, but 20240514 (kernel 6.8.8->6.8.9) has the brightness keys working. (Even if it's maybe technically a workaround rather than a "proper" fix) Thanks again! -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com