Linux no longer boots after update
-
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 error0.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
-
Doesn’t change anything I said. The whole dream of Linux as a free alternative to the desktop is fucking dead as we all have mostly close sourced computers in our pockets. I’m on a drunken rampage sorry op
Lets build a DIY FOSS phone
-
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 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 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.
-
14 fucking minutes and there's no response? Oh noes.
14 hours now and nothing but flame wars going. You got anything else.
-
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
-
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.
-
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.
-
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!
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
-
-
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!
-
-
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
-
-
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
-
Hmmm. Can you try to give us more logs?
Honestly I'm starting to wonder if you're having hardware issues.
-
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 -
System shared this topic on
