News:

Latest versions:
Server plugin: 0.5.1
MVP dongle: 0.5.2
Raspberry Pi client: 0.5.2
Windows client: 0.5.2-1

Main Menu
Menu

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.

Show posts Menu

Messages - rumi

#1
Hi,

I've problems with the last vomp-server 0.3.1-3 and the windows-client 0.3.1-1.

1. Only the first live-tv-channel is available.
2. With recordings in fast-forward/backward.

My MVPs are working fine.

Any hint?

Regards Rumi
#2
Quote from: hondansx on March 11, 2009, 21:10:06
So far I think the problem is vdr 1.6.0-8ctvdr2. You should upgrade or downgrade vdr or change to another vdrdistro.

I downgraded two days ago from 1.6.0-8ctvdr2 to 1.6.0-6ctvdr1 and everything with vomp extension works fine.

Thanks Rumi
#3
VOMP General / MVP / Re: Testers Needed!
July 12, 2008, 16:26:20
@MartenR

It seems to be working fine in my WLAN-Network ... also if the WLAN-connection isn't so good. Then I have dropouts in tone and picture, but the vdr-connection or the vomp-windows-client doesn't crash.

Very good job ... thank you very much.

Rumi
#4
Hi,

my MVPs D3A connected via DLAN 200AVpro are working fine ... only one crash during the last 10 days.

But my MVPs (also D3A) connected via Linksys WAP54 (DD-WRT-Firmware) will crash in less then 1 minute ... LiveTV and playing recordings stop with "lost connection ..." and must be restarted by unplugging power.

EDIT: I'd tuned the connection between the AccessPoint(WAP54) and the Clients (WAP54) and had installed the new released DD-WRT-Firmware v24 on all WAP54s.
Now it is working  :D Thank you for this great software  :D


Any hints ?

Rumi
#5
VOMP General / MVP / D3A can't get dongle.bin
May 14, 2008, 17:02:43
Hello,

I installed the new CVS-vomp with makedevenv-5 on my Ubuntu 8.04 VDR-Server.
I installed the actually VOMp-Server-Plugins.

None of my four MVP-D3A could start.
14:54:18.275117 [debug]  BOOTPD - Wait finished
14:54:18.275236 [debug]  BOOTPD - Got request
14:54:18.275308 [debug]  Config - Opened config file: /var/lib/vdr/plugins/vompserver/vomp-00-0D-FE-00-3F-00.conf
14:54:18.275349 [debug]  BOOTPD - Opened config file: /var/lib/vdr/plugins/vompserver/vomp-00-0D-FE-00-3F-00.conf
14:54:18.275437 [debug]  Config - Config error: Key IP not found
14:54:18.275483 [WARN]   BOOTPD - No IP found for MVP. Hopefully it has one already...
14:54:18.275549 [debug]  Config - Config error: Key Override IP not found
14:54:18.275593 [debug]  BOOTPD - Will not change MVP IP if it already has one
14:54:18.275632 [debug]  BOOTPD - Leave YI=0 as MVP already has good IP
14:54:18.275754 [debug]  BOOTPD - Starting wait
14:54:18.409329 [debug]  Tftpd - Wait finished
14:54:18.409449 [debug]  TftpClient - Client handler started
14:54:18.409546 [debug]  TftpClient - RRQ received for vomp-dongle
14:54:18.409595 [info]   TftpClient - File: '/usr/share/vdr-plugin-vompserver/vomp-dongle'
14:54:18.409713 [debug]  Tftpd - Starting wait
14:54:20.606375 [debug]  TftpClient - Retransmitting buffer
14:54:21.706375 [debug]  TftpClient - Retransmitting buffer
14:54:22.806371 [debug]  TftpClient - Retransmitting buffer
14:54:23.910369 [debug]  TftpClient - Retransmitting buffer
14:54:25.006372 [debug]  TftpClient - Retransmitting buffer
14:54:26.106370 [debug]  TftpClient - Retransmitting buffer
14:54:27.206369 [debug]  TftpClient - Retransmitting buffer
14:54:28.306371 [debug]  TftpClient - Retransmitting buffer
14:54:29.406371 [debug]  TftpClient - Retransmitting buffer
14:54:29.406509 [debug]  TftpClient - Lost connection, exiting

I search in this forum and via google, but do'nt find a hint for my situation.

