How to install some not-updated splash screens? [Solved]

Discussion in general that pertains to Sabayon Linux - Must Pertain to Sabayon Linux

Moderator: Moderators

Fitzcarraldo
Sagely Hen
Posts: 8200
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom
Contact:

Re: How to install some splash screens that were not updated?

Post by Fitzcarraldo » Thu Sep 25, 2008 2:27

This is driving me nuts! :evil:

I tried creating by hand the file /etc/splash/sabayon/1680x1050.cfg and then ran splash_manager in demo mode to see if the verbose splash screen SL background would appear, but all I got were the following error messages:

Code: Select all

# splash_manager -t sabayon -m v -c demo
/usr/bin/splash_manager: line 190: fbcondecor_ctl: command not found
/usr/bin/splash_manager: line 174: fbcondecor_ctl: command not found
/usr/bin/splash_manager: line 175: fbcondecor_ctl: command not found
/usr/bin/splash_manager: line 176: fbcondecor_ctl: command not found

/usr/bin/splash_manager: line 395: fbcondecor_ctl: command not found
# 
To try and get rid of the "fbcondecor_ctl: command not found" error message I then edited the /etc/portage/package.use file, added the fbcondecor USE flag to media-gfx/splashutils and then did:

Code: Select all

emerge --newuse -1v splashutils
which ran to completion. Then when I ran splash_manager in demo mode again I got:

Code: Select all

# splash_manager -t sabayon -m v -c demo

# 
and nothing happened apart from the extra line feed after a few seconds. I wondered whether my manually created 1680x1050.cfg file was not correct so then I tried to create one automatically using the splash_resize command:

Code: Select all

# splash_resize sabayon 1024x768 1680x1050
Resized config file for theme 'sabayon' for '1680x1050' resolution successfully created.
#
but the last line in the newly created version of 1680x1050.cfg was the same as in the 1024x768.cfg file, namely:

Code: Select all

rect repaint     0    695  1024 768
which, looking at the various .cfg files for different screen resolutions, should not contain those values so I changed it to:

Code: Select all

rect repaint     0    950  1680 1050
Also, splash_resize had changed the values of tx and ty in 1680x1050.cfg whereas all the other .cfg files have tx=38 and ty=38 so I changed those back again.

Here's the resulting 1680x1050.cfg:

Code: Select all

# Copyright 2004-2007 Sabayon Linux
# Distributed under the terms of the GNU General Public License v2
#
# Theme design and graphics by
# Fabio Erculiani <[email protected]>
#

# constants
tx=38
ty=38
text_size=0
text_color=0xffffff00
text_font=Verdana.ttf
bgcolor=0

tw=1560
th=883
#text_x=530
#text_y=690
changes
pic=images/verbose-1680x1050.png
silentpic=images/background-1680x1050.png

# lines
# -> horizontal <starting pixel X - starting pixel Y - ending pixel X - ending pixel Y>
box silent        885 881 1164 916 #FFFFFF55

# progress bar
box silent inter  885 881 885 916 #FFFFFF #FFFFFF #FFFFFF #FFFFFF
box silent        885 881 1159 916 #FFFFFF #FFFFFF #FFFFFF #FFFFFF

rect repaint     0    950  1680 1050
and here's the resulting 1440x900.cfg also created with splash_resize and with the "rect repaint" line and the tx and ty edited by me for the reasons I gave above:

Code: Select all

# Copyright 2004-2007 Sabayon Linux
# Distributed under the terms of the GNU General Public License v2
#
# Theme design and graphics by
# Fabio Erculiani <[email protected]>
#

# constantschanges
tx=38
ty=38
text_size=0
text_color=0xffffff00
text_font=Verdana.ttf
bgcolor=0

tw=1337
th=757
#text_x=530
#text_y=690

pic=images/verbose-1440x900.png
silentpic=images/background-1440x900.png

# lines
# -> horizontal <starting pixel X - starting pixel Y - ending pixel X - ending pixel Y>
box silent        759 755 998 785 #FFFFFF55

