NightOps

Awesome, thank you for the write-up. Not sure I fully understand the patch number bit... the notes from the latest kernel from @thro2002ro say: 13 for unraid 6.8.3, 17 for unraid 6.9.2, 18 for unraid 6.10rc1, 19 for unraid 6.10rc2, 21 for unraid 6.10rc3, 22 for unraid 6.10rc4/6.10rc5, etc... What about for rc6, 7, 8? I don't want to assume they're going to incrementally increase for each RC, as both RC 4 and 5 use the same patch number. Thanks for your help!!!

tbh, if the system suffers from hard locks, then can we really say "it works"? 🙂 Honestly, it's just a matter of time. the 12th gen evidently wasn't the first to suffer from such setbacks, and I can imagine it won't be the last.

Lack of E-cores and different iGPU... though personally I'd be surprised if it came down to the E-cores, and would actually be potentially much more problematic.

Maybe there’s better drivers for the UHD 730, but I ran the exact same steps for my 12600k, got it running and verified HW transcoding worked, and would have a crash somewhere between 7 and 9 days. The overwhelming majority of plays through Plex are Direct for me - so seldom do I have a transcode going on. If I forced one over cellular, it would crash immediately. At this time the 12600k is beefy enough for me that I have been fine without iGPU supported/configured, but I would love to have it working. I’ve tried on rc2 through rc5, just gave up.

Using this same method of enabling QS, I was able to run about 9 days before I would have a complete system lockup.. Hopefully you get better results. I am using the Z690-P D4 and the i5-12600k. As soon as I took the iGPU out of Plex and Handbrake, then suddenly I had 0 issues... and I've been running for about 90 days with no lockups.

Just curious, what is your uptime?

For me it was just a matter of it running

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.

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.

--device=/dev/dri is simply adding a "device" to your Plex docker, and the path to that device is /dev/dri. Easiest way to look at it is "/dev" are devices within the machine. "/dri" is one such device within Linux for Direct Rendering Infrastructure - basically the general purpose pathway for Linux to be able to use a rendering device. So by specifying "--device=/dev/dri" you are effectively adding a display rendering device to your docker for whatever purposes it can access via the Direct Rendering Manager API. That's about the extent of what I understand in all this.

I've gotten Plex to do some hardware transcoding - for a time. However within 2 weeks I'll have lockups and be forced to hard shut down and restart... resulting in the inevitable parity sync. Same situation with using QS for Handbrake. However once I shut down Plex and Handbrake from using the iGPU, I've had 0 problems... 56 days no parity sync, and the only downtime was planned so that I could update to RC4.

I have not, I’m running Plex and Handbrake in docker. I’ve isolated 2 E cores to unRAID, and pretty much left the rest wide open. I don’t have many non direct play users, so I figured I would just sit tight until a release came out using the 5.16.x kernel that fully supports the iGPU on the 12600k

Running RC4 on the Asus Prime Z690-p D4, seems same as RC3. Still haven’t tried iGPU passthrough for Plex or Handbrake, but everything seems stable so far.

Good question - but I believe the internal version of RC3 he was using was running kernel 15.16.x

Full support will be in 15.16. If you are just looking for increased security and support for the thread scheduler, then rc3 is good - but if you are talking about iGPU support for QSV/transcoding, and for additional 2.5GbE support, it’s not there yet.

You absolutely can. The E-cores have more than enough to handle unRAID with plenty of performance.

I've got my last 2 E-cores isolated for unRAID, and haven't had a single issue. I can't say I've noticed any appreciable performance issues. Running for well over a month now with no lockups/etc. Now if only the updated Kernel would fall into our laps for iGPU passthrough!

Very stable, as long as you don’t try to use the iGPU for encoding/transcoding. I’ve been running it for 35 days straight with no issues.

It depends on what you mean by "work". unRAID works fine using 11th/12th gen, but if you are wanting to use hardware transcoding for plex, QSV for handbrake, and pass-through graphics for VMs, then the next version of unRAID with kernel 5.16+ should be solid - but obviously I have no way to confirm that. I've been running 11 days straight using software encoding/transcoding on an i5-12600k and up to 5 remote streams on Plex without any issues...but it's using way more CPU that I'd like... and if a file hits handbrake it either slows things way down (no CPU pinning), or the encode takes a while (6 CPUs pinned for handbrake, 1 for OS)

I was able to run hardware transcoding from HVEC/x265 containers @4k down to 1080p on a 20Mbps line through Plex, but I have yet to truly be stable. Handbrake encoding using QSV has not faired so well…. I’m guessing it’s going to take some BIOS maturation and kernel 15.16 before we see Alder Lake truly shine in unRAID for these purposes… but I’m a n00b at unRAID, so that’s just my $0.02

No idea, I just stepped into the world of unRAID with 6.10-rc2 … needed to replace an aging Windows box that had been fulfilling media/file storage roles for a decade. So glad I did, and that I stuck through with unRAID even after my initial hiccups.

I switched to software and the file encoded correctly, no issues. No server lockups... looking good! I suspect this is an issue with the current driver in Kernel rc2? Hopefully rc3 will fix it?

k, I'll switch my preset to use software h.265. My CPU is the i5-12600k

Just tried running the conversion. Here are the settings I'm using (handbrake_settings.png). Also attaching diagnostics and conversion.log legion-diagnostics-20220126-1244.zip conversion.log

Yes. I've since done a lot of work on the server and cleared up some issues that I didn't realize I had. I'll try it all again using the same preset and see what happens.