Add HDHomeRun driver packages

[jdierkse]

I'm currently in the process of making a HDHomerun driver package. I've created packages for DSM 4.3 (1.0.0) and DSM 5.0 (1.0.1) for just about every relevant architecture, and they can be found on http://syno.dierkse.nl If there are people who can test these packages, that would be awesome. Meanwhile I'll finalize the creation and create a pull request once done.

[poulanker]

This is awesome and what I have been looking forward to see available for my DS213+.

I installed the hdhomerun_qoriq_1.0.1-1.spk on my DS213+.running DSM 5.0-4482

Unfortunately it refuses to start. The only entry recorded in the logfile dvbhdhomerun_libhdhomerun.log each time i tried starting hdhomerun, is a single line like this: 20140604-23:44:26 Debug enabled I have tried restarting the NAS, stopping VideoStation and TVHeadend, but hdhomerun simply refuses to start.

Have some of you had any luck testing this specific package for qorig?

[jdierkse]

@poulanker Can you check for logs in /var/log/messages and run dmesg to see what's going on?

[poulanker]

@jdierkse The messages contains the following entries (among others) related to hdhomerun: Jun 4 23:44:27 DS2 entry.cgi_SYNO.Core.Package.Control[1].start[32312]: pkgstartstop.cpp:121 Failed to start package hdhomerun Jun 4 23:55:02 DS2 index.cgi: webutils.cpp (461) Can't find HTTP_HOST in env Jun 4 23:57:31 DS2 index.cgi: webutils.cpp (461) Can't find HTTP_HOST in env Jun 5 00:02:41 DS2 index.cgi: webutils.cpp (461) Can't find HTTP_HOST in env Jun 5 00:06:06 DS2 index.cgi: webutils.cpp (461) Can't find HTTP_HOST in env Jun 5 00:20:45 DS2 tvheadend[19324]: dvr: Output directory for video recording is not yet configured for DVR configuration "". Defaulting to to "/usr/local/tvheadend-testing/var". This can be changed from the web user interface. Jun 5 00:21:02 DS2 tvheadend[19324]: HTTP: 192.168.1.188: / -- 401 Jun 5 00:21:06 DS2 tvheadend[19324]: HTTP: 192.168.1.188: / -- 401 Jun 5 00:23:52 DS2 entry.cgi_SYNO.Core.Package.Control[1].start[21132]: pkgstartstop.cpp:121 Failed to start package hdhomerun Jun 5 00:24:25 DS2 entry.cgi_SYNO.Core.Package.Control[1].start[22169]: pkgstartstop.cpp:121 Failed to start package hdhomerun Jun 5 00:27:34 DS2 entry.cgi_SYNO.Core.Package.Control[1].start[24305]: pkgstartstop.cpp:121 Failed to start package hdhomerun Jun 5 00:45:08 DS2 index.cgi: webutils.cpp (461) Can't find HTTP_HOST in env Jun 5 00:56:59 DS2 index.cgi: webutils.cpp (461) Can't find HTTP_HOST in env

and dmesg produces the following output related to hdhomerun: [ 73.327129] sd 7:0:0:0: [sdu] Attached SCSI disk [ 73.625430] Slow work thread pool: Starting up [ 73.631102] Slow work thread pool: Ready [ 75.212161] findhostd uses obsolete (PF_INET,SOCK_PACKET) [ 348.292954] HDHomeRun: Begin init, version 0.0.16 [ 348.313753] HDHomeRun: Waiting for userspace to connect [ 348.319022] HDHomeRun: End init

Not much info, I'm afraid. As you can see, the tvheadend package installed and ran without problems. I have tried both versions of hdhomerun, but with the same result.

[poulanker]

@jdierkse I have found the cause of hdhomerun not starting. The connection to the HDHR3-EU was lost due to a bad connector on the CAT-5 cable. I was not aware of this, it has been a long time since I last checked the state of the device. I'm sorry for raising the issue, hopefully I will now get it to work. Thanks for your great work.

