Which Window Manager are you using ? (if any).

I'm not reproducing with Gnome.

Also are you using any display manager ?

Apologies for the delay.  The mythtv-setup and mythfrontend run in windows in a KDE Plasma display.  A VGA monitor and an HDMI TV share a single nVidia screen, with selection by the myth --geometry override.  The dmesg warning occurs when the myth window opens.

{{{
2021-03-04 12:09:46.900967 I  Display: Have main widget
2021-03-04 12:09:46.967959 I  UIBounds: New UI bounds: 1024x576+0+0
2021-03-04 12:09:47.143186 I  Display: Have main window
2021-03-04 12:09:47.143210 I  Display: Found screen 'VGA-0'
2021-03-04 12:09:47.668148 I  OpenGL: OpenGL vendor        : NVIDIA Corporation
2021-03-04 12:09:47.668154 I  OpenGL: OpenGL renderer      : GeForce GT 710/PCIe/SSE2
2021-03-04 12:09:47.668157 I  OpenGL: OpenGL version       : 4.6.0 NVIDIA 460.56
2021-03-04 12:09:47.668161 I  OpenGL: Qt platform          : xcb
2021-03-04 12:09:47.668174 I  OpenGL: EGL display          : No
2021-03-04 12:09:47.668178 I  OpenGL: Qt OpenGL module     : OpenGL (not ES)
2021-03-04 12:09:47.668181 I  OpenGL: Qt OpenGL format     : OpenGL 4.6
2021-03-04 12:09:47.668184 I  OpenGL: Qt OpenGL surface    : RGBA: 8:8:8:0 Depth: 24 Stencil: 0
2021-03-04 12:09:47.668188 I  OpenGL: Max texture size     : 16384
2021-03-04 12:09:47.668191 I  OpenGL: Shaders              : Vertex,Fragment,Geometry,Compute
2021-03-04 12:09:47.668195 I  OpenGL: 16bit framebuffers   : Yes
2021-03-04 12:09:47.686667 I  OpenGL: Initialised MythRenderOpenGL
2021-03-04 12:09:47.686672 I  OpenGL: Using full range output


}}}

I would report the issue to nvidia with a simple reproducer (I don't reproduce with my mythtv 0.31 setups).

I don't get why drm_master should be used with mythtv in such setup...


For info, are you be able to reproduce using our mythtv 0.31 build ? That would help.

I'm afraid I can't easily set up a mythtv v31 now.  DB would be incompatible.

A search of Xorg.0.log shows this:

[   147.125] Kernel command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.10.19-100.fc32.x86_64 root=/dev/mapper/fedora-root ro rd.driver.blacklist=nouveau modprobe.blacklist=nouveau rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet nvidia-drm.modeset=1

and

[   147.541] (II) xfree86: Adding drm device (/dev/dri/card0)

and recent mythtv commits have included some drm stuff.  Perhaps related?

I have put a link to this BZ on the mythtv-users list.

yeah, but mythtv db incompatibility is a lest problem compared with nvidia been proprietary...

I have updated everything except mythtv on a similar F32 box and do not get the warning on starting mythtv-setup as built on 3 Feb, v32.Pre.2205.gf5346...

There were updates of both kernel and nVidia driver.

After updating mythtv to current master, v32.Pre.2384.gf236..., dmesg there has essentially the warning that prompted this BZ.

Then I expect this is a mythtv upstream problem and as we don't distribute this development version, I expect you will fordward the issue there.
(please mention the upstream report if any).

Of course, the other part of the issue is to reproduce with a floss driver (nouveau or else on other hw).


Closing for now, but please add any additional links for this issue.
And please re-open if you think there is something that need to be fixed on our end.

Thanks for the report.