From nobody@FreeBSD.ORG Mon Oct 18 06:40:41 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id CEC9C14D51; Mon, 18 Oct 1999 06:40:41 -0700 (PDT)
Message-Id: <19991018134041.CEC9C14D51@hub.freebsd.org>
Date: Mon, 18 Oct 1999 06:40:41 -0700 (PDT)
From: jan.grant@bristol.ac.uk
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: Floppy install of 3.2-release, 3.3-release hang without detecting keyboard
X-Send-Pr-Version: www-1.0

>Number:         14396
>Category:       i386
>Synopsis:       Floppy install of 3.2-release, 3.3-release hang without detecting keyboard
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 18 06:50:01 PDT 1999
>Closed-Date:    Wed Sep 26 12:19:14 PDT 2001
>Last-Modified:  Wed Sep 26 12:19:42 PDT 2001
>Originator:     Jan Grant
>Release:        3.3
>Organization:
ILRT, Bristol University
>Environment:
Not applicable - didn't get that far
>Description:
Using the boot floppy/FTP install method on a Genie-2 Pentium II-350
machine from Viglen. (1245522-SEM is the serial number, exact motherboard
details are available from their website keyed on this); BIOS is
PhoenixBIOS 4.0 rel 6.0, dated 08/20/98.
Boot didn't progress very far: "keyboard: no" was displayed. Either the
bios or the bootloader can't see the keyboard.
I've called this a "low prioprity" problem 'cause it's simple to
work around; however, failing at the first hurdle may put off potential
BSD users.
>How-To-Repeat:
I tried this in multiple configurations on a few recent Viglen machines,
all had the same BIOS revision.
>Fix:
The workaround I used was to drop into BIOS setup and exit during the
floppy boot. Note, this doesn't affect normal operation, just the 
installation.

>Release-Note:
>Audit-Trail:

From: Sheldon Hearn <sheldonh@uunet.co.za>
To: jan.grant@bristol.ac.uk
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: i386/14396: Floppy install of 3.2-release, 3.3-release hang without detecting keyboard 
Date: Mon, 18 Oct 1999 16:09:44 +0200

 On Mon, 18 Oct 1999 06:40:41 MST, jan.grant@bristol.ac.uk wrote:
 
 > >Synopsis:  Floppy install of 3.2-release, 3.3-release hang without
 > >detecting keyboard
 
 Are you sure you get this with 3.3-RELEASE and not 3.2_RELEASE? This was
 a known problem with 3.2-RELEASE, but it's not mentioned in the
 3.3-RELEASE ERRATA.TXT.
 
 See http://www2.za.freebsd.org/releases/3.2R/errata.html .
 
 Ciao,
 Sheldon.
 

From: jan grant <jan.grant@bristol.ac.uk>
To: freebsd-gnats-submit@freebsd.org, jan.grant@bristol.ac.uk
Cc:  
Subject: Re: i386/14396: Floppy install of 3.2-release, 3.3-release hang 
         without  detecting keyboard
Date: Fri, 29 Oct 1999 11:15:52 +0100

 Yep, I'm sure; i tried both 3.2 and 3.3 install disks, which I got
 directly from ftp.freebsd.org (I've been stung by mirror latency before)
 
 -- 
 jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/
 Tel +44(0)117 9287163 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk
 Goedel would be proud - I'm both inconsistent _and_ incomplete.
 

From: d-lewart@uiuc.edu (Daniel S. Lewart)
To: freebsd-gnats-submit@freebsd.org, jan.grant@bristol.ac.uk
Cc:  
Subject: Re: i386/14396: Floppy install of 3.2-release, 3.3-release hang without detecting keyboard
Date: Sat, 13 Nov 1999 18:25:11 -0600 (CST)

 FreeBSD bug exterminators,
 
 > Are you sure you get this with 3.3-RELEASE and not 3.2_RELEASE?  This was
 > a known problem with 3.2-RELEASE, but it's not mentioned in the
 > 3.3-RELEASE ERRATA.TXT.
 
 I also get this with 3.3-RELEASE.  Here are some details:
 	Keyboard:	NetServer 101-key HP C1405B
 	Motherboard:	HP NetServer LM D2182-60006
 	BIOS:		PhoenixBIOS(TM) E486 Version 1.00.20.AM0
 After "boot -v", the following lines are in /var/run/dmesg.boot.
 
 Good luck,
 Daniel Lewart
 d-lewart@uiuc.edu
 -------------------------------------------------------------------------------
 Probing for devices on the ISA bus:
 atkbd: the current kbd controller command byte 0065
 atkbd: keyboard ID 0x41ab (2)
 kbdc: RESET_KBD return code:00fa
 kbdc: RESET_KBD status:00aa
 sc0 on isa
 sc0: fb0 kbd0
 sc0: VGA color <16 virtual consoles, flags=0x0>
 ed0 not found at 0x280
 fe0 not found at 0x300
 atkbdc0 at 0x60-0x6f on motherboard
 atkbd0 irq 1 on isa
 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000
 psm0: current command byte:0065
 kbdc: TEST_AUX_PORT status:0000
 kbdc: RESET_AUX return code:00fe
 kbdc: RESET_AUX return code:00fe
 kbdc: RESET_AUX return code:00fe
 kbdc: DIAGNOSE status:0055
 kbdc: TEST_KBD_PORT status:0000
 -------------------------------------------------------------------------------
 
State-Changed-From-To: open->feedback 
State-Changed-By: iedowse 
State-Changed-When: Mon Jul 9 16:37:30 PDT 2001 
State-Changed-Why:  

Is this still a problem with more recent releases such as 4.3? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=14396 
State-Changed-From-To: feedback->closed 
State-Changed-By: iedowse 
State-Changed-When: Wed Sep 26 12:19:14 PDT 2001 
State-Changed-Why:  

Feedback timeout. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=14396 
>Unformatted:
