[mythtv-users] mythtv issues at 4K (Intel NUC 12th Gen)

[Dan Wilga]

On 11/17/22 2:19 PM, Gabriel Kuri via mythtv-users wrote:
> I have an Intel NUC 12th Gen that I loaded a mythfrontend on 
> (31/fixes). When X is running at 4K resolution (3840x2160), 
> mythfrontend won't load. Running it in the foreground generates the 
> following output. The X server didn't die, it's still there and 
> running fine...
>
> 2022-11-17 11:11:17.555931 I  OpenGL: Initialised MythRenderOpenGL
> 2022-11-17 11:11:17.555932 I  OpenGL: Using full range output
> 2022-11-17 11:11:17.556364 I  UICache: Pruning cache directory: 
> /home/mythtv/.mythtv/cache/remotecache
> 2022-11-17 11:11:17.556374 I  UICache: Kept 0 files, deleted 0 files, 
> stat error on 0 files
> 2022-11-17 11:11:17.556375 I  UICache: Pruning cache directory: 
> /home/mythtv/.mythtv/cache/thumbnails
> 2022-11-17 11:11:17.556377 I  UICache: Kept 0 files, deleted 0 files, 
> stat error on 0 files
> 2022-11-17 11:11:17.580900 I  CECAdapter: libCEC support is disabled.
> .752015 I  Qt: The X11 connection broke (error 4). Did the X11 server die?
> .753197 I  UDPListener: Disabling
>
> If I force mythfrontend to a lower geometry (ie 1080p), it comes up 
> fine. I can even go up to geometry 2000x1800, it loads. But as I 
> increase either the X or Y on the geometry, it will eventually get to 
> the point where it won't load and log the error "Qt: The X11 
> connection broke (error 4). Did the X11 server die?".
>
> I realize the GPU on this Nuc 12th gen is pretty new, I think it's an 
> Iris Xe ? I do have linux kernel 6.0.8 running to provide the latest 
> i915 driver and I also updated the intel-media-va-driver to 22.2.1.
>
> I also tried myth 32/fixes with the same result.
>
> I ran mplayer with a 4K test file and it plays.
>
> I'm not sure how to further debug the issue at this point. Anyone 
> running a newer Intel NUC 12th gen with the newer Alder Lake GPU ? Any 
> thoughts on what's going on?

I would look in the X server logs. The location depends on your distro, 
but one common location is /var/log/Xorg.0.log. (Substitute the correct 
X display ID for "0".)

My guess is that you could be running out of memory due to the much 
higher amount required for that resolution.