From owner-freebsd-hardware Mon May 12 19:32:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA22464 for hardware-outgoing; Mon, 12 May 1997 19:32:31 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA22459 for ; Mon, 12 May 1997 19:32:26 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA12619; Tue, 13 May 1997 12:02:12 +0930 (CST) From: Michael Smith Message-Id: <199705130232.MAA12619@genesis.atrad.adelaide.edu.au> Subject: Re: TEAC CDROM support In-Reply-To: <3.0.1.32.19970512192309.006acdac@nightflight.com> from Gary Crutcher at "May 12, 97 07:23:09 pm" To: gcrutchr@nightflight.com (Gary Crutcher) Date: Tue, 13 May 1997 12:02:12 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Gary Crutcher stands accused of saying: > Yes, I tried to do the install. > The system hung after probing for APM support. > > I "assumed" after reading the hardware.txt file > that it was because the TEAC drive was not listed > as supported hardware. > > Bad assumption? Yes. The most common cause of this is a bad BIOS not properly initialising the FPU, which is then used for various things. Try 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. You can also try disabling apm0, as it's possible your APM BIOS is busted too. > Gary -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[