From: Duarte Silva <duartejcsilva@gmail.com>
To: linux-acpi@vger.kernel.org
Subject: Re: need help with buggy dsdt
Date: Mon, 10 Nov 2008 12:01:36 +0000 [thread overview]
Message-ID: <200811101201.36488.duartejcsilva@gmail.com> (raw)
In-Reply-To: <491813CF.3070603@gmail.com>
It means that you have unresolved externals in the DSDT. Something like this
External (^CPU0._PPC) should be removed.
I had that problem on my DSDT too. But take care that if the same error doesnt
occur during the initialization of the kernel (something like AE_NOT_FOUND
Failure from lookup %s should be present in the kernel log) you shouldnt
remove it ->> I guess <<-.
On Monday 10 November 2008 10:58:23 M. I. Veken wrote:
> i need help with my (buggy) dsdt:
>
> i get these errors when trying to recompile (iasl -tc dsdt.dsl):
> paste.ubuntu.com/69766/
>
> here is my dsdt.dsl:
> paste.ubuntu.com/69765/
>
> thank you in advance for the help
>
> PS sry for the links but i don't know how to manage that..
>
> > it does not like your external referencies. remove them and you are down
> > to 16 errors. proper externals could be acquired from SSDTs nearby...
>
> i don't understand that sry, could you explain please? why doesn't it like
> my links? what's that "down to 16 errors" about? what are SSDTs?
> sry for my noobishness:|
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-10 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 10:58 need help with buggy dsdt M. I. Veken
2008-11-10 12:01 ` Duarte Silva [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-09 21:50 M. I. Veken
2008-11-09 22:27 ` Alexey Starikovskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200811101201.36488.duartejcsilva@gmail.com \
--to=duartejcsilva@gmail.com \
--cc=linux-acpi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.