On Wed, Jul 1, 2020 at 6:45 AM James Jones <jajones@xxxxxxxxxx> wrote:
This implies something is trying to use one of the old
DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK format modifiers with DRM-KMS without
first checking whether it is supported by the kernel. I had tried to
force an Xorg+Mesa stack without my userspace patches to hit this error
when testing, but must have missed some permutation. If the stalled
Mesa patches go in, this would stop happening of course, but those were
held up for a long time in review, and are now waiting on me to make
some modifications.
that's completely irrelevant. If a kernel change breaks userspace,
it's a kernel bug.
Are you using the modesetting driver in X? If so, with glamor I
presume? What version of Mesa? Any distro patches? Any non-default
xorg.conf options that would affect modesetting, your X driver if it
isn't modesetting, or glamour?
Thanks,
-James
On 6/30/20 4:08 PM, Kirill A. Shutemov wrote:
On Tue, Jun 02, 2020 at 04:06:32PM +1000, Dave Airlie wrote:_______________________________________________
James Jones (4):...
drm/nouveau/kms: Support NVIDIA format modifiers
This commit is the first one that breaks Xorg startup for my setup:
GTX 1080 + Dell UP2414Q (4K DP MST monitor).
I believe this is the crucial part of dmesg (full dmesg is attached):
[ 29.997140] [drm:nouveau_framebuffer_new] Unsupported modifier: 0x300000000000014
[ 29.997143] [drm:drm_internal_framebuffer_create] could not create framebuffer
[ 29.997145] [drm:drm_ioctl] pid=3393, ret = -22
Any suggestions?
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel