From owner-freebsd-current@FreeBSD.ORG Sun Feb 15 12:50:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5EDF16A4CE for ; Sun, 15 Feb 2004 12:50:23 -0800 (PST) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8947F43D1D for ; Sun, 15 Feb 2004 12:50:23 -0800 (PST) (envelope-from freebsd-current@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1AsTDZ-0000xt-00 for ; Sun, 15 Feb 2004 21:50:21 +0100 Received: from ppp-62-194.customer.wingnet.net ([206.30.62.194]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun Feb 15 20:50:21 2004 Received: from jesse by ppp-62-194.customer.wingnet.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun Feb 15 20:50:21 2004 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Jesse Guardiani Date: Sun, 15 Feb 2004 15:50:13 -0500 Organization: WingNET Lines: 60 Message-ID: References: <402E3611.70804@freebsd.org> <20040214234449.GA38808@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: ppp-62-194.customer.wingnet.net User-Agent: KNode/0.7.2 X-Mail-Copies-To: never Sender: news Subject: Re: FreeBSD 5.2.1-RC2 available X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jesse@wingnet.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2004 20:50:24 -0000 Kris Kennaway wrote: > On Sat, Feb 14, 2004 at 06:37:30PM -0500, Jesse Guardiani wrote: > >> I'm having great difficulty with 5.2.1-RC2. I installed from an ISO just >> this afternoon. Getting the installer running wasn't easy. I tried all of >> the usual tricks that have worked for me in the past under 5.1-RELEASE >> and 5.2-RELEASE: >> >> - set hw.pci.allow_unsupported_io_range=1 >> - disabling ACPI >> >> But none of that helped. Without ACPI, my kernel would panic before >> starting sysinstall's device detection (somewhere before the keyboard >> probe). And WITH ACPI it would get further - to the sysinstall device >> detection screen, but promptly panic. Finally, I got it to install >> 5.2.1-RC2 by selecting "safe mode" from the loader menu. > > We can't do much without at least a transcription of the panic. > >> hw.ata.atapi_dma=1 >> >> Perhaps my hw.ata.atapi_dma line is breaking things? > > Certainly possible, because that's non-default and unsupported by a > lot of hardware. :) It's supported just fine on my hardware. It worked in 5.1-RELEASE and 5.2-RELEASE. And it's working now in 5.2.1-RC2. I'm writing this on the 5.2.1-RC2 kernel. I finally got it booting by manually executing these commands at the loader prompt: set hw.pci.allow_unsupported_io_range=1 set hint.apic.0.disabled=1 I guess this is OK, but I never had to set hint.apic.0.disabled=1 before. So I suppose it could be considered a regression. In addition, APM suspend/resume seems to be even more broken than it was in 5.2-RELEASE. I can't get the machine to come back from suspend no matter what I do now, whereas I used to be able to get it to resume if I booted with `boot-vD` in 5.2-RELEASE, and under 5.1-RELEASE I could get suspend/resume working with both APM *AND* ACPI. Also, setting ACPI_LOAD="NO" in /boot/loader.conf seems to be broken in 5.2.1-RC2. The loader will load acpi.ko regardless, unless explicitly told to not load it at the boot prompt with: unset ACPI_LOAD set hint.acpi.0.disabled=1 Thanks. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net