New i5 NUC Linux server, can't transcode

Server Version#: 1.32.8.7639
Player Version#: 4.123.2

I just got a new NUC (Geekom Mini IT13) to run Plex on instead of my old Synology NAS. It’s running a i5-13500H processor, with Intel Xe GPU on Ubuntu 22.04. The reason I did this was because I was experiencing playback issues with mkv files where I have to convert them all to mp4 because my NAS wasn’t transcoding. So I hoped this would resolve that issue. Unfortunately, it’s not been resolved yet. I tried playing an mkv last night on an Apple TV, LG TV, and a FireTV stick, and it just spins until it times out on every one of them. I have set the new server to hardware transcoding, HDR mapping, etc, but it still doesn’t work. This morning I went in and optimized the file in question. That was 2 hours ago and it is still at 0% converted.

Any idea what I could be missing? Thanks for the help!

Please do the following:

  1. Confirm SERVER debug logging is enabled.
  2. Restart PMS
  3. Wait 2 minutes (need to see the startup sequence before playback starts)
  4. Start playback
  5. Let play 30 seconds
  6. Stop
  7. Download logs zip
  8. attach here

NOTE: Reading the hardware spec

Do you have dual channel memory enabled – two matching DIMMs?

If only one DIMM, Xe graphics will be disabled by the CPU

Intel® Iris® Xe Graphics only: to use the Intel® Iris® Xe brand, the system must be populated with 128-bit (dual channel) memory. Otherwise, use the Intel® UHD brand.

I went through this process, but after I restarted PMS the file now plays everywhere… So I’m not sure if it’s an issue or just needed a restart.

hey if you would, please provide the info anyway. It’s a great opportunity for us to learn- whether it’s the cpu, linux or your files or what’s causing the issue.

Theoretically you should have zero issues as far as playability with the NUC. It’s new gen, quick sync, and excellent overall processing and single thread speed. Should be butter, Im curious to know the cause of the issue (mostly bc Im flirting with the idea of building a linux box).

Sure, no problem. I’ll go through these steps and post the log here late today when I get home. I assumed it would all work without issue as well. Hopefully this has been resolved now. I have tried optimizing a couple files today and they all worked and optimized 5-6GB files in about 4 minutes.

if he no longer has an issue than posting logs of a properly functioning machine isn’t going to tell you why it wasn’t working prior to reboot right?

I got the same NUC 14 days ago. I’m running Ubuntu Server 22.04 and at the beginning I also had the problem that HW transcoding didn’t work. The problem was the kernel. An update to version 6.5 was the solution for me.

You’re right, wouldn’t show anything. No need to post the log since it’s working now.

Thank you! I’ll update it this weekend!

@ChuckPa see this comment. noting since i know you maintain the package for linux systems.

Folks,
Just getting back into the office today. was out sick all week.

Is this a 22.04 / mismatched kernel problem or ???

I can not say exactly. In any case, with kernel 5… no HW transcoding worked for me. Everything works fine with HWE Kernel 6.5.

I’ve removed Windows and installed Ubuntu 22.04. Is it possible to upgrade the kernel without Windows installed? Is it the Chipset download that I need to use? Thanks!

When you installed 22.04, your second option on the installation image was HWE (hardware enablement)

You can check this by typing uname -a and see if you have the hwe kernel 6.x

If you don’t,

sudo apt install --install-recommends linux-generic-hwe-22.04 

will install the HWE stack and bring you up to the current 6.x kernel.

Uh the logs prior to the reboot obviously might give you the best insight if it was in fact working after. That’s why they keep PMS logs 1-5 with 1 being the most recent. Since he had the issue and went through the trouble of posting, I’m guessing he went to troubleshooting page in PMS and exported log data as recommended. Even if he didn’t it’s still there.

Even if a reboot was all it took to straighten itself out, I was interested to know what his experience now that it was working. From what it reads, he was really hoping for help, then rebooted during the thread, it worked and declared it fixed without a ton of time in between, w/o much testing (can’t be sure) and it seemed like more than a reboot but hopefully not.

I was just hoping to learn something as I was thinking of putting ubuntu on a mini machine like a NUC (or similar) that comes with a current (or close) gen intel. Also the Geekoms on paper seem to check the right boxes- one of very few mini machines with 13 gen chips (the beefier ones) and footprint, but the price point was so inexpensive it surprised me. To the ‘too good to be true’ point and did some reading nut always best to hear first hand.

Edit/Update- Never-mind he just reposted today (new thread) and the problems have returned, plus a coupe more which seem more user focused. New i5 NUC issues: remote access, limited connection, transcoding

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.