From owner-freebsd-stable Sun Feb 11 5: 2:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id 9D81637B4EC for ; Sun, 11 Feb 2001 05:02:27 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.11.1/8.11.1) id f1BD1ML14545 for stable@freebsd.org; Sun, 11 Feb 2001 08:01:22 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200102111301.f1BD1ML14545@hda.hda.com> Subject: Re: uh oh - after 4 -> 4.2 cvsup, no keyboard. any ideas? In-Reply-To: <200102110855.RAA08201@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Feb 11, 2001 05:55:08 pm" To: stable@freebsd.org Date: Sun, 11 Feb 2001 08:01:12 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >:If the flags 0x100 is specified to syscons (this is now default in > >:GENERIC), syscons should revert to the AT keyboard when the USB > >:keyboard has gone. > >: > >:Kazu > > > > ok... so if we remove 'flags 0x1' from atkbd0, and leave > > 'flags 0x100' on sc0, and add an entry to /etc/usbd.conf to > > transfer control to the USB keyboard, then we will be ok? Or not? > > Yes, it should be OK. But, I have to check several things before we go > committing things. IIRC, currently USB keyboards (for that matter, > the AT keyboard too) don't have explicit /dev entries. We need to add > them, otherwise usbd and kbdcontrol won't be able to refer to the > newly attached USB keyboard. To work properly it has to be done at a lower level than usbd, you want it working when you boot into ddb. USB keyboards do have /dev entries, I have a cordless USB keyboard, I've been doing this insufficient hack at boot: if [ -c /dev/kbd1 ]; then cp /dev/null /dev/kbd1 2> /dev/null if [ $? = 0 ]; then /usr/sbin/kbdcontrol -k /dev/kbd1 fi fi which works for me especially since I just leave a second keyboard plugged into it. Yes, I know this is no solution. I assume there was a problem with leaving both keyboards enabled and mixing the input? That would work for me. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message