Any and all help would be so greatly appreciated. I’ve been battling with my laptop to be able to dual-boot Ubuntu Cinnamon and Windows 10 for about four days now. I’ve probably gone down five or six different rabbit-holes of troubleshooting, GRUB command-line fun, reinstalling and updating the BIOS, trying and failing to deal with VMX and locked NVram. As of now, my system boot-loops and fails to run Windows, but paradoxically I am able to get Ubuntu running, which is what I am using now.

I’ll try to provide as much relevant information here as I can:

  • Device: HP ZBook 17, gen 6
  • Primary OS: Windows 10 Home
  • Linux distro: Ubuntu Cinnamon 23.10
  • Ubuntu location: /dev/sda3
  • grub-install --version = 2.12~rc1-10ubuntu4
  • boot-repair Boot-info summary: https://paste.ubuntu.com/p/rxZ3D5GtpP/
  • I’m more than happy to provide more information as it’s requested.

As of now, I am unable to run Windows through the BIOS. If I run via the dedicated SSD as I normally do, it boot-loops, and if I try to go through any other drives it just tells me I need to install an OS. I am currently able to run Ubuntu, but only by going through the following process:

  1. Startup menu
  2. Boot configuration
  3. Boot from EFI > Ubuntu > shimx64.efi
    • Classy@sh.itjust.worksOP
      0·
      10 months ago

      I appreciate the elegance of your answer but it’s a bit lacking in detail. Are you saying that I should go with the nuclear option when installing Linux and remove the old files? I might just remove my HDD in that case and install Linux into the dedicated SSD.

      • beta_tester@lemmy.ml
        0·
        10 months ago

        Yes. Nuclear everything. Fuck grub.

        No idea who spreads the word of dual booting. I went into that trap as well. I’ve spent so much time on grub. Don’t waste your time. Even if you manage to fix it after hours, you are not better off than before. You will run into the same or another issue again. And you won’t remember what worked did before. Backup your stuff an run.

        Nowadays I use an atomic/immutable system but I wouldn’t do it on a traditional install differently.

        1. Install all packages as flatpak
        2. Server stuff is installed with podman (docker in the past)
        3. Whatever is not available as flatpak is installed via distrobox
        4. Install only base apps to the system itself
        • Classy@sh.itjust.worksOP
          0·
          10 months ago

          Thanks for the no-nonsense reply. I have been smelling a little bit of bullshit with the whole dual boot fiasco here for a bit. VMX not behaving, Windows’ VM utility not behaving, BIOS not behaving, it’s like goddamn if I type a command I wouldn’t mind if it stuck instead of seemingly getting thrown into a black hole.

          Going with your approach, I imagine if I pick a home distro and decide I want to move to another down the line the transition is far easier than this? Even if I am switching from say Ubuntu to Fedora?

          • Caravaggio@feddit.nl
            0·
            10 months ago

            I’ve been happily dualbooting Win10/Mint for years on the very machine I’m writing from. Zero issues with boots, GRUB, no need for flatpaks, both systems work fine, both configs heavily customized.

          • beta_tester@lemmy.ml
            0·
            10 months ago

            If you keep all your personal files in your home directory and stay away from snaps and don’t switch desktop environments, i.e. stay with GNOME or KDE you can switch back and forth as you wish. There are minor “bugs”/issues when switching between DEs but nothing too serious. Best is to have a seperate partition for Home but that’s luxury. Choose one (bigger) distro. If you need to install another distro because a package is only available on that system, just use distrobox instead. Want to check out another distro? Use a vm. Don’t use a nieche distro as a beginner. Use a system that auto updates itself so that you will never interact with the system again.

            • Classy@sh.itjust.worksOP
              0·
              10 months ago

              I’ll have to spend some time backing up and moving some files around but I think this is how I’ll move forward. I think I’ll also find a cracked Win10 image and I’ll keep it on a thumb drive if ever i need to full on run the OS. I use a few proprietary software that universally get the JUST USE FOSS ALTERNATIVES argument from people not in the know.

        • mateomaui@reddthat.comEnglish
          0·
          10 months ago

          Should definitely be mentioned that dual booting isn’t nearly the headache if you have separate drives and don’t try to have the boot loaders in the same partition. I have Win10 and its boot area on one ssd, and two distros of linux sharing the boot partition on the second ssd, and there’s been no issues. But there’s a good chance Windows boot gets screwed if you try to put it all on one disk.