• griefreeze@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    This is what made me switch to Linux full-time. I’m not surprised this is still a thing 10+ years later

  • milicent_bystandr@lemm.ee
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I have in fact never had or seen this problem, and I’m quite bewildered by so many people having it. Do your normal windows updates do it? Or transition between major Windows versions? Or is it just a Win 11 problem?

    I’ve pretty much always used a dual boot Win/Linux laptop, since around Vista, and I’m on 10 now (but only use it for a few games; all important things in Linux).

    • Luccus@feddit.de
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I’m not sure how it is now, but when I was still dual booting I had the same problem until I got a separate drive for Linux instead of just using different partitions of the same drive.

      • Flatfire@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Funny enough, I think the only time I’ve run into bootloader problems on a single drive, it ended up being Linux that broke my Windows boot. Typically Windows leaves my EFI partition well enough alone during updates.

    • FlyingPiisami@sopuli.xyz
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      Usually people have issues with this when they don’t create the partition free space for the linux partition inside windows first

      • milicent_bystandr@lemm.ee
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        1 year ago

        Ah, that could be it. It’s a long time since I used to resize Windows from Linux; now on a new laptop I always (…I think?!) resize from Windows to make space, unless it’s a friend’s laptop with extra D/E/etc partitions I can delete or resize one.

  • lurch (he/him)@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    1 year ago

    I’m a bit offended by Linux beeing in a wheelchair, implying it can’t run, even if one wheel wasn’t stolen 😤

    Instead, it should be 8 legged and run the web 😉

    • ditty@lemm.ee
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      1 year ago

      This just happened to me on my laptop like a week ago. I can still Systemd boot into Pop!_Os so I haven’t looked into fixing it yet.

      • SokathHisEyesOpen@lemmy.ml
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        You just need to boot from a live USB, chroot into the OS, and rebuild the boot sector. Pop has a great document on how to do it. It takes maybe 5 minutes.

        • ditty@lemm.ee
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          Thanks! I assume this is the guide? I’ll have to try this out this weekend. I had looked at this earlier but moved on when it started mentioning grub since I use refind boot loader. Probably the same process nonetheless!

          • SokathHisEyesOpen@lemmy.ml
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            Yup! That’s the one. I think you can just do the grub install and then boot in and run refind. Idk though, I’ve never used refind.

    • Pika@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      1 year ago

      For others who were interested in this like I was.

      Be aware that systems with secure boot enabled are not supported and the author has stated will likely never be supported due to the hassle of getting it signed by a trusted authority.

      not a huge issue but, still an annoyance

      • o11c@programming.dev
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        1 year ago

        To be fair, Secure Boot is actively hostile toward dual-booting in the first place. Worst of all, it might seem to work for a while then suddenly start causing errors sometime later.