"Linux doesn't boot"
Maybe begin with any information at all then if you want this to be helpful to others?
this post was submitted on 09 Mar 2025
46 points (94.2% liked)
Linux
51482 readers
273 users here now
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.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
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 :)
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.
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:
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.
I'd add :
- back up your data
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
Maybe try adding
acpi=off
Or
acpi=strict
Or
acpi=force
To your kernel parameters
Good recommendation, but didn't work. I'm quite puzzled by this problem and it's much more difficult than I at first thought. I'm pretty sure it has to do with the bios since the computer doesn't turn off properly and there are many more weird bugs.
Hmmm. Can you try to give us more logs?
Honestly I'm starting to wonder if you're having hardware issues.
I fixed it! A bios reset did the trick.
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
Disconnect the other drive when you do it and you'll be fine.
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
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.
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.
Update: I reset the bios and that fixed the issue.
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.
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 ???
I don't understand the purpose of this post
Lmao typical Linux forum responses. Criticisms for no error message in main post but when given the message everyone goes silent.
14 hours now and nothing but flame wars going. You got anything else.
There are plenty of responses from people trying to help.
If the OP isn't willing to try any steps or provide feedback to the people who offered suggestions that's on them.
On the other hand, you're engaging in exactly the kind of zero effort flame posts that you're also complaining about. It is hypocritical to complain about toxic Linux communities while being part of the toxicity.