There is no option amd_pstate.replace in the list of modinfo.
You can check what is the output of sudo modinfo -p amd_pstate that shows only one parameter/option.
shared_mem:enable amd-pstate on processors with shared memory solution (false = disabled (default), true = enabled) (bool)
That means the option replace does not exist in Linux Kernel 5.18.3
And the other option amd_pstate.enable does not exist too.
A post was split to a new topic: Installation von nvidia-utils (515.48.07-2) verletzt Abhängigkeit »nvidia-utils=510.73.05«, benötigt von linux414-nvidia
Workaround at this point is to start program as
MESA_GL_VERSION_OVERRIDE=4.1 blender
I’m getting a loud BEEP from my laptop at the exact moment I click the “restart” button on the restart dialogue window. I’ve never heard a beep like this from the laptop before.
Edit: (also for power off)
same for me on poweroff button.
3 posts were merged into an existing topic: Installation von nvidia-utils (515.48.07-2) verletzt Abhängigkeit »nvidia-utils=510.73.05«, benötigt von linux414-nvidia
My acpi_call DKMS module always shows an install error when I install kernels/headers with MSM but when I install the kernel and headers with the Pamac GUI the module is found and installs properly every time.
That worked, thank you very much 
I’ve tested LTS kernel 5.15.46-1 and 5.10.121-1, both lead to completly unusable VBox guest-systems. At the moment I run kernel 5.18.3-1 and it seems to work.
I have a problem with bt. After the update I can’t connect to my bt-speaker. The error message: “org.bluez.Error.Failed br-connection-profile-unavailable”.
Deleting and adding the device didn’t help with it.
UPD: The problem has solved. Had pulseaudio-modules-bt installed.
Changed it for pulseaudio-bluetooth and all worked well after restart. The source.
Please be careful!
I’ve got heavy F2FS filesystem corruption on 5.18.3 on two of my machines. With 5.18.3 installed, lots of smaller files became inaccessible (it worked OK on both 5.17.9 and 5.18.1 taken from unstable branch).
The error says “the structure needs cleanup”
Fortunately the damage is not permanent and all files are accessible again when kernel is downgraded.
Not all F2FS partitions are affected, but 2 out of 5 are.
Shared Memory is the only thing, which sucks on this driver
Finally updated.
And i have to say, trying to preserve Akonadi’s log file fails spectacularly. So i removed that part from the solutions.
i wonder why this massive fail with akonadi and all the resulting blows haven’t been recognized in advance. that should not happen on a stable branch even if it’s rolling release.
After update I have lock screen freezes on Plasma with AMDGPU. When waking up after some time of inactivity the lock screen is not responsive. I can input my password, which is not showing up on screen, and can login after 10-20 seconds. I downgraded to 5.17 to see if it is kernel related.
Update completed without errors. I had to create the logfile for akonadi, but that worked fine. I had two issues. One seemed to resolve itself but the other one I had to work around.
First tracker-extract-3 slammed my CPU hard. I let it run and it finally stopped, but I think it was rebuilding something. I am running Plasma, but probably have some gtk stuff installed, so not sure what that was.
Latte-dock won’t start normally. It will start from a terminal without errors and will start with alt+f2 - latte-dock. However with auto-start or from the menu it just slams the cpu like tracker was doing.
I cannot reproduce your description using amdgpu and kde plasma 5.24.5, all amd system
The update itself went fine for me, but today I found that trying to launch VMs in VirtualBox while running the new 5.18.3 kernel results in the application hanging with a progress bar for “Starting virtual machine.” I end up doing a hard power reset because the process for VBoxSVC won’t terminate. Removing and reinstalling all the VirtualBox packages through Pamac did not help. Switching back to the 5.15.44 kernel does resolve the issue. I don’t have time to investigate further right now.
Edited to add: To be clear, Manjaro is my host system. I see other comments on the thread about VirtualBox, but it looks like they are talking about Manjaro as a guest system.
The beep might be a result of the systemd upgrade, see this post in the testing branch: