Messages

It's a tricky one, since to do it properly would need a fair bit of GUI work to set the timer or whatever.

Well, I never thought it was going to be easy  As is usual with work suddenly things get hectic and then I don't get to play...

How do you want it to actually operate?

Well, the VDR sleeptimer plugin allows you to either set a time (which defaults to now) to turn off, or a settable number of minutes from now. So I guess something similar would be ideal, though maybe just a choice of a few options would be fine too.

Do you need a sleep timer because you have a TV that has none but will turn itself off after a while of no-signal?

I realise the MVPs don't actually 'poweroff' but yes, my (LCD) TV doesn't have a timer but will poweroff after a few seconds of no signal. I'm quite fond of listening to the radio and usually have the sleeptimer set to 15 mins or so,

(http://sourceforge.net/tracker/index.php?func=detail&aid=1547495&group_id=139484&atid=743658)

The only thing keeping me from using my H3 in the bedroom is lack of a sleeptimer, like my current VDR diskless client has.

I can do a bit of straight 'C' coding amongst other languages, but I know zero about C++. As I don't really expect anybody to jump in to code my every whim for me, I thought I'd have a go myself - at least that should give everyone a good laugh. To get me started in the right direction, could anybody point me in a vague direction to explore 

-Guv

Aha.

Adding some extra logging to mtdmvp.cc I see that /dev/mtd1 cannot be opened. In fact, none of the mtd? can be opened.

Anyone know what module adds support for the /dev/mtd? devices? I see that xrmod.o cannot be loaded ("unresolved symbol register_chrdev_Rffd6b7ed") but I don't think that's the one I want.

TheGuv

Information source for adding H3 support.

Thanks for the info. It's a call for developers fixing the wireless MVP boot problems.

I don't have an actual bootloader problem, I just can't build the dongle as the build system fails. The MVP boots fine with the MVPMC dongle.

TheGuv

Hi all,

I'm trying to get VOMP working on my new flash-based H3 revision MediaMVP.

As the current VOMP development system doesn't seem to be able to create a build due to being unable to extract the filesystem from the the new Hauppauge dongle (dongle_split.pl fails as the new dongle doesn't have a ramdisk based filesystem but, by the looks of it, a Squash FS based one) I'm booting the MVP with the current MVPMC dongle. I thought I'd be sneaky and let it boot this way, then use the fetched config file to kill the mvpmc application and launch vompclient - which I've made available via an NFS mount.

Good try, but I get the following problem with the MTD module:

# /mnt/test/vompclient -d
18:05:00.649040 [info]   Core - Starting up...
18:05:00.719479 [info]   Core - Signal handlers set up successfully
18:05:00.734889 [info]   Core - Remote module initialised
18:05:00.735751 [info]   Core - LED module initialised
18:05:00.736690 [EMERG]  Core - Mtd module failed to initialise
18:05:00.737631 [notice] Core - ViewMan module shut down
18:05:00.738566 [notice] Core - Command module shut down
18:05:00.739407 [notice] Core - VDR module shut down
18:05:00.740152 [notice] Core - OSD module shut down
18:05:00.740708 [notice] Core - Audio module shut down
18:05:00.741246 [notice] Core - Video module shut down
18:05:00.741783 [notice] Core - Timers module shut down
18:05:00.742315 [notice] Core - MTD module shut down
18:05:00.742846 [notice] Core - LED module shut down
18:05:00.743416 [notice] Core - Remote module shut down
18:05:00.743940 [notice] Core - Log module shutting down... bye!

Am I right in believing that the vompclient app is statically linked, and thus has _all_ of the support libraries it needs to work linked in? I've just copied the vompclient binary, did I need anything else?

TheGuv

Still, I can't event get the TFTP

Scrub, that - all is nicely booting now - didn't realise you needed a dhcp and tftp server on wierd ports as well is the normal ones.

MVPMC works very nicely indeed, so at least there's hope. Just need to get a VOMP dongle for this hardware version. Any idea what's needed in the kernel; looks like a video driver issue?

TheGuv

Hi Fourty2,

I'm watching this thread intently at least. I splashed out on *TWO* MVPs after deciding that VOMP is the way I want to go.

I was a bit twitchy when I saw this thread about version H3, and now I'm worried, because both of my MVPs (from different distributors) are H3s that'll teach me! Still, I can't event get the TFTP (I already have dhcpd and a tftp server on the LAN, so don't want to use the inbuilt VOMP ones) to download a dongle, let alone worry that it isn't working...

TheGuv

Hi all,

the GNU_SOURCE define is already in the server plugin Makefile as of version 0.2.4. (It's not on the defines line where I should have put it, but the effect is the same )

I have to concur with Lodda. I too use LinVDR and had the exact same compile error, nicely fixed with the -D_GNU_SOURCE in the plugin's Makefile.

Go figure eh