Thank you @jexposit, but no luck with drm_info
, I have only one screen in both cases, internal laptop screen.
Diff of drm_info
output has some differences for CRTC's and Planes (only on /dev/dri/card1
(in both cases integrated amdgpu
)), and only connector with status connected
is on the same card (amdgpu
), same details :/
It's probably something specific for this hardware I have.
Addition to my previous comment.
it is also visible from the log that nvidia is being used
new mesa
gnome-shell[2253]: Device '/dev/dri/card0' prefers shadow buffer
gnome-shell[2253]: Added device '/dev/dri/card0' (nvidia-drm) using atomic mode setting.
gnome-shell[2253]: Device '/dev/dri/card1' prefers shadow buffer
gnome-shell[2253]: Added device '/dev/dri/card1' (amdgpu) using atomic mode setting.
gnome-shell[2253]: Created gbm renderer for '/dev/dri/card0'
gnome-shell[2253]: Created gbm renderer for '/dev/dri/card1'
gnome-shell[2253]: GPU /dev/dri/card0 selected as primary
old mesa
gnome-shell[2577]: Device '/dev/dri/card0' prefers shadow buffer
gnome-shell[2577]: Added device '/dev/dri/card0' (nvidia-drm) using atomic mode setting.
gnome-shell[2577]: Device '/dev/dri/card1' prefers shadow buffer
gnome-shell[2577]: Added device '/dev/dri/card1' (amdgpu) using atomic mode setting.
gnome-shell[2577]: Created gbm renderer for '/dev/dri/card0'
gnome-shell[2577]: Created gbm renderer for '/dev/dri/card1'
gnome-shell[2577]: GPU /dev/dri/card1 selected primary from builtin panel presence
For me it seems that there is a regression on my hybrid graphics setup, for some reason it picks up nvidia gpu (confirmed by glxinfo64 -B
as well as nvidia-smi
while in bios it was still set to hybrid graphics like before). And everything becomes really slow.
01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1)
35:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev c8)
Maybe there other updates as well with this combination that make it work like that, but if I only downgrade mesa
to
mesa-*:24.3.2-2.fc41.x86_64
everything starts working normally again.
Works ok on two systems. Also noted on one of the systems that panel size changed as @nucleo mentioned (I fixed it manually to default size).
Evolution, Epiphany and Liferea works as expected (all use webkit2gtk3)
Generally works, boots fine, shuts down fine, suspend/resume works, no new "kernel error messages".
gnome-control-center still works in general, Fedora logo is displayed on About page (I guess that's related to this change).
If using a wayland based session is enough for testing then all still works for me.
@perex do you want to push this to stable? (it doesn't get much more feedback) It seems that automatic push was disabled due to first build having issues and our negative karma, but it seems bodhi doesn't reset those options when new build was added and karma was reset. (not sure how it works, not a packager)
Indirectly tested using applications which in the background (via other libraries) use gnutls, no issues with HTTPS connections.
All works ok (intel integrated graphics)
Generally works, no issues on boot/shutdown, suspend2ram works. Also solves issue with intel hd audio and realtek codec. (same issue as @freddyw mentioned.
Quick testing of Epiphany, Liferea and Evolution all seems to work as expected.
Audio/video plays with gstreamer1 based players.
System still works after reboot.
@jexposit yes. I'm following all related issues, Fedora (RH Bugzilla), as well as RPMFusion. It most likely is, even with udev rule to force primary gpu, I also noticed that apps using webkit-gtk are broken, not displaying content of pages... as other mentioned. (but interesting is most things work with forcing my primary gpu, and work well, and fast as before, except webkit-gtk apps like epiphany, liferea (but interesting Evolution works, and renders messages (for which I think it also uses webkit-gtk))
Thank you!