Messages

Hi.

I just got involved into this theme in vdr-portal.de. Since then i have an idea how to proceed.


To make sure you can prove if i understood it right here is what i assume about the surrounding conditions:

- "HCW_COMPATIBLE_VERSION and HCW_BUILD_VERSION in the kernel patch file" determine the versioning *only* in vompclient's dongle.bin.

- dongle.bin.ver is created after installation from dongle.bin.

- the versioning in dongle.bin.ver ist just a means to force the OS of MediaMVP to load dongle.bin.


If the above is true we should avoid mixing up problems. Let HCW_COMPATIBLE_VERSION and HCW_BUILD_VERSION in the kernel patch file be dedicated to whatever they are now. Maybe vompclient needs to know it's own version number perhaps at least to display it?

Doing so reduces the problem on how to built a usable dongle.bin.ver. This could be done be the attached script. (Cross-posted in vdr-portal.de.) I hope it will prove to be usable for everybody.

Have fun
ekluba.

Chris, avvdr,

thanks a lot to both of you. That is exactly what i have tried to achieve. Glad to here it will work. I will try this perhaps next week. Special thanks to avvdr for posting you configuration. This will help a lot. I will post if it works (or if i need more help )

Have fun.
ekluba.

Hi alltogether.

Mvprelay was compiled and startet on nslu2 as described in http://mvpmc.wikispaces.com/mvprelay. It works exactly as described by Chris. Problem solved.

This way it is a lot more comfortable. You just start mediamvp and leave it alone until the menu appears.

So for now i will concentrate on speeding up the boot process of my vdr machine. Although it seems to me having  the tftp part of vompserver as a separate server (machine) would enhance flexibility and gain more speed. Since i am planning to join the development this might be a good thing to start.

Thank you.

ekluba.

Hi Chris,

thank you for the immediate response. Mvprelay may well solve the problem. Compilation is no problem. There is a fully usable debian on the nslu2. I will try it within the next days and post the result.

ekluba.

Hi alltogether.

Is it possible to load dongle.bin before vdr is running? I have tried google, searched the topics here and vdr-portal but didn't find a solution.

The scenario is as follows:

My local LAN has a central 7x24 server running DHCP and DNS services. To save power this Server runs on a nslu2. My VDR runs on Dell Optiplex GX200. It is started by wake-on-lan from the dhcpd on nslu2 whenever a MediaMVP requests a lease from the DHCP server.

Since it takes a few minutes for VDR to boot, MediaMVP fails to locate the vdr and prompts the user to start a new scan. For me this is not a big problem. But visitors, guests and - that's of course the real problem - my wife don't like it.

Of course there are several workarounds. As always. For the moment i am just adding a MediaMVP to each TV in the household. This means using the existing set top box for live tv and using the MediaMVP to set timers and play recordings.

It would be better to use the streaming client to do all of it. This means: MediaMVP should load the dongle.bin from the nslu2 while VDR is already booting. The loaded dongle.bin then should be able to connect to the VDR as soon at it comes up. Keeping the user informed what is going on.


Any ideas?

TIA.
ekluba.


A short description of my LAN for you information:

- VDR and vdr-vompserver-plugin are running on Dell Optiplex gx200.
- vomp-client runs on MediaMVP H4.
- DHCP and DNS run on nslu2
- DSL is done by fritz!box fon 5140 (with DHCP disabled)