Solved How to change the FreeBSD logo which appears as soon it boots with that of the little devil.

ZioMario

ZioMario

Hello.

I would be happy if someone could put me in the right direction helping me to understand how to change this FreeBSD logo that I see as soon as it boots :

Screenshot_2022-07-24_20-59-54.jpg


with this,which I like much more :
image_widget_w0nk11mh60i71.png
 
After having installed the package "bsd-splash-changer",I've got the following message :

Code: 
Message from bsd-splash-changer-060211:


--

To use the port you need to perform the following steps:


1) Place your image files into /usr/local/share/bsd-splash-changer.

2) Add the following to /etc/rc.conf[.local] to enable it:


   splash_changer_enable="YES"


3) Enable the boot splash screen as described in splash(4) and set the

   following in /boot/loader.conf[.local]:


   bitmap_name="/boot/splash"


Also, be careful if you already have a file "/boot/splash" because it will be

replaced when the script is executed.

my doubts are :

1) Place your image files into /usr/local/share/bsd-splash-changer : which kind of files should I place here ?
2) Which kind of file is splash ? is it the beastie image ?
 
ziomario said:
... how to change this FreeBSD logo that I see as soon as it boots :
Click to expand...
Images at the boot menu can be displayed only in frame buffer. If the system is BIOS, it must support Vesa BIOS Extension (VBE) ( VT(vbefb): ). UEFI firmware does support frame buffer ( VT(efifb): ): dmesg | grep 'VT(' .

From the opening post #1, save beastie in browser on local system, i.e daemon.png, mv daemon.png /boot/images.

Code: 
# cd /boot/lua
# cp gfx-orb.lua gfx-daemon.lua
# sed -i '' 's/freebsd-logo-rev.png/daemon.png/' gfx-daemon.lua

/boot/loader.conf
Code: 
loader_logo="daemon"
Reboot system.

Image of a EFI VirtualBox VM.

daemon-boot-menu.png
 
T-Daemon said:
Images at the boot menu can be displayed only in frame buffer. If the system is BIOS, it must support Vesa BIOS Extension (VBE) ( VT(vbefb): ). UEFI firmware does support frame buffer ( VT(efifb): ): dmesg | grep 'VT(' .

From the opening post #1, save beastie in browser on local system, i.e daemon.png, mv daemon.png /boot/images.

Code: 
# cd /boot/lua
# cp gfx-orb.lua gfx-daemon.lua
# sed -i '' 's/freebsd-logo-rev.png/daemon.png/' gfx-daemon.lua

/etc/loader.conf
Code: 
loader_logo="daemon"
Reboot system.

Image of a EFI VirtualBox VM.

View attachment 14470
Click to expand...

So nice,this is what I want ! Ya know,Beastie is just like me.
 
T-Daemon said:
Images at the boot menu can be displayed only in frame buffer. If the system is BIOS, it must support Vesa BIOS Extension (VBE) ( VT(vbefb): ). UEFI firmware does support frame buffer ( VT(efifb): ): dmesg | grep 'VT(' .

From the opening post #1, save beastie in browser on local system, i.e daemon.png, mv daemon.png /boot/images.

Code: 
# cd /boot/lua
# cp gfx-orb.lua gfx-daemon.lua
# sed -i '' 's/freebsd-logo-rev.png/daemon.png/' gfx-daemon.lua

/boot/loader.conf
Code: 
loader_logo="daemon"
Reboot system.

Image of a EFI VirtualBox VM.

View attachment 14470
Click to expand...

Yes that works, well ... but not completely.

It definitely works for the png file of the beastie as provided by Freebsd. But for other png files it is a bit hit and miss.

I have tried various of my own png files, but they do not work, and the logo reverts to the text logo. I have also tried various png files that I downloaded from the internet. It seems to work with some transparent pngs. I have not worked out the criteria of what works and what does not.

Here are three pngs that do work and you can have next to the boot menu:

q11.png
q14.png
q15.png
 
Geezer said:
Yes that works, well ... but not completely.

