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

H3 boot problem

Started by timbba, July 03, 2009, 05:37:24

Previous topic - Next topic

timbba

Hi,

Has anyone figured out that what might be causing boot failures on H3 Media MVP? I have more or less very unreliable boot process. I have 5% chance to get into vomp client on MVP and booting usually fails to "Loading application" and "Failed to locate GUI server" cycles. On the server side, there are lots of retransmissions on dongle.bin. What is causing this and is there something that can be done to make the boot process more reliable?

DHCP is set on my adsl router, but I have also tried to set it to my VDR box. I also tried to disable built-in tftp on vompserver and tried with another tftp server.. But so far no luck. 5% is the chance that boot succeeds.

I read something about half/full duplex mismatches. So is it so that when MVP has downloaded dongle.bin.ver and dongle.bin, then it reboots and tries to get IP address by DHCP again? Maybe the linkdown is not detected by router/switch and it fails, so is it possible to add some kind of delay to second DHCP request? Or is it possible to put static IP address for the vomp client?

Here are some logs, if someone figures out something from it:
16:39:31.371189 [info]   Main - Logging started
16:39:31.371448 [debug]  UDPReplier - UDP replier started
16:39:31.371773 [debug]  Config - Config error: Key MVPRelay enabled not found
16:39:31.371799 [info]   Main - Not starting Bootpd
16:39:31.371865 [info]   Main - TFTP path '/tftpboot/'
16:39:31.371887 [debug]  Tftpd - Starting TFTPd
16:39:31.371951 [debug]  Tftpd - Starting wait
16:39:31.372011 [debug]  Tftpd - TFTP server started with base path '/tftpboot/'
16:39:31.372078 [debug]  MVPRelay - MVPRelay replier started
16:39:31.372107 [info]   Main - MVPRelay started
16:39:31.372192 [debug]  Main - MVPServer run success
16:40:32.095519 [debug]  MVPRelay - MVPRelay request from 192.168.10.10
16:40:32.095703 [debug]  MVPRelay - Sending my IP as c0a80a02
16:40:33.448758 [debug]  MVPRelay - MVPRelay request from 192.168.10.10
16:40:33.448904 [debug]  MVPRelay - Sending my IP as c0a80a02
16:40:58.215570 [debug]  MVPRelay - MVPRelay request from 192.168.10.10
16:40:58.215709 [debug]  MVPRelay - Sending my IP as c0a80a02
16:40:58.489326 [debug]  MVPRelay - MVPRelay request from 192.168.10.10
16:40:58.489487 [debug]  MVPRelay - Sending my IP as c0a80a02
16:41:00.041668 [debug]  Tftpd - Wait finished
16:41:00.041764 [debug]  TftpClient - Client handler started
16:41:00.041901 [debug]  TftpClient - RRQ received for dongle.bin.ver
16:41:00.041983 [info]   TftpClient - File: '/tftpboot/dongle.bin.ver'
16:41:00.042195 [debug]  Tftpd - Starting wait
16:41:00.143366 [debug]  Tftpd - Wait finished
16:41:00.143462 [debug]  TftpClient - Client handler started
16:41:00.143649 [debug]  TftpClient - RRQ received for dongle.bin
16:41:00.143802 [info]   TftpClient - File: '/tftpboot/dongle.bin'
16:41:00.144263 [debug]  Tftpd - Starting wait
16:41:02.335291 [debug]  TftpClient - Retransmitting buffer
16:41:03.435278 [debug]  TftpClient - Retransmitting buffer
16:41:04.050438 [ERR]    TftpClient - Client sent a data packet!
16:41:04.050534 [info]   TftpClient - processMessage terminating connection
16:41:04.535277 [debug]  TftpClient - Retransmitting buffer
16:41:05.635275 [debug]  TftpClient - Retransmitting buffer
16:41:06.735281 [debug]  TftpClient - Retransmitting buffer
16:41:07.835273 [debug]  TftpClient - Retransmitting buffer
16:41:08.935278 [debug]  TftpClient - Retransmitting buffer
16:41:09.047946 [debug]  Tftpd - Wait finished
16:41:09.048086 [debug]  TftpClient - Client handler started
16:41:09.048228 [debug]  TftpClient - RRQ received for dongle.bin
16:41:09.048282 [info]   TftpClient - File: '/tftpboot/dongle.bin'
16:41:09.049367 [debug]  Tftpd - Starting wait
16:41:10.035276 [debug]  TftpClient - Retransmitting buffer
16:41:11.135270 [debug]  TftpClient - Retransmitting buffer
16:41:11.135420 [debug]  TftpClient - Lost connection, exiting
16:41:22.259277 [debug]  TftpClient - Retransmitting buffer
16:41:22.263237 [ERR]    TftpClient - Client sent a data packet!
16:41:22.263308 [info]   TftpClient - processMessage terminating connection
16:41:27.259220 [debug]  Tftpd - Wait finished
16:41:27.259409 [debug]  TftpClient - Client handler started
16:41:27.259546 [debug]  TftpClient - RRQ received for dongle.bin
16:41:27.259600 [info]   TftpClient - File: '/tftpboot/dongle.bin'
16:41:27.259822 [debug]  Tftpd - Starting wait
16:41:30.379829 [ERR]    TftpClient - Client sent a data packet!
16:41:30.379935 [info]   TftpClient - processMessage terminating connection


Edit: I don't know why it works now, but at least it seems now more stable :).. Maybe when I changed the router, it helped (assumption).