Mountain Lion GUIDE - 2012 Sony VAIO S Series (SVS)

[johnrey]

hello guys. there are also older dsdt files and kext/utilities from Vaio S Series 2011. with some built in screen works, other times it doesn't. also some of them don't allow to shut down or set brightness. How can we get the best out of all of them or create a custom dsdt?

thanks

here are some links:
http://www.tonymacx86.com/lion-laptop-support/61997-guide-lion-sony-vaio-s-2012-series-svs.html
http://www.tonymacx86.com/mountain-...n-lion-guide-2012-sony-vaio-s-series-svs.html
http://www.tonymacx86.com/lion-laptop-support/36995-guide-lion-sony-vaio-sa-sb-se-vpcsa-sb-se.html
http://www.tonymacx86.com/mountain-...332-guide-mac-os-10-8-sony-vaio-sa-sb-se.html

EDIT: I currently use a dsdt from 2011 Vaios and noticed that in System Information it shows a HD3000 in system info and 384mb vram available. will try out a newer dsdt.

EDIT2: I forgot to mention what guide I followed. This one: http://www.insanelymac.com/forum/topic/283613-sony-vaio-s-2012-ml-success-ivy-i5-hd-4000/

I installed Mountain Lion in Windows 8/Virtualbox on the same Laptop (some guides say 'install on a non ivy bridge machine' but I only have this). The DSDT in the guide doesn't make the resolution 1600x900 but instead 1920x1080. Changing it to 1600x900 doesn't 'zoom out' the image. HDMI works ok. I try with "HD4000PlatformId=4" because 3 let's the built in screen black (with backlight on).

 

[RehabMan]

hello guys. there are also older dsdt files and kext/utilities from Vaio S Series 2011. with some built in screen works, other times it doesn't. also some of them don't allow to shut down or set brightness. How can we get the best out of all of them or create a custom dsdt?

thanks

here are some links:
http://www.tonymacx86.com/lion-laptop-support/61997-guide-lion-sony-vaio-s-2012-series-svs.html
http://www.tonymacx86.com/mountain-...n-lion-guide-2012-sony-vaio-s-series-svs.html
http://www.tonymacx86.com/lion-laptop-support/36995-guide-lion-sony-vaio-sa-sb-se-vpcsa-sb-se.html
http://www.tonymacx86.com/mountain-...332-guide-mac-os-10-8-sony-vaio-sa-sb-se.html

EDIT: I currently use a dsdt from 2011 Vaios and noticed that in System Information it shows a HD3000 in system info and 384mb vram available. will try out a newer dsdt.

EDIT2: I forgot to mention what guide I followed. This one: http://www.insanelymac.com/forum/topic/283613-sony-vaio-s-2012-ml-success-ivy-i5-hd-4000/

It is best just to patch your own DSDT. Forget about randomly trying DSDTs made from/for other computers.

I installed Mountain Lion in Windows 8/Virtualbox on the same Laptop (some guides say 'install on a non ivy bridge machine' but I only have this). The DSDT in the guide doesn't make the resolution 1600x900 but instead 1920x1080. Changing it to 1600x900 doesn't 'zoom out' the image. HDMI works ok. I try with "HD4000PlatformId=4" because 3 let's the built in screen black (with backlight on).

DSDT patch for ig-platform-id=4 is readily available and easy to apply to DSDT. Use MaciASL to apply the following patch:

#Maintained by: RehabMan for: HP Probook 4x30s/4x40s
# 03b_1080p+HDMI.txt

#
# Use this patch if your laptop has 1600x900 or higher
# resolution screen.
# 
# For example, 47x0s (17") or 45x0s with 1080p user
# upgraded screen.
#

#   Inject HDMI info and dual-link into GFX0/IGPU   */
into method label _DSM parent_adr 0x00020000 remove_entry;
into device name_adr 0x00020000 insert
begin
Method (_DSM, 4, NotSerialized)\n
{\n
    If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }\n
    Return (Package()\n
    {\n
        "AAPL,ig-platform-id",\n
        Buffer() { 0x04, 0x00, 0x66, 0x01 },\n
        "hda-gfx",\n
        Buffer() { "onboard-1" },\n
        "AAPL00,DualLink",\n
        Buffer() { 0x01, 0x00, 0x00, 0x00 },\n
    })\n
}\n
end;

 

[johnrey]

first of all thanks for the fast response..

yes, I guess the best way is to "make" my own dsdt and make everything work step by step.

I extracted my DSDT and tried to compile with different programs but I always get errors (attachments). what am I doing wrong? I tried to figure out by comparing different DSDTs but I don't understand the code.

what found out:
- voodoo battery didn't work with/without DSDT (I tried different kexts)
- resolution/built-in lcd is okay without dsdt or with some dsdts but not all
- there is no brightness control without dsdt, but only 1 dsdt lets me control brightness
- I could get the battery info and indicator with this http://www.osx86.net/view/2732-smart_battery_no_need_dsdt.html
but it only works without dsdt so I can't control brightness

 

[RehabMan]

first of all thanks for the fast response..

yes, I guess the best way is to "make" my own dsdt and make everything work step by step.

I extracted my DSDT and tried to compile with different programs but I always get errors (attachments). what am I doing wrong?

You have one error... a common one. You will find two declarations for TNOT, remove the one that *is not* a declaration of MethodObj.

I tried to figure out by comparing different DSDTs but I don't understand the code.

Are you a programmer? If so, download the ACPI spec so you know what you're looking at.

what found out:
- voodoo battery didn't work with/without DSDT (I tried different kexts)

For battery status to work, you generally need to do DSDT edits. And the edits are not generic -- they are specific to each family of computers. A little bit of programming knowledge is necessary.

- resolution/built-in lcd is okay without dsdt or with some dsdts but not all

Don't all into the trap of using a DSDT for a different computer. Patch your own...

- there is no brightness control without dsdt, but only 1 dsdt lets me control brightness

Standard brightness patch is this:

#   Brightness control fix
into device label PNLF remove_entry;
into scope label \_SB insert
begin
Device (PNLF)\n
{\n
	Name (_HID, EisaId ("APP0002"))\n
	Name (_CID, "backlight")\n
	Name (_UID, 0x0A)\n
	Name (_STA, 0x0B)\n
}\n
end;

- I could get the battery info and indicator with this http://www.osx86.net/view/2732-smart_battery_no_need_dsdt.html
but it only works without dsdt so I can't control brightness

