From owner-freebsd-questions@FreeBSD.ORG Thu May 29 18:40:49 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5139D37B401 for ; Thu, 29 May 2003 18:40:49 -0700 (PDT) Received: from smtp.us2.messagingengine.com (ny2.fastmail.fm [66.111.4.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64E1243FA3 for ; Thu, 29 May 2003 18:40:48 -0700 (PDT) (envelope-from judmarc@fastmail.fm) Received: from www.fastmail.fm (server1.internal [10.202.2.132]) by server2.messagingengine.com (Postfix) with ESMTP id 19305506BE; Thu, 29 May 2003 21:40:45 -0400 (EDT) Received: from 127.0.0.1 ([127.0.0.1] helo=www.fastmail.fm) by messagingengine.com with SMTP; Thu, 29 May 2003 21:40:44 -0400 X-Epoch: 1054258844 X-Sasl-enc: OQ4mVDA+s5re1igiRazaFA Received: from sparky (dialup-67.74.84.5.Dial1.Philadelphia1.Level3.net [67.74.84.5]) by www.fastmail.fm (Postfix) with ESMTP id AA49B2A2DF; Thu, 29 May 2003 21:40:42 -0400 (EDT) To: Rich Morin , freebsd-questions@freebsd.org References: Message-ID: Content-Type: text/plain; charset=utf-8; format=flowed From: Jud MIME-Version: 1.0 Date: Thu, 29 May 2003 21:40:45 -0400 In-Reply-To: User-Agent: Opera7.11/Win32 M2 build 2880 Subject: Re: Boot problem: "ata0: resetting devices" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 May 2003 01:40:49 -0000 On Thu, 29 May 2003 01:35:37 -0700, Rich Morin wrote: > Here's a bit more information on the configuration: > > OS: FreeBSD 4.5 > > Disk: Seagate Barracuda ATA II (ST320420A; 20 GB) > > Chips: 478 pin Celeron; 2.1 GHz > 512 MB DDR DIMM (2 ea.) > SiS645DX Northbridge _or_ SiS962(L) Southbridge > > The manual indicates that the motherboard could have either a > Northbridge or Southbridge chipset, but I don't know an easy > way to tell which one this board has. Suggestions? This was a common problem along about 4.5-4.6. Upgrade to at least 4.7, see if it helps; the cause of the common problem was fixed in 4.7- prerelease. Jud