From owner-freebsd-hardware Tue May 13 06:07:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA19203 for hardware-outgoing; Tue, 13 May 1997 06:07:38 -0700 (PDT) Received: from nightflight.com (nightflight.com [207.135.216.194]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA19198 for ; Tue, 13 May 1997 06:07:35 -0700 (PDT) Received: from GCRUTCHER.eosintl.com (dragon [204.31.148.2]) by nightflight.com (8.8.5/8.6.9) with SMTP id GAA16972; Tue, 13 May 1997 06:03:32 -0700 (PDT) Message-Id: <3.0.1.32.19970513060404.006a5630@nightflight.com> X-Sender: gcrutchr@nightflight.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Tue, 13 May 1997 06:04:04 -0700 To: Bruce Evans From: Gary Crutcher Subject: Re: TEAC CDROM support Cc: hardware@freebsd.org In-Reply-To: <199705130603.QAA14046@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk So.. What would be the best way to resolve this? Thanks, Gary At 04:03 PM 5/13/97 +1000, you wrote: >>> Yes, I tried to do the install. >>> The system hung after probing for APM support. > >>Yes. The most common cause of this is a bad BIOS not properly >>initialising the FPU, which is then used for various things. Try > >Erm, FreeBSD initializes the FPU before using it. > >>setting the flags value for npx0 to 1 using userconfig when booting >>(boot with '-c'), which will disable the use of the FPU in this fashion. > >Flag 1 only disables using the FPU to access video memory. Some video >memory is buggy and causes system hangs when accessed by the FPU. > >Bruce > > ------------------------------------------------------------- Gary Crutcher E-mail: gcrutchr@nightflight.com Webmaster URL: http://www.nightflight.com Member of the Internet Developers Association -------------------------------------------------------------