s.Oliver

i see. do maybe different models of your reader exist? (smartcard size)

no problem, i can live with your time schedule and appreciating your effort. thx. man. do you just tune into FTA channels?

just had a look into the 4.0.5.5 files and couldn't even find that VID in there. so i guess they fuxored somewhere, something badly up. i sent them an email and so we'll see. thx. saarg for helping out this far.

my translated text earlier, seemed to be an answer my retailer got from HID. there the version 4.0.5.5 was recommended as the current latest driver (non-beta anyway), which he used/tested with debian wheezy (64bit) and confirms it working/recognizing the reader out-of-the-box. so, i would like to ask, if you could use that version 4.0.5.5 (the link earlier posted) and incorporate it, instead of the one actually being included (beta 4.2.8). maybe they screwed up the list of PID/VIDs in the beta driver. thx. saarg

yah, thanks for that well, i tried adding it, but somewhere there seems to be still a small kind of problem. starting up the docker after the change it's log shows one 'good' line as expected: [HID Global] HID Global OMNIKEY CCID driver x86_64 v4.2.8 [email protected] but then these errors: 00000000 readerfactory.c:1110:RFInitializeReader() Open Port 0x200000 Failed (usb:076b/3031:libudev:0:/dev/bus/usb/001/006) 00000008 readerfactory.c:375:RFAddReader() OMNIKEY CardMan (076B:3031) 3121 [OMNIKEY 3x21 Smart Card Reader] init failed. 00000009 hotplug_libudev.c:520:HPAddDevice() Failed adding USB device: OMNIKEY CardMan (076B:3031) 3121 so the changes made seem to get picked up, but... (inserted a good reason here) it won't accept/activate it properly. got an idea?

...from my retailer i got the following response (freely translated to english): the new models of omnikey-readers have a new usb identifier (PID/VID). for those models you'll need a recent driver. old versions (v3.9.0 and earlier) won't recognize those identifiers. customers need to download a recent driver from our website, for linux these are 4.0.5.5. if linux user want to use CCID drivers, they also need to update. the new versions of the CCID drivers should recognize the new PID/VID from the readers firmware 2.04. if there are no newer CCID drivers for your linux variant, which recognize these new PID/VID, it is possible to manually add them to the config. you need to edit the file /etc/libccid_info.plist and add the new PID/VID to three corresponding places and add also the name of the reader. we are encouraging you to try out our new driver version 4.0.5.5; get them here: https://www.hidglobal.com/drivers/21278 for 64bit version (replace the last '8' with '7' to get the 32bit version) @saarg: the link provides a file named 'ifdokccid_linux_x86_64-v4.0.5.5.tar.gz' (402,5 KB). but it looks like this driver is way older than what you implemented? there's a v4.2.8 listed from 08.06.2016 hmm… comparing what i see under Tools/System Devices: Rev. A (which works): ID 076b:3022 OmniKey AG CardMan 3021 (even though it is a 3121) Rev. B (doesn't work): ID 076b:3031 OmniKey AG @saarg: could that help a bit to get that newer one also working? thx. for any help. that machine is for a friend and it would be too bad to not get it working, just because of a cheap usb-reader. i already convinced him to get an unRAID system built, but now we need the final touches working.

ok, i might found something... despite having ordered the same model, despite it looking absolutely identical it seems to be different. i could do a crosscheck a few minutes ago and discovered, that the 1st (which works on 6.2.4) also works on 6.3.2. the 2nd (new one) doesn't work on 6.2.4. so it's not a docker-/passthrough bug/problem. they both have same name, only a slightly different part no. and the 1st is rev. A and the 2nd (new) is rev. B. @saarg: but you checked/said there are no newer drivers out there... bummer. how can they fuxor up this bad with a rev. B model? any good advice on usb-smartcard readers for pay-tv cards from you guys?

which usb-readers for smartcards (encrypted ones for cable, satellite) do you guys successfully use on 6.3 onwards? maybe (if it is really an kernel incompatibility) i could simply get another one, which is verified working by someone here. thx.

