Dvbhdhomerun SPK

[BlueWombat]

Hi.

I'd like to request an SPK for the Dvbhdhomerun driver, as it's proven to be a nightmare for me to compile it on my Ubuntu machine, even though I'm following this tutorial: https://www.lonelycoder.com/redmine/boards/4/topics/3706?r=4330#message-4330.

What could be even cooler is, if a GUI could be made for tuning the device, not anything complicated, just so one woudn't have to open the scan tool via SSH afterwards.

Here's a thred on the QNAP forum discussing the QPKG virtualdj has made of Dvbhdhomerun for the QNAP NAS': http://forum.qnap.com/viewtopic.php?f=276&t=54068&start=165.

Thanks in advance, and keep up the good work.

Mikkel:-)

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[jaredhanks]

+1 for this!

I've tried to compile this on my Synology DS1512+ and DS209j but haven't had any luck. I installed the tvheadend package but can't use it due to not being able to figure out the HDHomeRun/dvbhdhomerun driver compile/install.

[Diaoul]

Spksrc doesn't support building kernel modules for now. This request is gonna be delayed until someone wants to add kernel building modules in spksrc. Along with cross and native there could be a kernel-module directory. Of course this would require to get the GPL source in sources directory.

Lot of work in the framework.

[BlueWombat]

Well, I'm not that experienced in developing for *Nix-based systems, I'm professionally using high-level languages such as C#.Net for Windows, which is very different.

But I know for sure, that with the new DSM 4.1 Beta, they've first of all updated the kernel to 3.x.y.z, and they've also added native support for DVB, as their new Video Station app supports a few different DVB-T tunere.

I did an ls -l on /dev, before starting the Video Station app, and saw that the node /dev/dvb was present. Once you've started Video Station, it actually creates node /dev/dvb/adapter0 /dev/dvb/adapter1 /dev/dvb/adapter2, which seems to be the number of different tuners it currently supports.

Don't know if could be of any help compiling the SPK, that the required modules are already present?

Or if the modules could be prebuilt, and instead of linked to the make file, just hand copied?

Sorry if these questions are dumb, but as I said, I'm not that comfortable in this world yet, hope to be at some point:-)

[Diaoul]

Modules can be loaded dymically. That's what audio station does to recognize USB sound cards for example. I guess video station loads/unloads kernel modules at start/stop too.

I think we'll wait for the release of 4.1 to see if DSM includes the correct kernel modules :) That'd be great

[BlueWombat]

@Diaoul I can confirm that it does, if I look at dmesg I can see that it loads a ton of different USB-DVB drivers, and then as soon as Video Station starts, it creates adpater node 0 through 2.

Unfortunately dmesg dosen't show Dvbhdhomerun, which is most likely because it's not a real driver, more a prxy for sending the different requests on to the userspace application that actually interfaces with the HDHomerun.

But it's definately an improvement:-)

Btw, great jo on the OSCam package. Now all I need is to compile an FTDI driver for my Phoenix reader, as the only prebuilt I could find was for the old 2.6.3.2 kernel.

[henningdalgaard]

Hdhomerun would be great! What is the timeframe for this? I am considering swithching to qnap since they have tvheadend and hdhomerun apps. Thanks for all the great work!

[Diaoul]

Well kernel modules aren't really my cup of tea so I would've to spend a huge amount of time in this. I don't have that much free time. Unless someone else is on it, i'd say a few months. Le 17 juil. 2012 08:32, "henningdalgaard" < reply@reply.github.com> a écrit :

Hdhomerun would be great! What is the timeframe for this? I am considering swithching to qnap since they have tvheadend and hdhomerun apps. Thanks for all the great work!

---

Reply to this email directly or view it on GitHub: https://github.com/SynoCommunity/spksrc/issues/161#issuecomment-7027755

[BlueWombat]

@henningdalgaard I won't assign myself to this issue, as I'm not guaranteeing Ican get this thing working myself, but I'm on it. First is to get it to compile to start with, which currently isn't possible for me, as I have the new beta, with a newer kernel, and the GPL Source for that isn't released by Synology before it makes it out of beta.

But my plan is to compile this, get it running, and afterwards try and make it an SPK. I'll probably be doing the same for the USB to Serial driver needed for my Phoenix Smartmouse for OSCam.

