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

Pages: [1] 2 3 ... 9
1
VOMP for Raspberry Pi / Re: No signal from MLD vomp after TV power off
« on: September 03, 2013, 16:28:18 »
Hi,

I have updated the vompclinet of the MLD

Claus

2
VOMP for Raspberry Pi / Re: RPI cleint with IR remote controller
« on: June 26, 2013, 15:08:06 »
Hi,

that is possible, but e.g. my libigorusb reciver don't work correct on the RPI.
If you load the uinput kernel module and start the lirc daemon with the --uinput option, you can control the vompclient by a remote that needs lirc. Your lirc configuration must generate Events of the Linux input namespace.

Claus

3
VOMP for Raspberry Pi / Re: Alternative remotes to CEC
« on: June 26, 2013, 15:01:38 »
Hi Laz,

if you load the uinput kernel modul and start the lirc daemon with the --uinput option, you can control the vompclient ba a remote that needs lirc. Your lirc configuration must generate Events of the Linux input namespace.

Claus

4
VOMP for Raspberry Pi / Re: Raspi Vompclient, no channels?
« on: June 26, 2013, 14:52:25 »
Hi Marten,

I have talked with hlundberg, and his problem was a mistake by entering the mpeg2 license code. Now he has channels in the channel list.

Claus

5
VOMP for Raspberry Pi / Re: vompclient don't start
« on: February 25, 2013, 15:36:27 »
OK, I have kreate a patch, that update the libcec 1.9.0 configure.ac for the actual vc lib.

Claus

6
VOMP for Raspberry Pi / Re: vompclient don't start
« on: February 25, 2013, 10:34:29 »
OK, I found the reason. I have the problem, since I use the version 1.9 of the libcec. This version has a bug, that disable the RPI support. If I try to enable the support by configure switch, I get only a error message. Now I'm locking for a version of the libcec, that can be compile with RPI support and is compatible to the vompclient.

Claus

7
VOMP for Raspberry Pi / Re: sweet RPi port!
« on: February 25, 2013, 09:37:56 »
Hi Tobi,

I'm just looking for the problem with the vompclient on the MLD. I hope to find the reason there for the next days. Until then, you can try the oldest available MLD image (of November 2012), because that still working. You can get it on the download page, if you are hover the download link, and than hover the versions number with your mouse.

Claus

8
VOMP for Raspberry Pi / Re: vompclient don't start
« on: February 06, 2013, 22:26:03 »
Hi,

I have mode no changes on libcec. I use the version 1.9.0, since newer versions don't compile. I use this version since the last half a year.
With the last update, I update also the Kernel to the 3.6.11 (latest version) and the firmware to the latest version. But I think this should not be the problem, since an older version (I compiled in december) runs without problems on this system.

Do you have any further ideas where I do the mistake? If you have no idea, I will try a recompile of the hole system.

Claus

9
VOMP for Raspberry Pi / vompclient don't start
« on: February 05, 2013, 08:50:25 »
Hi Marten,

