From owner-freebsd-questions@FreeBSD.ORG  Sun May  8 21:42:26 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 777AC16A4E6
	for <freebsd-questions@freebsd.org>;
	Sun,  8 May 2005 21:42:26 +0000 (GMT)
Received: from smtp-vbr4.xs4all.nl (smtp-vbr4.xs4all.nl [194.109.24.24])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D527A43D8E
	for <freebsd-questions@freebsd.org>;
	Sun,  8 May 2005 21:42:25 +0000 (GMT)
	(envelope-from rsmith@xs4all.nl)
Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160])
	by smtp-vbr4.xs4all.nl (8.12.11/8.12.11) with ESMTP id j48LgOpx076657;
	Sun, 8 May 2005 23:42:24 +0200 (CEST)
	(envelope-from rsmith@xs4all.nl)
Received: by slackbox.xs4all.nl (Postfix, from userid 1001)
	id 452EE6590; Sun,  8 May 2005 23:42:24 +0200 (CEST)
Date: Sun, 8 May 2005 23:42:24 +0200
From: Roland Smith <rsmith@xs4all.nl>
To: freebsd-questions@freebsd.org
Message-ID: <20050508214224.GA24749@slackbox.xs4all.nl>
Mail-Followup-To: freebsd-questions@freebsd.org,
	Joseph Borg <juu.borg@gmail.com>
References: <20050508192015.GA24133@slackbox.xs4all.nl>
	<427e7fe3.55102a4e.25f3.4bf0@mx.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK"
Content-Disposition: inline
In-Reply-To: <427e7fe3.55102a4e.25f3.4bf0@mx.gmail.com>
User-Agent: Mutt/1.4.2.1i
X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725
X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt
X-GPG-Notice: If this message is not signed, don't assume I sent it!
Organization: Me, organized?
X-Virus-Scanned: by XS4ALL Virus Scanner
cc: Joseph Borg <juu.borg@gmail.com>
Subject: Re: FreeBSD on AMD 64 Boot Lock Up - ACPI Related
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 08 May 2005 21:42:26 -0000


--CE+1k2dSO48ffgeK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sun, May 08, 2005 at 11:08:49PM +0200, Joseph Borg wrote:
> Hi,
> Yes that seems to have solved the problem. Incidentally, would you know what
> the disadvantage of having acpi disabled like that is?

First of all, please to not top-post. It disturbs the normal flow of
reading.

But to answer your question, if your PC's devices are all correctly
working with FreeBSD drivers and if you don't use power management I see
no great need for ACPI. Laptops might need the power management
component of ACPI. Some motherboards use ACPI to let you read out things
like temperatures and fan speeds. But those can mostly also be
discovered by other programs.

Roland

--
R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text.
public key: http://www.xs4all.nl/~rsmith/pubkey.txt
--CE+1k2dSO48ffgeK
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQFCfofAEnfvsMMhpyURApiSAJ0cHNfSEXyunfK2nJoQ/9rHSHoZwACfar4/
Nki5r/iS/StatYBGuY718x0=
=elzi
-----END PGP SIGNATURE-----

--CE+1k2dSO48ffgeK--