Keep looking. There was some discussion about this (by kibibo and effem?) in the forums. Try searching for "fb raw", since that's the format the images are in, IIRC.

To remove the splash screen, you need to edit the /boot/grub/menu.lst booting in rescue mode or from USB. Add to the line:

kernel /boot/vmlinuz-2.6.21.4-eeepc ... nosplash=y

Dr_Jeff wrote:

what if one wants to change them to something more interesting, where are the files located that need to be replaced & what are their names?

thanks
Jeff

Look in opt/xandros/share/AsusShutdownDialog

albkwan wrote:

To remove the splash screen, you need to edit the /boot/grub/menu.lst booting in rescue mode or from USB. Add to the line:

kernel /boot/vmlinuz-2.6.21.4-eeepc ... nosplash=y

Does this HAVE to be done in rescue mode? Why cant you just edit it while logged into Xandros?

theSuperman wrote:

Does this HAVE to be done in rescue mode? Why cant you just edit it while logged into Xandros?

Unless you've disabled unionfs, any changes you make to this file will be stored on /dev/sda2, the user partition.  But grub is reading from /dev/sda1, the system partition.

You should be able to reinstall grub, if you like, pointing it at /dev/sda2 for menu.lst.  I doubt it's clever enough to work this out on its own, though, so you'll probably need to get your hands dirty - it's unlikely to be just a matter of running "install-grub" blindly.

They're just plain framebuffer dumps.  It's a 640x480 image at 16bpp in 5-6-5 RGB format, little-endian.  The actual images in /boot contain junk at the end which seems to be in a different format - maybe 32-bit?  It's not necessary to pad your files out though.

There's probably some decent software that will output in this format (Gimp?), but I couldn't get Imagemagick's convert utility to do it (it's not the easiest program to use...).  I wrote a short python script to do the conversion though, which works fine for me.

    http://www.glost.eclipse.co.uk/gfoot/eee/png2fb

Save it to disk, make it executable with "chmod +x png2fb", then run it on any 640x480 image you create:

./png2fb test.png test.fb

The first argument is the input file, which doesn't have to be PNG, despite the name, and the second argument is the output file.  I think this should work without needing to install any new packages, but it's hard for me to tell, so sorry if it doesn't.

Your mileage may vary replacing the startup image - it might get read before the union is mounted.  Or not, I can't be bothered to check.  But if you find that replacing it doesn't work, you might have to copy it to the system partition from a rescue console or something like that.

Hi there,

Away from EEE PC at the moment........ Plus not sure I'd be alright in knowing how to follow you instructions.

Could somebody please be so nice as to make a startup.fb and shutdown.fb (OR whatever they are called?) with the input image being totally black. I s'pose that means a 640x480 image consisting of total black. I think that would solve my problem: I have removed the spash already but now I get some odd lines of colour for the few milliseconds that my splash were to be displayed.. Presumably as there is no .fb anymore. A total black .fb I believe would mean I'd effectively not be any the wiser that there *was* a splash (As the screen both before and after the splash is black anyway).

If somebody could knock these .fb's up for me that'd be really appreciated.

Cheers.

EDIT: Done it myself now I'm home... Cheers!

Last edited by LavaChild (2008-01-24 11:12:21 am)

Okay, so its not as easy as I thought. :-/

I can open the images (which appear to have 16 shades of grey),  I can modify them, I can save them in photoshop.  (This is all on a different machine than the eee).

I can replace the original images.  I'm using "sudo XandrosFileManager" to do it.

The start image hasn't changed.  The close down image has, but it isn't the nice 16 shades of grey I had, It's got nasty blue fringing. :-(

Also, the original images are twice the file size as my saved images, so I've got something a bit wrong.

So, unless someone knows where I'm going wrong, gfoot's python script is probably the way to go.

gfoot wrote:

The red channel is in the high bits, blue in the low bits.

I haven't tried your script, but I've changed the screens right now and I think the images are not RGB, but BGR. I mean, the red channel is in the low bits, and the blue in the high bits.

Well, I'm writing a wiki article. Feel free to improve it: http://wiki.eeeuser.com/custom_startup_ … wn_screens

Great Tips! I have been looking for this for ages..
I hear mention of USB key to boot. I need to enter rescue mode repeatedly on multiple eee pc's. How would we be able to use the wiki article and a USB stick instead of repeating the task through Grub / BusyBox?

I did everything on the wiki and the startup screen has changed, but the shutdown did not. I tried three times to no avail. did this happen to any of you? what do you think might be happening?


also, I thought it would be good idea to post the contents of the script given above in case the link goes dead (experience...)

#!/usr/bin/python

import sys

try:
        infile = sys.argv[1]
        outfile = sys.argv[2]
except:
        print "Usage: %s <input> <output>" % ( sys.argv[0], )
        print
        print "    <input>: any existing image file, e.g. a PNG,"
        print "             preferably 640x480"
        print
        print "   <output>: output filename - raw data to dump to"
        print "             /dev/fb/0, assuming you got the image"
        print "             dimensions right"
        print
        sys.exit(1)

import Image
im = Image.open( infile )
im2 = im.convert( "RGB" )
data = im2.getdata()

fp = open( outfile, "wb" )
for (r,g,b) in data:
        assert r >= 0 and r <= 255
        assert g >= 0 and g <= 255
        assert b >= 0 and b <= 255
        r /= 8
        g /= 4
        b /= 8
        assert r >= 0 and r <= 31
        assert g >= 0 and g <= 63
        assert b >= 0 and b <= 31
        value = r*2048+g*32+b
        assert value >= 0 and value <= 65535
        fp.write( chr(value%256)+chr(value/256) )

Show the output from the following commands (where THEFILE is the file you are talking about):

ls -l THEFILE
file THEFILE

If everything was fine, the "ls -l" should output a line beginning with -rwxr-xr-x. If that's not the case, probably the permission is wrong. Anyway, paste the results here.