No heads up for X.org config changes?
David Chisnall
theraven at FreeBSD.org
Tue Jun 6 12:23:56 UTC 2017
Hello x11 ports folk,
I updated X.org to the latest version at the weekend (actually, a week or two ago, but I didn’t restart it until then) and discovered that X would no longer start. The fix appeared to be quite simple in the end - I had to replace ‘radeon’ in my driver line for my device section in xorg.conf with ‘modesetting’. Apparently I probably also want Option "AccelMethod" “glamor” to enable 2D acceleration and need to add Load “glamoregl” to my modules section.
None of this was documented. I looked in the UPDATING entries for xorg-drivers and xorg, on the freebsd-x11 mailing list archives and in the form and didn’t find anything relevant. Given that this update apparently broken any existing xorg.conf files that were configured to use DRI drivers, I imagine that other people were hit by it (though anyone using auto config was probably okay), so some public announcement (ideally in the UPDATING file, telling me I needed to update my config when I upgraded xorg-drivers) would have been nice.
David
More information about the freebsd-x11
mailing list