the latest version of the vompclient don't will start. It only switch for a short time to a black screen. Maybe you have an idea. Here is the log:
Code: [Select]
09:43:16.827874 [info]   2867 Core - Starting up...
09:43:16.831514 [info]   2867 Core - Signal handlers set up successfully
09:43:16.833712 [EMERG]  2867 Core - Could not retrieve free virtual console, please change permissions
09:43:16.836090 [notice] 2867 Remote - Probe /dev/input/event0
09:43:16.838860 [notice] 2867 Remote - Add /dev/input/event0 to List
09:43:16.841269 [notice] 2867 Remote - Probe /dev/input/event1
09:43:16.848807 [notice] 2867 Remote - Add /dev/input/event1 to List
09:43:16.851969 [notice] 2867 Remote - Probe /dev/input/event2
09:43:16.853403 [notice] 2867 Remote - Add /dev/input/event2 to List
09:43:16.854834 [notice] 2867 Remote - Probe /dev/input/event3
09:43:16.856233 [notice] 2867 Remote - Add /dev/input/event3 to List
09:43:16.858477 [notice] 2867 Remote - Probe /dev/input/event4
09:43:16.859913 [notice] 2867 Remote - Add /dev/input/event4 to List
09:43:16.865828 [notice] 2867 Remote - Init LibCEC
09:43:17.407224 [notice] 2867 Remote - CEC: No adapter found
09:43:17.419940 [info]   2867 Core - Remote module initialised
09:43:17.421995 [info]   2867 Core - LED module initialised
09:43:17.423724 [info]   2867 Core - Mtd module initialised
09:43:17.426192 [info]   2867 Core - Timers module initialised
09:43:17.428987 [info]   2867 Core - Read from MTD: PAL 720x576
09:43:17.438584 [debug]  2867 Video - vc_gencmd_send failed ffffffff
09:43:17.440934 [debug]  2867 Video - Setting aspect to 0: PAR 12 11
09:43:17.442446 [notice] 2867 Video - HDMI plugged
09:43:17.443879 [notice] 2867 Video - HDMI set
09:43:17.445652 [notice] 2867 Video - No CEA fall back to DMT modes
09:43:17.447094 [notice] 2867 Remote - Shutdown libcec begin
09:43:17.449712 [debug]  2867 Remote - CECLOG: 447 4 unregistering all CEC clients
09:43:17.459480 [debug]  2867 Remote - CECLOG: 457 4 unregistering all CEC clients
09:43:17.461740 [debug]  2867 Remote - CECLOG: 459 4 unregistering all CEC clients
09:43:17.464968 [notice] 2867 Remote - Shutdown libcec end
09:43:17.466602 [notice] 2867 Video - Switch to prefered mode
09:43:17.469592 [notice] 2867 Remote - Probe /dev/input/event0
09:43:17.476495 [notice] 2867 Remote - Add /dev/input/event0 to List
09:43:17.477906 [notice] 2867 Remote - Probe /dev/input/event1
09:43:17.479151 [notice] 2867 Remote - Add /dev/input/event1 to List
09:43:17.482565 [notice] 2867 Remote - Probe /dev/input/event2
09:43:17.483873 [notice] 2867 Remote - Add /dev/input/event2 to List
09:43:17.485070 [notice] 2867 Remote - Probe /dev/input/event3
09:43:17.486678 [notice] 2867 Remote - Add /dev/input/event3 to List
09:43:17.491467 [notice] 2867 Remote - Probe /dev/input/event4
09:43:17.492687 [notice] 2867 Remote - Add /dev/input/event4 to List
09:43:17.501617 [notice] 2867 Remote - Init LibCEC
09:43:17.899902 [notice] 2867 Remote - CEC: No adapter found
09:43:17.903725 [debug]  2867 Video - Init OMX failed 80001009
09:43:17.908043 [EMERG]  2867 Core - Video module failed to initialise
09:43:17.909970 [notice] 2867 Core - BoxStack module shut down
09:43:17.912302 [notice] 2867 Core - Command module shut down
09:43:17.918988 [notice] 2867 Core - VDR module shut down
09:43:17.921435 [notice] 2867 Core - OSD module shut down
09:43:17.923238 [notice] 2867 Core - Audio module shut down
09:43:17.925044 [notice] 2867 Video - Shutdown video module
09:43:17.926418 [debug]  2867 Video - enter deallocatecodecsomx
09:43:17.932153 [debug]  2867 Video - leave deallocate codecs OMX
09:43:17.955791 [notice] 2867 Core - Video module shut down
09:43:17.956262 [debug]  2867 Timers - Timers shutdown start
09:43:17.958927 [debug]  2867 Timers - Timers shutdown end
09:43:17.968377 [notice] 2867 Core - Timers module shut down
09:43:17.970190 [notice] 2867 Core - MTD module shut down
09:43:17.972555 [notice] 2867 Core - LED module shut down
09:43:17.974653 [notice] 2867 Remote - Shutdown libcec begin
09:43:17.978744 [debug]  2867 Remote - CECLOG: 471 4 unregistering all CEC clients
09:43:17.980213 [debug]  2867 Remote - CECLOG: 472 4 unregistering all CEC clients
09:43:17.982484 [debug]  2867 Remote - CECLOG: 475 4 unregistering all CEC clients
09:43:17.984883 [notice] 2867 Remote - Shutdown libcec end
09:43:17.989092 [notice] 2867 Core - Remote module shut down
09:43:17.990451 [notice] 2867 Core - WOL module shut down
09:43:17.999896 [notice] 2867 Core - Sleeptimer module shut down
09:43:18.001632 [notice] 2867 Core - Log module shutting down... bye!
And here I have the tvservice output:
Code: [Select]
tvservice -m CEA
Group CEA has 14 modes:
           mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive
           mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive
           mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive
           mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive
           mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced
  (native) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive
           mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive
           mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive
           mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive
           mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced
           mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive
           mode 32: 1920x1080 @ 24Hz 16:9, clock:74MHz progressive
           mode 33: 1920x1080 @ 25Hz 16:9, clock:74MHz progressive
           mode 34: 1920x1080 @ 30Hz 16:9, clock:74MHz progressive
