Re: Custom DSDT--The Debian Way?
On Mon, Dec 20, 2004 at 11:19:58PM +1100, Daniel Pittman wrote:
> Date: Mon, 20 Dec 2004 23:19:58 +1100
> From: Daniel Pittman <firstname.lastname@example.org>
> To: email@example.com
> Subject: Re: Custom DSDT--The Debian Way?
> On 20 Dec 2004, David Goodenough wrote:
> > On Monday 20 December 2004 04:24, Ridge Chittenden wrote:
> >> Hello all,
> >> The DSDT on my Dell Inspiron 300m seems buggy--KDE tells me I "appear
> >> to have a partial ACPI installantion," and I get a bunch of ACPI
> >> errors on bootup.
> >> But there are a bunch of different methods listed at the ACPI
> >> project: A kernel patch that statically links the custom DSDT in,
> >> another patch that allows the kernel to load a custom DSDT in an
> >> initrd. (N.B.: These patches appear to be against a vanilla
> >> kernel...)
> >> So what's The Debian Way to do it? What do other folks do?
> > I asked a very similar question a couple of weeks ago, and got the
> > answer that there was no Debian way, and that the ACPI group preferred
> > way is to statically link the customer DSDT.
> > I have to say that I think this is the wrong choice, as the initrd
> > choice gives the option of using a stock kernel, which the link in
> > choice does not.
> Last time I checked, using the initrd hack prevented you using an initrd
> to boot with. This is incompatible with both future kernel plans where
> early boot-time code like partition detection move to an initrd, and
> with Debian kernels -- they use an initrd by default.
I've used initrd patch from http://gaugusch.at/kernel.shtml applied on debian
kernel 2.4.27 without any problem. Didn't prevent me from using initrd