Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Oct 2004 09:27:31 +0200
From:      Geert Hendrickx <geert.hendrickx@ua.ac.be>
To:        Subhro <subhro.kar@gmail.com>
Cc:        rchopra@cal.berkeley.edu
Subject:   Re: Shutdown And User Intervention
Message-ID:  <20041014072731.GA31155@lori.mine.nu>
In-Reply-To: <b2807d04041014001726bc77cb@mail.gmail.com>
References:  <20041013175012.GA23062@lori.mine.nu> <20041014043925.34640.qmail@web52101.mail.yahoo.com> <b2807d04041014001726bc77cb@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 14, 2004 at 12:47:59PM +0530, Subhro wrote:
> On Wed, 13 Oct 2004 21:39:25 -0700 (PDT), Rishi Chopra
> <idfubar@yahoo.com> wrote:
> 
> > Thanks to Mick, Andreas, Geert and Dee for their
> > suggestions.
> > 
> > I tried adding the suggested line (I'm running 5.2.1)
> > but the response is:
> > 
> > config: Error: device "acpica" is unknown
> > config: 1  errors
> > 
> > Do I need to be running a special kernel to enable
> > acpica?  Is there any other way to enable ACPI?  Will
> > I have to start a daemon after compiling the kernel to
> > enable ACPI?
> 
> There are two ways to do it. One of them is to add the line device
> acpi to the kernel config and recompile the kernel. The second option
> is to load acpi as a module.
> kldload acpi.ko
> 
> Alternatively you can put acpi_enable="YES" in /boot/loader.conf to
> automate the process. And there is no daemon like apmd for acpi. It is
> a KLM.
> 
> Regards
> S.


Ok, so apparantly this is a difference between 4.x and 5.x.  In 4.x,
there is no LKM for this, and the line to add is indeed device acpica.  

Sorry from a 4.x-junkie ;-)  

GH

-- 
:wq



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041014072731.GA31155>