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.

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').

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.

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):

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.

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...

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.