- Thread Starter
- #26
What am I missing to load the colored logo instead?
screen.textmode=0
splash="/boot/images/freebsd-logo-rev.png"
boot_mute="YES"
screen.textmode=0
splash="/boot/images/freebsd-logo-rev.png"
boot_mute="YES"
seems it only works with mono color image as described hereboot_mute="YES"
splash="/boot/images/freebsd-logo-rev.png"
If it's BIOS the loader BIOS is text only from 14.2 upwards, including stable/13 : https://cgit.freebsd.org/src/commit/?id=4d3b05a8530e
Rich (BB code):src/share/mk/src.opts.mk @@ -129,6 +129,7 @@ __DEFAULT_YES_OPTIONS = \ + LOADER_BIOS_TEXTONLY \ @@ -206,7 +207,6 @@ __DEFAULT_NO_OPTIONS = \ - LOADER_BIOS_TEXTONLY \
I haven't tried it myself, but you could revert the modification, build and install system from source.
To quote from the commit logWhy the graphic daemon disappeared?
Add back GZIP and BZIP2 compression support. Many of the downstream MFC
packaging systems depend on this. This adds back 20k to the size of the
loader.
Make the boot loader text-only by default. This saves 40k in size. Net,
we're 20k smaller. The graphics loader for BIOS is less useful than the
zip functionality: You can still boot w/a text only one it and you can
build a custom one if you really want it. It's also the default we use
for dual console.
TheI already mentioned that the splash is already showing, the problem is that I can't change it.
seems the "splash" parameter is getting ignored
splash="/boot/images/freebsd-logo-rev.png"
so it shows the default white devil.
spash= variable is not supported on legacy BIOS systems. It is only supported under UEFI, as you correctly noted.Seems it was only added to UEFI boot.
![]()
loader: Load a splash screen if "splash" variable is defined · freebsd/freebsd-src@00460cc
Load a splash screen that vt(4) can use if the "splash" env variable is defined. For now only png is supported and decoding is done in loader and not in kernel compared to splash screen s...github.com
rmomota, is your system BIOS or UEFI?
It is BIOS but what difference does it make if it was working on 14.1, note that this problem appeared after upgrade?