SynoCommunity / spksrc

Cross compilation framework to create native packages for the Synology's NAS
https://synocommunity.com
Other
3.01k stars 1.23k forks source link

Add HDHomeRun driver packages #958

Closed jdierkse closed 8 years ago

jdierkse commented 10 years ago

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.

SathishN commented 10 years ago

After changing the tuner type to ATSC, and restarted services it shows up the right countries,

I'm still waiting for mux to scan!!

When I stop the HDHomeRun package DiskStation> /var/packages/hdhomerun/scripts/start-stop-status stop killall: userhdhomerun: no process killed

Is that expected?

SathishN commented 10 years ago

wow.. it worked.. gr8, thanks a lot @jdierkse

image

jdierkse commented 10 years ago

@SathishN, I will look into creating an install window which will query for the correct tuner mode. The killall message can occur when there is no userhdhomerun process running, and can be ignored. Awesome that the drivers work, thanks again for testing!

SathishN commented 10 years ago

@jdierkse thanks for all your hard work :)

Smiggel commented 10 years ago

@SathishN Do you run it on DSM 4 or 5?

schumi2004 commented 10 years ago

Confirmed working on DS211 DSM5 (88f6281) Thank you @jdierkse I think you made a lot of people happy certainly since you fixed it for (i think) every architecture, awesome

schumi2004 commented 10 years ago

@jdierkse want another challenge ;) comskip (commmercial skipping tool) http://forum.xbmc.org/showthread.php?tid=150084

SathishN commented 10 years ago

@Smiggel it works on DSM 5.0-4458.

jdierkse commented 10 years ago

@schumi2004 I first would like to see whether I can compile TvHeadend with transcoding support for Synology, but it looks very interesting! Can TvHeadend use ComSkip?

schumi2004 commented 10 years ago

What would be the benefit of adding transcode to TVH? About comskip, comskip itself is more a standalone app triggerd by a post-processing script in TVH http://forum.xbmc.org/showthread.php?tid=150084&pid=1400001#pid1400001 It generates a EDL file which XBMC can use to skip commercials, should also be possible to do it on the fly but not yet tested it.

jdierkse commented 10 years ago

@schumi2004: transcoding would allow one to send channels in a lower resolution than the raw stream, which would enable one to watch tv over lower bandwidth connections. I'll put ComSkip on my todo-list :)

schumi2004 commented 10 years ago

@jdierkse ok cool. Did you contact @adamsutton already for your transcoding idea?

jdierkse commented 10 years ago

@schumi2004 Not yet, but transcoding is already an option in TvHeadend as far as I know.

Smiggel commented 10 years ago

@jdierkse works fine on DSM 5! Thanks for the great work!

gebruikerh commented 10 years ago

Hi jdierkse, thank for the effort. But could you also get it work for the HDHR3-4DC (4 tuner bvd-c). I can see it tvheadend...but not with correct tuners.. The same problem as I had with DSM 4.

jdierkse commented 10 years ago

@gebruikerh can you post the ouput of hdhomerun_config discover?

permster commented 10 years ago

Is there a package for the mv6282 (Armada 300)? I would be glad to test it out. I'm on DSM 5.

jdierkse commented 10 years ago

@permster I guess the 88f6281 package should work for you.

TonVH commented 10 years ago

Hope someone can help. Trying to get TVheadend working on a DS414 with DSM v5.

I installed the HDhomerun driver (ArmadaXP) from http://syno.dierkse.nl/ then installed TVheadend. Now when I start TVheadend from the icon on the TopLeft of the DSM Desktop then I get an error saying page "http://192.168.1.222:5000/webman/3rdparty/tvheadend/tvheadend.cgi" does not exist.

If I start from "http://192.168.1.222:9981/extjs.html" then I get the correct TVheadend window. Next I go to "Configuration/TV Adapters" but the dropdown contains nothing.

How do I proceed or where can I find instructions on this?

jdierkse commented 10 years ago

@antoniong, does /var/log/messages show any error messages, or perhaps running dmesg shows some errors?

TonVH commented 10 years ago

@jdierkse: I do not really know what to look for so I restarted my NAS and put the log in here http://pastebin.com/Hs3h95ak I can see a lot of error messages "hot plug.c ....... failed to get ....." at 10:04:25 probably not important.

At 10:01:22 there are many messages pertaining to the HDHR but I see no problems there.

More important probably is at 10:04:39 "about experimental version, older and more". Also at 10:05:25 there are 4 messages (I have 2 HDHR3) "TVheadend .... (no such device)"

Dmesg shows no errors:

