Good day,
a friend of mine got an H4 MediaMVP, I configured VDR, tftp and dhcp, and wonder why it still says failed to contact server.
Does the dongle.bin.vdr that is delivered with the e-tobi packages high enough (i.e. > 1.1.5) to convince the box to download the new dongle.bin?
Any and all help is greatly appreciated.
rgds
Oliver
PS: I have the tftp server setup on the standard tftp server port, plug another tftp server at 16869, and the mvprelad running at 16881 according to nmap.
Hi posde.
You are right.
I tried Version 0.3.0 from tobi with a H4 and it failed to connect unless the version number in the dongle.bin.ver was increased.
Good luck.
ekluba.
Hi again.
Perhaps there ist something else beside the version number ...
What i have done is to create the vomp-dongle-0.3.0.ver from the vomp-dongle-0.3.0 file installed from tobi. I did it with the script
create-dongle-bin-ver.sh from http://www.vdr-wiki.de/wiki/index.php/MediaMVP_-_create-dongle-bin-ver
.
What i have done in steps:
# cp vomp-dongle-0.3.0.ver hd vomp-dongle-0.3.0.ver.tobi
# create-dongle-bin-ver.sh vomp-dongle-0.3.0 vomp-dongle-0.3.0.ver
The resulting files look very different. As follows.
#hd vomp-dongle-0.3.0.ver.tobi
00000000 00 00 00 00 39 40 00 00 01 08 00 00 00 00 00 00 |....9@..........|
00000010 15 89 00 00 01 08 00 00 00 00 00 00 16 89 00 00 |................|
00000020 01 08 00 00 00 00 00 00 |........|
00000028
# hd vomp-dongle-0.3.0.ver
00000000 48 43 57 20 4d 56 50 00 00 00 00 28 00 01 00 00 |HCW MVP....(....|
00000010 01 01 00 00 80 80 ff 03 00 00 00 00 00 00 00 00 |................|
00000020 00 00 00 00 00 00 00 00 |........|
00000028
The mvp now loads the dongle.bin. I can watch live TV and recordings. But there is a problem I didn't had with the old version: Pressing fast forward ends the replay. By now i do not know if this has got something to do with the contents of the dongle.bin.ver.
ekluba
It sounds like the ver file from the e-tobi package is old.
ekluba, you are correct - to get this working the ver file needs to be regenerated from the dongle file. This can be done like this:
dd if=vomp-dongle-0.3.0 of=vomp-dongle-0.3.0.ver bs=1 count=40 skip=52
ekluba: This can't really be anything to do with your fast forward problem. What version of VDR are you using?
OK, great, this just worked fine - but I have a general question:
Why doesn't keep the MVP the dongle in it's own flash memory? Or do you need a special tool to upload the dongle to the flash? Or did I get something competely wrong??
Just wondering,
Lutz
I guess only Hauppauge know how to do that. Also, I think most people would not want to flash 3rd party mod software to the MVP hardware - the way we use it now means that just powering down the MVP returns it to factory state.
It's just because I'm trying to power down alll the standby equipment in my House, and the mvps are always powered up... and I guess, most of the vdr users use it only with their vdrs... but anyhow... just ma 2 cents...
Lutz
Quote from: Chris on August 10, 2008, 18:24:50
It sounds like the ver file from the e-tobi package is old.
ekluba, you are correct - to get this working the ver file needs to be regenerated from the dongle file. This can be done like this:
dd if=vomp-dongle-0.3.0 of=vomp-dongle-0.3.0.ver bs=1 count=40 skip=52
@Chris.
Using
dd if=vomp-dongle-0.3.0 of=vomp-dongle-0.3.0.ver bs=1 count=40 skip=52
didn't work for h3 and h4 in the past if the version number in the mvp was too big. Looking in the 0.3.0 version of dongle.bin it looks as if a maximum version number is used. Is this correct? If so I will change the wiki article appropriately since the above command is a lot easier to use then to download an additional script from somewhere else.
BTW: how will tobi knew it's using the old dongle.bin.ver?
ekluba.
Quote from: Chris on August 10, 2008, 18:24:50
ekluba: This can't really be anything to do with your fast forward problem. What version of VDR are you using?
Everything on my vdr is taken from tobi:
vdr:~# dpkg -l|grep vdr
ii vdr 1.6.0-6ctvdr1 Video Disk Recorder for DVB cards
ii vdr-addon-tvmovie2vdr 0.5.14-1 VDR addon for using online programme guides
ii vdr-plugin-vompserver 0.3.0-2 vdr-plugin for vdr on mediamvp(VOMP)
ii vdr-vompclient-mvp 0.3.0-1 mediamvp client firmware for vomp
ii vdradmin-am 3.6.2-1 Web-based administration tool for vdr
ekluba.
Hi again again.
Now I'am puzzled. Home again after nearly one week if find my mvp able to play fast forward. ???!
The mvp was booted last weekend several times when i tried to find out what was wrong and the vdr was restarted. The only thing that might make the difference is that the vdr hat several reboots within that period. (A server (nslu2) wakes it via WOL before the next recording.)
What did i miss? Any ideas?
Tia.
ekluba.
Thanks guys for the information regarding getting the dongle-ver file created again. I will try that as soon as i get my hands on the mvp again.
Thanks again.
rgds
Oliver
Okay, I downloaded
wget http://www.loggytronic.com/dl/vomp-dongle-0.3.0
and put it into the dir of my tftpserver as dongle.bin
I created a dongle.bin.ver in parallel to that file with the command
dd if=dongle.bin of=dongle.bin.ver bs=1 count=40 skip=52
However, nothing gets loaded from the tftpserver.
My DHCP entries are
host mvp-nds {
filename "/tftpboot/lts/dongle.bin.ver";
hardware ethernet 00:0d:fe:23:80:10;
next-server 10.1.2.5;
fixed-address 10.1.2.74;
}
What do I do wrong? The MediaMVP does get the IP address, but stays on 1.1.50.0
Any and all help is greatly appreciated.
Best regards
Oliver
Is the dongle.bin.ver from etobi really not correct? It should be generated automatically from the dongle. If there is some wrong please tell me and I will fix the package.
Marten