The big question is, if I can figure out a way to circumvent the fact that Spksrc currently dosen't take the kernel parameter. If I can precompile the modules and just include them in some way, or easily modify the Spksrc tool.

[Diaoul]

The idea is to have spksrc handle the cross compilation of kernel modules itself, not include binaries built someplace else. Anyway, this could be a start :)

[Jeroenve]

@sirgadget only the kernel for the high-end DS are upgraded to 3.2.11.

The Linux kernel has been updated to 3.2.11 on the following models: DS712+, DS1512+, DS1812+, DS3612xs, RS3412xs, RS3412RPxs, DS412+, RS812+, RS812RP+, RS2212+, RS2212RP+, RS3411xs, RS3411RPxs, RS2211+, RS2211RP+, DS3611xs, DS2411+, DS1511+, DS411+II, DS411+, DS810+, RS810RP+, DS1010+ and DS710+.

[BlueWombat]

@Jeroenve Okay, but I have a DS1010+, which is a hign-end model, so nonetheless, I'm still waiting for the source:-)

Unless I can just download the kernel alone, but doubt it'll work only copying the configuration file needed for my DS, as I suspect Synology have done a lot more than just changing a config file.

[BlueWombat]

@Diaoul Yeah, you gotta crawl before you can walk^^ I'll try and get it working. Currently this really issue with my ubuntu distro. For some reason whenever I run make on the Synology source (for DSM 4.0), it for some reason can not load all the utils in the compiler directory, only the compiler itself. This makes the Makefile fail miserably, and me not getting any binaries:-(

Though I do an ls -l on the folder, and verify they're all there, with same permissions, it just gives me an The file or directory could not be found.

And I'm stuck.

[henningdalgaard]

okay, so you think that at some point it will be possible to have tvheadend with hdhomerun on the synology (211+). And that my xbmc will be able to use that as a backend to whatch tv. I understand it is hard to predict, but do you think this will happen in 2012? Thanks again for all your great work

[BlueWombat]

@henningdalgaard I already know of several people doing it right now. But they've all compiled the driver themselves, could possibly get one of them to realease their binaries, they're only a few kilobytes. But the cool thing would of course be to have them as an SPK, even cooler with a little interface for tuning, setting tuner type, etc.

[tougher]

Check this one http://forum.synology.com/enu/viewtopic.php?f=190&t=55075. It's work in progress and I can't find any kernel modules for x86 NAS's, the QNAP ones does not work (different kernel versions i guess).

[Valdimarsson]

I can personally vouch for the hdhomerun driver @tougher is referring to. I'm using it right now ;) And it has the feature to set the tuner too :)

[BlueWombat]

@tougher I've tried and compiling the drivers both on my Ubuntu machine, and directly on my NA. Just realized today that I used the wrong toolchain, I'll try in couple with a different toolchain, and see if that solves the problem.

The issue isn't that kernels aren't compatible, itøs because the kernel modules should be 64-bit, while the userspace part is 32-bit, which results in an error.

I'll get back later.

[BlueWombat]

@tougher Also, when you have a working spk, compatible with most variations of our NAS's, you really should add it to the SynoCommunity repo, it would be awesome to have it together, meaning anyone in here could also progress the development on the excellent spk you've created:-)

[Valdimarsson]

That's good thinking @sirgadget . Just me or is this tvheadend + hdhomerun only associated with Denmark ;) Wherever I look it's almost exclusively Danish guys trying to compile and create :)

another thing. I read that you @sirgadget tried to get xmltv "ontv" to work with the tvheadend. Did you succeed? I've tried all the same things as you but to no avail and tried a couple of other things. Right now it looks exactly what yours ls -l looks like with chown and chmod. I don't know what I did wrong but for a couple of minutes ago my var/log/messages says this: Aug 21 12:09:24 tvheadend[17229]: spawn: pid 17229 cannot execute /usr/local/bin/tv_grab_file -- Exec format error ? Have you ever seen that?

[tougher]

@sirgadget my package is still to unstable and does not support x86. If you manage to get working modules for your NAS (dvb_core.ko, dvb_hdhomerun_core.ko, dvb_hdhomerun_fe.ko and dvb_hdhomerun.ko), please let me know.

[BlueWombat]

@Valdimarsson Well, I think our main "problem" is, that it seems more of us Danes have chosen the bigger Intel based models, but you're right, we're a lot of Danes trying this out:-) Ont he log message, I haven't noticed it, but will try and look for it, I never did get it to work unfortunately:-(

