From: Michael Notforyou <sqfreak@tr...> - 2002-08-28 02:26:24
It's really OK now. The problem was that I was compiling an SMP kernel
which automatically enables Local APIC which crashes the system. Compiling
all ACPI elements into the kernel worked - as long as there was no SMP
support. Everything (except sleep and swsusp - which won't compile, long
story) works. I have easy battery ratings.
Thanks for your help!
At 01:01 PM 8/27/2002 +0100, you wrote:
>Michael Notforyou [sqfreak@...] wrote:
> > I think I need to patch my DSDT as well. I have no battery rating with the
> > unpatched kernel (meaning the SourceForge ACPI not applied). Nor do I have
> > performance.
> > The command you gave me to export my DSDT did nothing but spit out garbage
> > and corrupt my terminal display.
>Sounds like you forgot to put the redirect which would cause it to get
>saved to a file the "> dsdt.txt" was part of the command. It's not junk
>it's just 'compiled' - computer readable, rather than source - human
>You need to use pacpidump on that file and then use iasl to find errors
>and fix them.
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.19/kernel/drivers/acpi/MODULENAME.o
> > depmod: acpi_ut_debug_print
> > depmod: acpi_ut_value_exit
> > depmod: acpi_ut_exit
> > depmod: acpi_ut_trace
>It's possible there is a problem with the build for making these things
>as modules, I have only ever made them as built-in because I can't think
>of a time when I would ever want them not to be loaded.
>Software Development Manager,
>ClaraNET Ltd. Tel 020 7903 3000
>The faster we go, the rounder we get.
> -- The Grateful Dead
"My God, I'm full of stars!"
Darmok and Jalad at Tanagra!
Get latest updates about Open Source Projects, Conferences and News.