Cessquill

Thanks for that - I'm guessing that between TBS official, OpenSource, 6.3.5 and 6.4.0 I might be comparing apples to oranges, but I've been taking a look. I've extracted what I think is the important part of 6.3.5's system log after a boot. Contains all references to TBS, plus anything else surrounding that looked related. Oct 19 07:33:48 unRAID1 kernel: Linux video capture interface: v2.00 Oct 19 07:33:48 unRAID1 kernel: pps_core: LinuxPPS API ver. 1 registered Oct 19 07:33:48 unRAID1 kernel: TBS version 160405 Oct 19 07:33:48 unRAID1 kernel: ahci 0000:00:1f.2: version 3.0 Oct 19 07:33:48 unRAID1 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]> Oct 19 07:33:48 unRAID1 kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode Oct 19 07:33:48 unRAID1 kernel: ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ems apst Oct 19 07:33:48 unRAID1 kernel: mpt3sas version 13.100.00.00 loaded Oct 19 07:33:48 unRAID1 kernel: IR NEC protocol handler initialized Oct 19 07:33:48 unRAID1 kernel: PTP clock support registered Oct 19 07:33:48 unRAID1 kernel: Linux agpgart interface v0.103 Oct 19 07:33:48 unRAID1 kernel: mpt3sas 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control Oct 19 07:33:48 unRAID1 kernel: cx23885 driver version 0.0.3 loaded Oct 19 07:33:48 unRAID1 kernel: DMAR: 32bit 0000:07:00.0 uses non-identity mapping Oct 19 07:33:48 unRAID1 kernel: CORE cx23885[0]: subsystem: 6981:8888, board: TurboSight TBS 6981 [card=33,autodetected] Oct 19 07:33:48 unRAID1 kernel: igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k . . . Oct 19 07:33:48 unRAID1 kernel: cx23885_dvb_register() allocating 1 frontend(s) Oct 19 07:33:48 unRAID1 kernel: cx23885[0]: cx23885 based dvb card Oct 19 07:33:48 unRAID1 kernel: tbs6981fe: module license 'TurboSight Proprietary: www.tbsdtv.com' taints kernel. Oct 19 07:33:48 unRAID1 kernel: Disabling lock debugging due to kernel taint Oct 19 07:33:48 unRAID1 kernel: TurboSight TBS 6981 Frontend 0 Attaching... . . . Oct 19 07:33:48 unRAID1 kernel: TurboSight TBS 6981 Frontend: Oct 19 07:33:48 unRAID1 kernel: tbs6981fe - software version is 1.95.2.21 Oct 19 07:33:48 unRAID1 kernel: TurboSight TBS 6981 Frontend: Oct 19 07:33:48 unRAID1 kernel: tbs6981fe - Successfully Initialized Oct 19 07:33:48 unRAID1 kernel: DVB: registering new adapter (cx23885[0]) Oct 19 07:33:48 unRAID1 kernel: DVB: registering adapter 0 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)... Oct 19 07:33:48 unRAID1 kernel: TurboSight TBS698x Dual DVB-S2 card port0 MAC=00:22:ab:f0:27:70 Oct 19 07:33:48 unRAID1 kernel: cx23885_dvb_register() allocating 1 frontend(s) Oct 19 07:33:48 unRAID1 kernel: cx23885[0]: cx23885 based dvb card Oct 19 07:33:48 unRAID1 kernel: TurboSight TBS 6981 Frontend 1 Attaching... Oct 19 07:33:48 unRAID1 kernel: DVB: registering new adapter (cx23885[0]) Oct 19 07:33:48 unRAID1 kernel: DVB: registering adapter 1 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)... Oct 19 07:33:48 unRAID1 kernel: TurboSight TBS698x Dual DVB-S2 card port1 MAC=00:22:ab:f0:27:71 Oct 19 07:33:48 unRAID1 kernel: cx23885_dev_checkrevision() Hardware revision = 0xa5 Oct 19 07:33:48 unRAID1 kernel: cx23885[0]/0: found at 0000:07:00.0, rev: 4, irq: 16, latency: 0, mmio: 0xf7200000 Oct 19 07:33:48 unRAID1 kernel: Registered IR keymap rc-tbs-nec Oct 19 07:33:48 unRAID1 kernel: input: cx23885 IR (TurboSight TBS 6981) as /devices/pci0000:00/0000:00:1c.4/0000:07:00.0/rc/rc0/input6 Oct 19 07:33:48 unRAID1 kernel: rc0: cx23885 IR (TurboSight TBS 6981) as /devices/pci0000:00/0000:00:1c.4/0000:07:00.0/rc/rc0 ...whereas all 6.4.0 opensource mentioned was this... Oct 19 07:26:22 unRAID1 kernel: Linux video capture interface: v2.00 Oct 19 07:26:22 unRAID1 kernel: WARNING: You are using an experimental version of the media stack. Oct 19 07:26:22 unRAID1 kernel: As the driver is backported to an older kernel, it doesn't offer Oct 19 07:26:22 unRAID1 kernel: enough quality for its usage in production. Oct 19 07:26:22 unRAID1 kernel: Use it with care. Oct 19 07:26:22 unRAID1 kernel: Latest git patches (needed if you report a bug to [email protected]): Oct 19 07:26:22 unRAID1 kernel: 2cacea5c44b45c46712837dd2afdbdde18447e0c Merge branch 'tbsdtv_linux_media/master' into tbsdtv_linux_media/latest Oct 19 07:26:22 unRAID1 kernel: fbcon: astdrmfb (fb0) is primary device Oct 19 07:26:22 unRAID1 kernel: igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k Oct 19 07:26:22 unRAID1 kernel: igb: Copyright (c) 2007-2014 Intel Corporation. Oct 19 07:26:22 unRAID1 kernel: Console: switching to colour frame buffer device 128x48 Oct 19 07:26:22 unRAID1 kernel: WARNING: You are using an experimental version of the media stack. Oct 19 07:26:22 unRAID1 kernel: As the driver is backported to an older kernel, it doesn't offer Oct 19 07:26:22 unRAID1 kernel: enough quality for its usage in production. Oct 19 07:26:22 unRAID1 kernel: Use it with care. Oct 19 07:26:22 unRAID1 kernel: Latest git patches (needed if you report a bug to [email protected]): Oct 19 07:26:22 unRAID1 kernel: 2cacea5c44b45c46712837dd2afdbdde18447e0c Merge branch 'tbsdtv_linux_media/master' into dvbdtv_linux_media/latest Oct 19 07:26:22 unRAID1 kernel: ast 0000:04:00.0: fb0: astdrmfb frame buffer device Oct 19 07:26:22 unRAID1 kernel: WARNING: You are using an experimental version of the media stack. Oct 19 07:26:22 unRAID1 kernel: As the driver is backported to an older kernel, it doesn't offer Oct 19 07:26:22 unRAID1 kernel: enough quality for its usage in production. Oct 19 07:26:22 unRAID1 kernel: Use it with care. Oct 19 07:26:22 unRAID1 kernel: Latest git patches (needed if you report a bug to [email protected]): Oct 19 07:26:22 unRAID1 kernel: 2cacea5c44b45c46712837dd2afdbdde18447e0c Merge branch 'tbsdtv_linux_media/master' into tbsdtv_linux_media/latest Oct 19 07:26:22 unRAID1 kernel: videobuf2_memops: Unknown symbol put_vaddr_frames (err 0) Oct 19 07:26:22 unRAID1 kernel: videobuf2_memops: Unknown symbol get_vaddr_frames (err 0) Oct 19 07:26:22 unRAID1 kernel: videobuf2_memops: Unknown symbol frame_vector_destroy (err 0) Oct 19 07:26:22 unRAID1 kernel: videobuf2_memops: Unknown symbol frame_vector_create (err 0) Oct 19 07:26:22 unRAID1 kernel: [drm] Initialized ast 0.1.0 20120228 for 0000:04:00.0 on minor 0 Are you saying I should putty in to my unraid box and do a modprobe cx23885 then? If so, into 6.3.5, 6.4.0 or both? (bear with me, I'll get there!)

