Talk:Silent boot

From ArchWiki
Jump to navigation Jump to search

Remove console cursor blinking

The console cursor at boot keeps blinking if you follow these intstructions. This can be solved by passing vt.global_cursor_default=0 to the kernel (source).

--Farsil (talk) 08:50, 23 September 2016 (UTC)

Retaining fsck output

Is there any way to retain the output, to keep a record or a log if fsck does in fact do something drastic? Ordinarily one would > or >> to a file, but are not all filesystems as yet unmounted at this point? quequotion (talk) 15:22, 21 August 2017 (UTC)

You can disable clearing of the console before the login prompt, see getty#Have_boot_messages_stay_on_tty1. -- Lahwaacz (talk) 16:02, 21 August 2017 (UTC)

Started Bpfilter

As of 4.18, "Started Bpfilter" is displayed at boot after following all listed instructions. I am currently unsure of a way to silence. --Bumblebeer (talk) 03:03, 26 August 2018‎ (UTC)

Add more info about i915.fastboot=1

As said here [1](https://www.phoronix.com/scan.php?page=news_item&px=Flicker-Free-Arch-Linux), i915.fastboot=1 now replaces quiet splash vt.global_cursor_default=0 rd.loglevel=0 systemd.show_status=false rd.udev.log-priority=0 udev.log-priority=0, tested on intel ivy bridge and it works well. --Sigmasd (talk) 14:52, 13 December 2018 (UTC)

systemd.show_status=error instead of auto

So reading https://systemd.network/init.html looks like the appropiate value of systemd.show_status to disable succesful messages while displaying error ones is using error, not auto, as auto should behave like false (which is not desirable in this situation) except when some unit is taking too long, then it changes to enable, displaying everything. Also, if you only want to hide the succesful systemd units while displaying error ones and also not changing the default behaviour of the kernel, you should just use systemd.show_status=error while not using quiet or loglevel, so the only addition to the parameters would be systemd.show_status=error. Also, i want to mention that while quiet loglevel=3 rd.systemd.show_status=auto worked for me, only using rd.systemd.show_status=auto did not worked and i had to remove the rd., using only systemd.show_status=auto, i don't know why

—This unsigned comment is by Akrai (talk) 16:54, 31 March 2020‎. Please sign your posts with ~~~~!