From owner-freebsd-hackers Sat May 5 11:27:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from waste.silverserver.co.at (waste.silverserver.co.at [194.152.178.7]) by hub.freebsd.org (Postfix) with ESMTP id 8660E37B43C for ; Sat, 5 May 2001 11:27:10 -0700 (PDT) (envelope-from if@sil.at) Received: from ikarus (ikarus.sil.at [194.152.178.41]) by waste.silverserver.co.at (8.11.2/8.11.2) with ESMTP id f45ILlX06097; Sat, 5 May 2001 20:21:47 +0200 Date: Sat, 5 May 2001 20:32:06 +0200 (MEST) From: Ingo Flaschberger X-Sender: chaoztc@ikarus To: Chris Faulhaber Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: no keyboard In-Reply-To: <20010505133510.A94399@peitho.fxp.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > i'm working at an iap, and we are using freebsd (4.2) boxes as routers. > > normally no keyboard or monitor is attached to the box. > > the problem is, when i connect after the boot a keyboard at the box, it is > > not recognized. at the colocations we often need access to this boxes (not > > remote access). > > is there a solution for this problem? > > > > See atkbd(4)... (remove 'flags 0x1' from the atkbd0 line) i don't have set the flags 0x1 at the kernel config. at the box the keyboard driver is installed at boot time: ---- snip --- atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 --- snap --- but if i connect a keyboard later to the box, it doesn't work. bye, Ingo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message