Can confirm that 6.3.5 open source finds my TBS 6981 card, but 6.4.0-rc1 doesn't. Haven't tried rc2-8, but guessing it won't be promising. I'll leave you to it with fingers crossed. Thanks for your time.

OK, thanks for that

TBS tuners needs TBS build. TBS drivers aren't in mainline kernel that LibreELEC is based on. OK, fair enough. Do you want me to go back through the RCs to see if there's a point at which it's recognised? Do TBS not make an official driver for the current kernel (I hadn't used the OpenSource/CrazyCat versions up until now)?

Hi again - sorry to chime in, but I'm still learning about this set up. I've just tried using LibreElec 6.5.0-rc9f to see whether my TBS 6981 would show up, and it's showing two "Conexant CX24117/CX24132" adapters. As expected, these are showing up in TVHeadend and not enabled. Would it be possible/normal/advisable to rebuild my TVH config based on these inputs? Are they likely to work? Or should I be sticking to TBS builds?

I've tried the latest Crazy Cat and Open Source versions to try and get my TBS card recognised without luck (see attached). Reverted back to 6.3.5 official for now to get TVH back up. Not sure what to do now - was looking to get TVHProxy set up, but can't get card recognised on new versions - no longer supported?

Hi - If I revert back to 6.3.5 TBS Official DVB-S/T I get... Adapter drivers: Detected DVB Adapters 0 & 1: TurboSight TBS 6981 DVBS/S2 front end (apologies, I got my model name wrong, but it would appear that - for me - the Open Source & CrazyCat versions aren't picking up my card) Is there something I'm missing? All I've done is install the LT plugin for allowing pre-release updates and selected a new DVB build.

Good point - I'll get a screenshot shortly (I'm connected remotely via a mobile at the moment and it'll take a bit of stitching). However I have a TBS 6982 (from memory) with 2 DVB-S inputs, and they're not showing as detected on the DVB plugin page. I'm getting... unRAID Version: 6.4.0-rc9f DVB Version: TBS (Open Source) & LibreELEC ATSC-C, DVB-C, DVB-S(2) & DVB-T(2) Driver Version: 220917 Kernel: Detected Adapter Drivers and Adapters 0-7: Not Detected

Hi - I've just switched to 6.4.0 rc9, and re-run this plugin. I was running the TBS official before, but as that appears to be only for stable, I've switched to the open source version. Since then, TVHeadend doesn't start. I've tried removing and reinstalling, but I get the message... root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="tvheadend" --net="bridge" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "PGID"="100" -e "PUID"="99" -p 9981:9981/tcp -p 9982:9982/tcp -v "/mnt/cache/appdata/tvheadend":"/config":rw -v "/mnt/user/utilities/Incoming/Recordings/":"/recordings":rw --device=/dev/dvb linuxserver/tvheadend 38a90774afa7fc0fa164224f332cfd9d3eb900a2b8ce4a678165f3da0175dfd0 /usr/bin/docker: Error response from daemon: linux runtime spec devices: error gathering device information while adding custom device "/dev/dvb": lstat /dev/dvb: no such file or directory. The command failed. Any ideas? Is it because I've switched drivers? The extra parameters is still in the config.

Now I've got TVH running as I want it, I'm moving on to TVHProxy. Are you guys running the 6.4 version of Unraid to enable dockers on different IPs?

I've got Plex & TVHeadend installed (the latter needs reconfiguring after I cleared it out to start again, but it does work), and I'm looking to get TVHProxy up and running. Giving all different IPs isn't ideal, but it's not the end of the world. Do I have to add the two Container Ports manually, and I may be being stupid, but I don't have the option of a br0 network type. Any idea?

I know this is an old topic, but it's still relevant. I have a few questions though... In the original post you've stated that transcoding outside of the docker is no longer required. The link to the original instructions no longer works. I must have missed something somewhere, since my current setup has the host path of /transcode mapped to /mnt/cache/appdata/plexmediaserver/transcode/ (and in Plex Transcoder settings, the temporary directory is /transcode). Are you saying I don't need to do this any more? If not, what's the current advice? Also, I'm looking to move from linuxserver's version to the official Plex docker. I've moved before without fuss, but I just want to make sure I get it right... I'm not sure whether the option was there when I last updated, but when deleting the old docker, I have the selected option of "also remove image". I'm having a bit of a thick day today, so just to be clear, do I remove the image?

Does anybody know if switching to the Plex version is simple/reliable from linuxserver or limetech's version? I've done it between those two before pretty painlessly, but since the Plex support link is external it's harder to gauge. Also, is it stable/mature enough to run? I'm assuming with the support it's had, it will be.

Ahh, OK. Thanks I was guessing that for the next 48 hours we'll be getting some oddities until everything propagates and flushes.

Hi - I don't know whether it's a backlog caused by the migration, but I'm getting post notifications from about 23 hours ago. I'm currently set to receive emails whenever a reply is posted (I think), and I've been gradually getting them throughout the morning about a docker topic I'm following. Might this be something that's flushed out once everything catches up?

Same here Stupid question alert - could you put a graphics card in the server (given the right mobo ports) and leverage the power off that, or are we looking at system upgrades?

That's interesting. Forgive my ignorance - I'm finding my way, is this something that unRAID owners could make use of now, or would upgrades still likely be necessary? Appreciate it's very vague, but whilst the unRAID architecture allows for storage and media serving in one box, they might have quite different hardware demands.

I'm going through the same thing at the moment. I've got one of the new Nvidia TV Shields, but no 4K display yet (looking at upgrading the projector later in the year). However, everything else is still 1080p and Chromecast (or web browser, or external). I'm currently using the fastest processor for my motherboard, and it's unable to cope with some 4K demo clips I've got. I've put these into a separate "4K tests" library for now. The best stopgap I can see for now is to use Plex's "Optimise" function to create 1080p versions of all 4K clips. I was experimenting at the weekend, and Plex seems to automatically pick this pre-transcoded version. Presumably, when going into the TV Shield and 4K projector, it will automatically direct stream the full version. Until hardware comes out that satisfies both unRAID and Plex, this seems like an option.

Thank you - off to play with that now

Don't think it's currently possible, but it would be nice to be able to start and / or stop a docker on a schedule. For example, only have download type dockers run overnight, or media servers running on evenings/weekends. Likely not that simple to get a full featured scheduler in there, but might be nice.

Yep, same here

Doesn't seem to be updating for me... Signed in to duckdns, created a subdomain and got my token. Installed the docker and filled in SUBDOMAINS and TOKEN. Worked fine initially, but my IP address didn't update - I've ?ust done it manually at duckdns. Am I missing something?

Ahh, thank you. I misunderstood "destination" to mean they'll be copied to the backup destination (which they are by the end of it). Obviously not a problem - thanks for your time.

Apologies for a stupid question, but I'm late to the party and have only just discovered the backup plugin now it's on its own. It pointed me here for support, but at 92 pages I'm a bit overwhelmed! I've just set up and run my first backup, leaving everything pretty much as default, except for... - set appdata share to /mnt/user/appdata (should it be cache/appdata? I have a cache only share) - set disk # to disk2 - set destination share to appdata-backup/ (a share I created for this) - set it to a weekly backup to run on Monday I triggered a manual backup, and all has run fine, but in addition to the two "Community_Applications_USB_Backup" and "Community_Applications_VM_XML_Backup" folders in my appdata-backup share, they're also now in appdata. Should they be here? Obviously not a huge issue, but I thought I'd ask - I'd love to save your time and read through this thread, but at 92 pages it's not looking likely...! Any advice greatly appreciated

Hi - I'm running v6.2.1, and I was going to run the New Permissions utility across my cache drive. I do this when I've uploaded files to my server using the proFTPd plugin to reset the user ownership (as they're added as a different user and I can't do anything to the files). I'm using IE11 (don't laugh, it's a Windows Home Server that I'm RDC'd into!), and if I view the browser's console I get "start is undefined" when clicking the "I'm sure I want to do this" checkbox. In the interim, can I perform the same action using via Putty? EDIT: for now in the command line I've changed to the directories in question and run "newperms ."