"[ 295.787203] hdhomerun: creating dvb device for 1220E3D6-1 [ 295.818558] DVB: registering new adapter (HDHomeRun) [ 295.836138] HDHomeRun HDHomeRun.3: DVB: registering adapter 3 frontend 0 (HDHomeRun DVB-C 1220E3D6-1)... [ 295.882571] HDHomeRun3: DVB Frontend registered [ 295.887203] HDHomeRun3: Registered DVB adapter3 [ 295.920835] hdhomerun: device /dev/hdhomerun_data3 created [ 295.960126] hdhomerun: userhdhomerun connected" 4 times this for each channel.

jdierkse commented 10 years ago

@antoniong, It seems like you're starting TvHeadend (probably automatically) before you're starting the HDHomeRun driver. Try stopping TvHeadend and restarting, and re-check for errors.

TonVH commented 10 years ago

Stopped TVheadend and restarted it. get these error messages:

May 1 10:14:40 DS414 tvheadend[10677]: HTTP: 192.168.1.111: /extjs.html -- 401 May 1 10:25:53 DS414 afpd[18645]: [afp_dsi.c:791-E] bad function 7A May 1 10:30:53 DS414 afpd[18645]: [afp_dsi.c:429-E] afp_alarm: child timed out, entering disconnected state May 1 10:45:14 DS414 tvheadend[22443]: dvb: /dev/dvb/adapter0/frontend0: unable to query (err=Invalid argument) May 1 10:45:14 DS414 tvheadend[22443]: dvb: /dev/dvb/adapter1/frontend0: unable to open (err=No such device) May 1 10:45:14 DS414 tvheadend[22443]: dvb: /dev/dvb/adapter2/frontend0: unable to open (err=No such device) May 1 10:45:14 DS414 tvheadend[22443]: dvb: /dev/dvb/adapter3/frontend0: unable to open (err=No such device) May 1 10:45:14 DS414 tvheadend[22443]: dvr: Output directory for video recording is not yet configured for DVR configuration "". Defaulting to to "/usr/local/tvheadend/var". This can be changed from the web user interface. May 1 10:45:19 DS414 tvheadend[22443]: HTTP: 192.168.1.111: / -- 401

"bad function 7a" could be the culprit? I checked tvheadend.org but found no list of error messages there.

jdierkse commented 10 years ago

@antoniong, Is the HDHomeRun package started? Do the HDHomeRun kernel modules turn up when you run lsmod? Are there any userhdhomerun processes running?

TonVH commented 10 years ago

I turned off TVheadend and HDHomerun. Restarted HDHR then TVheadend. There is still nothing in the drop down. There is a proces "userhdhomerun" present but in sleepmode.

Messages contains:

May 1 11:09:36 DS414 kernel: [ 4148.155697] dvb_core: Unknown symbol refrigerator (err 0) May 1 11:09:37 DS414 kernel: [ 4148.841319] hdhomerun: dvb device for this tuner already exists, ignore request 1220A78E-0 May 1 11:09:37 DS414 kernel: [ 4148.859666] hdhomerun: dvb device for this tuner already exists, ignore request 1220A78E-1 May 1 11:09:37 DS414 kernel: [ 4148.878826] hdhomerun: dvb device for this tuner already exists, ignore request 1220E3D6-0 May 1 11:09:37 DS414 kernel: [ 4148.897270] hdhomerun: dvb device for this tuner already exists, ignore request 1220E3D6-1 May 1 11:09:51 DS414 tvheadend[32364]: dvb: /dev/dvb/adapter0/frontend0: unable to query (err=Invalid argument) May 1 11:09:51 DS414 tvheadend[32364]: dvb: /dev/dvb/adapter1/frontend0: unable to open (err=No such device) May 1 11:09:51 DS414 tvheadend[32364]: dvb: /dev/dvb/adapter2/frontend0: unable to open (err=No such device) May 1 11:09:51 DS414 tvheadend[32364]: dvb: /dev/dvb/adapter3/frontend0: unable to open (err=No such device) May 1 11:09:51 DS414 tvheadend[32364]: dvr: Output directory for video recording is not yet configured for DVR configuration "". Defaulting to to "/usr/local/tvheadend/var". This can be changed from the web user interface.

Dmesg contains:

