rpmbuild for the ryzen_smu kernel module
Activate repo and instal the package: dnf install dkms-ryzen_smu
The following unofficial repositories are provided as-is by owner of this project. Contact the owner directly for bugs or issues (IE: not bugzilla).
* Total number of packages downloaded in the last seven days.
Sorry in advance, I’m not a technically minded person.
Ive been having trouble installing this module. After enabling the repo and entering the command “dnf install dkms-ryzen_smu” the module appears to install, however it does not seem like the module actually was.
I have entered lsmod and dmesg to see if “ryzen_smu” is there and it does not show up.
Also, I am attempting to run this python script: GitHub - svenlange2/Ryzen-5800x3d-linux-undervolting: A Python script to use Ryzen SMU for Linux PBO tunind of 5800x3d CPU. Mostly needed for Ryzen 5800x3d undervolting. (that relies on this module). When I attempt to run it, I get a message that states “the driver doesn’t seem to be loaded”.
I am running fedora 6.3.11-200.fc38.x86_64. Is it that the module file is Fedora 37 that is causing problems?
What commands/outputs would someone need to see to help troubleshoot this?
thanks,
Dancing Queen
Can you please show the status of the moule on dkms side ?
dkms status
After the installtion the module is not active before a reboot.
However you can activate the module without a reboot with:
insmod ryzen_smu.ko
either as root or with sudo
When done, you can check the dmesg log to see if it works:
I did also update the module to the latest version 0.1.5 now.
Hello, thanks for your response!
Here is the output prior to reboot:
Here is output after reboot:
dmesg did not show module. There was extensive output and I was not sure which section (if any) you’d want so did not post.
Looking online, I have tried a few other things, as seen in the picture to no avail:
Again, bad at tech stuff, and thanks for your response!
-Dancing Queen
The error you posted seems to be related to secureboot in general.
A temporary solution would be to boot without secureboot and see if that works.
I will try to see if i can fix this on the package side to sign the module after building
