On Mon, 30 Jun 2008, [EMAIL PROTECTED] wrote:
I have the mvpmc set up and it initially boots and loads over wireless.
If I power the MediaMVP down after the mvpmc has successful loaded, and I
power the device back on it works fine. However if I power it off an then
power it back on the next day, once it gets to the step "Creating Setup
Image" it simply reboots.
When you say "power it off" do you mean that you use the green "Power"
button on the remote control? This doesn't actually power down the
MediaMVP, it simply kills part of the mvpmc application that is running on
it, and shuts down its video output. It sounds like something on your MVP
is getting messed up in the interim, most likely eating up lots of memory.
Looking at the code, the only thing that occurs between "Creating setup
image" and "Creating file browser image" is that an image file is read
into memory and converted to the mvpmc's internal format. So it's likely
that there isn't enough memory left to allocate this.
It will continue in this reboot cycle until I
pull the power and reload the application.
Again, it's not actually rebooting here, it's just repeatedly trying to
start the main part of the mvpmc application.
I've tried both with and
without encryption on the wireless link and it does the same thing. I've
tried various version of the dongle.bin file. Right now I have the
nightly build from 20080621. I also have a non-wireless MediaMVP and it
works fine.
Are you using the same dongle.bin and dongle.bin.config for both of these?
The only real difference I can think of here is that the Wireless module
isn't loaded on wired models (or wireless models not using the wireless
interface). This leads to wired models having more memory available, but
the features you're describing would seem to imply that there might be a
memory leak in the wireless module.
Any idea why the mvpmc keeps rebooting and what action I
might need to take. If you have some debugging suggestion I'll take that
also, like is there a way to have mvpmc write out more debug information
to the TV monitor?
The best method for debugging this is going to be to login to the telnet
interface of mvpmc and have a bit of a play around.
Once the first stage of the mvpmc bootup (with the red/green coloured
squares) has completed (well, actually from some point in the middle of
this) you should be able to login to your MediaMVP by simply doing:
telnet <ip address of your mvp>
From here you can use some of the usual unix methods of investigating
memory usage and the like...
Try comparing the output of "top" and "cat /proc/meminfo" shortly after
you've turned the mvpmc application off with the Power button to what it
says after it's been off for a day or so (when you would normally have the
problems).
You can also get a bit more debugging output out of the mvpmc application
itself by killing the version started up by the startup script:
killall mvpmc
and then running it manually with all the same arguments as you have in
your dongle.bin.config-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/
