-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AMD APU no display on kernels 6.2 and newer #3122
Comments
This this might be related to my issue. Will try rolling back to the latest 5.x kernel. The laptop I have after the recently (talking a few days ago) update to a new kernel has remove the ability to change screen resolutions.. Only one option exists for the built in screen (2560x1600 and I like to change to 1280x800 for various things including playing games) I understand this is probably a kernel upstream issue, but it seems to have caused an issue for my AMD (built in) GPU as well.
|
Okay booted to "old/previous" kernel (hold space bar after bios screen) and now have a list of screen resolutions to choose from:
|
So there is something wrong with the newer kernels and AMDGPUs. For those curious on the older kernel
and the newer kernel:
Why did the modelines change? |
@dx9s I believe you're seeing pop-os/linux#269 which will be fixed by pop-os/linux#276, which will be released a bit later today. |
@dx9s what you are reporting seems to be a different issue. The one I am referring to seems to stem from patch sets in this thread https://lore.kernel.org/amd-gfx/CADnq5_NmnX3mz16NcjBp--Z2Mu=io407Cuj4ShfVOQW=SdaBKA@mail.gmail.com/ in which amd made changes to kfd, and iommu memory handling. For most laptop users it will be seen as an issue where the system won't be able to resume after suspend, if it is able to boot into graphics at all. |
I just ran an update and it installed a new kernel. I was hoping it would fix the issue and it has not. Luckily the kernel update didn't remove the older 6.2.6 kernel so I can still grub -> pick older kernel and get the ability to select more than one video resolution. Not sure where I am supposed to report this issue, here or some place else. Everything is stock.. I fear an update will update to even new 6.4+ and remove the 6.2 kernal and things will be still broken. At least my notes here will help me to get the older kernel version so I can forcefully roll back to older kernel and have a work around for a while.. I've seen this problem (xrandr only display ONE modeiline for attached monitor) only once before on a System76 machine (still not fixed there either, years ago) and the display properties will ONLY show resolution options based on what xrandr shows. This laptop I own forces 4K video on the 4K laptop display, no way to select other resolutions other than using Xrandr to force GPU to scale from command like or the nvidia drivers to hack a way around it. Scaling just the fonts is a workaround that doesn't solve everything there. But with this computer w/ amdgpu, I know this worked (past tense) and it was a recent kernel update that broke it. |
@dx9s I linked to the issue tracking the bug you're seeing, so posting there would be more appropriate since this thread is not about the same thing. As an update, the 6.4.11 kernel (with the fix, as I mentioned) couldn't be released because of a different bug. The 6.4.6 update you saw was just a small update to fix that bug. Since it wasn't a new version, it didn't replace the oldkern version, as you observed. The next update, which I believe will be 6.5.4 also has the fix. |
Distribution (run
cat /etc/os-release
):PRETTY_NAME="Pop!_OS 22.04 LTS"
Related Application and/or Package Version (run
apt policy $PACKAGE NAME
):linux-image-generic
linux-modules-*-generic
Issue/Bug Description:
Pop-OS! with kernel 6.2 and newer do not initialize display consistently on AMD APUs and do not generate signal. Tested Athlon 3000g, Ryzen 5600g, both HDMI and DP. Asrock x300 deskmini and Asrock x300 deskmeet, with various bios & agesa versions.
Reddit comments indicate 2400g may also be affected, and kernel mail-list also indicates laptops with amd apus affected in other ways.
kernel requires the argument
amdgpu.ignore_crat=1
for proper display initialization. Other arguments (e.g. iommu modes and kfd settings) will also help initialize the display, but would have issues on standby, hibernation, virtualization ability or security.Steps to reproduce (if you know):
Install Pop-OS! on AMD APU system with default settings, boot
Expected behavior:
Display initializes properly (e.g. into text console as safe mode, or the installer detects the need for the parameter and adds it to the kernel command line in a manner that persists though kernel package updates/upgrades)
Other Notes:
Arguably AMD broke the amdgpu and related drivers in 6.2 and they "fixed" it in 6.3. However even kernel 6.4.6 on Pop-OS! exhibits the behavior and requires the parameter added to the kernel command line (which is not an easy thing to do persistently though upgrades with Pop-OS!). It looks like AMD has acknowledged that further fixes are needed and they are prepping them for 6.5
The text was updated successfully, but these errors were encountered: