Date: Wed, 11 Mar 2020 14:54:43 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Greg Rivers <gcr+freebsd-stable@tharned.org> Cc: FreeBSD current users <FreeBSD-current@freebsd.org>, FreeBSD Stable Users <freebsd-stable@freebsd.org> Subject: Re: New Xorg - different key-codes Message-ID: <CAN6yY1v_NjMuOF84F6bYEbB2guJNMw_8x_JjbCv_QSmy4tg2WQ@mail.gmail.com> In-Reply-To: <1938208.uJW0cDvVUg@no.place.like.home> References: <6762.1583886003@critter.freebsd.dk> <f130773f-7d68-2062-3ada-e9ebd888a5fe@freebsd.org> <20200311185345.GG3091@server.rulingia.com> <1938208.uJW0cDvVUg@no.place.like.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 11, 2020 at 1:51 PM Greg Rivers <gcr+freebsd-stable@tharned.org> wrote: > On Wednesday, 11 March 2020 13:53:45 CDT Peter Jeremy wrote: > > On 2020-Mar-11 10:29:08 +0100, Niclas Zeising <zeising@freebsd.org> > wrote: > > >This has to do with switching to using evdev to handle input devices on > > >FreeBSD 12 and CURRENT. There's been several reports, and suggested > > >solutions to this, as well as an UPDATING entry detailing the change. > > > > The UPDATING entry says that it's switched from devd to udev. There's no > > mention of evdev or that the keycodes have been roto-tilled. It's > basically > > a vanilla "things have been changed, see the documentation" entry. Given > > that entry, it's hardly surprising that people are confused. > > > Indeed, the change has been a bit inconvenient and time consuming to deal > with. > > But I don't think we should let this overshadow the dedication and very > hard work that Niclas and the graphics team have done and continue to do to > keep FreeBSD relevant on the desktop. I for one am very grateful for that. > > -- > Greg > And the people involved have been very active in helping people resolve the problems. In particular, Michael Gmelin had been very helpful in providing a workaround for the failure of the brightness control buttons on my rather ancient T520. He has also provided a solution for the failure of the volume control buttons that I've had since the last update to MATE. I have yet to try it as something else (no idea what) had magically fixed this after a couple of months of them not working. I can't figure out what "fixed" this, but it just started working a couple of weeks ago. Until/unless it fails, I'm not touching things. Also, my apologies to Michael as I have not responded to him with a status update for WAY too long. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1v_NjMuOF84F6bYEbB2guJNMw_8x_JjbCv_QSmy4tg2WQ>