[kbriggs346]

thanks for the help i appreciate it.

[Quiptix]

Eventually I moved on to Openelec. Despite my good knowledge of Linux systems I didn't want to admin something at home.

Their Frodo releases quickly follow the officials and suits my hardware perfectly!
Vincent

[lcapriotti]

Would anyone pls try and add the following lines in file /usr/bin/startxbmcbuntu :

Code:

count=1
while [ $count -le 5 ]
do
        if [ -e /proc/asound/cards ]; then
                # echo "ALSA up!"
                break
        fi

        sleep 1
        count=`expr $count + 1`
done

just before the final exec:

Code:

# Start the LXDE session
exec /usr/bin/lxsession -s XBMCbuntu -e LXDE

Tks

[SkyHead]

For some reason I cant create "[" and "]" in sudo nano command
I'm a newb to linux so dunno how

And should I remove the sleep 10 command from /etc/init/lightdm.conf to see if the new fix works by itself?

[PhilipJ]

Would anyone pls try and add the following lines in file /usr/bin/startxbmcbuntu :

Code:

count=1
while [ $count -le 5 ]
do
        if [ -e /proc/asound/cards ]; then
                # echo "ALSA up!"
                break
        fi

        sleep 1
        count=`expr $count + 1`
done

Didn't work for me.
But adding "and stopped udevtrigger" to the "start on" statement in /etc/init/lightdm.conf helped.
As mentioned here: https://bugs.launchpad.net/ubuntu/+sourc...bug/969489

I'm running xbmcbuntu 12.00 on an AT5IONT-I motherboard, off a seagate momentus xt hybrid drive - I didn't have this problem right after installation, only after 2 or 3 reboots (probably when the SSD cache started working).

[lcapriotti]

do you mind to test again increasing the 5 seconds delay to 10 or more?

Code:

while [ $count -le 5 ]

[PhilipJ]

do you mind to test again increasing the 5 seconds delay to 10 or more?

Code:

while [ $count -le 5 ]

well, it seems this script is not even getting executed during boot - I've created a world writeable directory /test/, and put

Code:

count=1
while [ $count -le 30 ]
do
        echo "waiting for ALSA: $count" >> /test/startup.log
        if [ -e /proc/asound/cards ]; then
                echo "ALSA up!" >> /test/startup.log
                break
        fi

        sleep 1
        count=`expr $count + 1`
done

into /usr/bin/startxbmcbuntu right before

Code:

# Start the LXDE session
exec /usr/bin/lxsession -s XBMCbuntu -e LXDE

and no file has been created in /test/...

[un1versal]

Code:

count=1
while [ $count -le 30 ]
do
        touch /test/startup.log
        echo "waiting for ALSA: $count" >> /test/startup.log
        if [ -e /proc/asound/cards ]; then
                echo "ALSA up!" >> /test/startup.log
                break
        fi

        sleep 1
        count=`expr $count + 1`
done

The difference being you touch file before you put stuff inside it. idk Try it.

uNi

[PhilipJ]

Code:

count=1
while [ $count -le 30 ]
do
        touch /test/startup.log
        echo "waiting for ALSA: $count" >> /test/startup.log
        if [ -e /proc/asound/cards ]; then
                echo "ALSA up!" >> /test/startup.log
                break
        fi

        sleep 1
        count=`expr $count + 1`
done

The difference being you touch file before you put stuff inside it. idk Try it.

uNi

That's irrelevant. Redirecting output to a nonexistent file will create the file, ie there's absolutely no need to create it by touch before.
try for yourself:

Code:

echo "foo" >> foo.out

[un1versal]

Sure! In this case creating the file via touch will ensure that your original script is actually being executed too which is likely is not. Sorry for bothering, Ill be out enjoying XBMC.

uNi

[PhilipJ]

Sure! In this case creating the file via touch will ensure that your original script is actually being executed too which is likely is not. Sorry for bothering, Ill be out enjoying XBMC.

uNi

it would be created even without the touch
In fact, touching the file in that loop would mean its timestamp gets updated 2 times per iteration - first time with the touch, second time with the redirected output. Apart from this, it would have no other effect

[Vicious]

The file "/usr/bin/startxbmcbuntu" is for starting the LXDE session, not XBMC so why modify that one?
When autostarting to XBMC with XBMCbuntu the process goes like this:
LightDM starts, if XBMC is set as the default session in /etc/lightdm/lightdm.conf then it executes the corresponding file: /usr/share/xsessions/XBMC.desktop
This file executes xbmc-standalone (/usr/bin/xbmc-standalone).

Either create a new/modify current xsession file that executes a custom script instead of xbmc-standalone or modify /usr/bin/xbmc-standalone.
Modifying startxbmcbuntu won't help.

[lcapriotti]

oops, brain cells did not serve me well

xbmc-standalone is the way to go then

[apeg]

for anyone having this problem, this did the trick for my Veriton N282G

sudo nano /etc/init/lightdm.conf

start on ((filesystem
and runlevel [!06]
and started dbus
and stopped udevtrigger
and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1
or stopped udev-fallback-graphics))
or runlevel PREVLEVEL=S)

The bold line is what to add and where

Good luck,
-aPeg

[fasteddy]

Interesting, I added a 10 second delay, but I'm not thrilled about that kind of a hack. I'll try the line about udevtrigger. Any idea why this works (assuming it does)?