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 :)

  • ColdWater@lemmy.ca
    link
    fedilink
    arrow-up
    3
    ·
    2 hours ago

    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.

  • gonzo-rand19@moist.catsweat.com
    link
    fedilink
    arrow-up
    22
    arrow-down
    2
    ·
    7 hours ago

    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.

    • anonvurr@lemmy.zipOP
      link
      fedilink
      English
      arrow-up
      7
      ·
      edit-2
      4 hours ago

      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.

        • anonvurr@lemmy.zipOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 hours ago

          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.

          • Telorand@reddthat.com
            link
            fedilink
            arrow-up
            2
            ·
            1 hour ago

            That link I gave mentioned a Grub setting for ignoring SGX. Maybe try that after updating your BIOS, if that doesn’t work.

      • gonzo-rand19@moist.catsweat.com
        link
        fedilink
        arrow-up
        5
        ·
        3 hours ago

        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.

        • anonvurr@lemmy.zipOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 hours ago

          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.

  • atzanteol@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    47
    arrow-down
    4
    ·
    8 hours ago

    “Linux doesn’t boot”

    Maybe begin with any information at all then if you want this to be helpful to others?

    • anonvurr@lemmy.zipOP
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      2 hours ago

      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)
      
  • golden_zealot@lemmy.ml
    link
    fedilink
    English
    arrow-up
    35
    arrow-down
    1
    ·
    8 hours ago

    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?

    • anonvurr@lemmy.zipOP
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      4 hours ago

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

    • Z3k3@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      ·
      8 hours ago

      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

  • TheGreatSnacku@lemm.ee
    link
    fedilink
    English
    arrow-up
    8
    ·
    8 hours ago

    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.

  • BombOmOm@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    edit-2
    8 hours ago

    What errors do you get on boot? Also, are Windows and Linux on the same drive, or separate?

  • Zexks@lemmy.world
    link
    fedilink
    arrow-up
    6
    arrow-down
    10
    ·
    4 hours ago

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

  • buwho@lemmy.ml
    link
    fedilink
    English
    arrow-up
    2
    ·
    6 hours ago

    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?

  • obbeel@lemmy.eco.br
    link
    fedilink
    arrow-up
    7
    arrow-down
    3
    ·
    8 hours ago

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

    • HelloRoot@lemy.lol
      link
      fedilink
      English
      arrow-up
      13
      arrow-down
      2
      ·
      edit-2
      6 hours ago

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