[jdierkse]

@poulanker good luck with that, please let me know if you have any other issues.

[Smiggel]

Here the driver still runs stable!

Only after the latest DSM 5 update (5.0-4493) I actually had to remove the package and re-install it to make it work. Package started fine, but TVH did not see the driver anymore right after the DMS update. After the remove and new install it worked fine again. :+1:

[poulanker]

@jdierkse I actually have a problem with tvheadend which does not show anything in the TV Adapters tab. I will try updating DSM to 5.0.4493 as advised by Smiggel. @Smiggel Thanks for the advise, I will try that out. Did you upgrade from 5.0.4482 ?

[Smiggel]

@poulanker I think so. I had was up to date until I received an e-mail from the nas about the latest DSM.

[jdierkse]

@poulanker Some people have reported issues with the startup order of the HDHomeRun package and TvHeadend. You can try stopping both, then starting HDHomeRun and then TvHeadend.

[poulanker]

@Smiggel @jdierkse BINGO :-) After updating to DSM 5.0.4493 and reinstalling hdhomerun, tvheadend now display both tuners. Now I have to figure out how to configure tvheadend, but that's another thing. Have you, by the way ,seen any good guides covering the latest tvheadend? Some of those I did find showed a different configuration setup for tvheadend. Thanks for your great help in getting this up and running.

[ghost]

First of all i want to thank you for making this package available. I successfully installed HDHomerun 1.0.1-1 and TvHeadend-testing 3.9.674-3 and this is working quiet good. Only after a certain period (within 24 hours) I noticed that TvHeadend cannot detect input on the tuner anymore. When looking then at Tvheadend I see that the signal strength is 0%, but at that time HDHomerun is still running as a process. The only thing i can find in the log is "hdhomerun_control_recv_sock: recv failed (11)". To solve this I need to restart both packages. I'm currently have DSM 5.0-4493 running on a DS214play. Any idea what could cause this behaviour?

[jdierkse]

@Mr-MarQuez, it seems there is a communication error between your NAS and the HDHomeRun unit. Does that sound plausible? Probably just restarting the userhdhomerun process will do though...

[ghost]

That sounds very plausible, the problem only is that happens at least once a day which is quiet annoying and not really waf. Is there something we can do about this?

[asmaras]

I have the same setup as @Mr-MarQuez (DSM 5.0-4493 running on a DS214play, using HDHomeRun 1.0.1-1) and have the exact same problem with TvHeadend 3.9.674-3. After a short while it can't detect any input anymore. Usually, after startup, streaming works fine. Then when you stop streaming and TvHeadend does some epg grabbing for a while, the connection with the HDHomeRun units is broken. This happens with al the 3.9.xxx testing versions.

However, with TvHeadend 3.4 it works 100% stable. Hope we can pinpoint the problem in the later versions.

Thanks for creating these packages!

[ghost]

@hlennaerts good to know that i'm not the only one who is experiencing this problem. I did not test with 3.4 but will also check. Did you find something strange in the logs when the issue occurs?

[asmaras]

