Linux no longer boots after update
-
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?
-
"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) -
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
Lmao typical Linux forum responses. Criticisms for no error message in main post but when given the message everyone goes silent.
-
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)try searching up what SGX is
-
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.
-
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.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.
-
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.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.
-
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.
-
Have you tried this? https://askubuntu.com/questions/1411354/ubuntu-22-04-acpi-bios-error-bug
-
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.Also try enabling sgx in bios
-
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
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 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.
-
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.
-
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.
-
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
Kinda why Linux sucks and I barely use desktop pcs anymore they’re literally nerd territory now.
-
Kinda why Linux sucks and I barely use desktop pcs anymore they’re literally nerd territory now.
99% of Linux users don't experience 'random' boot problems. Ever.
-
99% of Linux users don't experience 'random' boot problems. Ever.
Yeah me neither since I barely ever touch a desktop pc it’s not the 90s anymore and most people are on their phones.
-
Yeah me neither since I barely ever touch a desktop pc it’s not the 90s anymore and most people are on their phones.
Good for you, except OP is clearly using a desktop PC.
-
Good for you, except OP is clearly using a desktop PC.
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
-
Yeah me neither since I barely ever touch a desktop pc it’s not the 90s anymore and most people are on their phones.
Yeah me neither since I barely ever touch a desktop pc
I suppose it's not required for your work/education or whatever your occupation happens to be. That's absolutely fine. But this doesn't warrant being dismissive towards those that have a different situation. Most people that work behind a desk are required to do some work on the PC. The same applies to students.
it’s not the 90s anymore
I wouldn't be surprised if PC usage has been much higher this past decade compared to the 90s. Therefore, this comment seems very out of touch.
most people are on their phones.
Nothing wrong with that. But most people can be on their phones AND PC usage can still be a lot more that it was in the 90s. There's no mutual exclusivity at hand. Only if you would gauge how often the PC is used as a device (relative to other computer-like devices) would you see a relative decline for PCs.
