There are 3 sources of messages being printed to the screen:
* The kernel (messages are typically prefixed with a timestamp)
* The systemd init process (messages are typically prefixed with an [ OK ] )
* The getty login session.
The reason you see the internet message is because the network subsystem is not het finished initializing by the time the login session is displayed on the screen. Therefore, the kernel shows the information about the ethernet late in the boot process, displaying it along with the login session's messages.
Here are a few potential solutions:
* Move the login session to a different terminal (e.g. tty2)
* Delay the login session so it only appears after the network subsystem is fully initialized
* Remove console=tty1 from cmdline.txt
* Move the kernel messages to a different terminal (e.g. tty2) while keeping the login session on tty1.
etc.
I suppose you'll just have to decide whether or not to display the messages, where to display them, and/or adjust their timing so they appear more deterministically.
You can also control the type of messages to be displayed from the kernel with the loglevel kernel command line argument
* The kernel (messages are typically prefixed with a timestamp)
* The systemd init process (messages are typically prefixed with an [ OK ] )
* The getty login session.
The reason you see the internet message is because the network subsystem is not het finished initializing by the time the login session is displayed on the screen. Therefore, the kernel shows the information about the ethernet late in the boot process, displaying it along with the login session's messages.
Here are a few potential solutions:
* Move the login session to a different terminal (e.g. tty2)
* Delay the login session so it only appears after the network subsystem is fully initialized
* Remove console=tty1 from cmdline.txt
* Move the kernel messages to a different terminal (e.g. tty2) while keeping the login session on tty1.
etc.
I suppose you'll just have to decide whether or not to display the messages, where to display them, and/or adjust their timing so they appear more deterministically.
You can also control the type of messages to be displayed from the kernel with the loglevel kernel command line argument
Statistics: Posted by JinShil — Tue May 13, 2025 11:18 pm