8
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 30 Sep 2026
8 points (100.0% liked)
Nura
132 readers
8 users here now
Nura - The Linux distribution for mobile devices and beyond. π§ π± π©βπ»
Rules:
- Be nice, follow CoC
- Donβt ask for device ports, consider DIY
- Report bugs in the issue tracker (not here! π)
See also:
founded 1 month ago
MODERATORS
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.