hmm... what else i could test? are there any unraid shell commands we could use to "talk" to the usb-reader and verify it isn't an incompatibility? ok, does that last line in the docker log (when it has started up) which indicates it found a passed through device show up on every-bodies log as well? thx. saarg, for being quick here.

hey guys! back here with another oscam/usb-reader/docker/passthrough-question. for a test-installation i used a pc which did exactly the same (= same hardware). software is newer alas latest unRAID 6.3.2 with current oscam docker. passing through an omnikey 3132 usb-reader to oscam-docker with --device=/dev/bus/usb/00x/00x (x=actual numbers from host). when trying to use the reader, oscam segfaults, oscam log shows Omnikey [pcsc] Restarting reader / Omnikey [pcsc] creating thread for device 0 / Omnikey [pcsc] Cannot open device: 0 now when i compare the setup to a working machine with unRAID 6.2.4 and the same reader-hardware, i do see in the docker log as last line (and guessing here) that the reader got recognized = passed through successfully; it reads: [HID Global] HID Global OMNIKEY CCID driver x86_64 v4.2.8 [email protected] this line is missing from docker log on the new machine setup. i tried various usb-ports (even exact the same one, that once 6.2.4 ran on this same machine and same reader) worked beautifully. it seems, that the extra line parameter has no effect. on the other hand, oscam shows under Readers / Scan USB that device with the correct numbers (as they are used for the passthrough). well, has anything changed with 6.3.x versions of unRAID and usb-passthrough to dockers? i tried to find glues for it, but haven't. thx. and hope you're all doin' fine.

yep. not with the admin user, not with the additional user, i'm kinda at a loss. ok, am i right (can't remember anymore when setup the 1st time within the v6.1.9) that the admin-user (created at install time) has all capabilities? SOLVED! well, couldn't get it running with new installs, then tonight copied my appdata from the old install (6.1.9er unRAID) and thought: hurray, the recording button is back! but, it didn't record and i saw errors with unix permissions for directories (it tried to set the internal /recordings to 775 and couldn't). changed them accordingly and now it runs as it should.

well, one time i tried to setup tvh after the wizard (then with this mixture of tuners), but somehow couldn't get it to scan for services and gave up. thought that the wizard maybe made some settings somewhere and didn't feel for digging through all of it (not knowing that it eventually could be fixed anyway). probably will try once again.

yep. not with the admin user, not with the additional user, i'm kinda at a loss. ok, am i right (can't remember anymore when setup the 1st time within the v6.1.9) that the admin-user (created at install time) has all capabilities?

ok, today i switched at least 2 times between the closed / open source drivers for testing/fixing. but i got to say, the open source drivers seem to have some kind of problems with the setup assistant routine. i couldn't select all 4 tuners for dvb-c reception. all possible (offered from the tbs-card) tuners needed to be selected at least once, i could not select more than 2x the dvb-c tuner. strange.

solved – it was the same misconfiguration as with tvh. the basic view of the docker setup didn't provide/show the extra parameters field. i had set it up manually, but that didn't work. now with advanced view ticked, i could enter the data into that field and it starts up correctly. BUT: back to tvh – all seems to work fine, except that i can't record anything. i never ever see the button to click for record. i provided the default mapped path to several different shares, even an unassigned devices one. it simply doesn't matter, i can't record. but why?

