Jump to content

ASUS A56CM - K56CM - TUTORIAL ML 10.8.2


Piuma
 Share

244 posts in this topic

Recommended Posts

Thank you all in this post. Here is the tutorial (sorry for bad english!)

 

 

 

ASUS A56CM - K56CM - TUTORIAL MOUNTAIN LION 10.8.2

  1. Go into the bios and set the following parameters:


    • Fast Boot: Disabled
    • Boot: Launch CSM
    • USB Legacy Enabled
    • XHCI: Disabled
    • Secure Boot Control: Disabled

NOT TOUCH "Intel Anti-Theft"

  1. Install the operating system:


    • Personally I have tried with different images on USB.
      I tried it with a stick created from a legally acquired copy of ML but was not able to complete the installation.
    • Install with this will lead to the infamous "boot0: error"


    • After preparing the usb, start the computer with the usb inserted.
    • When you start the PC, when the ASUS logo appears, press ESC from the menu that appears choose to start from USB.
    • Once in the installation process, before installing, go up to "Utilities" and select "Disk Utility". At this point you need to partition your drive (a partition if you want to install OSX only, two or more partitions if you want to make multiboot with windows or linux).
    • Important: before partitioning options click on the button below and select MASTER BOOT RECORD as Partition Map.
    • Install

  1. Configure the operating system:


    • After installation the first reboot the PC will crash if you try to enter the operating system normally, then start again from the flash installation but without starting the installation. When you start the PC, when the ASUS logo appears, press ESC from the menu that appears choose to boot from USB key, you will see a second menu, select the partition where you installed OSX and start with bootflag-x (safe mode)
    • Enter the data for the creation of your user account, but skip the internet configuration, otherwise the system will reboot.
    • Now is the time to install the latest version of Chameleon or Chimera bootloader and FakeSMC.
    • Install Kext Drop or Kext Wizard and install all the kext that you find in the attached zip.
    • Once installed you restart, go to the Finder, go into your disk on which you installed OSX (if not stated you can get in using "disk utility").
    • Here should be 5 folders, we are interested in the one called "Extra". If the folder "Extra" does not exist, create it manually and drop in all the files you will find in the attached zip.
    • Check that you have not previously installed the kext nullCPU ... and if you did, delete it!
    • Now open the terminal and type "sudo-s" (without the quotes). Ask for the password you just chose, write (will not appear anything but have faith you are writing). Now paste this string of commands in the terminal and pressed enter:

rm - rf / System / Library / Extensions / GeForce. kext

rm - rf / System / Library / Extensions / GeForceGA. plugin

rm - rf / System / Library / Extensions / GeForceGLDriver. bundle

rm - rf / System / Library / Extensions / GeForceVADriver. bundle

rm - rf / System / Library / Extensions / NVDAGF100Hal. kext

rm - rf / System / Library / Extensions / NVDAGK100Hal. kext

rm - rf / System / Library / Extensions / NVDANV50Hal. kext

rm - rf / System / Library / Extensions / NVDAResman. kext

rm - rf / System / Library / Extensions / NVDAStartup. kext


    • At this point, repair permissions (for luck!) And reboot.

At this point could be the notorious problem "boot0: error", for the resolution of which follow this guide:

 

http://www.insanelym... # entry1873521

 

If update version 10.8.2 will then need to restart via usb in safe mode (-x) and manually reset the two kext that you will find in the zip. Install with Kext Drop. If Kernel Panic, restart in safe mode and reinstall with kext wizard and repair permissions.

You will also need to re-open the terminal and repeat step colored blue in the guide.

Reboot and cross your fingers.

 

At the moment it is impossible to operate the wifi, maybe in the future, I recommend buying a usb wifi (first confirm that it is compatible).

The FN keys do not work, at least not all.

Perhaps the most picky, like me, will notice that the screen is darker, there is a trick to do to get the maximum brightness. Basically, do not know why, if the screen goes to sleep and then back here the brightness is magically become normal. So I recommend to set up a corner of the screen to "put the monitor to sleep" when you move the mouse. So every time you can up brightness in a second.

There may be various other problems during the process of installation and configuration too long to explain. If you have trouble write me if I can help you, good job ;)

 

TNX TO LEJENK & TONIO1987

K56CM.zip

Edited by Gringo Vermelho
References to warez removed.
  • Like 3
Link to comment
Share on other sites

For all those who don't yet know our position about tonymac, and your [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] software, your Forun, your Toll, thank you for reading this and this. p.s : pls read the forum rules !!!

InsanelyMac doesn't support tonymac's tools.

Please edit your post

 

Thanks!!!!

  • Like 2
Link to comment
Share on other sites

Hi,

 

For the bootloader, i can recommend Enoch, a branch of Chameleon.

One of the problems is definitely the combination HD4000 + GT635M, but probably not only, as "GraphicsEnabler = No" does not work. Only safe mode.

 

 

After installation, boot into safe mode and delete al the Nvidia related kexts. Open up terminal and give in the following commands:

 

rm -rf /System/Library/Extensions/GeForce.kext
rm -rf /System/Library/Extensions/GeForceGA.plugin
rm -rf /System/Library/Extensions/GeForceGLDriver.bundle
rm -rf /System/Library/Extensions/GeForceVADriver.bundle
rm -rf /System/Library/Extensions/NVDAGF100Hal.kext
rm -rf /System/Library/Extensions/NVDAGK100Hal.kext
rm -rf /System/Library/Extensions/NVDANV50Hal.kext
rm -rf /System/Library/Extensions/NVDAResman.kext
rm -rf /System/Library/Extensions/NVDAStartup.kext

If a kext is not found, continue with the next one, the above lines also include the kext that need to be removed after updating to 10.8.2.

 

 

Next open org.chameleon.boot.plist and add the efi string for the HD4000:

<key>device-properties</key><string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000004006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d32</string>

 

If this string does not work, so your screen just turns black when the OS X login window should appear, then you are on the right track. You just need to try another EFI string, and boot with GraphicsEnabler=No, else the Nvidia will conflict.

  • Like 2
Link to comment
Share on other sites

Arrived on the desktop with the safe mode I proceed to install #######, of course selecting the right kexts and the Chimera bootloader.

Upon reboot bootloader is not even loaded and the computer just turned on, it shows two lines that read:

 

Boot0: test

Boot0: error

 

It seems as if the hard drive is not seen, and this problem occurs in both ways: with map MBR and GUID partition map.

Only at that point is to start with the usb stick installation that is recognized (as opposed to the internal hard disk).

The problem is that even through the usb installation only access to the system is via safe mode.

 

Reading through comments on kexts.com I read about someone who thanked him for the release of a kext in the operation of the battery and said it works perfectly on his S56CM. So installation is possible on these machines, but after a month of frustrated tentative start to wonder HOW IT IS POSSIBLE!

 

Any help will be greatly appreciated. If I will solve the problem I will write a short guide in English to leave to help desperate future.

 

Matthew

 

Which proves, for the millionth time, that tonymac's beasts cause more problems than they solve.

  • Like 3
Link to comment
Share on other sites

I do not want to defend anyone, but I think that the problem of boot0 is related to an incompatibility between the bootloader and some types of harddisk. I'm doing a new installation test right now, I will update the topic soon.

 

Which proves, for the millionth time, that tonymac's beasts cause more problems than they solve.

Link to comment
Share on other sites

I managed to solve the problem of boot0 following this fix:

http://www.macbreaker.com/2012/02/hackintosh-boot0-error.html

 

I tried to delete the kext nvidia as lejenk suggested. But I had to delete throwing them in the trash and emptying. Because through the terminal it told me that I hadn't permission to do so.

 

I also added the string for the HD4000 but I can't still access.

 

I can try with other string? And where i can find them?

Link to comment
Share on other sites

ig-platform-id: 01660000, Stolen RAM for FB: 96MB, Pipes: 3, Ports: 4, FBMem: 3

Code:

<key>device-properties</key>

<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000000006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

ig-platform-id: 01660001, Stolen RAM for FB: 96MB, Pipes: 3, Ports: 4, FBMem: 3

Code:

<key>device-properties</key>

<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000001006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

ig-platform-id: 01660002, Stolen RAM for FB: 64MB, Pipes: 3, Ports: 1, FBMem: 1

Code:

<key>device-properties</key>

<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000002006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

ig-platform-id: 01660003, Stolen RAM for FB: 64MB, Pipes: 2, Ports: 2, FBMem: 2

Code:

<key>device-properties</key>

