Date: Sat, 28 Aug 1999 11:16:43 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: Doug <Doug@gorean.org> Cc: freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Splash screen problem after being interrupted Message-ID: <199908280216.LAA28670@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Thu, 26 Aug 1999 23:34:03 MST." <37C6315B.22B08397@gorean.org> References: <37C6315B.22B08397@gorean.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Tonight while testing my rc file changes I decided to interrupt the spl
>ash
>screen display I have to see the boot messages. I hit scroll lock to do
>this, and it killed the splash screen, but when I went to log in the
>keyboard on the console was pretty much fubar. Every key was mapped to a
>different value, and I couldn't even C-A-D to reboot clean, I had to do a
>soft reset.
>
> Obviously this is a "... well don't do that" case, but I'm not sure it
>should be fatal. Hopefully this is of use to someone.
It depends on when you hit a key... If you happen to hit a key when
the keyboard is about to be initialized, or during the keyboard is
being initialized, bad thing may happen.
The following patch may improbe the situation, by taking longer time
to flush the keyboard buffer.
Kazu
Index: atkbd.c
===================================================================
RCS file: /src/CVS/src/sys/dev/kbd/atkbd.c,v
retrieving revision 1.13
diff -u -r1.13 atkbd.c
--- atkbd.c 1999/08/15 06:06:14 1.13
+++ atkbd.c 1999/08/19 12:08:22
@@ -1154,7 +1189,7 @@
}
/* save the current controller command byte */
- empty_both_buffers(kbdc, 10);
+ empty_both_buffers(kbdc, 200);
c = get_controller_command_byte(kbdc);
if (c == -1) {
/* CONTROLLER ERROR */
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908280216.LAA28670>