He's right, the DSDT gets patched by the BIOS before the OS uses it, so you need to extract it from a running OS.
Right. But at how many positions? AFAIK it is only the "OperationRegion" that is directly dynamically related to the amount of RAM.
(..)
OperationRegion (SMOD, SystemMemory, 0x000FF840, One)
(..)
OperationRegion (RCRB, SystemMemory, 0xFED1C000, 0x4000)
(..)
OperationRegion (ELKM, SystemMemory, 0x000FFFEA, One)
(..)
OperationRegion (EXTM, SystemMemory, 0x000FF830, 0x10)
(..)
As I don't have access to my machine right now: I am wondering if the 0x4000 is the total amount of RAM of my machine? And the masterquestion: does anyone know how the OperationRegion gets calculated - means: can we make dsdt.aml files universal for different amounts of RAM (with same BIOS rev.) by patching the OperationRegion - means by letting Chameleon patch the OperationRegion dynamically at boot time?
And would it make sense to invest time in such a question? Means: are the BIOS/MoBo manufacturers going to do better jobs? Are they facing this as an issue for impact on sales? We should tell them by not buying that crap
So is there any BIOS/MoBo company doing a well job with their ACPI implementations?