Created attachment 1860703 [details] dmesg output of working kernel. Created attachment 1860703 [details] dmesg output of working kernel. 1. Please describe the problem: The last 2 kernel upgrades in Fedora 35, kernel-5.16.7-200.fc35.x86_64 and kernel-5.16.5-200.fc35.x86_64, have made my system unable to detect my monitors native resolutions. The kernels prior to this, e.g. kernel-5.15.18-200.fc35.x86_6, detect them just fine. 2. What is the Version-Release number of the kernel: kernel-5.16.7-200.fc35.x86_64 and kernel-5.16.5-200.fc35.x86_64 are not working correctly. 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : 5.15.18-200.fc35.x86_6 works. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: If I log into 5.15.18-200.fc35.x86_6 my resolutions are detected correctly. xrandr output: Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 16384 x 16384 DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 disconnected (normal left inverted right x axis y axis) DisplayPort-2 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 697mm x 392mm 2560x1440 164.96*+ 143.97 + 120.00 99.95 59.95 1920x1200 164.96 1920x1080 120.00 100.00 119.88 60.00 60.00 50.00 59.94 1600x1200 164.96 1680x1050 164.96 1280x1024 164.96 1440x900 164.96 1280x800 164.96 1280x720 60.00 50.00 59.94 1024x768 60.00 800x600 60.32 720x480 60.00 59.94 640x480 60.00 59.94 HDMI-A-0 disconnected (normal left inverted right x axis y axis) If I log into kernel-5.16.7-200.fc35.x86_64 and kernel-5.16.5-200.fc35.x86_64 the highest resolution detected is 1080p @ 60hz. xrandr output: Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 disconnected (normal left inverted right x axis y axis) DisplayPort-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 697mm x 392mm 1920x1080 60.00 60.00* 50.00 59.94 1280x720 60.00 50.00 59.94 1024x768 60.00 800x600 60.32 720x480 60.00 59.94 640x480 60.00 59.94 HDMI-A-0 disconnected (normal left inverted right x axis y axis) 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: The problem occurs with the rawhide kernel 5.17.0-0.rc3.89.fc36.x86_64 6. Are you running any modules that not shipped with directly Fedora's kernel?: Don't think so, can check if provided a command. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Attached working output, not working output, and rawhide not working output.
More information at https://ask.fedoraproject.org/t/fedora-35-kernel-5-16-removes-monitor-resolutions-automatically-detected-in-kernel-5-15/20136/6 which is where I originally raised this. They suggested to raise a bug here as well as with AMD. Have raised a bug there at https://gitlab.freedesktop.org/drm/amd/-/issues/1899
Created attachment 1860707 [details] dmesg output of kernel that isn't working.
Created attachment 1860709 [details] dmesg out of rawhide kernel that isn't working.
I had time to reinstall Fedora using the KDE spin and the kernel that comes with that, 5.14.10-300.fc35.x86_64, is working fine. I upgraded the system and the latest kernel from that update, kernel-5.16.9-200.fc35.x86_64, is still broken with the same issue.
I manually reinstalled 5.15.18-200.fc35.x86_64 and it is working correctly. But any higher kernels are still not working.
It looks like this is possibly an issue with using a KVM. Another user on the AMD bug reported the same behaviour when they used a KVM and it was working without it. Their KVM supports DP 1.4, mine DP 1.2, and apparently kernel 5.16 introduced support for DP 2.
I tested the KVM theory and that seems to be correct. I just manually installed kernel-5.16.1-200.fc35.x86_64 and booted into that with the KVM and the resolution issue I described is there. When removing the KVM and booting to kernel-5.16.1-200.fc35.x86_64 again my resolution is detected correctly, although I have to fix this manually with my autorandr profile. This behaviour is consistent with what the other user on the AMD bug described and the developers over there thought this could be a regression with the EDID being processed through the KVM. I also did the same test with kernel-5.16.9-200.fc35.x86_64 and had the same result. My next steps are going to be to try and do bug bisect ( https://www.kernel.org/doc/html/latest/admin-guide/bug-bisect.html ) between 5.15.18-200 and 5.16.1-200. 5.15.18-200 is when the resolution through the KVM is last working and 5.16.1-200is when the resolution through the KVM isn’t working.
Upgrading to Fedora 36 and using kernel 5.17.6-300.fc36.x86_64 has solved my issue.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.