You are not logged in.
I am using systemd-boot with unified kernel image /boot/EFI/Linux/archlinux.efi,
created by mkinitcpio preset:
ALL_config="/etc/mkinitcpio.conf"
ALL_kver="/boot/vmlinuz-linux"
ALL_microcode=(/boot/amd-ucode.img)
PRESETS=('default')
default_image="/boot/initramfs-linux.img"
default_efi_image="/boot/EFI/Linux/archlinux.efi"
default_options="--splash /usr/share/systemd/bootctl/splash-arch.bmp"
After systemd update to 252.1 when I boot this image I get this in journal:
root@lnb ~ $ journalctl -b
lis 11 19:56:09 lnb kernel: Linux version 6.0.8-arch1-1 (linux@archlinux) (gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39.0) #1 SMP P>
lis 11 19:56:09 lnb kernel: [500B blob data]
lis 11 19:56:09 lnb kernel: [Firmware Info]: CPU: Re-enabling disabled Topology Extensions Support.
(blob data instead of kernel parameters)
I did check:
jp@lnb ~ $ cat /proc/cmdline
root=LABEL=ARCHFS tsc=unstable trace_clock=local rw 8250.nr_uarts=1 loglevel=3 m~o}V9}߿?{^7_oo~wϯߚmZۿ-)k_~o?zwۼow7vb{=?|m{3~_o~^߿~}?~ǿϯ[?o_}<W{?߽~{w}?omO?~?~'w{mw?o_?wo~W~_3y?}}owdž?o?ߟ}o?~}?}_oSmw߭_ww{ߍy㿛ϧ;}]o{稷ww_{?7˟Oſws??~?e?{_ۿϵvߞ_^o_}8m{??;^wSןooz?\}d?o>۪___z?|:].~ݻ/o~ݾ͗+}}~uw?gUO{{o[}~wu]_
When I boot "standard" way, using arch.conf:
root@lnb ~ $ cat /boot/loader/entries/arch1.conf
title Arch Linux
version manual entry
linux /vmlinuz-linux
initrd /amd-ucode.img
initrd /initramfs-linux.img
options root=LABEL=ARCHFS notsc rw 8250.nr_uarts=1 fsck.mode=force fsck.repair=yes loglevel=3
it boots without errors
root@lnb ~ $ journalctl -b -1
lis 11 19:54:09 lnb kernel: Linux version 6.0.8-arch1-1 (linux@archlinux) (gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39.0) #1 SMP PREEMPT_DYNAMIC Thu, 10 Nov 2022 21:14:24 +0000
lis 11 19:54:09 lnb kernel: Command line: initrd=\amd-ucode.img initrd=\initramfs-linux.img root=LABEL=ARCHFS notsc rw 8250.nr_uarts=1 fsck.mode=force fsck.repair=yes loglevel=3
lis 11 19:54:09 lnb kernel: [Firmware Info]: CPU: Re-enabling disabled Topology Extensions Support.
Is this upstream bug or is it bug in mkinitcpio?
Edit: image creation
jp@lnb /etc/kernel $ sudo mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -U /boot/EFI/Linux/archlinux.efi -g /boot/initramfs-linux.img --splash /usr/share/systemd/bootctl/splash-arch.bmp --microcode /boot/amd-ucode.img
==> Starting build: 6.0.8-arch1-1
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Creating UEFI executable: /boot/EFI/Linux/archlinux.efi
-> Using UEFI stub: /usr/lib/systemd/boot/efi/linuxx64.efi.stub
-> Using kernel image: /lib/modules/6.0.8-arch1-1/vmlinuz
-> Using cmdline file: /etc/kernel/cmdline
-> Using os-release file: /etc/os-release
-> Using splash image: /usr/share/systemd/bootctl/splash-arch.bmp
-> Using microcode image: /boot/amd-ucode.img
==> UEFI executable generation successful
Edit2: If unified image created manually, commandline looks ok
https://wiki.archlinux.org/title/Unifie … e#Manually
Edit3: If unified image created with sbctl, commandline looks ok
https://wiki.archlinux.org/title/Unifie … mage#sbctl
... so problem is in mkinitcpio (I think)
Last edited by GeorgeJP (2022-11-28 15:37:07)
Offline
I get this in journal:
jp@lnb ~ $ cat /proc/cmdline
I'm assuming that is from the journal and not from /proc/cmdline? Whichever it is, what does the other one say?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Offline
GeorgeJP wrote:I get this in journal:
jp@lnb ~ $ cat /proc/cmdline
I'm assuming that is from the journal and not from /proc/cmdline? Whichever it is, what does the other one say?
Sorry, copy paste mistake ... corrected
Thank you
Edit: resolved upstream in systemd 252.2-2
Last edited by GeorgeJP (2022-11-28 15:38:04)
Offline