
God aften Kasper, Søndag den 2. november 2003 16:00 kvad Kasper Thunoe:
>> When my SuSE 9.0 boots up it does so without using a >> bootsplash theme. Bootsplash packages are installed so >> how do enable these at >> startup? > >Is YaST2 -> System -> editor for /etc/sysconfig Files -> > System -> Boot -> SPLASH set to "yes"?
Yup it is set to 'yes', and a theme is chosen, but still it wont show anything....??? [...]I spent last nite trying to do different things in my lilo.conf[...]
You are using LILO. I am using GRUB.
My standard GRUB kernel line for 9.0 looks like this:
kernel (hd0,1)/vmlinuz root=/dev/hda6 vga=0x317 splash=silent desktop hdb=ide-scsi hdblun=0 showopts
This makes my boot splash work.
What does your corresponding LILO kernel line look like?
I just changed loader from lilo to grub, and compared my config file to yours which is more or less the same. I added the vga=0x317, but that didnt work well. Actually it didnt boot at all. Which vga mode should I use for a laptop LCD screen with a max. res of 1024x768 anyways???
Here is the grub entry for linux: title Linux kernel (hd0,4)/boot/vmlinuz root=/dev/hda5 showopts splash=silent desktop initrd (hd0,4)/boot/initrd
I am sorry, but I am all out of ideas now.
Anyone else with ideas?
Although this is not an idea, it might be a pointer in some interesting direction. I have just experienced the same as you, and at first glance it seems to have something to do with where the boot loader is placed, when it's on a dual boot system. I have set up a dual boot computer (SuSE 8.2 for production + SuSE 9.0 for a test swing). I bet this resembles your setup with Win XP and SuSE 9.0. Now, when, during the install, I choose to put the test system's boot loader on a floppy, the test system's boot splash comes up fine, no matter whether I boot the test system from the floppy or directly from my production system's boot loader. However, when, during install, I choose to put the test system's boot loader in the boot sector of the test system's partition, the boot splash does not show, no matter whether I boot the test system directly from my production system's bootlader or by chain loading the test system's boot loader from the production system's boot loader. As far as I can see, the difference between the two types of install, is where I put the boot loader for the test system. Does this give you any ideas? Hilsen Johnny :o)