Currently testing with TvHeadend 3.9.952. I will post any relevant results. @jdierkse at some point, the HDHomeRun 1.0.1-1 package would not start anymore, even after restart of the NAS. I had to do stuff like below in order to get it to start again. Can you alter the script to take this into account? DiskStation> rmmod /usr/local/hdhomerun/bin/dvb_hdhomerun.ko DiskStation> rmmod /usr/local/hdhomerun/bin/dvb-core.ko DiskStation> rmmod /usr/local/hdhomerun/bin/dvb_hdhomerun_fe.ko DiskStation> rmmod /usr/local/hdhomerun/bin/dvb_hdhomerun_core.ko DiskStation> rm /dev/hdhomerun_control DiskStation> rm -r /dev/dvb/*

[asmaras]

The first failure occurred 2 hours after starting TvHeadend 3.9.952. No error in HDHomerun log. In TvHeadend log this can be seen when the problem starts:

---

2014-06-29 18:41:59.005 [ INFO]:subscription: 'epggrab' subscribing to mux, weight: 3, adapter: 'HDHomeRun DVB-C 12206102-1 : DVB-C #0', network: 'Ziggo', mux: '618750' ..... 2014-06-29 18:41:59.005 [ INFO]:subscription: 'epggrab' subscribing to mux, weight: 3, adapter: 'HDHomeRun DVB-C 12209F7E-0 : DVB-C #0', network: 'Ziggo', mux: '498750' ..... 2014-06-29 18:41:59.006 [ INFO]:subscription: 'epggrab' subscribing to mux, weight: 3, adapter: 'HDHomeRun DVB-C 12209F7E-1 : DVB-C #0', network: 'Ziggo', mux: '698750' ..... 2014-06-29 18:42:01.067 [ DEBUG]:linuxdvb: HDHomeRun DVB-C 12206102-1 : DVB-C #0 - status BAD (SIGNAL | CARRIER) 2014-06-29 18:42:01.067 [ DEBUG]:linuxdvb: HDHomeRun DVB-C 12209F7E-0 : DVB-C #0 - status UNKNOWN (SIGNAL) 2014-06-29 18:42:01.067 [ DEBUG]:linuxdvb: HDHomeRun DVB-C 12209F7E-1 : DVB-C #0 - status UNKNOWN (SIGNAL)

---

The "BAD" signal messages the keep coming and you will have to restart the HDHomeRun driver package. Hope this info helps.

As said before, no problem with TvHeadend version 3.4.

[hobbsAU]

@hlennaerts, I started getting the same issue when I upgraded to tvheadend 3.9.952-4 (see similar logs below). I have a DS 1512+ running DSM 5.0-4493 Update 2.

I fixed mine by downgrading to TVheadend 3.9.929-1 and still using the same HDHomeRun 1.0.1-1 (cedarview) driver. Both sourced from jdierkse's awesome repository here: http://syno.dierkse.nl/

Something's probably broken in the latest TVheadend dev build so I think I'll wait until I upgrade again as 3.9.929-1 seems pretty stable.

Logs from /usr/local/tvheadend-testing/var/tvheadend.log

2014-07-01 18:05:37.000 [ INFO]:mpegts: 226500 - tuning on HDHomeRun DVB-T 11104F26-0 : DVB-T #0 2014-07-01 18:05:37.000 [ DEBUG]:linuxdvb: HDHomeRun DVB-T 11104F26-0 : DVB-T #0 - starting 226500 2014-07-01 18:05:37.000 [ DEBUG]:mpegts: 226500 - started 2014-07-01 18:05:37.001 [ DEBUG]:mpegts: 226500 - open PID 0039 (57) [2/0xce4eb0] 2014-07-01 18:05:37.001 [ DEBUG]:viasat_baltic: installed table handlers 2014-07-01 18:05:37.001 [ DEBUG]:mpegts: 226500 - open PID 0BBA (3002) [2/0x118bab0] 2014-07-01 18:05:37.001 [ DEBUG]:mpegts: 226500 - open PID 0BBB (3003) [2/0xf463d0] 2014-07-01 18:05:37.001 [ DEBUG]:uk_freesat: installed table handlers 2014-07-01 18:05:37.001 [ DEBUG]:mpegts: 226500 - open PID 0012 (18) [3/0xf4a7a0] 2014-07-01 18:05:37.001 [ DEBUG]:eit: installed table handlers 2014-07-01 18:05:37.001 [ INFO]:subscription: 'epggrab' subscribing to mux, weight: 3, adapter: 'HDHomeRun DVB-T 11104F26-0 : DVB-T #0', network: 'AU-SYD', mux: '226500' 2014-07-01 18:05:37.001 [ DEBUG]:eit: grab started 2014-07-01 18:05:37.001 [ INFO]:mpegts: 536500 - tuning on HDHomeRun DVB-T 11104F26-1 : DVB-T #0 2014-07-01 18:05:37.001 [ DEBUG]:linuxdvb: HDHomeRun DVB-T 11104F26-1 : DVB-T #0 - starting 536500 2014-07-01 18:05:37.001 [ DEBUG]:mpegts: 536500 - started 2014-07-01 18:05:37.001 [ DEBUG]:mpegts: 536500 - open PID 0039 (57) [2/0xf66f70] 2014-07-01 18:05:37.001 [ DEBUG]:viasat_baltic: installed table handlers 2014-07-01 18:05:37.001 [ DEBUG]:mpegts: 536500 - open PID 0BBA (3002) [2/0xfaf130] 2014-07-01 18:05:37.001 [ DEBUG]:mpegts: 536500 - open PID 0BBB (3003) [2/0x10dbc50] 2014-07-01 18:05:37.001 [ DEBUG]:uk_freesat: installed table handlers 2014-07-01 18:05:37.001 [ DEBUG]:mpegts: 536500 - open PID 0012 (18) [3/0xd841a0] 2014-07-01 18:05:37.001 [ DEBUG]:eit: installed table handlers 2014-07-01 18:05:37.001 [ INFO]:subscription: 'epggrab' subscribing to mux, weight: 3, adapter: 'HDHomeRun DVB-T 11104F26-1 : DVB-T #0', network: 'AU-SYD', mux: '536500' 2014-07-01 18:05:37.001 [ DEBUG]:eit: grab started 2014-07-01 18:05:37.610 [ DEBUG]:linuxdvb: HDHomeRun DVB-T 11104F26-0 : DVB-T #0 - status UNKNOWN (SIGNAL) 2014-07-01 18:05:37.610 [ DEBUG]:linuxdvb: HDHomeRun DVB-T 11104F26-1 : DVB-T #0 - status UNKNOWN (SIGNAL) 2014-07-01 18:05:37.712 [ DEBUG]:linuxdvb: HDHomeRun DVB-T 11104F26-0 : DVB-T #0 - status UNKNOWN () 2014-07-01 18:05:37.712 [ DEBUG]:linuxdvb: HDHomeRun DVB-T 11104F26-1 : DVB-T #0 - status UNKNOWN () 2014-07-01 18:05:37.814 [ DEBUG]:linuxdvb: HDHomeRun DVB-T 11104F26-0 : DVB-T #0 - status UNKNOWN (SIGNAL) 2014-07-01 18:05:37.814 [ DEBUG]:linuxdvb: HDHomeRun DVB-T 11104F26-1 : DVB-T #0 - status UNKNOWN (SIGNAL) 2014-07-01 18:05:37.916 [ DEBUG]:linuxdvb: HDHomeRun DVB-T 11104F26-0 : DVB-T #0 - status UNKNOWN () 2014-07-01 18:05:37.916 [ DEBUG]:linuxdvb: HDHomeRun DVB-T 11104F26-1 : DVB-T #0 - status UNKNOWN ()

[asmaras]

@hobbsAU, I've tried TVheadend 3.9.929-1. But it still produces the same issue of "loosing" the tuners after some time. In fact, all 3.9.xxx version have this issue. Only version 3.4 (from the synocommunity repository) works stable on my DS214play.

[jdierkse]

Hi guys. I haven't been active on this for quite a while now. I'll look into your problems asap.

[jdierkse]

@hlennaerts the rmmod commands you request are already in the stop_daemon part of the start / stop script. I'll build a new version of tvheadend (3.9.1084), and let's hope that these tuner errors have been fixed.

[jdierkse]

On http://syno.dierkse.nl you can now find TvHeadend 3.9.1084. This version is not yet tested by me, but if you want to try it, please feel free to do so.

[asmaras]

@jdierkse I will test this version soon. Your work is greatly appreciated. About the rmmod (start/stop script) issue: I actually encountered the problem where I did stop the HDHomeRun package, uninstalled it, and then wasn't able to install it anymore (package center kept giving an error). That's when I had to perform the rmmod commands manually.

[bzhnunu]

Hi, i've just get a DS214play. I try to install hdhomerun on DSM5 (last update so 4493 update3). 1.0.1-1 evansport.

under /Var/messages i got:

DiskStation> cat /var/log/messages | grep hdhomerun Jul 24 20:09:43 DiskStation kernel: [ 1171.838031] dvb_hdhomerun: Unknown symbol dvb_dmxdev_init (err 0) Jul 24 20:09:43 DiskStation kernel: [ 1171.844464] dvb_hdhomerun: Unknown symbol dvb_register_adapter (err 0) Jul 24 20:09:43 DiskStation kernel: [ 1171.851273] dvb_hdhomerun: Unknown symbol dvb_dmx_release (err 0) Jul 24 20:09:43 DiskStation kernel: [ 1171.857446] dvb_hdhomerun: Unknown symbol dvb_dmx_swfilter (err 0) Jul 24 20:09:43 DiskStation kernel: [ 1171.863660] dvb_hdhomerun: Unknown symbol dvb_dmxdev_release (err 0) Jul 24 20:09:43 DiskStation kernel: [ 1171.870113] dvb_hdhomerun: Unknown symbol dvb_frontend_detach (err 0) Jul 24 20:09:43 DiskStation kernel: [ 1171.876624] dvb_hdhomerun: Unknown symbol dvb_unregister_frontend (err 0) Jul 24 20:09:43 DiskStation kernel: [ 1171.883487] dvb_hdhomerun: Unknown symbol dvb_register_frontend (err 0) Jul 24 20:09:43 DiskStation kernel: [ 1171.890147] dvb_hdhomerun: Unknown symbol dvb_unregister_adapter (err 0) Jul 24 20:09:43 DiskStation kernel: [ 1171.896871] dvb_hdhomerun: Unknown symbol dvb_dmx_init (err 0) Jul 24 20:09:44 DiskStation entry.cgi_SYNO.Core.Package.Control[1].start[21580]: pkgstartstop.cpp:121 Failed to start package hdhomerun Jul 24 20:10:15 DiskStation entry.cgi_SYNO.Core.Package.Control[1].start[23817]: pkgstartstop.cpp:121 Failed to start package hdhomerun Jul 24 20:20:55 DiskStation entry.cgi_SYNO.Core.Package.Control[1].start[18061]: pkgstartstop.cpp:121 Failed to start package hdhomerun Jul 24 20:22:38 DiskStation entry.cgi_SYNO.Core.Package.Control[1].start[19642]: pkgstartstop.cpp:121 Failed to start package hdhomerun Jul 24 20:23:26 DiskStation entry.cgi_SYNO.Core.Package.Control[1].start[20890]: pkgstartstop.cpp:121 Failed to start package hdhomerun Jul 24 20:29:31 DiskStation entry.cgi_SYNO.Core.Package.Control[1].start[18191]: pkgstartstop.cpp:121 Failed to start package hdhomerun Jul 27 11:39:11 DiskStation entry.cgi_SYNO.Core.Package.Control[1].start[29178]: pkgstartstop.cpp:121 Failed to start package hdhomerun

after starting the hdhomerun driver i got: DiskStation> lsmod | grep hd dvb_hdhomerun 9869 4 dvb_hdhomerun_fe 4965 1 dvb_hdhomerun dvb_hdhomerun_core 1787 2 dvb_hdhomerun,dvb_hdhomerun_fe dvb_core 74730 1 dvb_hdhomerun

discover is OK: DiskStation> hdhomerun_config discover hdhomerun device 11106FDC found at 192.168.1.121

but tvheadend (3.5 & 3.9) doesn't see dvb devices.

Any idea :) ?

regards

[bzhnunu]

hum, i don't know why but it seems working fine now .... with stable version of tvheadend of synocommunity.

[asmaras]

@jdierkse TvHeadend 3.9.1084 exposes the same problem, where it logs the signal status as UNKNOWN after some time of operation. Even the synocommunity version 3.4 seems to have this problem very, very occasionally.

Currently I think that the problem might be the way the HDHomeRun driver uses sockets to receive the stream from the tuner device.

This is based on what I saw with the HDHomeRun Windows GUI tool (that you can download from the silicondust site). The tool shows:

• the frequency a tuner is tuned to
• the signal quality
• the destination IP:port for the RTP stream
• the bandwidth of the stream

When all is fine, all of the above have a sensible value. For an HD channel, the bandwidth could be around 13 Mbps. When scanning muxes, the bandwidth might be between 1 and 2 Mbps. However, when the problem starts you can see the following:

• frequency is correct and dependent in the channel you select in xbmc
• signal quality is fine
• destination IP:port is empty and the bandwidth is 0 Mbps

So the fact is that the tuner is still being controlled by TvHeadend, but there is no more destination for the RTP stream. This leads me to believe that the driver is unable to open a socket at that time.

Then why is version 3.4 more stable? It uses the tuners continuously (idle scanning enabled), while version 3.9.x stops the tuners very often. If there is an occasional problem with opening sockets to receive the mux stream, it makes sense that version 3.9.x runs into this problem earlier than version 3.4.

I don't know how to research this further right now, so I'm hoping someone else has an idea....

[thomas7977]

Hi I've just tried with my DS712+ to install hdhomerun on DSM5 (last update so 4493 update3). 1.0.1-1 x86. Same problem as you bzhnunu. Someone has an idea ?

[jdierkse]

I've had some problems after updating to DSM 5 as well (have been on 4.3 until the recent synolocker issues). What helped wat stopping the package, making sure all the kernel modules were unloaded, removing everything with "hdhomerun" from /dev, removing everything from /dev/dvb, and starting the package.

[Don-black]

I am a complete newbie trying to get tvheadend to work with hdhomerunprime and xbmc. Can anyone offer some instructions or guide as to how I get this to work I have been working on this for months with no luck except upnp connection in xbmc

[asmaras]

I've been running Tvheadend-Testing 3.9.1341-1 for two weeks without running into problems with the HDHomeRun tuners (they would stop streaming with previous versions at some point).

Although this version of Tvheadend still has some flaws, it is a lot easier to configure than version 3.4!

[1972rx2]

Hi guys, Thank you so much jdierske for your hard work on this. Yesterday I updated my Xpenology box to 4493 update 5 which broke my Digitalnow Tinytwin tuner so I thought I would revisit using my HDHomerun. In the past I had trouble with your driver saying that the "package failed to start", I came across this thread and by following some of the commands I got it up and running with TVHeadend 3.9.1341. So far so good. Cheers!

[1972rx2]

I have a bit of an update after using this for a few days. I am using Tvheadend-Testing 3.9.1341-1 and it seems each day I need to stop and restart the HDhomerun package otherwise I get this error in TVHeadend....... 2014-10-01 20:20:56.001 subscription: No transponder available for subscription "DVR: The Block Glasshouse - New" to channel "Nine Melbourne"

After a restart of the driver and TVHeadend everything works fine again for another day or so.

[1972rx2]

This is what I get from the HDhomerun logs

[bzhnunu]

Hello, i'd would like to know if somebody has hdhomerun + tvheadend working with DSM 5.1 ? (i'am on evansport CPU). regards nunu

[jdierkse]

@bzhnunu I'd expect not, as I need the kernel sources to build a new driver, and the kernel sources for 5.1 are not yet available...

[bzhnunu]

Thanks for your answer. So, kernel version has been changed too with dsm 5.1 ?

[bzhnunu]

oups ... kernel module seems insert (lsmod). If it was not compatible, kernel module can't insert (as far as i know)?

regards

[jdierkse]

Hmm, that's interesting. I haven't tried it for myself, so I don't know what the problem is. Can you identify what the issue is?

[bzhnunu]

Tvheadend don't see any tuner. If i use command : hdhomerun_config discover, HDHomerun is descted. I don't know if it's enough to say that HDHomrun driver is running. In TVheadend logs, it says : can't open devices. I have checked /dev/dvb, and all seems OK..

What kind of logs to you need exactly ?

regards nunu

[jdierkse]

What's in /var/log/messages? And perhaps running dmesg shows some useful information.

[bzhnunu]

dmsg | grep hdhomerun

[ 1109.579277] hdhomerun: userhdhomerun connected [ 1109.583909] hdhomerun: userhdhomerun connected [ 1109.588402] hdhomerun: creating dvb device for 11106FDC-0 [ 1109.616467] hdhomerun: device /dev/hdhomerun_data0 created [ 1109.622101] hdhomerun: userhdhomerun connected [ 1109.626584] hdhomerun: creating dvb device for 11106FDC-1 [ 1109.654597] hdhomerun: device /dev/hdhomerun_data1 created [ 1109.660285] hdhomerun: userhdhomerun connected [34800.821385] hdhomerun: userhdhomerun disconnected [34800.941497] hdhomerun: userhdhomerun disconnected [34801.194820] hdhomerun: userhdhomerun disconnected [34801.200027] hdhomerun: userhdhomerun disconnected [37707.435752] hdhomerun: userhdhomerun connected [37707.440363] hdhomerun: userhdhomerun connected [37707.444831] hdhomerun: creating dvb device for 11106FDC-0 [37707.474623] hdhomerun: device /dev/hdhomerun_data0 created [37707.480287] hdhomerun: userhdhomerun connected [37707.484748] hdhomerun: creating dvb device for 11106FDC-1 [37707.514196] hdhomerun: device /dev/hdhomerun_data1 created [37707.520257] hdhomerun: userhdhomerun connected

DiskStation> dmesg | grep tvheadend [ 1792.294301] tvheadend[28223]: segfault at 0 ip b74692c1 sp b43dd7f0 error 4 in libc.so.6[b73f4000+171000]

/var/log/messages

Nov 8 20:25:28 DiskStation tvheadend[8392]: linuxdvb: unable to open /dev/dvb/adapter0/frontend0 Nov 8 20:25:28 DiskStation tvheadend[12962]: linuxdvb: unable to open /dev/dvb/adapter0/frontend0 Nov 8 20:25:28 DiskStation tvheadend[16375]: linuxdvb: unable to open /dev/dvb/adapter0/frontend0 Nov 8 20:25:32 DiskStation tvheadend[8392]: linuxdvb: unable to open /dev/dvb/adapter2/frontend0 Nov 8 20:25:32 DiskStation tvheadend[16375]: linuxdvb: unable to open /dev/dvb/adapter2/frontend0 Nov 8 20:25:32 DiskStation tvheadend[12962]: linuxdvb: unable to open /dev/dvb/adapter2/frontend0 Nov 8 20:25:34 DiskStation tvheadend[8392]: linuxdvb: unable to open /dev/dvb/adapter3/frontend0 Nov 8 20:25:34 DiskStation tvheadend[12962]: linuxdvb: unable to open /dev/dvb/adapter3/frontend0 Nov 8 20:25:34 DiskStation tvheadend[16375]: linuxdvb: unable to open /dev/dvb/adapter3/frontend0 Nov 8 20:25:36 DiskStation tvheadend[8392]: linuxdvb: unable to open /dev/dvb/adapter4/frontend0 Nov 8 20:25:36 DiskStation tvheadend[12962]: linuxdvb: unable to open /dev/dvb/adapter4/frontend0 Nov 8 20:25:36 DiskStation tvheadend[16375]: linuxdvb: unable to open /dev/dvb/adapter4/frontend0 Nov 8 20:25:38 DiskStation tvheadend[8392]: linuxdvb: unable to open /dev/dvb/adapter5/frontend0 Nov 8 20:25:38 DiskStation tvheadend[12962]: linuxdvb: unable to open /dev/dvb/adapter5/frontend0 Nov 8 20:25:38 DiskStation tvheadend[16375]: linuxdvb: unable to open /dev/dvb/adapter5/frontend0 Nov 8 20:25:40 DiskStation tvheadend[8392]: linuxdvb: unable to open /dev/dvb/adapter6/frontend0 Nov 8 20:25:40 DiskStation tvheadend[12962]: linuxdvb: unable to open /dev/dvb/adapter6/frontend0 Nov 8 20:25:40 DiskStation tvheadend[16375]: linuxdvb: unable to open /dev/dvb/adapter6/frontend0 Nov 8 20:25:42 DiskStation tvheadend[8392]: linuxdvb: unable to open /dev/dvb/adapter7/frontend0 Nov 8 20:25:42 DiskStation tvheadend[12962]: linuxdvb: unable to open /dev/dvb/adapter7/frontend0 Nov 8 20:25:42 DiskStation tvheadend[16375]: linuxdvb: unable to open /dev/dvb/adapter7/frontend0

[bzhnunu]

DiskStation> ls -al drwxr-xr-x 2 root root 120 Nov 8 20:25 . drwxrwxrwx 10 root root 200 Nov 8 20:25 .. crw------- 1 root root 212, 4 Nov 8 20:25 demux0 crw------- 1 root root 212, 5 Nov 8 20:25 dvr0 crw------- 1 root root 212, 3 Nov 8 20:25 frontend0 crw-rw-rw- 1 root root 212, 7 Nov 8 20:25 net0 DiskStation> cd .. DiskStation> ls -al drwxrwxrwx 10 root root 200 Nov 8 20:25 . drwxr-xr-x 15 root root 8860 Nov 8 20:25 .. drwxr-xr-x 2 root root 120 Nov 8 20:25 adapter0 drwxr-xr-x 2 root root 120 Nov 8 20:25 adapter1 drwxr-xr-x 2 root root 120 Nov 8 20:25 adapter2 drwxr-xr-x 2 root root 120 Nov 8 20:25 adapter3 drwxr-xr-x 2 root root 120 Nov 8 20:25 adapter4 drwxr-xr-x 2 root root 120 Nov 8 20:25 adapter5 drwxr-xr-x 2 root root 120 Nov 8 20:25 adapter6 drwxr-xr-x 2 root root 120 Nov 8 20:25 adapter7 DiskStation>

[jdierkse]

Do you have a running process '''userhdhomerun'''?

[helio58]

Hi, I hade hdhomerun running yesterday, today after update sinology , hdhomerun will not start , get a error in package center, "This package does not have a digital signature"

[jdierkse]

@helio58 to run a custom package on 5.1 you will need to lower the security level.

[helio58]

@jdierkse thanks , but could you please let me know how to lower the security level DS415play

Thanks

[bzhnunu]

Yes it seems : DiskStation> ps -w | grep hdhomerun 11215 root 19896 S /usr/bin/userhdhomerun -f -d 16525 root 3776 R grep hdhomerun

[jdierkse]

@helio58 http://forum.synology.com/enu/viewtopic.php?f=193&t=90710 @bzhnunu strange, then it seems that the hdhomerun driver is working fine...

[jdierkse]

@bzhnunu PERHAPS nick green's comment in https://github.com/SynoCommunity/spksrc/pull/931 can help?

[helio58]

@jdierkse have install it have same result as bzhnunu Lagring> ps -w | grep hdhomerun 16459 root 19896 S /usr/bin/userhdhomerun -f -d 17420 root 3772 S grep hdhomerun

but no adapters