# progress bar
box silent inter  759 755 759 785 #FFFFFF #FFFFFF #FFFFFF #FFFFFF
box silent        759 755 994 785 #FFFFFF #FFFFFF #FFFFFF #FFFFFF

rect repaint     0    814  1440 900
When I run splash_manager in demo mode to see the silent splash screen:

Code: Select all

# splash_manager -t sabayon -m s -c demo
I see the SL blue splash screen with the white bar and the "please wait..." as expected, but when I run splash_manger in demo mode to see the verbose splash screen:

Code: Select all

# splash_manager -t sabayon -m v -c demo
nothing happens on screen and, after a few seconds, an extra line feed appears on the Terminal/Konsole window and the root prompt reappears.

Any advice on how to get the verbose splash screen working would be appreciated.

Fitzcarraldo
Sagely Hen
Posts: 8200
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom
Contact:

Re: How to install some splash screens that were not updated?

Post by Fitzcarraldo » Mon Sep 29, 2008 1:10

I have discovered that the background image displayed when I press Alt-F1 (see link below for an example) is not called a 'splash screen', it's called a 'console background'.

http://wiki.sabayonlinux.org/index.php? ... 5boot5.png

I booted the SL 3.5 LiveDVD to compare it with my HDD installation, and I discovered that fbcondecor (Framebuffer Console Decorations kernel patch) is at the 'default' runlevel, so I added it to my HDD installation's 'default' runlevel:

Code: Select all

rc-update add fbcondecor default
I observed that the LiveDVD's file /etc/conf.d/fbcondecor has FBCONDECOR_TTYS="1 2 3 4 5 6", so I uncommented FBCONDECOR_TTYS="1 2 3 4 5 6" in /etc/conf.d/fbcondecor on my HDD.

As the LiveDVD does not have the following files which I had created on my HDD (see my earlier post): /etc/splash/sabayon/1680x1050.cfg, /etc/splash/sabayon/1440x900.cfg, /etc/splash/sabayon/images/background-1680x1050.png, /etc/splash/sabayon/images/verbose-1680x1050.png, /etc/splash/sabayon/images/background-1440x900.png, /etc/splash/sabayon/images/verbose-1440x900.png, I deleted them from my HDD.

I observed that /etc/conf.d/splash on the LiveDVD and my HDD are the same.

I observed that the LiveDVD does not have the file /etc/fb.modes so I deleted the file /etc/fb.modes that I had manually created earlier on my HDD based on a post I had read in the Gentoo forums.

Upon rebooting I now find that the console background still does not appear when I press Alt-F1, but then it does appear later in the boot process. Furthermore, the console background is now visible when I shutdown.

I changed fbcondecor to the boot runlevel to see if the console background would appear as soon as I pressed Alt-F1, but it made no difference (so I've moved it back to the default runlevel).

So, to summarise, I am now in the position that the console background does appear but only late in the boot process, not straight after pressing Alt-F1 as it does for the LiveDVD. Any ideas on how to get the console background to appear as soon as I press Alt-F1 while booting?

sjieke
Technological Hen
Posts: 321
Joined: Thu Mar 01, 2007 10:46
Location: Maldegem, Belgium

Re: How to install some splash screens that were not updated?

Post by sjieke » Mon Sep 29, 2008 9:33

I don't know the details but I remember reading somewhere (a long time ago, so not 100% sure) that if you want it to appear almost immidiately you have to use an initrd file during boot and the splash/console background needs to be in there...

Maybe this gives you a direction to look into.

Fitzcarraldo
Sagely Hen
Posts: 8200
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom
Contact:

Re: How to install some splash screens that were not updated?

Post by Fitzcarraldo » Mon Sep 29, 2008 13:34

Thanks for your reply, sjieke. Yes, after my previous post I had started investigating initrd and initramfs as they are covered in a number of Gentoo Wiki articles and forum threads that I had been reading:

Fbsplash

[SOLVED] fbcondecor - No image during kernel boot

TIP Design your own Framebuffer Splash

My current /boot/grub/grub.conf looks like this:

Code: Select all

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,2)
#          kernel /kernel-genkernel real_root=UUID=6c2e8b37-21cb-4d0f-9ef9-e47598fe1763
#          initrd /initramfs-genkernel
#boot=sda3
default=0
timeout=10
splashimage=(hd0,2)/grub/splash.xpm.gz
password --md5 $1$ÔHv5ýÆ0A$9olWBksDkWtnK8nU15RCk.
#
title=Sabayon Linux x86_64 (2.6.26-sabayon)
	root (hd0,2)
	kernel /kernel-genkernel-x86_64-2.6.26-sabayon  root=/dev/ram0 ramdisk=8192 real_root=UUID=6c2e8b37-21cb-4d0f-9ef9-e47598fe1763  quiet  init=/linuxrc splash=silent,theme:sabayon vga=791 CONSOLE=/dev/tty1 pci=nomsi 
	initrd /initramfs-genkernel-x86_64-2.6.26-sabayon
