TinkerOS silent boot? Splash screen?

[kngdmond]

@Im4Tinker I'll give that a try. Just figured if they went to all that work to fill an image full of spam, the last thing they'd want to do is tell people how to remove it. I asked not looking for a spoon fed answer...but hoping somebody could point me in the right direction.

[Im4Tinker]

My curiosity tickled my to try for myself. I see the logo is appearing during the boot, as long as the systemd starts up. So for some conditions it might be a service that will trigger a sort of overlapping image. Funny to know how this is done in the way to make it persistent during the scrolling text.

It might be better to keep plymouth with a neutral splash screen, so systemd report will be covered.

The systemd will appear though because there's an error, Failed to start Load Kernel Modules.

If I use lxterminal, then there are no nagging logo over there. There's a logo when logging on the serial port or SSH login, which is easy to overcome by commenting the /etc/pam.d/ssd & /etc/pam.d/login and comment

Code:

session    optional     pam_motd.so .....

I still hard to find the way to log in via SSH. The daemon is up and running but I can't get connected wired nor wireless.

[kngdmond]

I couldn't login via SSH or with Wincsp until I physically logged in. Once I was physically logged in then I could remotely login via ssh or Wincsp. I managed to get rid of all the messages by commenting out all the motd files.

The only kernel module error I got was from cups. I just uninstalled it because I don't print.

I tried installing SDL2. I got it to got glmark2 to install. Could run it from X11 and console...but from console I couldn't get it to use openGLES....it worked but was throwing rockchip driver not found errors.

The source of the boot image is still a mystery.

[yandex]

Guys, any news? Does anybody have the update about splash screen?
I modify u-boot env, by advice on the internet (add "bmp display xxx" into my u-boot), and nothing new
Who is a hero, who wins this? ... damn splash image

[Im4Tinker]

Is this that you read ?
In brief, it will need a bitmap image on the same kernel partition.
What is your script about that splash screen ?

[yandex]

Is this that you read ?
In brief, it will need a bitmap image on the same kernel partition.
What is your script about that splash screen ?

yeah, I read it. 

Code:

setenv showsplash "fatload mmc 1 40001000 splash.bmp; bmp display 40001000" (sure, I have splash.bmp on /boot)
setenv bootcmd "run distro_bootcmd;run showsplash"

...or I tried run before distro

Code:

setenv bootcmd "run showsplash;run distro_bootcmd"
saveenv

boot (or just reboot)
and nothing splash..
I see reading my file as a result:

Code:

....
reading splash.bmp
241078 bytes read in 16 ms (14.4 MiB/s)
....

[Im4Tinker]

If you were doing it interactively I doubt it's working. So there could be to write several times the boot.scr and give it a test.
But you may try interactively to see whether the image is loaded on memory. Perhaps at certain point, it will take to resize the allocation.
I can't give you much support for that, as much as I didn't bother to have a splash screen yet.
I'd suggest you to try the armbian u-boot which is compiled with the splash screen.

[yandex]

If you were doing it interactively I doubt it's working. So there could be to write several times the boot.scr and give it a test.
But you may try interactively to see whether the image is loaded on memory. Perhaps at certain point, it will take to resize the allocation.
I can't give you much support for that, as much as I didn't bother to have a splash screen yet.
I'd suggest you to try the armbian u-boot which is compiled with the splash screen.

I think the problem is not in u-boot, coz the display doesn't start at that time... display subsystem inits about 3 sec after starting kernel, and it's kernel procedure,not uboot. So, for linaro it doesn't help

[Im4Tinker]

You're right. The display is managed by the kernel, which should get the (supposed to be) right details by a dtb file, passed by the u-boot.
Until now, I wonder why there are 2 device-tree (maybe 3) files for the tinker board (not S).