On Tuesday 11 July 2006 19:30, [EMAIL PROTECTED] wrote:
> > >> Hi
> > >> is anybody able to though more light:
> > >>
> > >> To rebuild my kernel (its a long story ...) I do:
> > >>
> > >> apt-get source linux-image-2.6.15-25-686
> > >> apt-get build-dep linux-image-2.6.15-25-686
> > >> unpack /usr/src/linux-source-2.6.15.tar.bz2
> > >> link linux to linux-source-2.6.15
> > >> copy /boot/config-2.6.15-25-686 to .config
> > >> edit Makefile to make EXTRAVERSION =
> > >> instead of the rubbish in there.(.7-ubuntu1)
> > >> make oldconfig
> > >> make-kpkg --append-to-version "-25-686" --stem linux -us -uc --initrd
> > >> kernel_image
> > >>
> > >> OK the trouble starts here:
> > >>
> > >> dpkg -i linux-image-2.6.15-25-686_10.00.Custom_i386.deb
> > >> bla ...
> > >> Searching for splash image ... none found, skipping ...
> > >> Found kernel: /boot/vmlinuz-2.6.15-25-686
> > >> Found kernel: /boot/memtest86+.bin
> > >>
> > >> How do I add the splash image?
>
> sudo apt-get install grub-splashimages
>
> then you need to update the file
> /boot/grub/menu.lst
>
> add something like this near the top:
> splashimage=(hd0,0)/boot/grub/splashimages/bike_gua.xmp.gz
>
>
> if you websearch "grub splash image" you'll find sites explaining how to
> make your own splash images.

Yes it is a grub message, and no that's not what I want.

My newly built vmlinuz and the old behave identically (show boot splash)
My newly built initrd does not show the splash, the old does
Many instances of googled howtos are WRONG:
   they say put a /sbin/usplash_write "TIMEOUT 120" into the initrd init file
   the working (as installed) initrd does NOT have one!

----------------------------------------------------
compare not working initrd files, with working ones
----------------------------------------------------
[EMAIL PROTECTED]:/home/jamu/temp# 
for i in `find . -type f`
> do
> cmp $i ../tmp/$i
> done
./conf/modules ../tmp/./conf/modules differ: byte 1, line 1
./lib/modules/2.6.15-25-686/kernel/drivers/scsi/aacraid/aacraid.ko 
../tmp/./lib/modules/2.6.15-25-686/kernel/drivers/scsi/aacraid/aacraid.ko 
differ: byte 39537, line 27
./init ../tmp/./init differ: byte 1506, line 96
[EMAIL PROTECTED]:/home/jamu/temp# 

----------------------------------------------------
from the working initrd looking at the unworking one
----------------------------------------------------
[EMAIL PROTECTED]:/home/jamu/tmp# for i in `find . -type f`; do cmp $i 
../temp/$i; 
done
./conf/modules ../temp/./conf/modules differ: byte 1, line 1
./lib/modules/2.6.15-25-686/kernel/drivers/scsi/aacraid/aacraid.ko 
../temp/./lib/modules/2.6.15-25-686/kernel/drivers/scsi/aacraid/aacraid.ko 
differ: byte 39537, line 27
cmp: 
../temp/./lib/modules/2.6.15-25-686/kernel/drivers/video/console/softcursor.ko: 
No such file or directory
cmp: 
../temp/./lib/modules/2.6.15-25-686/kernel/drivers/video/console/bitblit.ko: 
No such file or directory
cmp: ../temp/./lib/modules/2.6.15-25-686/kernel/drivers/video/console/font.ko: 
No such file or directory
cmp: 
../temp/./lib/modules/2.6.15-25-686/kernel/drivers/video/console/tileblit.ko: 
No such file or directory
cmp: ../temp/./lib/modules/2.6.15-25-686/kernel/drivers/video/console/fbcon.ko: 
No such file or directory
cmp: ../temp/./lib/modules/2.6.15-25-686/kernel/security/commoncap.ko: No such 
file or directory
cmp: ../temp/./lib/modules/2.6.15-25-686/initrd/vesafb.ko: No such file or 
directory
cmp: ../temp/./lib/modules/2.6.15-25-686/initrd/capability.ko: No such file or 
directory
./init ../temp/./init differ: byte 1506, line 96

OK this is too technical for the list. The answer lies above. Frustrating that 
it's not documented! Oh the reason for all this: vmserver works. It does not 
work if apt-get'd. module vmnet not present for kernel 2.6.15-25-686

Thanks
James
-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to