The last update to dom0 included in kernel-latest the 6.17.9-1 version of the kernel. But it does not boot on my Framework 13 AMD 7840U, getting hung up after printing some messages about the VGA BIOS.
The previous kernel, 6.15.10-1 boots properly.
Some reports online say that 6.17 boots on this type of computer with no problems on other Linux distributions. I wonder if anyone else has seen this.
I have also seen this problem, but with a Framework 16 when booting 6.17.9-1. Processor is also AMD Ryzen 7 7840HS. The computer “boots” to a blank screen. Nothing about VGA. I have a feeling the root problem is the same though.
Most probably. Quoting Alexander Hansen Færøy from Mastodon:
I’ve been using Qubes 4.3 in the RC phase on my Framework 13 laptop. I usually go with kernel-latest, but started seeing a bootup freeze right after the amdgpu driver was initialized. I solved this by manually blocking the amdxdna driver from loading. You can do this either with the module_blacklist kernel argument or via /etc/modprobe.d/ and re-generating your grub environment with grub2-mkconfig.
@pablob@pypy@random1 if any of you tries ahf’s solutions and it works for you, I appreciate if you could provide feedback. So the appropriate measures could be taken.
I can confirm that blacklisting amdxdna by adding module_blacklist=amdxdna to grub_cmdline_linux works. Without it when trying to boot the latest kernel, the boot process goes no further that the prompt for the luks password.
Thank you very much for the feedback. A patch for this issue was merged two days ago. And new prebuilt kernel-latest which was uploaded 7 hours ago should also fix it. After updating the kernel, you should not need that workaround anymore and you may revert it.
Just one more point. The kernel which has the patch is 6.18.1. It is currently in testing repository. Should take few days for it to land in stable repositories:
Is this the same or related bug (with similar solution) ? Because it shares xdna but is not an issue that happens at luks unlock but randomly after running for hours
I can’t answer that. My machine exhibits the on-boot black screen unless I use the module blacklist, and I haven’t seen the random lockups you describe at all.