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.
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.
Quote from: phenigma on December 02, 2009, 06:26:35 PM
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
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.
I can't get the orbiter to even load, I see the linuxmce is starting screen but thats about it.
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):
...
[ 103.50xxxx] CIFS VFS: Write2 ret -12, wrote 0
...
repeats filling screen
...
And attaching to LMCE_Launch_Manager with screen I see the following:
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):
========== 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.
Quote from: totallymaxed on December 02, 2009, 06:41:34 PM
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.
I installed with the beta2 dvd install.
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.
Follow my post here to get the lastest intel chipset drivers..
http://forum.linuxmce.org/index.php?topic=9149.0
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:
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.
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.
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.
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.
same problem here! any news on that?
thanks
IF
pedplar: all lmce logs are located in /var/log/pluto/* You may want to start with LaunchManager.log, you should be able to find which device is not starting. It would also be a good idea to start another topic for the UI1 video blackout issue. I will try to test this out this weekend sometime and see if I have the same issue.
_if_: Which issue? UI2 not loading or UI1 video blackout during playback?
J.
the UI2 issue, I get the same error: CIFS VFS: Write2 ret -12, wrote 0
to add: last time i tried again and suddenly AVWizard came on. I tried to complete it, but in the middle of the process the screens turned black...
it doesn't matter which one. With ui1 as long as you keep pressing the remote button every 10 or 15 mins its fine. useable. ui2 is very unuseable
ui2 might have the same problem also. I checked LaunchManager.log, thats all that showed up. It still said some devices failed to load
05 12/05/09 2:03:42.674 void ClientSocket::Disconnect() on this socket: 0x9709a40 (m_Socket: 10) <0xb7794b90>
05 12/05/09 2:03:44.501 Requested respawning of new children devices <0xb7794b90>
05 12/05/09 2:03:45.268 Spawning new children devices - media <0xb7794b90>
05 12/05/09 2:03:47.142 Finished spawning new children devices - media <0xb7794b90>
05 12/05/09 2:03:47.169 Finished respawning of new children devices <0xb7794b90>
hey pedplar,
I don't know if you got it already working but I did so today(at least some kind of). UI2 is working for me at 800x600 with 65HZ (not 60 as default) . It's not perfect and I don't know if it's working for you as well, but it's at least something to work with...
greetz
IF
No still not working. ui2 at all, and ui1 not really either
mine neather! it worked for some minutes with ui2 but after a reboot same problem as before... same shitty error message.
I believe here are a view EEE users, are we the only two guys who get this error?
Has anybody any idea where to start?
thanks
IF
I was able to watch 1 movie with ui1. mythtv will only play for a couple minutes before the screen grays out.
Its working with ui2 so far. I ran update and dist-upgrade to get the latest updates. Looks like most if not all were kde updates from ubuntu rrepos, I figured I would try ui2 again. So far, its 30mins into a movie and its still working.
I now made a new clean netinstall (with all new updates) on the core, but still have no success getting the EEE box running as a MD. same CIVS errors again :-(
I am having no problems with ui1. There are issues with ui2 and 0810. The intel drivers will need to be updated and that will likely happen when 1004 is released.
J
the intel drivers were working in 7.10, weren't they? so what's the difference now and aren't a punch of people have it working properly in 8.10 with ui2? (call for EEE users!)
I had it working with ui2 with the latest updates and updated intel driver. But the wife likes ui1 on it better. I fixed the black screen issue I was having by updating the bios to the latest version.
Pedplar: Which driver version did you use and from which source? There's a trac ticket open for this issue that I'd like to update if there is a working scenario.
I also have updated the B202 bios and do not experience the UI1 black screen.
J.
I followed this post http://forum.linuxmce.org/index.php?topic=9149.0. I also used a xorg.conf from my wife's laptop to check if it was just the eee box or intel.
Hmm, I had done that previously without success. That was before I did the bios update on the b202. I'll try it again, if I get it working I'll work to have it implemented.
J.
Have you tried it yet. I went through the av wizard again just to be sure it would work again, and it does.
I've tried just about everything. UI2 boots with your xorg.conf *sometimes*, it still crashes at least 50% of the time. When ui2 does show, the menus are garbled and unusable and there is no PSS showing. This is what I always used to get with ui2 on the b202, this issue is fixed in a newer intel driver but requires a newer ubuntu to install. I'm at a loss. I'll go back to ui1 for now, it doesn't appear that I can get ui2 under any circumstances right now.
J
I also have the hardware acceleration in the web admin set to cle266x11. If I remember thats how I fixed the garbled menu. I also have the pss disabled.
Hi All,
Anyone ever get this working? I recently installed Beta2 and am also having the CIFS VFS error (after the initial Video and Audio wizard and the start of the orbiter generation).
Changing the xorg didn't seem to help. Did the intel driver work for anyone? Anything else to suggest?
Cheers,
WR.
no luck on my side as well...
ui1 is running for some minutes but then suddenly the screen turns black and thats it.
Quote from: wombiroller on January 22, 2010, 02:06:47 PM
Anyone ever get this working? I recently installed Beta2 and am also having the CIFS VFS error (after the initial Video and Audio wizard and the start of the orbiter generation).
Changing the xorg didn't seem to help. Did the intel driver work for anyone? Anything else to suggest?
There is a problem with the 0810 Intel graphics driver which causes OrbiterGL (UI2) to crash. Newer Intel graphics drivers solve the issue but require an upgrade of ubuntu to 0910 or newer (the 1004 drivers work great) so this will not be an issue in LinuxMCE 1004 (the next planned version). I have tried lots of different things with xorg.conf with no success. It is *possible* to upgrade xorg to use a newer version of the Intel driver but all input functionality is killed when you do this so I do not recommend it.
J.
Quote from: _if_ on January 22, 2010, 05:48:55 PM
ui1 is running for some minutes but then suddenly the screen turns black and thats it.
Have you tried updating the EeeBox BIOS? I had this problem but it went away for me when I updated the EeeBox B202 BIOS to the latest version.
J.
thanks a lot, but I would like to use ui2 anyway so it would not be worth the effort...maybe it's an option if nobody comes up with a solution for ui2.
the thing which I don't understand is, why did it work so well in 7.10 and now it doesn't.
Quote from: phenigma on January 22, 2010, 10:27:09 PM
Quote from: wombiroller on January 22, 2010, 02:06:47 PM
Anyone ever get this working? I recently installed Beta2 and am also having the CIFS VFS error (after the initial Video and Audio wizard and the start of the orbiter generation).
Changing the xorg didn't seem to help. Did the intel driver work for anyone? Anything else to suggest?
There is a problem with the 0810 Intel graphics driver which causes OrbiterGL (UI2) to crash. Newer Intel graphics drivers solve the issue but require an upgrade of ubuntu to 0910 or newer (the 1004 drivers work great) so this will not be an issue in LinuxMCE 1004 (the next planned version). I have tried lots of different things with xorg.conf with no success. It is *possible* to upgrade xorg to use a newer version of the Intel driver but all input functionality is killed when you do this so I do not recommend it.
J.
Ouch! That sounds like a nasty bug!
totallymaxed - Is there something fundamentally different with the Dianemo/Cascade builds? You mentioned at the start of the thread you had it working...???
Quote from: _if_ on January 22, 2010, 10:51:45 PM
thanks a lot, but I would like to use ui2 anyway so it would not be worth the effort...maybe it's an option if nobody comes up with a solution for ui2.
the thing which I don't understand is, why did it work so well in 7.10 and now it doesn't.
I consider you lucky if you've ever had UI2 working on Intel graphics in 0710 or 0810. Every time I have tried under 0710 or the 0810 alphas I would always get a garbled screen. Totallymaxed had suggested forcing the video ram to 128mb in BIOS to cure the garbled video problem, there is no option in my EeeBox B202 BIOS for this and xorg is reporting 256mb videoram in it's logs. Somewhere in the late alpha stage UI2 starting causing orbiter to actually crash.
The Intel driver from 0910 or 1004 work great with UI2. I would love to find a way to get it to work in 0810 but I havn't had any success. Hmmm, CVT has ported and compiled orbiter on 0910, I wonder if xorg could be upgraded on an 0810 system and the compiled orbiter binaries dropped in to maintain input functionality.... This is not elegant but *could* work, assuming it doesn't break anything else...
J.
Quote from: phenigma on January 23, 2010, 03:20:37 PM
Quote from: _if_ on January 22, 2010, 10:51:45 PM
thanks a lot, but I would like to use ui2 anyway so it would not be worth the effort...maybe it's an option if nobody comes up with a solution for ui2.
the thing which I don't understand is, why did it work so well in 7.10 and now it doesn't.
I consider you lucky if you've ever had UI2 working on Intel graphics in 0710 or 0810. Every time I have tried under 0710 or the 0810 alphas I would always get a garbled screen.
Actually for the record I had UI2 (masked) running fine for many months in 0710 & the eee box b202...no garble, very rare to have a crash.
I had ui2 on 710 working for months also. I also had ui2 working on 810 for a couple days. Wife likes ui1 better so went back to it.