Persistent FreeBSD boot splash screen instead of console messages

M

Matthew45

Hello everyone,

I would like to suggest a small visual improvement to the FreeBSD boot process, particularly for desktop users.
I'm currently running FreeBSD 15.1-RELEASE with KDE Plasma, NVIDIA graphics and UEFI boot.

During startup, FreeBSD displays the boot logo initially, but then switches to a text console showing system initialization messages before reaching the graphical login screen.
Would it be possible for FreeBSD to display its logo throughout the entire boot process, until the desktop login manager appears?

Ideally, users could choose between two modes:

1. Graphical boot: Display the FreeBSD logo throughout startup.
2. Verbose boot: Display the traditional console messages for troubleshooting.

It would also be useful to have a keyboard shortcut to switch between these modes during startup.

I understand that the console output is extremely valuable for diagnosing boot problems, and I am not suggesting removing it.
I simply think an optional persistent boot splash would make FreeBSD feel more polished as a desktop operating system.

FreeBSD has been an excellent desktop experience for me, and I believe this would be a nice improvement.
What do you think? Is anything like this being considered for future FreeBSD releases?
 
Matthew45 said:
Hello everyone,

I would like to suggest a small visual improvement to the FreeBSD boot process, particularly for desktop users.
I'm currently running FreeBSD 15.1-RELEASE with KDE Plasma, NVIDIA graphics and UEFI boot.

During startup, FreeBSD displays the boot logo initially, but then switches to a text console showing system initialization messages before reaching the graphical login screen.
Would it be possible for FreeBSD to display its logo throughout the entire boot process, until the desktop login manager appears?

Ideally, users could choose between two modes:

1. Graphical boot: Display the FreeBSD logo throughout startup.
2. Verbose boot: Display the traditional console messages for troubleshooting.

It would also be useful to have a keyboard shortcut to switch between these modes during startup.

I understand that the console output is extremely valuable for diagnosing boot problems, and I am not suggesting removing it.
I simply think an optional persistent boot splash would make FreeBSD feel more polished as a desktop operating system.

FreeBSD has been an excellent desktop experience for me, and I believe this would be a nice improvement.
What do you think? Is anything like this being considered for future FreeBSD releases?
Click to expand...
Bad idea in base. Base needs to be simple, streamlined, bug-free, and able to run a variety of configurations, including headless ones, and servers that need fast debugging. And small, I don't feel like downloading megabytes of splash screens needlessly.

If someone wants this, put it in a port or package. Maybe add it to a combined meta-port, such as the one for GUI.
 
you dont need to install anything... use a single png file... its provided by default from bsd...

first verify if the image exist:
ls -l /boot/images/freebsd-logo-rev.png

make a copy of your loader:
cp -p /boot/loader.conf /boot/loader.conf.bak

edit the loader:
ee /boot/loader.conf

insert this into your loader.
# FreeBSD Boot Splash
boot_mute="YES"
splash="/boot/images/freebsd-logo-rev.png"

to reduce text in the startup:
sysrc rc_startmsgs="NO"
sysrc rc_info="NO"

and this is the basics without break anything.

enjoy.
 
Not exactly persistent splash screen up to the SDDM display manager, there is a gap of empty screen and a few lines of text on this setup of a VirtualBox VM.

silent_boot.gif


Configuration:

The 'sddm' message can be silenced, commenting out the echo line in /usr/local/etc/rc.d/sddm.

It's possible to disguise all visible console text, but it's not recommended. You lose virtual console visibility when changing from Xorg to console.

/boot/loader.conf
Code: 
boot_mute="YES"

# set white console text color to black during the boot process
kern.vt.color.7.rgb="0,0,0"

/etc/rc.conf
Code: 
# To silence 'background file system check' message, background_fsck can safely disabled on Root-on-ZFS.

background_fsck="NO"

# Reverse black console text color to white after system boot.
# For available colors (except white), execute 'vidcontrol show' in virtual console.

allscreens_flags="lightwhite"
Skip allscreens_flags configuration if the few lines of console text is still bothering you. In case Xorg doesn't come up, for repairs, you need to blind enter user name and password and execute 'vidcontrol <color>', or ssh-in from another machine (can be from a smartphone/tablet app, 'termux' for example).
 
Never used it. What makes it disappear before the kernel boot output? I think that should be moved forward in the boot process.
Something switches it off. The kernel itself?
 
Re-branding and ricing will be difficult until morale and donations improve.

Also vermaden did blogpost about sending boot screen messages to null, essentially.

I have one use for all this - to confuse the hell out of pentesters with Windows 95 boot screen.
 
T-Daemon said:
Not exactly persistent splash screen up to the SDDM display manager, there is a gap of empty screen and a few lines of text on this setup of a VirtualBox VM.

View attachment 27738

Configuration:

The 'sddm' message can be silenced, commenting out the echo line in /usr/local/etc/rc.d/sddm.

It's possible to disguise all visible console text, but it's not recommended. You lose virtual console visibility when changing from Xorg to console.

/boot/loader.conf
Code: 
boot_mute="YES"

# set white console text color to black during the boot process
kern.vt.color.7.rgb="0,0,0"

/etc/rc.conf
Code: 
# To silence 'background file system check' message, background_fsck can safely disabled on Root-on-ZFS.

background_fsck="NO"

# Reverse black console text color to white after system boot.
# For available colors (except white), execute 'vidcontrol show' in virtual console.

allscreens_flags="lightwhite"
Skip allscreens_flags configuration if the few lines of console text is still bothering you. In case Xorg doesn't come up, for repairs, you need to blind enter user name and password and execute 'vidcontrol <color>', or ssh-in from another machine (can be from a smartphone/tablet app, 'termux' for example).
Click to expand...
It looks nice, little detail but somehow it looks more complete:D I know you dont see a console and all the things going on while booting but, it would be nice to have both boot option with dedicated keyboard shortcut.
 
You must log in or register to reply here.
Back
Top