Bootsplash and Debian. A paradox?

**raid517** · 05-11-2005, 03:31 PM

Hi can someone please help me? I have installed bootsplash in my Kanotix install. It was working fine until I upgraded the kernel. However after I installed the latest kernel (2.6.11-kanotix-10) It stopped working, and now refuses to work at all. This is despite the fact that that I have not altered any options in the kernel (bootsplash is set to yes, vesafb is set to Yes initial file system support is set to yes and virtual memory file system support set to yes). I have also ran (Debian) dpkg-reconfigure bootsplash and selected my prefered bootsplash theme (indeed I have tried several) and I am also using identical options in my grub.conf file when bootsplash was last working. These are as follows:

Code:

 title        Kanotix/Linux, kernel
root        (hd0,5)
kernel        /vmlinuz root=/dev/hda3 ro ramdisk_size=100000 lang=us apm=power-off selinux=0 nomce vga=791 splash=silent video=vesafb:nomtrr
boot

The relevant sections of dmesge regarding bootsplash show no problems:

Code:

bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (1024x768, 22648 bytes, v3).
bootsplash: status on console 1 changed to on
bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (1024x768, 22648 bytes, v3).
bootsplash: status on console 2 changed to on
bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (1024x768, 22648 bytes, v3).
bootsplash: status on console 3 changed to on
bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (1024x768, 22648 bytes, v3).
bootsplash: status on console 4 changed to on
bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (1024x768, 22648 bytes, v3).
bootsplash: status on console 5 changed to on

Code:

vesafb: framebuffer at 0xd0000000, mapped to 0xe0880000, using 6144k, total 16384k
vesafb: mode is 1024x768x16, linelength=2048, pages=9
vesafb: protected mode interface info at c000:ab90
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device

In order to test if bootsplash simply needed to be reinstalled I tried uninstalling it and then installing it again.

But when I did, this is what happend:

Snip

Code:

Selecting previously deselected package bootsplash-theme-newlinux.
Reading database.  212901 files and directories currently installed.
Unpacking bootsplash-theme newlinux from bootsplash theme newlinux 0.5-5 all.deb
Selecting previously deselected package bootsplash-theme-kanotix.
Unpacking bootsplash-theme-kanotix from ...bootsplash-theme-kanotix_0.5-5_all.deb...
Selecting previously deselected package bootsplash.
Unpacking bootsplash from ...bootsplash_3.1-11_i386.deb ...

Selecting previously deselected package sysv-rc-bootsplash.
Unpacking sysv-rc-bootsplash from ...sysv-rc-bootsplash_1.0.0-5_i386.deb ...
Setting up sysv-rc-bootsplash 1.0.0-5 ...
Testing if patches apply cleanly...
Patching files...
patching file etc/nit.drcS
patching file etcinit.drc

Setting up bootsplash-theme-newlinux 0.5-5 ...
dpkg: error processing bootsplash-theme-newlinux --configure:
subprocess post-installation script returned error exit status 10
Setting up bootsplash-theme-kanotix 0.5-5 ...
dpkg: error processing bootsplash-theme-kanotix --configure:
subprocess post-installation script returned error exit status 10
dpkg: dependency problems prevent configuration of bootsplash:
bootsplash depends on bootsplash-theme-newlinux  bootsplash-theme; however:
Package bootsplash-theme-newlinux is not configured yet.
Package bootsplash-theme is not installed.

Which is typically nonsensical. Bootsplash is marked as a dependency of bootsplash-theme-newlinux. However bootsplash can't be configured, because bootsplash-theme-newlinux isn't configured yet. Bootsplash theme newlinux is marked as a dependency of bootsplash (it needs bootslpash installed before it can be configured correctly) however bootsplash-theme-new-linux can't be configured, because bootsplash isn't properly installed yet. Which is an impossible situation!

Can anyone suggest any sane or sensible reason why, given the fact that everything is configured correctly to use bootsplash that bootsplash might have chosen now to stop working?

Any input would be appreciated.

Q