Subject: Keyboard goes away on DEC 425SL with -current kernel
To: None <port-i386@NetBSD.ORG, current-users@NetBSD.ORG>
From: Michael Richardson <>
List: current-users
Date: 01/20/1997 00:09:12

  I recently recompiled a kernel from -current to use on my
notebook. The keyboard doesn't work... More details:

  I had been running -current kernel with a PCVT console on it, and
PPP running at 9600 baud on COM0. Due to the fact that I SUP on one
machine and then use rsync to keep a second one up to date (no NFS
allowed between them), I can't be certain what date of -current it
was. I believe it was before Jan. 6.
  I installed a new kernel via FTP, rebooted remotedly. I stupidly
didn't save the old one (I had three working previous ones on the disk
already...). I rebooted, and then discovered that my keyboard didn't
work. The 1.2 kcadp install kernel works, as does a kernel from a
production 1.2 machine. I have since rebuilt with pc0 instead of vt0
(which i thought was the culprit) and have found the same problem..
  I should note that the keyboard works at the boot loader. It doesn't
work when you boot with -a to answer the root? prompt, so this isn't
getty or something not working. I have not had DDB built in, or I'd
have tried CTL-ALT-ESC.
  With pcvt, I got complaints before the kernel banner of:	
	pcvt: doreset() - timeout controller write command
  I'm beginning to get suspicious of perhaps the delay macros...

  I have since (today) merged the PCMCIA-current in hoping maybe this
might do something. (It does recognize my 3c589 now)
  My next step is to recompile the kernel with DDB console on
COM1. I'm open to other suggestions, particularly compiled kernels
of particular vintages (knowing when -current started to break would
be nice...)

   :!mcr!:            |  Network security consulting and 
   Michael Richardson |      contract programming
 WWW: PGP key available.

Version: 2.6.3ia
Charset: latin1
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface