The good news is: It is quite simple to get splashy to work despite of the mentioned problem.
Tasks to follow:
1.) Download splashy 0.3.13 and directfb 1.0.1, compile the latter one first, install it, then splashy. As usual use CFLAGS=“-Os -pipe -march=i486 -mtune=i686”, splashy with –prefix=/ and make DESTDIR=install_dir_path install.
2.) Recompile the tc kernel with unsetting the option CONFIG_LOGO or use the kernel boot code “logo.nologo”.
3.) Extract tinycore.gz and copy the files from install_dir_path to the extracted rootfs from tinycore.gz.
4.) Change the file etc/init.d/tc-config in the extracted rootfs folder to startup splashy and do some screen updates while following the commands in the file. For example /sbin/splashy boot, /sbin/splashy_update “progress 10”, /sbin/splashy_update “progress 20”, and so on. On the very top of the file you should enter a “exec >/dev/null” to suppress any text messages.
5.) Be sure to start splashy not too early, depending on your hardware the first entry point can be the section after WAITUSB in the tc-config, otherwise you will get an framebuffer not configured correctly error.
6.) Customize your splashy theme and edit config.xml.
7.) Repack the tinycore.gz and boot it with framebuffer options, for example boot code vga=0x366.
As a result you will have a tinycore.gz with about 12.5 to 13 MB including boot splash feature.
