From owner-freebsd-x11@FreeBSD.ORG Wed Jun 18 09:46:02 2014 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1B3BFDEF for ; Wed, 18 Jun 2014 09:46:02 +0000 (UTC) Received: from mail-la0-x233.google.com (mail-la0-x233.google.com [IPv6:2a00:1450:4010:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7E4282C96 for ; Wed, 18 Jun 2014 09:46:01 +0000 (UTC) Received: by mail-la0-f51.google.com with SMTP id mc6so340761lab.24 for ; Wed, 18 Jun 2014 02:45:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=nIfRaNtrwt+UwwNE+Cv0G9BlwDA0SElru4RZS+eVHV4=; b=d5cIyt6QCB1PG+5+3Hw2Nv8bJ6jQMDNQtxinwUhRPYLL9SavtDOI8uTAqBf7aT6rWW YT2Q5xWetc8exiAqWvV4miyd+FVyMpEIraFhn8+p8qQxewP+/JopUuhe5rC0eA6E6Z+F Ok0eQXyBldsM0OmtELAaCyOCD4enU0PcyMbU5BghXEhDZXbk8z6nu7X3Fjp92Kmz4B6f 4GAxJ84/v9y/arls0XejJPQ57EIlI0gdsUzxWDBXF1VeKFz+RO4JLODwQju1PV7wS5nn EXxcQ6zckxCh9oxZu/5Qw2dGH6ZCgTN+1KjENwTlpV+hWdwoPKPyZPzhMDPsZK3Ks69F Ul4A== X-Received: by 10.152.36.38 with SMTP id n6mr677774laj.0.1403084758673; Wed, 18 Jun 2014 02:45:58 -0700 (PDT) Received: from [192.168.1.197] (xdsl-205-163.nblnetworks.fi. [83.145.205.163]) by mx.google.com with ESMTPSA id ul4sm1187914lbb.33.2014.06.18.02.45.56 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 18 Jun 2014 02:45:57 -0700 (PDT) Message-ID: <53A15FD1.6040206@gmail.com> Date: Wed, 18 Jun 2014 12:45:53 +0300 From: Jukka Ukkonen User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: x11@FreeBSD.org Subject: Fwd: Xorg 7.7 suddenly lost the keyboard References: <53A03A3F.9000503@gmail.com> In-Reply-To: <53A03A3F.9000503@gmail.com> X-Forwarded-Message-Id: <53A03A3F.9000503@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2014 09:46:02 -0000 Hi all, I sent the following issue to questions@freebsd.org, but it seems there are no ideas available there. So, in the hope that someone on the list x11@freebsd.org might have some idea what has happened, I send the same issue to this mailing list as well. It would be really nice to get my keyboard working with x11/xorg again. --jau -------- Original Message -------- Subject: Re: Xorg 7.7 suddenly lost the keyboard Date: Tue, 17 Jun 2014 15:53:19 +0300 From: Jukka Ukkonen To: questions@freebsd.org After digging a bit deeper in the issue the most revealing symptom is this error in /var/log/Xorg.0.log... [ 585.774] (II) Using input driver 'kbd' for 'Keyboard0' [ 585.774] (**) Option "CoreKeyboard" [ 585.774] (**) Keyboard0: always reports core events [ 585.774] (**) Keyboard0: always reports core events [ 585.774] (**) Option "Protocol" "standard" [ 585.774] (**) Option "Device" "/dev/kbdmux0" [ 585.774] (EE) Keyboard0: cannot open "/dev/kbdmux0" [ 585.774] (EE) PreInit returned 8 for "Keyboard0" [ 585.774] (II) UnloadModule: "kbd" That "PreInit" is apparently kbdPreInit() and the returned code 8 stands for BadMatch. What should I make of this? --jau On 2014-06-15 17:32, Jukka Ukkonen wrote: > > Hello everybody, > > I recently had a very peculiar experience with Xorg 7.7 on an amd64 > system running FreeBSD 10-stable. > Suddenly any and all X11 applications lost the keyboard. When using > vanilla vt only the same keyboard > works just fine. > I guess this happened after I had updated the ports tree using svn and > run "portupgrade --batch -y -a". > Does anyone have any idea what might be the root cause and how to get > around this. > Previously I have been using HAL configured devices with Xorg. Now > even explicitly forcing the automatic > device detection off did not bring the keyboard back. Rebuilding > xorg-server to use devd instead of HAL > did not help either. So, I am confused. Any ideas what to try? > > Cheers, > --jau >