s.Oliver

@CHBMB – here my update on LibreELEC build & Digital Devices TV-Card it seems that with every beginning of a reording i see a mixture out of these errors in the TVH docker: 2018-03-14 20:11:30.052 [WARNING] linuxdvb: Unable to provide BER value. 2018-03-14 20:11:30.260 [WARNING] TS: DVB-C Network/130MHz/Channel Name Transport error indicator (total 1) 2018-03-14 20:12:00.051 [WARNING] linuxdvb: Unable to provide BER value. 2018-03-14 20:12:00.051 [WARNING] linuxdvb: Unhandled ERROR_BLOCK_COUNT scale: 0 2018-03-14 20:12:00.051 [WARNING] linuxdvb: Unable to provide UNC value. 2018-03-14 20:12:00.053 [WARNING] linuxdvb: Unable to provide BER value. 2018-03-14 20:12:00.054 [WARNING] linuxdvb: Unhandled ERROR_BLOCK_COUNT scale: 0 2018-03-14 20:12:00.054 [WARNING] linuxdvb: Unable to provide UNC value. 2018-03-14 20:12:00.143 [WARNING] TS: DVB-C Network/530MHz/Channel Name Transport error indicator (total 1) 2018-03-14 20:12:00.161 [WARNING] TS: DVB-C Network/522MHz/Channel Name Transport error indicator (total 1) 2018-03-14 20:12:00.224 [WARNING] tbl-pass: pass-eit: -: invalid checksum (len 109, errors 1) 2018-03-14 20:12:00.262 [WARNING] tbl-pass: pass-eit: -: invalid checksum (len 3638, errors 1) can't check the files (they just started recording) but i guess these errors at the beginning aren't (actually) serious, but because of TVH listing them in the list of running recordings (and so later in finished recordings) i can't tell a day or two later, if these errors were serious or not (because it can be, that additional errors occur while they get recorded). so in comparison to the github version it's a definite drawback for me. i've lots of recordings running, so it arises as a nightmare when i'm about to decide which to keep and which are worth of being treated any further (removing ads, etc.) and put them into the plex library. if i might ask for one more 6.5.x Github build? please. i'm willing to do testing with LibreELEC from time to time, but now, it's not the standard i was enjoying.

definitely related to usb/serial devices, so something for @saarg in future releases of kernels, to watch out for.

i've spotted this line in the unRAID log: Mar 14 14:53:57 unRAID kernel: ftdi_sio ttyUSB0: use of SPD flags is deprecated think it's new since v6.5 (probably cause of newer kernel drivers and their requirements?).

yeah, i do see occasional use for OSCam on unRAID without DVB-Build.

before as: crw-rw---- 1 root dialout 188, 0 Mar 14 12:26 ttyUSB0 i can confirm now, that chmod'ding to 777 was enough, to get it going. i left the user:group at the display values (root:dialout). THANKS! @CHBMB couldn't you extract from an installed oscam docker it's used --extra parameters and use these settings to do the necessary correction on the permissions? or let's have a configureable option in the DVB-Plugin to specify it manually. no?

Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='oscam' --net='host' -e TZ="Europe/Berlin" -e HOST_OS="unRAID" -e 'PGID'='100' -e 'PUID'='99' -e 'TCP_PORT_8888'='8888' -e 'TCP_PORT_10000'='10000' -e 'TCP_PORT_10001'='10001' -e 'TCP_PORT_10002'='10002' -v '/mnt/user/appdata/oscam':'/config':'rw' --device=/dev/ttyUSB0 'linuxserver/oscam:66'

hey CHBMB, thx. for looking into it. output of lsusb: root@unRAID:/dev# ls -la /dev/bus/usb/ drwxr-xr-x 6 root root 120 Mar 14 12:26 ./ drwxr-xr-x 3 root root 60 Mar 14 12:26 ../ drwxr-xr-x 2 root root 80 Mar 14 12:26 001/ drwxr-xr-x 2 root root 80 Mar 14 12:26 002/ drwxr-xr-x 2 root root 140 Mar 14 12:26 003/ drwxr-xr-x 2 root root 80 Mar 14 12:26 004/ hmm… how to lookup the complete docker run command from an installed docker?

have an Digital Device Card running with the LibreELEC build. do you use a docker which access an USB device like a card reader?

didn't need to do this. so it seems different for diff. users (you were maybe on RC before?).

hey @CHBMB just installed 6.5 LibreELEC and ran immediately into a problem: OSCam docker doesn't see usb-reader. worked always flawlessly, this time errors with "Opening device /dev/bus/usb/003/003 (errno=13 Permission denied)" or ".../dev/ttyUSB0..." (same access denied). i compared the permissions for the device, they seems same as before. i tried to set docker as "Privilleged" no joy also. need help, please.

