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

#1
Hello Chris,
I tried this when I testet the mvpmc-dongle and it is always the same. :-(

Can you provide us with a dongle from the current cvs (there should be some changes for the Hx-MVP's). Is this dongle compatible with the vompserver 2.6 on the vdr?

Bye, Uwe.
#2
Hello tycoon96,
do you get the same result on the MVP like me (it stops at loading applications, and the Link LED go off and on again)?

So it seems that I'm not the only one with such a problem. But I think there are some H3-Users in the forum where the MVP is working fine with the VOMP (like sirwo).

Eventually can one of the developers can guide us to debug what the MVP is doing to find a solution for this problem.

Bye, Uwe.
#3
Hello sirwio,

I used also the mvpmc 0.3.1 dongle. I called it a "selfmade" dongle, because it is not a official Hauppauge Dongle using the Hauppauge-Software. Because I do not have any server which the mvpmc-dongle can use there was a message that it did not found a server (after loading applications screen).

And I think that the dongle was not able to finish the boot-proccess because he did not find the server. Should the telnet work without finish booting.

Yes I waited more than 2 minutes untill start the next try.

Bye, Uwe.
#4
Hallo,
I tested the MVP with a mvpmc-dongle to check if a other ("selfmade") dongle is booting. And with this donfle the MVP was booting. I still could not open a telnet session, but I think this is because the software (from the dongle.bin) did not find a GUI-Server and so the boot-process was not finished.

What did I learned: The MVP do not freeze with the mvpmc-dongle  :o, but I still want to use the vomp-dongle  ;D

Any ideas or thinks what I should try on the MVP?

Bye, Uwe.
#5
Hello,

have anyone a idea for my problem? Is the MVP not booting the dongle? Or get the MVP a other IP from the Router (but why the router say that there is no other device in the network)?

Bye, Uwe.
#6
Hello Chris,

after LED turning on again, I could not do a ping to the address and could also not start a telnet session.
Befor turning off the LED I can do a ping to the address. The MVP should have the address 192.168.0.4 and the router say's that there is only this address is used in the network.

Bye, Uwe.
#7
Hello Chris,

I checked the Link-LED (orange LED) when I start the MVP.

Start MVP -> LED off
Checking Network and Locating Server -> LED on
Loading Applications -> LED on
when the MVP freezes, the LED turns off and after 1 second turns on again.

So I think the dongle.bin is booting but then the MVP does nothing.

Kind regards,
Uwe Heinritz.
#8
Hello,

it is definitly a MVP Rev. H3 (this is printed to the label on the back from the MVP).

I can't take a look to the Link-Light until tomorrow, because I don't have the MVP at home (it is connected to the TV from my brother).

Am I the only one who have this problem?

Bye, Uwe.
#9
the dongle.bin.ver is a copy from 40bytes beginning with the 52' byte from dongle.bin.
You can create the file with dd -if=./dongle.bin -of=/dongle.bin.ver bs=1 skip=52 count=40 erstellen.

bye, Uwe.
#10
Hello,

because the vompserver 0.2.5 does not work on the MVP H3 I was waiting for the new version.

Mow I downloaded the source and create a debian-package using the new source code and the debian-folder from a 0.2.5-2 source package. I installed the new package and copied the new dongle.bin (downloaded the new 0.2.6 dongle) into the tftp-folder. I also created a dongle.bin.ver.

Then I started the MVP and selelected the vdr-server. Because the MVP found the server without running the mvprelay I think that the new 0.2.6 vompserver is running well (the windows client work also very fine). Then the MVP did a restart and freezes on the screen "loading applications" 3 bars befor end. I tried it more then 10 times and the MVP freezes always at the same time.

I can see in the log-file that the MVP connect to the VDR, then load the dongle.bin.ver and then try to load the dongle.bin. But when loading the dongle.bin I get some messages from the tftpclient (which were not in the 0.2.5) and then the connection get lost.

Here is the Log-File:

11:20:43.648962 [debug]  MVPRelay - MVPRelay request from 192.168.0.4
11:20:43.649048 [debug]  MVPRelay - Sending my IP as c0a800fc
11:20:45.202741 [debug]  Tftpd - Wait finished
11:22:05.196267 [debug]  TftpClient - Client handler started
11:22:05.196405 [debug]  Tftpd - Starting wait
11:22:05.196457 [debug]  TftpClient - RRQ received for dongle.bin.ver
11:22:05.196494 [info]   TftpClient - File: '/usr/share/vdr-plugin-vompserver/dongle.bin.ver'
11:22:05.198865 [debug]  Tftpd - Wait finished
11:22:05.198938 [debug]  TftpClient - Client handler started
11:22:05.199062 [debug]  Tftpd - Starting wait
11:22:05.199108 [debug]  TftpClient - RRQ received for dongle.bin
11:22:05.199143 [info]   TftpClient - File: '/usr/share/vdr-plugin-vompserver/dongle.bin'
11:22:07.395598 [debug]  TftpClient - Retransmitting buffer
11:22:08.495445 [debug]  TftpClient - Retransmitting buffer
11:22:08.993353 [debug]  TftpClient - Retransmitting buffer
11:22:09.595264 [debug]  TftpClient - Retransmitting buffer
11:22:10.093186 [debug]  TftpClient - Retransmitting buffer
11:22:10.695097 [debug]  TftpClient - Retransmitting buffer
11:22:11.193022 [debug]  TftpClient - Retransmitting buffer
11:22:11.794927 [debug]  TftpClient - Retransmitting buffer
11:22:12.292852 [debug]  TftpClient - Retransmitting buffer
11:22:12.894760 [debug]  TftpClient - Retransmitting buffer
11:22:13.392685 [debug]  TftpClient - Retransmitting buffer
11:22:13.994595 [debug]  TftpClient - Retransmitting buffer
11:22:14.492517 [debug]  TftpClient - Retransmitting buffer
11:22:15.094428 [debug]  TftpClient - Retransmitting buffer
11:22:15.592350 [debug]  TftpClient - Retransmitting buffer
11:22:16.194260 [debug]  TftpClient - Retransmitting buffer
11:22:16.194339 [debug]  TftpClient - Lost connection, exiting
11:22:16.692183 [debug]  TftpClient - Retransmitting buffer
11:22:16.692265 [debug]  TftpClient - Lost connection, exiting


What can I do to get the MVP H3 (not wireless!) running with my VDR (1.4.0 and vompserver 0.2.6-1)?

Kind regards,
Uwe Heinritz.
#11
Hello,
can anyone help me please? I bought a MediaMVP to use it as a thin Client for my VDR (because the Win-Vomp-Client was working well). But now I have the problem that the only hardware-version which was available was the H3.

After trying the Windows-Server, I wanted to try the vdr-plugin-vompserver (version 2.5.1). But with the included dongle.bin the MediaMVP H3 does not boot. In some other threads I read that there are some Patches to get the H3 running.

Can anyone send me a compiled Dongle.bin (which is working with the H3) an the Source for the VompServer (which is compatible with the Dongle.bin)? I can create a Debian-Package from the VompServer-Source by my own, but creating a Dongle.bin is too heavy for me.

Please send me a PrivateMessage if you can help me.

Kind regards,
Uwe Heinritz.