Messages

1

Users / Re: Video: Black screen but sound!

« on: August 25, 2011, 11:01:26 pm »

Exactly what I suspected... Alpha rendering in NVidia is broken since

works:
libnvidia-tls.so.260.19.29 => /usr/lib/nvidia-glx-260/tls/libnvidia-tls.so.260.19.29 (0x00352000)
libnvidia-tls.so.270.41.06 => /usr/lib/tls/libnvidia-tls.so.270.41.06 (0x0056e000)
libnvidia-glcore.so.260.19.29 => /usr/lib/nvidia-glx-260/libnvidia-glcore.so.260.19.29 (0x02e64000)
libnvidia-glcore.so.270.41.06 => /usr/lib/libnvidia-glcore.so.270.41.06 (0x12952000)

broken:
libnvidia-tls.so.260.19.29 => /usr/lib/nvidia-glx-260/tls/libnvidia-tls.so.260.19.29 (0x00649000)
libnvidia-tls.so.280.13 => /usr/lib/tls/libnvidia-tls.so.280.13 (0x0056e000)
libnvidia-glcore.so.280.13 => /usr/lib/libnvidia-glcore.so.280.13 (0x1621b000)
libnvidia-glcore.so.260.19.29 => /usr/lib/nvidia-glx-260/libnvidia-glcore.so.260.19.29 (0x023c5000)

@totallymaxed: did you have a chance to further pinpoint the problem in the Orbiter?
IMO it seems that the driver is discarding the alpha byte. I recall a bug in older nvidia drivers that handled values of 255 wrong, maybe we are being hit by something like this.

2

Users / Re: Video: Black screen but sound!

« on: August 22, 2011, 12:23:09 am »

Ah, now we are getting somewhere.
You mean, you have two installations of 10.04 of which only one is affected?

If so, could you please verify that on both the version of OrbiterGL is the same?
File location is /usr/pluto/bin/OrbiterGL
Please paste the output of the following commands.

Code: [Select]

linuxmce:/usr/pluto/bin# ls -al /usr/pluto/bin/OrbiterGL
-rwxr-xr-x 1 root root 2940616 2011-08-17 17:18 /usr/pluto/bin/OrbiterGL

linuxmce:/usr/pluto/bin# ldd /usr/pluto/bin/OrbiterGL
        linux-gate.so.1 =>  (0x00b80000)
        libmysqlclient_r.so.16 => /usr/lib/libmysqlclient_r.so.16 (0x00110000)
        libDCECommon.so => /usr/pluto/lib/libDCECommon.so (0x00306000)
        libSDL_Helpers.so => /usr/pluto/lib/libSDL_Helpers.so (0x009e2000)
        libXtst.so.6 => /usr/lib/libXtst.so.6 (0x00643000)
        libGL.so.1 => /usr/lib/nvidia-glx-260/libGL.so.1 (0x00d5b000)
        libGLU.so.1 => /usr/lib/libGLU.so.1 (0x00aee000)
        libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00651000)
        libXext.so.6 => /usr/lib/libXext.so.6 (0x00f12000)
        libSDL-1.2.so.0 => /usr/lib/libSDL-1.2.so.0 (0x006ba000)
        libSDL_ttf-2.0.so.0 => /usr/lib/libSDL_ttf-2.0.so.0 (0x00984000)
        libSDL_image-1.2.so.0 => /usr/lib/libSDL_image-1.2.so.0 (0x00a5c000)
        libhid.so.0 => /usr/lib/libhid.so.0 (0x00677000)
        libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x00f22000)
        libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x003f6000)
        libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x0048c000)
        libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0x00ca1000)
        libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x004a8000)
        libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x00e50000)
        libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0x004cf000)
        libcairo.so.2 => /usr/lib/libcairo.so.2 (0x004db000)
        libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00555000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00598000)
        libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x007fa000)
        libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00753000)
        libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x0060e000)
        libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x00613000)
        librt.so.1 => /lib/tls/i686/cmov/librt.so.1 (0x00619000)
        libglib-2.0.so.0 => /lib/libglib-2.0.so.0 (0x0082a000)
        libX11.so.6 => /usr/lib/libX11.so.6 (0x00b81000)
        libXmu.so.6 => /usr/lib/libXmu.so.6 (0x00622000)
        libSerializeClass.so => /usr/pluto/lib/libSerializeClass.so (0x00686000)
        libPlutoUtils.so => /usr/pluto/lib/libPlutoUtils.so (0x00792000)
        libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0x0065b000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x1748d000)
        libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0x008f4000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x0091a000)
        libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0x12d6b000)
        libz.so.1 => /lib/libz.so.1 (0x006a4000)
        libusb-0.1.so.4 => /lib/libusb-0.1.so.4 (0x00639000)
        libcrypt.so.1 => /lib/tls/i686/cmov/libcrypt.so.1 (0x00939000)
        libnsl.so.1 => /lib/tls/i686/cmov/libnsl.so.1 (0x0096b000)
        libpng12.so.0 => /lib/libpng12.so.0 (0x009a9000)
        libSDL_gfx.so.13 => /usr/lib/libSDL_gfx.so.13 (0x00e30000)
        libXi.so.6 => /usr/lib/libXi.so.6 (0x009ce000)
        libnvidia-tls.so.260.19.29 => /usr/lib/nvidia-glx-260/tls/libnvidia-tls.so.260.19.29 (0x00649000)
        libnvidia-glcore.so.260.19.29 => /usr/lib/nvidia-glx-260/libnvidia-glcore.so.260.19.29 (0x023c5000)
        libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0x0064b000)
        libasound.so.2 => /usr/lib/libasound.so.2 (0x131f0000)
        libesd.so.0 => /usr/lib/libesd.so.0 (0x009f3000)
        libpulse-simple.so.0 => /usr/lib/libpulse-simple.so.0 (0x007f2000)
        libpulse.so.0 => /usr/lib/libpulse.so.0 (0x009fe000)
        libdirectfb-1.2.so.0 => /usr/lib/libdirectfb-1.2.so.0 (0x00e6a000)
        libfusion-1.2.so.0 => /usr/lib/libfusion-1.2.so.0 (0x00a7c000)
        libdirect-1.2.so.0 => /usr/lib/libdirect-1.2.so.0 (0x00a40000)
        libaa.so.1 => /usr/lib/libaa.so.1 (0x00a86000)
        libncurses.so.5 => /lib/libncurses.so.5 (0x00aa2000)
        libslang.so.2 => /lib/libslang.so.2 (0x1f8ea000)
        libcaca.so.0 => /usr/lib/libcaca.so.0 (0x1b6f4000)
        libtiff.so.4 => /usr/lib/libtiff.so.4 (0x012f7000)
        libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x00b5f000)
        libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x009dc000)
        libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00eff000)
        libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x00ada000)
        libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0x00ae8000)
        libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x00a56000)
        libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00d3f000)
        libpcre.so.3 => /lib/libpcre.so.3 (0x01f66000)
        libresolv.so.2 => /lib/tls/i686/cmov/libresolv.so.2 (0x00d45000)
        libselinux.so.1 => /lib/libselinux.so.1 (0x00ee1000)
        libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x057c2000)
        libxcb-render-util.so.0 => /usr/lib/libxcb-render-util.so.0 (0x00e24000)
        libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0x00e45000)
        libxcb.so.1 => /usr/lib/libxcb.so.1 (0x0dd89000)
        libexpat.so.1 => /lib/libexpat.so.1 (0x1a30f000)
        /lib/ld-linux.so.2 (0x0098c000)
        libXt.so.6 => /usr/lib/libXt.so.6 (0x0731f000)
        libaudiofile.so.0 => /usr/lib/libaudiofile.so.0 (0x07a5e000)
        libpulsecommon-0.9.21.so => /usr/lib/libpulsecommon-0.9.21.so (0x15825000)
        libICE.so.6 => /usr/lib/libICE.so.6 (0x14adb000)
        libSM.so.6 => /usr/lib/libSM.so.6 (0x00f07000)
        libgpm.so.2 => /usr/lib/libgpm.so.2 (0x00e29000)
        libncursesw.so.5 => /lib/libncursesw.so.5 (0x0b900000)
        libXau.so.6 => /usr/lib/libXau.so.6 (0x00ae4000)
        libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x1f586000)
        libwrap.so.0 => /lib/libwrap.so.0 (0x0aeac000)
        libsndfile.so.1 => /usr/lib/libsndfile.so.1 (0x1c8c9000)
        libdbus-1.so.3 => /lib/libdbus-1.so.3 (0x0deff000)
        libuuid.so.1 => /lib/libuuid.so.1 (0x0c1e3000)
        libFLAC.so.8 => /usr/lib/libFLAC.so.8 (0x16f8b000)
        libvorbisenc.so.2 => /usr/lib/libvorbisenc.so.2 (0x1e2a0000)
        libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x0fdb2000)
        libogg.so.0 => /usr/lib/libogg.so.0 (0x1618a000)
