Unraid V6.2 Beta 19 DVB Files

[maciver]

"My Kernel fails to load, the bzimage loads, but then the bzroot fails after 3 dots, for a millisecond I can see a Kernel error and then loops back to the unraid boot menu. "

 

I have the same Problem - Stock Boot 100% working. I think perhaps there's a problem with downloading the Mediabuild Files - i would like to check the hash tags on this Files, can somebody provide crc infos?

 

[CHBMB]

I have migrated the files to the linuxserver.io server, I'll post some dropbox links to try and I'm going to rebuild these and do md5 before uploading.

 

bzimage-6-1-3-openelec

2244acaf7931798e979593920f811586

bzroot-6-1-3-openelec

f836cb09817b5779f6dd7c1038e32986

bzimage-6-1-3-tbs

f75fdcb0e06fc94319bbea7312bfb1f4

bzroot-6-1-3-tbs

ae8f67e957eba14ac767ae69bfe52c3b

bzimage-6-1-3-ddexp

2244acaf7931798e979593920f811586

bzroot-6-1-3-ddexp

002b03d00c0712afe9d4e7daea7131ae

[maciver]

 

the Openelec-Dropbox-Files are working 100%. Thank You

[CHBMB]

 

the Openelec-Dropbox-Files are working 100%. Thank You

Thabks for helping me get to the bottom of this!

[maciver]

I have some problems to get my DVB-C Stick to work:

Nov 4 17:32:03 Tower kernel: si2168 3-0064: found a 'Silicon Labs Si2168-B40'

Nov 4 17:32:03 Tower kernel: si2168 3-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'

Nov 4 17:32:03 Tower kernel: si2168 3-0064: firmware version: 4.0.19

Nov 4 17:32:03 Tower kernel: si2157 4-0060: found a 'Silicon Labs Si2157-A30'

Nov 4 17:32:03 Tower kernel: si2157 4-0060: firmware version: 3.0.5

- Permissions are ok, Problem exists since few weeks - Something in Tvheadend or Firmware Files changed.

 

 

Nov 4 17:28:15 Tower tvheadend[16]: mpegts: 113MHz in KDG - tuning on Silicon Labs Si2168 : DVB-C #0

Nov 4 17:28:15 Tower tvheadend[16]: subscription: 0002: "scan" subscribing to mux "113MHz", weight: 6, adapter: "Silicon Labs Si2168 : DVB-C #0", network: "KDG", service: "Raw PID Subscription"

Nov 4 17:28:19 Tower tvheadend[16]: linuxdvb: Unable to provide signal strength value.

Nov 4 17:28:19 Tower tvheadend[16]: linuxdvb: Unable to provide BER value.

Nov 4 17:28:19 Tower tvheadend[16]: linuxdvb: Unhandled SNR scale: 0

Nov 4 17:28:19 Tower tvheadend[16]: linuxdvb: Unable to provide SNR value.

Nov 4 17:28:19 Tower tvheadend[16]: linuxdvb: Unable to provide UNC value.

[CHBMB]

I have some problems to get my DVB-C Stick to work:

Nov 4 17:32:03 Tower kernel: si2168 3-0064: found a 'Silicon Labs Si2168-B40'

Nov 4 17:32:03 Tower kernel: si2168 3-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'

Nov 4 17:32:03 Tower kernel: si2168 3-0064: firmware version: 4.0.19

Nov 4 17:32:03 Tower kernel: si2157 4-0060: found a 'Silicon Labs Si2157-A30'

Nov 4 17:32:03 Tower kernel: si2157 4-0060: firmware version: 3.0.5

- Permissions are ok, Problem exists since few weeks - Something in Tvheadend or Firmware Files changed.

 

 

Nov 4 17:28:15 Tower tvheadend[16]: mpegts: 113MHz in KDG - tuning on Silicon Labs Si2168 : DVB-C #0

Nov 4 17:28:15 Tower tvheadend[16]: subscription: 0002: "scan" subscribing to mux "113MHz", weight: 6, adapter: "Silicon Labs Si2168 : DVB-C #0", network: "KDG", service: "Raw PID Subscription"

Nov 4 17:28:19 Tower tvheadend[16]: linuxdvb: Unable to provide signal strength value.

Nov 4 17:28:19 Tower tvheadend[16]: linuxdvb: Unable to provide BER value.

Nov 4 17:28:19 Tower tvheadend[16]: linuxdvb: Unhandled SNR scale: 0

Nov 4 17:28:19 Tower tvheadend[16]: linuxdvb: Unable to provide SNR value.

Nov 4 17:28:19 Tower tvheadend[16]: linuxdvb: Unable to provide UNC value.

 

What version/type mediabuild you using before?  What happens if you downgrade to that?

 

TVHeadEnd was updated recently, and although this time mine was fine, I did have to do a reinstall after one of the TVHeadEnd updates.

 

Assuming you've got saarg's mediabuild check plugin installed and that shows that all is well

[maciver]

 

i dont remember - i'm using DVB-C only for one TV Station, all others are IPTV.

 