@tougher I definately will:-) On a said note, you could branch this repo, and merge it back later, when everything is sorted out:-) Do you have any version control on what you're doing now? If I could contribute with anytihing? You're also welcome to get SSH to my box, I trust you won't snoop around my files;-)

Also note that there're currently four different toolchains for INtel, depneding on which CPU you have, the Pinewview, the Cedarview, the Bromolow and a generic, the last one is probably for the new i3 based devices. My DS1010+ is a D510 (Pineview), according to what I could find:-)

[tougher]

@sirgadget right now I'm in the state of trial and error :-)

I don't think we are able to build the modules in the NAS itself, but thanks for the trust :-) Is this http://sourceforge.net/projects/dsgpl/files/DSM%204.0%20Tool%20Chains/Intel%20x86%20Linux%202.6.32%20%28Pineview%29/ the version for you NAS? Does the kernel version (2.6.32) still match?

[BlueWombat]

@tougher I am able to compile it all directly on my NAS, with the above mentioned toolchain. Unfortunately, it still dosen't work.

No my kernel is 3.2.11, this happened with DSM 4.1 beta for Intel. So what I did was, that I downloaded a fresh kernel off of kernel.org, and copied the config file from the GPL source of the 4.0, and compile it.

Everything works, accept being able to userhdhomerun/hdhomerun_config from the driver, because of the isctl32 error:-(

I have no idea how to circumvent this:-/

It's worth noting, that the USBSerial drivers I compiled, work great, so does any other kernel module, everything accept the DVBHDhomerun driver, because of the mixed architectures, it's so frustrating!:-(

[tougher]

What does a insmod dvb-core.ko gives?

[BlueWombat]

@tougher Actually nothing, dmesg dosen't report anything...

[tougher]

@sirgadget nothing means that it's loaded :-) What about lsmod? Does _dvb_hdhomeruncore.ko, _dvb_hdhomerunfe.ko and _dvbhdhomerun.ko also gives nothing?

I have this in my start script:

    MODULES_LOADED=$(lsmod | grep dvb_hdhomerun)
    if [ "$MODULES_LOADED" = "" ]; then
        insmod ${INSTALL_DIR}/dvb_core.ko
        insmod ${INSTALL_DIR}/dvb_hdhomerun_core.ko
        insmod ${INSTALL_DIR}/dvb_hdhomerun_fe.ko
        insmod ${INSTALL_DIR}/dvb_hdhomerun.ko
    fi

[BlueWombat]

@tougher This is result of dmesg:

[ 3638.692110] HDHomeRun: Begin exit [ 3638.696036] HDHomeRun: End exit [ 8690.495684] HDHomeRun: Begin init, version 0.0.10 [ 8690.500973] HDHomeRun: Waiting for userspace to connect [ 8690.506253] HDHomeRun: End init

Subsequently I get

[ 8690.981462] ioctl32(userhdhomerun:15855): Unknown cmd fd(3) cmd(c01c7600){t:'v';sz:28} arg(fffaa554) on /dev/hdhomerun_control [ 8690.993121] ioctl32(userhdhomerun:15855): Unknown cmd fd(4) cmd(c01c7600){t:'v';sz:28} arg(fffaa554) on /dev/hdhomerun_control

lsmod says:

dvb_hdhomerun 10670 0 dvb_hdhomerun_fe 6028 1 dvb_hdhomerun dvb_hdhomerun_core 2131 2 dvb_hdhomerun,dvb_hdhomerun_fe dvb_core 85394 1 dvb_hdhomerun

cat /opt/dvbhdhomerun/dvbhdhomerun.log: Running as user: root Num of devices = 1 Device 1220b9c8 is type 1 and has 2 tuners Name of device: 1220B9C8-0 Auto detecting tuner type Type of device: hdhomerun3_dvbtc Tuner: 0 Set initial pass-all filter for tuner: 1 Name of device: 1220B9C8-1 Auto detecting tuner type Type of device: hdhomerun3_dvbtc Tuner: 1 Set initial pass-all filter for tuner: 1 Couldn't create tuner! ioctl failed. This means the kernel module is either not loaded or has malfunctioned. Check dmesg. Couldn't create tuner! ioctl failed. This means the kernel module is either not loaded or has malfunctioned. Check dmesg.

[BlueWombat]

@tougher My startup script (/opt/etv/init.d/S51dvbhdhomerun)

-

-- create device nodes for HDHomerun

mkdir -p /dev/dvb/adapter3 mknod /dev/dvb/adapter3/demux0 c 212 0 mknod /dev/dvb/adapter3/dvr0 c 212 1 mknod /dev/dvb/adapter3/frontend0 c 212 2 mkdir -p /dev/dvb/adapter4 mknod /dev/dvb/adapter4/demux0 c 212 3 mknod /dev/dvb/adapter4/dvr0 c 212 4 mknod /dev/dvb/adapter4/frontend0 c 212 5

-

-- set permissions

chmod 755 /dev/dvb/adapter* chmod 666 /dev/dvb/adapter/ chown root:root /dev/dvb/adapter/

-

insmod /opt/lib/modules/3.2.11/dvb-core.ko insmod /opt/lib/modules/3.2.11/dvb_hdhomerun_core.ko insmod /opt/lib/modules/3.2.11/dvb_hdhomerun_fe.ko insmod /opt/lib/modules/3.2.11/dvb_hdhomerun.ko

-

DYNAMIC_ID=$(grep -e hdhomerun_control /proc/misc | awk "{print \$1}") if [ "$DYNAMIC_ID" != "" ]; then echo "making node hdhomerun_control" $DYNAMIC_ID mknod /dev/hdhomerun_control c 10 $DYNAMIC_ID else echo "Unable to detect hdhomerun_control inside /proc/misc." fi

-

-- set permissions

chmod 666 /dev/hdhomerun_control chown root:root /dev/hdhomerun_control

-

-- clear userhdhomerun log

rm -f "/opt/dvbhdhomerun/dvbhdhomerun.log"

-

-- run userhdhomerun with LD_PRELOAD

-- (because libhdhomerun.so is inside dvbhdhomerun folder)

/opt/dvbhdhomerun/userhdhomerun/build/userhdhomerun -f -u root -g root -l "/opt/dvbhdhomerun/dvbhdhomerun.log"

-

sleep 1

-

DYNAMIC_ID=$(grep -e hdhomerun_data /proc/devices | awk "{print \$1}") if [ "$DYNAMIC_ID" != "" ]; then echo "making node hdhomerun_data" $DYNAMIC_ID mknod /dev/hdhomerun_data0 c $DYNAMIC_ID 0 mknod /dev/hdhomerun_data1 c $DYNAMIC_ID 1 else echo "Unable to detect hdhomerun_data inside /proc/devices." fi

-

-- set permissions

chmod 666 /dev/hdhomerun_data chown root:root /dev/hdhomerun_data

[tougher]

@sirgadget Oh, so the modules loads. That's great news. Do you run the script as root or admin? Look at the 3. post in this thread http://sourceforge.net/projects/dvbhdhomerun/forums/forum/1223414/topic/4937536

[BlueWombat]

@tougher Owner and group are both set to root, I presume that's also the context they're executed in by the startup process on the box?

Also when I run it by hand., I'm logged in as root.

[tougher]

@sirgadget ok. I've noticed your script is making device nodes in /dev/dvb/adapter3 and /dev/dvb/adapter4. The default for userhdhomerun is adapter0 and 1 or what? Also I guess the device node numbers can vary from system to system. My start script has this:

DYNAMIC_ID=$(grep DVB /proc/devices | awk "{print \$1}")
if [ "$DYNAMIC_ID" != "" ]; then

    echo "Creating DVB device nodes to major device #$DYNAMIC_ID..."

    mkdir -p /dev/dvb/adapter0
    DYNAMIC_ID2=$(cut -f2 -d':' /sys/class/dvb/dvb0.frontend0/dev)
    mknod /dev/dvb/adapter0/frontend0 c $DYNAMIC_ID $DYNAMIC_ID2
    DYNAMIC_ID2=$(cut -f2 -d':' /sys/class/dvb/dvb0.demux0/dev)
    mknod /dev/dvb/adapter0/demux0 c $DYNAMIC_ID $DYNAMIC_ID2
    DYNAMIC_ID2=$(cut -f2 -d':' /sys/class/dvb/dvb0.dvr0/dev)
    mknod /dev/dvb/adapter0/dvr0 c $DYNAMIC_ID $DYNAMIC_ID2

    mkdir -p /dev/dvb/adapter1
    DYNAMIC_ID2=$(cut -f2 -d':' /sys/class/dvb/dvb1.frontend0/dev)
    mknod /dev/dvb/adapter1/frontend0 c $DYNAMIC_ID $DYNAMIC_ID2
    DYNAMIC_ID2=$(cut -f2 -d':' /sys/class/dvb/dvb1.demux0/dev)
    mknod /dev/dvb/adapter1/demux0 c $DYNAMIC_ID $DYNAMIC_ID2
    DYNAMIC_ID2=$(cut -f2 -d':' /sys/class/dvb/dvb1.dvr0/dev)
    mknod /dev/dvb/adapter1/dvr0 c $DYNAMIC_ID $DYNAMIC_ID2
else
    echo "ERROR: Unable to detect DVB inside /proc/devices; dvb_core.ko"
fi

But I don't think it has anything to do with the ioctl issue :-/

[BlueWombat]

@tougher I can confirm it has nothing to do with issue, the only reason for doing it was, that after upgrading to DSM 4.1 beta, it auto created adapter 0 through 2, so I just didn't want any interference, if I could make sure not to:-)

The most of the autostartscript, I've copied from the user hoontune on the Tvheadend forum, who have used it on his Synology DS211.

[silasrye]

I have a ds412+ running DSM 4.1-2636. I am following the work here and able to test packages if that helps.

[BlueWombat]

@Valdimarsson I've got XMLTV to run fine now, can post the correcct chmod, + plus changes to the script, if you'd like?

I semi gave up on the HDHomerun, because of the mixed arch issue, does @tougher have any progress on the matter? In my frustration I bought a TecchnoTrend tuner with built-in CA slot that was reported working well with TVHeadend. After a lot of trial and error on compiling the damn drivers, I finally got it working, but am now stuck at TVHeadend saying "Unable to query adapter."

Arghh, makes me nuts!

I'd really really like TVHeadend to work, but if I can't get it to run from my DS1010+, I'm gonna give up, as I don't like the thought of having a machine running 24/7 just for that. So if I can't resolve the problems, I'll probably resort to a Dreambox or a VU+.

[tfylliv]

FYI,

[ 8690.981462] ioctl32(userhdhomerun:15855): Unknown cmd fd(3) cmd(c01c7600){t:'v';sz:28} arg(fffaa554) on /dev/hdhomerun_control
[ 8690.993121] ioctl32(userhdhomerun:15855): Unknown cmd fd(4) cmd(c01c7600){t:'v';sz:28} arg(fffaa554) on /dev/hdhomerun_control

This one happens as a result of using a 32 bit compiler on your NAS where as your kernel modules are compiled with a 64 bit compiler. For some odd reason the g++ on your (64 bit) NAS is a 32 bit version - and I guess you've cross compiled kernel modules?.

Long story short, if you really want to combine 64 bit kernel module with 32 bit user space application you can do the following, in dvbhdhomerun source code:

kernel/dvb_hdhomerun_control.c - locate:

if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,36)

.unlocked_ioctl = hdhomerun_control_ioctl,

Add a line more so you have:

if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,36)

