Tiny Core Linux
Tiny Core Base => Raspberry Pi => Topic started by: andyj on May 19, 2015, 04:58:43 PM
-
I managed to get plymouth running on the Pi 2, but it appears to be for naught. It seems that the Pi doesn't support vga modes in the cmdline, so instead of graphics I get some text squares that approximate what I'm hoping for. Since it's only for about 4 seconds, at this point a simple program that would show a static image would suffice. What sort of lightweight programs are there that will work in the framebuffer console? Is it possible for the kernel logo to persist once init starts?
-
fbv
Frame Buffer Viewer
Views images in frame buffer. Supported formats limited to png, jpg and bmp.
http://s-tech.elsat.net.pl/fbv/
-
Thanks! I was looking for that too.
-
Sounds nice. Until you try to build it. What's the trick?
-
Fim works, but it's kinda big at 604k. Fbi works too, and it's not quite so big at 375k. I haven't tried it on my 320x240 display yet. Neither of these sizes include the dependencies. Is there anything smaller out there?
-
Sounds nice. Until you try to build it. What's the trick?
Hmm, true.
...
In file included from /usr/local/include/pngconf.h:72:0,
from /usr/local/include/png.h:476,
from png.c:22:
png.c: In function ‘fh_png_getsize’:
png.c:164:23: error: dereferencing pointer to incomplete type
if (setjmp(png_ptr->jmpbuf))
^
<builtin>: recipe for target 'png.o' failed
make: *** [png.o] Error 1
I guess you can't use the x86 build (167.9K) on ARM?
http://tinycorelinux.net/4.x/x86/tcz/fbv.tcz
-
This is the kind of error you see when trying to compile something looking for libpng12 when you have libpng16 (or vice-versa).
-
..and in that case someone has often already created a patch: look in packages.ubuntu.com for example.
-
I found a patched version here http://repo.or.cz/w/fbv.git/tree (http://repo.or.cz/w/fbv.git/tree) that works. I compiled it for png only without gif, jpeg, and bmp support, so it's only 18k and only requires libpng16. I can live with that.
-
Apparently, if you don't let anything at all output to the console then the kernel boot logo will persist intact until the X desktop appears about 5 seconds later. No image viewer needed. This is really only practical if the kernel image is the same size as the screen so you don't get multiple images (one per core).