After installing it, all the hardware works using the Windows application. I can serve the H3 MediaMVP from my Linux box using Windows under Vmware.
But I don't want to run a Windows server on my network. So I have installed mvpboot on Linux which seems to work: syslog:Jan 1 20:52:47 localhost mvpboot[6790]: got mvpboot request packet from 192.168.1.112:2053 (seq=1 id1=babe id2=fafe hwaddr=000dfe0c4950 client_addr=3232235888 client_port=16882 guiserv_addr=0 guiserv_port=0 conserv_addr=0 conserv_port=0 serv_addr=0 serv_port=0) syslog:Jan 1 20:52:47 localhost mvpboot[6790]: client hwaddr: 000dfe0c4950 ip: 192.168.1.112 port: 16882 syslog:Jan 1 20:52:47 localhost mvpboot[6790]: sending mvpboot reply packet to 192.168.1.112:16882 (seq=1 id1=fafe id2=babe hwaddr=0011d8356e73 client_addr=3232235888 client_port=2048 guiserv_addr=3232235777 guiserv_port=5906 conserv_addr=3232235777 conserv_port=6337 serv_addr=3232235777 serv_port=16886) I have also installed tftp server instances on ports 69 and 16869 The logs also show copies of the Windows dongle.bin and dongle.bin.ver being served by tftp from /tftpboot : Jan 1 22:00:02 localhost atftpd[10528]: Advanced Trivial FTP server started (0.7) Jan 1 22:00:02 localhost atftpd[10528]: Serving dongle.bin.ver to 192.168.1.112:2049 Jan 1 22:00:02 localhost atftpd[10528]: Serving dongle.bin to 192.168.1.112:2050 Jan 1 22:00:07 localhost atftpd[10528]: timeout: retrying... Jan 1 22:00:20 localhost last message repeated 5 times The display on the MVP it suggests that it is downloading the application and then it seems to fail to contact the servers ( I guess for the servers/services configured in the Windows specific dongle.bin ). But it seems to keep retrying the mvpboot request: Jan 1 22:00:22 localhost mvpboot[6790]: got mvpboot request packet from 192.168.1.112:2048 (seq=1 id1=babe id2=fafe hwaddr=000dfe0c4950 client_addr=3232235888 client_port=16882 guiserv_addr=0 guiserv_port=0 conserv_addr=0 conserv_port=0 serv_addr=0 serv_port=0) Jan 1 22:00:22 localhost mvpboot[6790]: client hwaddr: 000dfe0c4950 ip: 192.168.1.112 port: 16882 Jan 1 22:00:22 localhost mvpboot[6790]: sending mvpboot reply packet to 192.168.1.112:16882 (seq=1 id1=fafe id2=babe hwaddr=0011d8356e73 client_addr=3232235888 client_port=2048 guiserv_addr=3232235777 guiserv_port=5906 conserv_addr=3232235777 conserv_port=6337 serv_addr=3232235777 serv_port=16886) Attempts to contact 192.168.1.112 using telnet fail, whether the MVP booted from Windows or whether it attempted to load the application from Linux. However, this IP responds to a ping which suggests some functionality has loaded successfully. Would supplying another dongle.bin and dongle.bin.ver from Linux be likely to work ? If so does a set of precompiled files which work on the H3 exist, likely to enable me to prove this all works, prior to my exploring the next stage which will involve supplying a NFS aware client from Linux to the MVP ? Any help or suggestions appreciated. Richard Kay. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
