Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - phenigma

Pages: 1 ... 60 61 [62] 63 64 ... 69
916
Users / Re: 0810 Beta 2 upgrade experience...
« on: December 03, 2009, 06:59:57 pm »
OK, then I did not have it in there because i did an 0810 beta1 install - or what ?

Sounds right to me.  I believe the beta1 had only the 'testing' repo by default and needed the 'release' repo added manually and then avenard repo changed and mythtv was upgraded to 0.22 in 'release' pretty much the day beta1 was released...  It was a bit of a clusterf**k which was beyond the control of anyone working on LMCE.

J.

917
Users / Re: eee box 202 8.10 beta2
« on: December 03, 2009, 06:55:37 pm »
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: [Select]
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.

918
Users / Re: eee box 202 8.10 beta2
« on: December 03, 2009, 04:15:05 am »
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.

919
Users / Re: eee box 202 8.10 beta2
« on: December 03, 2009, 12:47:22 am »
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.

920
Users / Re: eee box 202 8.10 beta2
« on: December 03, 2009, 12:17:48 am »
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: [Select]
...
[    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: [Select]
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: [Select]
========== 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.

921
Users / Re: eee box 202 8.10 beta2
« on: December 02, 2009, 07:34:33 pm »
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.

922
Users / Re: eee box 202 8.10 beta2
« 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.

923
Users / Re: 0810 Beta 2 upgrade experience...
« on: December 02, 2009, 06:24:11 pm »
Hmm, not sure if that is correctly !? Did you install from the DVD ?

I was upgrading from alpha 2.37 to beta2.  I also did a fresh net install on a virtual machine, I'll be testing a fresh DVD install in a virtual machine this evening when I get home from work.

The current installer is adding the avenard 'release' repo during a net or dvd installation.

From pre-install-from-repo.sh and pre-install-from-dvd.sh
Code: [Select]
AddRepoToSources "http://www.avenard.org/files/ubuntu-repos intrepid release"

J.

924
Users / Re: 0810 Beta 2 upgrade experience...
« on: December 02, 2009, 03:52:34 am »
lmce and avenard are seperate repositories but lmce is using the avenard repositories for nvidia drivers, libvdpau & mythtv.  You should have the avenard 'release' repo in your sources.list.  The lmce repository has also been updated and should automatically be changed during the upgrade to beta2.

J.

925
Users / Re: Wiimotes
« on: December 01, 2009, 05:00:00 pm »
When I was testing my wiimote with lmce there was no 'pairing' of the remote to lmce.  I could use the wiimote with lmce by pressing the 1&2 buttons to activate it (as long as my wii was not on) and then I could still use it with the wii by pressing the power button on the wiimote.  So as long as your wii is off and you don't press the power button you should be able to use it with LMCE or the wii.  YMMV.

J.

926
Installation issues / Re: lmce-mythtv scripts
« on: December 01, 2009, 01:03:20 am »
Orbitergen ran for 1 hour on my p4 2.8 (make sure you wait for it) through all of that time I had a black screen with a white mouse cursor.  After orbitergen finished the media director services did not start up.

I rebooted after orbitergen finished (I watched it running in 'top' from an ssh session) and my system started up perfectly.

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

J.

927
Users / Re: 0810 Beta 2 upgrade experience...
« on: December 01, 2009, 12:55:35 am »
After an hour Orbitergen finished and I am left with a black screen with white mouse cursor.  (My heart sank.)  Both my diskless MDs (not yet updated)  were woken with WOL and seem to function properly.

After I was certain all upgrade activity had ceased I rebooted one more time and orbiter came up just fine.  At first glance everything seems okay and I'm going to update my MDs next.  I think I may do a rebuild on them.

Anyways, still up and running...

J.

928
Users / Re: 0810 Beta 2
« on: November 30, 2009, 11:15:16 pm »
Alright, I was upgrading from Alpha 2.37 and had a minor hiccup during the upgrade.

A mythtv related script has moved from one package to another which has caused an upgrade hiccup.  Here's my experience:

Code: [Select]
# apt-get update
# apt-get dist-upgrade

After downloading for about 45 minutes apt began updating packages but failed, a window opened telling me that "lmce-mythtv-scripts 2.0.0.44.09112922522 had failed to install or upgrade."

So I performed another dist-upgrade and watched the screen as it failed again (and left other packages not upgraded):

Code: [Select]
Unpacking lmce-mythtv-scripts (from .../lmce-mythtv-scripts_2.0.0.44.09112922522_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/lmce-mythtv-scripts_2.0.0.44.09112922522_i386.deb (--unpack):
 trying to overwrite `/usr/pluto/bin/SaveMythRecording.sh', which is also in package pluto-mythtv-player

Now almost all of the packages have been updated but... I performed another dist-upgrade and watched the screen:

Code: [Select]
You might want to run `apt-get -f install' to correct these.
The following packages have unmet dependencies:         
  pluto-mythtv-player: Depends: lmce-mythtv-scripts (>= 2.0.0.44) but it is not installed 
                       Depends: lmce-mythtv-scripts (< 2.0.0.45) but it is not installed           
  pluto-mythtv-plugin: Depends: lmce-mythtv-scripts (>= 2.0.0.44) but it is not installed
                       Depends: lmce-mythtv-scripts (< 2.0.0.45) but it is not installed   
E: Unmet dependencies. Try using -f.             


All other packages have been updated at this point, so then I did an "apt-get -f install" and it installed the lmce-mythtv-scripts package successfully.

I used apt-get, "aptitude dist-upgrade" may have been able to deal with the removal/install ordering better, I'm not sure.

I rebooted and am currently waiting for orbiter to regenerate.

J.

929
Users / 0810 Beta 2 upgrade experience...
« on: November 30, 2009, 09:17:30 pm »
Just did an 'apt-get update' on my core only to find a whole bunch of lmce updates.  

I checked the webpage and it shows LinuxMCE Beta 2.  Congrats on Beta 2 guys!

I'm going to update my core momentarily and report my progress.

J.

930
Installation issues / Re: 0810 and Hauppauge HVR-4000
« on: November 27, 2009, 08:11:49 pm »
LMCE has a script which automaticlly restarts mythbackend when it dies, except when mythtv-setup is running.  The script is:

/usr/pluto/bin/Restart_MythBackend.sh

You will have to kill this script before you stop mythbackend and do your scan or mythbackend will automatically restart and lock your dvb adaptors again.

J.

Pages: 1 ... 60 61 [62] 63 64 ... 69