.unlocked_ioctl = hdhomerun_control_ioctl, .compat_ioctl = hdhomerun_control_ioctl,

Build the kernel modules - copy to NAS. Run the userhdhomerun you build on the NAS. Profit.

Also see: http://sourceforge.net/projects/dvbhdhomerun/forums/forum/1223414/topic/6050427

[jekkos]

Ok, maybe you should use the kernel hotplugging scripts supplied by VideoStation when you want to load your own DVB modules. I did some investigation and will share the gained knowledge with you here.

After some research I managed to get a USB WinTV 930C HVR to work (em28xx based) with my DS213. I cross compiled the bleeding edge dvb drivers for the stick from the LinuxTV repository.

All kernel modules that should be loaded are listed in /usr/syno/hotplug/usb.DVB.dep.table. The information in this file is linked with the information in the usb.VID file, which contains the device VIDs and PIDs of plenty of DVB dongles. In that file the kernel modules linked to each dongle is specified. Every kernel module in its turn can have dependencies on others (which should be loaded beforehand) - otherwise your setup won't work.

You should have VideoStation installed to have the files there. Without VideoStation there will be NO hotplugging functionality for any DVB device. The package startiup script copies the scripts from the VideoStation directory (/volume1/@appstore/VideoStation/scripts/kernel) to the hotplug directory on startup. If you stop VideoStation, those scripts will be removed. I eventually deinstalled it, but sourced the hotplugging scripts for this functionality from there.

