Skinny Extra Sweet Ubuntu
Iasl has an error limit of 200 before it just gives up. If there was an error on the 3rd line out of a possible of 10,000-11,000 lines, then everything below that 3rd line would also show up as an error. Crazy isn't it? What is the first error in the list?Originally Posted by litspliff
A Carafe of Ubuntu
Of course, the file is already in my dropbox and all of my computersMy advice is to keep a copy of the fixed DSDT.aml in a safe place. The DSDT shipped with your BIOS is broken and will never change. If you ever do a clean install of any Linux/Mac OS, then you will have to reuse the custom DSDT. You can use it for any distro.
I'll also try to understand what you did ...
Diego
Skinny Extra Sweet Ubuntu
The _GLK and _WAK errors are well documented. The _DOD section on line 1122 is where I did the custom work. You can compare it with the original.
A Carafe of Ubuntu
this is the first page when i
.... | less
Code:Intel ACPI Component Architecture ASL Optimizing Compiler version 20081204 [Jan 10 2009] Copyright (C) 2000 - 2008 Intel Corporation Supports ACPI Specification Revision 3.0a ACPI Error (nsaccess-0528): ACPI path has too many parent prefixes (^) - reached beyond root node [20081204] Maximum error count (200) exceeded /home/-user-/dsdt.dsl 21: External (^Z00G, IntObj) Error 4014 - From ACPI CA Subsystem ^ (AE_NOT_FOUND Failure from lookup %s ) /home/-user-/dsdt.dsl 24: Name (RBRF, 0x01) Error 4063 - Object does not exist ^ (RBRF) /home/-user-/dsdt.dsl 25: Name (L10F, 0x00) Error 4063 - Object does not exist ^ (L10F) /home/-user-/dsdt.dsl 26: Name (SCIC, 0x00) Error 4063 - Object does not exist ^ (SCIC) :
LOG - slauce.com/log
MUSIC - noisemachine.org
WORK - dynatron.org
STORE - dynatron.org/store
Skinny Extra Sweet Ubuntu
Delete the first two lines in your dsdt.dsl file, save and try it again.
A Carafe of Ubuntu
more specific please (the first two lines are commented, after the comments, the first two lines seem important)....
are you refering to the definition block, the External, or the name lines?Code:DefinitionBlock ("dsdt.aml", "DSDT", 1, "NVIDIA", "MCP67", 0x06040000) { External (^Z00G, IntObj) External (\_PR_.CPU0._PPC, IntObj) Name (RBRF, 0x01) Name (L10F, 0x00) Name (SCIC, 0x00) Name (SCID, 0x00)
LOG - slauce.com/log
MUSIC - noisemachine.org
WORK - dynatron.org
STORE - dynatron.org/store
A Carafe of Ubuntu
not sure if this is worth mentioning, but i'm running 64-bit ubuntu jaunty on my laptop. (F700 presario)
LOG - slauce.com/log
MUSIC - noisemachine.org
WORK - dynatron.org
STORE - dynatron.org/store
Skinny Extra Sweet Ubuntu
It is hard to say without seeing the file. Send me a copy of the dsdt.dsl file and I can either fix it, or help walk you through it if you would rather do it. 32bit vs 64bit doesn't matter with the DSDT.
A Carafe of Ubuntu
67GTA,
I found mine to be interesting.
It does not have any errors, but it does have some warnings and optimizations. Where the surprise came for me, is that my system is from a linux OEM. They have atleast branded the BIOS, I would have thought they would not let something like this slip bye. Since you seem to be the resident expert: If you see something in there that concerns you, I will pass it along to them.
Code:Intel ACPI Component Architecture ASL Optimizing Compiler version 20081204 [Jan 10 2009] Copyright (C) 2000 - 2008 Intel Corporation Supports ACPI Specification Revision 3.0a /home/scotty/dsdt.dsl 2033: Method (_BQC, 0, NotSerialized) Warning 1087 - Not all control paths return a value ^ (_BQC) /home/scotty/dsdt.dsl 2033: Method (_BQC, 0, NotSerialized) Warning 1080 - Reserved method must return a value ^ (_BQC) /home/scotty/dsdt.dsl 2581: Or (TMOR, TMPV) Warning 1105 - Result is not used, operator has no effect ^ /home/scotty/dsdt.dsl 5259: Or (TMOR, TMPV) Warning 1105 - Result is not used, operator has no effect ^ ASL Input: /home/scotty/dsdt.dsl - 6599 lines, 209268 bytes, 2418 keywords AML Output: /home/scotty/dsdt.aml - 22137 bytes, 686 named objects, 1732 executable opcodes Compilation complete. 0 Errors, 4 Warnings, 0 Remarks, 41 Optimizations
Socialism is a philosophy of failure, the creed of ignorance, and the gospel of envy, its inherent virtue is the equal sharing of misery - Winston Churchill
Skinny Extra Sweet Ubuntu
Most people don't dig this deep(LOL) You actually have two warnings. The first two are related. Fix the first and the second fixes it's self.
Yours is fine. IASL is open source and an industry standard. It doesn't let anything get by it. It is just complaining because there is not a "null" value. That means there is not a value to tell the kernel what to do if there is no brightness level returned. I know that seems silly, but the IASL compiler is that precise. The third and fourth warnings are also meaningless. The two lines it is referencing has extra values pertaining to Windows that are not usable to Linux, but won't hurt anything by being there. The kernel just ignores them. In your case there would not be any ACPI errors for anyone to follow. I fixed them, but it's probably not worth the trouble to keep a custom DSDT on this machine. We are just simply are making IASL happyCode:From the ACPI manual... _BQC Brightness Query Current – returns the current display brightness level.You can see the optimizations made by using
dsdt.aml.zipCode:iasl -tc -vo
Posting Permissions
Adv Reply
Bookmarks