eee box 202 8.10 beta2

[pedplar]

I can not get the eee box to run with ui2 no matter what.  ui1 at 720p works fine.  is there anything special I need to do to get ui2 working.

[phenigma]

I believe there are still issues with running the Photo screen saver with UI2 on intel graphics adapters.  Either disable the PSS when using UI2 or use UI1.  The incompatibility with intel graphics adapters appears to have been fixed in newer versions of ubuntu/kubuntu so a future release of lmce (1004) should address these issues, but not before.

J.

[totallymaxed]

I believe there are still issues with running the Photo screen saver with UI2 on intel graphics adapters.  Either disable the PSS when using UI2 or use UI1.  The incompatibility with intel graphics adapters appears to have been fixed in newer versions of ubuntu/kubuntu so a future release of lmce (1004) should address these issues, but not before.

J.

We have the PSS & UI2 + Overlay working fine on our Dianemo/Cascade builds using various Intel GPU's... we find that manually forcing the graphics memory to 128K in BIOS is usually a good idea (most BIOS's have this set to 'auto').

All the best

Andrew

[phenigma]

Thanks Andrew, very interesting.  Last I tried I was still having freezing and locking issues with UI2 and PSS active.  I'll check my bios video settings and see what's what.  I've had UI2 and PSS working with the 1.9.0 intel drivers but they require xorg 1.6 and updating breaks mouse and keyboard access in orbiter.

J.

[pedplar]

I can't get the orbiter to even load, I see the linuxmce is starting screen but thats about it.

[phenigma]

Alright, I can confirm this behaviour.  The system crashes after attempting to launch orbiter (after it has finished regenerating).  X crashes and displays the following on vt-1 (which suggests a samba timeout problem... maybe):

Code:

...
[    103.50xxxx]   CIFS VFS: Write2 ret -12, wrote 0
...
repeats filling screen
...

And attaching to LMCE_Launch_Manager with screen I see the following:

Code:

Activating Orbiter...
Orbiter: no process killed
Error: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to autolaunch D-Bus session: Autolaunch error: X11 initialization failed.

Trying Bonobo
Error:
OrbiterGL: no process killed
Orbiter: no process killed
Error: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to autolaunch D-Bus session: Autolaunch error: X11 initialization failed.

Trying Bonobo
Error:

/var/log/pluto/43_LaunchOrbiter.sh.log shows orbiter dying and attempting to restart (it can't since X has crashed):

Code:

========== NEW LOG SECTION ==========
1       12/02/09 17:49:44       43 (spawning-device)    ^[[1;00mStarting... 1^[[1;00m
1       12/02/09 17:49:44       43 (spawning-device)    ^[[1;00mFound /usr/pluto/bin/LaunchOrbiter.sh^[[1;00m
05      12/02/09 17:49:45.515           ^[[33;1mUsing masked UI? YES^[[0m <0xb67ffb90>
Return code: 139
3       12/02/09 17:49:54       43 (spawning-device)    ^[[1;31mDevice died... count=1/50 dev=43^[[1;00m
Wed Dec  2 17:49:54 EST 2009 died
========== NEW LOG SECTION ==========
1       12/02/09 17:50:04       43 (spawning-device)    ^[[1;00mStarting... 2^[[1;00m
1       12/02/09 17:50:04       43 (spawning-device)    ^[[1;00mFound /usr/pluto/bin/LaunchOrbiter.sh^[[1;00m
Return code: 2
2       12/02/09 17:50:10       43 (spawning-device)    ^[[1;33mDevice requests restart... count=2/50 dev=43^[[1;00m
Wed Dec  2 17:50:10 EST 2009 Restart
========== NEW LOG SECTION ==========
1       12/02/09 17:50:18       43 (spawning-device)    ^[[1;00mStarting... 2^[[1;00m
1       12/02/09 17:50:18       43 (spawning-device)    ^[[1;00mFound /usr/pluto/bin/LaunchOrbiter.sh^[[1;00m
Return code: 2
2       12/02/09 17:50:24       43 (spawning-device)    ^[[1;33mDevice requests restart... count=2/50 dev=43^[[1;00m
Wed Dec  2 17:50:24 EST 2009 Restart
...
and it attempts to restart numerous times, the count stays at 2/50 everytime

This really means nothing to me except that X appears to be crashing with orbiter launching.

Did you upgrade to beta2, install the dvd or do a net install?  I upgraded my system from Alpha to beta2, ran Diskless_CreateTBZ and then rebuilt the MD image.

I'll file a trac ticket with this information.  It appears to be UI2 specific.  It would be good to find out if it is the eeebox or any system with intel graphics.

J.

[phenigma]

We have the PSS & UI2 + Overlay working fine on our Dianemo/Cascade builds using various Intel GPU's... we find that manually forcing the graphics memory to 128K in BIOS is usually a good idea (most BIOS's have this set to 'auto').

Hmmm, strangest thing I've seen in a while...  my EeeBox BIOS has absolutely no video information or settings in it at all....  I'm running AMI Bios 0510 (over a year old).  I'm going to look and see if there is an update for the BIOS.

J.

[pedplar]

I installed with the beta2 dvd install.

[phenigma]

I updated to the latest BIOS for the eeebox, 1114 I believe.  No change with UI2.  Still no video settings, I think RAM can be forced with an xorg.conf setting.

J.

[MANDINGO]

Follow my post here to get the lastest intel chipset drivers..

http://forum.linuxmce.org/index.php?topic=9149.0

[phenigma]

Thanks Mandingo for that info, I hadn't done that yet.  However... no joy.  :-(  But, where there was no useful info in the xorg log before I now see this near the end of the log:

Code:

Backtrace:
0: X(xf86SigHandler+0x79) [0x80c3019]
1: [0xb8006400]
2: /usr/lib/xorg/modules/extensions//libdri.so(DRICopyWindow+0xfe) [0xb7ac16de]
3: X(compCopyWindow+0xb4) [0x81424f4]
4: X(miSlideAndSizeWindow+0x743) [0x8128583]
5: X(compResizeWindow+0xb8) [0x81429f8]
6: X(ConfigureWindow+0xb23) [0x80789e3]
7: X(ProcConfigureWindow+0x92) [0x808be42]
8: X(Dispatch+0x34f) [0x808c89f]
9: X(main+0x47d) [0x8071d1d]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7c07685]
11: X [0x8071101]
Saw signal 11.  Server aborting.

Same error showing in LMCE_Launch_Manager window.

I'm going to re-run the avwizard for... fun... ya...  Anyone have any suggestions as to what to try next?

J.

[pedplar]

phenigma, have you tried playing a video file in ui1 yet.  After about 10 minutes, my screen goes black.  The video is still playing because I can hear sound.

[phenigma]

Hmm, I'm still playing with UI2 right now.  I remember something like you describe happening to me on the eeebox before but the machine is almost exclusively used for audio playback so I can't comment right now.  Sounds kinda like the screen saver/power off settings kicking in, try changing the power off time for the orbiter in webadmin, see if that makes a difference...

J.

[pedplar]

I don't think its the screensaver.  I set it to 60 seconds and watched a video for a good 5 minutes.  When I restarted the eee pc I actually watched it boot all the way up.  It said that something failed to start.  Where would I look to see what failed.

[_if_]

same problem here! any news on that?

thanks
IF