Difference between revisions of "Disable clearing of boot messages"

From ArchWiki
Jump to: navigation, search
(Have boot messages stay on tty1: moved to getty)
(update merge target)
Line 6: Line 6:
 
{{Related|Arch boot process}}
 
{{Related|Arch boot process}}
 
{{Related articles end}}
 
{{Related articles end}}
{{Merge|getty|Most information on this page is about modifying the agetty service}}
+
{{Merge|General_troubleshooting#Boot_problems}}
 
After the boot process, the screen is cleared and the login prompt appears, leaving users unable to read init output and error messages. This default behavior may be modified using methods outlined in this article.
 
After the boot process, the screen is cleared and the login prompt appears, leaving users unable to read init output and error messages. This default behavior may be modified using methods outlined in this article.
  

Revision as of 15:41, 22 August 2016

Merge-arrows-2.pngThis article or section is a candidate for merging with General_troubleshooting#Boot_problems.Merge-arrows-2.png

Notes: please use the second argument of the template to provide more detailed indications. (Discuss in Talk:Disable clearing of boot messages#)

After the boot process, the screen is cleared and the login prompt appears, leaving users unable to read init output and error messages. This default behavior may be modified using methods outlined in this article.

Note that regardless of the chosen option, kernel messages can be displayed for inspection after booting by using dmesg or all logs from the current boot with journalctl -b.

Using flow control

This is basic management that applies to most terminal emulators, including virtual consoles (vc):

  • Press Ctrl+S to pause the output
  • And Ctrl+Q to resume it
Note: This pauses not only the output, but also programs which try to print to the terminal, since they'll block on the write() calls for as long as the output is paused. If your init appears frozen, make sure the system console is not paused.