hey CHBMB! thx. for the hint – i was in "Basic View" (didn't look at that corner space) and it didn't show the (known from v6.1.9) field "Extra Parameters", so i thought, ok, define a device… it seems to be alright now, i can see my tuners now. another question to this: i read awhile ago, that in the future, or at least starting from unRAID built 6.3 onwards. just the open source drivers are supported; is that so? and thanks!

Part 2: OSCam docker GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 18:15:20 00000000 s >> OSCam << cardserver log switched, version 1.20-unstable_svn, build r11342 (x86_64-alpine-linux-musl) 18:15:20 00000000 s (main) System name = Linux 18:15:20 00000000 s (main) Host name = unRAID 18:15:20 00000000 s (main) Release = 4.4.30-unRAID [HID Global] HID Global OMNIKEY CCID driver x86_64 v4.2.8 [email protected] 00000000 readerfactory.c:1110:RFInitializeReader() Open Port 0x200000 Failed (usb:076b/3022:libudev:0:/dev/bus/usb/003/002) 00000004 readerfactory.c:375:RFAddReader() OMNIKEY CardMan (076B:3022) 3021 init failed. 00000005 hotplug_libudev.c:520:HPAddDevice() Failed adding USB device: OMNIKEY CardMan (076B:3022) 3021 18:15:20 00000000 s (main) Version = #1 SMP PREEMPT Sun Nov 6 19:10:12 GMT 2016 18:15:20 00000000 s (main) Machine = x86_64 18:15:20 00000000 s (main) creating pidfile /tmp/.oscam/oscam.pid with pid 236 18:15:20 00000000 s (main) signal handling initialized 18:15:20 00000000 s (stat) loadbalancer: could not open /tmp/.oscam/stat for reading (errno=2 No such file or directory) 18:15:20 00000000 s (main) waiting for local card init 18:15:20 6D2C1A5D h (webif) webif: decompressed 178006 bytes back into 434104 bytes 18:15:20 6D2C1A5D h (webif) HTTP Server running. ip=0.0.0.0 port=8888 18:15:20 00000000 s (main) init for all local cards done 18:15:20 00000000 s (emmcache) loading emmcache disabled since no reader is using it! 18:15:20 00000000 s (emmcache) loading emmstats disabled since no reader is using it! 18:15:20 00000000 s (anticasc) anti cascading disabled here are errors obviously, but can't understand why. i did try already different usb-ports (v3.0, v2.0) didn't change anyhting, same errors (with expected usb-port number).

hey saarg, thanks for joining in so fast! sure, well, i would like to start with TVH. this is the log from the docker start: ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 2017-01-22 17:52:55.210 [ INFO] main: Log started 2017-01-22 17:52:55.211 [ INFO] http: Starting HTTP server 0.0.0.0:9981 2017-01-22 17:52:55.213 [ INFO] htsp: Starting HTSP server 0.0.0.0:9982 2017-01-22 17:52:55.213 [ ERROR] satips: use --satip_bindaddr parameter to select the local IP for SAT>IP 2017-01-22 17:52:55.213 [ ERROR] satips: using Google lookup (might block the task until timeout) 2017-01-22 17:52:55.267 [ INFO] config: loaded 2017-01-22 17:52:55.267 [ INFO] config: scanfile (re)initialization with path <none> 2017-01-22 17:52:55.268 [ INFO] bouquet: new bouquet 'Canal Digitaal SD' 2017-01-22 17:52:55.268 [ INFO] bouquet: new bouquet 'Canal Digitaal HD' 2017-01-22 17:52:55.269 [ INFO] bouquet: new bouquet 'TV Vlaanderen SD' 2017-01-22 17:52:55.269 [ INFO] bouquet: new bouquet 'TV Vlaanderen HD' 2017-01-22 17:52:55.269 [ INFO] bouquet: new bouquet 'TéléSAT SD' 2017-01-22 17:52:55.269 [ INFO] bouquet: new bouquet 'TéléSAT HD' 2017-01-22 17:52:55.269 [ INFO] bouquet: new bouquet 'AustriaSat Astra1' 2017-01-22 17:52:55.269 [ INFO] bouquet: new bouquet 'Canal Digitaal HD' 2017-01-22 17:52:55.269 [ INFO] bouquet: new bouquet 'TV Vlaanderen HD' 2017-01-22 17:52:55.269 [ INFO] bouquet: new bouquet 'TéléSAT HD' 2017-01-22 17:52:55.269 [ INFO] bouquet: new bouquet 'AustriaSat Astra3' 2017-01-22 17:52:55.269 [ INFO] bouquet: new bouquet 'Skylink: Czech Republic' 2017-01-22 17:52:55.269 [ INFO] bouquet: new bouquet 'Skylink: Slovak Republic' 2017-01-22 17:52:55.269 [ INFO] dvr: Creating new configuration '' 2017-01-22 17:52:55.269 [WARNING] access: Created default wide open access controle entry 2017-01-22 17:52:55.269 [ INFO] csa: Using SSE2 128bit parallel descrambling 2017-01-22 17:52:55.269 [ INFO] descrambler: adding CAID 2600 as constant crypto-word (BISS) 2017-01-22 17:52:55.269 [ INFO] epggrab: module eit created 2017-01-22 17:52:55.269 [ INFO] epggrab: module uk_freesat created 2017-01-22 17:52:55.269 [ INFO] epggrab: module uk_freeview created 2017-01-22 17:52:55.269 [ INFO] epggrab: module viasat_baltic created 2017-01-22 17:52:55.269 [ INFO] epggrab: module Bulsatcom_39E created 2017-01-22 17:52:55.269 [ INFO] epggrab: module psip created 2017-01-22 17:52:55.274 [ INFO] epggrab: module opentv-ausat created 2017-01-22 17:52:55.274 [ INFO] epggrab: module opentv-skyit created 2017-01-22 17:52:55.275 [ INFO] epggrab: module opentv-skynz created 2017-01-22 17:52:55.275 [ INFO] epggrab: module opentv-skyuk created 2017-01-22 17:52:55.276 [ INFO] epggrab: module pyepg created 2017-01-22 17:52:55.276 [ INFO] epggrab: module xmltv created 2017-01-22 17:52:55.276 [ INFO] spawn: Executing "/usr/bin/tv_find_grabbers" 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_ar created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_ch_search created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_combiner created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_dk_dr created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_dtv_la created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_es_laguiatv created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_eu_dotmedia created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_eu_egon created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_eu_epgdata created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_fi created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_fi_sv created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_fr created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_fr_kazer created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_hr created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_huro created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_il created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_is created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_it created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_na_dd created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_na_dtv created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_na_tvmedia created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_nl created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_pt created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_pt_meo created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_sd_json created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_se_swedb created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_se_tvzon created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_tr created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_uk_atlas created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_uk_bleb created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_uk_rt created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_uk_tvguide created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_file created 2017-01-22 17:52:56.978 [ INFO] epggrab: module /usr/bin/tv_grab_wg created 2017-01-22 17:52:56.979 [ INFO] epgdb: gzip format detected, inflating (ratio 72.3% deflated size 138) 2017-01-22 17:52:56.979 [ INFO] epgdb: parsing 191 bytes 2017-01-22 17:52:56.979 [ INFO] epgdb: loaded v2 2017-01-22 17:52:56.979 [ INFO] epgdb: config 1 2017-01-22 17:52:56.979 [ INFO] epgdb: brands 0 2017-01-22 17:52:56.979 [ INFO] epgdb: seasons 0 2017-01-22 17:52:56.979 [ INFO] epgdb: episodes 0 2017-01-22 17:52:56.979 [ INFO] epgdb: broadcasts 0 2017-01-22 17:52:56.979 [ NOTICE] START: HTS Tvheadend version 4.1-2415~ge5f5a42 started, running as PID:212 UID:99 GID:100, CWD:/var/run/s6/services/tvheadend CNF:/config 2017-01-22 17:52:57.116 [ INFO] scanfile: DVB-S - loaded 1 regions with 112 networks 2017-01-22 17:52:57.116 [ INFO] scanfile: DVB-T - loaded 43 regions with 1106 networks 2017-01-22 17:52:57.116 [ INFO] scanfile: DVB-C - loaded 17 regions with 56 networks 2017-01-22 17:52:57.116 [ INFO] scanfile: ATSC-T - loaded 2 regions with 9 networks 2017-01-22 17:52:57.116 [ INFO] scanfile: ATSC-C - loaded 1 regions with 5 networks 2017-01-22 17:52:57.116 [ INFO] scanfile: ISDB-T - loaded 2 regions with 1297 networks after the startup i do see the normal setup screens and following along the part with "Network 1" doesn't show any tuner. when finsihing the assistant and going to "TV-Adapter" it doesn't list anything beside that default "TV-Adapter" with the yellow folder-icon. but nothing there. ok, just be sure about the difference from 6.1.9 to 6.2.4: the configuration of the docker is a little bit different. did i do it right? my settings are all at default values, except i added a device with name "TBS-Card", value "--device=/dev/dvb/" (which is listed in file system with owner "nobody:users" with official drivers and curiously was "root:root" with the open source drivers). correct so far?

hey guys. sorry, i need help. totally crashed here, can't think straight anymore. wanted to move my tvheadend-solution from an old pc-box running 6.1.9 to my newer server-box with 6.2.4. that includes a usb-card reader & tbs card dvb-c. the devices are recognized on 6.2.4, the unRAID DVB-Edition does report all detected right, but: a) oscam can't initialize the usb-device; despite passthrough and recognizing the correct usb-device b) tvheadend doesn't recognize the tuner card when the setup assistant is run (i tried both TBS driver packs official & open source) everything which came to mind i tried, but know i'm left empty handed here. guess i need a coffee first, i'll come back later. maybe someone has an idea...? thx.

