MVP boots to black screen when loading Sage UI

[jpaddock3000]

For some reason on only 1 of my 3 mvp's, it is booting into a black screen instead of the normal Sage UI screen. I went ahead and tried booting the MVP using the MVP server software on another computer connected to a different network and it booted into that one just fine. I then renamed the mvp.bin file and called it dongle.bin and again it booted into the black screen using the MVP server software. Any idea what could cause something like this???

Thanks

[gplasky]

Why don't you take that MVP and plug it in at a location where you have one working and see if it makes a difference. If it does then it's a network cable issue. Also try leaving it unplugged from the AC power ofr 15 or more minutes.

Gerry

[jpaddock3000]

Originally Posted by gplasky

Why don't you take that MVP and plug it in at a location where you have one working and see if it makes a difference. If it does then it's a network cable issue. Also try leaving it unplugged from the AC power ofr 15 or more minutes.

Gerry

I actually already tried that. The other extender works great using the same network cable. I have also had the mvp off for a couple of days. Power disconnected.

[carlgar]

Go into the the clients directory within the sage directory and find the properties files that match the problem MVP mac address. Rename or delete the files (the autobackup also), so that Sage will have to recreate them. See if that corrects the problem.

[jpaddock3000]

Originally Posted by carlgar

Go into the the clients directory within the sage directory and find the properties files that match the problem MVP mac address. Rename or delete the files (the autobackup also), so that Sage will have to recreate them. See if that corrects the problem.

I deleted the files and it appears that it just recreated the same file again. I then copied all the settings from a working MVP and put them in the non working MVP settings file and autobackup files. Still same problem.

[carlgar]

Have you verified that you are running the same version of Sage on both systems?

[jpaddock3000]

Originally Posted by carlgar

Have you verified that you are running the same version of Sage on both systems?

The other system wasn't running Sage, only the MediaMVP software.

[carlgar]

What sage version are you using? My speculation is that Sage is not loading the MVP.bin file properly. This was broken in the 6.5 betas. I believe it was fixed in the final release, but I have not tested it. Your other 2 MVP's probably still works because they have not lost power and do not need to reload the MVP.bin file. Did this problem show up because the MVP was in the no power state?

[jpaddock3000]

Originally Posted by carlgar

What sage version are you using? My speculation is that Sage is not loading the MVP.bin file properly. This was broken in the 6.5 betas. I believe it was fixed in the final release, but I have not tested it. Your other 2 MVP's probably still works because they have not lost power and do not need to reload the MVP.bin file. Did this problem show up because the MVP was in the no power state?

I'm using Version 6.5.9. I just installed version 6.4.8 on a VM and the mvp.bin file is the same file size and has the same date as the 6.5.9 version. I don't have an issue if I hard reset any of the other mvp's. They will boot up just fine.

At first I was thinking the mvp might be bad, but since it can boot into the mvp software, I'm thinking it is something else, just don't know what it could be.

Any other ideas?

[carlgar]

Originally Posted by jpaddock3000

I'm using Version 6.5.9. I just installed version 6.4.8 on a VM and the mvp.bin file is the same file size and has the same date as the 6.5.9 version. I don't have an issue if I hard reset any of the other mvp's. They will boot up just fine.

The problem was not with the mvp.bin file itself, it was with the transfer of the file to the MVP. By hard reset do you mean that you remove power for more than 5 mins and then reboot?

I would not trust 6.5.9. I think the released system was 6.5.10 and the current beta is 6.5.11. I think the released system is the best to use. As I recall the transfer was unreliable, every time a new beta came out I would try to boot my MVP. If it worked, I think the problem was solved but then I would have trouble rebooting it. That is why I have not powered off my MVP. I don't know if I would be able to reboot it if I did.

No other ideas, I also doubt if it is hardware.

See post http://forums.sage.tv/forums/showthr...413#post335413
I think the following statement is what fixed the issue.

1. Go back to using 32k buffers by default in the miniclient push
streaming; the data we had about using 64k being better wasn't valid.

[jpaddock3000]

I upgraded to 6.5.11 and it is working like a champ. Thanks so much for all the help.