flyize

I'll post the results, just in case. But I don't think they will help. I had to move back to GPU transcoding due to Unraid instabilities with my Alder Lake CPU. I'll circle back whenever RC3 comes out. root@Truffle:~# timeout -k .500 .400 intel_gpu_top -J -s 250 { "period": { "duration": 0.004918, "unit": "ms" }, "frequency": { "requested": 0.000000, "actual": 0.000000, "unit": "MHz" }, "interrupts": { "count": 0.000000, "unit": "irq/s" }, "rc6": { "value": 100.000000, "unit": "%" }, "power": { "GPU": 0.000000, "Package": 0.000000, "unit": "W" }, "engines": { "Render/3D/0": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "Blitter/0": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "Video/0": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "Video/1": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "VideoEnhance/0": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" } } }, { "period": { "duration": 250.182461, "unit": "ms" }, "frequency": { "requested": 0.000000, "actual": 0.000000, "unit": "MHz" }, "interrupts": { "count": 0.000000, "unit": "irq/s" }, "rc6": { "value": 100.000000, "unit": "%" }, "power": { "GPU": 0.000000, "Package": 27.051546, "unit": "W" }, "engines": { "Render/3D/0": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "Blitter/0": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "Video/0": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "Video/1": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "VideoEnhance/0": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" } } }

I can't add the epg via plex. Plex makes you chose one or the other, and I have to use xml for my IPTV. I wish they would fix that. So I do now have it setup where the hdhr is direct to plex, but I'm using the xml from xteve. And then my iptv is using VLC. So it may be a bit messy, but it works!

Is the hdhr generating its own xml? Where is that?

With pulseaudio they both work in VLC. But what I think you're saying is that I can still get xteve to generate the hdhr xml, use the hdhr directly in Plex, and then point it to the xteve XML for guide data?

Good call on not getting an Alder Lake. I'm still sitting here GPU transcoding until Unraid updates the Linux kernel so I can use the iGPU.

You've nailed it. That does seem to fix it. However, you're correct in that I could just use the HDHR directly in Plex and then use xteve for the IPTV. Not sure why I didn't think of that. edit: Oh wait, I need xteve/guide2go for the xml guide for the hdhr. So I do need both in xteve.

So I got it all working, sorta. Thanks for your help. I'm having an odd problem, and I'm wondering if it could be because something is missing from the container. No matter which buffer setting I use, either my IPTV or my HDHomeRun doesn't work. It goes like this: None: HDHomeRun works. IPTV does not (obviously no errors in log) xTeVe: HDHomeRun works. IPTV error: 2022-01-31 16:33:13 [xTeVe] [ERROR] Streaming error (Server sends an incompatible content-type) - EC: 4003 FFMPEG: HDHomeRun works. IPTV error: 2022-01-31 16:35:04 [xTeVe] [ERROR] FFMPEG error (Streaming was stopped by third party transcoder (FFmpeg / VLC)) - EC: 1204 VLC: IPTV works. HDHomeRun error: 2022-01-31 16:36:01 [xTeVe] VLC log: [0000154f983afa30] vlcpulse audio output error: PulseAudio server connection failure: Connection refused I filed a bug report over at xTeVe, but after thinking about it, I wanted to make sure that something wasn't missing from the container.

Anyone else using sstvproxy successfully?

I added some echos and the errors are when it tries to update xteve. Apologies, are you aware of a good walkthrough on how to set this all up? I appreciate the help, but am probably really missing some basic stuff here.

It appears to be getting data though. The .xml is 32MB.

Got it! As expected, this was user error. However, I still get a bit of an error at the end of running the cronjob. 2022/01/31 10:46:55 [G2G ] Deleted Program Informations: 0 Locked [423] Locked [423] <html><head><title>Unauthorized</title></head><body><h1>401 Unauthorized</h1></body></html>/ edit: And another question. When I attempt to setup xTeve its asking for an .m3u. Where does that come from?