The vomp 0.2.7 and vdr 1.6.0 from e-tobi are working, but the LiveTV crash so many times a day.
But this should be a known problem ... so I like to try the latest version from CVS.

Any hints ?

rumi
#6
OK ... sorry.
#7
OḰ ... it works.

First I tried on my old machine with Ubuntu 7.10 ... works fine.

Then I tried it a second time on my new VDR-Server ... I don't know why, but now itworks also.

Thanks in advance

rumi
#8
But I'm thinking makedevenv-5 use the gcc-3.4.5 with the crosstool.
#9
den Hinweis auf make ... all habe ich nirgends gefunden.
Und die vorherige Anweisung VDRDIR mit den zwei .. am Ende war auch Bullshit.

Kaum begreiflich, warum VOMP-User so in den Irre geführt werden.

Have a nice day

rumi
#10
Hello,

basically Ubuntu 8.04 amd64, vdr 1.6.0 from e-tobi.

I got with makedevenv-5 after many minutes
/usr/local/src/crosstool/gcc-3.4.5-glibc-2.2.5/powerpc-405-linux-gnu/bin/powerpc-405-linux-gnu-g++ -O3 -Wall -Wshadow -Werror -D_GNU_SOURCE -I../jpeg/jpeg-6b   -c -o vdr.o vdr.cc
vdr.cc: In member function `virtual void VDR::threadMethod()':
vdr.cc:197: warning: 'vresp' might be used uninitialized in this function
make: *** [vdr.o] Fehler 1

What's wrong ?

is asking rumi
#11
Hello,

anybody out there, who will explain me compiling the actual vompserver-vdr-plugin on an amd64-ubuntu-8.04-machine.

I have vdr-dev, gcc 4.2 und vompserver-Sources.

I stored the sources in /usr/local/src/vompserver.
Then I do a make in this directory with 'make VDRDIR=/usr/include/vdr/.. LIBDIR=.' ... but I don't get a libvdr-vompserverso.1.6.0 ... what's wrong ?

Thanks Rumi
#12
VOMP General / MVP / VOMP_MVP network problem ?
March 24, 2007, 15:28:21
Hello,

I have the problem, that the my mvps (3x mvps) don't boot in a new separate class-c-network.
The mvps got there ip and then nothing happend.

This following constellation is working, but I want to splitt the network for better network-performance for the mvps.

192.168.111.x,   Gigabit: 2x SUN Solaris9/10 as router (DMZ) with DNS and DHCP redundant, VDR-Server 1.4.6 Ubuntu 6.10, actual vompserver and client, several other Server MacOS/X, Suse 9.0/9.2, W2k, some Workstation.
192.168.133.x, 100MBit: WLAN with direct network to SUNs and the VDR
192.168.155.x, 100MBit: DLAN (AVpro) only direct network with the VDR

The mvps booting normal in 192.168.111x and 192.168.133.x, but the WLAN is many times to slow, because there are more then 15 wlan-clients (fast enough for them). In 192.168.111.x I have sometimes problems with the mvps, when heavy traffic between the servers (nfs/rsync/backup) is coming up.

That's the reason to put the mvps in a separate network (DLAN 192.168.155.x). With my latop everything is working ... DHCP, DNS, Internet and also the vompclient for windows ... but the mvps stops at the second block of the boot-screen.

They get there ip from the vdr-server via dhcp ... and that's all. Ping is working.

vompserver.log:

13:12:30.250261 [debug]  BOOTPD - Got request
13:12:30.250613 [debug]  Config - Opened config file: /var/lib/vdr/plugins/vomp-00-0D-FE-00-A3-7D.conf
13:12:30.250643 [debug]  BOOTPD - Opened config file: /var/lib/vdr/plugins/vomp-00-0D-FE-00-A3-7D.conf
13:12:30.250745 [debug]  BOOTPD - Found IP 192.168.155.111 for MVP
13:12:30.250809 [debug]  BOOTPD - Will enforce IP 192.168.155.111 on MVP even if it already has another
13:12:30.250832 [debug]  BOOTPD - Giving MVP IP from config
13:12:30.250969 [debug]  BOOTPD - Starting wait
13:12:39.270741 [debug]  BOOTPD - Wait finished

iptraf is reporting udp-packets from the mvps to the vompserver, but the vompserver does'nt answer or send the dongle.bin.

Any hints about whta's going wrong ?

Thanx Michael