From nobody@FreeBSD.org Wed Mar 15 05:08:33 2000 Return-Path: Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 95F6737BA05 for ; Wed, 15 Mar 2000 05:08:33 -0800 (PST) (envelope-from nobody@FreeBSD.org) Received: (from nobody@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id FAA22388; Wed, 15 Mar 2000 05:08:33 -0800 (PST) (envelope-from nobody@FreeBSD.org) Message-Id: <200003151308.FAA22388@freefall.freebsd.org> Date: Wed, 15 Mar 2000 05:08:33 -0800 (PST) From: sperber@informatik.uni-tuebingen.de Sender: nobody@FreeBSD.org To: freebsd-gnats-submit@FreeBSD.org Subject: FreeBSD boot loader does not recognize keyboard on MSI 6195 motherboard X-Send-Pr-Version: www-1.0 >Number: 17391 >Category: i386 >Synopsis: FreeBSD boot loader does not recognize keyboard on MSI 6195 motherboard >Confidential: no >Severity: critical >Priority: high >Responsible: jhb >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Mar 15 05:10:01 PST 2000 >Closed-Date: Sun Oct 20 11:32:23 PDT 2002 >Last-Modified: Sun Oct 20 11:32:23 PDT 2002 >Originator: Mike Sperber >Release: 3.2-RELEASE, 3.4-RELEASE, and 4.0-CURRENT >Organization: University of Tübingen >Environment: N/A >Description: The FreeBSD boot disk (of all releases mentioned above) starts up with keyboard: no on my new Athlon 600Mhz system on an MSI 6195 motherboard. This is not a hardware problem, as both NT and RedHat 6.1 boot fine on the system. >How-To-Repeat: Boot off any of the boot.flp images. >Fix: >Release-Note: >Audit-Trail: From: Sheldon Hearn To: sperber@informatik.uni-tuebingen.de Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: i386/17391: FreeBSD boot loader does not recognize keyboard on MSI 6195 motherboard Date: Wed, 15 Mar 2000 15:27:39 +0200 On Wed, 15 Mar 2000 05:08:33 PST, sperber@informatik.uni-tuebingen.de wrote: > The FreeBSD boot disk (of all releases mentioned above) starts up with > > keyboard: no > > on my new Athlon 600Mhz system on an MSI 6195 motherboard. What keyboard have you got, and is the keyboard enabled in your BIOS? Ciao, Sheldon. From: sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) To: Sheldon Hearn Cc: freebsd-gnats-submit@freebsd.org Subject: Re: i386/17391: FreeBSD boot loader does not recognize keyboard on MSI 6195 motherboard Date: 15 Mar 2000 14:31:10 +0100 >>>>> "Sheldon" == Sheldon Hearn writes: Sheldon> On Wed, 15 Mar 2000 05:08:33 PST, sperber@informatik.uni-tuebingen.de wrote: >> The FreeBSD boot disk (of all releases mentioned above) starts up with >> >> keyboard: no >> >> on my new Athlon 600Mhz system on an MSI 6195 motherboard. Sheldon> What keyboard have you got, I've tried a Keysonic KB 230, an old Cherry MF/2 keyboard (previously hooked up and working fine on another FreeBSD system), and an Olivetti PS/2 keyboard. Same result everywhere. Sheldon> and is the keyboard enabled in your BIOS? Yes. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla Responsible-Changed-From-To: freebsd-bugs->rnordier Responsible-Changed-By: sheldonh Responsible-Changed-When: Wed Mar 15 05:48:25 PST 2000 Responsible-Changed-Why: Robert, can you have a look at this one? From: sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) To: Sheldon Hearn Cc: freebsd-gnats-submit@freebsd.org Subject: Re: i386/17391: FreeBSD boot loader does not recognize keyboard on MSI 6195 motherboard Date: 15 Mar 2000 19:06:13 +0100 >>>>> "Sheldon" == Sheldon Hearn writes: Sheldon> On Wed, 15 Mar 2000 05:08:33 PST, sperber@informatik.uni-tuebingen.de wrote: >> The FreeBSD boot disk (of all releases mentioned above) starts up with >> >> keyboard: no >> >> on my new Athlon 600Mhz system on an MSI 6195 motherboard. I've found the cause: it's the timing of the keyboard probe. When I set #define PROBE_MAXRETRY 500 #define PROBE_MAXWAIT 40000 in probe_keyboard.c, the keyboard gets detected. Furthermore, I can install with -h. It seems to me the delay code there is going to be less and less likely to work with newer motherboards. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla Responsible-Changed-From-To: rnordier->freebsd-bugs Responsible-Changed-By: rnordier Responsible-Changed-When: Tue Jun 13 14:43:12 PDT 2000 Responsible-Changed-Why: Return this to the pool, as I'm not actively involved with the boot code just now. http://www.freebsd.org/cgi/query-pr.cgi?pr=17391 Responsible-Changed-From-To: freebsd-bugs->jhb Responsible-Changed-By: jhb Responsible-Changed-When: Mon Jun 19 10:37:25 PDT 2000 Responsible-Changed-Why: This may be fixed by some hacking around in boot2's keyboard probe code. Since I sort of maintain boot2, I'll take this. http://www.freebsd.org/cgi/query-pr.cgi?pr=17391 From: Keith Jones To: freebsd-gnats-submit@FreeBSD.org, sperber@informatik.uni-tuebingen.de Cc: Subject: Re: i386/17391: FreeBSD boot loader does not recognize keyboard on MSI 6195 motherboard Date: Tue, 15 Oct 2002 20:19:23 +0100 Hi, As it doesn't look like much has happened with this PR I thought I'd resurrect it, so I took a look at the boot code. The commentary around delay1ms() in /usr/src/sys/boot/i386/libi386/vidconsole.c has this to say: /* * This routine uses an inb to an unused port, the time to execute that * inb is approximately 1.25uS. This value is pretty constant across * all CPU's and all buses, with the exception of some PCI implentations * that do not forward this I/O address to the ISA bus as they know it * is not a valid ISA bus address, those machines execute this inb in * 60 nS :-(. * */ The unused port in question is port 0x84. (Incidentally, this is #define'd in the code; the macro is used in delay7() but not in delay1ms(). This should probably be corrected for neatness' sake.) I suspect the MSI 6195 is one of those boards which breaks the delay routine. ;) (Strangely enough, MSI chipset works just fine with it.) There are two workarounds for this; either, as suggested, whack up PROBE_MAXWAIT to about 20 times its current value, or come up with a better delay routine. The only problem I can see with increasing PROBE_MAXWAIT is that it may slow things down marginally when you boot up a machine that doesn't have a keyboard and don't put the '-P' option into 'boot.conf'. A better delay routine might be neater but is beyond my capabilities, I'm afraid ;) Keith From: sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) To: Keith Jones Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: i386/17391: FreeBSD boot loader does not recognize keyboard on MSI 6195 motherboard Date: Sun, 20 Oct 2002 17:48:19 +0200 This PR can be closed. >>>>> "Keith" == Keith Jones writes: Keith> Hi, Keith> As it doesn't look like much has happened with this PR I thought I'd Keith> resurrect it, so I took a look at the boot code. The commentary around Keith> delay1ms() in /usr/src/sys/boot/i386/libi386/vidconsole.c has this to Keith> say: Keith> /* Keith> * This routine uses an inb to an unused port, the time to execute that Keith> * inb is approximately 1.25uS. This value is pretty constant across Keith> * all CPU's and all buses, with the exception of some PCI implentations Keith> * that do not forward this I/O address to the ISA bus as they know it Keith> * is not a valid ISA bus address, those machines execute this inb in Keith> * 60 nS :-(. Keith> * Keith> */ Keith> The unused port in question is port 0x84. (Incidentally, this is Keith> #define'd in the code; the macro is used in delay7() but not in Keith> delay1ms(). This should probably be corrected for neatness' sake.) Keith> I suspect the MSI 6195 is one of those boards which breaks the delay Keith> routine. ;) (Strangely enough, MSI chipset works just fine with it.) Keith> There are two workarounds for this; either, as suggested, whack up Keith> PROBE_MAXWAIT to about 20 times its current value, or come up with a Keith> better delay routine. The only problem I can see with increasing Keith> PROBE_MAXWAIT is that it may slow things down marginally when you boot Keith> up a machine that doesn't have a keyboard and don't put the '-P' Keith> option into 'boot.conf'. A better delay routine might be neater but is Keith> beyond my capabilities, I'm afraid ;) I just checked again: for whatever reason, things work fine now with 4.6.2. Thanks for taking a look! -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla State-Changed-From-To: open->closed State-Changed-By: jhb State-Changed-When: Sun Oct 20 11:32:04 PDT 2002 State-Changed-Why: Submitter reports that problem does not occur with 4.6.2. http://www.freebsd.org/cgi/query-pr.cgi?pr=17391 >Unformatted: