From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
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 :)
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:
"Linux doesn't boot"
Maybe begin with any information at all then if you want this to be helpful to others?
When I restart the computer, the screen remains dark so I have to shut it down. After I select distro it hangs. 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 could be wrong but I feel like I’ve seen
AE_AML_INVALID_RESOURCE_TYPE
Before,
Now take what I say with a grain of salt because in my experience 9 times out of 10 drives not mounting properly stop the system from booting, if you have multiple drives connected to your pc that automatically mount and you’re familiar with your /etc/fstab I would suggest disabling auto-mount to any drive that isn’t your boot drive and try again.
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.
Maybe try adding
acpi=off
Or
acpi=strict
Or
acpi=force
To your kernel parameters
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.
Also try enabling sgx in bios
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?
No, it can just affect the boot record in some cases. This is not that case.
This would be what I was thinking of then, thanks for clarifying.
I have been avoiding a deb upgrade to 12 1 because of this. However you have me wondering if I'm overly paranoid as my installs while on the same bootloader are on different drives
I think it's only Windows that will break things, so you should be good. Also, I think it's only when it's on the same drive, but I'm not sure. That's how mine was that got messed up. I just ended up ditching Windows because I didn't need it anymore though. That's the proper solution.
The plan is to ditch win in the long term. Not quite at that point yet.
I'm not overly fussed about upgrading windows any further for this reason but I do remember seeing deb have a similar solution for the bootloader bug it's addressing with the warning in the release notes it spooked me
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.
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.
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.