Having problems trying booting into Pop Os after todays updates.
I was able to boot into an old kernel. I used mainline to update to 6.4.11. Rebooted and was stuck again.
No longer able to boot into old kernel (makes sense)
Refreshed install. Can now boot. Applied all updates. Back to not booting.
Currently back in after another refresh but I won’t be updating.
AMD 5800X3D 32gb Ram AMD 7900
AMD RX7900 systems will be fixed by linux-firmware 20230815, which we will release tomorrow.
thank you
Thanks for this.
I can confirm that this is now fixed. Thanks again.
Can you be more specific about what you mean by it won’t boot? Where or how is the computer getting stuck? How far into the boot sequence?
It gets stuck after post is displayed. After post, it just goes black and then nothing comes through the monitors
Here is a list of all the recent changes from yesterday:
https://github.com/pop-os/repo-release/pull/270
The only thing I can think of is the amd64-microcode update causing issues, though perhaps the linux-firmware could also be a culprit.
Both have updates to AMD CPU and GPUs. Perhaps you can try updating everything but those two components when you have time to mess around.
Thanks for the help. I was thinking the same thing regarding the and microcode. I’ll see if I can hold those packages back from update.
I held back the amd microcode from the update and it worked. Although now it says I’m pop shop update the I have firmware to install, not the microcode.
Anyway, I’m happy I’m back up and running.
Damn im having this same issue. The only way i can get into the GUI is if i add nomodeset to the boot. I have a 7700x CPU and a 7900xt GPU. Anyway to revert the updates or is it just best to refresh from recovery?
Looks like Pop just pushed out linux-firmware
20230815which contains this revert:https://github.com/pop-os/linux-firmware/commit/ae80f1f10609ee6b81f96b98b97aecdb52b5ff5f
It causes some systems to fail to resume from S3 and some systems to fail to boot. Our priority should be making things work with kernels that we can actively support, not EOL kernels. Stable kernels, the LTS kernel, and development kernels all work with the latest firmware.
It seems like this should fix your issue.
deleted by creator
