9
submitted 2 years ago* (last edited 2 years ago) by CannonGoBoom@lemmy.world to c/pop_os@lemmy.world

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

top 11 comments
sorted by: hot top controversial new old
[-] mmstick@lemmy.world 3 points 2 years ago* (last edited 2 years ago)

AMD RX7900 systems will be fixed by linux-firmware 20230815, which we will release tomorrow.

[-] humanenough@lemm.ee 3 points 2 years ago
[-] CannonGoBoom@lemmy.world 1 points 2 years ago

I can confirm that this is now fixed. Thanks again.

[-] CannonGoBoom@lemmy.world 1 points 2 years ago

Thanks for this.

[-] pnutzh4x0r@lemmy.ndlug.org 3 points 2 years ago

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?

[-] CannonGoBoom@lemmy.world 1 points 2 years ago

It gets stuck after post is displayed. After post, it just goes black and then nothing comes through the monitors

[-] pnutzh4x0r@lemmy.ndlug.org 3 points 2 years ago

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.

[-] CannonGoBoom@lemmy.world 2 points 2 years ago

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.

[-] CannonGoBoom@lemmy.world 2 points 2 years ago

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.

[-] david279@lemmy.world 2 points 2 years ago

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?

[-] pnutzh4x0r@lemmy.ndlug.org 3 points 2 years ago

Looks like Pop just pushed out linux-firmware 20230815 which 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.

this post was submitted on 22 Aug 2023
9 points (100.0% liked)

Pop!_OS (Linux)

5612 readers
3 users here now

Pop!_OS is an operating system developed by System76 for STEM and creative professionals who use their computer as a tool to discover and create. Unleash your potential on secure, reliable open source software. Based on your exceptional curiosity, we sense you have a lot of it.

Unleash your potential

Whether this is your first experience with Linux, or your latest adventure, all are welcome to discuss and ask questions about Pop!_OS and COSMIC. Keep the discussions friendly though, and remember to assume good intentions whenever you reply. We're all here because we have a shared love for Linux and open source software.

System76 Logo

Support us by buying System76 hardware for you or your company! Or by donating on the Pop!_OS website through the "Support Pop" button. Pop!_OS and COSMIC are fully funded by System76 hardware sales. All systems are assembled in the USA. With your support, we'll work to push the Linux desktop forward with COSMIC.

Links

Guides

Hardware

Recommended

Community Rules

Follow the Code of Conduct

All posts on pop_os must adhere to the Pop!_OS community Code of Conduct. https://github.com/pop-os/code-of-conduct

Be helpful

Posts to pop_os must be helpful. When responding to a user asking for help, do not provide tongue-in-cheek responses like "RTM" or links to LMGTFY. Linking to direct sources that answer the asker's question is fine, but it's advised to provide some explanation as to how you got to that source.

Critique should be constructive

We within the Pop!_OS community welcome helpful criticism or ideas on ways to improve. However, basic "It's bad" or other simple negative comments don't help anyone fix anything. When voicing a complaint about something, try to point out ways the complaint could be improved or worked around, so that we can make a better product for it.

This rule applies to both Pop!_OS and its projects as well as other products available from third-parties.

Don't post malicious "advice"

It can be funny to joke about malicious commands, however this is not the venue for it. Do not advise users to run commands which will lock up their systems, steal their data, or erase their drive. Examples of this include (but are not limited to) fork bombs, rm, etc.

Posts violating this rule will be removed, even if the post is clearly in jest. Repeated offences may lead to a ban. You may understand that the command isn't serious, but a new user might not.

No personal attacks

Posts making a personal attack on any user will not be tolerated.

No hate speech

Hate speech of any kind will not be tolerated. Any violations will be removed, and are grounds for a ban.

founded 2 years ago
MODERATORS