Date: Sat, 06 Oct 2018 15:38:00 +0300 From: Greg V <greg@unrelenting.technology> To: Theron <theron.tarigo@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org>, x11-list freebsd <freebsd-x11@freebsd.org> Subject: Re: linux-c7 and opengl apps? Message-ID: <1538829480.11691.0@smtp.migadu.com> In-Reply-To: <dbff419a-b104-fb60-d0b3-0eecd7dbd0d1@gmail.com> References: <CAECmPwvjJWNFELoeMcxGNFi_oXS5hWE4D2tTxi0TJpwBOriOrQ@mail.gmail.com> <dbff419a-b104-fb60-d0b3-0eecd7dbd0d1@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 5, 2018 at 11:21 PM, Theron <theron.tarigo@gmail.com> wrote: > % /compat/linux/opt/VirtualGL/bin/glxinfo | grep OpenGL > libGL error: MESA-LOADER: failed to retrieve device information Do you have linsysfs mounted? Try reading /compat/linux/sys/class/drm/card0/device/uevent. Mesa won't retrieve device information without linsysfs. I wrote the linsysfs patch that exposed the info there so that recent=20 Mesa would work :) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222375 (Wow, that was a year ago=85 interesting note from there: you might=20 need to set LIBGL_DRI3_DISABLE=3D1 for Linux apps) Also, what's with the "/opt/VirtualGL"? Are you using mesa from=20 linux-c7 or something=85 weird? > This problem has existed forever. I am not sure it is actually a=20 > fault in Linux emulation, as these very same symptoms ("failed to=20 > retrieve device information" message, console freeze) existed back in=20 > FreeBSDDesktop/freebsd-base-graphics days when attempting to run=20 > purely FreeBSD OpenGL apps. At the time the workaround was a patch=20 > to Mesa's GPU detection; the underlying kernel problem wasn't=20 > addressed. There was a somewhat related issue (but not the same one, FreeBSD and=20 Linux versions of mesa/libdrm use different mechanisms to get device=20 info). Mostly affected Wayland-EGL clients =97 they would try to access=20 /dev/dri/card408 instead of /dev/dri/card0, fail to get info and fall=20 back to software rendering. I fixed it a while ago:=20 https://gitlab.freedesktop.org/mesa/mesa/commit/db8519a369261cdedda50852fac= c45616d4eba28 But I never saw console freezes when Mesa couldn't properly detect the=20 GPU o_0 =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1538829480.11691.0>