11-04-2012, 05:05 AM
(This post was last modified: 11-04-2012, 06:23 AM by TimeWalker.)
So .. here is my little research regarding sleep issues for OSX in later BIOS releases... as an example I'm looking at my vostro's bios changes.
First of all the VBIOS for HD 3000 is updated..
but swapping out newer version for the older one didn't do the justice.
Then I dug deeper, I went ahead and looked at all the modules related to sleep state (S3).. here's the result from A04 to A13:
I will try to backport the module from A04 into A13 to see if it would resolve the issue.
UPD:
Didn't help a bit ..
.. the only way we can trace this is by taking two versions .. one which hadn't the problem and the followup incremental version which has the issue (just to make sure changes to the modules are the least possible across these versions .. for me it would be comparing A04 and A07) and comparing all the modules against each other to see what has changed and what hasn't .. to determine what could impact the wake functionality in the later versions. It's [censored] of a job .. and most users here wouldn't need it anyway, but it'd be nice to trace the roots of this ...
First of all the VBIOS for HD 3000 is updated..
Code:
A04: Intel(R)Sandybridge Mobile PCI Accelerated SVGA BIOS Build Number: 2098 PC 14.34
A13: Intel(R)Sandybridge Mobile PCI Accelerated SVGA BIOS Build Number: 2104 PC 14.34
Then I dug deeper, I went ahead and looked at all the modules related to sleep state (S3).. here's the result from A04 to A13:
Code:
SystemS3ResumePei.efi - 8BCEDDD7-E285-4168-9B3F-09AF66C93FFE - Identical
SystemAcpiS3SaveDxe.efi - 2BDED685-F733-455F-A840-43A22B791FB3 - Identical
PchS3Support.efi - C7EA9787-CA0A-43B4-B1E5-25EF87391F8D - Identical
PchS3Peim.efi - 271DD6F2-54CB-45E6-8585-8C923C1AC706 - Identical
PlatformS3Save.efi - F5AC7057-5650-466E-B692-76A47223EFB0 - Identical
PlatformS3SaveDxe.efi - 51D4BACC-E70A-4136-9426-546973ED938C - Not identical! 89 diffs fount ..
UPD:
Didn't help a bit ..
.. the only way we can trace this is by taking two versions .. one which hadn't the problem and the followup incremental version which has the issue (just to make sure changes to the modules are the least possible across these versions .. for me it would be comparing A04 and A07) and comparing all the modules against each other to see what has changed and what hasn't .. to determine what could impact the wake functionality in the later versions. It's [censored] of a job .. and most users here wouldn't need it anyway, but it'd be nice to trace the roots of this ...