Contribute
Register

[Guide] Mountain Lion Installation for Asus Vivobook S200, X202, S400...

Status
Not open for further replies.
Here is some information for those who want to patch your own DSDT with MaciASL, these are the patches that I used in my own DSDT:

-The first patch you need is the DTGP patch. This can be found in the default Sourceforge repository in MaciASL. However, Clover can also patch DTGP on the fly so you can do it that way if you prefer as well.

The following patches can be found in Rehabman’s MaciASL repo:
-HPET patch (Clover can also autopatch this)
-RTC patch (Clover can’t do this DSDT patch, but it can autopatch the AppleRTC kext)
-Asus-N55SL/Vivobook Battery Patch - This allows the battery to show it’s correct percentage without having to use the AppleACPIPlatform.kext from Snow Leopard (which will disable Ivy Bridge GPU power management). You still need ACPIBatteryManager.kext for this to work.
-Rename all instances of GFX0 to IGPU - This will enable proper graphics power management, provided you are using a vanilla AppleACPIPlatform.kext.
-Audio Layout 12 patch (change 12 to 28)
-IRQ patch
-Lid sleep patch here: http://www.tonymacx86.com/mountain-...us-vivobook-s200-x202-s400-13.html#post652559 (thanks to dpg12 for originally posting it and fvl for converting it into MaciASL patch format)


IMPORTANT:
Note that if you have MaciASL automatically extract your DSDT and you are using Clover's autopatch features, it will extract the one that was autopatched by Clover. Currently, the easiest way to get a fresh, unpatched DSDT is to boot into Clover at press F4 at the menu. When you boot into OS X, mount your EFI partition and you will see a bunch of .aml files in EFI/Clover/ACPI/origin. Edit the DSDT.aml you find there, and place it in the EFI/Clover/ACPI/patched folder when you are finished.
 
Here is some information for those who want to patch your own DSDT with MaciASL, these are the patches that I used in my own DSDT:

-The first patch you need is the DTGP patch. This can be found in the default Sourceforge repository in MaciASL. However, Clover can also patch DTGP on the fly so you can do it that way if you prefer as well.

The following patches can be found in Rehabman’s MaciASL repo:
-HPET patch (Clover can also autopatch this)
-RTC patch (Clover can’t do this DSDT patch, but it can autopatch the AppleRTC kext)
-Asus-N55SL/Vivobook Battery Patch - This allows the battery to show it’s correct percentage without having to use the AppleACPIPlatform.kext from Snow Leopard (which will disable Ivy Bridge GPU power management). You still need ACPIBatteryManager.kext for this to work.
-Rename all instances of GFX0 to IGPU - This will enable proper graphics power management, provided you are using a vanilla AppleACPIPlatform.kext.
-Audio Layout 12 patch (change 12 to 28)
-IRQ patch
-Lid sleep patch here: http://www.tonymacx86.com/mountain-...us-vivobook-s200-x202-s400-13.html#post652559 (thanks to dpg12 for originally posting it and fvl for converting it into MaciASL patch format)


IMPORTANT:
Note that if you have MaciASL automatically extract your DSDT and you are using Clover's autopatch features, it will extract the one that was autopatched by Clover. Currently, the easiest way to get a fresh, unpatched DSDT is to boot into Clover at press F4 at the menu. When you boot into OS X, mount your EFI partition and you will see a bunch of .aml files in EFI/Clover/ACPI/origin. Edit the DSDT.aml you find there, and place it in the EFI/Clover/ACPI/patched folder when you are finished.

I don't think you need DTGP for any of the patches you mention above. My patch repo certainly doesn't need it.
 
Here is some information for those who want to patch your own DSDT with MaciASL, these are the patches that I used in my own DSDT:

-The first patch you need is the DTGP patch. This can be found in the default Sourceforge repository in MaciASL. However, Clover can also patch DTGP on the fly so you can do it that way if you prefer as well.

The following patches can be found in Rehabman’s MaciASL repo:
-HPET patch (Clover can also autopatch this)
-RTC patch (Clover can’t do this DSDT patch, but it can autopatch the AppleRTC kext)
-Asus-N55SL/Vivobook Battery Patch - This allows the battery to show it’s correct percentage without having to use the AppleACPIPlatform.kext from Snow Leopard (which will disable Ivy Bridge GPU power management). You still need ACPIBatteryManager.kext for this to work.
-Rename all instances of GFX0 to IGPU - This will enable proper graphics power management, provided you are using a vanilla AppleACPIPlatform.kext.
-Audio Layout 12 patch (change 12 to 28)
-IRQ patch
-Lid sleep patch here: http://www.tonymacx86.com/mountain-...us-vivobook-s200-x202-s400-13.html#post652559 (thanks to dpg12 for originally posting it and fvl for converting it into MaciASL patch format)


