looks more like the default boot line in /boot/grub/grub.cfg
That is because it is
sbctl needs the configuration just as grub needs it configuration - in fact the unified kernel approach here can eliminate grub - and you can use the firmware’s boot override to select between Manjaro Linux and Windows.
I have edited the relevant part to read
I am slow (tungnem) , but in a fresh install of manjaro-kde-24.2.1-minimal-241216-linux612.iso in Virtualbox :
$ grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub > /home/vshare/1.txt
GRUB_CMDLINE_LINUX_DEFAULT='quiet splash resume=UUID=7fa453a4-1817-467d-a3fd-f593aead290a udev.log_priority=3'
but your /etc/kernel/cmdline
says
root=UUID=<uuid> rw quiet splash apparmor=1 security=apparmor udev.log_priority=3
There must be a step that transforms the raw line from /etc/grub/default to what should be in /etc/kernel/cmdline. A tungnem user might be confused.
You use apparmor, but that is not in the default minimal install /boot/grub/grub.cfg.
$ grep 'root=UUID=' /boot/grub/grub.cfg | head -1
linux /boot/vmlinuz-6.12-x86_64 root=UUID=d53bded7-40af-4d57-b8e4-1b8561a1f6e7 rw quiet splash resume=UUID=7fa453a4-1817-467d-a3fd-f593aead290a udev.log_priority=3
Is it enough to remove 'linux /boot/vmlinuz-6.12-x86_64 ’ or must the ‘resume=UUID=…’ part be removed too?
I only hear that word from my wife
What I refer to is a default installation - you should use the version that is used in your /etc/default/grub - the one I refer to is the default for the installation I did - always extract the one used on your system.
So a file /etc/kernel/cmdline
with one line containing
quiet splash resume=UUID=7fa453a4-1817-467d-a3fd-f593aead290a udev.log_priority=3
could be used ?
If that is what is in your current grub command line - then yes
OK, so basically the user should run this as root:
grep 'GRUB_CMDLINE_LINUX_DEFAULT=' /etc/default/grub | sed -e 's/GRUB_CMDLINE_LINUX_DEFAULT=//' -e 's/"//g' > /etc/kernel/cmdline
That looks great
→ I did think about such addition - but you know - what the mind wants is not always what we do
6 posts were split to a new topic: Failing to implement Secure Boot
A post was merged into an existing topic: Failing to implement Secure Boot