For em28xx these modules were quite a few, as there are plenty of tuners that use this kernel module. I removed all of the other tuners except for mine (xc5000.ko, drxk.ko) which seems to speed up the initialisation (uses less RAM etc). You can easily see which modules your stick need by plugging it in eg an ubuntu box and checking lsmod output before and after the dongle was attached.

You can find the kernel module load order in the DVB.dep.table file, which is also in the /usr/syno/hotplug directory after installing VideoStation. First you have the name of the tuner, and secondly a listing of modules in the order they should be insmodded.

In my case the Synology forgot to add some dependencies for the em28xx-alsa module, which caused it to fail loading (symbols not found in the dmesg output). You should add the following modules to the em28xx-alsa line in usb.DVB.dep.table: soundcore snd snd-timer snd-pcm em28xx em28xx-alsa Note that those lines are duplicated in the file for different kernel versions used among the diskstation models.

Finally I symlinked my homebrew ko's /lib/modules (I store them in /opt/lib/modules/2.6.32.12/dvb). In this case I didn't need to write a startup script to load them, as I was able to resuse the existing hotpluggin scripts.

This complete setup works fine with tvheaded 3.2.18 which is soon avalaible from this repository.

[bru7us]

Small note that as of PR #363 , spksrc now supports kernel source dependency for all supported architectures.