The running vompserver is not the latest version. I hope this is not the reason :)

Claus

10
VOMP for Raspberry Pi / Re: Segmentation fault with latest version
« on: November 12, 2012, 09:46:13 »
Hi Marten,

that's no problem, since I give back my borrowed RPI today and not get already my own. I think I will get my own one this or next week. But until next week I will be in vacation for two week, so now you have three weeks to find a solution :)

Claus

11
VOMP for Raspberry Pi / Re: Segmentation fault with latest version
« on: November 11, 2012, 11:05:36 »
OK, this helps. Now the vompclient starts every time correct.

Also the TV do not switch to an other source on vompclinet stop.

Claus

12
VOMP for Raspberry Pi / Re: Segmentation fault with latest version
« on: November 11, 2012, 10:25:25 »
Hi,

OK, now I have made some tests. The kill SIGTERM works. But it makes no different to a kill -9.
I have add your changes and detect, that it helps with a millisleep of 3000 (2000 is to less). If I take a look on the "tvservice -m CEA" output until I start the vompclient, I see, that for about 0.2 Seconds no modes avaliable. In the case, that the start get well, there are two times 0.2 Seconds (with a distance of 0.5 Seconds) no modes available. So I think, it is necessary, to test for some Seconds, if there will be modes available. Or better, if you can found the reason why this filed (now exact) every second try, to fix it if it's possible.

Also I have a other with. If I stop the vompclient, my TV switched to a other input source. If I than switch the TV beck to the hdmi source, I can see the terminal. Is it possible, to let the hdmi source activated on vompclient stop, so that the TV don't switch to an other source?

Claus

13
VOMP for Raspberry Pi / Re: Segmentation fault with latest version
« on: November 09, 2012, 16:34:05 »
Yes, I made a "kill -9" since a SIGTERM do not kill the vompclient in most cases. OK, I try the SIGTERM some weeks ago at last. I will check if a SIGTERM will be better.

Claus

14
VOMP for Raspberry Pi / Re: Segmentation fault with latest version
« on: November 09, 2012, 14:19:07 »
Hi,

with restart I mean to kill and start the vompclient.
I will try your suggestions tomorrow.

Does you power off the hdmi if I kill the vompclient? It seems so, because if I kill it, the TV switched to an other source. If I start the vompclient, the TV switch to the vompclinet hdmi source, but if it fails (about every second try), it switched back to an other source after one second.
On all this tests I only start the vompclient, and do not select a TV channel. Also I have no seg fault with this vompclinet version.

Claus

15
VOMP for Raspberry Pi / Re: Hang when vdr connection lost
« on: November 08, 2012, 19:05:38 »
I also can confirm this.
But I think to remember, that it is possible to select the OK with the keybord and only not with the remote.

Claus

Pages: [1] 2 3 ... 9