Linux no longer boots after update

[thegreatsnacku@lemm.ee]

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.

[obbeel@lemmy.eco.br]

This is common in rolling releases, but Pop OS isn't a rolling release distro. Maybe a package you installed or something similar?

[golden_zealot@lemmy.ml]

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?

[z3k3@lemmy.world]

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

[catloaf@lemm.ee]

I don't understand the purpose of this post

[gonzo-rand19@moist.catsweat.com]

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.

[buwho@lemmy.ml]

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?

[helloroot@lemy.lol]

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 ???

[just_another_person@lemmy.world]

No, it can just affect the boot record in some cases. This is not that case.

[Guest]

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.

[Guest]

It wasn't the windows update. It happened after a Linux update.

[Guest]

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)

[zexks@lemmy.world]

Lmao typical Linux forum responses. Criticisms for no error message in main post but when given the message everyone goes silent.

[jumuta@sh.itjust.works]

try searching up what SGX is

[golden_zealot@lemmy.ml]

This would be what I was thinking of then, thanks for clarifying.

[telorand@reddthat.com]

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.

[gonzo-rand19@moist.catsweat.com]

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.

[ikidd@lemmy.world]

14 fucking minutes and there's no response? Oh noes.

[nullpotential@lemmy.dbzer0.com]

Have you tried this? https://askubuntu.com/questions/1411354/ubuntu-22-04-acpi-bios-error-bug

[nullpotential@lemmy.dbzer0.com]

Also try enabling sgx in bios