Same error. I'm guessing it doesn't matter, but I'm actually running the command from inside the container. / # guide2go -configure /guide2go/tampa.yaml 2022/01/31 10:35:33 [G2G ] Version: 1.1.3 2022/01/31 10:35:33 [ERROR] open /guide2go/tampa.yaml: no such file or directory Also, is there a better container to use. I saw the one with Owl doesn't have the Beta tag.

You're correct. I totally have. Let me back up. Based on the instructions listed with the container, if I go into the console and type 'guide2go -configure /guide2go/tampa.json' I get an error. 2022/01/31 10:24:55 [ERROR] open /guide2go/tampa.yaml: no such file or directory Do I need to just create that folder?

So I'm trying to setup xteve_guide2go. I've created a config with 'guide2go -configure'. I then added a lineup and created the XMLTV file. I've got two issues: * My Plex container doesn't see anything * When I attempt to run './config/cronjob.sh' I get the following errors: sed: /guide2go/CBLguide.yaml: No such file or directory sed: /guide2go/CBLguide.yaml: No such file or directory 2022/01/31 10:11:03 [G2G ] Version: 1.1.3 2022/01/31 10:11:03 [ERROR] open /guide2go/CBLguide.yaml: no such file or directory sed: /guide2go/SATguide.yaml: No such file or directory sed: /guide2go/SATguide.yaml: No such file or directory 2022/01/31 10:11:03 [G2G ] Version: 1.1.3 2022/01/31 10:11:03 [ERROR] open /guide2go/SATguide.yaml: no such file or directory sed: /guide2go/SATSport.yaml: No such file or directory sed: /guide2go/SATSport.yaml: No such file or directory 2022/01/31 10:11:03 [G2G ] Version: 1.1.3 2022/01/31 10:11:03 [ERROR] open /guide2go/SATSport.yaml: no such file or directory curl: (7) Failed to connect to 192.168.1.2 port 34400 after 3048 ms: Host is unreachable curl: (7) Failed to connect to 192.168.1.2 port 34400 after 2069 ms: Host is unreachable

Apologies. I figured the answer would just be, yes. Attached truffle-diagnostics-20220125-1603.zip

Hopefully an easy one. Any ideas why my IMC Bus Utilization shows blank? Is that something that requires a discrete GPU?

Anyone even got a guess as to what this could be? I've recently upgrading the server hardware and am running 6.10.-rc2. Server works perfectly, as long as I don't turn on hardware transcoding in Plex. Also, I can't imagine that it matters, but I'm using binhex-plex.

The sstvproxy docker doesn't seem to work at all. When I hit port 8098 I get an 'internal server error'.

So transcoding seems to be 'soft' crashing my server. It responds to pings but nothing else. syslog shows this: Jan 16 16:39:12 Truffle kernel: i2c /dev entries driver Jan 16 17:10:06 Truffle kernel: i915 0000:00:02.0: [drm] Resetting vcs0 for preemption time out Jan 16 17:10:06 Truffle kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:4:28fffffd, in Plex Transcoder [8854] Any ideas?

I just got it all built yesterday. Last night and again this morning, the UI, all docker containers, and all VMs were unavailable. The server still responds to pings and the UI gives an NGINX error. Any ideas? Running 6.10-rc3 truffle-diagnostics-20220116-1136.zip

Got it. Thanks! I will inevitably forget about making these changes. Will this effect anything in the future?

Any chance you found a solution for this? FWIW, I'm running 6.10-rc2, but still the same issue. [ 23.505832] i915 0000:00:02.0: Your graphics device 4680 is not properly supported by the driver in this kernel version. To force driver probe anyway, use i915.force_probe=4680 module parameter or CONFIG_DRM_I915_FORCE_PROBE=4680 configuration option, or (recommended) check for kernel updates.

Oh, okay. That's great news. Thanks!

I attached a USB NIC and was able to get it loaded. truffle-diagnostics-20220114-1652.zip

I recently picked up a new CPU and mobo for my Unraid server. I booted it up and can't connect. I see can't find eth0 in the logs. Is this motherboard actually not supported? https://www.msi.com/Motherboard/PRO-Z690-A-DDR4