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 ... 55 56 [57] 58 59 ... 65
841
On to LinuxMCE related stuff:
- After entering KDE - How can one properly get back to LinuxMCE Orbiter?

There is a package called lmce-activate-orbiter-plasmoid which you could install to add this functionality, it is not installed by default.

Code: [Select]
apt-get install lmce-activate-orbiter-plasmoid

Then right-click on your kde desktop background and choose 'Add Widgets...' and choose 'Activate Orbiter' and it will add the plasmoid to your desktop.  Clicking the plasmoid should return you to the orbiter.  Works for me with UI2 on my core.  YMMV.

J.

842
MAIN QUESTION: How do fellow LinuxMCE users configure MythTV for first time use? (mythtv-setup)

- I've recently learned about /usr/pluto/bin/Restart_MythBackend.sh
How is a user supposed to run mythtv-setup if mythtv-backend can't be stopped without Restart_MythBackend doing its thing?
- In my case, in Belgium, using dvb-t and a Hauppauge HVR-4000 we have to use a workaround to get program information into mythconverg (mc2xml)
- With the new myth 0.22 version, multiple frontends are supported (THANK YOU!!)
However, after killing restart_mythbackend, after stopping myth-backend and entering mythtv-setup, I am
100% able to choose the correct /dev/dvb/adapterN/frontendN. Problem is the adapter is not recognized, so scanning channels is impossible.
- When leaving myth-setup there is a warning like:
Code: [Select]
"Path /home/user_1/data/pvr does not exist" solve?This path off course does exist, but the initial user has no permission...

There is a common misconception, especially for people who are familiar with mythtv, about how to run mythtv-setup in LinuxMCE.  I got stock on this for a long time.

In LinuxMCE mythtv-setup should always be run from the 'Computing' menu in orbiter.

If you do this it will run with the proper permissions and some LinuxMCE script additions will deal with things like Restart_MythBackend automatically for you.  Your file permissions issue with /home/user_1/data/pvr should also be taken care of by running mythtv-setup from the computing menu as it will be running with proper permissions.

J.

843
I know this is digging up an old topic but I've been trying to use this feature to backup my TV and Receiver device templates in 0810b2 and I'm getting some errors and no apparent output file.

The output I'm getting is here: http://pastebin.com/m2039a033

I'm thinking of doing a fresh install and would love to backup these templates first.  Is this working for anyone else right now?

J.

844
Works great!  I was able to play the same divx movie (on CD in the core) on 3 MDs simultaneously with no issues.  I don't have optical drives in any of my MDs yet. Great work!

J.

845
Installation issues / Re: vdpau on ion330
« on: December 04, 2009, 10:26:20 pm »
What format are the files you are playing in?  After reading your post I checked my ION 330.  My ripped .dvd files play fine with vdpau and my .mp4 files play (no proper handling of 5.1 AAC).  Some of my .mkv files play just fine and some have no video or audio, just a black screen.  I believe that xine has known issues with some .mkv format files.

J.

846
Installation issues / Re: vdpau on ion330
« on: December 04, 2009, 09:36:07 pm »
Try looking at /var/log/pluto/XX_Xine_Player.log, on the MD, and see if anything shows there (where XX is the device # that Xine_player starts with on the MD).  I don't know if it will contain anything useful or not.
J.

847
Users / Re: eee box 202 8.10 beta2
« on: December 04, 2009, 09:20:05 pm »
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.

848
Users / Re: eee box 202 8.10 beta2
« on: December 03, 2009, 09:59:05 pm »
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.

849
Installation issues / Re: pluto-orbiter failed to install?
« on: December 03, 2009, 07:10:56 pm »
I had this problem exactly and it was because the avenard 'release' repo was not in /etc/apt/sources.list it was in /etc/apt/sources.list.d/avenard.list (I had put it there manually during alpha days and upgraded to beta2)...  This causes the DisklessCreate_TBZ.sh to fail.  Put the avenard repo /etc/apt/sources.list as posde says and it worked like a charm!

J.

850
Users / Re: 0810 Beta 2 upgrade experience...
« on: December 03, 2009, 07:03:05 pm »
Just to continue my story... I'm trying to troubleshoot a bit of why UI2 is causing X to crash on my EeeBox B202 (intel graphics).  The latest is in this thread: http://forum.linuxmce.org/index.php?topic=9242.0.

J.

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

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

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

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

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

Pages: 1 ... 55 56 [57] 58 59 ... 65