A cross package just needs to have REQ_KERNEL defined and can then use $KERNEL_DIR as the path to the kernel source (with modules already compiled).

[jdierkse]

I'm working on a HDHomeRun package. My first tries are available on http://syno.dierkse.nl If you'd like to test on a certain DSM and on a certain architecture, please let me know so I can create the package.

[kasperhartwich]

Cool! I like to test it. I have a DS411+II with a Intel Atom D525 cpu.

[jdierkse]

@kasperhartwich I've put a 1.0.1 version of the HDHomeRun package for x86 on http://syno.dierkse.nl

[SathishN]

Is the working on DSM 5.0? I like to test on my DS201j with Marvell Kirkwood mv6281 ARM running DSM 5.0. Thanks

[jdierkse]

@SathishN There is a 88f6281 version of HDHomeRun 1.0.1 for DSM 5.0 on http://syno.dierkse.nl It's not tested yet, as I don't own the necessary hardware.

[SathishN]

@jdierkse : thanks, I'll test it when I get home today.

[kasperhartwich]

Tested on DS411+II with x86 hdhomerun+tvheadend. I can't see the hdhomerun in tvheadend. See screenshot: https://dl.dropboxusercontent.com/u/5164/tvheadend-hdhomerun.png

[jdierkse]

@kasperhartwich have you bootstrapped your syno? If so, can you login and run lsmod and print the output here?

[kasperhartwich]

Sure.