Media Tree: DETECTED

DVB Adapter: DETECTED

 

I will try to re-install the TVHeadend-Docker.

 

I found this: https://tvheadend.org/boards/4/topics/13782?r=15959

[CHBMB]

6.1.3 Builds all back on ls.io server and md5 confirmed as working..

[Mettbrot]

Hi Guys,

 

Great thread, and good work on the constant updates.

 

My Kernel fails to load, the bzimage loads, but then the bzroot fails after 3 dots, for a millisecond I can see a Kernel error and then loops back to the unraid boot menu.

 

I've had to resort back to 6.0.0 to get this working... I tried 6.1 - same issue.

 

I can't get any logs.. unless there is a way around it?

 

Any ideas?

 

Maybe some flavour of this? http://lime-technology.com/forum/index.php?topic=42800.msg409116#msg409116

 

I never figured it out when it works and when it doesn't. Each update I have to try several times...

[CHBMB]

Hi Guys,

 

Great thread, and good work on the constant updates.

 

My Kernel fails to load, the bzimage loads, but then the bzroot fails after 3 dots, for a millisecond I can see a Kernel error and then loops back to the unraid boot menu.

 

I've had to resort back to 6.0.0 to get this working... I tried 6.1 - same issue.

 

I can't get any logs.. unless there is a way around it?

 

Any ideas?

 

Maybe some flavour of this? http://lime-technology.com/forum/index.php?topic=42800.msg409116#msg409116

 

I never figured it out when it works and when it doesn't. Each update I have to try several times...

I did think of your problem mate, but it turned out this case was due to file corruption when I uploaded them to a new server. 

 

Fixed now as far as I know.

[CHBMB]

6.1.4 done and uploaded.  Also created a file with the md5 for the files to check integrity after the previous problems. 

[chvb]

6.1.4 done and uploaded.  Also created a file with the md5 for the files to check integrity after the previous problems. 

 

thank you very much. The Openelec Media Files are working.

[avpap]

I would like to ask a question that might be naive, but I was really wondering why the tuner card drivers are not integrated into the "official" unraid files? Is limetech reluctant to do so? Is it some sort of copyright problem?

[JonathanM]

I would like to ask a question that might be naive, but I was really wondering why the tuner card drivers are not integrated into the "official" unraid files? Is limetech reluctant to do so? Is it some sort of copyright problem?

Support. If they don't include it, they don't have to debug and support it. There are so many different tuner models, and since limetech is USA based, they would have no easy way to support and diagnose an issue with, for example, a european model of tuner and the myriad of signal options that exist in the european market.

 

As VM support matures, you should be able to pass through the tuners and use them in the VM OS, assuming your hardware supports passthrough in the first place. I don't think limetech will ever be persuaded to natively support hardware that will only ever work in a specific market for a limited number of users when alternatives are available using VM's.

[avpap]

That makes a lot of sense. Thank god for active communities!! They step up to support endeavors that would otherwise fall through.

[CHBMB]

I would like to ask a question that might be naive, but I was really wondering why the tuner card drivers are not integrated into the "official" unraid files? Is limetech reluctant to do so? Is it some sort of copyright problem?

 

Put simply, DVB support in Linux is a bit of a mess.... 

 

There are some drivers included in the kernel by default, but that option isn't enabled in Unraid by default and requires recompiling to activate.

 

Then other drivers need to be added in, but they aren't all "compatible" hence the reason there are 3 different mediabuilds.

 

To be fair to LimeTech, I was in discussion with them about natively producing a Mediabuild but for the reasons above it was technically not possible to produce a single, unifying, mediabuild which would have been the goal, and was therefore decided to not proceed for entirely understandable reasons.

 

Also some of the drivers are closed source and updating the kernel may cause them to break (this happened with the TBS drivers after the update to 6.1.0 and I had to contact TBS and they eventually released some new drivers)

 

As jonathanm states, support is also a big reason, as a commercial company, they cannot be expected to introduce a feature and not provide support and with the myriads of different tuners that would be difficult.

 

[CHBMB]

6.1.5 Builds are all done & uploaded with md5. 

[EdgarWallace]

Your are sooooo quick 

 

Thanks a lot for providing....working very well as always.

[CHBMB]

Your are sooooo quick 

 

Thanks a lot for providing....working very well as always.

 

You been talking to my wife?!   

 

[CHBMB]

6.1.6 All done, uploaded and md5 available. 

[DMcK]

too fast! I had updated the files to 6.1.5, but hadn't rebooted. This will save me a reboot.

 

[saarg]

Your are sooooo quick 

 

Thanks a lot for providing....working very well as always.

 

You been talking to my wife?!   

 

[CHBMB]

too fast! I had updated the files to 6.1.5, but hadn't rebooted. This will save me a reboot.

 

You might want to wait a day or two as I suspect 6.1.7 won't be too far away.. 

[DMcK]

lol. i will.

[chvb]

The 6.1.6 Openelec Media Files working fine.

 

Thank you.