i second the notion to have a stop mover functionality in the gui. a friend of mine has setup his first unRAID after seeing it at my place. now (cause of the wording "prefer") he changed a share and the mover started to copy all contents onto the cache drive – which is a SSD – and chokes becuase of too less space. now i tried alle commands which were recommended here in this thread – all DON'T work. they don't stop the mover! i would bet this situation will pop up more often and because of the misleading wording chosen for it's different kind of use cases. if nobody has a perfect one/two word naming, then (and why not), give the thing a small description in form of "Prefer (move/keep all share contents)" now, back to the question: how to stop a running mover script?

hey Johnny G., i guess you mixed up the numbers for the TBS cards, or? the 6502 is the DVB-T2/C card and the 6985 is the DVB-S2 one. i write here, to clear up your usage and therefore maybe driver related questions/answers from CHBMB. did i understand it correct, that you want to use one (of 2) 6205 cards for DVC-C and the other for DVB-T2 and then the only one 6985 for DVB-S2? if so, then we would have driver wise a complete separation of DVB-protocols – each card would only have to handle one DVB-protocal at a time. maybe this gives more insight for CHBMB and the necessary driver compiling/usage. greets, oliver

perfectly understandable – thx. alot for trying! well, i would also use VPN, but this backup-software doesn't support FTP – just SFTP. may i ask, what errors you were seeing? and is there's anything special related to unRAID v6.2 (is it compatible)? thx. again, oliver

yes sir, RobJ i did that. but have you read my bold SFTP tag, hihi -> Jay_III: that would be absolutely fantastic! :-)

hey guys! i'm in a need soon to have a SFTP server running and ideally that would be on unRAID (because of data storage). i heard of ProFTP (by name) quite often for some time and it seems to be a perfect fit. but, as a quick read brought up, enabling the secure protocol seems to be a little bit of a challenge. maybe someone here did that already and could give a little bit of feedback? i've no problem with fiddling through .config files and adjusting values, etc. but because of not having used ProFTP myself, for sure there are some tipps around (or maybe someone documented that journey) thx.

new version available from the website. erm – saarg...? MakeMKV v1.10.2 (11.9.2016 ) Added support for AACS v62 Improved support for BD-Java discs Small user interface improvements Bug fixes: The 3D left/right MVC view information was not preserved correctly when creating 3D MKV file