<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000003006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

ig-platform-id: 01660004, Stolen RAM for FB: 32MB, Pipes: 3, Ports: 1, FBMem: 1

Code:

<key>device-properties</key>

<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000004006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

ig-platform-id: 01660008, Stolen RAM for FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3

Code:

<key>device-properties</key>

<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000008006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

ig-platform-id: 01660009, Stolen RAM for FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3

Code:

<key>device-properties</key>

<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000009006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

ig-platform-id: 0166000A, Stolen RAM for FB: 32MB, Pipes: 2, Ports: 3, FBMem: 2

Code:

<key>device-properties</key>

<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d00690064000000080000000a006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

ig-platform-id: 0166000B, Stolen RAM for FB: 32MB, Pipes: 2, Ports: 3, FBMem: 2

Code:

<key>device-properties</key>

<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d00690064000000080000000b006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

ig-platform-id: 01620005, Stolen RAM for FB: 32MB, Pipes: 2, Ports: 3, FBMem: 2

Code:

<key>device-properties</key>

<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000005006201140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

  • Like 1
Link to comment
Share on other sites

I tried to delete the kext nvidia as lejenk suggested. But I had to delete throwing them in the trash and emptying. Because through the terminal it told me that I hadn't permission to do so.

 

My bad, forgot sudo -s before the other commands. That command gives you root access.

Link to comment
Share on other sites

Very Tnx Lejenk. Now i'll try with a new install because now i can't reach desktop even with -x

What do you recommend to install after the OS?

 

And in what order?

 

 

Is a good order?

- Operating system

- fakesmc

- nullcpu

- enoch

- String for HD4000

- Try with a reboot

Link to comment
Share on other sites

Install the OS, reboot, perhaps boot with -x, install the boot loader, after that the fakesmc and nullcpu, use a utility like kext wizard, or kext drop. Best leave the string out first and don't forget to delete the nvidia drivers. see if you reach the desktop, boot with -v.

Link to comment
Share on other sites

Lejenk, a moderator on another forum wrote me about situation:

 

What do you think about it?

 

---

Hi Matthew,

dual graphics laptops have been reported not working with OSX by many users, so I would start there.

If you can´t disable NV in BIOS, you are out of luck, I´m afraid. HD 4000 alone should work, of course.

 

Most people had success installing ML with Conti´s myHack, as some steps are automated that way.

You can of course prepare a thumb drive from scratch by hand, but chances are you´re missing something.

 

Boot0 error points to a AF 4k formatted drive, but I would keep that for later.

 

If you can only boot into safe mode with VESA graphics, it would be a shame to run OSX like that...

 

Good luck!

 

---

Link to comment
Share on other sites

Well, he is right :P

 

MyHack is a great tool for retail installations, used it myself, but still had to remove the nvidia kexts manually after installation.

If you have only OSX installed to the HDD, repartition it, the boot0 error will be gone too, if you have other data on it, move it, or we will get back to it after installation. :)

 

Some more information about MyHack: http://myhack.sojugarden.com/guide/

Link to comment
Share on other sites

I tried to install with myhack, but i can't start the installation with the usb stick. i don't know why.

It would be nice if I could turn on the HD4000 and disable the nvidia from my retail installation without myhack

Link to comment
Share on other sites

Only possible if you create a custom installer by hand, you can use a script to delete the kexts during the installation. About the HD4000, until you have the right device string, it is hard to enable it during setup.

Wich version of ML are did you install, 10.8, 10.8.1 or 10.8.2?

Link to comment
Share on other sites

Boot stop, or black screen?

Great, i'm working on a modified install package, you could replace the file on USB, and all should go automatic. Just need to test it, will reboot in a sec.

 

I used part B of this thread for information on how to: http://www.insanelym...using-boot-132/

It enables the option to add custom packages to the installation.

post-1090626-0-05510900-1360270653_thumb.png

Link to comment
Share on other sites

Now I'm stuck, I think because I can not make the recognition that the HD4000, I'm trying to insert several strings in the file org.chameleon.boot.plist

but so far nothing, I can only enter the system in Safe Mode and using bootloader from the usb. The same safe mode does not work if launched with the bootloader installed, only usb.

This makes me worry and think that maybe the card is not the only problem.

Link to comment
Share on other sites

 Share

×
×
  • Create New...