IMPORTANT:
Note that if you have MaciASL automatically extract your DSDT and you are using Clover's autopatch features, it will extract the one that was autopatched by Clover. Currently, the easiest way to get a fresh, unpatched DSDT is to boot into Clover at press F4 at the menu. When you boot into OS X, mount your EFI partition and you will see a bunch of .aml files in EFI/Clover/ACPI/origin. Edit the DSDT.aml you find there, and place it in the EFI/Clover/ACPI/patched folder when you are finished.

Sorry I'm kind of new at using DSDTs...
First off, I'm using the old Clover. I tried upgrading and I didn't know how to configure it so it would boot (if anyone could help me with this that'd be great!)
Second, when you say press F4, does that apply to the old Clover (the original one that was posted) too?
What exactly is the advantage of a DSDT?
 
Here's my latest clover config: http://d-h.st/Fgk

As far as Fn keys go, I have those all configured using the elantouchpad kext. so yes all of them work for me. What doesn't work is F1, F2, F3, etc... not that I have ever needed to use them in OS X so I switched it to not need the Fn key pressed to get those functions. Take a look at the kext and how I have it configured: http://d-h.st/zKh

could you reupload your config please? the link is broken :p
 
Sorry I'm kind of new at using DSDTs...
First off, I'm using the old Clover. I tried upgrading and I didn't know how to configure it so it would boot (if anyone could help me with this that'd be great!)
Second, when you say press F4, does that apply to the old Clover (the original one that was posted) too?
What exactly is the advantage of a DSDT?
Yes, it works with the old clover. The advantage of a dsdt is e ability to apply fixes such as the ones I posted above. It makes for a hack that runs a little bit more like a real Mac. For booting the new clover, download the installer, do a custom installation to install it with the uefi install, (make sure you check some uefi drivers during the installation, check all of them except csmvideo and lowmemfix). Then mount the efi partition (should already be mounted after the install, if not just use efi clover tools en to mount it), and add the config.plist to the /efi/clover folder and the kexts you are using to the efi/clover/kexts/10.9 folder. That should get it to boot.

I would recommend trying this on a USB drive first before you install it on your internal drive's efi partition.
 
Yes, it works with the old clover. The advantage of a dsdt is e ability to apply fixes such as the ones I posted above. It makes for a hack that runs a little bit more like a real Mac. For booting the new clover, download the installer, do a custom installation to install it with the uefi install, (make sure you check some uefi drivers during the installation, check all of them except csmvideo and lowmemfix). Then mount the efi partition (should already be mounted after the install, if not just use efi clover tools en to mount it), and add the config.plist to the /efi/clover folder and the kexts you are using to the efi/clover/kexts/10.9 folder. That should get it to boot.

I would recommend trying this on a USB drive first before you install it on your internal drive's efi partition.

I got it to finally boot! But after verbose mode, the screen turns black...I'm pretty sure it booted fully because if I press the space bar it makes a sound. What settings do I have to tweak in Clover?
 
I got it to finally boot! But after verbose mode, the screen turns black...I'm pretty sure it booted fully because if I press the space bar it makes a sound. What settings do I have to tweak in Clover?
I'm not sure why that happened, it should just work... Were you using the same config before as the one in the op? Perhaps someone else can be of more help. Can you boot with -x?

Edit: try removing the resolution setting in the config.plist. the s400 display might not support it. I thought clover was able to detect out regardless, but maybe I was wrong.
 
I'm not sure why that happened, it should just work... Were you using the same config before as the one in the op? Perhaps someone else can be of more help. Can you boot with -x?

Edit: try removing the resolution setting in the config.plist. the s400 display might not support it. I thought clover was able to detect out regardless, but maybe I was wrong.

There is no resolution setting in the config :p But I didn't edit any settings in Clover, so it doesn't match the one in the OP. I don't know what settings I have to change because the config layout isn't the same anymore. Could you post your config.plist ?
 
There is no resolution setting in the config :p But I didn't edit any settings in Clover, so it doesn't match the one in the OP. I don't know what settings I have to change because the config layout isn't the same anymore. Could you post your config.plist ?
I did a few posts back, I thought that was what you used. So you didn't use any config at all when you booted up and got the blank screen? Sounds like it just detected the graphics improperly. Clover does it's best to figure out the best settings on it's own, but sometimes it doesn't get it right, especially when you're dealing with something like hd4000. Try my config that I posted and see if that helps.
 
I did a few posts back, I thought that was what you used. So you didn't use any config at all when you booted up and got the blank screen? Sounds like it just detected the graphics improperly. Clover does it's best to figure out the best settings on it's own, but sometimes it doesn't get it right, especially when you're dealing with something like hd4000. Try my config that I posted and see if that helps.

Oh sorry! Didn't see that. It works perfectly now, thanks! Just btw I didn't have to change anything :D
 
Status
Not open for further replies.
Back
Top