You are not logged in.
Hi there!
The following warning shows up when mkinitcpio generates my ramdisk and .efi stub
Creating UEFI executable: /boot/EFI/Linux/archlinux-linux.efi
-> Using UEFI stub: /usr/lib/systemd/boot/efi/linuxx64.efi.stub
-> Using kernel image: /lib/modules/5.15.6-arch2-1/vmlinuz
==> WARNING: Note: /etc/kernel/cmdline does not exist and --cmdline is unset!
==> WARNING: Reusing current kernel cmdline from /proc/cmdline
-> Using cmdline file: /proc/cmdline
-> Using os-release file: /etc/os-release
-> Using splash image: /usr/share/systemd/bootctl/splash-arch.bmp
-> Using microcode image: /boot/intel-ucode.img
==> UEFI executable generation successfulAs you can see, there's no /etc/kernel/cmdline file present, so mkinitcpio reads from /proc/cmdline.
That's fine for now, as i am already passing my desired kernel parameters using my systemd-boot entry.conf file.
But what happens i.e. during Arch installation,
where i wouldn't want to create a systemd-boot entry file, but only use the mkinitcpio-created .efi stub (which automates the whole procedure)?
How would i set kernel parameters then?
I guess probably by creating the /etc/kernel/cmdline beforehand?
EDIT: and if so, what would be the correct format of the /etc/kernel/cmdline file?
EDIT2: Solved, Info Here
Last edited by Dante777 (2021-12-04 14:21:46)
Offline