From owner-freebsd-questions@FreeBSD.ORG Sun Mar 16 20:22:00 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 706DD106564A for ; Sun, 16 Mar 2008 20:22:00 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.235]) by mx1.freebsd.org (Postfix) with ESMTP id 24D448FC15 for ; Sun, 16 Mar 2008 20:21:59 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: by wr-out-0506.google.com with SMTP id 50so3387039wra.13 for ; Sun, 16 Mar 2008 13:21:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=MJl+lCvMznQ9ebKSryRe11cgWRQBPCwVjZsLBADHCgs=; b=sxfCZd9v/VYaY1V3LhJTjIvR0GblEt2uOqoXkhgUZPFYvTSErEE+hAkHIoy5gCA+Vo4Z5WbB1zFrd3cf4yRuBZvJh6rl4TIwnUN/SNxLna59RkPIc8yolNbAMknwhi4hO1kaJftJmJxSSEuULOIPSi8gL6veLg2nrdvI9X886Qs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Qjoa6/BoueXtFt9LKnYp14uioiNOpgTXPuzSYyzKyrWpnoxJ4c4IGOkV/V0vn91MBaHOdm/WlQzaczhsC4gBalGN7zRjAqtTJDd8jAAQjkNU6q9YLirlgQgjkXiRGspf3S7OIwZ3Zw8eHuFGSCdCz/fTVFqZX0Ut/gv5iZtrs5Q= Received: by 10.151.101.20 with SMTP id d20mr7213713ybm.193.1205698918930; Sun, 16 Mar 2008 13:21:58 -0700 (PDT) Received: by 10.150.230.16 with HTTP; Sun, 16 Mar 2008 13:21:58 -0700 (PDT) Message-ID: <3c0b01820803161321r59e93941t1bb3fe85f7726098@mail.gmail.com> Date: Sun, 16 Mar 2008 16:21:58 -0400 From: "Alexander Sack" To: "Isaac Mushinsky" In-Reply-To: <200803160107.01832.itz@mushinsky.net> MIME-Version: 1.0 References: <200803160107.01832.itz@mushinsky.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org Subject: Re: SATA problems (Abit IP35-Pro) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Mar 2008 20:22:00 -0000 On Sun, Mar 16, 2008 at 1:07 AM, Isaac Mushinsky wrote: > On Friday 14 March 2008 13:57:11 Isaac Mushinsky wrote: > > I am setting up a new system with Abit IP35-Pro (ich9r), 2 WD SATA > drives > > on the controller. There is also a SATA DVDRW to boot from. > > With the default SATA setup (SATA/IDE) the system cannot find any SATA > > drive. I was able to boot the install disk, attaching an old IDE CDROM, > but > > still could not make it see the hard drive. > > > > If I set SATA controller to AHCI, the system boots (although with some > ACPI > > errors), and I was able to install. However, fdisk thinks that the > geometry > > is "incorrect", and insists on a different one (it says the drives have > > 476gb rather than 500gb). > > > > I can install with this AHCI setup, but have no idea what the > implications > > are. Is there a known fix for SATA/IDE? Or is AHCI better? > > > Very well, but now I boot with ACPI errors like these: > > ACPI Error (psparse-0626) Method parse/execution failed [\\_TZ_.THRM._TMP] > (Node 0xffffff000224ac60), AE_AML_NO_RETURN_VALUE > ACPI Exception (dsutils-0766) AE_AML_NO_RETURN_VALUE Missing or null > operand > [20070320] > ACPI Exception (dsutils-0766) AE_AML_NO_RETURN_VALUE While creating Arg 0 > [20070320] > > If I attempt to boot without ACPI, the machine hangs while trying to mount > root filesystem. Why does disabling ACPI cause disk access problems? What > can > I do to fix this? Can I disable only thermal part of ACPI? > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > Could be a number reasons including interrupt routing to power management. Given that the AML error message refers to I believe a power mgmt table. Can you try disabling power management in the BIOS, enable AHCI, and give it a go? If that doesn't work, try turning SMP off. -aps -- "What lies behind us and what lies in front of us is of little concern to what lies within us." -Ralph Waldo Emerson