So I got this weird bug – I updated my Pop_OS install and now Linux doesn’t boot anymore. I should probably boot from USB and fix this. I could figure it out on my own, but maybe it will be good knowledge for people searching on engines so any advice is welcome. Windows still boots properly. Let’s give people some alternatives to reddit :)
If Windows and Linux are installed on the same drive under different partitions, I seem to recall that a Windows update can fuck your Linux partition.
Was there a Windows update recently?
It wasn’t the windows update. It happened after a Linux update.
The picture you posted doesn’t show an error, that’s a screen to select your boot drive. Are you saying you don’t know how to select a boot drive or that when you do select the boot drive, nothing happens? You’re not giving us any information to help you with.
When I restart the computer, the screen remains dark so I have to shut it down. When I select my distro, the screen hangs on that. When I boot from any live USB I get the error
0.083296] x86/cpu: SGX disabled by BIOS. 0.263311] ACPI Error: Aborting method \_SB.PCI0.SPI1.FPNT._CRS due to previous error (AE_AML_INVALID_RESOURCE_TYPE) (20220331/psparse-529) 0.263591] ACPI Error: Method execution failed \_SB.PCI0.SPI1.FPNT._CRS (AE_AML_INVALID_RESOURCE_TYPE) (20220331/uteval-68) 0.264837] ACPI Error: Aborting method \_SB.PCI0.SPI2.FPNT._CRS due to previous error (AE_AML_INVALID_RESOURCE_TYPE) (20220331/psparse-529) 0.265092] ACPI Error: Method execution failed \_SB.PCI0.SPI2.FPNT._CRS (AE_AML_INVALID_RESOURCE_TYPE) (20220331/uteval-68)I have tried different distros, but none work. Interestingly windows still works.
I wonder if it has anything to do with this:
https://askubuntu.com/questions/1418992/sgx-disabled-by-bios-message-on-ubuntu-20-04-booting
I’m not familiar with SGX, but it kinda sounds like a predecessor to Secure Boot? I wonder if that’s preventing some kind of startup.
Yes, I’m thinking that the bios got corrupted somehow and from what I can tell, it doesn’t matter what linux kernel version I try to run. There is no SGX setting in the bios. I will try to update the bios tomorrow (I already tried once and that hung as well) and will update the thread then. Luckily windows still works.
That link I gave mentioned a Grub setting for ignoring SGX. Maybe try that after updating your BIOS, if that doesn’t work.
ACPI errors shouldn’t be an issue, it’s somewhat common to see them. Are you still able to boot from live USB? Are your Linux and Windows installations on the same drive? Sometimes Windows can mess with the boot settings of other OSes and even break a GRUB install.
I have tried to boot from 3 distros and none of them worked, but a windows USB worked perfectly. I’m thinking that it has to do with the bios. No they are not on the same drive.
So I think that there may be a BIOS misconfiguration here somewhere. Try looking at the answers here, maybe one of them will help: https://askubuntu.com/questions/708247/cant-boot-into-ubuntu-in-windows-10-ubuntu-dual-boot
Also try enabling sgx in bios
Have you tried this? https://askubuntu.com/questions/1411354/ubuntu-22-04-acpi-bios-error-bug
You replied to the wrong person.
My common solution to boot issues that lock me out is,
-
Get a USB Live distro (always good to have a backup lying around)
-
Boot into live distro
-
Chroot into the broken distro (Arch wiki has an article on this)
-
Fix any bugs that I can find and/or reinstall the bootloader
-
Test, repeat until the problem has been found and fixed
Hope it helps any newcomers!
Popos also has specific guides for these common errors:
I’d add :
- back up your data
you don’t have to follow a wiki anymore; there are distro’s out there that specialize in repairing broken bootloaders using a point-and-click interface and they’re great if you’re as lazy as i am. lol
This may work in 99% of the cases, but not in my situation since I’ve tried 5 distros and none of them boot. I’m pretty sure there are deeper issues, but they are clearly beyond my level of knowledge.
-
This is common in rolling releases, but Pop OS isn’t a rolling release distro. Maybe a package you installed or something similar?
This is common in rolling releases
- me who has been using the same heckin arch install without any issues for over 7 years:
w a t ???
This is common in rolling releases
Happened to me on Ubuntu with minor kernel updates including regressions lol
Update: I reset the bios and that fixed the issue.
Looking through your response I think you got unlucky updating bad packages causing it to not boot anymore, my advice is to boot Live USB backup your data and reinstall a distro with time shift just to be safe.
thats strange, my boot menu has 2 kernel selections for pop os, the current one and one that is the previous running kernel. if a pop os update breaks my system i can just boot from the other kernel image. which has only happened once in 5 years. but was able to wait for pop to push fixes etc and then dist upgrade.
since you dont seem to have that option, you may need to boot from live usb and investigate further.
when you try to boot into it what happens?
Welcome to the Club!
I had a similar issue around 2 years ago now on POP where my bootloader didn’t even show up in the bios anymore.
If you still have the a USB with the live boot of POP you can use it to recover your files n stuff.
I don’t understand the purpose of this post
I’m not as familiar with Pop OS but it uses systemd boot as bootloader which is pretty simple. As the above commenter mentioned can you give a screenshot of any errors or where the boot hangs? Or if there’s just a black screen let us know. If it’s an early boot issue may need to just boot to live USB media and check the bootloader files and reinstall packages if any files are missing. People more familiar with systemd-boot and Pop OS may have better info.