[mailbinoy]

i have just shifted to suse from mandake. i loved the bootsplash configuration utility included with mandrake. I believe there is no such gui for suse. so i tried to install the bootsplash from cmdline.

I downloaded a bootsplash Aqua. extracted it and copied it to /etc/bootsplash/themes/

then i ran this command
splash -s -f /etc/bootsplash/themes/Aqua/config/bootsplash-1024x768.cfg > /boot/initrd.splash
there was a error
syntax error (unknown command): LOGO_CONSOLE=vt
so i edited bootsplash-1024x768.cfg and commented the last line
#LOGO_CONSOLE=vt
after which the splash command ran successfully
and it created a new file /boot/initrd.splash

i updated my lilo.conf as


menu-scheme = Wb:kw:Wb:Wb
default = Suse
timeout = 80
message = /boot/message
lba32
change-rules
reset
read-only
prompt
boot = /dev/hda
#************
#*************
image = /boot/vmlinuz
label = Suse.logo
root = /dev/hda1
initrd = /boot/initrd.splash
append = "resume=/dev/hdb2 selinux=0 splash=silent "
vga = 0x317


now when booting there is a kernel panic. the error message says , it was unable to initialize the ram device and please append a correct "root=" option to kernel. or something like that. (Is this logged in somewhere i can copy and paste?)

The default image boots fine.

[bigtomrodney]

I'm not sure but I would guess you need to rebuild the initrd for the kernel. Check out the mkinitrd help, but I think it is something like

mkinitrd /boot/yourkernel.x.x.x newinitrd.gz

It is a while since I've had to do this, ,maybe a man page visit will help you.

[borromini]

What do you get when you do # /sbin/lilo -V? Lilo will check for (syntax) errors in its config file then.

[mailbinoy]

Originally Posted by bigtomrodney

I'm not sure but I would guess you need to rebuild the initrd for the kernel. Check out the mkinitrd help, but I think it is something like

mkinitrd /boot/yourkernel.x.x.x newinitrd.gz

It is a while since I've had to do this, ,maybe a man page visit will help you.

mkinitrd / rebuilds the new initrd with the suse bootsplash screen. here's the output

********************8
Root device: /dev/hda1 (mounted on / as reiserfs)
Module list: piix reiserfs

Kernel image: /boot/vmlinuz-2.6.11.4-20a-default
Initrd image: /boot/initrd-2.6.11.4-20a-default
Shared libs: lib/ld-2.3.4.so lib/libblkid.so.1.0 lib/libc.so.6 lib/libselinux.so.1 lib/libuuid.so.1.2

