s.Oliver

Yeah, strange thing. That site was up for years and suddenly it disappeared.

thx. saarg - i’ll try that later.

@saarg maybe it's only cosmetic, but that latest oscam update (you switch to another source for oscam, right?) shows as build version r0. which version actually is it? same as the last one from the streamboard source? why i ask? you know my problems with tvheadend (posted on the tvheadend thread) since just a few days ago. in between i setup a complete new server (docker setup complete from scratch, incl. new usb stick in trial for unRAID) everything possible to think of (other destinations for recordings, etc.) – and now i'm struggling to find any other reasons, why my rock-solid tvh-docker has these super strange problems. and maybe, that would be my hope, maybe it's because of that new oscam build; that could explain alot and from the timeline would fit into this scenario. question: could i please ask for that docker build before the change? i remember it was something like r11391. that would be awesome. (i haven't found any tipps in regard of specifying a targeted version which to pull for the docker). thx. alot saarg, i hope you can help me out.

thx. for that. i did yesterday a re-install (and even a total rebuild of the docker.img) of the release:4-2 and also got the same version than you. but, i got a whole new bunch of problems, all fixed but one: some recordings just write the first few B/KB in the file and then it suddenly stops. Status / Abonnements shows still incoming data but nothing for outgoing – so the file isn't growing in size. the files are too small for inspection with a video editor (complains immediately that no video titles can be found). i never had this error before (with really alot of recordings happened). i use an unassigned drive as destination. since that, i did several re-installings (even back to latest 4.3.556) all show now the same problem. whenever a file is grown bigger than a few Bytes/KiloBytes it is finishing successfully. i checked logs from TVH/unRAID and there's nothing to see, all is like it always was. i'm pulling hairs now, because suddenly TVH has become unreliable in doing recordings. damn, wish i never had tried to get this version/updating stuff working. btw: again an update ready was shown for TVH release:4.2 docker, with (then) nothing to update – oh well. i'm still on unRAID v6.3.5, if that matters. more infos: it seems to be happening every 3rd/4th recording. and just now i had the case, that even if i aborted the recording and started it again it would not succeed – 4 tries 4 times the same result. but i could immediately live-stream this channel without problems. so this proves (in my opinion) that it is related to writing data to disk (and so maybe even not a TVH only problem). but then, i have not changed anything unRAID related beside the re-/new installation of TVH/dockers. bang. puff. dead.

well, we'll see what happens, i keep you posted here. need to get it addressed anyway, because always getting the impression/post of having an update is driving me mad.

ya, saw it just a few secs ago also. and that's the stable release then, probably, right? so mine is behind. will try to do a new install and see what happens then.

hihi, i did that in the past somehow i never understood which version was which tree (stable, unstable, development). well, this time i see this: that would probably fit (if it's the same tree). but that means that my docker is with 4.2.3-39 way behind.

ok, do you know the latest version in the release-4.2 as of yet?

hey guys, i reverted back to the "linuxserver/tvheadend:release-4.2" version and wanted to report/check for one failure/feature seen here with the update process of the docker. my installation of TVH shows this version "HTS Tvheadend 4.2.3-39~ge195d1845" as installed (i guess it was that version from start on). now, every time when dockers get checked for newer versions, i get notified that there is a newer one for TVH. letting it update doesn't resolve to any other/newer version – it stays the same. while it's showing the updating dialog there doesn't get one new part downloaded (it takes just 2-3 secs); so actually it ends in a pure restart of the docker with the same version. is it a known problem (bug) with version checking? has anybody the same? thx. and have a good day.

well, i read it, buy maybe i'm a little bit dumb here to understand the exact definition (wanted to make it a one time right setup, without much trial and error because of unRAID usage here, i would guess i need to add a custom variable while creating a new docker, right? if so, and i interpret a bit here, i could imagine it has to look like this: Name: my own name for it Key: linuxserver/tvheadend Value: release-4.2 Default Value: (can/must be empty?) if this is correct, then halleluja... please correct if wrong, else i can imagine, it helps quite a few people to see it simply put here. thx. as always :-)

ok, want to chime in, because of different 4.3.x troubles i cope with. i also will revert back to the 4.2 branch, but with a 'small' twist. i will keep my old installation, because of all the recordings done – i need to be able to search, sort and delete them (i guess still no one has overcome the problem of keeping/adjusting old recordings into a new installation of TVH – and maybe it isn't really possible at all; only read a few lines about it). so when i'll install a second docker for TVH i'll have to set manually the tag 'release-4.2'. i would guess this will provide updates into the 4.2.x release as they (if ever) come. also i would think it will then update to the 4.2.1, right? i wouldn't want to set it to 4.2.1 straight and then maybe a few months from now a 4.2.2 will be released. but because my installation doesn't show any tag field (it's current 4.3.x) i would need to guess how this field must be called to serve as version tag field. saarg: could you just please give a straight simple line how it is called? thx. alot.

ah, right – forgot that bug. safari shows this too – constantly reloading (and only showing the epg-tab); never completes and so can't use it. now i need to use a second browser (only for tvh). oh well...

yep, noticed the change as well. since then, safari (on macOS) also only shows the epg-tab – nothing else (and btw. it even takes firefox a second or two before it displays the other tabs). before that change, both browsers did show all tab instantly.

alright thx. i'll try that one (could get it faster and cheaper), but if it doesn't work will try the infinity usb smart one.

found this one: "Smartmouse / Easymouse 2 USB Premium" all talk is that most linux'es support it directly (has an FTDI chipset). protocols supported: smartmouse / phoenix – does smartmouse here mean smartreader (or smargo) in oscam? what do you think of that one?

yah, that would have been my next question (hey, how do you pulled that one – how far do brain waves travel?) ok, will probably look for one of those mentioned ones. might ask you then, if you think/know if it's supported.

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.