[ 3950.743177] hdhomerun: userhdhomerun disconnected [ 3950.748557] hdhomerun: userhdhomerun disconnected [ 3950.753287] hdhomerun: userhdhomerun disconnected [ 3950.758321] hdhomerun: userhdhomerun disconnected [ 3950.763049] hdhomerun: userhdhomerun disconnected [ 4148.155697] dvb_core: Unknown symbol refrigerator (err 0) [ 4148.826724] hdhomerun: userhdhomerun connected [ 4148.831284] hdhomerun: userhdhomerun connected [ 4148.835829] hdhomerun: creating dvb device for 1220A78E-0 [ 4148.841319] hdhomerun: dvb device for this tuner already exists, ignore request 1220A78E-0 [ 4148.849736] hdhomerun: userhdhomerun connected [ 4148.854200] hdhomerun: creating dvb device for 1220A78E-1 [ 4148.859666] hdhomerun: dvb device for this tuner already exists, ignore request 1220A78E-1 [ 4148.868847] hdhomerun: userhdhomerun connected [ 4148.873384] hdhomerun: creating dvb device for 1220E3D6-0 [ 4148.878826] hdhomerun: dvb device for this tuner already exists, ignore request 1220E3D6-0 [ 4148.887342] hdhomerun: userhdhomerun connected [ 4148.891836] hdhomerun: creating dvb device for 1220E3D6-1 [ 4148.897270] hdhomerun: dvb device for this tuner already exists, ignore request 1220E3D6-1 [ 4148.905716] hdhomerun: userhdhomerun connected

jdierkse commented 10 years ago

@antoniong, the dvb device for this tuner already exists, ignore request puzzle me. After stopping the HDHomeRun package, are there still any dvb modules loaded?

TonVH commented 10 years ago

That print was while HDHR was running. I stopped HDHR and TVheadend and then started (in this sequence) HDHR and then TVheadend.

The whole output of Dmesg is here http://pastebin.com/K4rK1uv2 since it is rather large I only enclosed the last lines. I know only a tiny bit of Linux so have no idea where to look or what is useful to know.

Op 1 mei 2014, om 14:50 heeft J. Dierkse notifications@github.com het volgende geschreven:

@antoniong, the dvb device for this tuner already exists, ignore request puzzle me. After stopping the HDHomeRun package, are there still any dvb modules loaded?

— Reply to this email directly or view it on GitHub.

jdierkse commented 10 years ago

@gebruikerh I've uploaded new packages to http://syno.dierkse.nl which should solve your problems.

jdierkse commented 10 years ago

@antoniong, I actually see quite serious crashes in your dmesg; Which DSM are you on, and which version of HDHomeRun have you installed?

TonVH commented 10 years ago

Did following: deleted the old HDHR, installed the new one, restarted NAS then I still could not select although in Dmesg it looked good. So I halted TVheadend and restarted that (to prevent failures of aut. starting) but no go.

It looks very much better but still I cannot select the tuner(s) in Configuration. I enclosed Dmesg (http://pastebin.com/gZggpcY2) and Messages (http://pastebin.com/PBmPwV0U).

Op 1 mei 2014, om 17:24 heeft J. Dierkse notifications@github.com het volgende geschreven:

@antoniong, I actually see quite serious crashes in your dmesg; Which DSM are you on, and which version of HDHomeRun have you installed?

— Reply to this email directly or view it on GitHub.

jdierkse commented 10 years ago

@antoniong, At least the crashes are gone, but it still seems that TvHeadend is started before the HDHomeRun driver. Try restarting TvHeadend.

TonVH commented 10 years ago

This is getting weird.

I stopped & uninstalled TVheadend, stopped & uninstalled HDHR Next rebooted the NAS. Installed HDHR BUT this ends with an error message(!):

May 1 18:46:26 DS414 kernel: [ 938.297279] dvb_core: Unknown symbol refrigerator (err 0) May 1 18:46:27 DS414 entry.cgi_SYNO.Core.Package.Control[1].start[17914]: pkgstartstop.cpp:121 Failed to start package hdhomerun

and Dmesg shows:

[ 812.377046] dvb_core: Unknown symbol refrigerator (err 0)

It's a pity I will have to postpone further testing to tomorrow (HDHR's are needed tonight).

Question. I have also installed DVBlink on this NAS. Can it be that this may be a problem?

Op 1 mei 2014, om 17:44 heeft J. Dierkse notifications@github.com het volgende geschreven:

@antoniong, At least the crashes are gone, but it still seems that TvHeadend is started before the HDHomeRun driver. Try restarting tvheadend.

— Reply to this email directly or view it on GitHub.

jdierkse commented 10 years ago

@antoniong, it seems like Unknown symbol refrigerator has something to do with ACPI support built into the kernel. I'll have a look to see whether I can build the kernel without ACPI support.

jdierkse commented 10 years ago

@antoniong, which exact version of DSM 5 are you running?

jdierkse commented 10 years ago

@antoniong, I've put a version with kernel modules built without ACPI support, and you can download it in http://syno.dierkse.nl/special/hdhomerun_armadaxp_1.0.1-1.spk

gebruikerh commented 10 years ago

@jdierkse. Thanks for the new upload. I will trie it tommorrow and let know the outcome

TonVH commented 10 years ago

@Dierkse At the end of the install procedure, after pressing "Apply" there is an error message "kon de pakket service niet uitvoeren" "could not execute the package service".

I rebooted the NAS but still cannot execute the package.

Op 1 mei 2014, om 21:48 heeft J. Dierkse notifications@github.com het volgende geschreven:

@antoniong, I've put a version with kernel modules built without ACPI support, and you can download it in http://syno.dierkse.nl/special/hdhomerun_armadaxp_1.0.1-1.spk

— Reply to this email directly or view it on GitHub.

jdierkse commented 10 years ago

@antoniong, which exact version of DSM 5 are you running?

TonVH commented 10 years ago

@dierkse: Using DSM 5.0-4482 dated 2014/04/18. The latest update to my knowledge Op 2 mei 2014, om 09:51 heeft J. Dierkse notifications@github.com het volgende geschreven:

@antoniong, which exact version of DSM 5 are you running?

— Reply to this email directly or view it on GitHub.

gebruikerh commented 10 years ago

@jdierkse your new driver works! thanks allot!

TonVH commented 10 years ago

@jdierkse :

Checked versions and if I understand correctly then your driver is for version 4458 and I have version 4482. Can it be that there is a big difference?

In Dmesg (http://pastebin.com/tA3cibPe) & Messages (http://pastebin.com/VMRp40cT) I see a number of error messages pertaining to HDHR. I enclosed them.

naumanmy commented 10 years ago

jdierkse thanks for the HDHomerun drivers. I also installed the tvheadend-testing 3.9 .

hdhomerun_config discover hdhomerun device xxxx found at 192.168.200.45

Though I am running into an issue., Maybe I am not seeing the information correctly. The tvheadend is asking me for a username password and I have no idea what that is so I cannot test that. can you please let me know what the default u/p is? okso I uninstalled it and tried to install the 3.4 from synocom and it asks me for the u/p in a pop up. your pack did not , but it also said that the default is admin admin and I tried that on your package and it works thanks

jdierkse commented 10 years ago

@antoniong, 4482 is the same kernel as 4458, so that version should just work for you. I think removing ACPI from the kernel didn't do much good for the package. All I'm seeing in messages is that it fails to start hdhomerun... Unfortunately at this point I don't know whether the package is flawed for ArmadaXP, or whether you have some specific setup that causes these issues. I haven't heard of anyone else even trying the ArmadaXP package, so until anyone does I think I can't really help you, sorry...

jdierkse commented 10 years ago

@naumanmy, The username and password are by default the same as your admin credentials for DSM.

TonVH commented 10 years ago

@jdierkse: I will try to see if I can get anyone with a DS414 to also test it.

What wonders me is that previous (HDHR) version seemed to install/start correctly. The problem was not seeing any tuners in TVheadend.

Op 5 mei 2014, om 09:52 heeft J. Dierkse notifications@github.com het volgende geschreven:

@antoniong, 4482 is the same kernel as 4458, so that version should just work for you. I think removing ACPI from the kernel didn't do much good for the package. All I'm seeing in messages is that it fails to start hdhomerun... Unfortunately at this point I don't know whether the package is flawed for ArmadaXP, or whether you have some specific setup that causes these issues. I haven't heard of anyone else even trying the ArmadaXP package, so until anyone does I think I can't really help you, sorry...

— Reply to this email directly or view it on GitHub.

TonVH commented 10 years ago

@jdierkse:

I have posted a message on the English & Dutch Synology forums. Hoper another DS414 + HDHR user will react.

Op 5 mei 2014, om 09:54 heeft J. Dierkse notifications@github.com het volgende geschreven:

@naumanmy, The username and password are by default the same as your admin credentials for DSM.

— Reply to this email directly or view it on GitHub.

samukas commented 10 years ago

@antoniong. Curious if you had this issue with DSM4.3 as well, and it's DSM5 that screw things up or if HDHomeRun didn't work with 4.3 either.

TonVH commented 10 years ago

I have never used the HDHR + TVheadend with DSM 4.x.

The strange thing is that DVBlogic has no problem whatsoever with the HDHR. Works like a gem.

Op 5 mei 2014, om 19:53 heeft Samukas notifications@github.com het volgende geschreven:

@antoniong. Curious if you had this issue with DSM4.3 as well, and it's DSM5 that screw things up or if HDHomeRun didn't work with 4.3 either.

— Reply to this email directly or view it on GitHub.

Smiggel commented 10 years ago

I have tested HDHR withTV from @jdierkse on DSM 4.3. Worked excellent. Driver is really stable. Never crashed on me. Only thing is I used it on a DSM 211+.

samukas commented 10 years ago

Confirmed running on the new EDS14 (Armada370 processor) under DSM4.3. No DSM5 for this model yet.