Boot screen info not properly retained even when set to

English Install/Boot/Login
1

Hello,

I’d like to retain the boot info which shows on the screen when booting and which by default is cleared right before the login prompt appears.

So, according to getty - ArchWiki I executed systemctl edit getty@ which created /etc/systemd/system/getty@.service.d/override.conf drop-in snippet which partly overrides the getty@.service systemd unit and into this snippet I’ve pasted:

[Service]
TTYVTDisallocate=no

This should prevent the boot info be cleared by systemd. Additionaly by default on openSUSE, there’s –noclear option specified to the agetty program in the getty@.service which prevents it to clear the boot screen too.

Yet, my boot screen still get mostly cleared. It retains only 2 last lines of the boot info:
https://imgur.com/RpflR3L

Is it a bug or what else can I do to fully retain the boot screen?

Thank You.

2

Hi
Remove quiet and silent entries from grub kernel command line options via YaST -> bootloader.

I see;

https://forums.opensuse.org/attachment.php?attachmentid=973&stc=1

IMG_1216.JPG

3

This neither works well. More lines of the boot info is retained but still the bottom half of the screen is unused and there’s a big gap in the output:
https://imgur.com/B9FQ1hH

4

Hi
I don’t use plymouth, disable temporarily via the kernel option plymouth.enable=0 plus I run a larger font… can see boot info via journalctl -b which provides much more information of the boot process if needed, plus boot time to multi-user is so quick…

5

plymouth.enable=0 option dit it. Now the boot info is properly retained and the whole screen is utilized, no need for a larger font. Thanks.

6

Hi
Then if not needed would remove the libply* and ply* files , add locks to them and rebuild initrd with mkinitrd to get rid of it completely.

7

With only 15 forum posts, maybe OP doesn’t know how:

sudo zypper rm plymou*
sudo zypper al plymou*
sudo mkinitrd

Or remove and taboo with YaST2, which I think will automatically rebuild the initrd(s) in the process.

I don’t ever allow plymouth to be installed in the first place, and I summarily purge both quiet and splash from Grub. :slight_smile:

8

Hi
And remove grub theme checkbox, since single boot always set time to zero and hide… likewise dracut.conf to get rid of unused modules…

9

Hi Atronach,

Is it really required to keep the boot info on the boot screen? You can only see the last few lines, anyway.

With only 15 forum posts, maybe OP doesn’t know how:

With that said, do you know that the log is not actually cleared resp. deleted?

As root:

journalctl -b

will give you the full info.

Edit:

Join DateSep 2012

Argh, probably yes.:shame:

10

I guess it’s better to have the boot info on screen so you’re aware of potential problems that come up during boot so you can fix them afterwards. I know about journalctl -b, but if there’s a problem and you don’t have the boot output enabled and instead having some splash screen or plymouth enabled and flashing in front of you, you don’t have a reason to execute journalctl -b​ in the first place. Plus it looks cool with all the information scrolling during boot, it reminds me of some movies with hackers and techies showing off with their skillslol!.

11

All that exactly! Plus, it’s not emulating Windows’ hiding activity behind minimalist graphical nonsense (or mousetype). :slight_smile: I haven’t allowed Plymouth or tty1 clearing in many many moons. :slight_smile:

12

Hi
Configure the journal to a tty… :wink: edit /etc/systemd/journald.conf for example;


ForwardToConsole=yes
TTYPath=/dev/tty9
MaxLevelConsole=info

I do have systemd-htop-service as well (tty12)…

13

I just hit the ESC key during boot to see the boot info.

14

Nice!

I do have systemd-htop-service as well (tty12)…

# systemctl list-unit-files | grep htop
#

Please explain how, or point to a howto.

15

Hi
See GitHub - malcolmlewis/systemd-htop-service: This is a systemd service to start htop on a virtual terminal (aka /dev/ttyN).

16

So today I upgraded to Leap 15.3 and the problem reoccurred. My TTY again retains only the last 2 lines of the boot info, like it was at the beginning of this thread.

I’ve checked the TTYVTDisallocate=no line in /etc/systemd/system/getty@.service.d/override.conf is there.
I’ve checked the –noclear option in getty@.service is there.
I’ve checked I don’t have any Plymouth-related packages installed.

What about you? Have you started to experience the problem recently or after upgrade or do you have any ideas how to fix it again?
Thanks.

17

I use the ‘quiet’ kernel parameter. Journal saves the information to /run and moves it to /var:

**i3-4130:~ #** journalctl -b -u systemd-journald.service  
-- Journal begins at Sun 2021-07-11 15:48:41 CEST, ends at Wed 2021-07-14 07:34:51 CEST. -- 
Jul 14 07:19:50 i3-4130 systemd-journald[195]: Journal started 
Jul 14 07:19:50 i3-4130 systemd-journald[195]: Runtime Journal (/run/log/journal/b650d066970b487eaffea649babf596a) is 8.0M, max 313.2M, 305.2M free. 
Jul 14 07:19:52 i3-4130 systemd-journald[195]: Journal stopped 
Jul 14 07:19:53 i3-4130 systemd-journald[493]: Journal started 
Jul 14 07:19:53 i3-4130 systemd-journald[493]: Runtime Journal (/run/log/journal/b650d066970b487eaffea649babf596a) is 8.0M, max 313.2M, 305.2M free. 
Jul 14 07:19:53 i3-4130 systemd[1]: systemd-journald.service: Deactivated successfully. 
Jul 14 07:19:53 i3-4130 systemd-journald[493]: Time spent on flushing to /var/log/journal/b650d066970b487eaffea649babf596a is 42.307ms for 1040 entries. 
Jul 14 07:19:53 i3-4130 systemd-journald[493]: System Journal (/var/log/journal/b650d066970b487eaffea649babf596a) is 48.0M, max 4.0G, 3.9G free. 
**i3-4130:~ #**

