Wayland on FreeBSD

Frederic Chardon chardon.frederic at gmail.com
Wed Apr 22 08:23:51 UTC 2020

Le lun. 20 avr. 2020 à 23:06, Jan Beich <jbeich at freebsd.org> a écrit :
> Frederic Chardon <chardon.frederic at gmail.com> 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?

> https://lists.freebsd.org/pipermail/freebsd-x11/2019-January/022551.html
> 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).


More information about the freebsd-questions mailing list