meep

OK, thanks. Pity Extra GPU it is!

So, I'm halfway there.... I set up my GX570 as primary boot GPU in bios and set UnRaid to UI boot mode I added the GPU bios rom to my VM config Now, when I boot the system, UnRaid UI comes up on the main display. When I run the VM, it 'takes over' the main display and runs fine. However, when I shutdown the VM, the unraid UI fails to come back up. Screen remains blank. Any hints?

Hi All I know this is possible, my GoogleFu has not been strong enough for me to find the solution applicable to me. Right now, I have a cheap & cheerful PCIe card in my server that UnRaid boots to. I have an AMD RX570 that I pass through to VMs. I have a display, keyboard and mouse connected for UnRaid control, and another display, keyboard and moue connected for VMs (keyboard/mouse are connected to a passe through USB card) I would like to ditch the cheap GPU (to gain a PCIe slot) and make the RX570 my default card for unRaid boot, but will be used for unraid. Essentially, I need one display, keyboard and mouse that will control unraid (when booted in standard or UI mode) As soon as a VM is launched, it will use the single screen and inputs. Shutting down the VM returns me to the UnRaid display As I understand it, I might need to include a ROM file in the VM config for this to work. Is this the case? Are there specific instructions for setting this up with AMD cards? General guides for this single screen/gpu config for VMs? Thanks!

I'm with this. My Settings and Plugin pages are now a mess of indistinguishable monochrome blandness. At least provide an either/or option.

Just updated now that the DVB Edition is available. Looks good. Couldn't resist. making up the attached...

Perfect. Changed to Read/Write and the error went away. I ended up setting timeshift to use RAM inside the Docker UI in this case as TVHeadEnd supports that but this is a handy trick to know.

I tried doing this on a tvheadend docker to write timeshift files to memory (/tmp/timeshift/) but the docker failed to start, showing this error; any ideas?

Just had a PM from @s.Oliver on this. Wasn't aware they were in kernel so will try to have a play in the coming days if I find the time. Will report back when I know more.

One thing on Emby, there's no plugin to click on. It integrates seamlessly with the Kodi libraries so, access movies, there they are. Click on music, voila! Is v18 close to release? Interested to see if the leanback works with this as well. Will try it on one of my clients and report back.

Hi @DZMM I think we might be twins or something. We share a lot of common thinking in any case! Really nice write up.. If you haven't done so already, I can only second the recommendation to use Emby as a back-end for Kodi. Seamless. Set it and forget it. Kodi+Emby = everything Plex has plus so much more.

I don't doubt it's user related for one minute!! I've tried to use Bouquets but they don't seem to be working. My real problem is that my openVPN has stopped working for some unknown reason. This means I can't troubleshoot during work! I need to get that fixed first.

I'll do that when I have the time and inclination to replicate the issue. Right now, my unRAID/ TVHeadEnd setup is refusing to map DVB-S services to channels and failing to record from DVB-T channels so a big mess that I'm trying to work on.

Here's the bug report for future reference; https://tvheadend.org/issues/4273

Probably something I messed up, in all likelihood!

Can't get at that now as, of course, my openVPN is also acting up following recent events. I'll check this evening and report back. Many many thanks to you and @CHBMB for your patience in holding my hand through this.

That makes complete sense. Thanks for the clarity and helping me understand!

And that's key to my question here.... I installed the 4.0.9 Stable version of this Docker. On my Docker page, an available update was show. I upgraded. Now my TVH reports v4.1.2449 Is this expected behaviour? Furthermore, this 4.0.9->4.1.2449 install it works for me whereas installing what I would understand to be the same version directly does not? That's the confusing bit.

Mostly jesting there, but... It is all working now but if future docker or TVH updates are going possibly break break things, of something changes in unRaid etc. or I neede to keep on top of the TVH people to address new issues, it's justall getting a bit unstable. Of course, I should just pick a working susyem and stick with it but I'm my own worst enemy when it comes to upgraditis!

Thanks. That was really my question - I don't want to uninstall my Stable (working) docker, install the 'latest', find the version, uninstall it and reinstall stable. Of course, I'd likely have all that done by now if I'd just started it instead of asking the question here.

Think I'll just go back to $ky.....

That doesn't make sense? I had originally installed 'Latest' docker version which didn't work and for which I didn't take a version number. I then deleted the docker and support folder and installed 4.0.9/Stable which worked. Afterwards, there was an update which I applied and I confirmed all tuners were still working. I checked the TVH version at that point and it's as screengrabbed in my post above (same as the version you noted just now). I would have expected the 'latest' nonworking version to be newer?

Do we know the version of the development build in the docker currently? I don't want to go through the uninstall/reinstall tango but do want to report it correctly to the nice TvHeadEnd people. Thanks

Yes

So I removed TVH Docker Default/Latest and installed Stable/4.0.9 and voila: I've posted back in the TVH thread as well as it looks like it might not be driver issue after all?

So it turns out it may be TVHeadEnd after all. I reverted to the 4.09 Stable Docker (I had initially installed Default/Latest in which I had the described problem). Immediately, the tuners all showed up as I would expect: I ran the Docker update and now I'm on tvheadend 4.1.x. Don't quite understand how that happened but the tuners are still correctly displayed. This is on the latest unRAID DVB 6.3.2 (stock DD drivers); So I guess the question is, why would the Default/Latest TVH Docker have the problem and the older version dos not?