#
title=Sabayon Linux x86_64 (2.6.25-sabayon-r1)
	root (hd0,2)
	kernel /kernel-genkernel-x86_64-2.6.25-sabayon-r1  root=/dev/ram0 ramdisk=8192 real_root=UUID=6c2e8b37-21cb-4d0f-9ef9-e47598fe1763  quiet  init=/linuxrc splash=silent,theme:sabayon vga=791 CONSOLE=/dev/tty1 pci=nomsi 
	initrd /initramfs-genkernel-x86_64-2.6.25-sabayon-r1
#
title Windows XP
	rootnoverify (hd0,1)
	chainloader +1
Notice that it already contains the line (i.e. not added by me) "initrd /initramfs-genkernel-x86_64-2.6.26-sabayon" to load the file /boot/initramfs-genkernel-x86_64-2.6.26-sabayon which contains, amongst other things, all the splash and console background files:

Code: Select all

localhost boot # zcat /boot/initramfs-genkernel-x86_64-2.6.26-sabayon | cpio --list
.
temp
sys
dev
dev/null
dev/tty1
dev/console
lib64
sbin
var
var/lock
var/lock/dmraid
etc
etc/fstab
proc
usr
usr/sbin
usr/bin
bin
.
init
lib
lib/keymaps
lib/keymaps/22.map
lib/keymaps/jp.map
lib/keymaps/trq.map
lib/keymaps/38.map
lib/keymaps/ua.map
lib/keymaps/39.map
lib/keymaps/il.map
lib/keymaps/19.map
lib/keymaps/fr.map
lib/keymaps/16.map
lib/keymaps/no.map
lib/keymaps/27.map
lib/keymaps/ru.map
lib/keymaps/31.map
lib/keymaps/14.map
lib/keymaps/et.map
lib/keymaps/keymapList
lib/keymaps/17.map
lib/keymaps/gr.map
lib/keymaps/2.map
lib/keymaps/be.map
lib/keymaps/1.map
lib/keymaps/azerty.map
lib/keymaps/br-a.map
lib/keymaps/4.map
lib/keymaps/28.map
lib/keymaps/pl.map
lib/keymaps/lt.map
lib/keymaps/24.map
lib/keymaps/cf.map
lib/keymaps/7.map
lib/keymaps/23.map
lib/keymaps/la.map
lib/keymaps/36.map
lib/keymaps/slovene.map
lib/keymaps/is.map
lib/keymaps/20.map
lib/keymaps/cz.map
lib/keymaps/9.map
lib/keymaps/pt.map
lib/keymaps/29.map
lib/keymaps/sk-z.map
lib/keymaps/35.map
lib/keymaps/it.map
lib/keymaps/21.map
lib/keymaps/8.map
lib/keymaps/croat.map
lib/keymaps/42.map
lib/keymaps/wangbe.map
lib/keymaps/5.map
lib/keymaps/br-l.map
lib/keymaps/18.map
lib/keymaps/hu.map
lib/keymaps/bg.map
lib/keymaps/3.map
lib/keymaps/26.map
lib/keymaps/nl.map
lib/keymaps/us.map
lib/keymaps/41.map
lib/keymaps/ro.map
lib/keymaps/30.map
lib/keymaps/37.map
lib/keymaps/trf.map
lib/keymaps/33.map
lib/keymaps/sg.map
lib/keymaps/mk.map
lib/keymaps/25.map
lib/keymaps/15.map
lib/keymaps/fi.map
lib/keymaps/40.map
lib/keymaps/uk.map
lib/keymaps/34.map
lib/keymaps/sk-y.map
lib/keymaps/es.map
lib/keymaps/13.map
lib/keymaps/de.map
lib/keymaps/10.map
lib/keymaps/6.map
lib/keymaps/by.map
lib/keymaps/dvorak.map
lib/keymaps/12.map
lib/keymaps/32.map
lib/keymaps/se.map
lib/keymaps/11.map
lib/keymaps/dk.map
sbin
sbin/modprobe
sbin/init
etc
etc/initrd.scripts
etc/initrd.defaults
linuxrc
.
bin
bin/udhcpc.scripts
bin/cut
bin/sh
bin/ash
bin/mount
bin/echo
bin/busybox
bin/uname
bin/[
.
lib
lib/modules
lib/modules/2.6.26-sabayon
lib/modules/2.6.26-sabayon/modules.inputmap
lib/modules/2.6.26-sabayon/modules.symbols
lib/modules/2.6.26-sabayon/kernel
lib/modules/2.6.26-sabayon/kernel/drivers
lib/modules/2.6.26-sabayon/kernel/drivers/block
lib/modules/2.6.26-sabayon/kernel/drivers/block/sx8.ko
lib/modules/2.6.26-sabayon/kernel/drivers/usb
lib/modules/2.6.26-sabayon/kernel/drivers/usb/host
lib/modules/2.6.26-sabayon/kernel/drivers/usb/host/ehci-hcd.ko
lib/modules/2.6.26-sabayon/kernel/drivers/usb/host/sl811-hcd.ko
lib/modules/2.6.26-sabayon/kernel/drivers/usb/host/uhci-hcd.ko
lib/modules/2.6.26-sabayon/kernel/drivers/usb/host/ohci-hcd.ko
lib/modules/2.6.26-sabayon/kernel/drivers/pcmcia
lib/modules/2.6.26-sabayon/kernel/drivers/pcmcia/yenta_socket.ko
lib/modules/2.6.26-sabayon/kernel/drivers/pcmcia/rsrc_nonstatic.ko
lib/modules/2.6.26-sabayon/kernel/drivers/pcmcia/pcmcia.ko
lib/modules/2.6.26-sabayon/kernel/drivers/ssb
lib/modules/2.6.26-sabayon/kernel/drivers/ssb/ssb.ko
lib/modules/2.6.26-sabayon/kernel/drivers/scsi
lib/modules/2.6.26-sabayon/kernel/drivers/scsi/scsi_wait_scan.ko
lib/modules/2.6.26-sabayon/kernel/drivers/scsi/fdomain.ko
lib/modules/2.6.26-sabayon/kernel/drivers/scsi/imm.ko
lib/modules/2.6.26-sabayon/kernel/drivers/media
lib/modules/2.6.26-sabayon/kernel/drivers/media/video
lib/modules/2.6.26-sabayon/kernel/drivers/media/video/videobuf-core.ko
lib/modules/2.6.26-sabayon/kernel/drivers/net
lib/modules/2.6.26-sabayon/kernel/drivers/net/tg3.ko
lib/modules/2.6.26-sabayon/kernel/drivers/net/e1000
lib/modules/2.6.26-sabayon/kernel/drivers/net/e1000/e1000.ko
lib/modules/2.6.26-sabayon/kernel/drivers/ata
lib/modules/2.6.26-sabayon/kernel/drivers/ata/pata_pcmcia.ko
lib/modules/2.6.26-sabayon/modules.seriomap
lib/modules/2.6.26-sabayon/modules.alias
lib/modules/2.6.26-sabayon/modules.dep
lib/modules/2.6.26-sabayon/modules.ccwmap
lib/modules/2.6.26-sabayon/modules.ieee1394map
lib/modules/2.6.26-sabayon/modules.usbmap
lib/modules/2.6.26-sabayon/modules.order
lib/modules/2.6.26-sabayon/modules.ofmap
lib/modules/2.6.26-sabayon/modules.pcimap
lib/modules/2.6.26-sabayon/modules.isapnpmap
etc
etc/modules
etc/modules/firewire
etc/modules/usb
etc/modules/pcmcia
etc/modules/pata
etc/modules/evms
etc/modules/mdraid
etc/modules/sata
etc/modules/dmraid
etc/modules/scsi
etc/modules/ataraid
etc/modules/lvm
etc/modules/net
etc/modules/fs
.
root
lib
lib/splash
lib/splash/sys
lib/splash/proc
dev
dev/null
dev/tty0
dev/fb
dev/misc
dev/console
dev/vc
sbin
sbin/fbcondecor_helper
sbin/splash_helper
etc
etc/initrd.splash
etc/splash
etc/splash/sabayon
etc/splash/sabayon/1600x1200.cfg
etc/splash/sabayon/1152x864.cfg
etc/splash/sabayon/1856x1392.cfg
etc/splash/sabayon/640x480.cfg
etc/splash/sabayon/2048x1536.cfg
etc/splash/sabayon/1792x1344.cfg
etc/splash/sabayon/1024x768.cfg
etc/splash/sabayon/1400x1050.cfg
etc/splash/sabayon/1920x1440.cfg
etc/splash/sabayon/800x600.cfg
etc/splash/sabayon/1280x1024.cfg
etc/splash/sabayon/images
etc/splash/sabayon/images/background-800x600.png
etc/splash/sabayon/images/background-1856x1392.png
etc/splash/sabayon/images/verbose-1400x1050.png
etc/splash/sabayon/images/verbose-800x600.png
etc/splash/sabayon/images/verbose-1792x1344.png
etc/splash/sabayon/images/background-1152x864.png
etc/splash/sabayon/images/background-1920x1440.png
etc/splash/sabayon/images/background-1792x1344.png
etc/splash/sabayon/images/verbose-2048x1536.png
etc/splash/sabayon/images/verbose-1920x1440.png
etc/splash/sabayon/images/background-1400x1050.png
etc/splash/sabayon/images/verbose-1600x1200.png
etc/splash/sabayon/images/verbose-640x480.png
etc/splash/sabayon/images/background-1600x1200.png
etc/splash/sabayon/images/background-640x480.png
etc/splash/sabayon/images/verbose-1280x960.png
etc/splash/sabayon/images/background-1280x960.png
etc/splash/sabayon/images/background-1024x768.png
etc/splash/sabayon/images/verbose-1024x768.png
etc/splash/sabayon/images/background-2048x1536.png
etc/splash/sabayon/images/verbose-1856x1392.png
etc/splash/sabayon/images/background-1280x1024.png
etc/splash/sabayon/images/verbose-1280x1024.png
etc/splash/sabayon/images/verbose-1152x864.png
etc/splash/sabayon/Verdana.ttf
etc/splash/sabayon/1280x960.cfg
12274 blocks
localhost boot # 
Now, I wondered whether I needed to rebuild the initramfs file, so I did the following:

Code: Select all

localhost boot # splash_geninitramfs -g /boot/initramfs-genkernel-x86_64-2.6.26-sabayon -v sabayon
o Creating directory structure..
o Copying //sbin/fbcondecor_helper..
o Copying themes..
  - sabayon
o Creating initramfs image..
localhost boot # 
But the problem with that is that it does not contain all the files that the original initramfs file did (it is missing the keymaps and modules, for example):

Code: Select all

localhost boot # zcat /boot/initramfs-genkernel-x86_64-2.6.26-sabayon | cpio --list
.
root
lib
lib/splash
lib/splash/sys
lib/splash/proc
dev
dev/null
dev/tty0
dev/fb
dev/misc
dev/console
dev/vc
sbin
sbin/fbcondecor_helper
sbin/splash_helper
etc
etc/splash
etc/splash/sabayon
etc/splash/sabayon/1600x1200.cfg
etc/splash/sabayon/1152x864.cfg
etc/splash/sabayon/1856x1392.cfg
etc/splash/sabayon/640x480.cfg
etc/splash/sabayon/2048x1536.cfg
etc/splash/sabayon/1792x1344.cfg
etc/splash/sabayon/1024x768.cfg
etc/splash/sabayon/1400x1050.cfg
etc/splash/sabayon/1920x1440.cfg
etc/splash/sabayon/800x600.cfg
etc/splash/sabayon/1280x1024.cfg
etc/splash/sabayon/images
etc/splash/sabayon/images/background-800x600.png
etc/splash/sabayon/images/background-1856x1392.png
etc/splash/sabayon/images/verbose-1400x1050.png
etc/splash/sabayon/images/verbose-800x600.png
etc/splash/sabayon/images/verbose-1792x1344.png
etc/splash/sabayon/images/background-1152x864.png
etc/splash/sabayon/images/background-1920x1440.png
etc/splash/sabayon/images/background-1792x1344.png
etc/splash/sabayon/images/verbose-2048x1536.png
etc/splash/sabayon/images/verbose-1920x1440.png
etc/splash/sabayon/images/background-1400x1050.png
etc/splash/sabayon/images/verbose-1600x1200.png
etc/splash/sabayon/images/verbose-640x480.png
etc/splash/sabayon/images/background-1600x1200.png
etc/splash/sabayon/images/background-640x480.png
etc/splash/sabayon/images/verbose-1280x960.png
etc/splash/sabayon/images/background-1280x960.png
etc/splash/sabayon/images/background-1024x768.png
etc/splash/sabayon/images/verbose-1024x768.png
etc/splash/sabayon/images/background-2048x1536.png
etc/splash/sabayon/images/verbose-1856x1392.png
etc/splash/sabayon/images/background-1280x1024.png
etc/splash/sabayon/images/verbose-1280x1024.png
etc/splash/sabayon/images/verbose-1152x864.png
etc/splash/sabayon/Verdana.ttf
etc/splash/sabayon/1280x960.cfg
6026 blocks
localhost boot # 
and results in a kernel panic if I reboot.

So my question is, how do I create a new initramfs file that contains all the same stuff as the original?

By the way, lxnay suggested that I change "splash=silent,theme:sabayon" to "splash=verbose,theme:sabayon" in my /boot/grub/grub.conf, but when I tried that the very first message on the console when I reboot is:

Code: Select all

This version of splashutils was compiled without support for fbcondecor.
Verbose mode will not be activated
But, as you can see below (and as I mentioned in a previous post), I had already built splashutils with fbcondecor support:

Code: Select all

# eix splashutils
[I] media-gfx/splashutils
    Available versions:  1.5.3.4 1.5.4.2 {fbcondecor gpm hardened mng png truetype}
    Installed versions:  1.5.4.2(17:12:22 25/09/08)(fbcondecor gpm mng png truetype -hardened)
    Homepage:            http://fbsplash.berlios.de
    Description:         Framebuffer splash utilities.

# 
This is what got me thinking that perhaps I needed to recreate the initramfs file.

Although I'm not sure if rebuilding it will solve the problem, how do I create a new initramfs file that contains all the same stuff as the original? The Gentoo Wiki article Initramfs is beyond me at the moment.

sjieke
Technological Hen
Posts: 321
Joined: Thu Mar 01, 2007 10:46
Location: Maldegem, Belgium

Re: How to install some splash screens that were not updated?

Post by sjieke » Mon Sep 29, 2008 14:51

It is a long time ago (a year or 2) since I played with it. I do remember that the easiest way of getting an initramfs matching your kernel is to use genkernel to create them both. I think the sabayon kernel is also built using genkernel, so maybe looking into genkernel can solve your problem.

Fitzcarraldo
Sagely Hen
Posts: 8200
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom
Contact:

Re: How to install some splash screens that were not updated?

Post by Fitzcarraldo » Mon Sep 29, 2008 15:02

^This must be proof that ESP exists! I had just started looking again at the SL Wiki article on rebuilding my kernel using genkernel, as I had come to the conclusion that I could rebuild /boot/initramfs-genkernel-x86_64-2.6.26-sabayon by rebuilding my kernel, and, as I had rebuilt splashutils with the fbcondecor USE flag, I assumed it would be used in my new initramfs-genkernel-x86_64-2.6.26-sabayon. I'll post here to let you know how it turns out.

sjieke
Technological Hen
Posts: 321
Joined: Thu Mar 01, 2007 10:46
Location: Maldegem, Belgium

Re: How to install some splash screens that were not updated?

Post by sjieke » Mon Sep 29, 2008 15:11

You can use genkernel to only create the initrd also, for example using

Code: Select all

genkernel --splash --no-install --no-clean initrd

Fitzcarraldo
Sagely Hen
Posts: 8200
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom
Contact:

Re: How to install some splash screens that were not updated?

Post by Fitzcarraldo » Mon Sep 29, 2008 18:08

Thanks, sjieke, but I decided to build everything just in case. I followed the SL Wiki article http://wiki.sabayonlinux.org/index.php? ... _genkernel with the addition that I prefixed emerge linux-sabayon with USE="splash grub" (although I don't think that makes any difference, as I had merged the latest x11-themes/sabayonlinux-artwork months ago).

I rebooted (leaving "splash=silent" as it is in /boot/grub/grub.conf) and, lo and behold, when the splash screen appeared and I pressed Alt-F1, there in all its glory, is the SL console background: http://wiki.sabayonlinux.org/index.php? ... 5boot5.png

So, after three months I have finally found the solution to the problem. Basically, I believe the root cause of the problem was that: a) splashutils was not built with the fbcondecor USE flag, AND b) fbcondecor was not in the default runlevel, AND c) FBCONDECOR_TTYS="1 2 3 4 5 6" was commented out in the /etc/conf.d/fbcondecor file, AND d) the initramfs file had not been built with fbcondecor enabled in splashutils. Once all those were fixed then my console background is able to load early during boot as soon as I press Alt-F1.

