Running vompclient on MVPMC filesystem

[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

[TheGuv]

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

[Chris]

Hi yes, as you probably are sure now since you have recompiled vompclient, it is statically linked and does contain all the libs it needs, except the jpg files which are in the root of the dongle filesystem.

As you have a dev environment and can compile vompclient, if you want to get it working fast n' dirty you can disable all MTD module stuff in the main.cc file and set the videoFormat variable manually. That's all the MTD module is used for!

I will be looking at the problems with H3s soon, when I get chance to work on vomp again. Of course, if you want to do it all properly and you fix all the problems, let me know!!

Just a heads up to all - when I get started on this I will need lots of user input as I don't have a H3.