DragonFly BSD
DragonFly kernel List (threaded) for 2004-05
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: New DFly ISO CD image available 20040506

From: YONETANI Tomokazu <qhwt+dragonfly-kernel@xxxxxxxxxx>
Date: Sat, 8 May 2004 12:34:16 +0900

On Fri, May 07, 2004 at 10:50:35PM -0400, Rahul Siddharthan wrote:
> YONETANI Tomokazu said on May  8, 2004 at 11:37:06:
> > > My module attempt was actually with the patch posted to submit@ by
> > > Tomokazu Yonetani on Apr 29; perhaps that was responsible for the
> > > hangs, I should have backed it out.
> > 
> > In that case, just type hint.acpi.0.disabled="1" in the boot loader
> > prompt and it should prevent acpi module from being loaded.
> One can also disable it from the boot loader.  But now I'm running a
> kernel with acpica5 built in.
> > And I have a question to others: does i386 UP kernel even compile
> > without the "gross hack" to /sys/i386/i386/machdep.c, when you
> > add `device acpica5' to your kernel config file?
> Yes, it compiled fine with vanilla kernel sources.

Hmm, when you compile acpica5 as module(from untouched sources),
and ${MACHINE} == "i386", madt.c is added to SRCS and that was
why I had to patch /sys/i386/i386/machdep.c, but somehow I've been
believing that I need it even when the acpica5 is compiled in the

Thanks for testing my patch. Oh, and you can remove acpi_toshiba.ko
from /modules; you probably don't need it unless you're using Toshiba

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]