@CHBMB sorry, been overly busy with day-to-day workload; couldn't respond earlier. i'll test the final v6.5 LibreELEC build with my new Digital Devices Tuner card and report back. last test i did showed lots of errors like these: [WARNING] linuxdvb: Unable to provide BER value. [WARNING] linuxdvb: Unhandled ERROR_BLOCK_COUNT scale: 0 [WARNING] linuxdvb: Unable to provide UNC value. [WARNING] tbl-pass: pass-eit: -: invalid checksum (len 785, errors 1) [WARNING] tbl-pass: pass-sdt: -: invalid checksum (len 388, errors 1) [WARNING] tbl-pass: pass-eit: -: invalid checksum (len 18, errors 1) although shown as warning in the TVH log, they were shown as errors to the responding (running at that time) recordings. i hadn't got the time back then, to investigate, if these errors would've been discoverable in the recorded shows, but because of the massive amount (like 15-30 errors per recording) i switched back immediately to the github build – and had no errors at all. and i need to add, that this github build (6.4.1) with that new DD card outperforms the previous TBS card (which showed a few errors from time to time compared to no errors with the DD card). hopefully the v6.5 LibreELEC build (and the associated drivers) will work like the ones right now.

i see, and don't get me wrong, didn't want to back off being a test-dummy ok, i did a short test with the LibreELEC build and my card. first things first: your plug-in reports v1.2.2 as drivers and everything is detected right. all tuners are recognized and they seem to work. BUT: i see alot of errors reported through TVH and also more errors in the TVH log (all in comparison to the github build to which i'm back now). i'll report a bit more detailed, but need to get some sleep now.

ah, thanks! i see. well, as long as you provide these dedicated builds i'll probably simply use them – and afterwards i hopefully remember that i've to use that LibreELEC build

ok, but i simply took the digital devices github build

well, we'll need your magic in the future, because in my tests i've seen no driver (or let me say detection of it) while using the standard unRAID build and an Digital Devices tv-card. if i would need to guess, i would say, that lime tech doesn't compile them in their kernel (probably as to get it as small as possible). my TBS 8-tuner DVB-C card had a small fan, which cried to loud. so i've replaced it with the DD Max A8, which is a passiv-cooled card. all seems to working well and it was a simple breeze to change TVH settings (2 min.) to use this card; and all was running immediately.

ok, thx. if drivers are included in kernel, do you have to do extra steps (or none at all) to make them useable for unRAIDs kernel? (JFMI)

ok, just had a phone call to digital devices and learned, that their tv-card drivers are incorporated into the linux kernel since v4.14. that means, we shouldn't have any problems with driver support, right? @CHBMB is that correct?

yah, i simply use only one dvb-broadcasting standard; doesn't add value here to use dvb-t, if you got dvb-c already. well, i'm waiting for @CHBMB to chime in to decide if digital device's 8 tuner card is an option. would make lots of things easier, even though, they charge a bit of an extra over TBS cards.

thx. rick. – good to know that this option would work. when i replaced the 6205 with the 6209 i had only to enable all the tuners and map the dvb-c network to them – everything else worked immediately. was a perfect thingie, except that noisy fan.

@CHBMB i've a TBS 6209 (Octa)-Tuner card in my system now, and all seems to work as expected. but: this card has an active cooling fan, which is annoying (loud to my ears). i'll probably return the card and struggle what to do next. so i could: scenario 1: buy another TBS-6205 (waste one more PCIe slot, which could backfire later) and interconnect card 1 OUT to card 2 IN – at least so i don´t need to use a splitter beforehand. question 1: because of two times (same) PCIe cards, will they both get pass'ed through (--device=/dev/dvb/) and seen correctly from TVH? is it then adapter 5-8 for the 2nd card or will there be another number scheme? scenario 2: buy one Digital Devices DD Max A8 TV card (also octa-tuner dvb-c) but has passiv cooling (so no waste of a PCI slot and quiet). question 2: how about the device driver support from digital devices? i can't recall exactly, but didn't they have problems? or would we expect any problems with drivers and/or TVHeadend? thx.

ya, ya, i see ? well, we got quite a bunch of muxes here, so i‘m hitting the ceiling now and then. if a lot of recordings are at the same time, i need to look at my mux-list to see, if my 4 tuners are enough.

still on 6205 (need to sell that one first) do we have to expect bigger changes or non-working situations? got a few friends which will get an unRAID/TVH-solution soon.

i can report, that at least my card was detected and TVH is recording now a few titles. can't tell though, if these are ok (at least i don't see any unusual error countings up to now).

what about taking the drive out, formatting with another machine and put it back in (so no old structures, partitions, etc. on drive).?

JFYI: just updated to the latest version (as of yet – 2018.01.07a) of UD and now see this error: Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 920 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1099 i've no shares, etc. mounted. maybe it is assuming, that there's at least one mounted?