I'm finally marking this thread as solved.

(Thanks for your posts, sjieke, as they reinforced my line of thinking just at the right time.)

wolfden
Sharecropper
Posts: 9051
Joined: Sat Jan 14, 2006 0:55
Location: Midwest USA
Contact:

Re: How to install some splash screens that were not updated?

Post by wolfden » Wed Oct 01, 2008 4:10

Fitzcarraldo wrote:
So, after three months I have finally found the solution to the problem. Basically, I believe the root cause of the problem was that: a) splashutils was not built with the fbcondecor USE flag, AND b) fbcondecor was not in the default runlevel, AND c) FBCONDECOR_TTYS="1 2 3 4 5 6" was commented out in the /etc/conf.d/fbcondecor file, AND d) the initramfs file had not been built with fbcondecor enabled in splashutils. Once all those were fixed then my console background is able to load early during boot as soon as I press Alt-F1.
So this needs to get changed for next release I take it?

Fitzcarraldo
Sagely Hen
Posts: 8200
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom
Contact:

Re: How to install some not-updated splash screens? [Solved]

Post by Fitzcarraldo » Wed Oct 01, 2008 13:13

wolfden, I have performed rolling updates since I installed SL 3.4f last year, and my installation is bang up-to-date (more so than the SL 3.5 LiveDVD). So, whether I boot from my HDD or from the SL 3.5 LiveDVD, the experience is the same (especially now that I have got the SL-style login prompt back and the verbose boot console background working). However I have never installed SL from the 3.5 LiveDVD so I don't know what the installed SL 3.5 contains, only the SL 3.5 LiveDVD. I assume people who installed SL 3.5 to their HDD are able to see the console background as soon as they press Alt-F1 at boot? If they can, then I assume that splashutils was built with the fbcondecor USE flag, and fbcondecor is in the default runlevel, and FBCONDECOR_TTYS="1 2 3 4 5 6" is not commented out in the /etc/conf.d/fbcondecor file? However, if people start merging/rebuilding packages and the kernel then perhaps the situation would change.

Does the installed SL 3.5 have the fbcondecor USE flag specified for media-gfx/splashutils in the /etc/portage/package.use file? If not, I recommend that Fabio adds it so that, if anyone does do any re-merging, updating or kernel rebuilding then fbcondecor support is not lost inadvertently.

Post Reply