Keyboard and mouse not working after X update

Steve O'Hara-Smith steve at sohara.org
Mon Jun 1 21:38:50 UTC 2020


On Mon, 1 Jun 2020 22:41:47 +0200
Polytropon <freebsd at edvax.de> wrote:

> Remaining question: Why does X still use VESA?

	Yep because that's why you're seeing such low performance from
glxgears.

> And what is that "modesetting" driver that
> gets loaded and unloaded?

	Good question - I thought it was the X end of kms but clearly not
since it gets loaded and unloaded for me too and everything driver related
is reported as 'intel' in Xorg.0.log. I run with no config at all apart
from the kld_list in rc.conf.

> X is complicated. Maybe nobody knows. :-)

	I understood X11R5 well enough to get it going on a box with no TCP
stack, no shared memory support and no streams or sockets[guess first then
see 1] - also a development environment where make had a line length limit
too short for several of the Makefiles. I did cheer when an X appeared and
followed the mouse, even more when I tortured the 1MB video card into
giving me the resolution I wanted.

	The current iteration of Xorg and DRI/DRM is mostly black magic to
me, but when it cooperates it is impressive.

[1] Pseudo TTY pairs for client/server transport - and only one half of that
code was written, I had to write the other half.

-- 
Steve O'Hara-Smith <steve at sohara.org>


More information about the freebsd-questions mailing list