[olympia]

In my setup, usplash starts displaying correctly during the boot process, but it seems doesn't stay on until xbmc starts. It is appearing, then drop back to the console at "Setting preliminary keymap..." stage, which is a pretty early-on message in the boot sequence.

Does anyone have (I know bobb0 do) this issue and a possible reason/fix for that?

It was not like this earlier, but I don't recall which change introduced this behaviour (although I strongly suspect on one of the nvidia driver update).

[queeup]

Good news.

I think we must change usplash start order. Because we use update-rc.d with defaults parameter. Xbmc and usplash both start same time (S20)

@olympia pls try my way. Its work for me.

first change usplash start order: (start usplash after xbmc / stop usplash after xbmc)

Code:

$ sudo update-rc.d -f usplash remove
$ sudo update-rc.d -f usplash start 99 2 3 4 5 . stop 99 0 1 6 .

now modify xbmc init: (so kill usplash after xbmc start not before.)

Code:

start)
        log_action_begin_msg "Starting XBMC"

        # if usplash is running, make sure to stop it now, yes "start" kills it.
        if pidof usplash > /dev/null; then
                DO_NOT_SWITCH_VT=yes /etc/init.d/usplash start
        fi

        /usr/bin/runXBMC.sh &

        log_action_end_msg 0
        ;;

to this

Code:

start)
        log_action_begin_msg "Starting XBMC"

        /usr/bin/runXBMC.sh &

        # if usplash is running, make sure to stop it now, yes "start" kills it.
        if pidof usplash > /dev/null; then
                DO_NOT_SWITCH_VT=yes /etc/init.d/usplash start
        fi

        log_action_end_msg 0
        ;;

[olympia]

Good news.

I think we must change usplash start order. Because we use update-rc.d with defaults parameter. Xbmc and usplash both start same time (S20)

@olympia pls try my way. Its work for me.

first change usplash start order: (start usplash after xbmc / stop usplash after xbmc)

No, it didn't work for me, but in my case, I think it's nothing to do with xbmc start. So it seems that you had a different issue.

As I mentioned, my splash stops displaying at boot stage: "Setting preliminary keymap...", that's very early, far earlier, then xbmc starting to launch.

[queeup]

hmmm then its lirc issue. Whats your lirc start order number?

[olympia]

hmmm then its lirc issue. Whats your lirc start order number?

hmmmm... Thanks for the tip! I will investigate around that a little bit more (although I am using suspend/resume, so I am not seeing that too much )

Unfortunately the next day, I will have some time fot his is Sunday.

(As I mentioned, I didn't experienced this before. Then I had to change my lirc device from MCE new to MCE old to have suspend working, maybe from that time I expereince this bad behaviour)...

SO, thanks again for the promising tip!