On my vostro only buttons that emit WMI codes are Fn+F4/F5... I see that DSDT from DoiX already has a needed fix implemented -> Name (_UID, "DELLWMI"), but also has some unnecessary changes done to it. AMW0 should always be notified with 0xD0, ie Notify (AMW0, 0xD0), that is how it comes stock .. instead some nasty hack was applied to DSDT to patch all EC queries to return same values as stored in INF2 (like Notify (AMW0, 0xE005) and similar). I assume this has been done to allow for IOWMIFamily to work "as is" .. I have rewritten the kext to take Dell's special case into account.
Can someone revert their DSDT back to stock and please try the kext ? I have included both debug and release versions.
I don't remember if those modifications were done by me, anyway, i'll try your kext and see how it works
Edit: It works.
@To the rest, I didn't really have much time to allocate to Osx86 lately, sorry about that. I assume my package is outdated in some extent by now, so.... what would you like to see in the next release, also what new bugs have you guys found that you would like to get fixed?
I know about the damned graphic artifacts in ML 10.8.1+ they seem to be a sort of allergic reaction of ML related to something. On my machine there are some scenarios i can replicate to get them:
1. Heavy usage on the GPU side
2. Too many sleep/wake cycles without a restart between
3. Deleting cached extensions - in this scenario they will disappear after a couple of system restarts (not force restarts)
4. Restarting/powering down the laptop after a KP. The first boot will always have artifacts, they are gone after restarting