Keeping the deltas small works best. The i3-4130 has:

**i3-4130:~ #** systemd-delta  
**[OVERRIDDEN]** /etc/tmpfiles.d/salt.conf → /usr/lib/tmpfiles.d/salt.conf 

--- /usr/lib/tmpfiles.d/salt.conf       2015-10-09 17:34:54.000000000 +0200 
+++ /etc/tmpfiles.d/salt.conf   2021-07-13 18:42:19.382036850 +0200 
@@ -1,5 +1,5 @@ 
 # Type Path                    Mode UID  GID     Age Argument 
-d      /var/run/salt           0750 root salt 
-d      /var/run/salt/master    0750 salt salt 
-d      /var/run/salt/minion    0750 root root 
+d          /run/salt           0750 root salt 
+d          /run/salt/master    0750 salt salt 
+d          /run/salt/minion    0750 root root 
  

**[EQUIVALENT]** /etc/systemd/system/default.target → /usr/lib/systemd/system/default.target 
**[OVERRIDDEN]** /etc/systemd/system/wpa_supplicant@.service → /usr/lib/systemd/system/wpa_supplicant@.service 

--- /usr/lib/systemd/system/wpa_supplicant@.service     2021-05-28 01:57:37.000000000 +0200 
+++ /etc/systemd/system/wpa_supplicant@.service 2021-07-02 18:55:26.731738812 +0200 
@@ -1,12 +1,10 @@ 
 [Unit] 
 Description=WPA Supplicant daemon (interface %i) 
-After=dbus.service network.target 
-Requires=sys-subsystem-net-devices-%I.device 
-After=sys-subsystem-net-devices-%I.device 
+Requires=sys-subsystem-net-devices-%i.device 
+After=sys-subsystem-net-devices-%i.device 
  
 [Service] 
-Type=dbus 
-BusName=fi.w1.wpa_supplicant1 
+Type=simple 
 ExecStart=/usr/sbin/wpa_supplicant -i%i -c /etc/wpa_supplicant/wpa_supplicant.conf -u -t -f /var/log/wpa_supplicant.log 
  
 [Install] 

**[EXTENDED]**   /usr/lib/systemd/system/NetworkManager.service → /usr/lib/systemd/system/NetworkManager.service.d/NetworkManager-ovs.conf 
**[EXTENDED]**   /usr/lib/systemd/system/btrfs-balance.timer → /etc/systemd/system/btrfs-balance.timer.d/schedule.conf 
**[EXTENDED]**   /usr/lib/systemd/system/btrfs-scrub.timer → /etc/systemd/system/btrfs-scrub.timer.d/schedule.conf 
**[EXTENDED]**   /usr/lib/systemd/system/rpc-gssd.service → /usr/lib/systemd/system/rpc-gssd.service.d/options.conf 
**[EXTENDED]**   /usr/lib/systemd/system/rpc-statd-notify.service → /usr/lib/systemd/system/rpc-statd-notify.service.d/options.conf 
**[EXTENDED]**   /usr/lib/systemd/system/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service.d/options.conf 
**[EXTENDED]**   /usr/lib/systemd/system/rpc-svcgssd.service → /usr/lib/systemd/system/rpc-svcgssd.service.d/options.conf 
**[EXTENDED]**   /usr/lib/systemd/system/systemd-logind.service → /usr/lib/systemd/system/systemd-logind.service.d/20-defaults-SUSE.conf 
**[EXTENDED]**   /usr/lib/systemd/system/systemd-sysctl.service → /usr/lib/systemd/system/systemd-sysctl.service.d/50-kernel-uname_r.conf 

12 overridden configuration files found. 
**i3-4130:~ #**
18

Nevermind. There was quiet an extensive system update pending after the upgrade to Leap 15.3. After that it’s all back to normal.

19

I just solved it for good. Till now, it was actually still not working reliably all the time. Half the time after booting, my boot screen would get cleared and also every time when waking up from hibernation. But coincidentally, I found this new thread: https://forums.opensuse.org/showthread.php/558455-Mysterious-new-eth0-line-in-agetty-login-prompt.

It discusses the new addition in Leap 15.3 called issue-generator which auto-generates /etc/issue file which puts some text on the virtual console after booting but before the login prompt. Maybe it’s a bug, but this text generation causes to clear the boot console from time to time.

When deleting the pkg issue-generator or adding –noissue option to agetty in /usr/lib/systemd/system/getty@.service, after restart it finally keeps my boot console from getting cleared no matter whether cold booting, warm booting or waking up from hibernation.

Also, putting TTYVTDisallocate=no to the getty@.service file is not necessary on openSUSE since the distro installs the /usr/lib/systemd/system/getty@tty1.service.d/20-defaults-SUSE.conf drop-in snippet in place with the exact same content.