I've uploaded an error log to the bugzilla [1] and have some questions that probably are more suited for a mailinglist? At first glance, the errors are identical to the 2010 acpi compiler. A few things I do not understand however. This board is only a few months old. The bios could be older, but more then a year hardly? Even the 'base' bits. I'd reccon one of the new compilers would be long available? (I know, OEM's don't like to upgrade their toolkits etc. *sigh* Also, the 20051117 iasl only supports ACPI Specification Rev 3.0, I'd guess it would support acpi 4.0a by now? (I think i found somewhere it only does 2.0 actually and I guess acpi is more of a laptop thing with the fancy stuff). Lastly, if I get 130 errors and but still a binary as a result how can that possibly even work? Would they even use this code 'as is' in production stuff? I suppose a DSDT isn't that important for a Desktop but from the way I see how buggy the uefi-bios is (for example it is extremely slow just post-ing with USB connected, maybe related to this?) How did this get past QA with so many errors, not even warnings. [1] https://bugzilla.kernel.org/show_bug.cgi?id=42502 Lastly, as Robert pointed out; according to On 09/08/11 00:00, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=42502 > > > Robert Moore <Robert.Moore@xxxxxxxxx> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |Robert.Moore@xxxxxxxxx > > > > > --- Comment #9 from Robert Moore <Robert.Moore@xxxxxxxxx> 2011-09-07 22:00:05 --- > * OEM Table ID "A M I" > * OEM Revision 0x00000000 (0) > * Compiler ID "INTL" > * Compiler Version 0x20051117 (537202967) > > This is a version of iASL from 2005. At some point, some of the code in this > DSDT was made illegal, and the compiler now reflects that. > > Namely, this code: > > Device (SATA) > { > Name (_ADR, 0x00110000) > If (LEqual (STCL, 0x0101)) > { > > The "If" is an "executable" opcode that appears outside of a control method. > This is now illegal ASL code. > > Typically, the fix is to move this code under _SB_._INI, this method gets > executed at table load time. But it's not always real simple to do this. > -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html