WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Splashy or usplash  (Read 6150 times)

Offline pimboli

  • Newbie
  • *
  • Posts: 21
Splashy or usplash
« on: August 09, 2009, 05:57:33 PM »
Hi,

is there any package for Splashy or uslpash?

or does it exist a howto?

Otherwise I will try to create my first package for tinycore....

regards

Offline ^thehatsrule^

  • Administrator
  • Hero Member
  • *****
  • Posts: 1726
Re: Splashy or usplash
« Reply #1 on: August 09, 2009, 06:10:24 PM »
I don't think so (yet).

Offline pimboli

  • Newbie
  • *
  • Posts: 21
Re: Splashy or usplash
« Reply #2 on: August 09, 2009, 06:45:35 PM »
ok, then I will try to compile it and if it works I will try to  create a package

Offline gutmensch

  • Administrator
  • Hero Member
  • *****
  • Posts: 605
  • I can make it disappear, have no fear!
    • remembrance blog
Re: Splashy or usplash
« Reply #3 on: September 29, 2009, 12:05:33 AM »
Unfortunately only an extension won't help, because splashy has to be started as soon as possible in the boot process, otherwise you will first see the TC kernel image, probably some text and then the splash screen.

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.
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.
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.

@all: With splashy, directfb and the theme the size of tinycore.gz grows by about 1.6 - 2 MB, maybe it would be an option to use splashy in the future, as it also has the feature to display boot text within the framebuffer image.

Best regards,
Robert
If I seem unduly clear to you, you must have misunderstood what I said. (Alan Greenspan)

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
Re: Splashy or usplash
« Reply #4 on: September 29, 2009, 01:44:49 AM »
I've added the previous post in the wiki
http://wiki.tinycorelinux.com/tiki-index.php?page=splashy
dCore user

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10957
Re: Splashy or usplash
« Reply #5 on: October 02, 2009, 01:44:31 PM »
Shouldn't need to recompile the kernel. Just use the boot code "logo.nologo"
The only barriers that can stop you are the ones you create yourself.

Offline devil

  • Newbie
  • *
  • Posts: 1
Re: Splashy or usplash
« Reply #6 on: October 20, 2009, 04:10:37 AM »
hi,
i have big problems with splashy. for compiling there is more necessary than directfb,
magic.h is needed. i only find file5.03. and also libjpeg is needed and and and.
but now it compiles, but when i start ./splashy test an error occured:
framebuffer is not configured ... i added vga=XXX to menu.lst
but i dont know what is the problem. could me please help someone?

Offline 3rail

  • Full Member
  • ***
  • Posts: 114
Re: Splashy or usplash
« Reply #7 on: October 21, 2009, 07:43:17 AM »
@curaga, is there an explanation somewhere about the logo.nologo boot code?  I don't see it in here http://tinycorelinux.com/faq.html#bootcodes

TIA

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10957
The only barriers that can stop you are the ones you create yourself.