Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Apr 2020 10:23:35 +0200
From:      Frederic Chardon <>
To:        Jan Beich <>
Cc:        Niclas Zeising <>,,  FreeBSD Questions Mailing List <>
Subject:   Re: Wayland on FreeBSD
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <> <6c7abdcf-aeef-4af4-b8f4-9d7fd0e45cf0@localhost> <> <> <> <> <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Le lun. 20 avr. 2020 =C3=A0 23:06, Jan Beich <> a =C3=A9c=
rit :
> Frederic Chardon <> writes:
> >
> > The trace shows usage of llvmpipe after the failed ioctl on
> > /dev/dri/card0, so as I understand the lack of hardware acceleration
> > concerns only Xwayland, whereas wayland itself is accelerated ?
> Yep. Check which ioctls fail then try to reproduce outside of Mesa or
> hardcode the result. Overriding PCI ID via INTEL_DEVID_OVERRIDE is
> unlikely to help e.g.,

All below failure occurs only in xwayland, X11 and wayland succeed.

The first failure is with I915_PARAM_CHIPSET_ID. When I hardcode the
correct ID I get a failure with I915_PARAM_HAS_RELAXED_DATA. When I
force the result to be true (as with X11 and Wayland), the ioctl
DRM_I915_GEM_EXECBUFFER2_WR fails with errno EPERM.

Should I open an issue on drm-kms github? Or it is more likely a
problem on mesa side?

> If you still have no clue try playing with sysctls under compat.linuxkpi
> via /boot/loader.conf.

Any hints which ones are worth a try? How did you solve your issue (as
it seems to be pretty similar).


Want to link to this message? Use this URL: <>