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 :)
Update: I reset the bios and that fixed the issue.
“Linux doesn’t boot”
Maybe begin with any information at all then if you want this to be helpful to others?
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!
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
-
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.
Have you tried this? https://askubuntu.com/questions/1411354/ubuntu-22-04-acpi-bios-error-bug
You replied to the wrong person.
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.
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 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 ???
They were like
yay -S *-git