cross-posted from: https://lemmy.ml/post/53368173

Hello lemmy and Nura :D.

First time being around these parts of the web. I am a MX Linux daily driver and would like to dualboot with Nura on PC. I already exported my pmbootstrap’d split images and installed them to the last 2 partitions of my SSD with Gnome Disks (idk if it counts as flashing, pls view the attached image).

Updating grub with # update-grub seemed to work, it printed pmOS being found at sda7, but trying to boot off that gets stuck. I tried talking to a LLM to solve the issue, and my conclusion is that neither does it know well enough about pmOS/Nura - I rather not waste my time in it’s hallucination, and also the way I try to setup Nura is probably not documented anywhere (or maybe I suck at reading wiki). For short, It has made me aware that os-prober does not know what to do with Nura, and that manually writing Nura to grub configs is the way.

Need a hand with that, please… thanks.

  • INeedMana@piefed.zip
    link
    fedilink
    English
    arrow-up
    1
    ·
    15 days ago

    What does it get stuck on? What are the complaints in the log?

    How do your grub entries look like?

    I see two boot partitions. You want to have them separate and choose on UEFI stage which to boot?

    • Mumuskeh@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      14 days ago
      1. Bellow all my entries there lies:

      • postmarketOS v26 (can’t remember full name)
      • advanced settings for postmarketOS v26
        • postmarketOS v26
        • postmarketOS v26 (yes it’s 2 identical in this menu)

      And again, I will mention that these entries were automatically generated by # update-grub.

      1. Nothing else to the left side of partition 7 & 8 (pmOS boot & root) matters, except EFI, since well it’s the EFI partition. I want to boot pmOS through GRUB. The other boot partition is for my main OS.
      • INeedMana@piefed.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        14 days ago

        Uh, sorry, I meant the actual contents of the grub config (most probably (pmOS boot)/grub.cfg. The one with stuff like vmlinuz and initrd

        To me it looks like there’s some problem with running the init. I’d guess either the partition reference, path or maybe just some empty something. But that’s all I can guess without the contents of the config

        Just for your info - you could be running from shared boot partition. Just make sure one OS doesn’t overwrite the kernel and initramd of the other. It’s not a problem, just a piece of info

        • Mumuskeh@lemmy.mlOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          13 days ago

          Ah, no problem! So there is nothing related to grub at all in pmOS_boot… However the system is boot-able through UEFI entries! I don’t know why I didn’t try that earlier.

          My workstation’s BIOS is all fancy and let’s you add custom entries, but it was easier to use MX’s UEFI manager. I simply added a new entry to pmOS’s BOOTX64.EFI. I still would like to boot it through my GRUB.

          Also thanks for the piece of info and all the interest in helping me so far :)