Date: Fri, 05 Jul 2002 16:01:08 +0900 From: Takanori Watanabe <takawata@axe-inc.co.jp> To: Alex Zepeda <zipzippy@sonic.net> Cc: current@freebsd.org Subject: Re: ACPI woes again.. Message-ID: <200207050700.QAA26015@axe-inc.co.jp> In-Reply-To: Your message of "Thu, 04 Jul 2002 23:50:52 MST." <20020705065052.GA412@blarf.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20020705065052.GA412@blarf.homeip.net>, Alex Zepeda wrote: >So thanks to a rather lacking support team at Epox (uh hey, reset your >BIOS settings it should be a-okay) and a very helpful Ducrot Bruno.. it >was determined that my DSDT was coded haphazardly. A few nips and tucks, >and a hardcoded table later, my kernel booted again (where before it hung >after probing a thermal zone). > >This worked all great, as I'd just patch the kernel after every cvsup. > >'Cept now that the ACPI code (rather tbget.c) has been restructured >enough, I'm not quite sure how to get a new kernel booted. > >Anyone else out there running an EPoX KP6-BS with -current? > >Should I just go about disabling ACPI (in favor of APM?)? > We already have a way to use your own bytecode without recompiling. Simply put your AML file to /boot/acpi_dsdt.aml and add 'acpi_dsdt_load="YES" to your /boot/loader.conf (Other necessary setting exist in /boot/default/loader.conf) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200207050700.QAA26015>