Bootlsplash no longer wrking after latest updsate!

randrake · 01-15-2006, 04:45 PM

Latest round of updates has rendered the bootsplash not working. I suspect it is from a kernel update and the bootloader is unrecoqnized. Anyone else find this and is there a patch for bootsplash?

Penguin of Wonder · 01-15-2006, 06:39 PM

Does it give you an error message? Or does the screen just not appear? Goto into your options in Gnome (or KDE) and change your bootsplash, maybe your updates have changed the name of, or removed the splash you were using all together. I didn't like the default splash anyway, so I changed mine.

randrake · 01-16-2006, 10:54 AM

Yes I changed mine, and also my Lilo splash, the files are all there, i changed back to Suse's and ran the script and Yast shows it as still on, however it does not work. After the update I did not run /sbin/lilo don't recall seeing a kernel update but there must of been one there as lilo would not load and grub must of been corrupt as the system would not boot. Neither could I get into the bios, or boot to cd or floppy, so reset the cmos and crossed my fingers and it booted the dvd and from there reinstalled lilo but lilo splash was gone, and bootsplash also gone. Have grub now however with no splash. Strange trouble with grub this release hence the use of lilo. Every thing working minus the splashes, might add updated Kde to 3.5 also.

abisko00 · 01-16-2006, 11:10 AM

Try to run mkinitrd (as root). Your ramdisk may contain a splash with the wrong resolution, so it does not show up. minitrd will detect the current resolution and include the correct picture.

randrake · 01-16-2006, 12:41 PM

Tried that as well but to no use, I first thought it was because I forgot to run lilo after but using grub now. No it's cooked for some reason. Like I said every thing in the config file is as it should as are all the themes and resolutons. The only thing I can think of is I am running kernel 6.13.15, perhaps there is a bootsplash patch needed. ashame too because I finaly had a theme I liked.
http://img79.imageshack.us/img79/971...80x10241zm.jpg

Penguin of Wonder · 01-16-2006, 06:51 PM

Nice pic, did you make it yourself, or did you find that somewhere?

randrake · 01-16-2006, 11:57 PM

Found it can't remember where, added the bootsplash text. Also was using it as wallpaper, and grub splash and XP boot, and logon screen. Kind of a system wide theme. Was great for the month or so it worked.

Nice system I still only have an Athalon XP3200. Do you find that 64 bit nix is much faster than 32?

Penguin of Wonder · 01-17-2006, 09:56 AM

Honestly, I can't tell a difference between the two. I'm in the process of switching to Gentoo because its 64bit version is supposedly better suited for 64 bit processors in a still prodominatly 32bit world. The only thing you ever hear from Gentoo users "its so fast!", so i'm goina see if its true.

abisko00 · 01-17-2006, 10:24 AM

Quote:

The only thing I can think of is I am running kernel 6.13.15, perhaps there is a bootsplash patch needed.

I guess you mean 2.6.13-15? If it's an original SUSE kernel it will contain the bootsplash patch. For a self-compiled, you need to include the patch.

So you get a text-mode boot instead? Or no output at all? Check the kernel-line in /boot/grub/menu.lst for the correct "vga=" and "splash=" entry. You could also check /etc/sysconfig/bootsplash if it is set to the right theme and to SPLASH="Yes" and run mkinitrd -s <your resolution>.

randrake · 01-18-2006, 03:14 AM

Quote:

Originally Posted by abisko00

I guess you mean 2.6.13-15? If it's an original SUSE kernel it will contain the bootsplash patch. For a self-compiled, you need to include the patch.

So you get a text-mode boot instead? Or no output at all? Check the kernel-line in /boot/grub/menu.lst for the correct "vga=" and "splash=" entry. You could also check /etc/sysconfig/bootsplash if it is set to the right theme and to SPLASH="Yes" and run mkinitrd -s <your resolution>.

yes, lol never noticed that, few years to go before we get that high.

Any ways backed up my home folder and did a clean reinstall. The first was an upgrade from 9.3. All is golden now. Note if you want to hack your grub splash backup the /boot/grub/message file first it will save you greef down the road as even a reinstall of grub won't fix a corrupted message file.
Yes I ran the mkinitrd cmd and Splash=yes was ok, didnot know of the vga= like I said the screen was there for a month or so. Any ways thanks all for the suggestions.

Jongi · 01-26-2006, 04:41 PM

I'm trying to get the Fingerprint splash to run on boot

# ls -l /etc/bootsplash/themes

Code:

drwxr-xr-x  5 root root  136 2006-01-18 21:53 .
drwxr-xr-x  3 root root   72 2005-09-09 18:46 ..
drwxr-xr-x  4  500 users  96 2005-09-30 11:51 Fingerprint
drwxr-xr-x  3 root root   72 2006-01-18 21:53 login-scan
drwxr-xr-x  6 root root  160 2006-01-12 20:18 SuSE

# cat /etc/sysconfig/bootsplash

Code:

## Path:        System/Boot
## Description: selects bootsplash graphics theme
## Type:        string
## Default:     SuSE
# Choose the bootsplash theme. It should be based in
# /etc/bootsplash/themes/
THEME="SuSE"
## Path:        System/Boot
## Description: enables/disables bootup graphics
## Type:        yesno
## Default:     yes
#
# SPLASH can be set to "no" to turn off the splash-screen on console 1
# at boot time (after kernel load).
#
# SPLASH=no to disable the splash screen
#
# SPLASH=yes to show the splash screen
#
SPLASH="yes"

And the normal SuSE bootsplash does not run

# cat /boot/grub/menu.lst

Code:

# Modified by YaST2. Last modification on Wed Jan 25 20:08:30 SAST 2006

color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd1,0)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title SuSE Linux 10.0
    root (hd1,0)
    kernel /boot/vmlinuz-2.6.13-15.7-default root=/dev/hdc1 selinux=0  resume=/dev/hdc5  splash=silent showopts vga=792
    initrd /boot/initrd-2.6.13-15.7-default


###Don't change this comment - YaST2 identifier: Original name: Fedora Core (2.6.11-1.1369_FC4) (/dev/hdc6)###
title Fedora Core 4
    kernel (hd1,5)/boot/vmlinuz-2.6.11-1.1369_FC4 root=LABEL=/ vga=792 ro rhgb quiet
    initrd (hd1,5)/boot/initrd-2.6.11-1.1369_FC4.img

###Don't change this comment - YaST2 identifier: Original name: windows 1###
title Windows XP
    chainloader (hd2,0)+1

###Don't change this comment - YaST2 identifier: Original name: floppy###
title Floppy
    chainloader (fd0)+1

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX 10.0
    root (hd1,0)
    kernel /boot/vmlinuz root=/dev/hdc1 showopts ide=nodma apm=off acpi=off noresume selinux=0 nosmp noapic maxcpus=0 edd=off 3
    initrd /boot/initrd

The Suse config is the one that I am wanting to show a bootsplash for.

# mkinitrd -s 1024x768

Code:

Root device:    /dev/hdc1 (mounted on / as reiserfs)
Module list:    sis5513 reiserfs processor thermal fan

Kernel image:   /boot/vmlinuz-2.6.13-15.7-default
Initrd image:   /boot/initrd-2.6.13-15.7-default
Shared libs:    lib/ld-2.3.5.so lib/libblkid.so.1.0 lib/libc-2.3.5.so lib/libselinux.so.1 lib/libuuid.so.1.2

Driver modules: ide-disk sis5513 processor thermal fan
Filesystem modules:     reiserfs
Including:      klibc initramfs udev fsck.reiserfs
Bootsplash:     SuSE (1024x768)
7805 blocks

Kernel image:   /boot/vmlinuz-2.6.13-15.7-xen
Initrd image:   /boot/initrd-2.6.13-15.7-xen
Shared libs:    lib/ld-2.3.5.so lib/libblkid.so.1.0 lib/libc-2.3.5.so lib/libselinux.so.1 lib/libuuid.so.1.2


Driver modules: ide-disk sis5513 processor thermal fan
Filesystem modules:     reiserfs
Including:      klibc initramfs udev fsck.reiserfs
Bootsplash:     SuSE (1024x768)
8106 blocks

abisko00 · 01-27-2006, 01:38 AM

Change THEME="SuSE" to THEME="Fingerprint" in /etc/sysconfig/bootsplash, then run mkinitrd.

I am not sure it it makes any difference, but you could remove a couple of excess spaces in parameters line of menu.lst (around "resume"). Otherwise everything looks normal.

Jongi · 01-27-2006, 11:09 AM

What files are meant to be in the login-scan directory? I think I might have copied some of the Fingerprint files into that directory and overwritten some files.

Interestingly in YaST the only theme that appears is SuSE.

Jongi · 02-02-2006, 03:22 PM

See the errors in bold:

Code:

# mkinitrd
Root device:    /dev/hdc1 (mounted on / as reiserfs)
Module list:    sis5513 processor thermal fan reiserfs

Kernel image:   /boot/vmlinuz-2.6.13-15-default
Initrd image:   /boot/initrd-2.6.13-15-default
Shared libs:    lib/ld-2.3.5.so lib/libblkid.so.1.0 lib/libc-2.3.5.so lib/libselinux.so.1 lib/libuuid.so.1.2

Driver modules: ide-disk sis5513 processor thermal fan
Filesystem modules:     reiserfs
Including:      klibc initramfs udev fsck.reiserfs
Bootsplash:     fingerprint-bs (1024x768)disabled for resolution 800x600

/etc/bootsplash/themes/login-scan/images/silent-1024x768.jpg: No such file or directory
7628 blocks

Kernel image:   /boot/vmlinuz-2.6.13-15-xen
Initrd image:   /boot/initrd-2.6.13-15-xen
Shared libs:    lib/ld-2.3.5.so lib/libblkid.so.1.0 lib/libc-2.3.5.so lib/libselinux.so.1 lib/libuuid.so.1.2


Driver modules: ide-disk sis5513 processor thermal fan
Filesystem modules:     reiserfs
Including:      klibc initramfs udev fsck.reiserfs
Bootsplash:     fingerprint-bs (1024x768)disabled for resolution 800x600

/etc/bootsplash/themes/login-scan/images/silent-1024x768.jpg: No such file or directory
7768 blocks

I re-extracted the files to the fingerprint-bs directory

Code:

# ls
.  ..  fingerprint-bs  SuSE

With the bootsplash file section as

Code:

# /etc/bootsplash/themes/
THEME="fingerprint-bs"
## Path:        System/Boot

I'm think that the problem is with what I have downloaded.

abisko00 · 02-03-2006, 02:30 AM

Strangely, mkinitrd mentiones resolution 800x600, but the picture is correct size. Maybe the vga parameter is not detected properly. Try to use vga=0x318 (hexadecimal) instead of vga=792 with SUSE.

Another point I don't understand is why mkinitrd searches for the splash picture in login-scan instead of the specified path. Maybe you can scan /etc for the string "login-scan" to find the file where this setting comes from.