You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Legion Slim 7 gen 7 16arha7 newest bios kfcn40ww
CachyOS
I get 3 errors while test and build
New power limit 100 is out of range 65 . 65
New power limit 75 is out of range 65 .65
New power limit 50 is out of range 65.65
Is this known, is there something I can do?
I've been struggling with linux performance on this laptop the gpu is crippled at 65 watts. Any help would be greatly appreciated
The text was updated successfully, but these errors were encountered:
I am not sure how these errors could be generated by the legion kernel module. Please describe when these errors are generated and how you read them. Please also fill out this bug report template:
Problem Description
Has the bug occurred following steps described in the README?
What steps did you take?
What commands did you enter?
What was the (full) error you received and what command or action did lead to it?
Model and Debug Info
Distribution: ??? (including version, e.g. Ubuntu 24.04)
Model name: ???
CPU model: ??? (e.g. AMD Ryzen 7 5800H)
GPU model: ??? (e.g NVIDIA RTX 3700)
Keyboard backlight: ??? (RGB, single color with off/on, single color with off/medium/bright)
Light in lid or logo: ??? (yes/no)
Light at IO-Ports at back: ??? (yes/no)
Output of sudo dmidecode -t system. Please remove Serial Number and UUID for privacy:
???
Output of sudo dmidecode -t bios:
???
Output of sudo cat /sys/kernel/debug/legion/fancurve:
Legion Slim 7 gen 7 16arha7 newest bios kfcn40ww
CachyOS
I get 3 errors while test and build
New power limit 100 is out of range 65 . 65
New power limit 75 is out of range 65 .65
New power limit 50 is out of range 65.65
Is this known, is there something I can do?
I've been struggling with linux performance on this laptop the gpu is crippled at 65 watts. Any help would be greatly appreciated
The text was updated successfully, but these errors were encountered: