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

MediaMVP does not complete boot process

Started by keither, January 07, 2013, 00:43:09

Previous topic - Next topic

keither

Hello all,

I used vdr and vompserver in the past and after some years disconnected I'm trying to get it working again. I'm using vdr 1.7.20 and is working fine.
The problem with vompserver 0.3.1 is that the clients are not booting. In the log I see that the dongle is transferred correctly. The last sentence is 'TftpClient - processMessage terminating connection'. In the TV I see how the first 4 of the 5 squares of the progress bar are completed.

I also tried to load the official DONGLE.BIN and the behaviour is exactly the same.
Also, I played with the IP settings of the config files without luck.

What can be wrong?
What can I try to get it working?
Here is the log:

23:49:25.581382 [debug]  BOOTPD - Wait finished
23:49:25.581550 [debug]  BOOTPD - Got request
23:49:25.581747 [debug]  Config - Opened config file: /etc/vdr/plugins/vompserver/vomp-00-0D-FE-00-6E-6E.conf
23:49:25.581792 [debug]  BOOTPD - Opened config file: /etc/vdr/plugins/vompserver/vomp-00-0D-FE-00-6E-6E.conf
23:49:25.582041 [debug]  BOOTPD - Found IP 192.168.1.245 for MVP
23:49:25.582235 [debug]  BOOTPD - Will enforce IP 192.168.1.245 on MVP even if it already has another
23:49:25.582282 [debug]  BOOTPD - Giving MVP IP from config
23:49:25.582675 [debug]  BOOTPD - Starting wait
23:49:25.582831 [debug]  BOOTPD - Wait finished
23:49:25.582869 [debug]  BOOTPD - Got request
23:49:25.583005 [debug]  Config - Opened config file: /etc/vdr/plugins/vompserver/vomp-00-0D-FE-00-6E-6E.conf
23:49:25.583135 [debug]  BOOTPD - Opened config file: /etc/vdr/plugins/vompserver/vomp-00-0D-FE-00-6E-6E.conf
23:49:25.583299 [debug]  BOOTPD - Found IP 192.168.1.245 for MVP
23:49:25.583552 [debug]  BOOTPD - Will enforce IP 192.168.1.245 on MVP even if it already has another
23:49:25.583608 [debug]  BOOTPD - Giving MVP IP from config
23:49:25.583948 [debug]  BOOTPD - Starting wait
23:49:25.713766 [debug]  Tftpd - Wait finished
23:49:25.713916 [debug]  TftpClient - Client handler started
23:49:25.714114 [debug]  Tftpd - Starting wait
23:49:25.714301 [debug]  TftpClient - RRQ received for vomp-dongle
23:49:25.714358 [info]   TftpClient - File: '/tftpboot/vomp-dongle'
23:49:27.916923 [debug]  TftpClient - Retransmitting buffer
23:49:34.944347 [info]   TftpClient - File transfer finished
23:49:34.944559 [info]   TftpClient - processMessage terminating connection


Here is the vomp.conf file

[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 = VDR

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

## Change the following to "no" to disable the
## built in mvprelay server

MVPRelay enabled = yes


And the client configuration:

[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.245

## 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]

## The client auto-detects whether to use PAL or NTSC. If you
## want to force the other one, set it here. Beware of popping
## your TV with this one!

# Override Video Format = NTSC


Thank you very much