Date: Wed, 22 Apr 2020 10:23:35 +0200 From: Frederic Chardon <chardon.frederic@gmail.com> To: Jan Beich <jbeich@freebsd.org> Cc: Niclas Zeising <zeising+freebsd@daemonic.se>, freebsd-x11@freebsd.org, FreeBSD Questions Mailing List <freebsd-questions@freebsd.org> Subject: Re: Wayland on FreeBSD Message-ID: <CAMODbkk0pr0cbxKJ51RG2jqEWA%2BCg07ZNzO3bdgqoLh2QJDHuA@mail.gmail.com> In-Reply-To: <lfmp-rhno-wny@FreeBSD.org> References: <CAFYkXjmfyLZAi1HZe-RE3wLxa6GRNP6GkmtZG-4T2puRDOz0JA@mail.gmail.com> <o8rn-snio-wny@FreeBSD.org> <CAMODbkmL5PT0Q3inE=o9T2T-Gw-d6_JcHCXZSYpfm_UGdXfzxg@mail.gmail.com> <6c7abdcf-aeef-4af4-b8f4-9d7fd0e45cf0@localhost> <7fba319c-c012-8893-3ce0-e2a166c38d2d@daemonic.se> <CAMODbkkGvUUwXqzFieyM-MMwQiRu2b6L1hmvgMn9MchDkpB7ig@mail.gmail.com> <d082-pa3p-wny@FreeBSD.org> <CAMODbknWFRzru%2B1Ej3XGV6fUmdKRQB-wUf-3bEqqrQJryw37MQ@mail.gmail.com> <wo6a-ouni-wny@FreeBSD.org> <CAMODbkkreoL=RsUF9B9z1pVtL2SMK%2BaXA6Z%2BYY1xcZP4h8U9rQ@mail.gmail.com> <lfmp-rhno-wny@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Le lun. 20 avr. 2020 =C3=A0 23:06, Jan Beich <jbeich@freebsd.org> a =C3=A9c= rit : > > Frederic Chardon <chardon.frederic@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). Thanks
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMODbkk0pr0cbxKJ51RG2jqEWA%2BCg07ZNzO3bdgqoLh2QJDHuA>