From owner-freebsd-questions Thu Feb 20 13: 1:41 2003 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 6F02C37B401 for ; Thu, 20 Feb 2003 13:01:40 -0800 (PST) Received: from mailhost.det3.ameritech.net (mailhost2-sfldmi.sfldmi.ameritech.net [206.141.193.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E06E43FCB for ; Thu, 20 Feb 2003 13:01:35 -0800 (PST) (envelope-from dbailey27@ameritech.net) Received: from ameritech.net ([67.38.15.139]) by mailhost.det3.ameritech.net (InterMail vM.4.01.02.17 201-229-119) with ESMTP id <20030220205348.SNIK176.mailhost.det3.ameritech.net@ameritech.net>; Thu, 20 Feb 2003 15:53:48 -0500 Message-ID: <3E55402E.3040901@ameritech.net> Date: Thu, 20 Feb 2003 15:53:02 -0500 From: northern snowfall User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.4.1) Gecko/20020518 Netscape6/6.2.3 X-Accept-Language: en-us MIME-Version: 1.0 To: David@webedited.com Cc: freebsd-questions@freebsd.org Subject: Re: Hang after soft reboot. References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > >Would there be any chance that the system is "working" with some generic >driver and there is a specific driver for my hard drive controller (it's >an ISA card), which would solve this? > Well... all ATA in freebsd are pretty much conglomerated into the same driver... but, the problem isn't really so much the ATA as it is that the ATA expects a PM telling it what to do. Since this is something that must be done via the hardware at boot, FreeBSD doesn't really have a way to tell the ATA what to do. One solution might be hacking extra reset controls, etc, into the ATA driver so that this functionality is asserted on boot. Then, though, there is a possible chicken-egg issue: you're initializing the disk and snarfing data off the disk at the same time as attempting a hard reset, which, might cause a lock (or worse). I think your most painless solution is upgrading your mother board. Don > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message