lory995
Members
-
Joined
-
Last visited
Solutions
-
lory995's post in Can't see "Interface Extra" in Network settings + other problems was marked as the answerNo i wasn't using the plugin i was still using the docker container. I just installed the plugin and solved the problem.............. Sorry, didn't know there was a plugin at all.
-
lory995's post in [Solved] Modprobe blacklisting and AMD P-STATE was marked as the answerEDIT 15 August 2024:
Linux Kernel atm is 6.1.x and since amd-pstate is now builtin all this hassle is not necessary anymore ( and doesn't work ).
I'm not sure if you must disable acpi-cpufreq for it to work but i've done it just to be sure ( and didn't want to waste time trying ).
To enable pstate:
Just go to "MAIN" click on the usb where you boot from and in the "Unraid OS" menu ( or whatever you use ) add "amd_pstate=passive" at the end.
Reboot and voilà, jobs done.
If you are from the future on Unraid 7 you shouldn't need any of this, just go in your power menu in settings and choose your flavor there. Everything else should be enabled by default.
Actually i did already enable all of that at the time you wrote here, but i wanted really go through and try this driver so i stopped and started looking around to try and understand really what i was doing. I read a lot of guides on linux kernel modules and how did they work.
And of course, as usually happens when you have some resemblance of understanding of what you are doing, i succeded.
What i did instead is injecting them at boot.
To do that i modified /boot/config/go adding *before everything* except for #!/bin/bash ( so right under it )
modprobe amd_pstate
[....]/emhttp was after the line written above, for example.
Then i created 2 .conf files in /etc/modprobe.d one for blacklisting acpi_cpufreq(1) and one for enabling pstate(2):
(1) i created it with " nano /etc/modprobe.d/acpifreqdisable.conf "
blacklist acpi_cpufreq (2) i created it with "nano /etc/modprobe.d/enableamdpstate.conf"
options amd_pstate shared_mem=1
and left /boot/syslinux/syslinux.cfg as link in my first post.
Now it works.
P.S: @Iker i've got it up an running the 26 or 27th of january and have yet to note any instability whatsoever fortunately. Maybe since you tried them the drivers got updated?