Jump to content

nForce OS X Mavericks (10.9) APP STORE DOWNLOAD INSTALL GUIDE on a Series 6 or 7 nForce chipset / Intel CPU MOBO

nForce chipset + Intel CPU nForce 650i and 650i Ultra nForce 750i and 780i nForce 790i and 790i Ultra nForce 680i Possibly nForce 630i

  • Please log in to reply
152 replies to this topic

#1
verdant

verdant

    InsanelyMac V.I.P.

  • Gurus
  • 5,570 posts
  • Gender:Male
  • Interests:At home, I have the following computers......
    >
    >
    >

nForce OS X Mavericks (OS X 10.9) APP STORE DOWNLOAD INSTALL GUIDE

on a Series 6 or 7 nForce chipset / Intel CPU MOBO

 

 

*************************************************************

 

GUIDE CONTENTS

 

*************************************************************

 

OS X Mavericks 10.9 FREE RETAIL is now running on my Asus P5N32-E SLI Plus nForce 650i MOBO, after installing to both MBR and GPT internal HDDs via my USB flash drive set up for GPT or MBR installation....   :thumbsup_anim:

 

So, my Install Guide is now UNDER CONSTRUCTION starting with Post #1......being typed from OS X Mavericks....... :construction:

 

Apologies for the slow completion of the guide but I have little free time and that is only on weekends......

 

Thanks

verdant

 

NOTE - Text in Black in this Install Guide is not to be followed yet as part of the Install Guide as it is subject to re-writing and/or removal where no longer valid or relevant etc.

 

 

Post #1 - How to Prepare for Installing OS X Mavericks on a HDD

 

Introduction

 

Download Links 

 

Acknowledgements

 

Methods for

 

[1] Enabling the download of OS X Mavericks 10.9 FREE RETAIL from the Apple App Store - to follow

 

[2] Making a USB Flash Drive GPT/MBR Installer for OS X Mavericks 10.9:

 

Part A. Enabling Snow Leopard running in 64bit mode, or Lion or Mountain Lion running in default 64bit mode on an nForce MOBO for downloading OS X Mavericks FREE RETAIL from the Apple App Store



 

Part B. Making a Bootable GPT Partitioned USB Flash Drive OS X Mavericks 10.9 GPT/MBR Installer

 

 

Post #2 - How to Install OS X Mavericks on a HDD

 

USB and DVD Installer Methods for Installing OS X Mavericks on a HDD Volume (GPT or MBR):

 

Part C. Installing a Bootable OS X Mavericks (OS X 10.9) System on either a GPT Partitioned Hard Drive Volume OR a MBR Partitioned Hard Drive Volume Using a Bootable GPT/MBR USB Flash Drive Installer

 

Part D. Cloning a Bootable OX Mavericks 10.9 system installed on a GPT/HFS+ HDD (e.g. external USB HDD) to an internal HDD MBR/HFS+ OS X target volume

Part E. Installing a Bootable OS X Mavericks 10.9 system on either a GPT Partitioned Hard Drive Volume OR a MBR Partitioned Hard Drive Volume Using verdant's OS X Mavericks 10.9 Dual Layer DVD GPT/MBR Installer

 

 

Post #3 - nVidia Graphics Card Operation in OS X Mavericks

 

Getting an nVidia graphics card working in Mavericks

 

Generating and Modifying an EFI Graphics String for Mavericks

 

Indications that Core Image (CI) and Quartz Extreme (QE) are both enabled in Mavericks

 

Obtaining the NVCAP data string from your nVidia graphics card BIOS via Windows

 

Inserting nVidia Graphics Card Hardware Matching Device ID into nVidia Graphics Kexts

 

 

Post #4 - Generating and Modifying the OS X Mavericks DSDT.aml File for Your Own nForce MOBO

Device (RTC) fix for the CMOS Reset issue

DTGP Method patch to enable use of other patches in the DSDT.aml file

Device (HPET) fix to enable the removal of NullCPUPowerManagement.kext from /Extra/Extensions/ or /System/Library/Extensions/ and the loading of AppleIntelCPUPowerManagement.kext

Device (LPCB) patch insertion into the DSDT.aml file to enable Native Power Management in OS X Mavericks

Device (TMR) and Device (PIC) fixes to prevent audio "stuttering" when Native Power Management in OS X is enabled, i.e. after SpeedStepping with C-states is enabled


Post #5 - How to Enable Natural Power Management ("vanilla SpeedStepping") in OS X Mountain Lion (and OS X Lion and OS X Snow Leopard) on an nForce chipset + Intel CPU MOBO

 

Post #6 - OS X Mavericks Installation / Boot / Operation Issues

 

Issue 1. [PCI configuration begin] bootup error - proposed solutions

 

Issue 2. Setting up Builtin Ethernet manually / LAN0 / (en0) - proposed solutions

 

 

Post #7 - Getting Audio Working in OS X Mavericks

 

Asus SupremeFX II Audio Card (Analog Devices AD1988B 8-Channel High Definition Audio chipset/CODEC)

 

 

Post #8 - Peripheral Devices on nForce chipset + Intel CPU MOBOs

Device 1. Asmedia 106x SATA Controller Ver 0.95 AHCI Mode
 

Issue 1. Displayed in System Report as "Generic AHCI Standard Controller:" and "Vendor: Generic"

Issue 2. Updating the ASM1061 firmware from version 0.89 to version 0.95 and then 0.95.1

Issue 3. Resolvable Issues when the Asmedia SATA Controller is connected to one or more SATA Optical Drives

 

 

*************************************************************

 

INTRODUCTION

 

*************************************************************

 

 

*************************************************************

 

DOWNLOADS

 

*************************************************************

 

Insanelymac Download Link for verdant_Mavericks_Support_Files_v1.0

 

Attached File  verdant_Mavericks_Support_Files_v1.0.zip   136.33MB   1665 downloads

 

 

verdant_Mavericks_Support_Files_v1.0 Contents

 

>> 64bit Kexts for /System/Library/Extensions/

ACPIMonitor.kext

AD1998b.FIX.kext

AppleHDA.1062.kext

AppleNForceATA.imk64bit.kext

AppleRTC.Mavericks.Patched.kext

EvOreboot.kext

FakeSMC.kext

IntelCPUMonitor.kext

IntelThermal.kext

nForceLAN.0.64.5.kext

NullCPUPowerManagement.kext

NVClockX.kext

NVEnabler 64.kext

SuperIOFamily.kext

VoodooHDA.kext (patched for AD1988B by oldnapalm)

 

>> Applications

Chameleon Wizard

Kext Wizard

SMC Monitor

 

>> Chameleon Bootloader

Chameleon Bootloader Insanelymac Download Link

 

>> Changelog for verdant_Mountain_LIon_Support_Files_v1.0.rtf

 

>> CUDA 5.5.28

cudadriver-5.5.28-macos.dmg - this is the image file for v5.5.28 CUDADriver.pkg

 

>> EFI Graphics String Apps

EFIStudio_GTX.zip

EFIStudio.1.1.zip

OSX86Tools_1.0.150.zip

plist_gfxutil.zip

 

>> FakeSMC 

FakeSMC (3.1.0) - Revision 493. Made by mojodojo

Release 10.6 - only use the HWSensor kexts appropriate for your hardware

SMC_Stat_i - this is a SMC monitor menu bar app

 

>> MaLd0n Extra Folder

Extra_Folder.zip - this is the .zip file for MaLd0n's Extra Folder.pkg

 

>> Pure 64bit Extra Kexts

AHCIPortInjector.kext

AppleACPIPS2Nub.kext

ApplePS2Controller.kext

ApplePS2Keyboard.kext

ApplePS2Mouse.kext

ApplePS2Trackpad.kext

ATAPortInjector.kext

AtherosFix.kext

FakeSMC.kext

JMicron36xATA.kext

JMicron36xSATA.kext

NullCPUPowerManagement.kext

OpenHaltRestart.kext

 

 

*************************************************************

 

ACKNOWLEDGEMENTS

 

*************************************************************

 

PLEASE NOTE that ALL CREDIT goes (in no particular order and both historically and currently) the original developers of the included applications/kexts/bootloaders and boot files etc:

 

 

In /System/Library/Extensions/

 

NullCPUPowerManagement.kext - David Elliott

AD1998b.FIX.kext - THe KiNG

AppleNForceATA.imk64bit.kext - MeDevil for original kext AND imk for the working 64bit version

EvOreboot.kext - EvO Team

FakeSMC.kext – netkas, Slice

nForceLAN.0.64.5.kext – eno

VoodooHDA patched for AD1988B - oldnalpalm

 

In boot sector, / and in /Extra/

 

Chameleon 2.2 svn r2266

 

Thanks to everyone involved in the development of Chameleon 2.2 svn r2266, making it a compatible bootloader for Mavericks......!

 

Chameleon Developers Team : http://forum.voodooprojects.org

 

zef, Turbo, dfe, netkas, mackerintel, mercurysquad, fassl, Kabyl, Crazor, Dense, kaitek, iNDi, munky, JrCs, asereBLN, rekursor, mozodojo, meklort, AnV, valv, AzimutZ, Slice, cosmo1t, cparm, Conti

 

With thanks to :

 

bumby, kalyway, Krazubu, Eddie11c, JaS, fassl, XyZ, SMF, flama, Galaxy, sckevyn, MasterChief, smith@@, blackosx, DHP, nawcom, scorpius, macman, dmazar

 

Chameleon 2.2 svn r2266 Package :

 

kalyway, AzimutZ, blackosx, ErmaC (who submitted the Chameleon 2.2 svn r2266 Installer PKG and Binaries format (Manual install) to IM Downloads), scrax, JrCs

 

 

Thanks also to MaLd0n for the MacPro3,1 SMBIOS.plist

 

Thanks also to oldnapalm for the Mavericks MBR patch 10.9 GM (13A603)

 

Apologies to anyone I have forgotten, or do not know to mention, or have yet to mention in the above credits......

 

 

*************************************************************

 

 

 

 

*************************************************************

 

Part B. Making a Bootable GPT Partitioned USB Flash Drive GPT/MBR OS X Mavericks 10.9 Installer

 

*************************************************************

 

Stage 1 - Making a Bootable GPT Partitioned USB Flash Drive GPT OS X Mavericks 10.9 Installer

 

1. You will need:

 

[1] Access to a working Mac or Hack x86 OS X Snow Leopard 10.6.x or OS X Lion 10.7.x or OS X Mountain Lion 10.8.x

 

(I am assuming that you already have OS X Snow Leopard 10.6.8 or OS X Lion 10.7.5 or OS X Mountain Lion 10.8.5 installed and running)

 

[2] A 8GB USB flash drive (memory stick)

 

[3] To be able to download OS X Mavericks (FREE RETAIL) from the Apple App Store. See Part A.

 

[4] To download my "verdant_Mavericks_Support_Files_v1.0.zip" folder

 

The “Install OS X Mavericks.app” installer app icon will show up in the Dock.

 

If it does, then the installer should also show up in your Applications folder.

 

* DO NOT click on the icon NOR right-click on the icon and select Open

* DO NOT double-click on its icon in the Applications folder 

 

 

2. Extracting Necessary Files from Mavericks Installer App

 

[1] Boot into Snow Leopard or OS X Lion or OS X Mountain Lion and go to the Applications folder and find Install OS X Mavericks.app WITHOUT clicking on the icon NOR right-click on the icon and selecting Open

 

[2] Unhide all files via a Terminal command:

 

***********************************************************

 

Terminal commands to show/hide hidden and system files:

 

To show hidden and system files:

 

defaults write com.apple.finder AppleShowAllFiles TRUE

killall Finder

 

 

To hide hidden and system files:

 

defaults write com.apple.finder AppleShowAllFiles FALSE

killall Finder

 

***********************************************************

 

Or, you can download and run TinkerTool ......select the Finder options: 'Show hidden and system files' option and then click Relaunch Finder to unhide......and deselect the Finder options: 'Show hidden and system files' option and then click Relaunch Finder to hide......

 

[3] Right-click on the Install OS X Mavericks.app installer icon and select Show Package Contents.

 

Open the Contents folder and the SharedSupport folder within it, and look for InstallESD.dmg

 

[4] Open i.e. mount InstallESD.dmg and look for BaseSystem.dmg……LEAVE the Mac OS X Install ESD window open…….

 

 

3. Preparing the USB flash drive as a Mac bootable device volume

 

[1] Plug in the USB flash drive and then using the Snow Leopard or Lion or Mountain Lion Disk Utility, partition/format it as a single GPT/HFS+ volume named OSX_Lion_USB_Installer (or your chosen name without spaces) as follows:

 

In the Disk Utility sidebar, highlight your USB flash drive device icon

 

In the Disk Utility main window, click on the Partition tab and select to partition as 1 volume, using a name with no spaces and format as Mac OS Extended (Journaled)……

 

Then click on Options button -> select GUID Partition Table (GPT) -> click Apply

 

Doing this will make the USB flash drive bootable on a Mac. Note that this operation will erase everything on the drive.

 

 

4. Installing necessary /Extra/ and directory files and the Chameleon 2.2 svn r22662 bootloader onto the partitioned/formatted USB flash drive

 

[1] In the Disk Utility main window, click on the Restore tab to load the BaseSystem.dmg onto the OSX_Mavericks_USB_Installer volume.....doing this puts a base OS X Mavericks system on the USB flash drive volume……

 

Choose the BaseSystem.dmg file as the Source by 'drag and dropping' it from the Mac OS X Install ESD window into the Source Window (note that a '+ in green circle' appears momentarily)

 

Choose your USB flash drive volume icon as the Destination by 'drag and dropping' it from the Disk Utility sidebar into the Destination window (note that a '+ in green circle' appears momentarily).

 

Click the Apply button and it will create your bootable USB drive. Note that Erase destination checkbox will be ticked by default, or applied by default.

 

The USB flash drive device name will be automatically changed to OS X Base System in the sidebar……

 

[2] On the USB flash drive volume, open the System folder and double-click on the Installation folder within it…..this opens an Installation folder window….

 

Right-click on the Packages alias icon and select Move to Trash

 

Go to the open Mac OS X Install ESD window and 'drag and drop' the Packages folder in the window into the open Installation folder window……the 4.8 GB Packages folder will take about 10 or so minutes to copy over……

 

Now go to the open Mac OS X Install ESD window and open the Packages folder in the window, and locate the BaseSystemBinaries.pkg.

 

Use Pacifist (current version is Pacifist 3.2.2) to extract the mach_kernel file from the BaseSystemBinaries.pkg to the root directory, i.e. / of the OS X Base System USB flash drive volume....i.e. into the open OS X Base System Window……

 

[3] Note that the USB flash drive OS X Base System volume /System/Library/Extensions/ folder does not contain all the graphics kexts that the installed OS X Mavericks /System/Library/Extensions/ does. The OS X Base System volume /System/Library/Extensions/ folder is missing the following kexts, bundles and plugins: 

 

Spoiler

 

Thus, depending on your installed graphics card i.e. nVidia or ATI, you may need to use Pacifist to extract the relevant kexts, bundles and plugin from /Volumes/OS\ X\ Install\ ESD/Packages/Essentials.pkg into the USB flash drive OS X Base System volume /System/Library/Extensions/ folder, in order for your GPU and display to function properly when booting from the Bootable GPT Partitioned USB Flash Drive OS X Mavericks 10.9 Installer, i.e. not present you with a black display screen at worst, or less worse, an incorrect and fixed display resolution, on reaching the OS X Mavericks Installer window.

 

Since I have an Inno3D GeForce 9800GT 512MB graphics card, I had to extract the following files into my USB flash drive OS X Base System volume /System/Library/Extensions/ folder, so that booting the USB installer did not just present me with a black display screen on reaching the OS X Mavericks Installer window:

 

GeForce.kext

GeForceGA.plugin

GeForceGLDriver.bundle

GeForceVADriver.bundle

 

Please be note that being able to use GraphicsEnabler=Yes in org.chameleon.Boot.plist for the same graphics card under different OS X versions via different Chameleon bootloader versions/revisions is not a given. 

 

For example, with my Inno3D GeForce 9800GT 512MB graphics card, to get full CI/QE and changeable display resolutions, the situation is as follows:

 

OS X Leopard 10.5.8 - GraphicsEnabler=No and NVEnabler.kext

OS X Snow Leopard 10.6.8 - GraphicsEnabler=Yes and so no NVinjector kext such as NVEnabler64.kext

OS X Lion 10.7.5 - GraphicsEnabler=No and NVEnabler64.kext

OS X Mountain Lion 10.8.5 - GraphicsEnabler=No and either a <key>device-properties</key> custom hex entry in org.chameleon.Boot.plist, that I generated using OSX86 Tools, or NVEnabler 64.kext, or DSDT GFX0 section patch.

OS X Mavericks 10.9 - GraphicsEnabler=No and a DSDT GFX0 section patch.

 

For help with:

 

1. ATI graphics cards go here 

 

2. nVidia graphics cards go to post #3 in this topic for single nVidia graphics card use

 

3. Multiple nVidia graphics card(s) and/or displays go here.

 

4. For help with mixed multiple ATI and/or nVidia graphics cards and /or multiple displays, Google is your friend......as are aqua-mac, netkas, and others.......  

 

[4] Run the Chameleon 2.2 svn r2266.pkg installer (download from link given above) and click on the Continue button in the Chameleon 2.2 svn r22662 Bootloader Installer window…….then click Continue and Continue again and Agree…..then in the Standard Install window click Change Install Location and select the USB flash drive OS X Base System volume in the Select a Destination window and click Continue……then click Install…..after a hopefully successful install, click Close....

 

[5] Go back to the open OS X Base System Window……the Chameleon bootloader installer should have created the /Extra/ folder……BUT you may have to create them manually afterward (as I did)……

 

[6] Copy across from your running 64bit mode Snow Leopard, or Lion, or Mountain Lion system, your MOBO's OS X DSDT.aml file into the open target HDD OS X Mavericks window, i.e. the target HDD volume's root i.e. / directory…….

 

[7] Copy across from your running 64bit mode Snow Leopard, or Lion, or Mountain Lion system, or from the verdant_Mavericks_Support_Files_v1.0 folder, into /Extra/ on the USB flash drive Mac OS X Base System volume, the following .plist files:

 

smbios.plist for MacPro3,1 (use the one from MaLd0n's Lion installation via USB stick using Chameleon, DP4, GM and FINAL topic…….), or whatever MacProx,y designation matches your CPU....

 

org.chameleon.Boot.plist (assuming that you are using a recent/current Chameleon boot loader version later than v2.0 r11xx, or a version 2.1 or 2.2 revision)

 

modules folder (containing e.g. FileNVRAM.dylib)

 

Also copy across (if you wish) your Chameleon bootloader Themes folder from your running 64bit mode Snow Leopard, or Lion, or Mountain Lion system......

 

[8] Copy the following kexts in /Extra/Extensions/ on your running 64bit mode Snow Leopard, or in /System/Library/Extensions/ on your Lion system, or Mountain Lion System, or from the verdant_Mavericks_Support_Files_v1.0 folder, into /System/Library/Extensions on the USB flash drive OS X Base System volume...

 

FakeSMC.kext

EvOreboot.kext

NullCPUPowerManagement.kext - ONLY if you are NOT booting your USB OS X Base System Flash Drive installer with your MOBOs DSDT.aml file, that is patched for OS X Natural Power Management, in the root directory

AppleRTC.Mavericks.Patched.kext

AppleNForceATA.imk64bit.kext

AD1998b.FIX.kext or VoodooHDA.kext (for AD1998b) - ONLY if this is the audio chipset/codec of your nForce chipset + Intel CPU MOBO

 

You may also have AppleHDA.10.6.2.kext, FakeSMC.kext and nForceLAN.0.64.5.kext in in /Extra/Extensions/ on your running 64bit mode Snow Leopard, or in /System/Library/Extensions/ on your Lion system, or Mountain Lion System....

 

Note the later versions/revisions of FakeSMC.kext v3.0 and later by mojodojo can function from /Extra/Extensions/ or from /System/Library/Extensions/ but be aware that earlier versions/revisions of FakeSMC.kext can only function from /System/Library/Extensions/ - hence step [9] below:

 

[9] If you have AppleHDA.10.6.2.kext, FakeSMC.kext and nForceLAN.0.64.5.kext in /System/Library/Extensions/ on your running 64bit mode Snow Leopard, or Lion, or Mountain Lion system, then these need to copied from there, or from the verdant_Mavericks_Support_Files_v1.0 folder, into /System/Library/Extensions/ on the USB flash drive OS X Base System volume……

 

[10] Having added AppleHDA.10.6.2.kext, FakeSMC.kext and nForceLAN.0.64.5.kext to /System/Library/Extensions/ on the USB flash drive OS X Base System volume, you need to use Terminal to reset the kexts ownership and permissions and rebuild the kernelcache file etc.....alternatively, you can use janek202's Kext Wizard for a Terminal-free life.......

 

In Terminal type:

sudo chown -R root:wheel /Volumes/OS\ X\ Base\ System/System/Library/Extensions
sudo chmod -R 755 /Volumes/OS\ X\ Base\ System/System/Library/Extensions
sudo touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions

followed by

sudo chflags nouchg /Volumes/OS\ X\ Base\ System/System/Library/CoreServices/boot.efi

[11] Close all open folders within the OS X Base System folder and in the Terminal type:

sudo chown -R 0:0 /Volumes/OS\ X\ Base\ System

[12] Close Terminal and then go to /System/Library/Caches/com.apple.kext.caches/Startup and delete all the files within Startup, e.g. kernelcache

 

[13] Close the OS X Base System Window and boot from the USB flash drive OS X Base System volume by pressing F8 at boot-up to bring up the PC BIOS "Boot Menu", then selecting the USB OS X Base System Flash Drive and pressing Enter.

 

[14] At the Chameleon boot prompt, type -v -f and press Enter.

 

[15] If you experience the [PCI configuration begin] error on booting from the USB OS X Base System Flash Drive installer, then see post #4, which gives four proposed solutions to this error.......

 

Stage 2 - Making a Bootable GPT Partitioned USB Flash Drive GPT/MBR OS X Mavericks 10.9 Installer

 

The following procedure assumes that you have already followed "Part B. Making a Bootable GPT Partitioned USB Flash Drive GPT/MBR OS X Mavericks 10.9 Installer" Stage 1 of this guide, and so now have a working bootable GPT USB Flash Drive GPT OS X Mavericks 10.9 Installer......

In order for you to install OS X Mavericks 10.9 onto your target HDD volume partitioned/formatted as MBR/HFS+, you need to use a modified OSInstall.mpkg package and OSInstall Unix executable file in place of the ones that the OS X Mavericks Installer on your bootable GPT USB Flash Drive Installer uses for installing OS X Mavericks to a target HDD volume partitioned/formatted as GPT/HFS+ ......

I have used as the starting point, the OSInstall.mpkg and OSInstall framework which have been MBR patched for OS X Mavericks by oldnapalm (based on nawcom's preceding work). 

 

However, I have then modified the OSInstall.mpkg in order to remove the Board-ID and RAM checks, and add some Custom Install Options too.

 

Attached File  verdant Patched oldnapalm MBR Modified OS X Mavericks OSInstall Package.zip   841.06KB   90 downloads

Step 1. Inserting the verdant patched oldnapalm MBR modified OS X Mavericks OSInstall.mpkg package and the oldnapalm MBR modified OS X Mavericks OSInstall Unix executable file in place of the ones included in the downloaded OS X Mavericks Installer on your bootable GPT USB Flash Drive Installer.

Download and unarchive

 

(i) the Mavericks MBR patch 10.9 GM (13A603) ….the unarchived folder contains the MBR modified OS X Mavericks OSInstall.mpkg package and OSInstall Unix executable file, and

 

(ii) the verdant Patched OSInstall.mpkg Mavericks v2.zip file.....the unarchived folder contains the verdant patched oldnapalm MBR modified OS X Mavericks OSInstall.mpkg package.

The procedure for installing the verdant patched oldnapalm MBR modified OS X Mavericks  OSInstall.mpkg package and the oldnapalm MBR modified OSInstall Unix executable file on your bootable GPT USB Flash Drive Installer in place of the original OS X Mavericks Installer versions is as follows:

1. Unhide the hidden and systems files on your OS X Mountain Lion USB Flash Drive Installer, named OS X Base System, using Terminal commands or Tinker Tool (see Part C. above)

2. Go to Terminal and then:

[1] Either type:

cd /Volumes/OS\ X\ Base\ System/System/Installation/Packages

or type

cd

and press the 'Space Bar', and then having navigated to System, then to Installation, then to Packages, 'drag and drop' the Packages folder into Terminal……

[2] Type the following:

sudo mv OSInstall.mpkg OSInstall.mpkg.GPT
ls

Note that you have now renamed the original file as shown by the 'ls' command…..

[3] Either type:

cd /Volumes/OS\ X\ Base\ System/System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A

or type

cd

and press the 'Space Bar', and then having navigated to System, then to Library, then to PrivateFrameworks, then to Install.framework, then to Frameworks, then to OSInstall.framework, then to Versions, and finally to the A folder, 'drag and drop' the A folder into Terminal……

[4] Type the following:

sudo mv OSInstall OSInstall.GPT
ls
exit

Note that you have now renamed the original file as shown by the 'ls' command…..

****************************************************

As a reminder if ever you wish to revert back to the original GPT installer versions......simply rename the original files by removing the .GPT extensions after having renamed the patched files with the .MBR extension, via Terminal:

cd /Volumes/OS\ X\ Base\ System/System/Installation/Packages
sudo mv OSInstall.mpkg OSInstall.mpkg.MBR
sudo mv OSInstall.mpkg.GPT OSInstall.mpkg

followed by

cd /Volumes/OS\ X\ Base\ System/System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A
sudo mv OSInstall OSInstall.MBR
sudo mv OSInstall.GPT OSInstall
exit

****************************************************

3. Then either 'drag and drop' the chosen version of OSInstall.mpkg into /Volumes/OS\ X\ Base\ System/System/Installation/Packages .....(or use the 'cp' command via Terminal):

sudo cp -p -R /Users/"User Name"/Desktop/verdant\ Patched\ oldnapalm\ MBR\ Modified\ OS\ X\ Mavericks\ OSInstall\ Package/OSInstall.mpkg /Volumes/OS\ X\ Base\ System/System/Installation/Packages

4. Then 'drag and drop' OSInstall into /Volumes/OS\ X\ Base\ System/System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A......(or use the 'cp' command via Terminal):

sudo cp -p -R /Users/"User Name"/Desktop/System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A/OSInstall /Volumes/OS\ X\ Base\ System/System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A

5. Close all windows.......

6. Now follow Part C. in Post #2 to install OS X Mavericks onto your target HDD volume partitioned/formatted as either GPT/HFS+ or as MBR/HFS+ :

 

 

*************************************************************



#2
verdant

verdant

    InsanelyMac V.I.P.

  • Gurus
  • 5,570 posts
  • Gender:Male
  • Interests:At home, I have the following computers......
    >
    >
    >

*************************************************************

Part C. Installing a Bootable OS X Mavericks (OS X 10.9) System on either a GPT Partitioned 
Hard Drive Volume OR a MBR Partitioned Hard Drive Volume Using a Bootable GPT/MBR USB Flash Drive Installer

 

*************************************************************

1. Preparing the target Hard Drive volume as a Mac bootable device volume

[1] Use the running Snow Leopard, or Lion, or Mountain Lion Disk Utility to partition/format your target HDD volume for OS X 10.9 as a EITHER

 

a GPT/HFS+ volume named OSX_10.9_GPT_A (or your chosen name without spaces)

 

OR

 

a MBR/HFS+ volume named OSX_10.9_MBR_A (or your chosen name without spaces)

 

****************************************************

VERY IMPORTANT TO CHECK : OS X target HDD ownership

****************************************************


Right-click on the target OS X HDD volume icon on your Desktop, and select Get Info. If the checkbox next to "Ignore ownership on this volume" is checked then click on the padlock symbol to authenticate and UNCHECK the checkbox.

Then to ensure that the target OS X HDD volume's root directory is owned by the root user, go to Terminal and type: (note that using 0:0 is equivalent to using root:wheel)
 

sudo chown 0:0 /Volumes/"your target OS X HDD volume name"

This is to make certain that the permissions are not scrambled after the installation of OS X.....and hence that you are able to boot from the OS X 10.9 hard drive........

[2] Now close all open windows on the Snow Leopard or Lion or Mountain Lion Desktop and any open applications.......

Reboot your PC and press the F8 key (or whichever key you need to) IMMEDIATELY after the message "Press DEL to enter SETUP, Press TAB to display BIOS POST message" or similar appears on-screen, in order to bring up the message "Loading Boot Menu......"

When the PC BIOS "Boot Menu" window appears on-screen, select the USB flash drive OS X Mavericks installer from the list of bootable drives presented in the "Boot Menu", and press Enter......

OR

Choose it from the list of bootable volumes presented by the Chameleon bootloader.....

Boot from the USB flash drive OS X Base System volume and follow the onscreen OS X Installer instructions to install OS X Mavericks onto the target HDD volume.....

[3] Re-boot back into OS X Snow Leopard or OS X Lion or OS X Mountain Lion and run the Chameleon 2.2 svn r2266 or 2269 pkg installer (download from link given above) and click on the Continue button in the Chameleon 2.2 svn r2266 or r2269 bootloader Installer window…….then click Continue and Continue again and Agree…..then in the Standard Install window click Change Install Location and select the target HDD OS X Mavericks volume icon in the Select a Destination window and click Continue……then click Install…..after a hopefully successful install, click Close…..

[4] Set up your video driver as you have done for running OS X 10.6.8 Snow Leopard in 64bit mode or OS X Lion 10.7.5 or OS X Mountain Lion 10.8.5 in default 64bit mode......

[5] Go back to the open target HDD OS X Mavericks System Window……the Chameleon bootloader installer should have created the /Extra/ directory and sub-folders……BUT you may have to create them manually afterward……

[6] Copy across from your running 64bit mode OS X Snow Leopard 10.6.8 system, or running OS X Lion 10.7.5 system, or OS X Mountain Lion 10.8.5 system, the DSDT.aml file into the open target HDD OS X Mavericks System Window, i.e. the target HDD volume's / directory…….

[7] Copy across from your running 64bit mode OS X Snow Leopard 10.6.8 system, or running OS X Lion 10.7.5 system, or OS X Mountain Lion 10.8.5 system, into /Extra on the target HDD volume, the following .plist files:

smbios.plist for MacPro3,1 (use the one from MaLd0n's Lion installation via USB stick using Chameleon, DP4, GM and FINAL topic…….), or whatever MacProx,y designation matches your CPU....

org.chameleon.Boot.plist (assuming that you are using a recent/current Chameleon boot loader version later than v2.0 r11xx, or a version 2.1 or a version 2.2 revision)

Also copy across (if you wish) your Chameleon bootloader Themes folder from your running 64bit mode OS X Snow Leopard 10.6.8 system, or running OS X Lion 10.7.5 system, or OS X Mountain Lion 10.8.5 system,  or from the folder....

[8] Copy the following kexts in /Extra/Extensions/ on your running 64bit mode Snow Leopard, or in /System/Library/Extensions/ on your running Lion or Mountain Lion system, or from the verdant_Mavericks_Support_Files_v1.0 folder, into /System/Library/Extensions/ in the open target HDD OS X Lion System Window……

FakeSMC.kext

EvOreboot.kext

NullCPUPowerManagement.kext 

(NullCPUPowerManagement.kext is not present or needed if you have already enabled, or are going to enable, Natural Power Management i.e. "vanilla SpeedStepping")

AppleNForceATA.imk64bit.kext

AD1998b.FIX.kext or VoodooHDA.kext 

(AD1998b.FIX.kext or VoodooHDA.kext are only present or needed if AD1988b the audio chipset/codec of your nForce chipset + Intel CPU MOBO; alternatively, you may have or need AppleHDA.10.6.2.kext for audio in /System/Library/Extensions/)

Then also copy the AppleRTC.Mavericks.Patched.kext from the verdant_Mavericks_Support_Files_v1.0 folder, into /System/Library/Extensions/ in the open target HDD OS X Mountain Lion System Window…

Alternatively, you can directly patch the installed OS X Mavericks AppleRTC.kext in /System/Library/Extensions/ in the open target HDD OS X Mountain Lion System Window, by running this perl script (courtesy of rayap modified by oldnapalm for  Mavericks) in Terminal, which has been posted by oldnapalm, which forces an unconditional jump over the rtcWrites() in updateChecksum() to prevent CMOS Resets:

sudo perl -pi -e 's|\x75\x2e\x0f\xb6|\xeb\x2e\x0f\xb6|' /System/Library/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC
sudo touch /System/Library/Extensions

N.B. If you have added the AppleRTC.Mavericks.Patched.kext from the verdant_Mavericks_Support_Files_v1.0 folder, into /System/Library/Extensions/ in the open target HDD OS X Mavericks System Window, 

then to ensure that this is the RTC kext that is loaded, rename the installed OS X Mavericks AppleRTC.kext in /System/Library/Extensions/ in the open target HDD OS X Mountain Lion System Window using the Terminal as follows:

sudo mv /Volumes/"your target OS X Mavericks HDD volume name"/System/Library/Extensions/AppleRTC.kext /Volumes/"your target OS X Mavericks HDD volume name"/System/Library/Extensions/AppleRTC.kext_Original

Note the later versions/revisions of FakeSMC.kext v3.0 and later by mojodojo can function from /Extra/Extensions/ or from /System/Library/Extensions/ but be aware that earlier versions/revisions of FakeSMC.kext can only function from /System/Library/Extensions/ - hence step [9] below:

[9] If you have AppleHDA.10.6.2.kext, FakeSMC.kext and nForceLAN.0.64.5.kext in /System/Library/Extensions/ on your running 64bit mode Snow Leopard system, or in /System/Library/Extensions/ on your running Lion or Mountain Lion system, then these kexts need to copied from there, or from the verdant_Mavericks_Support_Files_v1.0 folder, into /System/Library/Extensions/ in the open target HDD OS X Mountain Lion System Window……

[10] Having added these non-vanilla, i.e. non- Apple kexts, plus any others specific to your system; for example, I have added:

ACPIMonitor.kext
AppleNForceATA.imk64bit.kext

AppleRTL8169Ethernet.kext
AppleRTC.Mavericks.Patched.kext
EvOreboot.kext
FakeSMC.kext
IntelCPUMonitor.kext
IntelThermal.kext
nForceLAN.0.64.5.kext
NVClockX.kext
SuperIOFamily.kext
VoodooHDA.kext


to /System/Library/Extensions/ on the open target HDD OS X Mavericks System Window, you need to use Terminal to reset the kexts ownership and permissions and rebuild the kernelcache file……alternatively, you can use janek202's Kext Wizard for a Terminal-free life.......

In Terminal type:

sudo chown -R root:wheel /System/Library/Extensions
sudo chmod -R 755 /System/Library/Extensions
sudo touch /System/Library/Extensions
exit

Close Terminal and then go to /System/Library/Caches/com.apple.kext.caches/Startup and delete the files present within Startup….
 

invalidsignedkextalert.plist

IOKitPersonalities_x86_64.ioplist.gz

kernelcache

KextPropertyValues_OSBundleHelper_x86_64.plist.gz

loadedkextmt.plist

 

[11] Close the open target HDD OS X Mavericks System Window and boot from the target hard drive OS X Mavericks System volume......

[12] If you find that on shutting down OS X Mavericks and rebooting, that the CMOS has been "wiped clean" of your custom BIOS settings profile and the BIOS has reverted to using the in-built default BIOS settings, then reload your backed-up custom BIOS settings profile from its source (e.g. USB flash drive) and boot back into OS X Mavericks......

If this happens, then you have either

 

(i) not copied the AppleRTC.Mavericks.Patched.kext from the verdant_Mavericks_Support_Files_v1.0 folder, into /System/Library/Extensions/ in the open target HDD OS X Mavericks System Window, or

 

(ii) not directly patched the installed OS X Mavericks AppleRTC.kext in /System/Library/Extensions/ in the open target HDD OS X Mavericks System Window, by running this perl script in Terminal, which has been which has been posted by oldnapalm, which forces an unconditional jump over the rtcWrites() in updateChecksum() to prevent CMOS Resets:

sudo perl -pi -e 's|\x75\x2e\x0f\xb6|\xeb\x2e\x0f\xb6|' /System/Library/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC
sudo touch /System/Library/Extensions

N.B. If you have added the AppleRTC.Mavericks.Patched.kext from the verdant_Mavericks_Support_Files_v1.0 folder, into /System/Library/Extensions/ in the open target HDD OS X Mavericks System Window, 

then to ensure that this is the RTC kext that is loaded, rename the installed OS X Mavericks AppleRTC.kext in /System/Library/Extensions/ in the open target HDD OS X Mavericks System Window using the Terminal as follows:

sudo mv /Volumes/"your target OS X Mavericks HDD volume name"/System/Library/Extensions/AppleRTC.kext /Volumes/"your target OS X Mavericks HDD volume name"/System/Library/Extensions/AppleRTC.kext_Original
 

Now you need to again use Terminal to reset the kexts' ownership and permissions and rebuild the kernelcache file etc.....alternatively, you can use janek202's Kext Wizard for a Terminal-free life.......

In Terminal type:

sudo chown -R root:wheel /System/Library/Extensions
sudo chmod -R 755 /System/Library/Extensions
sudo touch /System/Library/Extensions
exit

Close Terminal and then go to /System/Library/Caches/com.apple.kext.caches/Startup and delete the files within Startup….
 

invalidsignedkextalert.plist

IOKitPersonalities_x86_64.ioplist.gz

kernelcache

KextPropertyValues_OSBundleHelper_x86_64.plist.gz

loadedkextmt.plist

 

[13] Close the open target HDD OS X Mavericks System Window and re-boot from the target hard drive OS X Mountain Lion System volume......

[14] Use the OS X Mavericks Disk Utility to repair the OS X Mavericks HDD system permissions......

 

N.B. If you experience the [PCI configuration begin] error on booting from the OS X Mountain Lion System installed on your target HDD volume, then see post #6, which gives four proposed solutions to this error.......

*************************************************************

*************************************************************

Part D. Cloning a Bootable OX Mavericks 10.9 system installed on a GPT/HFS+ HDD (e.g. external USB HDD) to your internal HDD MBR/HFS+ OS X target volume

*************************************************************

 

1. Simply use OS X Disk utility, or Carbon Copy Cloner, to clone a OX Mavericks 10.9 system installed on a GPT/HFS+ HDD (e.g. external USB HDD) to your internal HDD MBR/HFS+ OS X target volume........

2. Install the Chameleon 2.2 svn r2266 or r2269 pkg bootloader to your OS X Lion MBR/HFS+ partition/volume after cloning the OS X Lion system on your GPT/HFS+ HDD to your OS X Lion MBR/HFS+ partition/volume

3. Boot into the OS X Mavericks 10.9 system just installed on the MBR/HFS+ partition/volume.....

*************************************************************

*************************************************************

Part E. Installing a Bootable OS X Mavericks 10.9 system on either a GPT Partitioned Hard Drive Volume OR a MBR Partitioned Hard Drive Volume Using verdant's OS X Mavericks 10.9 Dual Layer DVD GPT/MBR Installer

*************************************************************

I have prepared the following guide for producing my OS X Mavericks 10.9 Dual Layer DVD MBR/GPT Installer for nForce MOBO owners who:

{a} who do not have ready access to an 8GB minimum size USB flash drive, 

{b} who are having difficulty booting their PC from a USB flash drive, or 

{c} who just like the idea of having an archival 'backup' installation method on an optical disk should their USB flash drive ever fail…….

 

NOTE:

 

The 3.19 GB size of the Essentials.pkg in the Packages folder in InstallESD.dmg means that an OS X Mavericks 10.9 Single Layer DVD MBR/GPT Installer cannot be simply produced for burning onto a single layer DVD of 4.7 GB capacity by just removing the AdditionalSpeechVoices.pkg package from the /System/Installation/Packages directory as was the case with OS X Mountain Lion.

 

I do not have the time nor the wish to create a "slimmed down" single layer DVD OS X Mavericks Installer, i.e. effectively a "distro", as it brings no advantages over a full system USB Installer or full system dual Layer DVD installer - if you need to use a DVD installer, then buy some dual layer DVD+R or DVD-R DL disks......

 

 

1. Creating a folder for my OS X Mavericks 10.9 Dual Layer DVD MBR/GPT Installer contents


[1] Boot into OS X Snow Leopard or OS X Lion or OS X Mountain Lion and go to the Applications folder and find Install OS X Mavericks.app WITHOUT clicking on the icon NOR right-click on the icon and selecting Open

[2] Unhide all files via a Terminal command:

***********************************************************

Terminal commands to show/hide hidden and system files:

To show hidden and system files:

defaults write com.apple.finder AppleShowAllFiles TRUE
killall Finder


To hide hidden and system files:

defaults write com.apple.finder AppleShowAllFiles FALSE
killall Finder

***********************************************************

Or, you can download and run TinkerTool......select the Finder options: 'Show hidden and system files' option and then click Relaunch Finder to unhide......and deselect the Finder options: 'Show hidden and system files' option and then click Relaunch Finder to hide......

[3] Create a folder on your Desktop called OS_X_10.9_Base_Sys_DLDVD and click to open it and leave it open.......

[4] Right-click on the Install OS X Mavericks.app installer icon and select Show Package Contents.

Open the Contents folder and the SharedSupport folder within it, and look for InstallESD.dmg

[5] Open i.e. mount InstallESD.dmg and look for BaseSystem.dmg……LEAVE the OS X Install ESD window open…….

[6] Open i.e. mount BaseSystem.dmg……LEAVE the BaseSystem window open…….

[7] 'Select All' files in the open BaseSystem window and copy them into the OS_X_10.9_Base_Sys_DLDVD folder that you created on your Desktop

[8] Open the copied-over System folder in the open OS_X_10.9_Base_Sys_DLDVD folder and double-click on the Installation folder within it…..this opens an Installation folder window….

[9] Right-click on the Packages alias icon and select Move to Trash

[10] Go to the already open OS X Install ESD window and 'drag and drop' the Packages folder in the window into the open Installation folder window……the 4.8 GB Packages folder will take a minute or two to copy over……

[11] Now go to the open OS X Install ESD window and open the Packages folder in the window, and locate the BaseSystemBinaries.pkg.

Use Pacifist (current version is Pacifist 3.2.3) to extract the mach_kernel file from the BaseSystemBinaries.pkg to the root directory, i.e. / of the OS X Base System USB flash drive volume....i.e. into the open OS X Base System Window……


[12] Note that the copied-over OS X Base System volume /System/Library/Extensions/ folder in the OS_X_10.9_Base_Sys_DLDVD folder does not contain all the graphics kexts that the installed OS X Mavericks/System/Library/Extensions/ does. 
 

The OS X Base System volume /System/Library/Extensions/ folder is missing the following kexts, bundles and plugins:

Spoiler


Thus, depending on your installed graphics card i.e. nVidia or ATI, you may need to use Pacifist to extract the relevant kexts, bundles and plugin from /Volumes/OS\ X\ Install\ ESD/Packages/Essentials.pkg into the USB flash drive OS X Base System volume /System/Library/Extensions/ folder, in order for your GPU and display to function properly when booting from the Bootable GPT Partitioned USB Flash Drive OS X Mavericks 10.9 Installer, i.e. not present you with a black display screen at worst, or less worse, an incorrect and fixed display resolution, on reaching the OS X Mavericks Installer window.

Since I have an Inno3D GeForce 9800GT 512MB graphics card, I had to extract the following files into my USB flash drive OS X Base System volume /System/Library/Extensions/ folder, so that booting the USB installer did not just present me with a black display screen on reaching the OS X Mavericks Installer window:

GeForce.kext
GeForceGA.plugin
GeForceGLDriver.bundle
GeForceVADriver.bundle

 

[13] Open the Chameleon 2.2 svn r2266 or 2269 i386 folder (download from link given above) then copy via Terminal, the cdboot file into /Users/"User Name"/Desktop/OS_X_10.9_Base_Sys_DLDVD/usr/standalone/i386, or, in non-Terminal "speak" go to Desktop >>>> OS_X_10.9_Base_Sys_DLDVD >>>> usr >>>> standalone >>>> i386, and then 'drag and drop' the cdboot file from the open source i386 folder into the target i386 folder.

[14] Go to /Users/"User Name"/Desktop/OS_X_10.9_Base_Sys_DLDVD/System/Library/CoreServices/,
i.e. in non-Terminal "speak" go to Desktop >>>> OS X Base System >>>> System >>>> Library >>>> CoreServices, and then highlight the 'locked' boot.efi file and right-click to select Get Info…….in the Get Info pop-up window that appears, uncheck the Locked checkbox……

or simply use the power of the Terminal, as shown in part B., by typing

sudo chflags nouchg /Users/"User Name"/Desktop/OS_X_10.9_Base_Sys_DLDVD/System/Library/CoreServices/boot.efi
exit

[15] Now download my nForce Extra folder for my OS X Mavericks Base System Dual Layer DVD Installer:

 

Still to be uploaded......

 

N.B. This version of my nForce Extra folder uses NVEnabler 64.kext with GraphicsEnabler=No.

If anyone has problems with this version, then let me know and I will prepare and upload a version of my nForce Extra folder without NVEnabler 64.kext and GraphicsEnabler=Yes........

Unzip it and then 'drag and drop' the Extra folder into the open OS_X_10.9_Base_Sys_DLDVD folder

[16] Go to Part B. in post #1 to download the verdant patched oldnapalm MBR modified OS X Mavericks OSInstall.mpkg package and the oldnapalm MBR modified OS X Mavericks OSInstall Unix executable file to the Desktop…….

[17] The procedure for installing the modified OSInstall.mpkg package and OSInstall Unix executable file in place of the original OS X Mavericks Installer versions is as follows:

1. Go to Terminal and then:

[1] Either type:

cd /Users/"User Name"/Desktop/OS_X_10.9_Base_Sys_DLDVD/System/Installation/Packages

or type

cd

and press the 'Space Bar', and then having navigated to System, then to Installation, then to Packages, 'drag and drop' the Packages folder into Terminal……

[2] Type the following:

sudo mv OSInstall.mpkg OSInstall.mpkg.GPT
ls

Note that you have now renamed the original file as shown by the 'ls' command…..

[3] Either type:

cd /Users/"User Name"/Desktop/OS_X_10.9_Base_Sys_DLDVD/System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A

or type

cd

and press the 'Space Bar', and then having navigated to System, then to Library, then to PrivateFrameworks, then to Install.framework, then to Frameworks, then to OSInstall.framework, then to Versions, and finally to the A folder, 'drag and drop' the A folder into Terminal……

[4] Type the following:

sudo mv OSInstall OSInstall.GPT
ls
exit

Note that you have now renamed the original file as shown by the 'ls' command…..

2. Then either 'drag and drop' the verdant patched oldnapalm MBR modified OS X Mavericks OSInstall.mpkg package into /Users/"User Name"/Desktop/OS_X_10.9_Base_Sys_DLDVD/System/Installation/Packages......(or use cp command via Terminal):

sudo cp -p -R /Users/"User Name"/Desktop/verdant\ Patched\ oldnapalm\ MBR\ Modified\ OS\ X\ Mavericks\ OSInstall\ Package/OSInstall.mpkg /Volumes/OS\ X\ Base\ System/System/Installation/Packages

3. Then 'drag and drop' the modified version of OSInstall into /Users/"User Name"/Desktop/OS_X_10.9_Base_Sys_DLDVD/System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A/OSInstall......(or use cp command via Terminal):

sudo cp -p -R /Users/"User Name"/Desktop/System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A/OSInstall /Volumes/OS\ X\ Base\ System/System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A

[18] Close all open folders within the OS_X_10.9_Base_Sys_DLDVD folder before closing it and then in the Terminal type:

sudo chown -R 0:0 /Users/"User Name"/Desktop/OS_X_10.9_Base_Sys_DLDVD

(Note: root:wheel and 0:0 are equivalent; but it is good to know both)

 

2. Creating my OS X Mavericks 10.9 Dual Layer DVD MBR/GPT Installer.ISO file

[19] Then in Terminal type:

sudo hdiutil makehybrid -o OSX_10.9_BaseSystemDLDVD.iso /Users/"User Name"/Desktop/OS_X_10.9_Base_Sys_DLDVD -iso -hfs -joliet -eltorito-boot /Users/"User Name"/Desktop/OS_X_10.9_Base_Sys_DLDVD/usr/standalone/i386/cdboot -no-emul-boot -hfs-volume-name "OSX_10.9_BaseSystemDLDVD" -joliet-volume-name "OSX_10.9_BaseSystemDLDVD"

If you have entered this line correctly you should see:

"Creating hybrid image...
……………………………………………………………………

"……………………………………………………………………" is a moving progress bar and after it stops, you should find a OSX_10.9_BaseSystemDLDVD.iso in the /Users/"User Name"/ directory.


[20] Burn this .iso image file to a dual layer DVD+R or DVD-R disc at x2.4 or slower, or at the stated dual layer DVD disc burn speed.......

 

BTW I use DVD+R DL discs because they have been on the market longer than dual layer DVD-R discs and so have had more development time based on user feedback etc......

Note that dual layer DVDs are not available in re-writable formats of DVD-RW or DVD+RW


3. Installing OS X Mavericks 10.9 to a target MBR/GPT HDD volume

[21] Use your running Snow Leopard or Lion Disk Utility to partition/format your target HDD volume for OS X 10.8 as a GPT or MBR/HFS+ volume named OSX_10.8_GPT_A or OSX_10.8_MBR_A (or your chosen name without spaces)


 

****************************************************

 

VERY IMPORTANT TO CHECK : OS X target HDD ownership

 

****************************************************



 

Right-click on the target OS X HDD volume icon on your Desktop, and select Get Info. If the checkbox next to "Ignore ownership on this volume" is checked then click on the padlock symbol to authenticate and UNCHECK the checkbox.



 

Then to ensure that the target OS X HDD volume's root directory is owned by the root user, go to Terminal and type: 



sudo chown 0:0 /Volumes/"your target OS X HDD volume name"

This is to make certain that the permissions are not scrambled after the installation of OS X.....and hence that you are able to boot from the OS X 10.9 hard drive........



 

Note that using 0:0 is equivalent to using root:wheel



 

[22] Now close all open windows on the Snow Leopard or Lion Desktop and any open applications.......



 

[23] Insert the OSX_10.9_BaseSystemDLDVD disc into your DVDRW and then reboot your PC and press the F8 key (or whichever key you need to) IMMEDIATELY after the message "Press DEL to enter SETUP, Press TAB to display BIOS POST message" or similar appears on-screen, in order to bring up the message "Loading Boot Menu......"




 

[24] When the PC BIOS "Boot Menu" window appears on-screen, select the DVDRW containing OSX_10.9_BaseSystemDLDVD disc from the list of bootable drives presented in the "Boot Menu", and press Enter......



 

[25] When the Chameleon bootloader menu appears, choose the OSX_10.9_BaseSystemDLDVD icon from the list of bootable volumes presented by the Chameleon bootloader.....



 

I recommend you choose -v as a boot flag before booting from the OS X Base System, so that you can see what is happening onscreen during booting…….



 

BE PREPARED - booting from the DVD is very slow - from booting the OSX_10.9_BaseSystemDLDVD to reaching the OS X Installer Desktop takes 10+ minutes........thus the OS X Mavericks system installation process takes even longer......



 

This is because [i] all kexts are loaded directly from /System/Library/Extensions/ and [ii] the OS X Mavericks BaseSystem.dmg files are no longer optimised for use with optical disks………….a further clear indication IMHO that Apple now view optical drives/disks as obsolete (just as they did with the floppy disk drive/disks)……..



 

[26] Follow the onscreen Mac OS X Installer instructions to install OS X Lion onto the target HDD volume.....



 

[27] Re-boot back into OS X Snow Leopard or OS X Lion or OS X Mountain Lion and run the Chameleon 2.2 svn r2266 pkg installer (download link in post #1 and in the verdant_Mountain Lion_Support_Files_v1.0 folder) and click on the Continue button in the Chameleon 2.2 svn r2266 ootloader Installer window…….then click Continue and Continue again and Agree…..then in the Standard Install window click Change Install Location and select the target HDD OS X Mavericks volume icon in the Select a Destination window and click Continue……then click Install…..after a hopefully successful install, click Close…..

 

[28] Set up your video driver as you have done for running OS X 10.6.8 Snow Leopard in 64bit mode or OS X Lion 10.7.5 or OS X Mountain Lion 10.8.5 in default 64bit mode......

 

[29] Go back to the open target HDD OS X Mavericks System Window……the Chameleon bootloader installer should have created the /Extra/ directory and sub-folders……BUT you may have to create them manually afterward……

 

[30] Copy across from your running 64bit mode OS X Snow Leopard 10.6.8 system, or running OS X Lion 10.7.5 system, or OS X Mountain Lion 10.8.5 system, the DSDT.aml file into the open target HDD OS X Mavericks System Window, i.e. the target HDD volume's / directory…….

 

[32] Copy across from your running 64bit mode OS X Snow Leopard 10.6.8 system, or running OS X Lion 10.7.5 system, or OS X Mountain Lion 10.8.5 system, into /Extra on the target HDD volume, the following .plist files:

 

smbios.plist for MacPro3,1 (use the one from MaLd0n's Lion installation via USB stick using Chameleon, DP4, GM and FINAL topic…….), or whatever MacProx,y designation matches your CPU....

 

org.chameleon.Boot.plist (assuming that you are using a recent/current Chameleon boot loader version later than v2.0 r11xx, or a version 2.1 or a version 2.2 revision)

 

Also copy across (if you wish) your Chameleon bootloader Themes folder from your running 64bit mode OS X Snow Leopard 10.6.8 system, or running OS X Lion 10.7.5 system, or OS X Mountain Lion 10.8.5 system,  or from the folder....

 

[33] Copy the following kexts in /Extra/Extensions/ on your running 64bit mode Snow Leopard, or in /System/Library/Extensions/ on your running Lion or Mountain Lion system, or from the verdant_Mavericks_Support_Files_v1.0 folder, into /System/Library/Extensions/ in the open target HDD OS X Lion System Window……

 

FakeSMC.kext

 

EvOreboot.kext

 

NullCPUPowerManagement.kext

 

(NullCPUPowerManagement.kext is not present or needed if you have already enabled, or are going to enable, Natural Power Management i.e. "vanilla SpeedStepping")

 

AppleNForceATA.imk64bit.kext

 

AD1998b.FIX.kext or VoodooHDA.kext

 

(AD1998b.FIX.kext or VoodooHDA.kext are only present or needed if AD1988b the audio chipset/codec of your nForce chipset + Intel CPU MOBO; alternatively, you may have or need

AppleHDA.10.6.2.kext for audio in /System/Library/Extensions/)

 

Then also copy the AppleRTC.Mavericks.Patched.kext from the verdant_Mavericks_Support_Files_v1.0 folder, into /System/Library/Extensions/ in the open target HDD OS X Mountain Lion System Window…

 

Alternatively, you can directly patch the installed OS X Mavericks AppleRTC.kext in /System/Library/Extensions/ in the open target HDD OS X Mountain Lion System Window, by running this perl script (courtesy of rayap modified by oldnapalm for  Mavericks) in Terminal, which has been posted by oldnapalm, which forces an unconditional jump over the rtcWrites() in updateChecksum() to prevent CMOS Resets:

sudo perl -pi -e 's|\x75\x2e\x0f\xb6|\xeb\x2e\x0f\xb6|' /System/Library/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC
sudo touch /System/Library/Extensions

N.B. If you have added the AppleRTC.Mavericks.Patched.kext from the verdant_Mavericks_Support_Files_v1.0 folder, into /System/Library/Extensions/ in the open target HDD OS X Mavericks System Window,
then to ensure that this is the RTC kext that is loaded, rename the installed OS X Mavericks AppleRTC.kext in /System/Library/Extensions/ in the open target HDD OS X Mountain Lion System Window using the Terminal as follows:

sudo mv /Volumes/"your target OS X Mavericks HDD volume name"/System/Library/Extensions/AppleRTC.kext /Volumes/"your target OS X Mavericks HDD volume name"/System/Library/Extensions/AppleRTC.kext_Origina

Note the later versions/revisions of FakeSMC.kext v3.0 and later by mojodojo can function from /Extra/Extensions/ or from /System/Library/Extensions/ but be aware that earlier versions/revisions of FakeSMC.kext can only function from /System/Library/Extensions/ - hence step [34] below:

 

[34] If you have AppleHDA.10.6.2.kext, FakeSMC.kext and nForceLAN.0.64.5.kext in /System/Library/Extensions/ on your running 64bit mode Snow Leopard system, or in /System/Library/Extensions/ on your running Lion or Mountain Lion system, then these kexts need to copied from there, or from the verdant_Mavericks_Support_Files_v1.0 folder, into /System/Library/Extensions/ in the open target HDD OS X Mountain Lion System Window……

 

[35] Having added these non-vanilla, i.e. non- Apple kexts, plus any others specific to your system; for example, I have added:

 

ACPIMonitor.kext


AppleNForceATA.imk64bit.kext


AppleRTL8169Ethernet.kext


AppleRTC.kext_ORIG
AppleRTC.MLion.Patched.kext


EvOreboot.kext


FakeSMC.kext


IntelCPUMonitor.kext


IntelThermal.kext


nForceLAN.0.64.5.kext


NVClockX.kext


SuperIOFamily.kext


VoodooHDA.kext



 

to /System/Library/Extensions/ on the open target HDD OS X Mountain Lion System Window, you need to use Terminal to reset the kexts ownership and permissions and rebuild the kernelcache file……alternatively, you can use janek202's Kext Wizard for a Terminal-free life.......

In Terminal type:




sudo chown -R root:wheel /System/Library/Extensions
sudo chmod -R 755 /System/Library/Extensions
sudo touch /System/Library/Extensions
exit





Close Terminal and then go to /System/Library/Caches/com.apple.kext.caches/Startup and delete the files within Startup….



 

invalidsignedkextalert.plist
IOKitPersonalities_x86_64.ioplist.gz
kernelcache
KextPropertyValues_OSBundleHelper_x86_64.plist.gz

loadedkextmt.plist



 

[36] Close the open target HDD OS X Mountain Lion System Window and boot from the target hard drive OS X Lion System volume......



 

[37] If you find that on shutting down OS X Lion and rebooting, that the CMOS has been "wiped clean" of your custom BIOS settings profile and the BIOS has reverted to using the in-built default BIOS settings, then reload your backed-up custom BIOS settings profile from its source (e.g. USB flash drive) and boot back into OS X Lion......



 

If this happens, then you have either

(i) not copied the AppleRTC.Mavericks.Patched.kext from the verdant_Mavericks_Support_Files_v1.0 folder, into /System/Library/Extensions/ in the open target HDD OS X Mavericks System Window, or

(ii) not directly patched the installed OS X Mavericks AppleRTC.kext in /System/Library/Extensions/ in the open target HDD OS X Mavericks System Window, by running this perl script in Terminal, which has been which has been
posted by oldnapalm, which forces an unconditional jump over the rtcWrites() in updateChecksum() to prevent CMOS Resets:

sudo perl -pi -e 's|\x75\x2e\x0f\xb6|\xeb\x2e\x0f\xb6|' /System/Library/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC
sudo touch /System/Library/Extensions

N.B. If you have added the AppleRTC.Mavericks.Patched.kext from the verdant_Mavericks_Support_Files_v1.0 folder, into /System/Library/Extensions/ in the open target HDD OS X Mavericks System Window,
then to ensure that this is the RTC kext that is loaded, rename the installed OS X Mavericks AppleRTC.kext in /System/Library/Extensions/ in the open target HDD OS X Mavericks System Window using the Terminal as follows:

sudo mv /Volumes/"your target OS X Mavericks HDD volume name"/System/Library/Extensions/AppleRTC.kext /Volumes/"your target OS X Mavericks HDD volume name"/System/Library/Extensions/AppleRTC.kext_Original

Now you need to again use Terminal to reset the kexts' ownership and permissions and rebuild the kernelcache file etc.....alternatively, you can use janek202's Kext Wizard for a Terminal-free life.......

In Terminal type:

sudo chown -R root:wheel /System/Library/Extensions
sudo chmod -R 755 /System/Library/Extensions
sudo touch /System/Library/Extensions
exit

Close Terminal and then go to /System/Library/Caches/com.apple.kext.caches/Startup and delete the files within Startup….

invalidsignedkextalert.plist
IOKitPersonalities_x86_64.ioplist.gz
kernelcache
KextPropertyValues_OSBundleHelper_x86_64.plist.gz
loadedkextmt.plist


[38] Close the open target HDD OS X Mavericks System Window and re-boot from the target hard drive OS X Mountain Lion System volume......

 

[39] Use the OS X Mavericks Disk Utility to repair the OS X Mavericks HDD system permissions......

N.B. If you experience the [PCI configuration begin] error on booting from the OS X Mountain Lion System installed on your target HDD volume, then see post #6, which gives four proposed solutions to this error.......

 

*************************************************************



#3
verdant

verdant

    InsanelyMac V.I.P.

  • Gurus
  • 5,570 posts
  • Gender:Male
  • Interests:At home, I have the following computers......
    >
    >
    >

Reserved for verdant



#4
verdant

verdant

    InsanelyMac V.I.P.

  • Gurus
  • 5,570 posts
  • Gender:Male
  • Interests:At home, I have the following computers......
    >
    >
    >

*************************************************************

 

Generating and Modifying the OS X Mavericks DSDT.aml File for Your Own nForce MOBO

 

*************************************************************

 

The modifications described below are what works for my Asus P5N32-E SLI Plus MOBO, and some are the same as those in the DSDT.aml files that I have for a nForce 790i MOBO and a nForce 680i MOBO.....

 

HOWEVER, the DSDT.aml is invariably MOBO brand/model specific and so what I have written below will need adapting for use in your own nForce chipset MOBO, unless of course, it is also a Asus P5N32-E SLI Plus MOBO......  ;)

 

To gain a clearer understanding of DSDT.aml modification procedures, be prepared to do a lot of reading in the DSDT Forum.....starting with the links in the now discontinued MaLd0n's DSDT Auto-Patcher topic........but also see olnapalm's DSDT editor and patcher (credit to el coniglio, who did the hard work writing the app).......however, for those lacking the knowledge and/or confidence to use DSDT editor and patcher and/or the time to manually do what DSDT editor and patcher does, see iHackintosh_PT's DSDT Auto-Patcher.......  :)

 

 

*************************************************************

1. Device (RTC) fix for the CMOS Reset issue

*************************************************************

 

 

A modified DSDT.aml was required to fix the CMOS reset bug in Snow Leopard as discovered by Stellarola; namely to edit the RTC section in the file so as to decrease the length of the IO segment from 4 to 2. RTC stands for Real Time Clock.

 

Assuming that you do not already have a basic fixed DSDT.aml, then run fassl's DSDT Patcher Version 1.0.1e (also see Stage 1 below and ) because as well as extracting your original DSDT, it will also perform some basic fixes providing a good base for further DSDT modification. Here is the DSDT Patcher Readme:

 

 

DSDT Patcher args:
-f force the compiling
-newHPET overwrites the fixed HPET with one that should work for all
somefile.dsl lets point you to another dsl file that should be patched

Version 1.0.1e
-added Mute fix by mackerintel
-added OSI emulation by mackerintel
thx for this  :)

Version 1.0.1d
-added the -newHPET function
-fixed an issue in the search Routine

Version 1.0.1c
-The patcher uses now getDSDT.sh for obtaining the DSDT through ioreg, since GetDSDT Tool does'nt work for some people
-added _T_ variable fix by mackertinel
-fixed CPU Aliases fix once again (everything that pointed to the alias had to be patched too)

Version 1.0.1b
-fixed a patching routine issue which caused non-compiling dsdt
-added "Method local variable is not initialized (Local0)" fix

Version 1.0.1a
-fixed CPU Aliases fix

Version 1.0.1
-added CPU Aliases fix
-added some device name fix

This should fix your DSDT so you should be able to run AppleIntelCPUPowerManagement.kext and the upcoming AppleRTC.kext which will panic otherwise. This will not patch your BIOS or whatever, so if you cant boot anymore after this, just delete the /DSDT.aml file and you should be fine. But still, try this at your own risk.

You need to install the Chameleon Bootloader with DSDT override from: http://www.insanelym...howtopic=132757 for this, use the newest version.

To patch your DSDT just double-click the DSDT Patcher, the fixed DSDT should now be dsdt.aml in the Patcher directory.

Install the new bootloader and put the resulting ./DSDT.aml in your Root /

Thanks to all Chameleon/OSX Developers who make such things possible, especially zef, kabyl and modbin for helping me at any time and share their work/knowledge, keep it up thanks.

Cheers fassl

 

The steps you have to go through will generate a dsdt.aml file that is specific to your PC, which then needs to be de-compiled to the corresponding dsdt.dsl file, that you can then edit using the Terminal nano editor......

You can use its search function or keyboard arrow keys to find your dsdt.dsl file's device (RTC) section and change the two or one IO segment length value(s) you see to 0x02.....then save the modified dsdt.dsl file, which is then re-compiled to give you your modified dsdt.aml file, that you then copy/rename as DSDT.aml file for later use in your / or /Extra directories e.g. on the USB stick and HDD......

For this, you will need OS X Leopard, or OS X Snow Leopard, or OS X Lion, or OS X Mountain Lion running on the PC onto which you plan to install OS X Mavericks.....

 

 

Stage 1. Generating dsdt.aml, dsdt.dsl files:

 

1. Copy fassl's DSDT_Patcher1.0.1e.zip file to the Desktop and double click it to extract it.

2. Open a Terminal window (Application -> Utilities) and then type the following commands:

cd ~/Desktop/DSDT_Patcher1.0.1e
./DSDT\ Patcher

Please do not forget the \ after DSDT and the space before Patcher

3. At this point a question about which platform you wish to emulate will appear. Choose 0 (zero) to emulate Darwin.

The program will then generate a number of files in folders within the DSDT_Patcher1.0.1e directory on the Desktop, and also may issue a few warnings that can be ignored safely at this stage.

 

 

Stage 2. To edit the dsdt.dsl file:

 

 

4. Type in the same Terminal window:

nano Debug/dsdt.dsl

5. This will open an editor window to enable you to decrease the length of the IO segment parameter in the Device (RTC) section in the dsdt.dsl file from 4 to 2.

Note that your dsdt.dsl file Device (RTC) section may not look the same as the example below (from my 650i Asus P5N32-E SLI Plus MOBO)......some MOBOs do not have a ATT1, ResourceTemplate, only a ATT0, ResourceTemplate and/or the IO segment length may be 0x08 rather than 0x04......

 

Device (RTC)
{
Name (_HID, EisaId ("PNP0B00"))
Name (ATT0, ResourceTemplate ()
{
IO (Decode16,
0x0070, // Range Minimum
0x0070, // Range Maximum
0x00, // Alignment

 

0x04, // Length

 

)
})
Name (ATT1, ResourceTemplate ()
{
IO (Decode16,
0x0070, // Range Minimum
0x0070, // Range Maximum
0x00, // Alignment
0x04, // Length
)

 

Change 0x04 to 0x02, and when you have finished the editing, press Control-O (i.e. press the Control key plus the letter "O" at the same time) and then RETURN to save the file. Then press Control-X to exit the nano text editor.

 

 

6. Back in the Terminal window, type:

./DSDT\ Patcher Debug/dsdt.dsl

Please do not forget the \ after DSDT and the space before Patcher

Which will create a file in the current directory called dsdt.aml but in doing so, you may see a few errors about pre-existing files; you can safely ignore these.

 

 

Stage 3. To produce the DSDT.aml file

 

 

7. Copy this dsdt.aml file (and rename it as DSDT.aml) to the Desktop

cp dsdt.aml /Users/"your username"/Desktop/DSDT.aml

Please note that DSDT must be in uppercase for the file to be loaded/work.

NOTE: The same procedure can be used to edit/modify the CMOS reset fix modded DSDT.aml file further as required........

 

 

*************************************************************

 

2. DTGP Method patch to enable use of other patches in the DSDT.aml file

 

*************************************************************

 

 

As an alternative to using fassl's DSDT Patcher in conjunction with a Terminal text editor such as nano (see above) to modify your DSDT.aml file, you can use EVOSx86 Team's DSDTSE

 

 

on OS X, or XP_DSDT running in Windows, or whatever method you prefer to use, perhaps using a separate DSDT extractor, DSDT compiler/decompiler and DSDT patcher......

In the original DSDT.aml file for my Asus P5N32-E SLI Plus MOBO, near to the top of the dsdt.dsl file, there is the following:

GP49, 8
}
Name (VSTA, 0x01)
Name (OSFX, 0x01)
Name (OSFL, 0x01)
Method (STRC, 2, NotSerialized)

You can insert the DTGP Method patch between Name (OSFL, 0x01) and Method (STRC, 2, NotSerialized), i.e. before the first Method in the DSDT.aml file.....

Hence, after patching with the code in red, you should have:

Name (OSFL, 0x01)

Method (DTGP, 5, NotSerialized)
{
If (LEqual (Arg0, Buffer (0x10)
{
/* 0000 */ 0xC6, 0xB7, 0xB5, 0xA0, 0x18, 0x13, 0x1C, 0x44,
/* 0008 */ 0xB0, 0xC9, 0xFE, 0x69, 0x5E, 0xAF, 0x94, 0x9B
}))
{
If (LEqual (Arg1, One))
{
If (LEqual (Arg2, Zero))
{
Store (Buffer (One)
{
0x03
}, Arg4)
Return (One)
}

If (LEqual (Arg2, One))
{
Return (One)
}
}
}

Store (Buffer (One)
{
0x00
}, Arg4)
Return (Zero)
}


Method (STRC, 2, NotSerialized)

 

 

*************************************************************

 

3. Device (HPET) fix to enable the removal of NullCPUPowerManagement.kext from /Extra/Extensions/ or /System/Library/Extensions/ and the loading of AppleIntelCPUPowerManagement.kext

 

*************************************************************

 

Special thanks go to Volcacius, who patched his 790i DSDT.aml file to enable working C-states (learning from Master Chief.....see here too.....) and posted it for me to see.......saving me a lot of time as the HPET fix he used also works for me!

 

The HPET fix enables you to remove NullCPUPowerManagement.kext from /Extra/Extensions/ and enables the AppleHPET.kext to load, so that the AppleIntelCPUPowerManagement.kext and AppleIntelCPUPowerManagementClient.kext can load without a kernel panic being generated......


"no HPETs available ... CPU(s) configured incorrectly\n"@/SourceCache/AppleIntelCPUPowerManagement/AppleIntelCPUPowerManagement-......."

Removing NullCPUPowerManagement.kext from /Extra/Extensions/ and hence loading the AppleIntelCPUPowerManagement.kext enables you to employ Intel SpeedStepping using Chameleon 2.2 svn r2266 as explained in 3. below. HPET stands for High Precision Event Timer.


My original Device (HPET) section [above device (RTC)] was:

Device (HPET)
{
Name (_HID, EisaId ("PNP0103"))
Name (ATT3, ResourceTemplate ()
{
IRQNoFlags ()
{0}
IRQNoFlags ()
{8}
Memory32Fixed (ReadWrite,
0xFEFF0000, // Address Base
0x00000400, // Address Length
)
})
Name (ATT4, ResourceTemplate ()
{
})
Method (_STA, 0, NotSerialized)
{
If (LEqual (OSFX, 0x03))
{
If (HPTF)
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
Else
{
Return (Zero)
}
}

Method (_CRS, 0, NotSerialized)
{
If (LEqual (OSFX, 0x03))
{
If (HPTF)
{
Return (ATT3)
}
Else
{
Return (ATT4)
}
}
Else
{
Return (ATT4)
}
}
}


Device (RTC)

and I replaced everything in { } belonging to Device (HPET) with:

 

Device (HPET)

 

{
Name (_HID, EisaId ("PNP0103"))
Name (_CID, EisaId ("PNP0C01"))
Name (ATT3, ResourceTemplate ()
{
IRQNoFlags ()
{0}
IRQNoFlags ()
{8}
Memory32Fixed (ReadWrite,
0xFEFF0000, // Address Base
0x00000400, // Address Length
)
})
Name (ATT4, ResourceTemplate ()
{
})
Method (_STA, 0, NotSerialized)
{
If (LGreaterEqual (OSFX, 0x03))
{
If (HPTF)
{
Return (0x0F)
}
}
Else
{
If (HPTF)
{
Return (0x0B)
}
}

Return (Zero)
}

Method (_CRS, 0, NotSerialized)
{
If (HPTF)
{
Return (ATT3)
}

Return (ATT4)
}
}

Return (ATT4)
}
}

 

Device (RTC)

 

 

*************************************************************

 

4. Device (LPCB) patch insertion into the DSDT.aml file to enable Native Power Management in OS X Mavericks

 

*************************************************************

 

 

To enable native power management in OS X Mavericks, you need to have:

[1] The appropriate Mac Model for your CPU, e.g. in my case MacPro3,1:

 

MacPro3,1 >>> Intel Xeon 5400 series ("Harpertown") / Use for Core2Quad

 

[2] In your BIOS you must have:

Enhanced C1 (C1E) [ENABLED]
Enhanced Intel Speedstep Technology [ENABLED]
HPET Support [ENABLED]

[3] To enable C-States, you must have the equivalent of AppleLPC working on your system.

This is because the AppleLPC.kext has to load into the kernel to enable native power management in OS X (and incidentally, for the `Start up automatically after a power failure' option to appear in the Energy Saver window in System Preferences)

However, for AppleLPC.kext to load, the OS X Mavericks DSDT.aml file has to have a LPC patch inserted as explained below.

 

N.B.  In order for OS X Mavericks to load the AppleLPC.kext, its DSDT.aml file requires a Method (_DSM, 4, NotSerialized) patch that is less simple than the Method (_DSM, 4, NotSerialized) patch that works for OS X Snow Leopard 10.6.x through to OS X Mountain Lion 10.8.x. 

The LPC bus was introduced by Intel in 1998 as a substitute for the Industry Standard Architecture (ISA) bus. LPC stands for Low Pin Count and modern Super-I/O chips use the Low Pin Count (LPC) bus instead of ISA for communication with the CPU via an LPC interface on the Southbridge chip of the MOBO.

This is the starting point for inserting the LPC patch into your DSDT.aml file because the LPC bus has replaced the ISA bus, effectively 'mapping' onto it.

 

So, start by installing Evosx86 Team's Snow Leopard x64 version v1.1 of the UNIX lspci utility which works with OS X Mavericks:

 

Attached File  lspci V1.1.zip   281.85KB   25 downloads

 

and then type in Terminal:

lspci -nn

and look for the ISA bridge entry, e.g. in my case:

 

00:0a.0 ISA bridge [0601]: nVidia Corporation MCP55 LPC Bridge [10de:0360] (rev a2)

 

What you are looking for are the digits at start of the line, i.e. Field 1, which is 00:0a.0 above.

Field 1 : 00:0a.0 : bus number (00), device number (0a) and function (0)

In the DSDT.aml file, addresses have 8 digits after 0x (0x signifies that the number that follows is a hexadecimal number), thus 00:0a.0 is equivalent to the 0x000a0000, i.e. 00:0 is 000; a is a, and .0 is written as 0000.

Now search the dsdt.dsl or dsdt.aml file using 0x000a0000 as the Search Term until you find a Device section with Name (_ADR, 0x000A0000) immediately below it.

In my dsdt file, Name (_ADR, 0x000A0000) appeared below the Device (LEG0). This was double-checked by searching for LEG0 in the OS X IORegistry using IORegistryExplorer (found in Xcode Developer folder >>>> Applications >>>> Utilities) to confirm its location in IOReg under AppleACPIPlatformExpert >>>> PCI0@0 >>>> AppleACPIPCI.

Now copy AppleLPC.kext to the Desktop and right-click on it and select Show Package Contents, then go to Contents >>>> Info.plist.

Open Info.plist using TextEdit, Property List Editor, TextMate or your favourite .plist file text editor, and look under

 

AppleLPC

CFBundleIdentifier
com.apple.driver.AppleLPC
IOClass
AppleLPC


and note the IONameMatch array; of particular interest are the entries with the nVidia vendor ID, i.e. 10de.

pci8086,2811
pci8086,2815
pci8086,27b9
pci8086,27bd
pci8086,2670
pci8086,8119
pci8086,2916
pci8086,3a18
pci8086,3b00
pci8086,3b01
pci8086,3b02
pci8086,3b09
pci10de,aac
pci10de,aae
pci10de,aaf
pci10de,d80
pci10de,d81
pci10de,d82
pci10de,d83

 

Although there are no entries matching, or very similar to, the ISA bus device ID 10de:0360, it has been found that for nForce chipset MOBOs under OS X, the device ID in the bold entry functions as an equivalent device ID to 0360.

 

I have personally found this to be true as I do not need to use a Info.plist only kext to inject the ISA bus device ID 10de:0360 via the following:

 

key>AppleLPC

CFBundleIdentifier
com.apple.driver.AppleLPC
IOClass
AppleLPC
IONameMatch

pci10de,360

 

Nevertheless, here is the LPC_injector.kext posted by iLeopod: zip.gif LPC_injector.kext.zip 2.33K 33 downloads

 

Thus aae becomes (written in reverse order): 0xAE, 0x0A, 0x00, 0x00

 

Back in the DSDT.aml file, Device (LEG0) becomes Device (LPCB) and all other instances of LEG0 are replaced by LPCB.

 

Now the relevant part of what was formely Device (LEG0), now named Device (LPCB) is:

 

Device (LEG0)
{
Name (_ADR, 0x000A0000)
OperationRegion (PIO0, PCI_Config, 0x04, 0x20)
Scope (\)
{
Field (\_SB.PCI0.LEG0.PIO0, ByteAcc, NoLock, Preserve)
{
SMEN, 8,
Offset (0x0C),
Offset (0x0D),
SMIO, 8
}
}

Scope (\)
{
OperationRegion (SCPP, SystemIO, 0x142E, One)
Field (SCPP, ByteAcc, NoLock, Preserve)
{
SMIP, 8
}
}

Method (^_INI, 0, NotSerialized)

 

because the LPC Method, i.e. Method (_DSM, 4, NotSerialized) patch patch needs to be inserted between the lower

 

Scope (/) { }

 

section and

 

Method (^_INI, 0, NotSerialized) section, as follows:

Device (LPCB)
{
Name (_ADR, 0x000A0000)
OperationRegion (PIO0, PCI_Config, 0x04, 0x20)
Scope (\)
{
Field (\_SB.PCI0.LPCB.PIO0, ByteAcc, NoLock, Preserve)
{
SMEN, 8,
Offset (0x0C),
Offset (0x0D),
SMIO, 8
}
}

Scope (\)
{
OperationRegion (SCPP, SystemIO, 0x142E, One)
Field (SCPP, ByteAcc, NoLock, Preserve)
{
SMIP, 8
}
}

 

Method (_DSM, 4, NotSerialized)

{

Store (Package (0x08)

{

"device-id", 

Buffer (0x04)

{

0xAE, 0x0A, 0x00, 0x00

}, 

 

"compatible", 

Buffer (0x0D)

{

"pci10de,aae"

}, 

 

"IOName", 

Buffer (0x0D)

{

"pci10de,aae"

}, 

 

"name", 

Buffer (0x0D)

{

"pci10de,aae"

}

}, Local0)

DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))

Return (Local0)

}


Method (^_INI, 0, NotSerialized)

 

N.B.  In order for OS X Mavericks to load the AppleLPC.kext, its DSDT.aml file requires a Method (_DSM, 4, NotSerialized) patch that is less simple than the Method (_DSM, 4, NotSerialized) patch that works for OS X Snow Leopard 10.6.x through to OS X Mountain Lion 10.8.x. 

 

The required modification is the added text in red in the above Method (_DSM, 4, NotSerialized) patch.

 

To confirm that OS X Mavericks is loading the AppleLPC.kext into the kernel, open the Terminal and type at the prompt

kextstat | grep LPC

If the AppleLPC.kext is not being loaded into the kernel, the SMC monitoring apps will show your CPU core temperatures as being of the order of 10°C hotter than when it is loaded into the kernel.

 

 

*************************************************************

 

5. Device (TMR) and Device (PIC) fixes to prevent audio "stuttering" when Native Power Management in OS X is enabled, i.e. after SpeedStepping with C-states is enabled

 

*************************************************************

 

The relevant section of Device (TMR) is shown here:

 

Device (TMR)
{
Name (_HID, EisaId ("PNP0100"))
Name (ATT5, ResourceTemplate ()
{
IO (Decode16,
0x0040, // Range Minimum
0x0040, // Range Maximum
0x00, // Alignment
0x04, // Length
)
IRQNoFlags ()
{0}

})
Name (ATT6, ResourceTemplate ()
{
IO (Decode16,
0x0040, // Range Minimum
0x0040, // Range Maximum
0x00, // Alignment
0x04, // Length
)
})

 

Note the presence of IRQNoFlags () {0} - the fix is simply to remove IRQNoFlags () {0} from this section:

 

Device (TMR)
{
Name (_HID, EisaId ("PNP0100"))
Name (ATT5, ResourceTemplate ()
{
IO (Decode16,
0x0040, // Range Minimum
0x0040, // Range Maximum
0x00, // Alignment
0x04, // Length
)
})
Name (ATT6, ResourceTemplate ()
{
IO (Decode16,
0x0040, // Range Minimum
0x0040, // Range Maximum
0x00, // Alignment
0x04, // Length
)
})

 

The relevant section of Device (PIC) is shown here:

 

Device (PIC)
{
Name (_HID, EisaId ("PNP0000"))
Name (_CRS, ResourceTemplate ()
{
IO (Decode16,
0x0020, // Range Minimum
0x0020, // Range Maximum
0x01, // Alignment
0x02, // Length
)
IO (Decode16,
0x00A0, // Range Minimum
0x00A0, // Range Maximum
0x01, // Alignment
0x02, // Length
)
IRQNoFlags ()
{2}

})
}

 

Note the presence of IRQNoFlags () {2} - the fix is simply to remove IRQNoFlags () {2} from this section:

 

Device (PIC)
{
Name (_HID, EisaId ("PNP0000"))
Name (_CRS, ResourceTemplate ()
{
IO (Decode16,
0x0020, // Range Minimum
0x0020, // Range Maximum
0x01, // Alignment
0x02, // Length
)
IO (Decode16,
0x00A0, // Range Minimum
0x00A0, // Range Maximum
0x01, // Alignment
0x02, // Length
)
})
}

 

*************************************************************



#5
verdant

verdant

    InsanelyMac V.I.P.

  • Gurus
  • 5,570 posts
  • Gender:Male
  • Interests:At home, I have the following computers......
    >
    >
    >

*************************************************************

How to Enable Natural Power Management ("vanilla SpeedStepping") in OS X Mavericks 10.9.x (and in 
OS X Mountain Lion 10.8.x, OS X Lion 10.7.x, and OS X Snow Leopard 10.6.x) on an nForce chipset + Intel CPU MOBO

 

*************************************************************
 

[1] Ensure that you have the appropriate Mac Model identifier for your CPU, e.g. MacPro3,1

[2] In your BIOS check that you have:

Enhanced C1 (C1E) [ENABLED]
Enhanced Intel Speedstep Technology [ENABLED]
HPET Support [ENABLED]


[3] Assuming that you do not already have a basic fixed DSDT.aml, then run fassl's DSDT Patcher Version 1.0.1e (also see post #4) because as well as extracting your original DSDT, it will also perform some basic fixes providing a good base for further DSDT modification: 


Attached File  DSDT_Patcher1.0.1e.zip   225.93KB   32 downloads

Here is the DSDT Patcher Readme:
 

DSDT Patcher args:
-f force the compiling
-newHPET overwrites the fixed HPET with one that should work for all
somefile.dsl lets point you to another dsl file that should be patched

Version 1.0.1e
-added Mute fix by mackerintel
-added OSI emulation by mackerintel
thx for this  :)

Version 1.0.1d
-added the -newHPET function
-fixed an issue in the search Routine

Version 1.0.1c
-The patcher uses now getDSDT.sh for obtaining the DSDT through ioreg, since GetDSDT Tool does'nt work for some people
-added _T_ variable fix by mackertinel
-fixed CPU Aliases fix once again (everything that pointed to the alias had to be patched too)

Version 1.0.1b
-fixed a patching routine issue which caused non-compiling dsdt
-added "Method local variable is not initialized (Local0)" fix

Version 1.0.1a
-fixed CPU Aliases fix

Version 1.0.1
-added CPU Aliases fix
-added some device name fix

This should fix your DSDT so you should be able to run AppleIntelCPUPowerManagement.kext and the upcoming AppleRTC.kext which will panic otherwise. This will not patch your BIOS or whatever, so if you cant boot anymore after this, just delete the /DSDT.aml file and you should be fine. But still, try this at your own risk.

You need to install the Chameleon Bootloader with DSDT override from: 

 

http://www.insanelym...howtopic=132757 for this, use the newest version.

To patch your DSDT just double-click the DSDT Patcher, the fixed DSDT should now be dsdt.aml in the Patcher directory.

Install the new bootloader and put the resulting ./DSDT.aml in your Root /

Thanks to all the Chameleon/OSX Developers who make such things possible, especially zef, kabyl and modbin for helping me at any time and share their work/knowledge, keep it up thanks.

Cheers fassl

 

[4] Modify the Device (HPET) section and insert the Device (LPCB) section into the appropriate DSDT.aml file as described in post #4 on Generating and Modifying the OS X Mavericks DSDT.aml File for Your Own nForce MOBO.

[5] Fix the Device (TMR) and Device (PIC) sections in the fixed HPET and LPCB patched DSDT.aml file, as described simply in post #4 on Generating and Modifying the OS X Mavericks DSDT.aml File for Your Own nForce MOBO, in order to to prevent audio "stuttering" when Native Power Management in OS X is enabled, i.e. after SpeedStepping with C-states is enabled. 


[6] Ensure you are running Chameleon 2.2 svn r2266,  or an even later revision if it working 100% for you, when installing OS X Mavericks.

[7] Modify org.chameleon.Boot.plist by adding:

<key>GeneratePStates</key>
<string>Yes</string>
<key>GenerateCStates</key>
<string>Yes</string>


N.B. The P-States and C-States generated by Chameleon are exported to the system via additional SSDTs, so if your BIOS has native SSDTs with _CST methods you should use "DropSSDT" = "Yes" option in org.chameleon.Boot.plist as follows:


<key>DropSSDT</key>
<string>Yes</string>

<key>GeneratePStates</key>
<string>Yes</string>
<key>GenerateCStates</key>
<string>Yes</string>


Likewise, if you have a modded DSDT with _CST methods you should remove them or there will be a kernel panic on system start. 

[8] Remove NullCPUPowerManagement.kext from /System/Library/Extensions/.

[9] Reboot.

 

[10] Open Terminal and type at the prompt

kextstat | grep LPC

to confirm that OS X Mavericks is loading the AppleLPC.kext into the kernel. 

 

If the AppleLPC.kext is not being loaded into the kernel, the SMC monitoring apps will show your CPU core temperatures as being of the order of 10°C hotter than when it is loaded into the kernel.

 

If you are booting Snow Leopard in 32bit mode you can use VoodooMonitor to check if you are speedstepping:
 

Attached File  Info.png   17.28KB   7 downloads Attached File  Status.png   31.39KB   3 downloads

Attached File  P_States.png   29.45KB   2 downloads

Attached File  Load_Test_Status.png   31.13KB   3 downloads

 

and you can carry out a CPU load test using CPUTest (CPUTest should work with OS X 10.3 and up, as CPUTest is a Universal binary app.) 

 

Attached File  CPUTest.zip   378.45KB   17 downloads

With thanks to aschar1, the mark-i application can also be used (32bit and 64bit mode): 

Attached File  mark_i.zip   333.56KB   33 downloads

 

You can check if speedstepping is working with mark-i app (works in 32bit and in 64bit mode).

 

Do not install the ringaccess.kext permanently in /S/L/E.

 

Just 'kextload' it using Terminal.
 

Download the attached zip file and unzip in a folder on your desktop.

 

Then:

 

a. In Terminal type

cd 

then drag the folder with mark-i and ringacces.kext into the Terminal window
 

b. In Terminal type

sudo chown -R root:wheel RingAccess.kext
sudo chmod -R 755 RingAccess.kext
sudo kextload RingAccess.kext

c. Start the mark-i app

 

Attached File  Mark_i_Idle.png   39.44KB   7 downloads Attached File  Mark_i_Load.png   39.55KB   8 downloads

 

You can also confirm that speed stepping is working in OS X Snow Leopard, OS X Lion,  OS X Mountain Lion, OS X Mavericks by installing and running SMC Monitor.app and/or smcK-Stat-i.app (both of these apps are included in the verdant_Maverick_Support_Files_v1.0 folder, which you can download by clicking on the link in post #1.)

Whether you are using mark-i.app, SMC Monitor.app or SMC Monitor.app, in all cases if speed stepping is working properly, you should see the CPU core frequencies changing dynamically with CPU load, e.g. when scrolling windows rapidly, browsing the Internet etc., i.e. cycling between your listed P-states.......


*************************************************************



#6
verdant

verdant

    InsanelyMac V.I.P.

  • Gurus
  • 5,570 posts
  • Gender:Male
  • Interests:At home, I have the following computers......
    >
    >
    >

Reserved for verdant



#7
verdant

verdant

    InsanelyMac V.I.P.

  • Gurus
  • 5,570 posts
  • Gender:Male
  • Interests:At home, I have the following computers......
    >
    >
    >

Reserved for verdant



#8
verdant

verdant

    InsanelyMac V.I.P.

  • Gurus
  • 5,570 posts
  • Gender:Male
  • Interests:At home, I have the following computers......
    >
    >
    >

*************************************************************

Peripheral Devices on nForce chipset + Intel CPU MOBOs

*************************************************************

Device 1. Asmedia 106x SATA Controller Ver 0.95.1 AHCI Mode

This device is referring to any PCI-e card with the asmedia ASM1061 chipset on it. This chipset has the following SATA features:

2 port Serial ATA PHY for 1.5, 3.0 and 6.0 GHz signalling (2 eSATA, or 2 SATA, or 1 eSATA + 1SATA; set via jumper block)
Supports Native Command Queue (NCQ)
Supports Gen 1m and 2m SATA PHY
Supports a Port Multiplier

AHCI Version 1.20 Supported

See here for a topic on its use with OS X on x86 hacks.......

Here is an interesting comparison of alternative SATA III controllers for connecting up SSDs.

I have overcome my nForce chipset issue with my SATA DVDRW by using two ASM1061 chipset PCI-e SATA III cards (2 eSATA, or 2 SATA, or 1 eSATA and 1 SATA port).

 

I have put one card in a spare x16 PCI-e slot and one card in a spare x8 PCI-e slot. 

 

 

Issue 1. Displayed in System Report as "Generic AHCI Controller" and "Vendor: Generic"

This is happening because Apple's GenericAHCI device in the AppleAHCIPort.kext is being used by OS X to recognise and support this device. 

Consequently, if you installed another PCI-e card SATA controller with a different chipset that is also recognised and supported by OS X Apple's GenericAHCI device in the AppleAHCIPort.kext, it too would display as "Generic AHCI Controller:" and "Vendor: Generic".

Thus, there is no point in making use of a LegacyAppleAHCIPort.kext to make the System Report display the ASM1061 chipset PCI-e card, for example, as "Asmedia 106x SATA Controller Ver 0.95 AHCI Mode", which would involve editing the Info.plist file of the legacy kext to be installed in /S/L/E/, by modifying the GenericAHCI device section.

This is because the resultant change in the System Report/Hardware/Serial-ATA/ window,would as explained above, be just a superficial and purely cosmetic change......and if these changes were made, both PCI-e SATA Controllers would then display as being "Asmedia 106x SATA Controller Ver 0.95.x AHCI Mode" and "Vendor: Asmedia Technology" when they are not.....

Furthermore, why worry about such cosmetic touches, when running OS X on your x86 Hack will never be the same as running it on a'real' Mac.......  :)


Issue 2. Updating the ASM1061 firmware from version 0.89 to version 0.95 and then 0.95.1

If your purchased PCI-e card with the Asmedia ASM1061 chipset shows up as "Asmedia 106x SATA Controller Ver 0.89 AHCI Mode" when booting your PC, you can update the ASM1061 firmware from version 0.89 to the current latest version 0.95 and then to revision 0.95.1 as follows:

1. Get access to a Windows OS and download and run Rufus v1.3.4 in Windows, in order to create an MS-DOS bootable USB flash drive:

Attached File  rufus_v1.3.4.exe.zip   441.52KB   6 downloads

2. Download the following zipped folder:

Attached File  ASMedia 1061 Firmware.zip   914.31KB   9 downloads

3. Unzip it and you should see a folder called ASMedia 1061 Firmware, that contains the folders N095 and N0951, which are extracted from the .zip and compressed .exe files. respectively.

 

The N095 folder contains:

 

106N095.BIN
106spi.exe
AHCI.BAT
ahci95A1.rom
dos4gw.exe
driver, bios, firmware, utilities.url
IDE.BAT
ide95A1.rom
ReadMe.txt

 

while the N0951 folder contains:

 

106N0951.BIN

106spi.exe

AHCI.BAT

ahci0951.rom

dos4gw.exe

IDE.BAT

ide0951.rom

 

 

4. Copy the contents of folder N095 onto the MS-DOS bootable USB flash drive, and boot the PC using the MS-DOS bootable flash drive

5. When the black boot screen is displayed, at the C:> prompt, type

AHCI.bat

and press Return.......the ASM1061 chipset firmware should then be updated to version 0.95.

6. Re-boot the PC and check that the following is displayed onscreen:

Asmedia 106x SATA Controller Ver 0.95 AHCI Mode

7. Replace these files on the MS-DOS bootable flash drive

 

106N095.BIN
106spi.exe
AHCI.BAT
ahci95A1.rom
dos4gw.exe
IDE.BAT
ide95A1.rom

 

with all the files in folder N0951

 

106N0951.BIN

106spi.exe

AHCI.BAT

ahci0951.rom

dos4gw.exe

IDE.BAT

ide0951.rom

 

and boot the PC using the MS-DOS bootable flash drive

8. When the black boot screen is displayed, at the C:> prompt, type

AHCI.bat

and press Return.......the ASM1061 chipset firmware should then be updated to version 0.951.

 

9. Re-boot the PC and check that the following is displayed onscreen:

 

Asmedia 106x SATA Controller Ver 0.951 AHCI Mode

 

 

Issue 3. Resolvable Issues when the Asmedia SATA Controller is connected to one or more SATA Optical Drives

When you have one or more SATA optical drive connected to the ASM1061 chipset PCI-e card, the optical drive tray(s) will open and close during the boot up process, and then when you reach the Desktop and put a disc in the tray(s), the drive(s) will stay inactive and a message will appear to say that ' blank DVD has been inserted into the drive', and the disc(s) will not appear on the Desktop.

I get around this quirky issue by placing one of my undamaged "coaster" CDs or DVDs in the SATA DVDRW before I boot into OS X and before I shut down OS X......i.e. I keep a CD/DVD in the SATA DVDRW all the time.....once OS X is booted and running, I have had no problems and simply put whatever CD/DVDRW I need to/want to use in the DVDRW........but when I want to shut OS X down I first put my "coaster" disc in the drive......


*************************************************************



#9
abhilash

abhilash

    InsanelyMac Protégé

  • Members
  • PipPip
  • 69 posts
  • Gender:Male
  • Location:INDIA

Hi Verdant, Good to see your Installation manual again. I can't install GM on my nForce 680i LT. :( I moved to USA.  



#10
mediamac

mediamac

    Mediarays

  • Members
  • PipPipPip
  • 174 posts
  • Gender:Male
  • Location:INDIA
  • Interests:Hackintoshing

Hi Verdant, Good to see your Installation manual again. I can't install GM on my nForce 680i LT. :( I moved to USA.  

I successfully installed mavericks on 680iLT with some kexts from mountain lion but it gives kernel panic within few minutes of logging in.



#11
verdant

verdant

    InsanelyMac V.I.P.

  • Gurus
  • 5,570 posts
  • Gender:Male
  • Interests:At home, I have the following computers......
    >
    >
    >

@ abilash 

 

A pity you do not have your nForce 680i LT with you in the USA.   Maybe you can find a cheap used one in the USA.......!

 

@ mediamac

 

Make sure that all the kexts are true 64bit kexts. Did you use the ones from my Mountain Lion download link?



#12
mediamac

mediamac

    Mediarays

  • Members
  • PipPipPip
  • 174 posts
  • Gender:Male
  • Location:INDIA
  • Interests:Hackintoshing

@ abilash 

 

A pity you do not have your nForce 680i LT with you in the USA.   Maybe you can find a cheap used one in the USA.......!

 

@ mediamac

 

Make sure that all the kexts are true 64bit kexts. Did you use the ones from my Mountain Lion download link?

Hi verdant,

 I am using the kexts provided by you for mountain lion but the kernel panic seems to be common even for the real mac users.They also reported the kernel panic in apple forum which is similar to my problem.

 Now I got these issues

Slow boot (takes a minute to boot)

Mail,reminder,notes,icloud and internet accounts are crashing.

Safari crash (kernel panic which I mentioned earlier )

App store account not working

Can you help me ?

Thanks in advance!



#13
verdant

verdant

    InsanelyMac V.I.P.

  • Gurus
  • 5,570 posts
  • Gender:Male
  • Interests:At home, I have the following computers......
    >
    >
    >

@ mediamac

 

Once I have finished my guide are you in a position to do a clean Mavericks install using the guide because I have experienced none of those issues?



#14
mediamac

mediamac

    Mediarays

  • Members
  • PipPipPip
  • 174 posts
  • Gender:Male
  • Location:INDIA
  • Interests:Hackintoshing

@ mediamac

 

Once I have finished my guide are you in a position to do a clean Mavericks install using the guide because I have experienced none those issues?

Update: Hi Verdant,

 I reinstall mavericks using your guide and so far no issues.

 But booting takes 60 seconds.

 Thanks



#15
verdant

verdant

    InsanelyMac V.I.P.

  • Gurus
  • 5,570 posts
  • Gender:Male
  • Interests:At home, I have the following computers......
    >
    >
    >

@ mediamac

 

That is good news.......I am pleased my guide worked well for you.......:)

 

The booting is about a minute because of the nForceATA.kext and nForce chipset interaction I believe......



#16
mediamac

mediamac

    Mediarays

  • Members
  • PipPipPip
  • 174 posts
  • Gender:Male
  • Location:INDIA
  • Interests:Hackintoshing

@ mediamac

 

That is good news.......I am pleased my guide worked well for you....... :)

 

The booting is about a minute because of the nForceATA.kext and nForce chipset interaction I believe......

So how to speed up the boot ? i have tried removing the nforceata and using ahciportinjector but no luck.

Any ideas ?



#17
verdant

verdant

    InsanelyMac V.I.P.

  • Gurus
  • 5,570 posts
  • Gender:Male
  • Interests:At home, I have the following computers......
    >
    >
    >

@ mediamac

 

You have to use the AppleNForceATA.imk64bit.kext. I will look into the boot time once I have finished the guide.....



#18
Kilopopo

Kilopopo

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 163 posts

thanks for the tip verdant



#19
tickerzoo

tickerzoo

    InsanelyMac Protégé

  • Members
  • Pip
  • 6 posts
  • Gender:Male

Great guide Thank you ,

I updated my mountain lion build to mavericks without issues.

In mountain lion my optical audio would always stutter using AD1998b.FIX with AppleHDA.1062 this no longer happens with mavericks (Thats with DSDT fixes).

theres a tiny issue with waking from sleep that never happened in ML the LAN is no longer able to connect to my network but thats no big deal for me at the moment.

Thanks again & keep up the great work.



#20
verdant

verdant

    InsanelyMac V.I.P.

  • Gurus
  • 5,570 posts
  • Gender:Male
  • Interests:At home, I have the following computers......
    >
    >
    >

@ Kilopopo

 

Which tip is that?

 

@ tickerzoo

 

Glad you like the guide and that it worked for you without any issues...... :)

 

Sleep on my 650i has never properly worked for me since OS X Leopard...........black screen, fans continue to run, and no waking up without a full re-boot..... :mad:

 

When I do my audio section, I would be happy to post your DSDT fix for optical audio etc.







Also tagged with one or more of these keywords: nForce chipset + Intel CPU, nForce 650i and 650i Ultra, nForce 750i and 780i, nForce 790i and 790i Ultra, nForce 680i, Possibly nForce 630i


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy