sorted by: new top controversial old
Advice needed for dualboot x86_64 on an already partitioned drive in c/nura@lemmy.world
Are there any decent sites where you can meet people online? in c/asklemmy@lemmy.ml
Advice needed for dualboot x86_64 on an already partitioned drive in c/nura@lemmy.world
[–] [S] 1 point 1 week ago
    1. and 3. is all correct.

I use systemd mode in MX. In pmOS's entries there is no such choice, unless... the 2 dublicate options in the "advanced options" GRUB entry is actually the dual init format specific to MX? Then we can assume this is an incompatibility on MX Linux's part? I guess I tried booting pmOS in both modes, but I don't see any difference. All the later tests bellow were done on the main pmOS GRUB entry, not in the "advanced options".

The strangely named "6969" UUID is real, sda6's UUID is named like that, and I don't know why.

All UIIDs in order:

  • EFI
    • 13AA-3B2E
  • OTHERS
    • 081de505-7ddd-482a-aff8-9403865510d7
    • 829c2c7a-d475-4692-bc78-d8502ded5d3b and LUKS e1bae6b2-c0b7-47de-bb88-3261cf0c83ba
    • 37e894b4-435c-4156-a923-7cfc27b6705f and LUKS f68c92ec-cade-4686-b467-70f4100c36e0
    • 0ba63eb1-ffa9-466c-ab2a-9b29db2882d2
  • PMOS
    • 6969-ACCE
    • 791e8d35-d7ec-46ed-9b53-a70a8beebe14

The photo is exactly all the visible text on screen, and nothing else appears bellow the screen.

There is no initrd in sda6, but there is vmlinuz-lts. In pmbootstrap I choose the Alpine LTS kernel, and I don't know if that's related to vmlinuz-lts's naming.

(hd0,gpt7) did not fix anything regarding the line 249 edit.

The line 242 edit produced, just bellow the rdinit error: Skipping autodetection of RAID arrays. (raid=autodetect will force). I later then reverted this edit and added sda7's UUID to line 249, replacing (hd0,gpt7), and it produces me same RAID array error.

  • permalink
  • fedilink
  • source
  • parent
  • context
    • Advice needed for dualboot x86_64 on an already partitioned drive in c/nura@lemmy.world
    Advice needed for dualboot x86_64 on an already partitioned drive in c/nura@lemmy.world
    [–] [S] 1 point 1 week ago (3 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • context
    • Advice needed for dualboot x86_64 on an already partitioned drive in c/nura@lemmy.world
    [–] [S] 1 point 1 week ago (5 children)

    2. 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.
  • permalink
  • fedilink
  • source
  • parent
  • context
    • 8
    Advice needed for dualboot x86_64 on an already partitioned drive (thelemmy.club)
     

    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.

    Advice needed for dualboot x86_64 on an already partitioned drive in c/postmarketos@lemmy.world
    4
    Advice needed for dualboot x86_64 on an already partitioned drive (thelemmy.club)
     

    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.

    Final thoughts on my Linux daily driving choice in c/linux@lemmy.ml
    [–] 2 points 1 week ago*

    MX is also solid for older Nvidia cards. The installer tool picks patched drivers for you in case they are needed. This is mostly up to preference, I don't like CachyOS as much as I don't like the rolling release model.

  • permalink
  • fedilink
  • source
    •