After 2 months of waiting for 6.19 kernel to be released and hoping for my problem to get fixed. After updating to new kernel the same problem still exist. The problem still exist. I really reconsidering to switching on other distro now. I hope you guys could understand me after waiting and giving opensuse a chance. Can anyone help me again plesae!
Sorry to hear the problem is still not solved, not that surprised though.
Yes, would be good to try another distro, that will show if things are OpenSuse specific, based on the topic I would not be surprised other distro’s give the same problem at least if they run >= 6.18.
I think the best chance to get this fixed is through an issue at https://gitlab.freedesktop.org/drm/amd, even better would to see if there is already a similar issue an pile on that.
Can you check your latest logs, do you still see “Permission firmware_load in class system not defined in policy” in it?
I just did an Ubuntu 26pre update on an amdgpu PC to bring kernel from 6.18 to 6.19. It previously worked fine without having linux-firmware-amd-graphics installed, but not any more. Perhaps your amdgpu firmware package needs a catch-up to work with the 6.19 kernel in TW? Is 20260214 installed on yours?
Update: I finally booted on my system normal on latest kernel 6.19.5-1 default. I tried to remove the amdgpu.dc=0 on my kernel boot and my system work. But I only did that temporary. I tried to remove the amdgpu.dc=0 on yast and apply then reboot but the command still on kernel boot how can I remove this command completely on my kernel boot. Anyone?
I know to add some command like:
sudo update-bootloader --add-option amdgpu.dc=0
But I don’t know how to remove it and update the bootloader in right way.
To delete an option:
sudo update-bootloader --del-option amdgpu.dc=0
sudo update-bootloader --config
I celebrate to early… now my both monitor will turns black (for couple minutes of using) for no reason and the second monitor will not be detected and will goes black and after few minutes will turn back on and will be detected.
But atleast this still a progress now I could boot on latest kernel maybe few more update this issue will be fixed. “Crossed my finger and hope won’t take this few months again”