Also can't get MVP to work, different symptoms

[cosmocat]

Hi.
I am trying out Sage ( ver 4.1.6 ) and tried out my MVP for the first time today. Absolutely no joy!.

I tried the Hauppauge software on a different machine on the network, all went OK, but when I shut that machine down and reboot the MVP to try out the Sage server it doesn't even get to the "connecting to servers" message, just stops with two large blue squares at the bottom of the screen.

My network uses 192.168.1.x IP addresses, and DHCP is running as a service on my Linux network server. Other clients ( Netgear MP101 ) get assigned IP addresses OK from DHCP.

I have extender enabled in Sage setup menu.

I have been looking around the forum and seen talk of "Clients" folder under SageTV folder, but the folder is missing on my server. I'm guessing that folder holds the MVP boot files etc. so if that whole directory is missing its not going to be able to load the MVP with software.
When does that folder get built, in the installation procedure? what should it contain?
and how do I put it in place

Any suggestions welcome
Thanks

[Opus4]

What is the mask in use by your network? Check the comments on IP address configuration, starting here & continuing with the subsequent posts. You should also check that the extender server is turned on in Detailed Setup -> Advanced. If you have changed that setting w/o restarting the server, toggle the SageTV Server option off & back on also. Another thing is to check your firewall ports.

The Clients subdirectory just holds the extender properties files that get created when it connects, not any startup files, so you aren't missing anything there.

- Andy

[wrwaugh]

Cosmocat
Did you get it going?

[larryf]

Originally Posted by cosmocat

I have been looking around the forum and seen talk of "Clients" folder under SageTV folder, but the folder is missing on my server. I'm guessing that folder holds the MVP boot files etc. so if that whole directory is missing its not going to be able to load the MVP with software.
When does that folder get built, in the installation procedure? what should it contain?
and how do I put it in place

Any suggestions welcome
Thanks

You are the second person here that said the 'clients' folder is missing.... Did you install the 4.1.6 beta first, or did you install it over the 4.1.3 package?

My 'clients' folder had something corrupted, which caused the MVP to power off after loadin the software. I deleted all the files in it, and a new file was created soon after booting the MVP.

Larry

[Opus4]

Originally Posted by larryf

You are the second person here that said the 'clients' folder is missing...

As I said above, the Clients subdirectory just holds the media extender properties files. Nothing gets installed there, so it isn't surprising not to have the directory if the MVP isn't running yet.

- Andy

[cosmocat]

Thanks for your replys.

OK so the client directory gets created after the MVP is setup, I found the MVP.bin file in the Sage directory so all that looks good.

Opus, I have been checking the other posts about IP addressing, I changed my network to 192.168.1.x from 192.168.0.x first thing I tried as other people seemed to find this helped, but no joy.
Forgot to mention in my first post, netmask set to 255.255.255.0, server is running XP + SP2 and the firewall is switched off. This is a clean install of 4.1.6 not over previous versions.

I got a trace out of the Linux DHCP server...
with MVP connected to Sage

DHCPDISCOVER from 00:50:c2:24:5f:ff via eth0
DHCPOFFER on 192.168.1.252 to 00:50:c2:24:5f:ff via eth0
DHCPDISCOVER from 00:50:c2:24:5f:ff via eth0
DHCPOFFER on 192.168.1.252 to 00:50:c2:24:5f:ff via eth0
DHCPDISCOVER from 00:50:c2:24:5f:ff via eth0
DHCPOFFER on 192.168.1.252 to 00:50:c2:24:5f:ff via eth0
...
going round never getting an IP address.


with MVP connected to hauppauge software

DHCPDISCOVER from 00:50:c2:24:5f:ff via eth0
DHCPOFFER on 192.168.1.251 to 00:50:c2:24:5f:ff via eth0
DHCPDISCOVER from 00:50:c2:24:5f:ff via eth0
DHCPOFFER on 192.168.1.254 to 00:50:c2:24:5f:ff via eth0
DHCPREQUEST for 192.168.1.254 (192.168.1.1) from 00:50:c2:24:5f:ff via eth0
DHCPACK on 192.168.1.254 to 00:50:c2:24:5f:ff via eth0

gets IP address and loads MVP software,

I think the DHCP gets to the DHCPREQUEST and DHCPACK after software has been loaded into the MVP.
I also put sage into debug. Other threads show debug messages about the MVP being recognised, but I get nothing, like the Sage TFTP server is not running to recognise that the MVP is even there.
Is ot part of sage .exe or would it appear as a seperate process I could check for in Task manager?

Still scratching my head....
Andrew.

[cosmocat]

Really out of ideas now
Tried reinstalling sage, slowing network card to 10Mb / half duplex.
Got a PC client running - that was OK
Re-installing Java
Uninstalling ALL haupauge software ( wintv2000 was still on the computer but not running)
Many re-boots / restarts of MVP, Sage and Server.
All no joy- Sage will not see the MVP to download its firmware.

With Sage in debug mode there are no messages about the MVP ever

5 days to go before trial runs out, whats is left to try
Will Matts plugin work along side 4.1.6 or will they clash ?

Regards
Andrew.

[Q*bert]

I feel your pain, cosmocat...

I'm the original "Can't get MVP to work..." guy and my trial runs out tomorrow.

I have followed every lead and have gotten no where.

I like what I see in SageTV, but until I can be certain that I can get the MVP to work, I'll hold off.

I'm using GB-PVR with an MVP and it's works great. But I know me, and I'm stubborn enough that I won't be happy until my problems with SageTV are conquered.

[ckron]

Originally Posted by cosmocat

Really out of ideas now
Tried reinstalling sage, slowing network card to 10Mb / half duplex.
Got a PC client running - that was OK
Re-installing Java
Uninstalling ALL haupauge software ( wintv2000 was still on the computer but not running)
Many re-boots / restarts of MVP, Sage and Server.
All no joy- Sage will not see the MVP to download its firmware.

With Sage in debug mode there are no messages about the MVP ever

5 days to go before trial runs out, whats is left to try
Will Matts plugin work along side 4.1.6 or will they clash ?

Regards
Andrew.

I am using Matt's latest client and having great success. I too tried the built in MVP support and got no where. The best part is, Matt's client is FREE!

[cosmocat]

Yeeeeaaaahhhh!!!! Cracked it !!!

I was reading another post about MVP not getting IP address with 4.1.6 and realised they were discribing my symptoms also

http://forums.sagetv.com/forums/show...t=15851&page=3

My Sage.properties file needed tweaking to enable the MVP extender by adding these lines...

miniserver/automvp=true
miniserver/clients=MVP/00:50:c2:24:5f:ff/192.168.1.11
miniserver/gateway=192.168.1.1

00:50:c2:24:5f:ff is the mac address of the MVP
192.168.1.11 is the fixed IP address it was to use.

Also had to add this to my DHCPD.conf file on my linux box DHCP server to assign the IP address to it...

host MVP {
# MVP fixed IP address
hardware ethernet 00:50:c2:24:5f:ff;
fixed-address 192.168.1.11;
}


Beware -- I have a rev D3A MVP and the mac address label on the bottom said a different address ! I got the one to use from my DHCP server debug trace.

Fired up Sage with the new sage.proerties file and MVP fired up straight away!
It seems that 4.1.6 does not initialise these lines properly by default ( well in my installation anyway ) Maybe an update installation would use an old sage.properties file that has this in correctly and so it works, but mine was a virgin install of 4.1.6. and needed the MVP enabled with the tweak.

Anyway Happy now,and wife can watch her Emmerdale in bed!!