From owner-freebsd-current Thu Nov 20 21:01:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA12614 for current-outgoing; Thu, 20 Nov 1997 21:01:21 -0800 (PST) (envelope-from owner-freebsd-current) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id VAA12609 for ; Thu, 20 Nov 1997 21:01:13 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0xYlDE-0004mj-00; Thu, 20 Nov 1997 21:01:04 -0800 Date: Thu, 20 Nov 1997 21:01:00 -0800 (PST) From: Tom To: "John W. DeBoskey" cc: dg@root.com, freebsd-current@freebsd.org Subject: Re: fxp0 causes machine lockup In-Reply-To: <199711210407.AA10760@iluvatar.unx.sas.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 20 Nov 1997, John W. DeBoskey wrote: > Hi, > > With respect to the following problem, the solution came from > an unexpected location. > > I asked our hardware support folks for a 2nd motherboard to see > if the problem was specific to the hardware. Before getting the > new MB, they suggested I upgrade the bios on my machine... I said > sure, thinking FreeBSD doesn't use the bios, what could happen? Errr... generally this is CMOS upgrade, of which the BIOS is a part of. Such upgrades can affect kinds of things. Motherboard chipsets have a lot of "soft" settings, and motherboards typically have a lot of onboard CMOS these days to hold this software. For example, you can add support for the AMD K6 to some motherboards via a CMOS upgrade. Tom