Yes it comes from omxplayer. I had these problems when switching my raspicade distro to read only. see my reply here http://www.raspberrypi.org/forums/viewtopic.php?p=680312#p680312

you have to delay the booting video to wait for stuff being loaded ;)

Be careful, don't upgrade firmware with rpi-update.... my dgen and gnego emu don't run anymore -> i get black screen.

Yes I noticed that too... so no more rpi-update ;)

Stella (libretro) is running on my raspicade distro... I don't have ScumVM...

@piplayah: i simple commented out the call of omxplayer in that file

# omyplayer ...

and it is not absurd what @ian57 saied with the delay. it seems, that the new kernel works a bit different. and in linux some initialization scripts are started in the order, ordered by thier file names...
so the script 'asplashscreen' comes before all the other scripts...
and maybe some resources that the 'asplashscreen' requires are not initialized at the moment where it is called...
but renaming the script to 'nasplashcreen' will change the order and bring the execution of that script somewhere after an other init script were executet...
so it seems that at this time the needed ressources are initialized before the "nasplashcreen" is called.

there are other init scripts that will follow a similar mechanism and thats the reason, why they are named with a number in front of, to ensure the scripts will be executed in a specific order...
ok, newer init methods do have a header with dependencies so the system can build a dependency tree to ensure the correct order of init scripts and will not use the file name based method, but for backward compatibility that is still available and in use.

FYI: https://wiki.debian.org/LSBInitScripts/DependencyBasedBoot

to check the dependency tree

~$ /usr/share/insserv/check-initd-order --help
usage: check-initd-order [-cdgko] [-b basedir]
  -b basedir (default /etc)
  -d enable debug output
  -o do not load override files
  -k use shutdown (reboot) sequence instead of boot sequence
  -g generate graph
  -c use combined boot and shutdown sequence (only for graphs)

~$ /usr/share/insserv/check-initd-order -g

# Generating graph
digraph packages {
rankdir=LR;
concentrate=true;
"asplashscreen" [shape=box];
"fake-hwclock" -> "checkroot"[color=yellow] ;
"fake-hwclock" [shape=box];
"glibc" -> "hostname"[color=springgreen] ;
"hostname" [shape=box];
"glibc" -> "mountkernfs"[color=springgreen] ;
"mountkernfs" [shape=box];
"mountkernfs" -> "udev"[color=blue] ;
"udev" [shape=box];
"keyboard-setup" -> "checkroot"[color=yellow] ;
"mountkernfs" -> "keyboard-setup"[color=blue] ;
"keymap" -> "keyboard-setup"[color=springgreen] ;
"udev" -> "keyboard-setup"[color=springgreen] ;
"keyboard-setup" [shape=box];
"mountkernfs" -> "mountdevsubfs"[color=blue] ;
"udev" -> "mountdevsubfs"[color=springgreen] ;
"mountdevsubfs" [shape=box];
"mountdevsubfs" -> "checkroot"[color=blue] ;
...

... you see, "asplashscreen" is the very first script, and some file system scripts are started afterwards... maybe not a good idea on the new kernel :)