Date: Mon, 06 Mar 2017 13:45:57 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-x11@FreeBSD.org Subject: [Bug 217585] graphics/libGL: MESA-LOADER: failed to retrieve device information Message-ID: <bug-217585-8047@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217585 Bug ID: 217585 Summary: graphics/libGL: MESA-LOADER: failed to retrieve device information Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: x11@FreeBSD.org Reporter: erisianash@gmail.com CC: freebsd-x11@FreeBSD.org Flags: maintainer-feedback?(x11@FreeBSD.org) Assignee: x11@FreeBSD.org Created attachment 180560 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=180560&action=edit glxinfo output I'm running the drm-next branch on a Lenovo Thinkpad T450s with Intel HD 5500 graphics. When testing the CFT for the Xorg 1.18 update gl worked as expected and modesetting+glamor worked flawlessly, however the Xorg+Mesa update has resulted in the following: * X fails to start with the modesetting driver reporting MESA-LOADER: failed to retrieve device information Require OpenGL version 2.1 or later. (EE) Fatal server error: (EE) AddScreen/ScreenInit failed for driver 0 on the console. * X starts with the intel driver but glxgears causes the screen to stop updating (except for the mouse pointer. glxinfo prints the same MESA-LOADER error and also reports "OpenGL renderer string: Mesa DRI Unknown Intel Chipset". I've observed this behavior on drm-next and TrueOS. -- You are receiving this mail because: You are on the CC list for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217585-8047>