dszego

Hi all, I haven't seen any reference to this here or via Google, but if you go to the Synology firmware download site and poke around, you'll find: https://dedl.synology.com/download/DSM/ ... .0.1/7393/ which is just an Apache index page containing that release for all models. At the bottom of the list, is: DSM_VirtualDSM_7393.pat 06-Jun-2016 06:36 223M So... What's this? A version of DSM made for a VM? It's about the right size... Anyone played with it? There's also: DSM_DockerDSM_7393.pat 06-Jun-2016 06:36 186M Maybe this could be useful? Or I'm being optimistic...

Not sure what to tell you. I got the PCHDTV drivers running by loading them with insmod -v, then looked at dmesg to see what dependancies weren't met, if it loaded OK etc., then using modinfo to see what dependant modules have to be loaded first. Basically you can create a list of what modules to load in what order to get your tuner's module up and running, and edit the S10loadmodules script to put them in the right order (and reverse on the unload line).

Unzip it to the root folder of your Synolog and reboot if it does not load the modules automatically you may need to edit the file in etc which is in the archive

Should be in there... instructions: http://www.linuxtv.org/wiki/index.php/TBS6280

Good prompting... Seems like those drivers are only available as of kernel 3.19, whereas Synology uses 3.10. I built (downloaded and backported) the latest V4L-DVB build as per instructions here: http://www.linuxtv.org/wiki/index.php/H ... ource_Code This let me put in all the latest greatest drivers, so you should be supported. I've updated the link in my post, so: - download it and untar it to the root directory of your NAS, - make sure you somehow run "depmod -a" (if you have an ipkg installed, "ipkg install module-init-tools" will likely put it in /opt/sbin/depmod), - run "start loadmodules" to load them all in. If you're lucky, it'll see your stick - type dmesg|more to find out!

Aaaannnnddd...... Both! =-) So, I've compiled all the "Media" and "USB" drivers as modules. I then wrote a quick script to load the PCHDTV modules in the right order, so you get a /dev/dvb/adapter0/frontend0 for TVHeadend and MythTV to see. Not sure how to make it visible by Video Station - if someone could add to things, that would be awesome. UPDATE: I've added the latest V4L-DVB build as of Oct. 21 2015 and built the backports, along with the firmwares, so you should now have even more media devices supported. Tarball has been updated, same link: The tarball can be downloaded here: https://app.box.com/s/1mldbb7d7lpvncibflyhqivglnkaekgm (31mb) Uncompress it to the root directory of your NAS, it will create: /lib/modules/LotsOfStuff.ko /etc/init/loadmodules.conf /opt/etc/init.d/S10modules /lib/firmware/LotsOfStuff.fw Good luck!

I'm currently downloading the toolchain and source to attempt the driver build as per https://hallard.me/how-to-install-kerne ... 0-dsm-4-1/ under a DebChRoot install, or if that doesn't work I'll try instructions as per http://www.upods.net/building-a-tv-server My goal would be to get MythTV working with my old PCHDTV-3000 card (an ATSC tuner), or at the very least TVHeadend with it. Either way - if it works, I'll compile all the modules available in the kernel, and post them to here. For background, I'm running XPenology directly (no VM) on an Intel SL5000-XVN server motherboard with dual quad-core Xeon 5500's (8 cores) at 1.6GHz, 8Gb RAM, and 6 3Tb WD Red NAS drives directly off the motherboard. If someone else already has the whole kernel compiled - why not upload it? (I can't be the only one trying...) Cheers, David.

Hi all, What should be the proper drive order in BIOS, to make sure that the system partition gets installed in the right place? I have the bootloader on a USB key internally - I believe this is the same as OEM hardware - and I boot off that. Then I've got a SATA card with 2 SSD's on it. One I'm using for cache, one seems just untouched by DSM. On the mobo, I've got 6 SATA ports, which connect to 6 drives that I'm letting DSM handle as my RAID array. However, I see the system partition installed on mobo SATA drive #3, which it then won't let me add to the array. My goal is to have drives in this order: USB-Bootloader PCI SATA SSD #1 - System PCI SATA SSD #2 - Cache Mobo SATA 1-6 - RAID6 array Is there some trick to forcing the system partition to boot off of SSD#1? Should I reinstall the system with only that drive plugged in, then add things afterwards? Thanks, David.

I've got this same problem on mine... But if I ssh in and "dmesg|more" to see the boot logs, I notice that on my 3Ware SATA RAID controller, "write cache not available" or something like that. So, it's probably just an artifact of Synology not having a good way of dealing with cache not being available on a controller, which would never happen on OEM hardware.