That one is battery manager kext + rollback AppleACPIPlatform.kext (usually a Snow Leopard version). The SL version of AppleACPIPlatform.kext doesn't have a problem reading EC registers bigger than 8-bit.. only Lion/ML have this problem, so it avoids the problem that causes us to patch DSDT (to make all EC register access 8-bit). Problem is some functions in ML don't work correctly with the SL version of AppleACPIPlatform.kext (not unexpected... you're mixing OS components from versions which are two major versions apart). In particular, Ivy Bridge power management doesn't work with the SL version of AppleACPIPlatform.kext.

 

[johnrey]

Wow! Thanks! It worked!

I removed "External (\TNOT)", then applied the HD4000 and brightness patch and compiled/saved with 0 errors and 4 warnings. To test it, I booted without 'HD4000PlatformId=4". It worked. Brightness control works now, too.

I have one question: Before this patch I made a line in my chameleon bootlist.plist for "HD4000PlatformId=4". Now I can boot without this line. Does this mean I can use a bootloader that does not have those HD4000PlatformId flags? Because now it's in the dsdt, right?

That one is battery manager kext + rollback AppleACPIPlatform.kext (usually a Snow Leopard version). The SL version of AppleACPIPlatform.kext doesn't have a problem reading EC registers bigger than 8-bit.. only Lion/ML have this problem, so it avoids the problem that causes us to patch DSDT (to make all EC register access 8-bit). Problem is some functions in ML don't work correctly with the SL version of AppleACPIPlatform.kext (not unexpected... you're mixing OS components from versions which are two major versions apart). In particular, Ivy Bridge power management doesn't work with the SL version of AppleACPIPlatform.kext.

What exactly does the power management do? Could I make use of it if I didn't use the Snow Leopard version of AppleACPIPlatform.kext but the new one from Mountain Lion?

Again thank you! I'm so happy.

 

[RehabMan]

Wow! Thanks! It worked!

I removed "External (\TNOT)", then applied the HD4000 and brightness patch and compiled/saved with 0 errors and 4 warnings. To test it, I booted without 'HD4000PlatformId=4". It worked. Brightness control works now, too.

I have one question: Before this patch I made a line in my chameleon bootlist.plist for "HD4000PlatformId=4". Now I can boot without this line. Does this mean I can use a bootloader that does not have those HD4000PlatformId flags? Because now it's in the dsdt, right?

DSDT is doing the same as your HD4000PlatformID=4 (what boot loader was that, BTW?)

So now you can use any bootloader with GraphicsEnabler=No (you don't need bootloader-based graphics injection, because your DSDT does it).

What exactly does the power management do? Could I make use of it if I didn't use the Snow Leopard version of AppleACPIPlatform.kext but the new one from Mountain Lion?

Ivy power management enables proper speedstep of your IvyBridge CPU. There is a long thread and dense first post on it here: http://www.tonymacx86.com/mountain-...tive-ivy-bridge-cpu-gpu-power-management.html

Definitely ideal to run native power management, vanilla AppleACPIPlatform.kext, and do DSDT patches to make battery status work. Best to avoid rollbacks if you can.

 

[johnrey]

DSDT is doing the same as your HD4000PlatformID=4 (what boot loader was that, BTW?)

So now you can use any bootloader with GraphicsEnabler=No (you don't need bootloader-based graphics injection, because your DSDT does it).

The bootloader is from here: http://www.insanelymac.com/forum/topic/283613-sony-vaio-s-2012-ml-success-ivy-i5-hd-4000/ .

I uploaded 2 attachments, one from Chameleon Wizard and one one from Champlist. I guess Chameleon v2.1 r2013 is the correct one because that's what I downloaded.

Ivy power management enables proper speedstep of your IvyBridge CPU. There is a long thread and dense first post on it here: http://www.tonymacx86.com/mountain-...tive-ivy-bridge-cpu-gpu-power-management.html

Definitely ideal to run native power management, vanilla AppleACPIPlatform.kext, and do DSDT patches to make battery status work. Best to avoid rollbacks if you can.

So right now Speedstep is definitely off, right? Battery is actually similar to Windows right now but with Speedstep it should be better, right?

I will read the thread and try it. Does sleep has anything to do with power management? Right now it's not working. But I didn't even install Sleep Enabler or anything to make it possible.

thanks for the help!

 

[RehabMan]

So right now Speedstep is definitely off, right? Battery is actually similar to Windows right now but with Speedstep it should be better, right?

I will read the thread and try it. Does sleep has anything to do with power management? Right now it's not working. But I didn't even install Sleep Enabler or anything to make it possible.

thanks for the help!

Probably you are using Sandy Bridge PM. I don't know if there is significant differences between Sandy PM and Ivy PM on Ivy CPU, as I don't have one so haven't been able to conduct any tests.

PM does have to do with sleep, but your sleep problem could be some other problem.

 

[johnrey]

back again. Created ssdt (I ran the script lol), copied it to Extra folder and enabled (?) it in my bootlist [DropSSDT=Yes]. Then I 'reverted' to Mountain Lion AppleACPI kext (version 1.7) and deleted the smart battery kext as it would have no use.

Are these steps correct? I noticed that my system boots up/shuts down faster than before, so I guess it's due to the power management or at least the 'original' ML appleacpi kext.

EDIT: I only shut down and booted up one time very fast but now it's similar to before.. confusing :/
EDIT 2: Sometimes it is faster, sometimes it's the same.

 

[RehabMan]

back again. Created ssdt (I ran the script lol), copied it to Extra folder and enabled (?) it in my bootlist [DropSSDT=Yes]. Then I 'reverted' to Mountain Lion AppleACPI kext (version 1.7) and deleted the smart battery kext as it would have no use.

Are these steps correct? I noticed that my system boots up/shuts down faster than before, so I guess it's due to the power management or at least the 'original' ML appleacpi kext.

Pretty much correct. To enable Ivy PM, you also must have an sysdef that is appropriate for Ivy CPU, which depends on what specific CPU you have.

Then you should verify by looking at ioreg to see if x86platformplugin is loading under CPU nodes. And run pstate checker in DPCIManager to verify pstates are being reached.