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 :)
You must log in or register to comment.
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/fstabI would suggest disabling auto-mount to any drive that isn’t your boot drive and try again.try searching up what SGX is
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
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
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.
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
Disconnect the other drive when you do it and you’ll be fine.
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?
Lmao typical Linux forum responses. Criticisms for no error message in main post but when given the message everyone goes silent.
14 fucking minutes and there’s no response? Oh noes.
14 hours now and nothing but flame wars going. You got anything else.
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.
