Date: Sun, 23 Mar 1997 00:40:01 -0800 (PST) From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: freebsd-bugs Subject: Re: kern/3067: Keyboard does not fonction after booting 2.2-RELEASE Message-ID: <199703230840.AAA29701@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/3067; it has been noted by GNATS. From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: hendrik@hg.com Cc: freebsd-gnats-submit@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: kern/3067: Keyboard does not fonction after booting 2.2-RELEASE Date: Sun, 23 Mar 1997 17:37:51 +0900 >>Number: 3067 >>Category: kern >>Synopsis: Keyboard does not fonction after booting 2.2-RELEASE >>Confidential: no >>Severity: critical >>Priority: high >>Responsible: freebsd-bugs >>State: open >>Class: sw-bug >>Submitter-Id: current-users >>Arrival-Date: Sat Mar 22 23:20:01 PST 1997 >>Last-Modified: >>Originator: Hendrik Groeneveld >>Organization: >>Release: 2.2-RELEASE >>Environment: >FreeBSD klatu.hg.com 2.2-RELEASE FreeBSD 2.2-RELEASE #0: Sun Mar 16 07:47:59 G >MT 1997 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386 >>Description: >When booting from the install floppy the keyboard does not function properly. >The keyboard does work properly in UserConfig but is not functional when sysin >stall executes. In sysinstall keys seem to produce random results. When bootin >g with the -v option the system reports a keyboard reset failure. I tried sett Would you tell us the exact error messages? With the -v option, I expect something like: sc0: the current keyboard command byte: bb. ... kbdio: RESET_KBD return code: xx. kbdio: RESET_KBD status: yy. sc0: failed to reset the keyboard. You may see the above "kbdio:..." lines repeated several times as the driver retries. (There may be additional messages for other keyboard I/O errors.) Also, have you booted the install floppy without entering UserConfig (by typing Q or ENTER when prompted to start configuration menu)? What was the outcome? >ing the console flags to 0x10 but it didn't help. I have not found a work-arou >nd for this problem. > >The problem occurs on a Vega 486 motherboard that worked very well with 2.1.5- >RELEASE. I don't think the flag bit 0x10 will help; it is primarily for some IBM ThinkPad models. So long as you did not need it before, you don't need it now too. Kazu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703230840.AAA29701>