MediaMVP does not start

[KarZan]

So now I have set up a windows server but the MediaMVP loads the dongle from my vdr setup and then connects to the windows server and everything works fine. But of course this is not the way I want But this proves (I think) that my setup should be correct. VDR is even found on the hauppauge software (but not playable).

To test more I used older dongles but the result was the same. I thought that maybe the dongle.bin was broken in Ubuntu repo.

The MediaMVP is still in the last stage leaving the last box white when using vomp-dongles

And I also tested with vomp for windows which also works fine.

What can I do ?

[TEDDYXXL]

After installing DebianSqueeze as a VBOX Client build of a dongle works fine but my mvp (Revision D3A) can't use this dongle with latest version

of vompserver from git.

Dongle is loading but menu doesn't appear.

11:03:24.576750 [debug]  BOOTPD - Starting bootpd
11:03:24.576782 [debug]  BOOTPD - Bootp replier started
11:03:24.576826 [info]   Main - TFTP path '/tftpboot/'
11:03:24.576837 [debug]  Tftpd - Starting TFTPd
11:03:24.576868 [debug]  Tftpd - TFTP server started with base path '/tftpboot/'
11:03:24.576905 [debug]  MVPRelay - MVPRelay replier started
11:03:24.576916 [info]   Main - MVPRelay started
11:03:24.576941 [debug]  Main - MVPServer run success
11:03:24.577182 [debug]  Tftpd - Starting wait
11:03:24.577203 [debug]  BOOTPD - Starting wait
11:03:46.257304 [debug]  BOOTPD - Wait finished
11:03:46.257354 [debug]  BOOTPD - Got request
11:03:46.257393 [debug]  Config - Opened config file: /video0/plugins/vompserver/vomp-00-0D-FE-00-48-F1.conf
11:03:46.257412 [debug]  BOOTPD - Opened config file: /video0/plugins/vompserver/vomp-00-0D-FE-00-48-F1.conf
11:03:46.257492 [debug]  Config - Config error: Key IP not found
11:03:46.257505 [WARN]   BOOTPD - No IP found for MVP. Hopefully it has one already...
11:03:46.257532 [debug]  Config - Config error: Key Override IP not found
11:03:46.257545 [debug]  BOOTPD - Will not change MVP IP if it already has one
11:03:46.257554 [debug]  BOOTPD - Leave YI=0 as MVP already has good IP
11:03:46.257625 [debug]  BOOTPD - Starting wait
11:03:46.388000 [debug]  Tftpd - Wait finished
11:03:46.388053 [debug]  TftpClient - Client handler started
11:03:46.388142 [debug]  Tftpd - Starting wait
11:03:46.388152 [debug]  TftpClient - RRQ received for vomp-dongle
11:03:46.388178 [info]   TftpClient - File: '/tftpboot/vomp-dongle'
11:03:54.027754 [debug]  TftpClient - Retransmitting buffer
11:03:57.039114 [debug]  TftpClient - Retransmitting buffer
11:03:57.691047 [info]   TftpClient - File transfer finished
11:03:57.691121 [info]   TftpClient - processMessage terminating connection

Some lines from my configs:

[Boot]

## If you enable the bootp server in vomp.conf, you can specify
## an IP to give out to this MVP here.

#IP = 192.168.1.29

## If you have a router that gives out addresses but you want
## the above address forced to the MVP, set this:

#Override IP = 1

## A file name to send to the MVP. The MVP will then request
## this file from the TFTP server. Don't use a path here!

TFTP file name = vomp-dongle

[General]
LangCode = en
Remote keys = H00000000I00000000K00H00000001I00000000K01H00000002I00000000K02H00000003I00000000K03H00000004I00000000K04H00000005I00000000K05H00000006I00000000K06H00000007I00000000K07H00000008I00000000K08
H00000009I00000000K09H0000000AI00000000K0AH0000000BI00000000K0BH0000000CI00000000K0CH0000000EI00000000K0EH0000000FI00000000K0FH00000010I00000000K10H00000011I00000000K11H00000012I00000000K12H00000018I0000
0000K18H00000019I00000000K19H0000001AI00000000K1AH0000001BI00000000K1BH0000001CI00000000K1CH0000001EI00000000K1EH00000020I00000000K20H00000021I00000000K21H00000024I00000000K24H00000029I00000000K29H000000
2EI00000000K2EH00000030I00000000K30H00000032I00000000K32H00000034I00000000K34H00000035I00000000K35H00000036I00000000K36H00000037I00000000K37H00000038I00000000K38H0000003BI00000000K3BH0000003CI00000000K3C
H0000003DI00000000K3D
Last Power State = On
PowerOnMode = Menu
VDR shutdown = On
ResumeId = 1
[Media]
ScaleFactor = 1
[TV]
[Advanced]

[General]

## Specify a log file here to enable logging

Log file = /tmp/vompserver.log

## If you have more than one vompserver running you
## can enter a name here that will appear on the
## server select list on the MVP

Server name = LAPPC

## Enable this to start the built in Bootp server
## Required to boot the MVP if you have not got a
## DHCP server that can tell the MVP its boot file
## name and server

Bootp server enabled = yes

## Enable this to start the built in TFTP server
## Required to boot the MVP if you have not got a
## TFTP server running elsewhere

TFTP server enabled = yes

## Base directory for TFTP server
## If you leave this blank the plugin config
## path will be used - i.e. where this file is

TFTP directory = /tftpboot

MVPRelay enabled = yes


Dirk

[KarZan]

Seems quite same behaviour as I have seen. Could you also try to put the hauppauge donge.bin to your tftp server to see if your MediaMVP starts? Just download the setup from hauppauge.lightpath.net/software/mediamvp/mediamvpsetup_34_25345.exe and extract the exe with some zip extractor and find the dongle.bin. Put it in your server and change TFTP file name = vomp-dongle in your vomp-00-0D-FE-00-48-F1.conf file to reflect the file name. No reboot of any kind is needed (you will see the file name change on the "TftpClient - File: '/tftpboot/vomp-dongle'" line in the log).

We have different revisions of MediaMVP but maybe it would show that the problem is in the client software.

[TEDDYXXL]

The dongle.bin from Hauppauge doesn't work here:

Failed to locate GUI Server

But the latest vomp.dongle from yaris (0.3.1-3) works without any problem on my four mvps (2 x E1, 1 x wxmvp H3, 1 x D3A) !

The latest vompserver-version from git loads this vomp.dongle (from yaris) without any problem.

The latest vompserver-version from git doesn't works with dongle.bin which is build from git-vompclient: No menu is shown, only a black screen !

The vompserver-version from yaris doesn't works with dongle.bin which is build from git-vompclient: No menu is shown, only a black screen !


Dirk

[KarZan]

I have vdr-vompclient-mvp (0.3.1.3-0yavdr0~precise) whis does not work on my mvp. It does work on my windows vomp client. I happen to have a raspberry pi and compiled vompclient-raspi from git but it turned out that it needs another version of the server plugin. Which again is not so easy to compile on ubuntu with vdr from the repos Or I did managed to compile it but then my vdr installation complained about it not being compatible on binary level :/

But as said my mvp loads the windows dongle nicely from my vdr server and then connects on windows server. But it does not want to work with any other dongle. It leaves the last box white when loading. Logs shows it has loaded the dongle.