-
-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System doesn't boot after disabling intel_pstate #658
Comments
This isn't really an auto-cpufreq issue. But make sure you have the following packages installed using:
|
|
Definitely not normal behavior. Maybe because it's a Huawei laptop. Personally, I didn't even know they made laptops. I would check your bios for any relevant settings. It might just be the firmware |
Let me know if i can be helpful somehow with my device |
You can try running In your bios, look for settings related to dynamic CPU frequency or P-states |
I don't actually know what signs to look for, I'm a newbie on Linux. These are all options in my bios: There is some extra information that might help: |
I have disabled intel_pstate by replacing But now system are so slow on battery. UI lags so much, almost unusable.
|
That means you have enabled intel_pstate
This is likely because of how intel_pstate handles the powersave governor |
Closing the issue due to inactivity. |
Fill out information requested in this template, without doing so issue will be ignored & closed!
Have you tried?
Error
After disabling intel_pstate system doesn't boot, Seems just stuck at showing vendor logo.
After reverting the changes of
/etc/default/grub
it boots normally again:This is my
grub
file:Tried removing
resume=UUID=75014eab-9c4f-4920-a93c-a146720c5adc
, But it's the same.After removing
intel_pstate=disable
and executingupdate-grub
through the recovery-mode system booted system normally.System information:
Device: Huawei Matebook D16 (HUAWEI RLEF-XX)
Add/paste output of:
Also please be descriptive about the issue you're reporting, i.e: what you tried & what's the expected behaviour.
The text was updated successfully, but these errors were encountered: