On Wed, 9 Sep 2020, Steven A. Falco wrote:
But that doesn't seem to have any effect. After booting, I still see:
# cat /proc/cmdline
BOOT_IMAGE=(hd1,msdos2)/vmlinuz-5.8.0-1.fc33.aarch64
root=UUID=36a097ba-7577-4cc9-977e-df76c6590c48 ro
Where does the kernel get its command line on RPi?
I have an rPi3 and Pinebook. Same place as Intel.
grubby --info=DEFAULT
shows default boot
grubby --info=ALL
to show all kernels
https://fedoramagazine.org/setting-kernel-command-line-arguments-with-fedora-30/
Here is Pinebook:
# grubby --info=DEFAULT
index=0
kernel="/boot/vmlinuz-5.8.6-201.fc32.aarch64"
args="ro"
root="/dev/mapper/pinevg-f32"
initrd="/boot/initramfs-5.8.6-201.fc32.aarch64.img"
title="Fedora (5.8.6-201.fc32.aarch64) 32 (Thirty Two)"
id="8814846c48db47e2bb50c252d4bc0a29-5.8.6-201.fc32.aarch64"
Note that root and args are defaulted to kernelopts in grubenv.
# grub2-editenv list
saved_entry=8814846c48db47e2bb50c252d4bc0a29-5.8.6-201.fc32.aarch64
kernelopts=root=/dev/mapper/pinevg-f32 ro
boot_success=1
boot_indeterminate=0
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
