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-grubseemed 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.
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 :)
Actually, here's the grub menu from MX, where pmOS entry was auto-generated.
EDIT: corrected accidental duplication when pasting the config
Ok, just to confirm I understand correctly:
postmarketOS v26.06 (on /dev/sda7)If all of that is correct, then:
you went with SysV or Systemd?
ahci0,gpt6 6969-ACCEseems weird, thoughWhat are the UUIDs of your partitions?
vmlinuz-lts?initrdfile in sda6?/dev/sda7isn't too earlyfor a test replace
dev/sda7in line 249 with(hd0,gpt7)Ideally it should be partition's UUID like in the earlier entries but without the UUIDs from earlier point I don't know the string to pass to you
insmod ext2after line 242?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:
The photo is exactly all the visible text on screen, and nothing else appears bellow the screen.
There is no
initrdin sda6, but there isvmlinuz-lts. In pmbootstrap I choose the Alpine LTS kernel, and I don't know if that's related tovmlinuz-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.