Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: imaad on February 24, 2015, 11:12:14 AM
-
Hi,
How can I know if the splash screen feature was enabled in the kernel (linux kernel 3.16.6)?
Thank you your answer,
-
Hi imaad,
may I ask, what is "splash screen feature"?
-
Hi Misalf,
I saw that in many documentations for exemple (http://www.stlinux.com/howto/splash-screen).
In fact, I think it's about framebuffer kernel mod. I don't understand very well.
I try to show just a image at boot. I can show a image in the grub menu but not when the system boot.
What is the best solution to display a image when the system boot until to X server start?
It's better to use a program like plymouth, xsplash or to modify initrd and to display the image?
-
Yes, you can build plymouth and modify the (or create an additional) initrd.
http://wiki.tinycorelinux.net/wiki:boot_splash
-
If you search the forum, it's been discussed many times, last here:
http://forum.tinycorelinux.net/index.php/topic,18086.msg109616.html#msg109616
-
Thank Misalf and curaga for yours advices.
Even if I spent some day before, to search about splash screen for Tiny Core, I didn't found the wiki:boot_splah page :o
curaga why have you abandoned the fbv to view an image at boot? It's the fliking the cause?
It is an equivalent soft for tc 6.x version (just to view an image like the fbv you have made for 2.x or 1.x version)?
How did you run the fbv at boot?
You say then in the start of tc-config start a framebuffer image viewer, and in the end kill it
what is tc-config ? How to start framebuffer at boot?
-
You can get fbv by entering this in a terminal
cd /etc/sysconfig/tcedir/optional
wget http://tinycorelinux.net/4.x/x86/tcz/fbv.tcz
tce-load -i fbv
fbv does work on TC 6.x.
To test fbv, exit out of X (Ctrl+Alt+Backspace) and enter
/local/bin/fbv -a -i /usr/local/share/pixmaps/logo.png
/etc/init.d/tc-config needs to be modified to start fbv - preferably before any messages are shown I guess - this needs remastering of core.gz . Also, fbv needs to be added to core.gz so it is available before extensions are getting loaded.
I believe framebuffer is enabled by vga= boot code?
-
Misalf I implemented fbv and modify tc-config to start fbv at boot of the system.
Everything work corectly the image is show at start of system, but the booting not continue, I need to tap Enter or Space and the system continu to boot as normally.
I try to put the command even in background but is the same think.
/local/bin/fbv -a -i /usr/local/share/pixmaps/logo.png &
It this comportment normal or I missed something ?
Thank for info.
You can get fbv by entering this in a terminal
cd /etc/sysconfig/tcedir/optional
wget http://tinycorelinux.net/4.x/x86/tcz/fbv.tcz
tce-load -i fbv
fbv does work on TC 6.x.
To test fbv, exit out of X (Ctrl+Alt+Backspace) and enter
/local/bin/fbv -a -i /usr/local/share/pixmaps/logo.png
/etc/init.d/tc-config needs to be modified to start fbv - preferably before any messages are shown I guess - this needs remastering of core.gz . Also, fbv needs to be added to core.gz so it is available before extensions are getting loaded.
I believe framebuffer is enabled by vga= boot code?
-
I've done something like that in the past. First direct the console out with console=/dev/null, then in the start of tc-config start a framebuffer image viewer, and in the end kill it. [...]
I guess console=/dev/null is a kernel boot code?
-
Now it's working, I have the image at boot.
Just some remarks :
- at the beginning the logo tiny core is show for approximately 1 second (the logo is kept in background even if my own logo is showed)
- until the x server start I have a black screen approximately 3 seconds (I think that is because the video driver is load and the resolution change)
- when I look in process liste the fbv is already killed (I think it's kill when the video driver is loading).
This remarks are not really a problem but I will try to fix them.
-
If the image disappears for some reason, you might be able to tell fbv to redraw the image by using its slideshow feature. Note the -d parameter which stands for "delay" and also the REPEAT variable.
This makes fbv showing the same picture 10 times with a delay of 200 ms:
[ -e /bin/fbv ] && killall -q fbv ; /bin/fbv -a -i -d 2 `REPEAT=10; while [ $REPEAT -gt 0 ]; do REPEAT=$(($REPEAT - 1)); echo -n " /usr/local/share/pixmaps/logo.png"; done` 2>/dev/null &
After the last image is shown however, fbv will quit. Might be extendable so fbv is executed again in background after the loop to show the image once more until killed.
Not sure about the old logo staying on screen after showing another one.
the parameters -c -u actually do this, if they are used (also nice without console=/dev/null boot code).
You might be able to clear the screen with clear before running fbv again.
I have no idea about what the preferred way to kill fbv would be. Maybe it just dies when tc-config is done?
-
I'm testing fbv on my netbook.
As the plymouth wiki says, intel graphics cards might make the screen resolution to change during boot. This happens for me too (even though the correct resolution is already set via vga= boot vode) and it will cause the image drawn by fbv to disappear.
There seems to be more in tc-config which interferes with fbv though.
fbv might need to be re-executed several times (or using slideshow)?
--
Full-screen ( -e parameter) 16x16 sized pictures look crisp clean and super retro. (:
-
Hi Misalf,
I'm agree with you, I have a nice image if I use -p parameter. I guess that I start an old player game. :)
I tried to use your code, without success. No error is showed. Do I need to put fbv in "/bin" ? I have used "/local/bin/fbv" instead of "/bin/fbv".
What mean [ -e /bin/fbv ] ?
[ -e /bin/fbv ] && killall -q fbv ; /bin/fbv -a -i -d 2 `REPEAT=10; while [ $REPEAT -gt 0 ]; do REPEAT=$(($REPEAT - 1)); echo -n " /usr/local/share/pixmaps/logo.png"; done` 2>/dev/null &
Anyway if I put (restart) the fbv after the xvesa driver is load in tc-config the image is reloaded and I have no black screen.
-
Oh, I put it in /bin because there is usually no /local directory in my file system root. It just seemed strange.
You need to change the code to point to /local/bin/fbv .
[ -e /bin/fbv ]
This checks if the file /bin/fbv does exist (-e) so the rest is only executed if that is true (&&).
-
OK I found the problem. When I wrote the commande I put ' instead of `, so the fbv could not find the path of logo.
Everything works now. Thank
PS: It's fbv also disponible in the repo for raspberry ? I tried to find it, but I don't see fbv for arm platform.
Where can I find the source of http://tinycorelinux.net/4.x/x86/tcz/fbv.tcz to recompile it.
-
from the fbv.tcz.info file:
...
Version: 1.0b
Author: Mateusz Golicz and Tomasz Sterna
Original-site: http://s-tech.elsat.net.pl/fbv/
Copying-policy: GPLv2
...
-
Hi Misalf
Oh, I put it in /bin because there is usually no /local directory in my file system root. It just seemed strange.
You need to change the code to point to /local/bin/fbv .
The maintainer made an error in packaging, it should have been /usr/local/bin/fbv
-
See the "logo.nologo" kernel boot code.
-
Finally I managed to create a splash screen, even if it'a a group of image but it's look ok (my opinion).
Here a demo : https://www.youtube.com/watch?v=Pmp65mAzUlw&feature=em-upload_owner
Thanks to all
-
When I worked on the plymouth code and wiki a few years ago one of the changes I suggested was to separate tc-config into rcS and tc-config, so that someone could put the splash code in rcS instead of tc-config under the assumption that by not changing tc-config that the splash code would be resistant to version upgrades. Have you tried it here? You would need to put it right before the call to tc-config at the end of rcS. Now that there is kernel splash code you are doing this without plymouth?
-
Hi andyj,
It's correctly what you say to use splash screen in another location and not in tc-config, but fbv is closing when the video driver is loaded because the resolution change. For this reason I must to restart fbv. In the other hand it allow to know the percentage of the operating system load.
I have not found another solution to create a splash screen with a minimum modification of the system such as fbv.