Module                  Size  Used by    Tainted: P  
cifs                  239749  0 
udf                    77771  0 
isofs                  31642  0 
loop                   16880  0 
usbip                  16010  0 
usbip_common_mod       12917  1 usbip
nfsd                  244577 13 
exportfs                3409  1 nfsd
rpcsec_gss_krb5        24797  0 
usbhid                 25083  0 
hid                    52146  1 usbhid
usblp                  10475  0 
usb_storage            45423  0 
uhci_hcd               22468  0 
etxhci_hcd             82516  0 
xhci_hcd               80459  0 
ehci_hcd               39952  0 
pineview_synobios      37103  0 
synoacl_vfs            16147  1 
zlib_deflate           20276  0 
libcrc32c                906  0 
hfsplus                91928  0 
md4                     3497  0 
hmac                    2857  0 
i2c_algo_bit            5007  0 
fuse                   76894  0 
vfat                   10073  0 
fat                    48943  1 vfat
ecryptfs               90946  0 
sha512_generic          5033  0 
sha256_generic         10197  0 
sha1_generic            2206  0 
ecb                     1849  0 
aes_x86_64              7363  0 
authenc                 6632  0 
chainiv                 3179  0 
des_generic            16459  0 
crc32c                  2664  1 
eseqiv                  2758  0 
krng                    1065  0 
ansi_cprng              3477  0 
cts                     3872  0 
rng                     1805  4 chainiv,eseqiv,krng,ansi_cprng
aes_generic            26362  1 aes_x86_64
md5                     2185  0 
cbc                     2448  0 
cryptomgr               2552  0 
pcompress               1365  0 
aead                    5507  2 authenc,cryptomgr
crypto_hash            11244 10 cifs,libcrc32c,md4,hmac,sha512_generic,sha256_generic,sha1_generic,authenc,crc32c,md5
crypto_blkcipher       12471  7 ecryptfs,ecb,authenc,chainiv,eseqiv,cts,cbc
crypto_wq                711  1 chainiv
crypto_algapi          11589 17 hmac,ecb,aes_x86_64,authenc,chainiv,des_generic,eseqiv,krng,ansi_cprng,cts,aes_generic,cbc,cryptomgr,pcompress,aead,crypto_hash,crypto_blkcipher
cpufreq_stats           2921  0 
freq_table              2346  1 cpufreq_stats
dm_snapshot            27200  0 
crc_itu_t               1235  1 udf
crc_ccitt               1235  0 
quota_v2                3607  2 
quota_tree              8057  1 quota_v2
usbcore               159582  9 usbip,usbhid,usblp,usb_storage,uhci_hcd,etxhci_hcd,xhci_hcd,ehci_hcd
psnap                   1781  0 
p8022                    979  0 
llc                     3441  2 psnap,p8022
usb_common               826  1 usbcore
ipv6                  273060 74 
zram                    8223  2 
sg                     23870  0

[jdierkse]

Can you list the contents of the /dev/dvb folder?

[kasperhartwich]

drwxr-xr-x    2 root     root          4096 Apr 22 20:30 adapter0
drwxr-xr-x    2 root     root          4096 Apr 22 20:30 adapter1
drwxr-xr-x    2 root     root          4096 Apr 22 20:30 adapter2
drwxr-xr-x    2 root     root          4096 Apr 22 20:33 adapter3

nas> ll /dev/dvb/adapter0/
drwxr-xr-x    2 root     root          4096 Apr 22 20:30 .
drwxr-xr-x    6 root     root          4096 Apr 22 20:33 ..
crw-rw-rw-    1 root     root      212,   4 Apr 22 20:30 demux0
crw-rw-rw-    1 root     root      212,   5 Apr 22 20:30 dvr0
crw-rw-rw-    1 root     root      212,   3 Apr 22 20:30 frontend0
crw-rw-rw-    1 root     root      212,   7 Apr 22 20:30 net0

[jdierkse]

And the contents of /usr/lib/modules/3.2.40 ?

[kasperhartwich]

nas> ll /usr/lib/modules/3.2.40
drwxr-xr-x    3 root     root          4096 Apr 22 14:27 .
drwxr-xr-x    3 root     root         20480 Apr 22 20:32 ..
drwxr-xr-x    2 root     root          4096 Apr 22 14:27 extra
-rw-r--r--    1 root     root            45 Apr 22 14:27 modules.alias
-rw-r--r--    1 root     root             8 Apr 22 14:27 modules.alias.bin
-rw-r--r--    1 root     root            69 Apr 22 14:27 modules.ccwmap
-rw-r--r--    1 root     root           179 Apr 22 14:27 modules.dep
-rw-r--r--    1 root     root           518 Apr 22 14:27 modules.dep.bin
-rw-r--r--    1 root     root            73 Apr 22 14:27 modules.ieee1394map
-rw-r--r--    1 root     root           141 Apr 22 14:27 modules.inputmap
-rw-r--r--    1 root     root            81 Apr 22 14:27 modules.isapnpmap
-rw-r--r--    1 root     root            74 Apr 22 14:27 modules.ofmap
-rw-r--r--    1 root     root            99 Apr 22 14:27 modules.pcimap
-rw-r--r--    1 root     root            43 Apr 22 14:27 modules.seriomap
-rw-r--r--    1 root     root          3082 Apr 22 14:27 modules.symbols
-rw-r--r--    1 root     root          4044 Apr 22 14:27 modules.symbols.bin
-rw-r--r--    1 root     root           189 Apr 22 14:27 modules.usbmap