You are not logged in.
I am trying to setup my efistub boot to be completely silent. I have managed to do so in the past following the instructions on Arch wiki (https://wiki.archlinux.org/title/silent_boot), yet on a new install I am unable to replicate.
Here is an example of the messages I am getting on boot:
[OK] Finished Load Kernel Module configfs.
[OK] Started Show Plymouth Boot Screen.
[OK] Started Forward Password Requests to Plymouth Directory Watch.
[OK] Reached target Local Encrypted Volumes. [OK] Reached target Path Units.
Activating swap Suap Partition...
Starting File Systen Check on /dev/disk/by-uuid/3887-4DDA... [OK] Activated swap Suap Partition. [OK] Reached target Swaps.
Mounting Temporary Directory /tap... [OK] Mounted Temporary Directory /tmp.
[OK] Finished File Systen Check on /dev/disk/by-uuid/3887-4DDA.
Mounting /boot...
[OK] Listening on Load/Save RF Kill Switch Status /deu/rfkill Watch. [OK] Mounted boot.
[OK] Reached target Local File Systems.
Starting Tell Plymouth To Write Out Runtime Data...
Starting Create Volatile Files and Directories...
[OK] Finished Tell Plymouth To Write Out Runtime Data.
[OK] Created slice Slice /system/systend-backlight.
Starting Load/Save Screen Backlight Brightness of leds: tpacpi::kbd_backlight... Starting Load/Save RF Kill Switch Status...
[OK] Reached target Bluetooth Support. [OK] Started Load/Save RF Kill Switch Status.
[OK] Finished Load/Save Screen Backlight Brightness of leds:tpacpi::kbd_backlight. [OK] Finished Create Volatile Files and Directories.
Starting Record System Boot/Shutdown in UTMP...
[OK] Finished Record System Boot/Shutdown in UTMP.
[OK] Reached target System Initialization.
[OK] Started Refresh existing PGP keys of archlinux-keyring regularly.
[OK] Started Daily verification of password and group files.
[OK] Started Daily Cleanup of Temporary Directories.
[OK] Reached target Timer Units.
[OK] Listening on D-Bus System Message Bus Socket.
[OK] Reached target Socket Units.
[OK] Reached target Basic System.
Starting D-Bus System Message Bus...
Starting Optimus Manager Commands Daemon...
Starting User Login Management... [OK] Started D-Bus Systen Message Bus. Starting Network Manager...This is how my efibootmgr setup looks like:
$ efibootmgr -u
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0003,0000
Boot0000* Arch Linux Fallback HD(1,GPT,f394b693-b593-f545-bcde-e70d42240648,0x800,0x96000)/File(\vmlinuz-linux)root=PARTUUID=78166d67-9747-9b4e-85df-e420f1ac10de resume=PARTUUID=c7bf5d0a-51ea-1441-a38b-9733a46ca96a rw initrd=\initramfs-linux-fallback.img
Boot0001 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0002 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0003* Arch Linux HD(1,GPT,f394b693-b593-f545-bcde-e70d42240648,0x800,0x96000)/File(\vmlinuz-linux)root=PARTUUID=78166d67-9747-9b4e-85df-e420f1ac10de resume=PARTUUID=c7bf5d0a-51ea-1441-a38b-9733a46ca96a rw initrd=\initramfs-linux.img quiet loglevel=3 systemd.show_status=auto rd.udev.log_level=3 nvidia-drm.modeset=1 module_blacklist=iTCO_wdt,iamt_wdt,mei_wdt nowatchdogand this is my mkinitcpio configuration ("sudo mkinitcpio -p linux" has been run after swapping udev hook with systemd):
$ cat /etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES=(usbhid xhci_hcd)
MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=()
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No RAID, lvm2, or encrypted root is needed.
# HOOKS=(base)
#
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS=(base udev autodetect modconf block filesystems fsck)
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS=(base udev modconf block filesystems fsck)
#
## This setup assembles a mdadm array with an encrypted root file system.
## Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices.
# HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck)
#
## This setup loads an lvm2 volume group.
# HOOKS=(base udev modconf block lvm2 filesystems fsck)
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr and fsck hooks.
HOOKS=(systemd autodetect modconf keyboard block filesystems fsck)
# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()
# MODULES_DECOMPRESS
# Decompress kernel modules during initramfs creation.
# Enable to speedup boot process, disable to save RAM
# during early userspace. Switch (yes/no).
#MODULES_DECOMPRESS="yes"According to the wiki
"""
Below are the parameters that you need to pass to your kernel to get a completely clean boot with systemd in your initramfs:
quiet loglevel=3 systemd.show_status=auto rd.udev.log_level=3"""
Any idea of what I could be missing on?
Last edited by jsaxx (2023-06-03 07:16:21)
Offline
well, you shouldn't see anything. you can try these workarounds:
https://wiki.archlinux.org/title/System … /dev/tty12
https://wiki.archlinux.org/title/Plymouth
note you won't see errors on boot at least with the first, you can show the logs with the second option when pressing [esc] during boot.
Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...
Offline
thanks for the pointers!
so killing plymouth using kernel params seems to achieve what I am looking for (https://wiki.archlinux.org/title/Plymou … parameters). I.e. black loading screen with no splash or msg. If anything goes south, I can always load into fallback where plymouth is enabled.
plymouth.enable=0 disablehooks=plymouthNot sure if to mark this one as solved, as this is really more of a workaround and as far as I can see it should have been working with my original setup.
Offline
from https://wiki.archlinux.org/title/Plymou … t_messages:
During boot you can switch to boot messages by pressing the Esc key.
so qou don't need the fallback kernel to see the messages.
I think you can mark it as solved (or as [workaround]
)
Last edited by jl2 (2023-05-31 13:13:09)
Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...
Offline
Ah! Does that work even with Plymouth disabled?
Will be away for a while, so won't be able to check it. In any case marking this one as [workaround], it does what I want in the end ![]()
Thanks for the help!
Offline