Date: Mon, 23 Jun 2014 17:03:56 +0300 From: Jukka Ukkonen <jau789@gmail.com> To: Warren Block <wblock@wonkity.com> Cc: Kevin Oberman <rkoberman@gmail.com>, ray@freebsd.org, "freebsd-x11@freebsd.org" <x11@freebsd.org> Subject: Re: Xorg 7.7 suddenly lost the keyboard Message-ID: <53A833CC.70207@gmail.com> In-Reply-To: <alpine.BSF.2.11.1406220619110.86722@wonkity.com> References: <53A03A3F.9000503@gmail.com> <53A15FD1.6040206@gmail.com> <CAN6yY1sYuGZRAYcz7tioJ62690umptjfwfxHWfqi1uOTes7YvQ@mail.gmail.com> <53A4013A.2090904@gmail.com> <53A41B08.1080304@gmail.com> <CAN6yY1uW5JD1ipEkq=1k4iubVxJk2hshjsdT0d5CbuoUGB=ZsQ@mail.gmail.com> <53A69BA5.2090100@gmail.com> <alpine.BSF.2.11.1406220619110.86722@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2014-06-22 15:23, Warren Block wrote: > On Sun, 22 Jun 2014, Jukka Ukkonen wrote: > >> So, AFAIK the culprit holding the kbdmux open is vt. I just did not >> even think of having also updated the OS to the latest 10-stable >> around the same time when I updated the ports kits. >> I guess there is a risk that anyone that update their OS to the latest >> 10-stable using vt instead of syscons as well as Xorg to the latest >> 7.7 which depends on vt(9) could start seeing the same lost keyboard >> problem when they launch X the next time. >> >> I cc this also to ray@freebsd.org (the author of the commit to vt >> on June 16th) hoping for a confirmation for the issue. >> Can you test using the latest 10-stable and the latest Xorg? >> >> --jau >> >> >> PS. >> In fact I already have a patch which helps with releasing the kbdmux >> device. A lot of the calls to kbd_allocate() and kbd_release() were >> passing as the token the keyboard id while other calls to the same >> functions were passing as the token a pointer to struct vt_device. >> This does not mean, though, that X were yet aware of how to wrestle >> the kbdmux device out of vt's grab and then able to open it from within >> xf86-input-keyboard. > > I'm using 10-STABLE r267699 and vt on this machine, and the keyboard > works. It could be important that HAL is not installed, xorg.conf > does not list input devices, and neither HAL nor DEVD were enabled > when building the xorg-server port. Right... Next I have to ask whether you have started X from the command line using startx or using a display manager via init and /etc/ttys? There might be some difference there. --jau PS. The patch to homogenize the use of token parameters when calling kbd_allocate() and kbd_release() is now in bugzilla.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53A833CC.70207>