Re: input devices after xorg update

[Kevin Oberman]

On Sat, Feb 22, 2020 at 12:06 PM Nuno Teixeira  wrote:

> Hi,
>
> More on udev libinput:
>
> New Xorg switch from devd to udev
> <
> https://forums.freebsd.org/threads/new-xorg-switch-from-devd-to-udev.74144/
> >
>
> Nuno Teixeira
>
>  escreveu no dia sábado, 22/02/2020 à(s) 16:54:
>
> > Hi,
> >
> > after taking quite a while to get a working x11 back, here's what
> > I learned: if you build everything from ports, it is important to
> > revisit the configured options on your x11 related ports. You need to
> > enable the libinput driver and on FreeBSD 12 or newer switch xorg-server
> > to using udev. While this is now default, your stored build options
> > might be different.
> >
> > For everyone using non-default keyboard layouts, configured as in
> > section 5.4.7.1 of the FreeBSD handbook: you now need to use the
> > "libinput" driver instead of "keyboard". Otherwise the keyboard
> > module gets loaded in addition to the libinput module, resulting in
> > both talking to the keyboard and rendering it unusable.
> >
> > Wolfgang


I have everything working again. I had to install the small patch in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244306
and follow the instructions in the pkg-message. I did NOT switch to UDEV. I
sill use the default of DEVD. I do have libinput and xf86-input-evdev
installed.

It appears that the FIXDRM patch is only required on certain hardware... in
my case a Sandy Bridge GPU.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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: input devices after xorg update

[Nuno Teixeira]

Hi,

More on udev libinput:

New Xorg switch from devd to udev


Nuno Teixeira

 escreveu no dia sábado, 22/02/2020 à(s) 16:54:

> Hi,
>
> after taking quite a while to get a working x11 back, here's what
> I learned: if you build everything from ports, it is important to
> revisit the configured options on your x11 related ports. You need to
> enable the libinput driver and on FreeBSD 12 or newer switch xorg-server
> to using udev. While this is now default, your stored build options
> might be different.
>
> For everyone using non-default keyboard layouts, configured as in
> section 5.4.7.1 of the FreeBSD handbook: you now need to use the
> "libinput" driver instead of "keyboard". Otherwise the keyboard
> module gets loaded in addition to the libinput module, resulting in
> both talking to the keyboard and rendering it unusable.
>
> Wolfgang
> ___
> 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"

input devices after xorg update

[wolfgang]

Hi,

after taking quite a while to get a working x11 back, here's what
I learned: if you build everything from ports, it is important to
revisit the configured options on your x11 related ports. You need to
enable the libinput driver and on FreeBSD 12 or newer switch xorg-server
to using udev. While this is now default, your stored build options
might be different.

For everyone using non-default keyboard layouts, configured as in
section 5.4.7.1 of the FreeBSD handbook: you now need to use the
"libinput" driver instead of "keyboard". Otherwise the keyboard
module gets loaded in addition to the libinput module, resulting in
both talking to the keyboard and rendering it unusable.

Wolfgang
___
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"