From owner-freebsd-alpha Sat Jun 3 13:12:35 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8CA2A37BF4C for ; Sat, 3 Jun 2000 13:12:29 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA17456; Sat, 3 Jun 2000 16:12:25 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA52514; Sat, 3 Jun 2000 16:11:55 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 3 Jun 2000 16:11:54 -0400 (EDT) To: wc.bulte@chello.nl Cc: FreeBSD-alpha mailing list Subject: Re: Miata console after 'halt' In-Reply-To: <20000603130518.A73911@freebie.wbnet> References: <20000603130518.A73911@freebie.wbnet> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14649.26030.594976.699497@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > I wonder if anybody has ever seen the following: > > Miata MX5 or Miata GL. Both run -current without any problems. Shutdown > FreeBSD. > > Now the SRM console yells for every keystroke: "scancode foo not supported" > or something close to that. Needless to say the (DEC) keyboard works just > fine when FreeBSD is running. A reset is needed to get the SRM to work with > the keyboard again. > > Not critical, but annoying. Yes, I see this. It hasn't been very high in my priority list. FWIW, I don't think it happens with an AS200 or an AS600... Have you seen any keyboard related oddities when running X? A while ago I noticed that if I had Xkbd enabled on my Miata GL at home, I'd get a random ` (back-quote) characters appearing about every 500th keypress. Turning putting XkbDisable in my /etc/XF86Config made the problem go away -- I assumed it was just a bad keyboard. (BTW, XkbDisable doesn't help the console problem you mention) Yesterday I fired up X (an old build of 3.3.4) on the UP1000 I'm working on (FreeBSD mostly works, BTW) and noticed that the keyboard didn't work at all. In fact, I had to reboot the machine after starting X in order to get the keyboard back. XkbDisable cures this problem too.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message