This is just to rule out potentional differences between our installations.

I'm currently setting up my installation as chroot'ed build environment and will try to debug the Orbiter in there then (my C++ days are a little back this is my first time building deb packages, was only using slackware until now, where building is a lot more easy as the dependency management is not as restrictive as in debian).
So I am still struggling getting all set (some packages are missing from all the repos, which causes the build scripts to fail)

3

Users / Re: Video: Black screen but sound!

« on: August 21, 2011, 07:45:01 am »

Ok, me again.

Problem "kind of persists".
Did a complete reinstall of 10.04 last evening and it went smoothly.
I could see Sarah for a short moment before the installer came up and the very moment the installer came up, away she was (could hear her still).
I finished the setup as usual (didn't have to see her anyway *g*) and came to the Orbiter in solid shiny black.

In fact all video output and the picture screensaver are affected but let me explain further.

During one startup, I happened to see the picture viewer for a short amount of time, therefore: it is rendering just fine.
So I jumped to console and killed OrbiterGL, picture viewer visible on xfwm4 workspace 3 (switched to it via mousewheel after enabling it via xfwm4-teak-settings).
So far so good, starting the orbiter up again (/usr/bin/screen -d -m -S OnScreen_Orbiter21 /usr/pluto/bin/Spawn_Device.sh 21 localhost LaunchOrbiter.sh) made the orbiter start up again and away went the picture viewer.
I thought it jumped to another workspace and therefore forced xfwm4 to have only one workspace (/root/.config/xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml: <property name="workspace_count" type="int" value="1"/>).
After that, I restarted X via /usr/pluto/bin/Stop_X.sh && /usr/pluto/bin/Start_X.sh but the picture viewer is still hidden "behind" the Orbiter.
Therefore, somehow the OrbiterGL is not rendering transparent but in solid black where transparency should appear.
Could anyone provide me with details of how to debug this issue further?

Regards
Chris

4

Users / Re: Video: Black screen but sound!

« on: August 17, 2011, 10:54:10 pm »

Same problem here.

According to the logs everything is set up just fine but it appears that the pipe vrom xinelib to pluto somehow is broken vor video.
Running the 1004 and getting my hands really dirty by playing around with vdr (no picture in MD also).
So far everything went fine aside from the no video.
Music also plays just fine.

Any guide into any direction is welcome.
Stracing the binaries so far led up to nothing.

Regards
Chris

5

Users / Re: LinuxMCE Users from Germany?

« on: February 14, 2010, 08:34:36 pm »

Ehm.. Tuebingen bei Stuttgart over here.
Looks like I am the Center of all of us.
Same distance to Frankfurt and Munich.

6

Installation issues / Re: hybrid into core on beta 2

« on: January 02, 2010, 02:35:39 pm »

you can still change "/etc/pluto.conf" by hand and alter the flag "AutostartMedia=1" to "AutostartMedia=0".
That way it should not start on your core (at least it does not on mine).

7

Users / Re: 8.10 beta2: VDR not running correctly

« on: January 02, 2010, 11:31:19 am »

Nope, same problem here.
Channel switching causes the vdr display to loose the connection with the vdr daemon.
The daemon tunes to the new channel according to the logs but the image never comes up.
I will have to dig a little more, maybe I can find some better information.

8

Users / Re: DVB Cards info needed for Templates

« on: December 31, 2009, 09:26:40 am »

My MD identified the card correct now.
Unfortunately it did tell me, that it could not determine a provider list.
How can I submit my details? (Provider and channel list)

9

Users / Re: DVB Cards info needed for Templates

« on: December 28, 2009, 11:08:05 pm »

I'm sorry, I did not make myself clear above.
I was able to scan for channels after killing vdr-kbd and put the channels.conf to /etc/vdr/channels.conf (it contains a ton of channels and several more tons of scrambled channels)

After that I rebootet to make sure vdr is coming up normally (what, according to the logs it did).

But vdr from the orbiter insists to have "no signal".
My mentioning of the device being busy above was meant to emphasize that vdr is in fact using the device (keeping it open and therefore restricting other apps from using it).

Sorry for any misunderstanding.

10

Users / Re: What Other Open Source Projects Do You Develop Code For?

« on: December 28, 2009, 06:06:51 pm »

Currently I am a heavy contributor to the TYPOlight CMS. http://www.typolight.org
My efforts include (but are not limited to) integrating all different kinds of APIs and tracking bugs in the core.
Therefore my skills are PHP in there.

I also was (and still am but pretty much retired in the past time) a developer for JEDIVCS, a version control system written in Borland Delphi for Project JEDI.

Aside from that I dig through all variants of OSS projects I use and provide patches and bug reports for stuff I find.

11

Users / Re: DVB Cards info needed for Templates

« on: December 28, 2009, 05:40:54 pm »

technisat cablestar hd2

Code: [Select]

02:0a.0 0480: 1822:4e35 (rev 01)
        Subsystem: 1ae4:0002
        Flags: bus master, medium devsel, latency 64, IRQ 22
        Memory at dfeff000 (32-bit, prefetchable) [size=4K]
        Kernel driver in use: Mantis
        Kernel modules: mantis
Mantis module compiled from http://mercurial.intuxication.org/hg/s2-liplianin (selectively compiled, hence there are a whole lot more drivers included).

Struggeling to make vdr actually use it now. I mean, it does open the device (listed in lsof and I get device is busy when trying to scan for channels while vdr is running) but it says "no signal" when switching to TV on my orbiter.
Any hints are welcome.

12

Users / Re: DVB Cards info needed for Templates

« on: December 20, 2009, 08:22:47 pm »

Code: [Select]

02:0a.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01)
Subsystem: Device 1ae4:0002
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (2000ns min, 63750ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at dfeff000 (32-bit, prefetchable) [size=4K]
Kernel modules: mantis


Code: [Select]

02:0a.0 0480: 1822:4e35 (rev 01)
Subsystem: 1ae4:0002
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at dfeff000 (32-bit, prefetchable) [size=4K]
Kernel modules: mantis

Output from v4l2-ctl will follow after I have recompiled my MD kernel (compiling right now) and I have urged the mantis module to work. Rumor has it, it is working with an older kernel than 2.6.25 and the mantis driver from s2-liplianin but I want to get it to work with the LMCE0810b2 default kernel, therefore I am hacking debug statements in there and it takes time. So please bear with me.

13

Users / Re: Magical dissappearing media!

« on: December 20, 2009, 03:09:06 pm »

On a sidenote, what amount of timeout are we talking about here?

I ask because I see mount and unmount requests on my NFS server every few seconds.
It goes like:

Code: [Select]

Dec 20 15:31:05 valhal mountd[3708]: authenticated mount request from 192.168.10.112:718 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:31:12 valhal mountd[3708]: authenticated mount request from 192.168.10.112:923 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:31:15 valhal mountd[3708]: authenticated mount request from 192.168.10.112:919 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:31:22 valhal mountd[3708]: authenticated mount request from 192.168.10.112:891 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:31:25 valhal mountd[3708]: authenticated mount request from 192.168.10.112:761 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:31:33 valhal mountd[3708]: authenticated mount request from 192.168.10.112:834 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:31:35 valhal mountd[3708]: authenticated mount request from 192.168.10.112:713 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:31:44 valhal mountd[3708]: authenticated mount request from 192.168.10.112:1017 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:31:46 valhal mountd[3708]: authenticated mount request from 192.168.10.112:734 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:31:54 valhal mountd[3708]: authenticated mount request from 192.168.10.112:769 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:31:57 valhal mountd[3708]: authenticated mount request from 192.168.10.112:942 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:32:04 valhal mountd[3708]: authenticated mount request from 192.168.10.112:791 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:32:06 valhal mountd[3708]: authenticated mount request from 192.168.10.112:974 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:32:09 valhal mountd[3708]: authenticated unmount request from 192.168.10.112:869 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:32:14 valhal mountd[3708]: authenticated mount request from 192.168.10.112:756 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:32:16 valhal mountd[3708]: authenticated mount request from 192.168.10.112:897 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:32:25 valhal mountd[3708]: authenticated mount request from 192.168.10.112:801 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:32:28 valhal mountd[3708]: authenticated mount request from 192.168.10.112:668 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:32:34 valhal mountd[3708]: authenticated mount request from 192.168.10.112:831 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:32:38 valhal mountd[3708]: authenticated mount request from 192.168.10.112:797 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:32:46 valhal mountd[3708]: authenticated mount request from 192.168.10.112:716 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:32:50 valhal mountd[3708]: authenticated mount request from 192.168.10.112:893 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:32:59 valhal mountd[3708]: authenticated mount request from 192.168.10.112:850 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:33:00 valhal mountd[3708]: authenticated mount request from 192.168.10.112:720 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:33:02 valhal mountd[3708]: authenticated mount request from 192.168.10.112:750 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:33:10 valhal mountd[3708]: authenticated mount request from 192.168.10.112:1006 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:33:12 valhal mountd[3708]: authenticated mount request from 192.168.10.112:784 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:33:20 valhal mountd[3708]: authenticated mount request from 192.168.10.112:930 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:33:22 valhal mountd[3708]: authenticated mount request from 192.168.10.112:822 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:33:30 valhal mountd[3708]: authenticated mount request from 192.168.10.112:742 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:33:32 valhal mountd[3708]: authenticated mount request from 192.168.10.112:668 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:33:40 valhal mountd[3708]: authenticated mount request from 192.168.10.112:777 for /mnt/data1/movies (/mnt/data1/movies)
Dec 20 15:33:42 valhal mountd[3708]: authenticated mount request from 192.168.10.112:973 for /mnt/data1/movies (/mnt/data1/movies)
As you see, there is a radical imbalance between mount and unmount.

Any ideas how to pinpoint the problem?

14

Users / Re: DVB Cards info needed for Templates

« on: December 20, 2009, 04:30:21 am »

I own a technisat cablestar hd2 which I am currently struggeling to get the kernel module of the mantis drivers to work in LMCE beta2.

I am stuck in hacking my way through the driver code, as currently it produces a kernel Oops when initializing the IR device.

As soon as I get the driver working, I'll be happy to provide a template for this card aswel but as you guys already know, kernel level debugging is a major PITA.

Output from lspci will follow as soon as I have my hands on the testsystem again.

15

Installation issues / Re: [SOLVED] Installed Beta2, but now no Autogenerated Media Scenarios

« on: December 17, 2009, 06:25:10 pm »

Yes, it was an upgrade from alpha to beta. Which I guess is the reason the missing column wasn't added.
But the main Problem was the unhandled "Deleted room" I guess.
I wonder what will happen if I delete the room again but do not want to risk this installation for too much testing.

I think I will have to install another innstallation directly from beta ad try there to add and then delete a room for checking if it also breaks UpdateEntArea.

Regards
Chris