users of drm-legacy-kmod or drm drivers from base
[ This is cross-posted across several mailing lists for maximum visibility. Please respect reply-to and keep replies to x...@freebsd.org . Thank you! ] In order to improve support for the new lkpi based graphics drivers (drm-kmod) and to improve the graphics stack we have switched mesa to prefer DRI3 over DRI2. This was done in r528071. For those using drm-kmod, this should improve performance somewhat, and more importantly alleviate the use of the FIXDRM option (now removed) in xorg-server. However, for those of you using graphics/drm-legacy-kmod or the drm drivers in base, this change can cause issues. If you are experiencing problems when running OpenGL applications, you can force the use of the DRI2 backend. To force mesa to use DRI2, set the environment variable LIBGL_DRI3_DISABLE to 1 before starting any OpenGL application. The easiest way to accomplish this is by adding it to either your shell startup file or ~/.xinitrc. As an example, for users of [t]csh, put setenv LIBGL_DRI3_DISABLE 1 in ~/.cshrc. For users of bourne type shells (sh, bash, ksh, zsh, ...) instead put export LIBGL_DRI3_DISABLE=1 in ~/.profile If you are using these legacy drivers, I'm also very interested in hearing what issues you are facing that prevents you from using the new lkpi based drivers. Regards -- Niclas Zeising FreeBSD Graphics Team ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing]
On 2020-03-09 04:15, bugzilla-nore...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235564 --- Comment #8 from commit-h...@freebsd.org --- A commit references this bug: Author: emaste Date: Sun Mar 8 18:14:45 UTC 2020 New revision: 358758 URL: https://svnweb.freebsd.org/changeset/base/358758 Log: MFC r355585: remove nonexistent from-* entries from vt INDEX.keymaps Is anyone actually working on the vt(4) driver? Will it ever become feature-parity with the old sc(4) driver? I've noticed some weird things happening on my console recently... like psychedelicly-colour-coded kernel messages.. far out, man. Just wondering, -andyf ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing]
On Mon, 9 Mar 2020 07:06:31 +1000 Andy Farkas an...@andyit.com.au said On 2020-03-09 04:15, bugzilla-nore...@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235564 > > --- Comment #8 from commit-h...@freebsd.org --- > A commit references this bug: > > Author: emaste > Date: Sun Mar 8 18:14:45 UTC 2020 > New revision: 358758 > URL: https://svnweb.freebsd.org/changeset/base/358758 > > Log: >MFC r355585: remove nonexistent from-* entries from vt INDEX.keymaps Is anyone actually working on the vt(4) driver? Will it ever become feature-parity with the old sc(4) driver? I've noticed some weird things happening on my console recently... like psychedelicly-colour-coded kernel messages.. far out, man. Just wondering, -andyf Thanks for bringing this up. I've been meaning to ask similar. When building a custom kernel, and including sc(4). Then adding kern.vt=sc to loader.conf(5). I'm presented with rainbow text. I wouldn't mind so much *except* that it's color choices, and places are simply *random* Thanks in advance for any insight on this. :) --Chris ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
