-
Posts
432 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by flyize
-
-
57 minutes ago, ich777 said:
I would wait a little longer, proper iGPU support for Alder Lake is maybe introduced in 6.11 RC series...
The issue with Linux and bleeding edge hardware is always that it works properly because Intel is always a bit behind submitting patches to the Kernel...
Gotcha. Is it safe to assume that 6.11 RCx is probably months away?
- 1
-
-
14 hours ago, Wintersdark said:
It runs fine, but does not allow Plex to use the igpu without crashing. Without hardware transcoding in Plex I've had no issues whatsoever.
According to the Plex devs, that's going to require kernel support coming in 5.17/5.18
According to this, its 5.18 I kinda almost regret picking up an Alder Lake at this point. 😅
https://forums.plex.tv/t/plex-media-server-on-ubuntu-21-10-with-intel-12th-gen-alder-lake/768123/30
- 3
-
Mine still crashed.
-
Then I'd like to update the wiki to something like:
For best performance, make sure there are no reads/writes happening to the array. The easiest way to do this is to bring the array up in maintenance mode.
Does that make sense? Had *I* known that, I'd have already had the old drive removed and the new drive replaced days ago.
-
5 minutes ago, JorgeB said:
That only makes sense if you were still using the array before.
The array was online and mounted (except the drive I was zeroing out). There isn't any mention that the array shouldn't be mounted in the wiki. Should there be?
-
Yeah, I started to attempt your suggestion which is why the array was stopped. The drive I'm removing isn't SMR. However, with the array in maintenance mode, I'm getting 182MB/s. That will do. Thanks!
-
I had that specific drive unmounted (that's what the advanced section of the wiki says to do). Just in case, here are diagnostics.
-
I have reconstruct write enabled, and am doing it manually. However, the array isn't in maintenance mode. Could that be the actual issue?
-
Following the writeup here: https://wiki.unraid.net/Shrink_array
Using dd to zero out the drive and its writing at about 1.1MB/s. At that rate, it seems the process will complete sometime around the fall of humanity. Am I doing something wrong?
-
2 hours ago, Cajones said:
So I had my first crash this morning, just short of 48 hour uptime. I was playing around with the 4k transcoding and HDR: the 4k transcode was not working at all (not sure if it was file or server, i suspect server). The HDR content is what I believe led to crash. Something I noticed before the server locked up was that my iGPU was pegged at ~7 Watts but not actually "doing" anything and wouldn't stop drawing until the server locked up.
It for sure doesn't work with tone mapping enabled (thats apparently an ICR issue). But either way, you can expect more lockups.
- 1
- 1
-
1 hour ago, Hurde said:
No idea if this is related to the same issue on Unraid:
The root cause of the failures for all versions above 20.04/ ICR 21.49 has been identified.
https://forums.plex.tv/t/plex-media-server-on-ubuntu-21-10-with-intel-12th-gen-alder-lake/768123/12
Nice find. I'm glad they found the issue, but that does NOT sound like a fix will happen soon. #FML
-
I wish you the best of luck @Cajones, but I don't think it will be stable.
- 1
-
46 minutes ago, NightOps said:
I understand completely. I'm a bit in the same boat. If we take just a slight bit larger view on things, the Linux kernel has fully supported the 11th and 12th gen Intel CPUs and iGPUs for a bit now, so the availability is there. I have faith that Lime Tech will get unRAID updated with the latest necessary kernel within a respectable time. I went 12th gen because of the opportunity for less power draw and the power of the iGPU. It's just a matter of time until we see the payout.
Except from what I'm reading, there seems to be a good chance that 5.16 alone will not fix the issue.
-
25 minutes ago, JonathanM said:
There is a good reason it's referred to as "cutting (bleeding) edge technology"
Serial 1st adopters have to be a special breed of person.
I suppose so. Honestly, when I bought it I had no idea how much trouble I'd have with it. I've probably built 20+ computers at this point and never had an OS support issue with a processor. New territory for me...
- 2
-
34 minutes ago, NightOps said:
Not sure about @flyize but for me HDR tone sample with HDR content caused it to bomb rapidly. Having hardware acceleration enabled in Plex would result in lockups after 9ish days.
Mine is measured in hours. Not sure if it makes a difference, but my Plex server is pretty heavily used.
- 1
-
35 minutes ago, Stringer said:
Is it generally unstable or only with HDR tone mapping enabled in Plex? I read somewhere in the thread that this is a problem, but I'm not sure if disabling it solves everything.
Generally unstable, even with tone mapping off.
-
20 hours ago, crankyCowboy said:
@flyize Many in this thread have reported success using QS in these 12th gen Alder Lakes with varying levels of success. It seems to be hit or miss with some people saying they aren't experiencing any problems whatsoever, where others are stating they are having hangs, freezes, and all kinds of problems. I'll probably disable until it's officially supported, but I have been able to get QS to work with initial tests.
It works. Until it crashes (in my case, no more than 24 hours). I've been monitoring this intently and don't think I've seen it work long term for anyone. I'd love to be wrong though!
-
8 hours ago, Brandon_K said:
Can you (or anyone else) give a condensed / step by step version on what needs done to get QS working under Unraid / Plex? I would be much greatful!I see you quoted a post from someone with an Alder Lake CPU. If you have one of those, QS just isn't going to work with Plex yet, no matter what you do.,
- 1
-
5 hours ago, ich777 said:
The developers from intel_gpu_tools reached today out to me that an update is in the works, I think intel_gpu_top is not quiet ready for Alder Lake yet, like the i915 module for Linux...
It takes a little bit until everything is working correctly on Linux with new hardware most of the times.
Yeah. Coming from an old Xeon, I was hoping to future proof myself, but I somewhat regret the Alder Lake purchase.
-
I keep seeing these repeated a couple times a day.
Feb 7 02:53:43 Truffle nginx: 2022/02/07 02:53:43 [error] 11093#11093: *1932704 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /stub_status HTTP/1.1", host: "localhost" Feb 7 02:53:44 Truffle nginx: 2022/02/07 02:53:44 [error] 11093#11093: *1932706 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /server-status?auto HTTP/1.1", host: "localhost" Feb 7 02:54:04 Truffle nginx: 2022/02/07 02:54:04 [error] 11093#11093: *1932884 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /server-status?auto HTTP/1.1", host: "localhost" Feb 7 02:54:05 Truffle nginx: 2022/02/07 02:54:05 [error] 11093#11093: *1932891 open() "/usr/local/emhttp/us" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /us HTTP/1.1", host: "localhost" Feb 7 02:54:05 Truffle nginx: 2022/02/07 02:54:05 [error] 11093#11093: *1932897 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /server-status?format=plain HTTP/1.1", host: "localhost" Feb 7 02:54:05 Truffle nginx: 2022/02/07 02:54:05 [error] 11093#11093: *1932905 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /status?full&json HTTP/1.1", host: "localhost" Feb 7 02:54:05 Truffle nginx: 2022/02/07 02:54:05 [error] 11093#11093: *1932915 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /server-status?auto HTTP/1.1", host: "localhost" Feb 7 02:54:05 Truffle nginx: 2022/02/07 02:54:05 [error] 11093#11093: *1932928 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 127.0.0.1, server: localhost, request: "GET /admin/api.php?version HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "localhost" Feb 7 02:54:14 Truffle nginx: 2022/02/07 02:54:14 [error] 11093#11093: *1933000 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /stub_status HTTP/1.1", host: "localhost" Feb 7 02:54:14 Truffle nginx: 2022/02/07 02:54:14 [error] 11093#11093: *1933007 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /status HTTP/1.1", host: "localhost" Feb 7 02:54:14 Truffle nginx: 2022/02/07 02:54:14 [error] 11093#11093: *1933014 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /status?full&json HTTP/1.1", host: "localhost"
-
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!
- 1
-
1 minute ago, alturismo said:
not really, i think plex finally made it possible to add more then 1 xml source.
so my approach would be
- add the hdhr including its epg (which should be coming automatically)
- add the xteve dvr with its xml for those channels
Is the hdhr generating its own xml? Where is that?
Intel 12th generation Alder Lake / Hybrid CPU
in Motherboards and CPUs
Posted
I had a friend try a couple of months ago, but was not able to do so. IIRC, the UI would never load.