From nobody@FreeBSD.ORG Tue Sep  7 19:03:24 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 4ECB014F2D; Tue,  7 Sep 1999 19:03:24 -0700 (PDT)
Message-Id: <19990908020324.4ECB014F2D@hub.freebsd.org>
Date: Tue,  7 Sep 1999 19:03:24 -0700 (PDT)
From: james-hunsaker@uiowa.edu
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: system halts after npx0 detected on 3.2 install
X-Send-Pr-Version: www-1.0

>Number:         13630
>Category:       kern
>Synopsis:       system halts after npx0 detected on 3.2 install
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Sep  7 19:10:01 PDT 1999
>Closed-Date:    Thu Jun 7 05:47:37 PDT 2001
>Last-Modified:  Thu Jun 07 05:58:17 PDT 2001
>Originator:     James A Hunsaker IV
>Release:        3.2 Install
>Organization:
>Environment:
Can't boot, however running a Celeron 400Mhz on an Intel CA810 motherboard which uses the 810 Chipset (shares video ram with main ram).  The system has 128MB ram and runs fine with other OSes.
>Description:
System halts on install after

npx0 on motherboard
npx0: INT 16 interface

is displayed.
Have tried setting flag 7, but still halts.
Have tried setting flag 1, but still halts.
Have tried disabling npx0, but halts after vga0.

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:

From: "James A Hunsaker IV" <james-hunsaker@uiowa.edu>
To: <freebsd-gnats-submit@freebsd.org>, <james-hunsaker@uiowa.edu>
Cc:  
Subject: Re: kern/13630: system halts after npx0 detected on 3.2 install
Date: Thu, 9 Sep 1999 20:32:24 -0500

 Tried using the 3.3 RC floppies and it booted the first time fine, however I
 had to quit the install.  When I tried booting using the same identical
 floppies an hour later, the old behavior came back.  It still freezes after
 displaying
 
 npx0 on motherboard
 npx0: INT 16 interface
 
 I configured the kernel EXACTLY the same way I did before when it worked.
 Also, I notice that before the install program comes up, it reports that
 RTC? memory doesn't match up with bios memory so using bios instead.  It
 reports this twice, but I can't get the exact error because it goes so fast.
 
 
 

From: <wganz@texoma.net>
To: <freebsd-gnats-submit@FreeBSD.org>, <james-hunsaker@uiowa.edu>
Cc:  
Subject: Re: kern/13630: system halts after npx0 detected on 3.2 install
Date: Tue, 22 Feb 2000 07:50:04 -0600

 I am trying to install FreeBSD3.4 on a  Compaq Deskpro 575(16mg/400mgHD).
 The only difference from factory configuration is that I put a SCSI ZIP on
 it to load \FreeBSD
                                                             \FreeBSD\bin
 
 \FreeBSD\floppies
 
 \FreeBSD\manpages
 
 \FreeBSD\packages
 
 Naturally packages was subset of the full CDROM.
 
 I am not interested in XWindows on it and a CLI with bash "is good enough"
 for my purposes.  .:.  the HD space limitations are not an acute problem but
 an annoyance.
 
 I ftp'd the latest 3.4 release since it was released after I got my 3.2 book
 so I am using the 3.2 book & the 3.4 errata & release notes from
 FreeBSD.org.
 
 Problem definition:
 Computer will boot & run Win3.1 without problem. Accesses ZIP drive & can
 copy to \FreeBSD desired files.
 .:.  we know that basic hardware works
 
 Create kernel & mfsroot floppies & boot in that sequence to installation
 screen.
 
 Installation dies at:
 npx0 on motherboard
 npx0 INT 16 interface
 <<dies here>>
 
 rtfm & rtfFAQ to find Problem Reports misc/13378 & kern/13630
 
 now try the "flags npx0 1" incantation
 config>visual
 remove conflicts
 Q Yes and
 npx0 on motherboard
 npx0 INT 16 interface
 <<dies here>>
 
 now try the "flags npx0 -1" incantation {{ done for lack of better ideas }}
 config>visual
 remove conflicts
 Q Yes and
 npx0 on motherboard
 npx0 INT 16 interface
 <<dies here>>
 
 now try the "flags npx0 7" incantation
 remove conflicts
 Q Yes and
 npx0 on motherboard
 npx0 INT 16 interface
 <<dies here>>
 
 now try the "disable npx0" incantation
 remove conflicts
 Q Yes and
 vga0 at 0x360-0x3df maddr 0xa0000 msize 131072 on isa
 <<dies here>>
 
 
 
 
State-Changed-From-To: open->feedback 
State-Changed-By: iedowse 
State-Changed-When: Wed Jun 6 17:43:57 PDT 2001 
State-Changed-Why:  

Is this still a problem in more recent releases? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=13630 
State-Changed-From-To: feedback->closed 
State-Changed-By: iedowse 
State-Changed-When: Thu Jun 7 05:47:37 PDT 2001 
State-Changed-Why:  

Submitter has not tried booting more recent releases on the problem 
machine, so without any further information, I'll assume the issue 
is resolved. 


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