Jump to content

74 posts in this topic

Recommended Posts

ASUS N53SM - INSTALL OS X USING CLOVER BOOT LOADER

 

 

About this Mac.   :hysterical:

http://youtu.be/9oullsazOiU

 

i7 2670QM

IntelHD 3000 - Nvidia GT630M

Realtek ALC269VB  Vendor Id: 0x10ec0269    Subsystem Id: 0x10431063

The EFI folder contains:

  • DSDT
  • SSDT
  • Config.plist configured for: native audio, HDMI audio, EDID, native AppleIntelCpuPowerManagement.kext, iMessage.

 

Step by Step

 

Download Clover

 http://youtu.be/YbeUP7r3MNI

 

Prepare USB for clover and OS X installer

http://youtu.be/-35g4LK7qAs

 

Install Clover to USB

https://youtu.be/HHx20DPyOFY

 

Configure Clover

http://youtu.be/j-TMfaQw0ZE

 

Copy OS X to USB

http://youtu.be/YegSyqC7DdY

 

Configure BIOS

Enable UEFI boot option in your BIOS setup

  

Install OS X 

http://youtu.be/HGnMJVltzyU

 

First boot  

http://youtu.be/yvTPYmKamQo 

                                        

Install Clover to HDD  

http://youtu.be/MTWH6atPju4

 

Copy preconfigured EFI folder for ASUS N53SM  

http://youtu.be/FNZzSpyVhFU

 

 

Required files:

  1. EFI Folder for Asus N53SM  https://drive.google.com/file/d/0B6jobf4PsIF6YWtldUI3a0dmc00/view?usp=sharing  UPDATED! 24/05/2015
  2. For audio i use AppleHda wizard with my audio config  https://drive.google.com/folderview?id=0B6jobf4PsIF6flZCMl9OU2FuYTl2c01WRWNIeThRZU5mYkQ0VVN2dk51dDloQXc5LVdmX3c&usp=sharing

post-796606-0-40018000-1409795423_thumb.png

Edited by anerik70

Share this post


Link to post
Share on other sites
Advertisement

Thank you so much for making this tutorial! 

 

Somehow i can't manage to create a working Clover UEFI bootable USB. It seems that i'm missing the kexts you are using to create the USB drive with.

Could you please share these as well?
 

Also, i used the EFI Folder for Asus N53SM from step 1 of the required files on the EFI partition of the USB.

In my bootmenu it recognises the USB with its UEFI capable boot (i can see the UEFI boot mode in the menu) but if i select this, my windows 8.1 uefi install gets loaded instead of Clover.

Do you perhaps know what i'm doing wrong? or are you perhaps able to help me creating a working clover bootable usb?, since this is the only thing that isn't working for me.

In the past i have had OSX 10.7 with Chameleon as bootloader running on my Asus N53SM.

 

I hope to hear from you soon.

 

(BTW, are you running the triple UEFI boot from one harddrive/SSD? if so, how have you managed to do this? i want the same kind of setup as you have created with Windows 8.1 Pro, OS X Yosemite and a Linux distro)

Share this post


Link to post
Share on other sites

Hello,

Thanks to anerik70 for creating this install guide.

 

one thing to be noted though is that the youtube video for:

-Prepare USB for clover 

and 

-install clover to USB

have the same link. i did find the right video on ANERIK70 list of uploaded videos on youtube so maybe he can fix the the link.

otherwise here is the link for it:

-Install clover to USB

https://www.youtube.com/watch?v=HHx20DPyOFY

 

also, in the video:

-Configure Clover

there are several files used to setup clover on the USB install stick, however i cant find those files anywhere.

 

is there a chance that maybe you can post those files ?

 

Thanks again ANERIK70 for taking the time to create the guide and share it with us.

Share this post


Link to post
Share on other sites

Hello,

Thanks to anerik70 for creating this install guide.

 

one thing to be noted though is that the youtube video for:

-Prepare USB for clover 

and 

-install clover to USB

have the same link. i did find the right video on ANERIK70 list of uploaded videos on youtube so maybe he can fix the the link.

otherwise here is the link for it:

-Install clover to USB

https://www.youtube.com/watch?v=HHx20DPyOFY

 

also, in the video:

-Configure Clover

there are several files used to setup clover on the USB install stick, however i cant find those files anywhere.

 

is there a chance that maybe you can post those files ?

 

Thanks again ANERIK70 for taking the time to create the guide and share it with us.

This guide is for Asus n53sm.

Here is my EFI folder use with caution and remember to personalize for your hardware.

https://drive.google.com/folderview?id=0B6jobf4PsIF6fllQeGFneF9CaHpVUmRLMTlERFlXd2NiRVIzRHQxMFpScHlDZ0lRdG9RdTQ&usp=sharing

Share this post


Link to post
Share on other sites

Ok, 

So after following this Guide (kinda) i have now been able to install Yosemite 10.10.2 and its running perfect on my machine.

(well the battery percentage always shows at 0, but I'll fix that later.)

 

here are the notes so that other people can use this guide. (thanks again to anerik70 for creating and posting the guide)

 

First:

This guide is for a N53SM model, however if you like me have a different model of the N53S series the guide still works but you need to make a change.

On the Video: Configure Clover you see him renaming a folder to N53SM. you need to rename that folder to same model as your machine. Mine is N53SV so that's the name i used to rename it. otherwise clover won't find your DSDT and you will have a Kernel Panic.

 

Second:

in the video of Configure Clover for the USB installer you can see there are 7 kext used.

these are not on the EFI folder he shared, but i have found them and i have attached them to this post for you to download.

 

Third:

if you have a 1080p screen or if you upgraded your 720p LCD panel to a 1080p like i did (very easy mod, just google it) then the machine will give you garbage on the screen when it boots up.

you need to patch the DSDT file.

i already done that for my machine and is also included on the files I'm sharing. replace the DSDT from his EFI folder and use the one i attached.

 

Fourth:

Copying his preconfigured EFI folder to my hard drive did not work for me. so i copied the one already created on the USB installer and that worked.

 

5th:

sound did not work for me. so i downloaded Voodoo kext installer (google it) and that worked. now i got sound.

ethernet and usb 3.0 did not work. download kext helper and install those kext.

 

and last,

the machine bios did not see the EFI partition to boot from the hard drive, so boot with usb installer select clover options and then choose "add boot options".

next time you reboot you will be able to select Clover as a EFI boot option.

 

... Just my two cents.

 

 

 

Clover and Kext files.zip

Share this post


Link to post
Share on other sites

Hi,

 

I am new to this forum and just tried 2 nights to get Yosemite running on my N53SM. Using this guide I can't get the notebook into clover bootloader. If I override the boot option in BIOS to "UEFI: My USB Stick" it just flickers and does nothing, which I'd say tells me it can't find the files to load it is looking for.

 

Booting a [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] Stick with MBR partitioning scheme works just fine but fails with initializing the graphics adapter and doesn't show anything but a black screen on the installer.

 

Do you have any hint on what I could try to make it work? Any files to provide to get help. 

 

I am also curious what is shown on the BIOS screenshots that are not working anymore. I also don't have the boot device choose menu from the videos. BIOS Version is 205.

 

Thanks a lot in advance.

 

Greets

Share this post


Link to post
Share on other sites

Hi,

 

I am new to this forum and just tried 2 nights to get Yosemite running on my N53SM. Using this guide I can't get the notebook into clover bootloader. If I override the boot option in BIOS to "UEFI: My USB Stick" it just flickers and does nothing, which I'd say tells me it can't find the files to load it is looking for.

 

Booting a ##### Stick with MBR partitioning scheme works just fine but fails with initializing the graphics adapter and doesn't show anything but a black screen on the installer.

 

Do you have any hint on what I could try to make it work? Any files to provide to get help. 

 

I am also curious what is shown on the BIOS screenshots that are not working anymore. I also don't have the boot device choose menu from the videos. BIOS Version is 205.

 

Thanks a lot in advance.

 

Greets

Follow these steps:

 

1. Put these files in the root of your *EFI partition https://drive.google.com/folderview?id=0B6jobf4PsIF6fllQeGFneF9CaHpVUmRLMTlERFlXd2NiRVIzRHQxMFpScHlDZ0lRdG9RdTQ&usp=sharing

​           

2. Enable UEFI boot option in your BIOS setup

3. Restart your Asus and press esc key to select boot device then press f12 to reach the efi shell

4. In the shell type "fs0:" (without quotes) and press enter

5. type "cd efi" (without quotes) and press enter

6. type "cd clover" (without quotes) and press enter

7. type "cloverx64.efi" (without quotes) and press enter

 

 
* EFI partition has to be the EFI partition of the your device to boot

Share this post


Link to post
Share on other sites

Forgot to say in my first post: thanks for your work providing these guides :)

 

Got it working by myself, by copying cloverx64.efi to usb key root and renaming it to shellx64.efi. I also preformatted my EFI partition with FAT16 with newfs_msdos. Had to do the same with my SSD EFI Partition to make the BIOS Autoboot into clover.

 

Here are my additions to make things even smoother:

 

For correct Webcam support even in Skype get Asusg75's Patched AnyiSightCam from http://forum.osxlatitude.com/index.php?/topic/6182-asus-g75vw/

 

The AppleHDA kext from the guide didn't work and VoodooHDA gave me screeches and crackles. Used this special AppleHDA which seems to work just fine. (AppleHDA-272.18-ALC269_Asus_N53sm_.zip):

http://www.insanelymac.com/forum/topic/298663-applehda-for-yosemite/

 

For correct 2 Finger scroll and trackpad support I used Smart Touchpad Driver 4.2: http://forum.osxlatitude.com/index.php?/topic/1948-elan-and-focaltech-smart-touchpad-driver-mac-os-x/

 

Next is trying out USB3 support. Didn't work so far with the provided kexts :)

Share this post


Link to post
Share on other sites

USB3 works now, seemed to be a reboot issue. Ethernet is working fine as well, thanks a lot! :) Is there any way to turn off Bluetooth (my button is greyed out)?

Share this post


Link to post
Share on other sites

Thank you so much for making this tutorial! 

 

Somehow i can't manage to create a working Clover UEFI bootable USB. It seems that i'm missing the kexts you are using to create the USB drive with.

Could you please share these as well?

 

Also, i used the EFI Folder for Asus N53SM from step 1 of the required files on the EFI partition of the USB.

In my bootmenu it recognises the USB with its UEFI capable boot (i can see the UEFI boot mode in the menu) but if i select this, my windows 8.1 uefi install gets loaded instead of Clover.

Do you perhaps know what i'm doing wrong? or are you perhaps able to help me creating a working clover bootable usb?, since this is the only thing that isn't working for me.

In the past i have had OSX 10.7 with Chameleon as bootloader running on my Asus N53SM.

 

I hope to hear from you soon.

 

(BTW, are you running the triple UEFI boot from one harddrive/SSD? if so, how have you managed to do this? i want the same kind of setup as you have created with Windows 8.1 Pro, OS X Yosemite and a Linux distro)

Follow these steps:

 

1. Put these files in the root of your *EFI partition https://drive.google...dTQ&usp=sharing

​           

2. Enable UEFI boot option in your BIOS setup

3. Restart your Asus and press esc key to select boot device then press f12 to reach the efi shell

4. In the shell type "fs0:" (without quotes) and press enter

5. type "cd efi" (without quotes) and press enter

6. type "cd clover" (without quotes) and press enter

7. type "cloverx64.efi" (without quotes) and press enter

Then navigate add the entries to your UEFI boot

 

 

* EFI partition has to be the EFI partition of the your device to boot

Hello,

Thanks to anerik70 for creating this install guide.

 

one thing to be noted though is that the youtube video for:

-Prepare USB for clover 

and 

-install clover to USB

have the same link. i did find the right video on ANERIK70 list of uploaded videos on youtube so maybe he can fix the the link.

otherwise here is the link for it:

-Install clover to USB

https://www.youtube.com/watch?v=HHx20DPyOFY

 

also, in the video:

-Configure Clover

there are several files used to setup clover on the USB install stick, however i cant find those files anywhere.

 

is there a chance that maybe you can post those files ?

 

Thanks again ANERIK70 for taking the time to create the guide and share it with us.

Thank you.

I've Fixed all

Ok, 

So after following this Guide (kinda) i have now been able to install Yosemite 10.10.2 and its running perfect on my machine.

(well the battery percentage always shows at 0, but I'll fix that later.)

 

here are the notes so that other people can use this guide. (thanks again to anerik70 for creating and posting the guide)

 

First:

This guide is for a N53SM model, however if you like me have a different model of the N53S series the guide still works but you need to make a change.

On the Video: Configure Clover you see him renaming a folder to N53SM. you need to rename that folder to same model as your machine. Mine is N53SV so that's the name i used to rename it. otherwise clover won't find your DSDT and you will have a Kernel Panic.

 

Second:

in the video of Configure Clover for the USB installer you can see there are 7 kext used.

these are not on the EFI folder he shared, but i have found them and i have attached them to this post for you to download.

 

Third:

if you have a 1080p screen or if you upgraded your 720p LCD panel to a 1080p like i did (very easy mod, just google it) then the machine will give you garbage on the screen when it boots up.

you need to patch the DSDT file.

i already done that for my machine and is also included on the files I'm sharing. replace the DSDT from his EFI folder and use the one i attached.

 

Fourth:

Copying his preconfigured EFI folder to my hard drive did not work for me. so i copied the one already created on the USB installer and that worked.

 

5th:

sound did not work for me. so i downloaded Voodoo kext installer (google it) and that worked. now i got sound.

ethernet and usb 3.0 did not work. download kext helper and install those kext.

 

and last,

the machine bios did not see the EFI partition to boot from the hard drive, so boot with usb installer select clover options and then choose "add boot options".

next time you reboot you will be able to select Clover as a EFI boot option.

 

... Just my two cents.

Here is my EFI folder Up to date

https://drive.google.com/folderview?id=0B6jobf4PsIF6fllQeGFneF9CaHpVUmRLMTlERFlXd2NiRVIzRHQxMFpScHlDZ0lRdG9RdTQ&usp=sharing

Forgot to say in my first post: thanks for your work providing these guides :)

 

Got it working by myself, by copying cloverx64.efi to usb key root and renaming it to shellx64.efi. I also preformatted my EFI partition with FAT16 with newfs_msdos. Had to do the same with my SSD EFI Partition to make the BIOS Autoboot into clover.

 

Here are my additions to make things even smoother:

 

For correct Webcam support even in Skype get Asusg75's Patched AnyiSightCam from http://forum.osxlatitude.com/index.php?/topic/6182-asus-g75vw/

 

The AppleHDA kext from the guide didn't work and VoodooHDA gave me screeches and crackles. Used this special AppleHDA which seems to work just fine. (AppleHDA-272.18-ALC269_Asus_N53sm_.zip):

http://www.insanelymac.com/forum/topic/298663-applehda-for-yosemite/

 

For correct 2 Finger scroll and trackpad support I used Smart Touchpad Driver 4.2: http://forum.osxlatitude.com/index.php?/topic/1948-elan-and-focaltech-smart-touchpad-driver-mac-os-x/

 

Next is trying out USB3 support. Didn't work so far with the provided kexts :)

That's a kext mirone make for me.  :yes:  but if you want to update your AppleHDA you can use HDA WIZARD like I do in this Video.

https://youtu.be/KqFa4esNK1M

Share this post


Link to post
Share on other sites

Hi, thanks for the post it was very useful for me, my bios version is old, 202, and in no way I can boot from my HDD I always have to boot from usb.

Have you got any suggestions?

Thanks again

Share this post


Link to post
Share on other sites

Hi! I'm trying to follow this guide to install Yosemite on my Asus N53SN, but I don't find some files in the folders that you have kindly provided: "config.plist", "SSDT.aml", and "HFSPlus-64.efi".

(The others are in the 5th post)

 

Is it possible to have them, please? Or where can I find them?

 

Thank you very much for the detailed guide!!

Share this post


Link to post
Share on other sites

Hi! I'm trying to follow this guide to install Yosemite on my Asus N53SN, but I don't find some files in the folders that you have kindly provided: "config.plist", "SSDT.aml", and "HFSPlus-64.efi".

(The others are in the 5th post)

 

Is it possible to have them, please? Or where can I find them?

 

Thank you very much for the detailed guide!!

https://drive.google.com/file/d/0B6jobf4PsIF6YWtldUI3a0dmc00/view?usp=sharing

 

There is a file called EFI. Download it. This is a folder download it and navigate to EFI/clover/oem/asus n53sm/UEFI/

Share this post


Link to post
Share on other sites

Hi! Thank you for your answer.

I'm sorry to bother you, but I only see the "efi" file as a unknown file of 1kb and I cannot navigate it...is this because I'm downloading from Windows?

 

Without those files I have been able to install OSX anyway, but with some problems, for instance I have wrong colours (green and pink-ish colours) in the desktop and some other problems like ethernet and wifi not working and touchpad navigation very strange (it takes a lot of "touching" to navigate the desktop, even if I increase the trackpad speed). Are those problems possibly related to the fact that I installed the system without the EFI files?

(I'm trying Yosemite 10.10 3)

 

Thank you very much!!

Share this post


Link to post
Share on other sites

Hi! Thank you for your answer.

I'm sorry to bother you, but I only see the "efi" file as a unknown file of 1kb and I cannot navigate it...is this because I'm downloading from Windows?

 

Without those files I have been able to install OSX anyway, but with some problems, for instance I have wrong colours (green and pink-ish colours) in the desktop and some other problems like ethernet and wifi not working and touchpad navigation very strange (it takes a lot of "touching" to navigate the desktop, even if I increase the trackpad speed). Are those problems possibly related to the fact that I installed the system without the EFI files?

(I'm trying Yosemite 10.10 3)

 

Thank you very much!!

I have updated the first link. Try 

Share this post


Link to post
Share on other sites

Hi anerik70!

Thank you very much! Now I can download the folder!

Unfortunately I'm not even able to reach the installer with the usb installer that I've just created following your guide.

I'm using Yosemite 10.10.3. I built the usb installer from the same pc in which I installed Yosemite 10.10.3 with a usb installation already prepared found on the web. It has a lot of problems (wrong display colours, wifi not working...), but at least the system boots...

I'd like to reinstall the system with your clean installation, with correct drivers.

It's absurd that with correct drivers I cannot reach the installer..,using "-v" boot flag I can see that it keeps saying: "IOBluetoothHostControllerUSBTransport" error,like in this picture http://www.tonymacx86.com/attachments/yosemite-laptop-support/121151d1420780213-lenovo-g580-cannot-reach-installer-wp_20150109_005.jpg

 

Thank you very much!!

Share this post


Link to post
Share on other sites

Hi anerik70!

How are you!?

Eventually after all these months I managed to install OS X on my computer too. I'm on 10.11.2. Since our machines are quite similar I am here to bother you again with many questions :)

 

 

1)As you can see from my signature (half copied from yours :) ) I'm stuck mainly with Bluetooth, WiFi and Battery Management that aren't working. I'd like to know how you managed to make them working, or if you can upload an updated version of your kext, dsdt,ssdt and config.plist. 

 

2)I have to admit that I'm still using your patched ssdt and dsdt from yosemite, without them I can't even boot...for these reasons I'd like to ask you if you remember which patches you applied (just for curiosity and to learn a bit from them). I tried to patch by myself my natively extracted dsdt and ssdt to have them clean, but I failed, so i'm still using yours. But I'd like to understand which are the patches to apply. For instance to enable the audio I read that I should use the "IRQ fix" but I don't know whether you had already patched it in yours or not...

 

 

Some other minor questions...

3)I managed to make alc269 working with Mirone's AppleHDAPatcher (after two days of work) and the audio seems working fine but I don't know whether it is normal that I can't see hdmi audio out and spdif, but only built-in speakers

 

4)Sometimes i have glitches of graphical errors of some kind, except for the fact that our intel hd3000 is native, did you set something in particular, like disable the nvidia card to avoid graphical problems?

 

5)Looking at your config.plist I saw that in the cpu section you checked the C2,C4,C6 checkbox...but how do you know the best settings? (I trust you blindly :) ) My config.plist is empty with respect to yours...

 

6)Why do you have many different ACPI folders with many different DSDT (sinbateria,sinfant,nvidia) in your Clover? you have it in Efi/Clover/Acpi/patched but also in Efi/Clover/Oem/N53SM/Uefi/Acpi/patched? (Unfortunately I wasn't able to install os x as uefi....)

 

7)Any other suggestions to make the system more stable? 

 

Ahah sorry for all these questions, but I'm in constant fear of breaking the functionality of the system. For instance now I'll try to edit the dsdt to correct the glitch while setting the brightness....

 

Thank you very much!!!!

Share this post


Link to post
Share on other sites

Hi anerik70!

How are you!?

Eventually after all these months I managed to install OS X on my computer too. I'm on 10.11.2. Since our machines are quite similar I am here to bother you again with many questions :)

 

 

1)As you can see from my signature (half copied from yours :) ) I'm stuck mainly with Bluetooth, WiFi and Battery Management that aren't working. I'd like to know how you managed to make them working, or if you can upload an updated version of your kext, dsdt,ssdt and config.plist. 

 

2)I have to admit that I'm still using your patched ssdt and dsdt from yosemite, without them I can't even boot...for these reasons I'd like to ask you if you remember which patches you applied (just for curiosity and to learn a bit from them). I tried to patch by myself my natively extracted dsdt and ssdt to have them clean, but I failed, so i'm still using yours. But I'd like to understand which are the patches to apply. For instance to enable the audio I read that I should use the "IRQ fix" but I don't know whether you had already patched it in yours or not...

 

 

Some other minor questions...

3)I managed to make alc269 working with Mirone's AppleHDAPatcher (after two days of work) and the audio seems working fine but I don't know whether it is normal that I can't see hdmi audio out and spdif, but only built-in speakers

 

4)Sometimes i have glitches of graphical errors of some kind, except for the fact that our intel hd3000 is native, did you set something in particular, like disable the nvidia card to avoid graphical problems?

 

5)Looking at your config.plist I saw that in the cpu section you checked the C2,C4,C6 checkbox...but how do you know the best settings? (I trust you blindly :) ) My config.plist is empty with respect to yours...

 

6)Why do you have many different ACPI folders with many different DSDT (sinbateria,sinfant,nvidia) in your Clover? you have it in Efi/Clover/Acpi/patched but also in Efi/Clover/Oem/N53SM/Uefi/Acpi/patched? (Unfortunately I wasn't able to install os x as uefi....)

 

7)Any other suggestions to make the system more stable? 

 

Ahah sorry for all these questions, but I'm in constant fear of breaking the functionality of the system. For instance now I'll try to edit the dsdt to correct the glitch while setting the brightness....

 

Thank you very much!!!!

Hi.

My system isn't same as yours.

The only thing that not works is NVIDIA GT 630M.

 

My current configuration for EL CAPITAN 10.11.2 is here: https://drive.google.com/file/d/0B6jobf4PsIF6aDdKUUtTcHpiWjQ/view?usp=sharing

I use OEM folder inside clover with my asus's name. If you want to use my efi folder you have to rename N53SM to N53SN 

Share this post


Link to post
Share on other sites

Hi Anerik70! Thank you very much!!

I'm sorry to bother you again...

 

I'm trying to install OSX without your patched files because I noticed that the SystemMemory addresses between my native DSDT and your patched DSDT are different, so as you say our machines are not the same, but probably they are similar.

 

So I'm trying to install without patching acpi files at all for now, but I cannot reach the installation screen because I'm stuck at a gray screen. I've finally managed to install the system with and external monitor connected via vga, so the problem is my display. But I don't understand how to solve this, even now that the system is installed it is stuck at a gray screen without external monitor. I was suggested this could be a backlight issue or edid issue...By any chance did you encountered this problem (if yes how did you solve it)? (I've the 1920x1080 display but maybe they are the same panel except for that...).

 

 

After having solved the first problem I'd like to patch my acpi files by myself (even to learn a bit), so by any chance do you remember which patches you applied to yours? Just to have a guideline because I cannot understand which patches are needed. I found a list:

"Fix _WAK Arg0 v2"
"HPET Fix"
"SMBUS Fix"
"IRQ Fix"
"RTC Fix"
"OS Check Fix"
"Fix Mutex with non-zero SyncLevel"
"Fix PNOT/PPNT"
"Add IMEI"

"6-series USB"

 

Do you remember whether you applied some of them? 

 

Thank you very much!!!

Share this post


Link to post
Share on other sites

Hello guys,

happy new year!

 

Thanks for the guide! i have good old n53sn notebook. I am trying installing el capitan on my n53sm following this guide, but i have some problems here:

1) Audio still doesn't work using AppleHDA (N53SN-fullhd display).

2) keyboard and trackpad doesn't work

3) I am still having problem installing clover on the same hd (main internal hd0) and i have to boot using an external usb stick... perhaps it's related to clover itself not to n53.

thanks!

Share this post


Link to post
Share on other sites

Hello guys!

Guys, if I install to USB Flash not Clover but Yosemite - will it install hackintosh this way or I should use only Clover?

Share this post


Link to post
Share on other sites

Hello guys!

 

Guys, if I install to USB Flash not Clover but Yosemite - will it install hackintosh this way or I should use only Clover?

Hi.

To install OS X on a non-Apple PC you need to use one of the so-called "bootloaders", like Clover, Chameleon, Enoch, etc.... Nowadays I'd say that if you learn to use Clover is probably better because it seems to be the way to go in the future.

So the answer to your question is that you need both a bootloader like Clover AND the operative system (Mavericks/Yosemite/El Capitan....) to setup your hackintosh. 

There are plenty of guides and tutorials on the internet that explain how to setup an USB pen drive with one or two partitions (it depends on the type of BIOS:legacy/UEFI) for bootloader and OSX.

Once you install the system you still need the bootloader to boot in it, so either you keep using the USB flash drive or you just install the bootloader in your internal hard disk.

I hope I've been enough clear.

 

Hello guys,

happy new year!

 

Thanks for the guide! i have good old n53sn notebook. I am trying installing el capitan on my n53sm following this guide, but i have some problems here:

1) Audio still doesn't work using AppleHDA (N53SN-fullhd display).

2) keyboard and trackpad doesn't work

3) I am still having problem installing clover on the same hd (main internal hd0) and i have to boot using an external usb stick... perhaps it's related to clover itself not to n53.

thanks!

Hi manmal!

1)I don't know on which system you are, but I am on El Capitan 10.11.3 with my Asus N53SN (full hd like yours). I tried to patch my appleHDA with Mirone's patch on https://github.com/Mirone/AppleHDAPatcherchoosing the patch that Anerik70 uses, so the " ALC269-AsusN53sm" one. I managed to make it work but it was unstable, sometimes it booted without audio working, sometime with the audio working. Then I tried Anerik70's "aDummyHDA" + injection of audio layout in my Clover's config.plist and now it is working without any problem! You can find it in the folder posted in post #19 between the kexts in the OEM folder.

2)I'm currently using without any problem the kexts in my signature to make keyboard and trackpad working, so they are Elan Touchpad (ApplePS2SmartTouchPad.kext) - FN Keys (AsusNBFnKeys.kext)[/size]. Probably you can find them between the kexts in the folder by Anerik70 posted in post #19. I use KextWizard to install them in S/L/E (system/library/extensions), and after the installation I rebuild kext caches and permissions always with KextWizard.

3)I'm using both windows and OSX in UEFI mode currently, so I chose not to install clover in my hdd, because I wanted Windows to keep its bootloader "clean" in the EFI partition of my HDD. However since I didn't want to use a usb pen drive to boot every time I manage to create a small partition on my internal HDD (being GPT I can create many partitions) around 300 MB formatted in fat32 and I just copied the content of the Clover partition of the USB pendrive onto this internal partition. Basically now I use this partition to boot into clover. The way I boot is a bit tricky if you want. Since our old laptop has a crappy bios, one of those which is both compatible with Legacy BIOS and UEFI (an early implementation of UEFI bios...) every time I want to boot OSX I enter the BIOS, go in UEFI shell, select the internal partition where clover is stored and manually browse in the "efi/boot" folder and run "bootx64.efi". That pops up clover and from there I can easily access OSX. Of course this is because my main system is Windows, otherwise I would have installed clover properly, but however trust me it doesn't take more than 15 second to boot into Clover once you are used to it!

Bye!

 

Hi.

My system isn't same as yours.

The only thing that not works is NVIDIA GT 630M.

 

My current configuration for EL CAPITAN 10.11.2 is here: https://drive.google.com/file/d/0B6jobf4PsIF6aDdKUUtTcHpiWjQ/view?usp=sharing

I use OEM folder inside clover with my asus's name. If you want to use my efi folder you have to rename N53SM to N53SN

Hi anerik70! I'm sorry to bother you again. I managed to make everything work, and for this I thank you again! But I'd like to ask you one last thing....I'm using your aDummyHDA.kext successfully, but I noticed that it has a version lower than the actual ones on El Capitan (the ones that the patcher produces). Even if it is working I'd like to understand how you managed to create a working aDummyHDA.

At first I used the patch by Mirone at https://github.com/Mirone/AppleHDAPatcher with the patch "ALC269-AsusN53sm" but it only creates the AppleHDA, not the aDummyHDA (moreover I was having problems).

Now I tried another patch always by Mirone at http://www.insanelymac.com/forum/files/file/496-applehda-patcher/but unfortunately it lacks the patch for " ALC269-AsusN53sm", so I tried all the possible variations of the version for ALC269 without success....

So how did you create your aDummyHDA??! You know just to understand and learn, even because in the future it could still be useful!

Thank you very much!!

Bye!

Share this post


Link to post
Share on other sites

Hi.

To install OS X on a non-Apple PC you need to use one of the so-called "bootloaders", like Clover, Chameleon, Enoch, etc.... Nowadays I'd say that if you learn to use Clover is probably better because it seems to be the way to go in the future.

So the answer to your question is that you need both a bootloader like Clover AND the operative system (Mavericks/Yosemite/El Capitan....) to setup your hackintosh. 

There are plenty of guides and tutorials on the internet that explain how to setup an USB pen drive with one or two partitions (it depends on the type of BIOS:legacy/UEFI) for bootloader and OSX.

Once you install the system you still need the bootloader to boot in it, so either you keep using the USB flash drive or you just install the bootloader in your internal hard disk.

I hope I've been enough clear.

 

Yep, I understand it!

Yesturday I tried to load UEFI from flash on me Asus N53Sm as it was shown in this topic guide.

But I really couldn't do it - Clover loader wasn't loading). UEFI is enabled in my BIOS.

The only guess I have is broken loader.

After preparing my USB Flash I guess to check data on it and plug it into Mac - and when I prepare USB Flash Mac shows 2 volumes (with OSX and UEFI), but second time only OSX volume. At the end of all I ignored safely removing hardware. Maybe this steps broke loader, I don't know). Today I'll try to prepare Flesh USB once again and try to install Mac))

But maybe you have idea, why Asus didn't load loader?It seens so strange.

 

P.S.: boot priority was set to UEFI flash

Share this post


Link to post
Share on other sites

Yep, I understand it!

Yesturday I tried to load UEFI from flash on me Asus N53Sm as it was shown in this topic guide.

But I really couldn't do it - Clover loader wasn't loading). UEFI is enabled in my BIOS.

The only guess I have is broken loader.

After preparing my USB Flash I guess to check data on it and plug it into Mac - and when I prepare USB Flash Mac shows 2 volumes (with OSX and UEFI), but second time only OSX volume. At the end of all I ignored safely removing hardware. Maybe this steps broke loader, I don't know). Today I'll try to prepare Flesh USB once again and try to install Mac))

But maybe you have idea, why Asus didn't load loader?It seens so strange.

 

P.S.: boot priority was set to UEFI flash

Keep on mind that the EFI partition is not mounted in OSX by default, so it is normal that the first time you create the USB flash with clover it will show the EFI partition, but after that every time you want to "see" the EFI partition you have to mount it manually through terminal and disk utility or using tools like Clover Configurator (which I suggest since later you'll use it probably to tweak your config.plist). As soon as you start Clover Configurator it will ask to mount the EFI partition. Here you must be careful and mount the right one, maybe on your mac there is already its own EFi partition, but you want the one with Clover on the USB flash drive. So after having mounted the EFI partition you can see it in your desktop as "EFI".

 

The second thing is that you can choose whether to use clover "legacy" for legacy bios or clover UEFI. You have to choose it when you prepare the clover USB key, and later boot accordingly. Probably the UEFI one is more future proof. Keep in mind that our laptop has an early implementation of UEFI boot with some limitations. Basically it's ok if you have enabled "UEFI boot" in bios, but for instance, when you press "ESC" at boot you are shown the bootable entries, and usually you should see your usb drive in two different ways, the "legacy" way and the "UEFI" way (prefixed with "UEFI: "). Ok now at least for me in that situation if I chose the UEFI one (for clover UEFI) I wasn't able to boot in clover. On our laptops it's better to use the EFI shell to boot devices in UEFI mode manually. To do so put in the root of your EFI partition on the USB key the file attached in this post (decompressed). To do so you have to mount the EFI partition of your usb key as explained above (with Clover Configurator or manually), and copy the file "shellx64.efi" (not the zip, extract the file) in the root of the "EFI" partition. Where you also have the "EFI" folder (not inside!). Once you do that you reboot the Asus N53SM and enter the bios (pressing F2 or "ESC" and choosing "Enter Setup"). Once you're in the bios go in the last tab "Save and Exit" and choose the option at the bottom: "Launch EFI shell..........".

 

Here wait the few seconds for the console to appear (or press any button if you don't want to wait) and go in the "EFI" partition on the USB key that you prepared before.

Pay attention, you should "find" the name or your USB flash drive or do some trial/error to find the correct one. You can type "map" without quotes to show the list of devices. To go in your usb drive, for instance for me it was the fs4, you should type: "fs4:" and press enter (if not fs4 try fs0, fs1, fs2....). Pay attention, I don't know the layout of your keyboard but in the efi shell the layout of the keyboard is the US layout so you could have some different combination of buttons to type ":", look up for the US keyboard layout on Google if you need.

 

Once you are in the device you can type "dir" to show the folders. You can already check if you selected the correct drive, you should have all the folders of Clover, so you should find "EFI" folder and others. If you don't see the "EFI" folder probably you entered the wrong device so you have to change drive always typing "fsX:" where X=1,2,3....

Once you find the correct drive with the "EfI" folder you type: "cd \efi\boot" and press enter.

Once you did that type "bootx64.efi" and press enter.

Now Clover should boot properly in UEFI mode. (In your bios the UEFI boot must be Enabled of course).

shellx64.efi.zip

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host
      Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. 
       
      The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg
       
      @colt2 HOW TO: Create a bootable El Capitan ISO for VMware
      @dsmccombs comment on faking Ivybridge Processor
      @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6
      @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
      VirtualBox Forum: Status of OSX on OSX
       
      Requirements
         Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X)    4GB or more RAM (2GB or more will be needed for OS X)    Hard Disk with at least 40GB free for Virtual Machine    Oracle VM VirtualBox v 5.0.34    Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75    16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC  
      Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes.  Note: you will need approx 16GB of free space on your hard disk for the script to complete.
       
       
       
      3.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 4.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
       
      Create an El Capitan Virtual Machine in VirtualBox
      1.  Open the VirtualBox program and click the "New" button to create a new VM.
       

       
      2.  Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version.  I named my Virtual Machine "El_Capitan", then clicked next...
       

       
      3.  Leave the Memory size at the recommended 2048 MB, then click next.
       

       
      4.  Choose to "Create a virtual hard disk now", then click the create button.
       

       
      5.  For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare.  Click next...
       

       
      6.  For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space).
       

       
      7.  On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger.  When you click the create button, you will now see your new VM in the VirtualBox main GUI.
       

       
      8.  Click the settings button on the Main Menu to tweak a few settings....
         a.  On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?)
       

       
         b.  On the System/Processor tab, you can increase the allocated CPU cores to 2
       

       
         c.  On the Display tab, you can increase the allocated Video Memory to 128MB
       

       
         d.  On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". 
       

       
      Navigate and select the El Capitan ISO we created earlier...
       

       
         e.  Click the OK button to finalise the VM settings.
       
       
      Patch El Capitan vbox configuration file with DMI Settings from a Mac
      1.  From the start menu, type cmd and click run as administrator to open an administrative command prompt. 
       

       
      2.  Choose a Mac Model similar to your host system, then type the following lines, followed by <enter>  after each line.  Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick...
       
      Eg iMac11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3.  Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors.  You can try from one of the following if this happens:

      To spoof Lynnfield i5 750 CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4.  Close the command prompt window.
       
       
      Installation of El Capitan
      We are now ready to start the El_Capitan Virtual Machine....
       



       
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

       
      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan.
       

       
      3.  Quit DU and choose Macintosh HD to install El Capitan on.
      4.  After 20-30 min (depending on how fast your system is), the installation will complete.  At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive.  The VM is now ready to reboot into OS X from the virtual hard drive.
      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
      7.  Finally, you will arrive at the El Capitan Desktop.
       

       
      8.  Network/internet and audio should work OOB but on my system, the sounds were distorted.  Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). 
       
       
      Customization with VBoxManage
      1.  You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt:
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
       
      Update:  For VirtualBox 5.2.x, the command for changing screen resolution has changed...
       
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution)
      eg
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2.  Adding serials and other SMBIOS details for the System Information Screen
      VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html.
       
      Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above).  Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free .
       

       
      UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51.
      UPDATE macOS High Sierra 17A365:  For macOS High Sierra, use CHSI.tool in post#73.
      UPDATE macOS Mojave Beta:  For macOS Mojave Beta, use CMJI.tool on page 4 of thread.
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
    • By MaLd0n
      Create a bootable copy of macOS Sierra Check out the link http://www.insanelymac.com/forum/files/file/559-flash-drive-maker/   --Install Clover UEFI in USB stick https://sourceforge.net/projects/cloverefiboot/files/Installer/   --Replace Folder CLOVER INSTALLATION.zip   --Install Sierra and boot into system!   --Install Clover UEFI and replace with my folder  CLOVER POST INSTALLATION.zip   --Reboot and activate video!   Bingo!   Now you need a fine tune! I prefer DSDT way, apply all patches in one file, many people prefer many SSDTs or Clover patches!   If you need DSDT edit... Run it RunMe.app   --DSDT My DSDT DSDT.ASUS H61M-A MaLd0n.zip   Patches -FIX ERRORS AND WARNINGS -HPET -SATA -SLPB -DARWIN -EHCx -LPC -HDEF -RTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -PNLF Clear NVRAM, Purge and Kextcache
          --FakeSMC http://www.hwsensors.com/releases --Audio https://github.com/vit9696/AppleALC --USB https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads --LAN http://www.insanelymac.com/forum/topic/287161-new-driver-for-realtek-rtl8111/   Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
    • By fantomas1
      -----------------------------
      Mise à jour 12/07/2018
      -----------------------------
       
      La sortie de macOS 10.14 Beta m'oblige à mettre ce topic à jour. Plus de détails dans ce post.
       

       

       
      -----------------------------
      Mise à jour 09/06/2017
       
      -----------------------------
       
      La sortie de macOS 10.13 Beta m'oblige à mettre ce topic à jour. Plus de détails dans ce post.
       

       
       
       
      -----------------------------
      Mise à jour 15/06/2016
      -----------------------------
       
      Une petite mise à jour du topic pour confirmer le bon fonctionnement du patch à la volé de Clover (r3561) avec macOS Sierra.
       

       
       
       
      -----------------------------
      Mise à jour 24/08/2015
      -----------------------------
       
      ok, très bien,
       
      comme pour la HD6770, la nouvelle méthode du patch à la volé est de nouveau fonctionnel et avec les dernières versions de Clover.
       
      pour ma part, je suis sur El Capitan DB7 et Clover r3259
       

       
       
      par contre, je suis toujours obligé de m’aider de l’astuce avec FakeSMC pour que mes kexts soient toujours chargés, mais au moins cela marche.   
       
       
       
       
      et pour config.plist, cela donne ça :
       

       
       
      ceci est juste un exemple avec ma HD4830, il va de soi que vous devez mettre Device-ID de votre carte graphique !!!
       
       
       
       
       
      Salut à tou(te)s
       
      Comme certain(e)s le savent, les cartes graphiques dites "Exotiques" ne sont pas supportés par le système d'exploitation d'Apple.
      En sus d'ajouter l'identifient de la carte graphique (Device ID) dans l'Info.plist du ou des kexts concernés, il faut aussi interagir sur la partie "binaire" du kext par le biais du "patching".
       
      Dans notre cas, les cartes graphiques exotiques sont les cartes AMD (anciennement ATI) de la série HD 48xx, et plus précisément les HD 4830, HD4850, HD4870x2 et HD4890.*
       
      Donc le but est de faire fonctionner ces cartes graphiques de manière stable et fluide en activant QE_CI, chose nécessaire pour en profiter pleinement du système d'exploitation.
       
      * Juste avant de commencer, vous l'avez peut-être remarqué, la HD4870 n'est pas sur la liste suscitée et pour cause c'est que cette carte graphique est nativement supportée par le système d'exploitation d'Apple. Son Device ID est 0x94401002 que vous pouvez trouvé dans l'Info.plist des kexts concernés et c'est celui-ci que nous allons utiliser afin de le remplacer par le Device ID de notre carte graphique.
       
      ** Ce tuto est fait pour fonctionner sous OS X Mavericks, mais il doit fonctionner aussi avec les autres. La seule chose différente c'est l'adresse binaire à patcher.    
       
       
      Très bien, comme le titre le suggère, nous allons voir comment faire reconnaître ces cartes graphiques sous Clover et obtenir par la même un QE_CI activé et parfaitement fonctionnelle.
       
      Je vais utiliser ma Sapphire HD4830 512 MB GDDR3 PCI-E (comme cobaye    ) pour ce test et qui a pour Device ID 0x944c1002.
       
      Pour que ce test réussisse, nous allons donc utiliser ces 2 kexts, à savoir AMD4800Controller.kext (pour la partie QE) et ATIRadeonX2000.kext (pour la partie CI) et allons ajouter notre Device ID dans l'Info.plist. via le tweak "KernelAndKextPatches"
       
      Donc les valeurs à entrer dans notre config.plist sont celle-ci :
      <key>KernelAndKextPatches</key>     <array>         <dict>             <key>Name</key>             <string>AMD4800Controller</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>         <dict>             <key>Name</key>             <string>ATIRadeonX2000</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>     </array> Comme vous pouvez le voir, la clé "InfoPlistPatch" sert à injecter notre Device ID "uniquement" dans Info.plist, sans y toucher à la partie "binaire" de nos kexts. La clé "Find" a pour fonction de trouver le Device ID que l'on veut remplacer par le notre en utilisant la clé "Replace".
       
      Très bien, maintenant comme nous l'avons dit au début de ce tutoriel, ajouter notre Device ID n'est pas suffisant pour faire fonctionner pleinement notre carte graphique, il faut encore interagir sur la partie "binaire" de nos kexts. Dans notre cas, il va falloir agir uniquement sur un kext, çàd sur ATIRadeonX2000.kext et plus particulièrement sur ATIRadeonX2000.kext/Contents/MacOS/ATIRadeonX2000
       
      Et pour cela, nous allons faire comme ceci :
      <key>KextsToPatch</key> <array> <dict>     <key>Name</key>     <string>ATIRadeonX2000</string>     <key>Find</key>     <data>0F8394010000</data>     <key>Replace</key>     <data>909090909090</data> </dict> </array> Là nous pouvons voir que la clé "InfoPlistPatch" n'est pas utilisée et donc ces valeurs n'auront aucun effet sur l'Info.plist mais agiront uniquement au niveau de la partie "binaire". 
       
      Et voici les valeurs en leur forme complète que vous devrez ajouter dans votre config.plist
      <key>KernelAndKextPatches</key>     <array>         <dict>             <key>Name</key>             <string>AMD4800Controller</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>         <dict>             <key>Name</key>             <string>ATIRadeonX2000</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>         <dict>             <key>Name</key>             <string>ATIRadeonX2000</string>             <key>Find</key>             <data>0F8394010000</data>             <key>Replace</key>             <data>909090909090</data>        </dict>     </array> Très bien, maintenant il ne nous reste plus qu'à autoriser l'injection des kexts, sans quoi le patch ne fonctionnera pas. Et nous allons le faire via le tweak "InjectKexts" comme ceci :
      <key>SystemParameters</key> --> clé principale <dict>       <key>InjectSystemID</key>       <true/>       <key>InjectKexts</key> --> sous clé       <string>Yes</string> </dict>  
       
      Si certain(e)s d'entre vous préfèrent utiliser le logiciel "Clover Configurator" pour plus de facilité, voici comment entrer ces valeurs :
       
      Allez sur l'onglet "Kernel And Kext Patches" et faites comme ceci :
       
       
       
      *Ne faites pas attention sur le majuscule/minuscule, cela ne fait aucune différence
       
       
      Et pour injecter les kexts, aller sur l'onglet "System Parameters" et mettez l'option Inject Kexts sur Yes comme ceci :
       

       
       
      Voilà, vous n'avez plus qu'à enregistrer les ajustements, redémarrer votre pc et apprécier le résultat.
       
       
      MAIS ... seulement voilà ... il y a un problème ... 
       
      Quoi ? 
       
      Initialement, les kexts ne sont pas présents dans le kernelcache à cause de "OSBundleRequired=Safe Boot" (ils ne sont pas chargés en local par défaut mais en mode sans échec) et donc le patchage "à la volé" (on the fly) ne fonctionnera pas.
       
      Donc quoi, tout ça pour rien ?
       
      Non, bien-sûr, voici l'astuce pour remédier à cela :
       
      Dans un premier temps, il vous faut booter l'OS sans kernelcache. Si vous utiliser Clover Configurator, il vous suffit juste de cocher l'option "No Caches" dans l'onglet "System and Parameters" ou bien vous le faites directement dans votre config.plist :
      <key>SystemParameters</key> <dict>       <key>InjectSystemID</key>       <true/>       <key>InjectKexts</key>       <string>Yes</string>       <key>NoCaches</key>       <true/> </dict> Ceci aura donc pour effet de bloquer kernelcache et obliger boot.efi de charger le kernel et les kexts séparément. Clover et FSInject vont ensuite intercepter tous les chargements des kexts par boot.efi et changer "OSBundleRequired=Safe Boot" en "OSBundleRequired=Root" à la volé (on the fly) et forceront boot .efi à charger les kexts. Et ensuite dans un second temps, Clover va patcher l'Info.plist de ces deux kexts et la partie binaire de ATIRadeonX2000, kernel va les charger et ils seront rattachés à votre carte graphique.
       
      Une fois ceci fait (donc les kexts utilisés), il vous suffit de faire sudo touch /System/Library/Extensions. Ceci créera un nouveau kernelcache qui cette fois-ci contiendra vos kexts utilisés. Ensuite il ne vous reste plus qu'à redémarrer normalement (en décochant l'option No Caches dans Clover Configurator) et le patch fonctionnera à merveille.
       
       
      Oui, mais ... là aussi ...
       
      Quoi encore ?
       
      Seulement voilà, pour une raison ou une autre, il peut arriver que kernelcache se reconstruit tout seul et le patch "à la volé" ne fonctionne plus.
       
      Alors je fais quoi moi en attendant ?
       
      L'astuce la plus efficace pour le moment est d'injecter les infos de vos kexts à l'intérieur de l'Info.plist de FakeSMC.kext comme des IOKitPersonalities additionnels.
       
      ????Kézako????
       
      Ces infos vous les trouverez dans l'Info.plist de ces 2 kexts, sous IOKitPersonalities. Les voici :
       
      Pour AMD4800Controller.kext
      <key>Controller</key> <dict>         <key>ATY,Cardinal</key>         <dict>                 <key>aty_config</key>                 <dict>                         <key>CFG_NO_PP</key>                         <true/>                 </dict>          </dict>          <key>CFBundleIdentifier</key>          <string>com.apple.kext.AMD4800Controller</string>          <key>IOClass</key>          <string>AMD4800Controller</string>          <key>IOMatchCategory</key>          <string>IOFramebuffer</string>          <key>IOName</key>          <string>AMD4800Controller</string>          <key>IOPCIMatch</key>          <string>0x94401002 0x944a1002</string>          <key>IOProbeScore</key>          <integer>65050</integer>          <key>IOProviderClass</key>          <string>IOPCIDevice</string>         <key>aty_config</key>          <dict>                 <key>CFG_NO_PP</key>                  <false/>                  <key>CFG_PAA</key>                  <integer>0</integer>                  <key>CFG_USE_USCN</key>                  <false/>          </dict>          <key>aty_properties</key>          <dict>                  <key>PP_GFXClockGatingEnabled</key>                  <integer>1</integer>          </dict> </dict> Et pour ATIRadeonX2000.kext
      <key>ATIRadeonX2000</key> <dict>         <key>ATIEnableWideBlitSupport</key>         <true/> <key>ATIUseTearingWideBlit</key> <false/> <key>CFBundleIdentifier</key> <string>com.apple.ATIRadeonX2000</string> <key>GpuDebugPolicy</key> <integer>0</integer> <key>IOCFPlugInTypes</key> <dict> <key>ACCF0000-0000-0000-0000-000a2789904e</key> <string>ATIRadeonX2000GA.plugin</string> </dict> <key>IOClass</key> <string>ATIRadeonX2000</string> <key>IODVDBundleName</key> <string>ATIRadeonX2000VADriver</string> <key>IOKitDebug</key> <integer>0</integer> <key>IOMatchCategory</key> <string>IOAccelerator</string> <key>IOPCIMatch</key> <string>0x94001002 0x94011002 0x94021002 0x94031002 0x95811002 0x95831002 0x95881002 0x94c81002 0x94c91002 0x95001002 0x95011002 0x95051002 0x95071002 0x95041002 0x95061002 0x95981002 0x94881002 0x95991002 0x95911002 0x95931002 0x94401002 0x94421002 0x944A1002 0x945A1002 0x94901002 0x949E1002 0x94801002 0x95401002 0x95411002 0x954E1002 0x954F1002 0x95521002 0x95531002 0x94a01002</string> <key>IOProviderClass</key> <string>IOPCIDevice</string> <key>IOSourceVersion</key> <string>8.24.11</string> <key>IOVARendererID</key> <integer>16908288</integer> <key>sensor-properties</key> <array> <dict> <key>device_type</key> <data> Z3B1LXNlbnNvcg== </data> <key>location</key> <string>GPU</string> <key>name</key> <string>gpu-sensor</string> <key>polling-period</key> <data> AAAAAQAAAAA= </data> <key>reg</key> <data> AAAAAg== </data> <key>sample-period</key> <data> AAAAAACYmAA= </data> <key>sensor-id</key> <data> AAAABg== </data> <key>version</key> <data> AAAAAg== </data> <key>zone</key> <data> AAAAAg== </data> </dict> </array </dict>  
      Et voici donc l'Info.plist de FakeSMC.kext dans son intégrité, vous pouvez jeter un oeil, histoire de voir à quoi cela ressemble :
       
      FakeSMC_Info.plist.zip
       
      Et pour les moins casse-têtes, voici FakeSMC.kext modifié que j'utilise pour charger les 2 kexts :
       
      FakeSMC.kext.zip
       
       
      Voilà, avec ceci, vous n'aurez plus besoin de savoir si oui ou non les kexts sont dans le kernelcache.
       
       
      Crédits attribués à :
       
      netkas  pour son incontournable QE_CI Exotic patch (même s'il n'importe plus son support)
       
      Slice  & co. pour leur bébé nommé Clover
       
      dmazar  pour son astuce avec FakeSMC.kext   (pour plus d'info, voir ici)
       
      duffs (rarement ici, plus sur le site de netkas) pour son astuce de comment patcher la partie binaire avec Clover, ce fût lors de la sortie de OS X Mavericks DP1
       
      nyolc8  pour le support de QE_CI Exotic patch pour Mavericks
       
      fantomas1  pour ......... pour ... quoi déjà ? Ah ben non ... non ... pour rien ...
    • By Slice
      Now I want to add vector graphics support in Clover. See rev 4560 and later.
      It is not working yet but designers may begin to create Vector Themes.
      It supposed to consist of SVG elements and has design size. It will be rendered to any screen size scaled from design size.
       
      What application in macOS can create SVG graphics?
      Inkscape is not working in macOS 10.11+. Pity.
      LibreOffice Draw works with SVG but buggy.
      Boxy SVG cost 10$ but looks good enough. It creates the best in simplicity files and have more then enough features.
      Illustrator is good but expensive.
       
      How to improve SVG file?
      Clover has restricted support for SVG. It is your job to make compatible file and as small as possible to speedup rendering.
      Some helps:
      Help:Inkscape – From invalid to valid SVG Inkscape files
      From invalid to valid SVG Adobe Illustrator files
      From invalid to valid SVG files of other editors: BKchem, ChemDraw and CorelDRAW
      Help:Illustrator – Assistance with creating and saving SVG images in Adobe Illustrator that will pass W3C validation
      User:Quibik/Cleaning up SVG files manually
      Later I will write own instructions specific to Clover abilities.
       
      How to create SVG fonts?
      You can google to find ready-to-use SVG fonts.  I found some problems with too beaty fonts: slow rendering and overflow crash. Be careful.
      You can get ttf or otf fonts and convert them into svg by using online WEB services. Not a problem to google.
      But then I want to find a way to simplify the font to reduce a size and speedup rendering.
      You can create own font by FontForge It is opensource and available for Windows, Mac and GNU+Linux. It creates otf font which you can convert to svg font.
       
       
    • By ErmaC
      Please be advised that this is not a discussion topic.
       

      This topic is a "direct" line of communication between the Developers of Clover (Clover Team).
      Unless a Developer/Coder asks for more information, all the critical information of a post should be contained in the subject and first post.
      Every post will be responded to in some fashion before being locked.
       
       
       
       

      Invalid Posts
      Since we are strictly interested in issue reports on this topic, the following post/reply are likely to be deleted immediately:
      1. Discussion topic aka OFF-TOPIC (What do you all think?)
      2. Invalid issue reports
      3. Feedback / Suggestion threads.
      4. Posts requesting information about the bootloader.
      5. Posts made on other forums (Don't spam.)
      6. "Accomplishment" threads, threads to advertise screenshots unrelated to bug reports.
      7. Posts requesting status updates on existing issues.
       
       
×