From owner-freebsd-current Sat Sep 18 23:28:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from garnet.sover.net (garnet.sover.net [209.198.87.53]) by hub.freebsd.org (Postfix) with ESMTP id 5661214C9D for ; Sat, 18 Sep 1999 23:28:20 -0700 (PDT) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc0a291.bf.sover.net [209.198.83.199]) by garnet.sover.net (8.9.3/8.9.3) with ESMTP id CAA23017; Sun, 19 Sep 1999 02:28:11 -0400 (EDT) Comments: SoVerNet Verification (on garnet.sover.net) nightfall.digitalspark.net from arc0a291.bf.sover.net [209.198.83.199] 209.198.83.199 Sun, 19 Sep 1999 02:28:11 -0400 (EDT) Date: Sun, 19 Sep 1999 02:31:58 +0000 (GMT) From: Adam Strohl To: "Rodney W. Grimes" Cc: Garrett Wollman , Matthew Dillon , N , current@FreeBSD.ORG Subject: Re: 2xPIIIx450 results & NFS results In-Reply-To: <199909190625.XAA54133@gndrsh.dnsmgr.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 18 Sep 1999, Rodney W. Grimes wrote: > So far about alls I have confirmed is that the problem does not exists > with BIOS 1009 when the apm code is not compiled into the kernel. I'll > have a full matrix of with/without apm 1008/1009/1010 some time tomarrow, > as the machines are building there system disks now. Sounds good. Is there a way to detect the BIOS revision on boot or something and either warn (ie; Say "Update yer BIOS!") or install a work around? - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message