<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 12 Jan 2022, at 9:27 pm, Justin Moore <<a href="mailto:justin.nonwork@gmail.com" class="">justin.nonwork@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I just went through the process of setting up MythTV on a NUC 11 PAHi5 running Ubuntu 20.04 LTS, and wanted to share some of the pain points I ran into in case anyone else is trying to do the same.<div class=""><br class=""></div><div class=""><a href="https://ark.intel.com/content/www/us/en/ark/products/205040/intel-nuc-11-performance-kit-nuc11pahi5.html" class="">https://ark.intel.com/content/www/us/en/ark/products/205040/intel-nuc-11-performance-kit-nuc11pahi5.html</a><br class=""><div class=""><br class=""></div><div class="">1. Getting IR to work</div><div class="">There's a BIOS setting to enable/disable the IR receiver. If this is unchecked -- mine was my default -- you won't see your receiver, and ir-keytable will tell you there's no IR receiver available. Make sure to enable it in the BIOS.</div><div class=""><br class=""></div><div class="">If you're using inputlirc make sure to use a udev rule to create a uniquely named symlink. E.g., in /etc/udev/rules.d/10-persistent-ir.rules have:</div><div class="">KERNEL=="event*",ATTRS{name}=="ITE8708 CIR transceiver",SYMLINK="input/irremote"<br class=""></div><div class="">And retrigger the udev processing. Otherwise if you have a keyboard attached and you try and use it, you'll get double key presses.</div><div class=""><br class=""></div><div class="">2. Getting sound to work</div><div class="">I couldn't get it working out of the gate. Apparently it is (was) a common issue:</div><div class=""><a href="https://community.intel.com/t5/Intel-NUCs/NUC-11-Performance-No-audio-on-any-Ubuntu-based-OS/m-p/1277346" class="">https://community.intel.com/t5/Intel-NUCs/NUC-11-Performance-No-audio-on-any-Ubuntu-based-OS/m-p/1277346</a><br class=""></div><div class="">I installed the linux-image-oem-20.04d package (kernel 5.14.0-1018-oem) and booted into it. That fixed the sound issue.</div><div class=""><br class=""></div><div class="">3. Getting video to work on a 4k display</div><div class=""><a href="https://askubuntu.com/questions/1364236/4k-graphics-problems-with-intel-nuc11-with-ubuntu-20-04-lts" class="">https://askubuntu.com/questions/1364236/4k-graphics-problems-with-intel-nuc11-with-ubuntu-20-04-lts</a></div><div class="">My NUC runs through a Denon receiver and into a 4k TV. All the hardware and cables should support 4k@60fps, but my screen was going blank every time I tried to go above 1920x1080@60fps. It turns out that by default Ubuntu will use the maximum possible color depth, which in my case was 12. 4k@60fps @ 12 bits is above the maximum data rate for HDMI 2.0:</div><div class=""><a href="https://wiki.ubuntu.com/DeepColourDepthSupportPlan" class="">https://wiki.ubuntu.com/DeepColourDepthSupportPlan</a><br class=""></div><div class=""><a href="https://en.wikipedia.org/wiki/HDMI#Refresh_frequency_limits_for_standard_video" class="">https://en.wikipedia.org/wiki/HDMI#Refresh_frequency_limits_for_standard_video</a> (uses 8 bits, so multiply by 1.5 to get 12 bit data rate)<br class=""></div><div class="">Once I set the bit depth to 8, it started working again:</div><div class=""><a href="https://www.soi.pw/posts/10-bit-color-on-ubuntu-20.04-with-amdgpu-driver/" class="">https://www.soi.pw/posts/10-bit-color-on-ubuntu-20.04-with-amdgpu-driver/</a><br class=""></div></div><div class=""><br class=""></div><div class="">4. [unsolved] Getting 1920x1080@24 fps video to not tear</div><div class="">I have a bunch of movies in my video directory, and for the life of me I couldn't get them to play without tearing when I was driving my video display at 4k. I tried the "TearFree" option but it looked like this, and playback kept blacking out:</div><div class=""><a href="https://i.stack.imgur.com/gDOkX.jpg" class="">https://i.stack.imgur.com/gDOkX.jpg</a><br class=""></div><div class="">I also tried various combinations of DRI3, triple buffering, and Wayland, but none of those seemed to work.</div><div class=""><br class=""></div><div class="">Ultimately I set my desktop and display to 1920x1080@120Hz@8bits and that seems to have solved the tearing problem. I don't have a bunch of 4k content but I was hoping to have this NUC be my future-proofed 4k@60fps and full surround sound system. It's ... mostly there, but not fully.</div><div class=""><br class=""></div><div class="">Hopefully this email is useful to anyone looking to get a NUC 11 system as a frontend, and if anyone figures out how to get 24fps video to not tear I'd be thrilled. :)</div></div></div></blockquote><br class=""></div><div>Justin I solved video (but I have no 4k) and audio by using SUSE Tumbleweed. (It's intel gen-11 HW that's the issue) (and LXQT messes up the GUI) but useful input, thanks)</div><div><br class=""></div><div>James</div><div><br class=""></div><div>PS I'll try some of the jelly clips to see 4k but still using 1080 HW.</div><br class=""></body></html>