From owner-freebsd-current@FreeBSD.ORG Tue Jul 3 01:12:35 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCF09106566B for ; Tue, 3 Jul 2012 01:12:35 +0000 (UTC) (envelope-from kaho@ed.niigata-u.ac.jp) Received: from caav02.cais.niigata-u.ac.jp (caav02.cais.niigata-u.ac.jp [133.35.17.134]) by mx1.freebsd.org (Postfix) with ESMTP id 895D98FC08 for ; Tue, 3 Jul 2012 01:12:35 +0000 (UTC) Received: from caav02.cais.niigata-u.ac.jp (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id C98D8282CAE; Tue, 3 Jul 2012 09:52:02 +0900 (JST) Received: from pf2.ed.niigata-u.ac.jp (pf2.ed.niigata-u.ac.jp [133.35.172.22]) by caav02.cais.niigata-u.ac.jp (Postfix) with ESMTPS id B4932282C9A; Tue, 3 Jul 2012 09:52:02 +0900 (JST) Received: from pf2.ed.niigata-u.ac.jp (localhost [127.0.0.1]) by pf2.ed.niigata-u.ac.jp (8.14.5/8.14.5) with ESMTP id q630pbEN006040; Tue, 3 Jul 2012 09:51:38 +0900 (JST) (envelope-from kaho@pf2.ed.niigata-u.ac.jp) To: Matthias Apitz References: <20120629133422.GA2233@tiny.Sisis.de> <201206301349.58930.erich@alogreentechnologies.com> <20120630151130.GA1106@tiny.Sisis.de> <201207010629.29148.erich@alogreentechnologies.com> <20120701065849.GA2681@tinyCurrent> X-Mailer: MH-E 8.2; MH 6.8.4.JP-3.05; GNU Emacs 23.4.1 User-Agent: EMH/1.14.1 SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-2022-JP-2?B?R29qGyQoRCtXGyhC?=) APEL/10.8 Emacs/23.4 (amd64-portbld-freebsd10.0) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=ISO-2022-JP-2 Date: Tue, 03 Jul 2012 09:51:37 +0900 Message-ID: <6039.1341276697@pf2.ed.niigata-u.ac.jp> From: Kaho Toshikazu X-Mailman-Approved-At: Tue, 03 Jul 2012 02:27:56 +0000 Cc: freebsd-current@freebsd.org, Hans Petter Selasky Subject: Re: no keyboard after booting r235646 in laptop FS Amilo D 7830 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2012 01:12:35 -0000 Hello Matthias Apitz and -current member, "sys/dev/atkbdc/atkbdc_isa.c" may not have your keyboard controller's ID. Run `acpidump -dt` and search your keyboard description. Is your keyboard controller "PNP0303" ? -- kaho@ed.niigata-u.ac.jp > El d$(D+c*$(B Sunday, July 01, 2012 a las 06:29:28AM +0700, Erich Dollansky escribi$(D+Q"k(B > > Hi, > > > and no older versions. I will install the USB booted system to harddisk > > and hope when booted from disk and not from USB the keyboard is working. > > > > I installed the system r235646 to disk and it shows the same problem: no > keyboard; > > if 7.4 still runs but not anything after 8.0, it is most likely what I have written. Some USB hardware is not supported anymore in 8 and later. > > I would install the old one just to see You will also know wat hwardware is used there and how it is supported. > > This might be the faster route before starting debugging something which is not there. > > I said already that it works with a r214444 version, CURRENT from > October 2010; so I booted this again and concerning keyboard, here is > the diff: > > r214444: > > $ fgrep -i kb /tmp/dmesg-r214444.txt > kbd1 at kbdmux0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > > $ ls -l /dev/kb* > lrwxr-xr-x 1 root wheel 6 Jul 1 08:39 /dev/kbd0 -> atkbd0 > lrwxr-xr-x 1 root wheel 7 Jul 1 08:39 /dev/kbd1 -> kbdmux0 > crw------- 1 root wheel 0, 17 Jul 1 08:39 /dev/kbdmux0 > > r235646: > > $ fgrep -i kb /tmp/dmesg-r235646.txt > atkbd: the current kbd controller command byte 0065 > atkbd: keyboard ID 0x41ab (2) > sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) > atkbdc0 failed to probe at port 0x60 on isa0 > > $ ls -l /dev/kb* > lrwxr-xr-x 1 root wheel 7 Jul 1 08:39 /dev/kbd1 -> kbdmux0 > crw------- 1 root wheel 0, 17 Jul 1 08:39 /dev/kbdmux0 > > the complete /tmp/dmesg-r214444.txt is attached, the > /tmp/dmesg-r235646.txt was in some message of this thread; > > So the question is: why the is not > detected anymore in r235646, while it is in r214444? > > Thanks > > matthias