Driver modules: kernel/drivers/ide/ide-core.ko kernel/drivers/ide/pci/piix.ko kernel/drivers/ide/ide-disk.ko kernel/drivers/cdrom/cdrom.ko kernel/drivers/ide/ide-cd.ko
Filesystem modules: kernel/fs/reiserfs/reiserfs.ko
Including: klibc initramfs udev fsck.reiserfs
Bootsplash: SuSE (1024x76
5894 blocks

############similar for xen
Run lilo now to update the boot loader configuration.
******************

This will i think restore the suse boot screen. But my obective is to change the boot screen.

I even tried
splash -s -f /etc/bootsplash/themes/Aqua/config/bootsplash-1024x768.cfg >> /boot/initrd-2.6.11.4-20a-default

(used >> instead of > ) but that again gives kernel panic.

[mailbinoy]

Originally Posted by bigtomrodney

I'm not sure but I would guess you need to rebuild the initrd for the kernel. Check out the mkinitrd help, but I think it is something like

mkinitrd /boot/yourkernel.x.x.x newinitrd.gz

It is a while since I've had to do this, ,maybe a man page visit will help you.

mkinitrd / rebuilds the new initrd with the suse bootsplash screen. here's the output

********************8
Root device: /dev/hda1 (mounted on / as reiserfs)
Module list: piix reiserfs

Kernel image: /boot/vmlinuz-2.6.11.4-20a-default
Initrd image: /boot/initrd-2.6.11.4-20a-default
Shared libs: lib/ld-2.3.4.so lib/libblkid.so.1.0 lib/libc.so.6 lib/libselinux.so.1 lib/libuuid.so.1.2

Driver modules: kernel/drivers/ide/ide-core.ko kernel/drivers/ide/pci/piix.ko kernel/drivers/ide/ide-disk.ko kernel/drivers/cdrom/cdrom.ko kernel/drivers/ide/ide-cd.ko
Filesystem modules: kernel/fs/reiserfs/reiserfs.ko
Including: klibc initramfs udev fsck.reiserfs
Bootsplash: SuSE (1024x76
5894 blocks

############similar for xen
Run lilo now to update the boot loader configuration.
******************

This will i think restore the suse boot screen. But my obective is to change the boot screen.

I even tried
splash -s -f /etc/bootsplash/themes/Aqua/config/bootsplash-1024x768.cfg >> /boot/initrd-2.6.11.4-20a-default

(used >> instead of > ) but that again gives kernel panic.

Originally Posted by bborromini

What do you get when you do # /sbin/lilo -V? Lilo will check for (syntax) errors in its config file then.

lilo -V gives
LILO version 22.3.4

[mailbinoy]

did i mention the bootsplash does show up before the kernel panic (chk snapshot at http://vdeckdemo.com/kernel_panic.jpg)

here is the exact message

ACPI wakeup devices:
SPB PCI0 HUB0 USB0 USB2 USBE
ACPI : (supports S0 S1 S4 S5)
md: Autodetecting RAID Arrays
md: autorun
md: ..........autorun DONE
RAMDISK: Compressed image found at block 0
input AT Translated set 2 keyboard on isa0060/serio0
Kernel panic - not syncing : VFS : Unable to mount root fs on unknown block (3,1)


I noticed when i boot with my normal suse initrd(which works) the message shows

ACPI wakeup devices:
SLPB PCI0 HUB0 USB0 USB1 USB2 USBE
ACPI: (supports S0 S1 S4 S5)
Freeing unused kernel memory: 204k freed
input: AT Translated Set 2 keyboard on isa0060/serio0
logips2pp: Detected unknown logitech mouse model 85
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH4: IDE controller at PCI slot 0000:00:1f.1
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI interrupt 0000:00:1f.1[A] -> GSI 11 (level, low) -> IRQ 11
ICH4: chipset revision 2
ICH4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hdaMA, hdbMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdcMA, hddMA
Probing IDE interface ide0...
hda: ST380011A, ATA DISK drive

##############whole lot of other mesages related to hdd and cdrom

ReiserFS: hda1: checking transaction log (hda1)
ReiserFS: hda1: Using r5 hash to sort names
bootsplash: status on console 0 changed to on
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com


does this mean my hdd and cdrom are not intialised by initrd ?
isnt there a GUI tool (like the one mandrkake provides) to make it simpler?

[mailbinoy]

OK i figured this one out (thanks to biophysics of LQ). Here's a quick tutor for newbies:

Put your theme in appropriate place: /etc/bootsplash/themes/mytheme
for e.g.
/etc/bootsplash/themes/Aqua
edit the file: /etc/sysconfig/bootsplash
change the line Theme to <your_theme_name>
for e.g.
Theme= Aqua

execute(as root) :
mkinitrd -b /boot -k <kernelname> -i <initrdname> -s 1024x768
initrdname can be a new initrd (recommended)
the new initrd is created in /boot
edit your lilo or grub config file and change the initrd entry to the new initrd
For e.g.
execute(as root) :
mkinitrd -b /boot -k vmlinuz-2.6.11.4-20a-default -i initrd.newbootscreen -s 1024x768
This will create the file /boot/initrd.newbootscreen

edit /etc/lilo.conf and add a new entry
#################
image = /boot/vmlinuz
label = Suse.logo
root = /dev/hda1
initrd = /boot/initrd.newbootscreen
append = "resume=/dev/hdb2 selinux=0 splash=silent "
vga = 0x317
####################
run lilo as root

If you are using grub
edit /boot/grub/menu.lst
#######################
title SUSE LINUX 9.3
kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 vga=0x317 selinux=0 splash=silent resume=/dev/hdb2 showopts
initrd (hd0,0)/boot/initrd.newsplashscreen
#######################


DONT COPY PASTE THE EXAMPLES INTO YOUR CONFIGURATION FILES. THEY ARE JUST EXAMPLES. USE YOUR LOGIC.

Thanks.