It definitely works for the png file of the beastie as provided by Freebsd. But for other png files it is a bit hit and miss.

I have tried various of my own png files, but they do not work, and the logo reverts to the text logo. I have also tried various png files that I downloaded from the internet. It seems to work with some transparent pngs. I have not worked out the criteria of what works and what does not.

Here are three pngs that do work and you can have next to the boot menu:

View attachment 14471 View attachment 14472 View attachment 14473
Click to expand...

can you add one image of Beastie with which it works great ?
 
judd said:
How could I get a screenshot like that, of the boot screen image of FreeBSD installed on real disk ?
Click to expand...
Only with a photo camera or a mobile device with an integrated photo camera, like smartphone, tablet, etc., taking a picture from the monitor screen.


Even if it were possible to take a screenshot of the vt(4) console from the installed system (it's not to my knowledge, neither with system tools or 3rd party programs), at this early stage of the booting process there is no file system mounted, no programs can be executed, only the loader builtin commands are available (loader_simp(8)).


By the way, for those who like eye-candy in the console, we can have splash(4) screen beginning from current stable/14 (stand/common/gfx_fb.c (look for "splash"). Not available in 14.1-RELEASE, but in upcoming 14.2-RELEASE in Dec 2024.

⚙ D45932 loader: Load a splash screen if "splash" variable is defined

reviews.freebsd.org reviews.freebsd.org
 
cracauer@ said:
The ASCII art demon is when you boot via BIOS.

The high resolution pixel demon is when you boot via uEFI.
Click to expand...
It's not accurate to generalize BIOS booted = ASCII art deamon, UEFI = high resolution pixel daemon.

A machine booted via BIOS can display high resolution pixel images with a graphics card supporting VESA BIOS Extensions (VBE).

I have in a BIOS machine a nVIDIA GT 640 GPU, which displays in VBE frame buffer the pixel daemon logo in a screen resolution of 1920x1080.

When VBE is supported, the system boot message will display VT(vbefb): resolution <WidthxHeight> ( check with dmesg | grep 'VT(' ).
 
T-Daemon said:
When VBE is supported, the system boot message will display VT([B]vbefb[/B]): resolution <WidthxHeight> ( check with dmesg | grep 'VT(' ).
Click to expand...
judd when it isn't (after upgrade 14.1 -> 14.2), what can I do?

Code: 
$ dmesg | grep 'VT('
VT(vga): resolution 640x480

Does the /boot/loader,conf need a nudge? Does stuff have to be copied into /boot?
 

Attachments

mro

What is your normal resolution before the upgrade ?

/boot/loader.conf ↓

Code: 
hw.vga.textmode="0"
efi_max_resolution="1920x1080"

Change according to your resolution.
 
ykla said:
The PNG images I tried didn't work. What are the specific requirements for the images?
Click to expand...
I was successful with
Code: 
$ file /boot/images/*.png
/boot/images/beastie-feature-image-240x200.png: PNG image data, 240 x 200, 8-bit/color RGB, non-interlaced
/boot/images/beastie-feature-image.png:         PNG image data, 320 x 200, 8-bit colormap, non-interlaced
/boot/images/daemon-240x200.png:                PNG image data, 210 x 240, 8-bit/color RGBA, non-interlaced
/boot/images/daemon.png:                        PNG image data, 1040 x 650, 8-bit colormap, non-interlaced
/boot/images/freebsd-brand-rev.png:             PNG image data, 375 x 100, 8-bit/color RGBA, non-interlaced
/boot/images/freebsd-brand.png:                 PNG image data, 385 x 100, 8-bit/color RGBA, non-interlaced
/boot/images/freebsd-logo-rev.orig.png:         PNG image data, 240 x 200, 8-bit/color RGBA, non-interlaced
/boot/images/freebsd-logo-rev.png:              symbolic link to daemon-240x200.png
and remember having had issues with palettes.

But then came 14.2 https://forums.freebsd.org/threads/freebsd-14-2-bootsplash-gone.96142/
 
You must log in or register to reply here.
Back
Top