Hi Thomas,
thanks for your prompt reply!
dsdt.dsl 1657: Field (IO, ByteAcc, Lock, Preserve)
Error 4094 - ^ parse error,
unexpected PARSEOP_IO, expecting error or PARSEOP_NAMESEG or
PARSEOP_NAMESTRING
You can workaround by renaming the field to XIO...
I thought of that for a microsecond, but was to anxious to rename things
I do not understand ;-)
For these object not exist messages:
dsdt.dsl 1929: Store (Arg0, DAT0)
Error 4062 - Object does not exist ^
(DAT0)
You need to add addtional external (DAT0) statements at the beginning of
your DSDT.
These variables are probably defined in SSDT. I think you have to
replace DAT0 with the whole path e.g. \_SB.xy.DAT0.
Sorry, but what is 'xy'?
The kernel sometimes (at boot and during operation) says:
ACPI-0142: *** Error: Store into Alias - should never happen
ACPI-1172: *** Error: Method execution failed
[\_SB_.PCI0.SBRG.EC0_._Q0C] (Node c14b4c20), AE_AML_INTERNAL
This sounds unrelated to your DSDT errors, but sever. Robert extended
the Alias stuff some months ago, maybe something slipped in...
Best is you point us to the whole acpidump and whole dmesg output.
OK, will do that when I'm on my laptop again; may take some days.
BTW, does it hurt that I'm not using the latest kernel?
Paul
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
