Jump to content

fluid | fixed

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

Started by verdant, Jul 28 2011 11:50 PM

  • Please log in to reply
428 replies to this topic

Poll: Lion on nForce + Intel CPU MOBO in Desktop (39 member(s) have cast votes)

Have you successfully installed a working, bootable Lion system?

  1. Yes, on a Series 7 (750i, 780i, or 790i) nForce chipset Intel CPU MOBO, using the USB flash drive installer method (13 votes [23.64%])

    Percentage of vote: 23.64%

  2. Yes, on a Series 6 (650i or 680i) nForce chipset Intel CPU MOBO, using the USB flash drive installer method (12 votes [21.82%])

    Percentage of vote: 21.82%

  3. Yes, on a Series 6 (610i or 630i) nForce chipset Intel CPU MOBO, using the USB flash drive installer method (0 votes [0.00%])

    Percentage of vote: 0.00%

  4. Yes, on a Series 7 (750i, 780i, or 790i) nForce chipset Intel CPU MOBO, using the verdant_nForce_OSX_Lion_Installer_DVD_Booter (0 votes [0.00%])

    Percentage of vote: 0.00%

  5. Yes, on a Series 6 (650i or 680i) nForce chipset Intel CPU MOBO, using the verdant_nForce_OSX_Lion_Installer_DVD_Booter (3 votes [5.45%])

    Percentage of vote: 5.45%

  6. Yes, on a Series 6 (610i or 630i) nForce chipset Intel CPU MOBO, using the verdant_nForce_OSX_Lion_Installer_DVD_Booter (0 votes [0.00%])

    Percentage of vote: 0.00%

  7. Yes, on a Series 7 (750i, 780i, or 790i) nForce chipset Intel CPU MOBO, using Snow Leopard from an Installer volume to another HDD/volume (1 votes [1.82%])

    Percentage of vote: 1.82%

  8. Yes, on a Series 6 (650i or 680i) nForce chipset Intel CPU MOBO, using Snow Leopard from an Installer volume to another HDD/volume (2 votes [3.64%])

    Percentage of vote: 3.64%

  9. Yes, on a Series 6 (610i or 630i) nForce chipset Intel CPU MOBO, using Snow Leopard from an Installer volume to another HDD/volume (0 votes [0.00%])

    Percentage of vote: 0.00%

  10. No, none of the above methods has worked for me (6 votes [10.91%])

    Percentage of vote: 10.91%

  11. I have sold or plan to sell my nForce chipset MOBO to go over to the "light" side....Intel chipset MOBO..... (1 votes [1.82%])

    Percentage of vote: 1.82%

  12. I have sold or plan to sell my nForce chipset MOBO to buy a "real" Mac (1 votes [1.82%])

    Percentage of vote: 1.82%

  13. Are you running 10.7.x successfully , having auto-updated without any problems? (7 votes [12.73%])

    Percentage of vote: 12.73%

  14. Are all the standard Apple applications running OK? (9 votes [16.36%])

    Percentage of vote: 16.36%

Would you say that your Lion system is working to your satisfaction (e.g. compared to Snow Leopard)

  1. 100% on (16 votes [27.59%])

    Percentage of vote: 27.59%

  2. Series 7 - 750i, 780i, or 790i (5 votes [8.62%])

    Percentage of vote: 8.62%

  3. Series 6 - 650i, 680i (8 votes [13.79%])

    Percentage of vote: 13.79%

  4. 90% on (7 votes [12.07%])

    Percentage of vote: 12.07%

  5. Series 7 - 750i, 780i, or 790i (4 votes [6.90%])

    Percentage of vote: 6.90%

  6. Series 6 - 650i or 680i (5 votes [8.62%])

    Percentage of vote: 8.62%

  7. 80% on (4 votes [6.90%])

    Percentage of vote: 6.90%

  8. Series 7 - 750i, 780i, or 790i (2 votes [3.45%])

    Percentage of vote: 3.45%

  9. Series 6 - 650i or 680i (3 votes [5.17%])

    Percentage of vote: 5.17%

  10. 70% on (1 votes [1.72%])

    Percentage of vote: 1.72%

  11. Series 7 - 750i, 780i, or 790i (0 votes [0.00%])

    Percentage of vote: 0.00%

  12. Series 6 - 650i or 680i (0 votes [0.00%])

    Percentage of vote: 0.00%

  13. 60% on (0 votes [0.00%])

    Percentage of vote: 0.00%

  14. Series 7 - 750i, 780i, or 790i (0 votes [0.00%])

    Percentage of vote: 0.00%

  15. Series 6 - 650i or 680i (1 votes [1.72%])

    Percentage of vote: 1.72%

  16. 50% on (1 votes [1.72%])

    Percentage of vote: 1.72%

  17. Series 7 - 750i, 780i, or 790i (1 votes [1.72%])

    Percentage of vote: 1.72%

  18. Series 6 - 650i or 680i (0 votes [0.00%])

    Percentage of vote: 0.00%

  19. < 50% on (0 votes [0.00%])

    Percentage of vote: 0.00%

  20. Acceptably on 610i or 630i (0 votes [0.00%])

    Percentage of vote: 0.00%

Is your Lion system working 100% on

  1. SATA HDD (31 votes [13.96%])

    Percentage of vote: 13.96%

  2. SATA DVDRW including burning disks (5 votes [2.25%])

    Percentage of vote: 2.25%

  3. PATA (IDE) HDD (7 votes [3.15%])

    Percentage of vote: 3.15%

  4. PATA (IDE) DVDRW including burning disks (9 votes [4.05%])

    Percentage of vote: 4.05%

  5. Video (22 votes [9.91%])

    Percentage of vote: 9.91%

  6. Onboard LAN (Ethernet) (23 votes [10.36%])

    Percentage of vote: 10.36%

  7. USB devices (mounting/unmounting), plus USB keyboard and USB mouse (25 votes [11.26%])

    Percentage of vote: 11.26%

  8. Firewire (10 votes [4.50%])

    Percentage of vote: 4.50%

  9. PS/2 keyboard and mouse (5 votes [2.25%])

    Percentage of vote: 2.25%

  10. Audio including Front Panel headphones and microphone (11 votes [4.95%])

    Percentage of vote: 4.95%

  11. Audio except Front Panel headphones (4 votes [1.80%])

    Percentage of vote: 1.80%

  12. Audio except Front Panel microphone (5 votes [2.25%])

    Percentage of vote: 2.25%

  13. Sleep including waking from sleep (6 votes [2.70%])

    Percentage of vote: 2.70%

  14. PCI NIC (4 votes [1.80%])

    Percentage of vote: 1.80%

  15. eSATA (3 votes [1.35%])

    Percentage of vote: 1.35%

  16. Bluetooth (10 votes [4.50%])

    Percentage of vote: 4.50%

  17. WiFi (10 votes [4.50%])

    Percentage of vote: 4.50%

  18. Time Machine (6 votes [2.70%])

    Percentage of vote: 2.70%

  19. Overclocking (11 votes [4.95%])

    Percentage of vote: 4.95%

  20. Auto Software Update e.g. to 10.7.x (15 votes [6.76%])

    Percentage of vote: 6.76%

Vote Guests cannot vote

#1
verdant
Posted 28 July 2011 - 11:50 PM

verdant

    InsanelyMac V.I.P.

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

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



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

N.B. This guide is being updated and expanded with time.......at present, please read posts #1, #2, #3, #4, #5, #6.....

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

GUIDE CONTENTS

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

Post #1 - How to Install OS X Lion on a HDD

Breaking News

Introduction

Latest Download Links

Previous Download Links

Acknowledgements

Methods for Installing OS X Lion on a HDD :


Part A. Enabling Snow Leopard running in 64bit mode on an nForce MOBO for OS X Lion Purchase and Download from the Apple App Store

Part B. Making a Bootable GPT Partitioned USB Flash Drive OS X Lion 10.7 Installer

Part C. Installing a Bootable OS X Lion OS 10.7 OS on a GPT Partitioned Hard Drive Using a Bootable GPT USB Flash Drive Installer

Part D. Installing a Bootable OS X Lion OS 10.7 OS on a MBR Partitioned Hard Drive Volume Using a Bootable GPT USB Flash Drive Installer

I have prepared the following BootCD/OS X Lion Base System Installer DVD installation methods for nForce MOBO owners

{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…….

BTW I use DVD+RW disks [rather than DVD-RW due to the claimed built-in defect management of DVD+RW] for [1] convenience (can be re-written up to 1000 times), and [2] long-term data-retention because the recording layer in DVD-RW and DVD+RW is not an organic dye [as used for DVD±R disks] but a phase change material, often GeSbTe chalcogenide glass, that can be transformed back and forth between a crystalline phase and an amorphous phase by a temperature change, also changing the reflectivity, depending on the power of the DVDRW laser beam.

N.B. Since the working 64bit AppleNforceATA.kext from imk does not support SATA DVDRWs for read/write , if you have to use the 64bit AppleNforceATA.kext from imk, then these DVD methods are only for use with PATA (IDE) DVDRWs......  this is because as far as I am aware, MeDevil has never released the source code for his 32bit AppleNForceATA_TEST.kext for SATA DVDRW support; only the source code for his 32bit AppleNForceATA.kext with PATA DVDRW read/write support has been released.  

Part E. Installing a Bootable OS X Lion OS 10.7 OS on a GPT Partitioned Hard Drive Using the verdant_nForce_OSX_Lion_Installer_DVD_Booter

Part F. Installing a Bootable OS X Lion OS 10.7 OS on a MBR Partitioned Hard Drive Using the verdant_nForce_OSX_Lion_Installer_DVD_Booter


Post #2 - Graphic Card Operation in OS X Lion

Getting an nVidia graphics card working in Lion

Getting an ATI graphics card working in Lion

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

Generating an EFI Graphics String for Lion

Inserting Graphics Card Hardware Matching Device ID into nVidia Graphics Kexts


Post #3 - Generating and Modifying the DSDT.aml File for Your Own nForce MOBO

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

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

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

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

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

Post #4 - OS X Lion 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 #5 - Getting Audio Working in Lion

1. Audio via Analog Devices AD1988B CODEC

2. Audio via Realtek ALC885 (ALC889a) CODEC

I will post methods for getting other other audio codecs on nForce chipset MOBOs working in Lion as and when I receive them from nForce MOBO users / readers of this topic.....


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


Post #7 - Resolving the "still waiting for root device" error message on bootup after updating to OS X Lion 10.7.2


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 "Unknown AHCI Standard Controller:" and "Vendor: Unknown"

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 Drive



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

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

BREAKING NEWS

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

1. The Apple Lion Update 10.7.1 (Client) is now available via Software Update, or as a standalone download (as is the Server version).......the 10.7.1 update is recommended for all users running OS X Lion and includes general operating system fixes that enhance the stability and compatibility of your Mac......

Note that it installs a 10.7.1 version of AppleHDA.kext, which means that if you were using the AppleHDA.kext version 10.6.2 in /System/Library/Extensions/ to enable your MOBO audio to function under Snow Leopard 10.6.8 and Lion 10.7.0, then by ensuring that in OS X Lion /System/Library/Extensions/, the 10.7.1 AppleHDA.kext is renamed using Terminal to AppleHDA.kext.1071_Orig, or something similar, so that it becomes a folder in /System/Library/Extensions/ :

sudo mv /System/Library/Extensions/AppleHDA.kext /System/Library/Extension/AppleHDA.kext.1071_Orig

your audio functioning will hopefully be restored as it is for the AD1988B codec...... Posted Image

Unfortunately, however, it does not appear to be that simple for the ALC885 codec........I will keep you updated on this......


2. You may have seen the announcement by Apple of their Lion Recovery Disk Assistant but running the Recovery Disk Assistant.app on my OSx86 /Hackintosh OS X Lion system generates the following message:

Posted Image  Lion_Recovery_Disk_Assistant.png   23.99K   120 downloads

because the USB Installer procedure outlined below, when installing OS X Lion on my OSx86 / Hackintosh PC, has not created a hidden Mac OS X 10.7 Lion Recovery HD volume of around 800MB, which can be seen on a real Mac by typing in the Terminal:

diskutil list

as the following example output shows:

Posted Image  diskutil.gif   20.66K   128 downloads

Note the Apple_Boot Recovery HD......

I installed OS X Lion to a 41 GB GPT partition and have 6.4 GB spare, so it is not a question of insufficient space.......

This is interesting.......although personally I am not a fan of hidden recovery volumes because I like to clone my own bootable backup volumes.......

Nevertheless, it is worth investigating to see how the USB flash drive OS X Lion Installer and/or the target OS X Lion HDD volume need modifying in order for the Lion Installer app to create a hidden Mac OS X 10.7 Lion Recovery HD volume within target OS X Lion HDD volume........

I would be very interested to know if the USB flash drive OS X Lion Installer setup procedure presently described in Part B. below has generated a hidden Mac OS X 10.7 Lion Recovery HD volume within target OS X Lion HDD volume for anyone on their OSx86 / Hackintosh nForce chipset PC.....

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

INTRODUCTION

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

This guide is:

1. Is focussed on installing and running OS X Lion on a Series 6 or 7 nForce chipset / Intel CPU MOBO:

Posted Image  nForce_Chipset_MOBOs.png   568.23K   371 downloads

simply because I have a 650i nForce chipset + Intel Q6600 CPU MOBO........nevertheless, I hope that owners of non-nForce chipset + Intel CPU MOBOs also find it interesting and even helpful too.......

I say this because:

{a} Each reader's MOBO brand/model typically has to have its own custom setup for DSDT/audio/networking/video etc.

{b} it is primarily the need for the AppleNForceATA.imk64bit.kext in /Extra/Extensions/ and nForceLAN.0.64.5.kext in /System/Library/ Extensions/, as well not being able to use a SleepEnabler.kext and having issues with sleep that distinguishes nForce chipset + Intel CPU MOBOs fromnon-nForce chipset + Intel CPU MOBOs rather than the basic procedures for installing OS X......... Posted Image

2. Split into sections and sub-sections (from post #1 to post #8) for ease of following and adding to....

3. A "live guide" that will evolve with both Lion and time (with some inevitable typo corrections, additions, deletions etc.).......So, please read the current online "live" guide before attempting to follow it, even if you had previously followed an earlier version successfully.....

4. Starts with the assumption that you already have OS X Snow Leopard (10.6.6 or later) installed and running in 64bit mode on a Mac or Hack using at least the following 64bit capable kexts in /Extra/Extensions:

AppleNForceATA.imk64bit.kext
EvOreboot.kext or OpenHaltRestart.kext
FakeSMC.kext
NullCPUPowerManagement.kext or Disabler.kext

HOWEVER, if you are currently running OS X Leopard, then see my nForce RETAIL INSTALL GUIDE for Snow Leopard (10.6) on a Series 6 or 7 nForce chipset / Intel CPU MOBO on how to install Snow Leopard.......

While I realise that some of you may have already obtained the OS X Lion 10.7.0 Installer as a .dmg /.iso image file, my working assumption is that most of you will need to have Snow Leopard installed in order to purchase and download the OS X Lion 10.7 Installer from the Apple App Store.......

My plea to all readers is:

Remember Apple are a company not a charity and they will do all they can to protect their market share and profits, and if they ever begin to see the OSx86/Hackintosh web fora as a 'serious threat', they may decide to fully 'lock down' OS X......!

SO PLEASE THANK APPLE FOR THEIR FANTASTIC OS AND FOR NOT FULLY LOCKING IT DOWN TO THEIR OWN HARDWARE BY SUPPORTING FURTHER AND FUTURE APPLE R&D ON OS X IF YOU CAN......

This you can do by:

[1] BUYING AND DOWNLOADING OS X LION 10.7 FROM THE APPLE APP STORE......

[2] IF AND WHEN YOU CAN AFFORD IT, PURCHASING A MAC AND/OR OTHER APPLE PRODUCTS IF THEY CAN DO WHAT YOU NEED THEM TO DO......


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

LATEST DOWNLOAD LINKS

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

SendSpace:

Download 1. verdant_nForce_OSX_Lion_Installer_DVD_Booter

verdant's BootCD and the Netkas boot files for a OS X Lion Mac OS X Base System DVD

Download 2. verdant_Lion_Support_Files_V1.1

verdant_Lion_Support_Files_V1.1>

64bit Kexts for Extra Extensions>
IntelThermal.kext
FakeSMC.kext
SuperIOFamily.kext
NVClockX.kext
ACPIMonitor.kext
IntelCPUMonitor.kext
AppleNForceATA.imk64bit.kext
EvOreboot.kext
AD1998b.FIX.kext
NullCPUPowerManagement.kext

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

Applications>
SMC Monitor
Kext Wizard

Lion FakeSMC> - FakeSMC (3.1.0) - Revision 493. Made by mojodojo
SMC_Stat_i - this is a SMC monitor menu bar app
Release 10.6 - only use the HWSensor kexts in /E/E/ appropriate for your hardware - see 64bit Kexts for Extra Extensions>

64bit Kexts for Sys_Lib_Extensions>
AppleRTC.Patched.kext
nForceLAN.0.64.5.kext
AppleHDA.1062.kext
AppleRTC.10.6.8.kext

CUDA 4.0 for Lion>
devdriver_4.0.21_macos.dmg - this is the image file for CUDADriver.pkg
CUDADriver.pkg

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

Chameleon 2.0 RC5 r1200 VS Installer>
Chameleon_2_RC5_VS.dmg

Chameleon 2.0 RC5 r1191 Themes and Extra .plist Files>
Themes
org.chameleon.Boot.plist
smbios.plist

Chameleon 2.0 RC5 r1191 VS Installer>
Chameleon 2 RC5 VS.dmg


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

PREVIOUS DOWNLOAD LINKS

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

Later versions of my Lion Support Files will have additions and/or deletions as time proceeds.....

SendSpace:

verdant_Lion_Support_Files_v1.0

Chameleon RC5 r1191 Themes and Extra .plist Files >
Themes
org.chameleon.Boot.plist
smbios.plist

64bit Kexts for Sys_Lib_Extensions >
FakeSMC.kext
nForceLAN.0.64.5.kext
AppleHDA.1062.kext
AppleRTC.kext

64bit Kexts for Extra Extensions >
IOATAFamily.RootBoot.kext - this is a Snow Leopard kext that may/may not speed bootup in Lion
AppleNForceATA.imk64bit.kext
EvOreboot.kext
AD1998b.FIX.kext - this is a AD1988B legacy kext for use with a DTGP and HDEF patched DSDT
NullCPUPowerManagement.kext

Chameleon 2 RC5 r1191 VS Installer >
Chameleon 2 RC5 VS.dmg

Note that Lion Support Files v1.0 is a just preliminary collection of the initial installers, .plist files, kexts etc. that I have used to get Lion OS X installed and running on my own Asus P5N32E SLI Plus (nForce 650i) MOBO........

Audio and USB are working fine.......but there are other still functions to be sorted out if possible.......I have not even considered sleep/waking, as it is not a function I use on my Desktop.......I still have to check out FireWire.....


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

ACKNOWLEDGEMENTS

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

ALL CREDIT goes (in no particular order) the original developers of the included applications/kexts/bootloaders and boot files etc:

In /Extra/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

In /System/Library/Extensions/

nForceLAN.0.64.5.kext – eno

In boot sector, / and /Extra/

Chameleon 2.0 RC5 r1191 –meklort has now enabled the BuildBot to host automatically compiled binaries of the latest Chameleon trunk: http://builds.voodoo...cts.org/builds/

Thanks to everyone involved in the development of Chameleon 2.0 RC5, making it a compatible bootloader for Lion......!

Evan Lojewski, Kabyl, Cosmosis Jones, Tamás Kosárszky, Rekursor, Blackosx, JrCs, DieBuche, Pradeesh, Charles Delorean, Andy Vandijck, naw com, Master Chief, mozodojo, valv, armel cadet-petit, MacMan, Daniel, Miranda, iFabio iFabio, Sergey Slice.

Not forgetting netkas for PC_EFI v10.6 and v10.7........ Posted Image

Thanks also to MaLd0n for the MacPro3,1 SMBIOS.plist
http://www.insanelym...howtopic=256729

Apologies to anyone I have forgotten, or do not know to mention, or have yet to mention in the above credits as the guide is expanded in due course......

For example, the coder of the Chameleon 2.0 RC5 r1191 [VS] .dmg installer and later Chameleon 2.0 RC5 revision [VS] installers - if anyone knows the coder(s) of the installer, please tell me, so that I can acknowledge their work......

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

Methods for Installing OS X Lion on a HDD

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

This section covers {a} the USB flash drive OS X Lion installer method and {b} my OS X Lion Boot CD + OS X Lion DVD installer method for installing OS X Lion on a GPT Partitioned HDD and/or on a MBR Partitioned HDD.


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

Part A. Enabling Snow Leopard running in 64bit mode on an nForce MOBO for OS X Lion Purchase and Download from the Apple App Store

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

According to Apple, to upgrade to OS X Lion, the following must be done:

Step 1: Make sure your Mac can run Lion.

Your Mac must have an Intel Core 2 Duo, Core i3, Core i5, Core i7 or Xeon processor to run Lion. Find out if your current Mac has one of these processors by clicking the Apple icon at the top left of your screen, then choosing About This Mac.

General requirements

* Mac computer with an Intel Core 2 Duo, Core i3, Core i5, Core i7, or Xeon processor
* 2GB of memory
* OS X v10.6.6 or later (v10.6.8 recommended)
* 7GB of available space
* Some features require an Apple ID

Step 2: Make sure you have the latest version of Snow Leopard.

Get up to date with the latest version of OS X Snow Leopard to purchase OS X Lion from the Mac App Store. If you have Snow Leopard, click the Apple icon and choose Software Update to install the latest version, which is 10.6.8.

Step 3: Download OS X Lion from the Mac App Store.

Open the Mac App Store from your Dock to buy and download Lion. Then follow the onscreen instructions to install it.


In the case of OSx86 / Hackintosh PCs, the equivalent steps are:

Step 1: Make sure your OSx86 / Hackintosh PC can run Lion.

Initial Requirements:

* At least 2GB of memory
* OS X v10.6.6 or later (v10.6.8 recommended) running in 64bit mode
* At least 7GB of available space
* Some features require an Apple ID and password

Further Requirements:

[1] If your PC has a CPU that System Profiler lists as 'Unknown' even though it is an Intel CPU, it is not just a case of editing:

[i] The AppleSystemInfo.strings "UnknownCPUKind" entry from "Unknown" to, for example, "Intel® Core™2 Quad CPU Q6600" (found in OS X 10.6.8 /System/Library/CoreServices/Resources/English.lproj/}.

[ii] The AboutThisMac.strings for Processor text fields in the About This Mac window (found in 10.6.8 /System/Library/CoreServices/loginwindow.app/Contents/Resources/), to get, for example, "3.0 MHz Intel® Core™2 Quad CPU Q6600" to display properly in the About This Mac window.

because these changes are purely cosmetic......OS X still regards your CPU as Unknown......consequently, some software installers (if not hacked) will fail to install because the CPU is not properly detected, e.g. the Microsoft Silverlight installer.

The solution is to use a bootloader with auto-CPU detection (following the work of DigitalDJ; see here).

RECOMMENDATION: Try using a recent/current Chameleon v2.0 RC5 bootloader version, such as Chameleon 2.0 RC5 r1191, or Chameleon 2.0 RC5 r1200, etc.

meklort has now enabled the BuildBot to host automatically compiled binaries of the latest Chameleon trunk: http://builds.voodoo...cts.org/builds/
Hence, with a Core2Quad CPU, e.g. Q6600, the Chameleon v2.0 RC5 bootloader will inject a "Quad-Core Intel Xeon" CPU-type......

[2] It is necessary to use a SMBIOS.plist which gives 'vaild' details as far as OS X Snow Leopard and Lion are concerned for the following keys:

SMbiosdate
SMbiosversion
SMboardproduct
SMfamily
SMmanufacter
SMproductname
SMserial

because in OS X Lion 10.7 /System/Library/CoreServices/PlatformSupport.plist, there is a list of Supported Board IDs:

Mac-F2268DC8
Mac-F22C86C8
Mac-F22587C8
Mac-F2218FA9
Mac-F2218EA9
Mac-F42D86A9
Mac-F22C8AC8
Mac-F22586C8
Mac-942B59F58194171B
Mac-F226BEC8
Mac-F4218FC8
Mac-942459F5819B171B
Mac-F4218EC8
Mac-F2208EC8
Mac-F22C89C8
Mac-F22587A1
Mac-F221DCC8
Mac-F42388C8
Mac-F223BEC8
Mac-F4238CC8
Mac-F222BEC8
Mac-F227BEC8
Mac-F4208AC8
Mac-F22788A9
Mac-F4238BC8
Mac-F221BEC8
Mac-F2238AC8
Mac-F4208EAA
Mac-F22788C8
Mac-F22589C8
Mac-F4228EC8
Mac-F22788AA
Mac-F42C86C8
Mac-F4208CA9
Mac-942C5DF58193131B
Mac-F2238BAE
Mac-F42289C8
Mac-F2268CC8
Mac-F4208DC8
Mac-F2218FC8
Mac-F2218EC8
Mac-F4208DA9
Mac-F42D89C8
Mac-F4208CAA
Mac-F42D89A9
Mac-F2268AC8
Mac-F42C89C8
Mac-942452F5819B1C1B
Mac-F42786A9
Mac-F42D88C8
Mac-F42187C8
Mac-94245B3640C91C81
Mac-F42D86C8
Mac-F2268EC8
Mac-F2268DAE
Mac-F42C8CC8
Mac-F42C88C8
Mac-94245A3940C91C80
Mac-F42386C8
Mac-942B5BF58194151B
Mac-F42189C8

Recommendation: Use the very useful Extra Folder Installer posted by MaLd0n here and run the Installer with the Extra Folder option UNCHECKED but CHECK the smbios.plist option that is applicable to your CPU:

iMac9,1 >>> Intel Core 2 Duo ("Penryn")

iMac10,1 >>> Intel Core 2 Duo ("Wolfdale")

iMac11,1 >>> Core i5, or Core i7 ("Nehalem")

iMac11,2 >>> Intel Core i3 or Core i5 ("Clarkdale")

iMac11,3 >>> Intel Core i3, Core i5, or Core i7 ("Clarkdale, Lynnfield")

iMac12,1 >>> Intel Core i5 or Core i7 ("Sandy Bridge")

iMac12,2 >>> Intel Core i5 or Core i7 ("Sandy Bridge")

MacBook2,1 >>> Intel Core 2 Duo Mobile ("Merom") / Intel Graphics Media Accelerator (GMA) 950

MacBook4,1 >>> Intel Core 2 Duo Mobile ("Penryn") / Intel Graphics Media Accelerator (GMA) X3100

MacBookPro4,1 >>> Intel Core 2 Duo Mobile ("Penryn") / NVIDIA GeForce

MacBookPro6,1 >>> Intel Core i5 or Core i7 Mobile ("Arrandale") / NVIDIA GeForce and Intel HD Graphics

MacBookPro8,1 >>> Intel Core i5 or Core i7 Mobile ("Sandy Bridge") / Intel HD Graphics 3000

MacBookPro8,3 >>> Intel Core i7 Mobile ("Sandy Bridge") / AMD Radeon HD and Intel HD 3000 Graphics

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

MacPro4,1 >>> Intel Xeon 3500 or 5500 series ("Bloomfield, Gainestown") / Use for Core i Nehalem/ Quad Core HT / Line 9xx

MacPro5,1 >>> Intel Xeon W3530, W3565, W3680, E5620, X5650, or X5670 ("Bloomfield, Westmere") / Use for Core i Nehalem/ Quad or Six Core HT / Line 9xx

I have found that without the correct SMBIOS.plist details, i.e. all the details recognisable as 'valid' by the Apple App Store, it is not possible to purchase and download the Install Mac OS X Lion app from the App Store, even though other software can be purchased and downloaded via the App Store using a 'validated' Apple ID......

For example, I have found that using SMBIOS.plist details for a MacPro2,1 with my Core2Quad Q6600 CPU, which results in my OSx86 / Hacintosh PC being recognised by Geekbench as a Mac:

Posted Image  GeekBench_Screen_shot_MacPro2_1.png   29.22K   199 downloads

did not enable the purchase and download of the Install Mac OS X Lion app, whereas using 'valid' SMBIOS.plist details for a MacPro3,1 (thanks to MaLd0n), which results in my OSx86 / Hackintosh PC being recognised by Geekbench as a Hackintosh:

Posted Image  Geekbench_Scree_shot_MacPro3_1.png   38.77K   145 downloads

did enable the purchase and download of the Install Mac OS X Lion app.....!

So, a OSx86 / Hackintosh PC being recognised by Geekbench as a Hackintosh is not necessarily an obstacle to being able to purchase and download the Install Mac OS X Lion app from the Apple App Store........

Step 2: Make sure you have the latest version of Snow Leopard.

While Apple have recommended using the latest version OS X Snow Leopard version, which is 10.6.8 (make sure you run Software Update, so that the recently released Mac OS X 10.6.8 Supplemental Update is installed; alternatively, you can download and run the standalone Mac OS X 10.6.8 Update Combo v1.1.....

However, some IM members have had problems with 10.6.8 but success with 10.6.7 when attempting to purchase and download the Install Mac OS X Lion app.....so, if 10.6.8 does not work for you, try 10.6.7, or even 10.6.6.....

Step 3: Download OS X Lion from the Mac App Store.

Before attempting to purchase and download the Install Mac OS X Lion app from the Apple App Store, you should check the following:

[i] That you can enter your Apple ID and password and have it accepted.......

If you have problem, then follow the procedure recommended by Apple here.....the procedure has worked for me on an Ethernet connection.....

[ii] That you can start the process of purchasing software from the App Store......

[iii] Read Section 1 of Part B. of this guide (in post #1)

If [i] and [ii] are achievable and [iii] has been done, then you should hopefully be able to open the Mac App Store from your Dock to buy and download Lion BUT DO NOT click on the “Install Mac OS X Lion” installer app icon that will show up in the Dock......If you still have problems then try the following:

[1] Go to System Preferences >>>> Network......select your Network Service i.e. Ethernet or AirPort in the sidebar and click the '-' tab at the sidebar bottom, which will delete the service

[2] Modify your org.chameleon.Boot.plist by adding in the following:

EthernetBuiltIn
Yes

If you have a PIC NIC installed it may also be necessary to add an entry in org.chameleon.Boot.plist for PCIRootUID because a MOBO may have pciroot = 0 or pciroot=1, shown here for pciroot=1:

PCIRootUID
1

To find your pciroot value, use this command in Terminal:

ioreg -l | grep -15  "AppleACPIPCI" | grep "_UID"

which should give "_UID" = "1" or "_UID" = "0".

[3] Reboot into OS X Lion and again go to System Preferences >>>> Network......but now click the '+' tab at the sidebar bottom, to add a new Network Service named Ethernet (en0) for your LAN service.....

I have a PIC NIC that is connected to the internet under the Network Service name 'Ethernet Adaptor (en0)' but is seen as built-in......System Profiler says against Ethernet Cards: This computer does not appear to have any PCI Ethernet cards installed.

I wish you the same success I had in purchasing and downloading the Install Mac OS X Lion app from the Apple App Store...... Posted Image

If you have problems with using

EthernetBuiltIn
Yes

and/or

PCIRootUID
1

then go to post #4 Issue 2 Setting up Builtin Ethernet / LAN0 / (en0)


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

Part B. Making a Bootable GPT Partitioned USB Flash Drive OS X Lion 10.7 Installer

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

1. You will need:

[1] Access to a working Mac or Hack x86 OS X Snow Leopard 10.6.8 system

(10.6.8 is better than 10.6.6 or 10.6.7 because it protects against MacDefender and may work better with App Store)

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

[3] To be able to purchase and download OS X Lion from the Apple App Store. See Part A.

[4] To download my "verdant_Lion_Support_Files_v1.1.zip" folder

The “Install Mac OS X Lion” 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 Lion Installer App

[1] Boot into Snow Leopard and go to the Applications folder and find Install Mac OS X Lion 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 Mac OS X Lion 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 Snow Leopard 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 directory files and Chameleon 2.0 RC5 r1191 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_Lion_USB_Installer volume.....doing this puts a base OS X Lion 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.

The USB flash drive device name will be automatically changed to Mac 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 3.26 GB Packages folder will take about 10 or minutes to copy over……

Also 'drag and drop' the mach_kernel file from the open Mac OS X Install ESD window into the into the USB flash drive volume's / directory…….i.e. into the open Mac OS X Base System Window……

[3] Run the Chameleon 2.0 RC5 r1191 [VS] .dmg installer (in the Lion_Support_Files_v1.1 folder) and double-click on the Install Chameleon icon in the Chameleon 2 RC5 VS window…….then click Continue…..accept the default-selected Chameleon (you do not not need to select Theme unless you want to, or AppleEMC, which installs the AppleEMC kext for iMac recognition....UNLESS you need to use an iMac SMBIOS.plist because of your CPU and find that having AppleEMC kext installed 'helps' the App Store recognize your OSx86 / Hacintosh PC).

Click Continue again……THEN click Change Install Location and select the USB flash drive Mac OS X Base System volume in the Select a Destination window and click Continue……then click Install…..after a hopefully successful install, click Close....

[4] Go back to the open Mac OS X Base System Window……the Chameleon bootloader installer should have created the /Extra/ and /Extra/Extensions/ directories or folders……

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

[6] Copy across from your running 64bit mode Snow Leopard system, or from the Lion Support Files v1.1 folder, into /Extra on 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 you have run the Chameleon 2.0 RC5 r1191 [VS] .dmg installer on your running 64bit mode Snow Leopard system)

Also copy across (if you wish) your Chameleon v2.0 RC5 r1191 Themes folder from your running 64bit mode Snow Leopard system, or from the Lion Support Files v1.1 folder....

[7] Copy the following kexts in /Extra/Extensions/ on your running 64bit mode Snow Leopard system, or from the Lion Support Files v1.1 folder, into /Extra/Extensions/ on the USB flash drive Mac OS X Base System volume...

AD1998b.FIX.kext
AppleNForceATA.imk64bit.kext
EvOreboot.kext
NullCPUPowerManagement.kext

You may also have AppleHDA.10.6.2.kext, FakeSMC.kext and nForceLAN.0.64.5.kext in /Extra/Extensions/.

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 [8] below:

[8] 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, then these need to copied from there, or from the Lion Support Files v1.1 folder, into /System/Library/Extensions/ on the USB flash drive Mac OS X Base System volume……

[9] Having added AppleHDA.10.6.2.kext, FakeSMC.kext and nForceLAN.0.64.5.kext to /System/Library/Extensions/ on the USB flash drive Mac 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/Mac\ OS\ X\ Base\ System/System/Library/Extensions
sudo chmod -R 755 /Volumes/Mac\ OS\ X\ Base\ System/System/Library/Extensions
sudo touch /Volumes/Mac\ OS\ X\ Base\ System/System/Library/Extensions

followed by

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

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

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

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

IOKitPersonalities_i386.ioplist.gz
IOKitPersonalities_x86_64.ioplist.gz
kernelcache
KextPropertyValues_OSBundleHelper_i386.plist.gz
KextPropertyValues_OSBundleHelper_x86_64.plist.gz

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

Posted Image  USB_with_All_Extra_Stuff.png   189.43K   198 downloads

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


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

This guide is being typed up from OS X Lion at present....... Posted Image

Posted Image  Lion_OS.png   471.47K   195 downloads

So far I have not experienced any problems e.g. freezes etc. during hours of use....... Posted Image

Here are my system details:

1. Software Info:

System Version: Mac OS X 10.7 (11A511)
Kernel Version: Darwin 11.0.0
Secure Virtual Memory: Enabled
64-bit Kernel and Extensions: Yes

2. Hardware Info:

Model Name: Mac Pro
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 3.00 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache: 8 MB
Memory: 6 GB
Bus Speed: 1.33 GHz
Boot ROM Version: MP31.006C.B05
SMC Version (system): 1.30f3

3. Loaded Kexts from /Extra/Extensions/:

AD1998b.FIX.kext
AppleNForceATA.imk64bit.kext
EvOreboot.kext
FakeSMC.kext
NullCPUPowerManagement.kext

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

Part C. Installing a Bootable OS X Lion OS 10.7 OS on a GPT Partitioned Hard Drive Using a Bootable GPT USB Flash Drive Installer

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

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

[1] Use the running Snow Leopard Disk Utility to partition/format your target HDD volume for OS X 10.7 as GPT/HFS+ volume named OSX_10.7_GPT_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 -> Get Info. If the checkbox next to "Ignore ownership on this volume" is checked then click on 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.7 hard drive........

[2] Now close all open windows on the Snow Leopard 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 Lion 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 Mac OS X Base System volume and follow the onscreen Mac OS X Installer instructions to install OS X Lion onto the target HDD volume.....

[3] Re-boot back into OS X Snow Leopard and run the Chameleon 2.0 RC5 r1191 [VS] .dmg installer (in the Lion_Support_Files_v1.1 folder) and double-click on the Install Chameleon icon in the Chameleon 2 RC5 VS window…….then click Continue…..accept the default-selected Chameleon and select Theme (you do not need to select AppleEMC, which installs the AppleEMC kext for iMac recognition….UNLESS you need to use an iMac SMBIOS.plist because of your CPU and find that having AppleEMC kext installed 'helps' the App Store recognize your OSx86 / Hacintosh PC).

Click Continue again……THEN click Change Install Location and select the target HDD OS X Lion 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 but note that in the Chameleon 2.0 RC5 r1191 [VS] update, com.apple.Boot.plist is renamed to org.chameleon.Boot.plist in /Extra, now that Chameleon uses org.chameleon.Boot.plist instead of com.apple.Boot.plist......

[5] Go back to the open target HDD OS X Lion System Window……the Chameleon bootloader installer should have created the /Extra/ and /Extra/Extensions/ directories or folders……

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

[7] Copy across from your running 64bit mode Snow Leopard system, or from the Lion Support Files v1.1 folder, 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 you have run the Chameleon 2.0 RC5 r1191 [VS] .dmg installer on your running 64bit mode Snow Leopard system)

Also copy across (if you wish) your Chameleon v2.0 RC5 r1191 Themes folder from your running 64bit mode Snow Leopard system…..

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

AD1998b.FIX.kext
AppleNForceATA.imk64bit.kext
EvOreboot.kext
NullCPUPowerManagement.kext

You may also have AppleHDA.10.6.2.kext, FakeSMC.kext and nForceLAN.0.64.5.kext in /Extra/Extensions/.……

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 [8] 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, then these need to copied from there, or from the Lion Support Files v1.1 folder, into /System/Library/Extensions/ in the open target HDD OS X Lion System Window……

[10] Having added AppleHDA.10.6.2.kext, FakeSMC.kext and nForceLAN.0.64.5.kext to /System/Library/Extensions/ on the open target HDD OS X 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….

IOKitPersonalities_i386.ioplist.gz
IOKitPersonalities_x86_64.ioplist.gz
kernelcache
KextPropertyValues_OSBundleHelper_i386.plist.gz
KextPropertyValues_OSBundleHelper_x86_64.plist.gz

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

[12] 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......

Then as a workaround 'drag and drop' the AppleRTC.kext (Snow Leopard AppleRTC.kext) from the Lion Support Files v1.0 folder into /System/Library/Extensions/ on the open target HDD OS X Lion System window......

Alternatively, you can patch your own OS X Lion AppleRTC.kext by running this perl script in Terminal, which has been posted by rayap, which forces an unconditional jump over the rtcWrites() in updateChecksum() to prevent CMOS Resets:

sudo perl -pi -e 's|\x75\x30\x44\x89\xf8|\xeb\x30\x44\x89\xf8|; s|\x75\x3d\x8b\x75\x08|\xeb\x3d\x8b\x75\x08|' /System/Library/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC

Now 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 /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….

IOKitPersonalities_i386.ioplist.gz
IOKitPersonalities_x86_64.ioplist.gz
kernelcache
KextPropertyValues_OSBundleHelper_i386.plist.gz
KextPropertyValues_OSBundleHelper_x86_64.plist.gz

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

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

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


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

Part D. Installing a Bootable OS X Lion OS 10.7 OS on a MBR Partitioned Hard Drive Volume Using a Bootable GPT USB Flash Drive Installer

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


Procedure 1. (No pre-existing Lion OS installation)

This procedure assumes that you have already followed "Part B. Making a Bootable GPT Partitioned USB Flash Drive OS X Lion 10.7 Installer" of this guide, and now have a working bootable GPT USB Flash Drive Installer......

In order for you to install OS X Lion 10.7 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 Lion Installer on your bootable GPT USB Flash Drive Installer uses......

There are two versions of OSInstall.mpkg and OSInstall that I have used:

Version 1 patcher: nawcom's GM MBR Patch

Create a folder named "nawcom MBR Patch" on your Desktop, and then download and unarchive Lion_OSInstall_GM.tar.bz2 file into it…….the unarchived System folder contains the modified OSInstall.mpkg package and the OSInstall Unix executable file, nested in Installation and Library, respectively….

Alternatively, here is a zipped archive for your convenience: Posted Image

MBR_Patch_for_OS_X_Lion_GM___by_nawcom.zip   701.95K   50 downloads

Version 2 patcher: MBR Patch 10.7.0 11A511 - by xpertvision

The binpatched OSInstall "framework" and "OSInstall.mpkg" in MBR Patch 10.7.0 11A511: Posted Image

MBR_Patch_10.7.0_11A511___by_Xpertvision.zip   707.73K   56 downloads

are modified versions of the original patches by nawcom, to enable the installation of OS X Lion 10.7.0 (11A511 release) onto a target HDD volume partitioned/formatted as MBR/HFS+, which are patched to:

[1] Overcome the default 2GB RAM limit for installation, allowing installation even on PCs having only 1GB RAM installed......but note these comments by smartie77:

Quote

running Lion with only 1 or 1.5 GB would be a pain leaving it in its default 64bit mode with all features on but the beast can be tamed a lot :

If for all you should only run it in 32bit mode this makes the biggest change in memory usage, then the next biggest turn off spotlight to a large degree, mainly the full text indexing of pdf,mail and websites; exclude all folders that are not your home folder and run most apps in 32bit mode only, not only the apps in /Applications but also the system apps in /System/Library/CoreServices - right click them "get info" and checkmark "run in 32bit mode" wherever it is available. Try slimming down the kexts - if you have a ATI for example throw out all IntelGMA,Nvidia etc kexts. If you have no thunderbolt and Firewire - out with them . No ATTO and Promise cards = rid off them..

Turn off the auto-reopening of all open windows and apps ( Lion constantly writes apps changing states, open documents and version changes to your hidden Home Library ).

There is more to tweak, time will tell.. Lion has a loads of background services running that were not in SL. And Apple seems to collect a lot of user and performance metric data .. Have a look in Systems LaunchAgents/Launchdaemons plists, there is way too much, but as of yet I cannot say what is safe to delete there.


[2] Custom Install Options added:

Language packs (select the language packs you want to install)

Server Install (install server options or not) - provided that you have the the OS X Lion 10.7.0 Server Installer as a .dmg /.iso image file and hence its Mac OS X Base System volume on your OS X Lion USB Flash Drive Installer.....


The procedure for installing the modified OSInstall.mpkg package and OSInstall Unix executable file on your bootable GPT USB Flash Drive Installer in place of the original OS X Lion Installer versions is the same, whichever version patcher you choose to use, and is as follows:

1. Unhide the hidden and systems files on your OS X Lion USB Flash Drive Installer, named Mac 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/Mac\ OS\ X\ Base\ System/System/Installation/Packages

or type

cd

and press the 'Space Bar', and then having navigated to System >>>> Installation >>>> 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/Mac\ 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 >>>> Library >>>> PrivateFrameworks >>>> Install.framework >>>> Frameworks >>>> OSInstall.framework >>>> Versions >>>> A, '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/Mac\ 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/Mac\ 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/Mac\ OS\ X\ Base\ System/System/Installation/Packages......(or use cp command via Terminal):

sudo cp -p -R /Users/"User Name"/Desktop/nawcom\ MBR\ Patch/System/Installation/Packages/OSInstall.mpkg /Volumes/Mac\ OS\ X\ Base\ System/System/Installation/Packages

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

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

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

6. Now follow the following procedure to install OS X Lion 10.7 onto your target HDD volume partitioned/formatted as MBR/HFS+ :


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

[1] Use the running Snow Leopard Disk Utility to partition/format your target HDD volume for OS X 10.7 as MBR/HFS+ volume named OSX_10.7_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 -> Get Info. If the checkbox next to "Ignore ownership on this volume" is checked then click on 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.7 hard drive........

[2] Now close all open windows on the Snow Leopard 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 Lion 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 Mac OS X Base System volume and follow the onscreen Mac OS X Installer instructions to install OS X Lion onto the target HDD volume.....

[3] Re-boot back into OS X Snow Leopard and run the Chameleon 2.0 RC5 r1191 [VS] .dmg installer (in the Lion_Support_Files_v1.1 folder) and double-click on the Install Chameleon icon in the Chameleon 2 RC5 VS window…….then click Continue…..accept the default-selected Chameleon and select Theme (you do not need to select AppleEMC, which installs the AppleEMC kext for iMac recognition….UNLESS you need to use an iMac SMBIOS.plist because of your CPU and find that having AppleEMC kext installed 'helps' the App Store recognize your OSx86 / Hacintosh PC).

Click Continue again……THEN click Change Install Location and select the USB flash drive Mac OS X Base System volume 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 but note that in the Chameleon 2.0 RC5 r1191 [VS] update, com.apple.Boot.plist is renamed to org.chameleon.Boot.plist in /Extra, now that Chameleon uses org.chameleon.Boot.plist instead of com.apple.Boot.plist......

[5] Go back to the open target HDD OS X Lion System Window……the Chameleon bootloader installer should have created the /Extra/ and /Extra/Extensions/ directories or folders……

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

[7] Copy across from your running 64bit mode Snow Leopard system, or from the Lion Support Files v1.1 folder, 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 you have run the Chameleon 2.0 RC5 r1191 [VS] .dmg installer on your running 64bit mode Snow Leopard system)

Also copy across (if you wish) your Chameleon v2.0 RC5 r1191 Themes folder from your running 64bit mode Snow Leopard system…..

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

AD1998b.FIX.kext
AppleNForceATA.imk64bit.kext
EvOreboot.kext
NullCPUPowerManagement.kext

You may also have AppleHDA.10.6.2.kext, FakeSMC.kext and nForceLAN.0.64.5.kext in /Extra/Extensions/.……

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 [8] 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, then these need to copied from there, or from the Lion Support Files v1.1 folder, into /System/Library/Extensions/ in the open target HDD OS X Lion System Window……

[10] Having added AppleHDA.10.6.2.kext, FakeSMC.kext and nForceLAN.0.64.5.kext to /System/Library/Extensions/ on the open target HDD OS X 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….

IOKitPersonalities_i386.ioplist.gz
IOKitPersonalities_x86_64.ioplist.gz
kernelcache
KextPropertyValues_OSBundleHelper_i386.plist.gz
KextPropertyValues_OSBundleHelper_x86_64.plist.gz

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

[12] 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......

Then as a workaround 'drag and drop' the AppleRTC.kext (Snow Leopard AppleRTC.kext) from the Lion Support Files v1.0 folder into /System/Library/Extensions/ on the open target HDD OS X Lion System window......

Alternatively, you can patch your own OS X Lion AppleRTC.kext by running this perl script in Terminal, which has been posted by rayap, which forces an unconditional jump over the rtcWrites() in updateChecksum() to prevent CMOS Resets:

sudo perl -pi -e 's|\x75\x30\x44\x89\xf8|\xeb\x30\x44\x89\xf8|; s|\x75\x3d\x8b\x75\x08|\xeb\x3d\x8b\x75\x08|' /System/Library/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC

Now 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 /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….

IOKitPersonalities_i386.ioplist.gz
IOKitPersonalities_x86_64.ioplist.gz
kernelcache
KextPropertyValues_OSBundleHelper_i386.plist.gz
KextPropertyValues_OSBundleHelper_x86_64.plist.gz

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

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

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

Procedure 2. (Pre-existing OS X Lion system installation)

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

2. Install the Chameleon RC5 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 OS X Lion OS on the MBR/HFS+ partition/volume.....


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

Part E. Installing a Bootable OS X Lion OS 10.7 OS on a GPT Partitioned Hard Drive Using the verdant_nForce_OSX_Lion_Installer_DVD_Booter

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

I have prepared the following BootCD/OS X Lion Base System Installer DVD installation methods for nForce MOBO owners {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…….

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

[1] Use the running Snow Leopard Disk Utility to partition/format your target HDD volume for OS X 10.7 as GPT/HFS+ volume named OSX_10.7_GPT_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 -> Get Info. If the checkbox next to "Ignore ownership on this volume" is checked then click on 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.7 hard drive........

[2] Download the verdantChameleonLionBootDVD.iso image file and the required i386 boot files

[3] Go to the Applications folder and find Install Mac OS X Lion WITHOUT clicking on the icon NOR right-click on the icon and selecting Open

[4] 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......

[5] Right-click on the Install Mac OS X Lion installer icon and select Show Package Contents.

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

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

[7] Create a folder on your Desktop called Mac OS X Base System

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

[9] 'Select All' files in the open BaseSystem window and copy them into the Mac OS X Base System folder that you created on your Desktop

[10] Open the System folder in the Mac OS X Base 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 3.26 GB Packages folder will take about 10 or minutes to copy over……

[11] Now 'drag and drop' the mach_kernel file from the open Mac OS X Install ESD window into the into the Mac OS X Base System folder…….

[12] Copy via Terminal or via 'drag and drop' the OSx86 boot files by netkas [i.e. PC_EFI v10.6 boot files (boot0, boot1h and cdboot) and 10.7 boot file (boot)] into /Users/"User Name"/Desktop/Mac\ OS\ X\ Base\ System/usr/standalone/i386,

i.e. in non-Terminal "speak" go to Desktop >>>> Mac OS X Base System >>>> usr >>>> standalone >>>> i386

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

For those of you who are interested, only the cdboot file is used to boot the MacOSXBaseSystemDVD but I have put the PC_EFI v10.6 boot files (boot0, boot1h and cdboot) and 10.7 boot file (boot) file into the i386 folder because some users may experience the following bootup freeze-causing error when trying to boot from the OS X Lion system they have installed on their HDD volume (by USB installer, or my DVD installer, or HDD partition installer):

BootCacheControl: Unable to open /var/db/BootCache.playlist: 2 no such file or directory
Bug:launchctl.c:2408 (24687):30: cdefd =open (g_overrides_db_patch....

and it has been reported by some with this problem that using the netkas PC_EFI v10.6 boot0 and boot1h files and the 10.7 boot file has overcome this problem, while using even the newer versions of the Chameleon 2.0 RC5 bootloader has not.............

To install these files manually on your target OS X Lion HDD/volume, you can use Terminal commands......follow this guide..........

Assuming your installation is on /dev/disk0s2

Install v10.6 boot0 to the MBR:
sudo ./fdisk440 -f boot0 -u -y /dev/rdisk0

Install v10.6 boot1h to the partition's bootsector:
sudo dd if=boot1h of=/dev/rdisk0s2

Install v10.7 boot to the partition's root directory:
sudo cp boot /

Alternatively, you can just download and run a PC_EFI v10.6 installer package and then just unhide the hidden/system files and delete the boot file in the root directory / and copy the PC_EFI v10.7 boot file into the / directory......

Also, see the post by akimoa here.....google for the PC efi 10.7 boot file from netkas or use this one http://cl.ly/3x0p0B041H3g3c2O3p2b

If you still have no joy, then try this version of fakesmc.kext posted by rubahgeni in IM that he extracted from ###### 3.8.0, as it sorted the launchctl.c error for him allowing him to boot the Lion installer......

FakeSMC.kext.zip   30.01K   1 downloads

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

[13] Now go to /Users/"User Name"/Desktop/Mac\ OS\ X\ Base\ System/System/Library/CoreServices/,

i.e. in non-Terminal "speak" go to Desktop >>>> Mac 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……

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

sudo chown -R 0:0 /Users/"User Name"/Desktop/Mac\ OS\ X\ Base\ System

[15] Then in Terminal type:

 sudo hdiutil makehybrid -o MacOSXBaseSystemDVD.iso /Users/"User Name"/Desktop/Mac\ OS\ X\ Base\ System  -iso -hfs -joliet -eltorito-boot /Users/"User Name"/Desktop/Mac\ OS\ X\ Base\ System/usr/standalone/i386/cdboot -no-emul-boot -hfs-volume-name "MacOSXBaseSystemDVD" -joliet-volume-name "MacOSXBaseSystemDVD"

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 MacOSXBaseSystemDVD.iso in the /Users/"User Name"/ directory

[16] Burn this .iso image file to a DVD at x4 or slower

[17] Burn the verdantChameleonLionBootDVD.iso image file to a CD……..

[18] Have the MacOSXBaseSystemDVD ready to hand and then insert the verdantChameleonLionBootCD into your DVDRW and boot from it………..follow the boot screen instructions…..I recommend you choose -v as a boot flag before booting from the MacOSXBaseSystemDVD, so that you can see what is happening onscreen…….

BE PREPARED - booting from the DVD is very slow - from booting the MacOSXBaseSystemDVD to reaching the Mac OS X Installer Desktop takes 13 minutes........thus the OS X Lion system installation process takes even longer......

This is because [i] all kexts are loaded directly from /System/Library/Extensions/ and [ii] the OS X Lion 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)……..

[19] Re-boot back into OS X Snow Leopard and run the Chameleon 2.0 RC5 r1191 [VS] .dmg installer (in the Lion_Support_Files_v1.1 folder) and double-click on the Install Chameleon icon in the Chameleon 2 RC5 VS window…….then click Continue…..accept the default-selected Chameleon and select Theme (you do not need to select AppleEMC, which installs the AppleEMC kext for iMac recognition….UNLESS you need to use an iMac SMBIOS.plist because of your CPU and find that having AppleEMC kext installed 'helps' the App Store recognize your OSx86 / Hacintosh PC).

Click Continue again……THEN click Change Install Location and select the target HDD OS X Lion volume icon in the Select a Destination window and click Continue……then click Install…..after a hopefully successful install, click Close…..

[20] Set up your video driver as you have done for running OS X 10.6.8 Snow Leopard in 64bit mode but note that in the Chameleon 2.0 RC5 r1191 [VS] update, com.apple.Boot.plist is renamed to org.chameleon.Boot.plist in /Extra, now that Chameleon uses org.chameleon.Boot.plist instead of com.apple.Boot.plist......

[21] Go back to the open target HDD OS X Lion System Window……the Chameleon bootloader installer should have created the /Extra/ and /Extra/Extensions/ directories or folders……

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

[23] Copy across from your running 64bit mode Snow Leopard system, or from the Lion Support Files v1.1 folder, 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 you have run the Chameleon 2.0 RC5 r1191 [VS] .dmg installer on your running 64bit mode Snow Leopard system)

Also copy across (if you wish) your Chameleon v2.0 RC5 r1191 Themes folder from your running 64bit mode Snow Leopard system…..

[24] Copy the following kexts in /Extra/Extensions/ on your running 64bit mode Snow Leopard system, or from the Lion Support Files v1.1 folder, into /Extra/Extensions/ in the open target HDD OS X Lion System Window……

AD1998b.FIX.kext
AppleNForceATA.imk64bit.kext
EvOreboot.kext
NullCPUPowerManagement.kext

You may also have AppleHDA.10.6.2.kext, FakeSMC.kext and nForceLAN.0.64.5.kext in /Extra/Extensions/.……

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 [8] below:

[25] 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, then these need to copied from there, or from the Lion Support Files v1.1 folder, into /System/Library/Extensions/ in the open target HDD OS X Lion System Window……

[26] Having added AppleHDA.10.6.2.kext, FakeSMC.kext and nForceLAN.0.64.5.kext to /System/Library/Extensions/ on the open target HDD OS X 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….

IOKitPersonalities_i386.ioplist.gz
IOKitPersonalities_x86_64.ioplist.gz
kernelcache
KextPropertyValues_OSBundleHelper_i386.plist.gz
KextPropertyValues_OSBundleHelper_x86_64.plist.gz

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

[28] 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......

Then as a workaround 'drag and drop' the AppleRTC.kext (Snow Leopard AppleRTC.kext) from the Lion Support Files v1.0 folder into /System/Library/Extensions/ on the open target HDD OS X Lion System window......

Alternatively, you can patch your own OS X Lion AppleRTC.kext by running this perl script in Terminal, which has been posted by rayap, which forces an unconditional jump over the rtcWrites() in updateChecksum() to prevent CMOS Resets:

sudo perl -pi -e 's|\x75\x30\x44\x89\xf8|\xeb\x30\x44\x89\xf8|; s|\x75\x3d\x8b\x75\x08|\xeb\x3d\x8b\x75\x08|' /System/Library/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC

Now 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 /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….

IOKitPersonalities_i386.ioplist.gz
IOKitPersonalities_x86_64.ioplist.gz
kernelcache
KextPropertyValues_OSBundleHelper_i386.plist.gz
KextPropertyValues_OSBundleHelper_x86_64.plist.gz

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

N.B. Since a DSDT.aml file with a RTC fix was and a patched version 10.7 AppleRTC.kext (or version 10.6.8 AppleRTC.kext) were not placed in the / directory and in /System/Library/Extensions, respectively, of the MacOSXBaseSystemDVD, the PC will reboot with a "CMOS checksum error - defaults loaded" message, i.e. the BIOS defaults will be loaded at bootup because your custom BIOS setup has been erased from the CMOS memory......

You will have to either re-enter your custom BIOS settings or, hopefully, just reload your custom BIOS setup from your BIOS backup, e.g. on a USB flash drive......

[30] Use the OS X Lion Disk Utility to repair the HDD OS X Lion system permissions......

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


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

Part F. Installing a Bootable OS X Lion OS 10.7 OS on a MBR Partitioned Hard Drive Using the verdant_nForce_OSX_Lion_Installer_DVD_Booter

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

Procedure 1. (No pre-existing Lion OS installation)

This procedure assumes that you have already followed Part E. steps [1] to [13]:

[1] Use the running Snow Leopard Disk Utility to partition/format your target HDD volume for OS X 10.7 as GPT/HFS+ volume named OSX_10.7_GPT_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 -> Get Info. If the checkbox next to "Ignore ownership on this volume" is checked then click on 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.7 hard drive........

[2] Download the verdantChameleonLionBootDVD.iso image file and the required i386 boot files

[3] Go to the Applications folder and find Install Mac OS X Lion WITHOUT clicking on the icon NOR right-click on the icon and selecting Open

[4] 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......

[5] Right-click on the Install Mac OS X Lion installer icon and select Show Package Contents.

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

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

[7] Create a folder on your Desktop called Mac OS X Base System

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

[9] 'Select All' files in the open BaseSystem window and copy them into the Mac OS X Base System folder that you created on your Desktop

[10] Open the System folder in the Mac OS X Base 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 3.26 GB Packages folder will take about 10 or minutes to copy over……

[11] Now 'drag and drop' the mach_kernel file from the open Mac OS X Install ESD window into the into the Mac OS X Base System folder…….

[12] Copy via Terminal or via 'drag and drop' the OSx86 boot files by netkas [i.e. PC_EFI v10.6 boot files (boot0, boot1h and cdboot) and 10.7 boot file (boot)] into /Users/"User Name"/Desktop/Mac\ OS\ X\ Base\ System/usr/standalone/i386,

i.e. in non-Terminal "speak" go to Desktop >>>> Mac OS X Base System >>>> usr >>>> standalone >>>> i386

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

For those of you who are interested, only the cdboot file is used to boot the MacOSXBaseSystemDVD but I have put the PC_EFI v10.6 boot files (boot0, boot1h and cdboot) and 10.7 boot file (boot) file into the i386 folder because some users may experience the following bootup freeze-causing error when trying to boot from the OS X Lion system they have installed on their HDD volume (by USB installer, or my DVD installer, or HDD partition installer):

BootCacheControl: Unable to open /var/db/BootCache.playlist: 2 no such file or directory
Bug:launchctl.c:2408 (24687):30: cdefd =open (g_overrides_db_patch....

and it has been reported by some with this problem that using the netkas PC_EFI v10.6 boot0 and boot1h files and the 10.7 boot file has overcome this problem, while using even the newer versions of the Chameleon 2.0 RC5 bootloader has not.............

To install these files manually on your target OS X Lion HDD/volume, you can use Terminal commands......follow this guide..........

Assuming your installation is on /dev/disk0s2

Install v10.6 boot0 to the MBR:
sudo ./fdisk440 -f boot0 -u -y /dev/rdisk0

Install v10.6 boot1h to the partition's bootsector:
sudo dd if=boot1h of=/dev/rdisk0s2

Install v10.7 boot to the partition's root directory:
sudo cp boot /

Alternatively, you can just download and run a PC_EFI v10.6 installer package and then just unhide the hidden/system files and delete the boot file in the root directory / and copy the PC_EFI v10.7 boot file into the / directory......

Also, see the post by akimoa here.....google for the PC efi 10.7 boot file from netkas or use this one http://cl.ly/3x0p0B041H3g3c2O3p2b

If you still have no joy, then try this version of fakesmc.kext posted by rubahgeni that he extracted from ###### 3.8.0, as it sorted the launchctl.c error for him allowing him to boot the Lion installer......

  FakeSMC.kext.zip   30.01K   1 downloads

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

[13] Now go to /Users/"User Name"/Desktop/Mac\ OS\ X\ Base\ System/System/Library/CoreServices/,

i.e. in non-Terminal "speak" go to Desktop >>>> Mac 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……

Now in order for you to install OS X Lion 10.7 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 in the Mac OS X Base System folder......

There are two versions of OSInstall.mpkg and OSInstall that I have used:

Version 1 patcher: nawcom's GM MBR Patch

Create a folder named "nawcom MBR Patch" on your Desktop, and then download and unarchive Lion_OSInstall_GM.tar.bz2 file into it…….the unarchived System folder contains the modified OSInstall.mpkg package and the OSInstall Unix executable file, nested in Installation and Library, respectively….

Alternatively, here is a zipped archive for your convenience: Posted Image

MBR_Patch_for_OS_X_Lion_GM___by_nawcom.zip   701.95K   50 downloads

Version 2 patcher: MBR Patch 10.7.0 11A511 - by xpertvision

The binpatched OSInstall "framework" and "OSInstall.mpkg" in MBR Patch 10.7.0 11A511: Posted Image

MBR_Patch_10.7.0_11A511___by_Xpertvision.zip   707.73K   56 downloads

are modified versions of the original patches by nawcom, to enable the installation of OS X Lion 10.7.0 (11A511 release) onto a target HDD volume partitioned/formatted as MBR/HFS+, which are patched to:

[1] Overcome the default 2GB RAM limit for installation, allowing installation even on PCs having only 1GB RAM installed......but note these comments by smartie77:

Quote

running Lion with only 1 or 1.5 GB would be a pain leaving it in its default 64bit mode with all features on but the beast can be tamed a lot :

If for all you should only run it in 32bit mode this makes the biggest change in memory usage, then the next biggest turn off spotlight to a large degree, mainly the full text indexing of pdf,mail and websites; exclude all folders that are not your home folder and run most apps in 32bit mode only, not only the apps in /Applications but also the system apps in /System/Library/CoreServices - right click them "get info" and checkmark "run in 32bit mode" wherever it is available. Try slimming down the kexts - if you have a ATI for example throw out all IntelGMA,Nvidia etc kexts. If you have no thunderbolt and Firewire - out with them . No ATTO and Promise cards = rid off them..

Turn off the auto-reopening of all open windows and apps ( Lion constantly writes apps changing states, open documents and version changes to your hidden Home Library ).

There is more to tweak, time will tell.. Lion has a loads of background services running that were not in SL. And Apple seems to collect a lot of user and performance metric data .. Have a look in Systems LaunchAgents/Launchdaemons plists, there is way too much, but as of yet I cannot say what is safe to delete there.



[2] Custom Install Options added:

Language packs (select the language packs you want to install)

Server Install (install server options or not) - provided that you have the the OS X Lion 10.7.0 Server Installer as a .dmg /.iso image file and hence its Mac OS X Base System volume on your OS X Lion USB Flash Drive Installer.....


The procedure for installing the modified OSInstall.mpkg package and OSInstall Unix executable file in the Mac OS X Base System folder in place of the original OS X Lion Installer versions is the same, whichever version patcher you choose to use, and is as follows:

1. Unhide the hidden and systems files in the Mac OS X Base System folder, using Terminal commands or Tinker Tool (see Part E. above)

2. Go to Terminal and then:

[1] Either type:

cd /Users/"User Name"/Desktop/Mac\ OS\ X\ Base\ System/System/Installation/Packages

or type

cd

and press the 'Space Bar', and then having navigated to System >>>> Installation >>>> 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/Mac\ 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 >>>> Library >>>> PrivateFrameworks >>>> Install.framework >>>> Frameworks >>>> OSInstall.framework >>>> Versions >>>> A, '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 /Users/"User Name"/Desktop/Mac\ OS\ X\ Base\ System/System/Installation/Packages																
sudo mv OSInstall.mpkg OSInstall.mpkg.MBR
sudo mv OSInstall.mpkg.GPT OSInstall.mpkg

followed by

cd /Users/"User Name"/Desktop/Mac\ 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 /Users/"User Name"/Desktop/Mac\ OS\ X\ Base\ System/System/Installation/Packages......(or use cp command via Terminal):

sudo cp -p -R /Users/"User Name"/Desktop/nawcom\ MBR\ Patch/System/Installation/Packages/OSInstall.mpkg /Users/"User Name"/Desktop/Mac\ OS\ X\ Base\ System/System/Installation/Packages

4. Then 'drag and drop' OSInstall into /Users/"User Name"/Desktop/Mac\ OS\ X\ Base\ System/System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A......(or use cp command via Terminal):

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

5. Close all open folders within the Mac OS X Base System folder and in the Terminal type:

sudo chown -R 0:0 /Users/"User Name"/Desktop/Mac\ OS\ X\ Base\ System

6. Then in Terminal type:

sudo hdiutil makehybrid -o MacOSXBaseSystemDVD.iso /Users/"User Name"/Desktop/Mac\ OS\ X\ Base\ System  -iso -hfs -joliet -eltorito-boot /Users/"User Name"/Desktop/Mac\ OS\ X\ Base\ System/usr/standalone/i386/cdboot -no-emul-boot -hfs-volume-name "MacOSXBaseSystemDVD" -joliet-volume-name "MacOSXBaseSystemDVD"

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 MacOSXBaseSystemDVD.iso in the /Users/"User Name"/ directory

7. Burn this .iso image file to a DVD at x4 or slower

8. Burn the verdantChameleonLionBootDVD.iso image file to a CD……..

9. Now follow the following procedure to install OS X Lion 10.7 onto your target HDD volume partitioned/formatted as MBR/HFS+ :

[1] Have the MacOSXBaseSystemDVD ready to hand and then insert the verdantChameleonLionBootCD into your DVDRW and boot from it………..follow the boot screen instructions…..I recommend you choose -v as a boot flag before booting from the MacOSXBaseSystemDVD, so that you can see what is happening onscreen…….

BE PREPARED - booting from the DVD is very slow because [1] all kexts are loaded directly from /System/Library/Extensions/ and [2] the OS X Lion BaseSystem.dmg files are no longer optimised for use with optical disks………….clear indication that Apple now view optical drives/disks as obsolete (just as they did with the floppy disk drive/disks)……..

HOWEVER I have prepared this installation method {a} for those who do not have ready access to an 8GB minimum size USB flash drive and {b} for those who like the idea of having a 'backup' installation method should their USB flash drive ever fail…….

[2] Re-boot back into OS X Snow Leopard and run the Chameleon 2.0 RC5 r1191 [VS] .dmg installer (in the Lion_Support_Files_v1.1 folder) and double-click on the Install Chameleon icon in the Chameleon 2 RC5 VS window…….then click Continue…..accept the default-selected Chameleon and select Theme (you do not need to select AppleEMC, which installs the AppleEMC kext for iMac recognition….UNLESS you need to use an iMac SMBIOS.plist because of your CPU and find that having AppleEMC kext installed 'helps' the App Store recognize your OSx86 / Hacintosh PC).

Click Continue again……THEN click Change Install Location and select the target HDD OS X Lion volume icon in the Select a Destination window and click Continue……then click Install…..after a hopefully successful install, click Close…..

[3] Set up your video driver as you have done for running OS X 10.6.8 Snow Leopard in 64bit mode but note that in the Chameleon 2.0 RC5 r1191 [VS] update, com.apple.Boot.plist is renamed to org.chameleon.Boot.plist in /Extra, now that Chameleon uses org.chameleon.Boot.plist instead of com.apple.Boot.plist......

[4] Go back to the open target HDD OS X Lion System Window……the Chameleon bootloader installer should have created the /Extra/ and /Extra/Extensions/ directories or folders……

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

[6] Copy across from your running 64bit mode Snow Leopard system, or from the Lion Support Files v1.1 folder, 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 you have run the Chameleon 2.0 RC5 r1191 [VS] .dmg installer on your running 64bit mode Snow Leopard system)

Also copy across (if you wish) your Chameleon v2.0 RC5 r1191 Themes folder from your running 64bit mode Snow Leopard system…..

[7] Copy the following kexts in /Extra/Extensions/ on your running 64bit mode Snow Leopard system, or from the Lion Support Files v1.1 folder, into /Extra/Extensions/ in the open target HDD OS X Lion System Window……

AD1998b.FIX.kext
AppleNForceATA.imk64bit.kext
EvOreboot.kext
NullCPUPowerManagement.kext

You may also have AppleHDA.10.6.2.kext, FakeSMC.kext and nForceLAN.0.64.5.kext in /Extra/Extensions/.……

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 [8] below:

[8] 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, then these need to copied from there, or from the Lion Support Files v1.1 folder, into /System/Library/Extensions/ in the open target HDD OS X Lion System Window……

[9] Having added AppleHDA.10.6.2.kext, FakeSMC.kext and nForceLAN.0.64.5.kext to /System/Library/Extensions/ on the open target HDD OS X 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….

IOKitPersonalities_i386.ioplist.gz
IOKitPersonalities_x86_64.ioplist.gz
kernelcache
KextPropertyValues_OSBundleHelper_i386.plist.gz
KextPropertyValues_OSBundleHelper_x86_64.plist.gz

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

[11] 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......

Then as a workaround 'drag and drop' the AppleRTC.kext (Snow Leopard AppleRTC.kext) from the Lion Support Files v1.0 folder into /System/Library/Extensions/ on the open target HDD OS X Lion System window......

Alternatively, you can patch your own OS X Lion AppleRTC.kext by running this perl script in Terminal, which has been posted by rayap, which forces an unconditional jump over the rtcWrites() in updateChecksum() to prevent CMOS Resets:

sudo perl -pi -e 's|\x75\x30\x44\x89\xf8|\xeb\x30\x44\x89\xf8|; s|\x75\x3d\x8b\x75\x08|\xeb\x3d\x8b\x75\x08|' /System/Library/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC

Now 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 /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….

IOKitPersonalities_i386.ioplist.gz
IOKitPersonalities_x86_64.ioplist.gz
kernelcache
KextPropertyValues_OSBundleHelper_i386.plist.gz
KextPropertyValues_OSBundleHelper_x86_64.plist.gz

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

[13] Use the OS X Lion Disk Utility to repair the HDD OS X Lion system permissions......

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


Procedure 2. (Pre-existing OS X Lion system installation)

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

2. Install the Chameleon RC5 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 OS X Lion OS on the MBR/HFS+ partition/volume.....


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

Attached Files


#2
verdant
Posted 29 July 2011 - 09:42 PM

verdant

    InsanelyMac V.I.P.

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

Graphic Card Operation in OS X Lion

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

This section deals with getting your graphics / video card(s) working in OS X Lion.......I have an nVidia 9800 GT graphics card and so can only be of limited help if you have an ATI graphics card.........likewise if you want to run more than 1 graphics card in your OSx86 / Hackintosh.........

This guide will hopefully include in time, more reports of successful attempts to get different graphics cards (both nVidia and ATI) working on different nForce chipset + Intel CPU MOBOs.........

Thus, I am happy to include clear to follow guides dealing with setting up of specific graphics card chipsets/models on nForce chipset + Intel CPU MOBOs.......

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

Getting an nVidia graphics card working in Lion

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

The 3 easiest methods for getting an nVidia graphics card working in Lion are as follows (easiest first).

1. Chameleon 2.0 RC5 GraphicsEnabler option via org.chameleon.Boot.plist:

<key>GraphicsEnabler</key>
<string>Yes</string>

2. Hexadecimal graphics string option via org.chameleon.Boot.plist:

<key>device-properties</key>
<string>"for example, 6c0200000100000001000000600200000d00000002010c.." </string>

where the graphics string is generated by EFIStudio v1.1 or OSx86Tools.....

3. NVEnabler injector kext, Injector kext, which enables TV-OUT and injects 2nd display operation very well......

The NVEnabler.kext (32bit/64bit) is not just another injector kext because it does on-the-fly ROM patching to give a more stable output configuration.......but depending on whether you are working with OS X Snow Leopard, or with OS X Lion, you may still need to insert your graphics card(s) Device ID into the Info.plist files of the NVDAResman.kext or the NVDAResmanG7xxx.kext and the NVDANV40HalG7xxx.kext, or NVDANV50hal.kext or NVDAGF100Hal.kext......see the section on Inserting Graphics Card Hardware Matching Device ID into nVidia Graphics Kexts below.....

Finally, if you are familiar with DSDT modding, you can choose to modify your DSDT.aml file with information on your NVCap values obtained via IORegistry Editor, which is the newest method but also the cleanest, most "vanilla" method because it is DSDT-based, rather than involving com.apple.Boot.plist changes, or using a non-vanilla kext.......

NOTE: The methods above are mutually exclusive......use only one.

The situation is a bit more complicated with the nVidia GeForce GTX and GTS series graphics cards ...... it may be necessary to insert the graphics card(s) Device ID directly into the appropriate vanilla kexts, as well as using a compatible enabler.....


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

Getting an ATI graphics card working in Lion

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

Two methods for getting an ATI graphics card working in Snow Leopard are:

1. Hexadecimal graphics string option via org.chameleon.Boot.plist:

<key>device-properties</key>
<string>"for example, 6c0200000100000001000000600200000d00000002010c.." </string>

where the graphics string is generated by EFIStudio v1.1 or OSx86Tools.....BUT there are far fewer built-in options than for nVidia graphics cards.......

2. EVOEnabler.kext (32/64bit) injector kext

NOTE: The methods above are mutually exclusive......use only one.

The situation with ATI graphics cards is invariably more complicated than for nVidia graphics cards, e.g. the ATI Radeon HD48xx series.......Google the regularly updated information from netkas.org.......it may be necessary to insert the graphics card(s) Device ID directly into the appropriate vanilla kexts, as well as using an enabler.....


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

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

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

If CI and QE are not fully enabled for your graphics card(s), then you will probably experience so-called mouse pointer "tearing", display-screen artifacts such as horizontal dashes, poor display refresh-rates, fixed screen-resolution etc.

In Leopard, System Profiler > Graphics/Displays would directly indicate this because Core Image would be shown as "Hardware Accelerated" and Quartz Extreme as "Supported" BUT this is no longer the case in Snow Leopard and Lion.......

However, there are 2 key ways to confirm that the Core Image functioning is hardware accelerated and that Quartz Extreme functioning is supported in Lion:

1. The top-menu bar is transluscent i.e. the underlying Desktop image is visible through the menu bar

2. First, go to system Preferences >>>> Mission Control and uncheck the 'Show Dashboard as a space' checkbox.

Then, when you click on the Dashboard icon in Dock or run the Dashboard app and add a widget, either via the LHS "+" button and clicking on a widget icon in the bottom widgets bar, or by 'dragging and dropping' a widget, you should see a "real-time" water-ripple effect as the new widget is "dropped" into the Dashboard.......

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

Generating an EFI Graphics String for Lion

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

If you can boot into 64bit mode you can try using in place of the EFI graphics string, either NVinject (64bit) or NatitSilent.kext (64bit) or, if not, try EVOenabler.kext (32/64bit)........but check in the Info.plist for

"VRAM,totalsize"

add if not present, and use appropriate data value against VRAM,totalsize for your graphics card VRAM

Data Value -------- VRAM (MB) ---------- String Value (Hexadecimal)

<00000002>-------------32------------------<0x02000000>
<00000004>-------------64------------------<0x04000000>
<00000008>------------128------------------<0x08000000>
<00000010>------------256------------------<0x10000000>
<00000014>------------320------------------<0x14000000>
<00000020>------------512------------------<0x20000000>
<00000028>------------640------------------<0x28000000>
<00000030>------------768------------------<0x30000000>
<00000038>------------896------------------<0x38000000>
<00000040>-----------1024 (1.0GB)--------<0x40000000>
<00000050>-----------1280 (1.28 GB)------<0x50000000>
<00000060>-----------1500 (1.5 GB)-------<0x60000000>
<00000080>-----------2000 (2.0 GB)-------<0x80000000>

using, for example, Property List Editor (available in XCode > Developer > Applications > Utilities) .......


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

Alternatively, if you want to continue using an "EFI graphics string", then you can:

1. Create a folder on your Leopard Desktop called GFXStringMod

I say this because according to aqua-mac:


QUOTE
PLEASE NOTE - SNOW LEOPARD When making your output file - that must be done booted from Leopard only. Snow Leopard gives the wrong info in the output file and you WILL NOT get QE/CI working! GFX strings will work fine on snow leopard once they are made, but the part where you translate the input file into the output file only works if made with Leopard. If you make that in snow it will give an incorrect one and you will not get Quartz Extreme or Core Image which makes OSX pretty useless. So you will need a Leo install on a laptop or someone with a Leo install at present. To reset permissions after you re-install the file, just run Disk Utility - Repair Permissions.


N.B. I have not checked if what aqua-mac says above is applicable to Lion as it is for Snow Leopard......if you do check, then let me know.......

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

2. Save your hexadecimal EFI graphics string as a GFXString.hex file to GFXStringMod (using either EFIStudio v1.1 or OSx86Tools)....

Yes....I know you can save the string as a .hex, or as a .xml (i.e. .plist) file using either EFIStudio v1.1 or OSX86Tools.....but I am using gfxutil v0.71b for a consistent approach.......AND BTW EFIStudio v1.1 itself uses gfxutil v0.71b...... wink.gif

3. Use gfxutil v0.71b to convert GFXString.hex to GFXString.plist as follows:

Copy downloaded gfxutil to GFXStringMod

In Terminal type (leave Terminal window open, as you will use it again)

CODE
cd /Users/"Username"/Desktop/GFXStringMod
./gfxutil -s -n -i hex -o xml ./GFXString.hex ./GFXString.plist


4. Use 'Property List Editor' (available in XCode > Developer > Applications > Utilities) to modify your settings by changing the number to the appropriate value for your VRAM:

VRAM,totalsize Data 00000080

5. Use gfxutil to convert from GFXString.plist to GFXString.hex as follows:

In Terminal type
CODE
./gfxutil -i xml -o hex ./GFXString.plist ./GFXString.hex


6. Copy the string in the new VRAM,totalsize-modified GFXString.hex file to /Library/Preferences/SystemConfiguration/com.apple.Boot.plist under/against <key>device-properties</key>

System Requirements according to Apple

    * 1GB of memory
    * 5GB of available disk space
    * DVD drive for installation......(or bootable USB flash drive and USB device booting BIOS)


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

Inserting Graphics Card Hardware Matching Device ID into nVidia Graphics Kexts

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


A. List of current NVIDIA graphics cards device IDs (as of May 2011) :

CODE
0040 = "NVIDIA GeForce 6800 Ultra"
0041 = "NVIDIA GeForce 6800"
0042 = "NVIDIA GeForce 6800 LE"
0043 = "NVIDIA GeForce 6800 XE"
0044 = "NVIDIA GeForce 6800 XT"
0045 = "NVIDIA GeForce 6800 GT"
0046 = "NVIDIA GeForce 6800 GT"
0047 = "NVIDIA GeForce 6800 GS"
0048 = "NVIDIA GeForce 6800 XT"
004E = "NVIDIA Quadro FX 4000"
0090 = "NVIDIA GeForce 7800 GTX"
0091 = "NVIDIA GeForce 7800 GTX"
0092 = "NVIDIA GeForce 7800 GT"
0093 = "NVIDIA GeForce 7800 GS"
0095 = "NVIDIA GeForce 7800 SLI"
009D = "NVIDIA Quadro FX 4500"
00C0 = "NVIDIA GeForce 6800 GS"
00C1 = "NVIDIA GeForce 6800"
00C2 = "NVIDIA GeForce 6800 LE"
00C3 = "NVIDIA GeForce 6800 XT"
00CD = "NVIDIA Quadro FX 3450/4000 SDI"
00CE = "NVIDIA Quadro FX 1400"
00F1 = "NVIDIA GeForce 6600 GT"
00F2 = "NVIDIA GeForce 6600"
00F3 = "NVIDIA GeForce 6200"
00F4 = "NVIDIA GeForce 6600 LE"
00F5 = "NVIDIA GeForce 7800 GS"
00F6 = "NVIDIA GeForce 6800 GS/XT"
00F8 = "NVIDIA Quadro FX 3400/4400"
00F9 = "NVIDIA GeForce 6800 Series GPU"
0140 = "NVIDIA GeForce 6600 GT"
0141 = "NVIDIA GeForce 6600"
0142 = "NVIDIA GeForce 6600 LE"
0143 = "NVIDIA GeForce 6600 VE"
0145 = "NVIDIA GeForce 6610 XL"
0147 = "NVIDIA GeForce 6700 XL"
014A = "NVIDIA Quadro NVS 440"
014C = "NVIDIA Quadro FX 540M"
014D = "NVIDIA Quadro FX 550"
014E = "NVIDIA Quadro FX 540"
014F = "NVIDIA GeForce 6200"
0160 = "NVIDIA GeForce 6500"
0161 = "NVIDIA GeForce 6200 TurboCache™"
0162 = "NVIDIA GeForce 6200SE TurboCache™"
0163 = "NVIDIA GeForce 6200 LE"
0165 = "NVIDIA Quadro NVS 285"
0169 = "NVIDIA GeForce 6250"
016A = "NVIDIA GeForce 7100 GS"
0191 = "NVIDIA GeForce 8800 GTX"
0193 = "NVIDIA GeForce 8800 GTS"
0194 = "NVIDIA GeForce 8800 Ultra"
0197 = "NVIDIA Tesla C870"
019D = "NVIDIA Quadro FX 5600"
019E = "NVIDIA Quadro FX 4600"
01D0 = "NVIDIA GeForce 7350 LE"
01D1 = "NVIDIA GeForce 7300 LE"
01D3 = "NVIDIA GeForce 7300 SE/7200 GS"
01DB = "NVIDIA Quadro NVS 120M"
01DD = "NVIDIA GeForce 7500 LE"
01DE = "NVIDIA Quadro FX 350"
01DF = "NVIDIA GeForce 7300 GS"
0211 = "NVIDIA GeForce 6800"
0212 = "NVIDIA GeForce 6800 LE"
0215 = "NVIDIA GeForce 6800 GT"
0218 = "NVIDIA GeForce 6800 XT"
0221 = "NVIDIA GeForce 6200"
0222 = "NVIDIA GeForce 6200 A-LE"
0240 = "NVIDIA GeForce 6150"
0241 = "NVIDIA GeForce 6150 LE"
0242 = "NVIDIA GeForce 6100"
0245 = "NVIDIA Quadro NVS 210S / NVIDIA GeForce 6150LE"
0290 = "NVIDIA GeForce 7900 GTX"
0291 = "NVIDIA GeForce 7900 GT/GTO"
0292 = "NVIDIA GeForce 7900 GS"
0293 = "NVIDIA GeForce 7950 GX2"
0294 = "NVIDIA GeForce 7950 GX2"
0295 = "NVIDIA GeForce 7950 GT"
029C = "NVIDIA Quadro FX 5500"
029D = "NVIDIA Quadro FX 3500"
029E = "NVIDIA Quadro FX 1500"
029F = "NVIDIA Quadro FX 4500 X2"
02E0 = "NVIDIA GeForce 7600 GT"
02E1 = "NVIDIA GeForce 7600 GS"
02E2 = "NVIDIA GeForce 7300 GT"
02E3 = "NVIDIA GeForce 7900 GS"
02E4 = "NVIDIA GeForce 7950 GT"
0390 = "NVIDIA GeForce 7650 GS"
0391 = "NVIDIA GeForce 7600 GT"
0392 = "NVIDIA GeForce 7600 GS"
0393 = "NVIDIA GeForce 7300 GT"
0394 = "NVIDIA GeForce 7600 LE"
0395 = "NVIDIA GeForce 7300 GT"
039C = "NVIDIA Quadro FX 560M"
039E = "NVIDIA Quadro FX 560"
03D0 = "NVIDIA GeForce 6150SE nForce 430"
03D1 = "NVIDIA GeForce 6100 nForce 405"
03D2 = "NVIDIA GeForce 6100 nForce 400"
03D5 = "NVIDIA GeForce 6100 nForce 420"
03D6 = "NVIDIA GeForce 7025 / NVIDIA nForce 630a"
0400 = "NVIDIA GeForce 8600 GTS"
0401 = "NVIDIA GeForce 8600 GT"
0402 = "NVIDIA GeForce 8600 GT"
0403 = "NVIDIA GeForce 8600 GS"
0404 = "NVIDIA GeForce 8400 GS"
0405 = "NVIDIA GeForce 9500M GS"
0406 = "NVIDIA GeForce 8300 GS"
0407 = "NVIDIA GeForce 8600M GT"
0408 = "NVIDIA GeForce 9650M GS"
0409 = "NVIDIA GeForce 8700M GT"
040A = "NVIDIA Quadro FX 370"
040B = "NVIDIA Quadro NVS 320M"
040C = "NVIDIA Quadro FX 570M"
040D = "NVIDIA Quadro FX 1600M"
040E = "NVIDIA Quadro FX 570"
040F = "NVIDIA Quadro FX 1700"
0410 = "NVIDIA GeForce GT 330"
0420 = "NVIDIA GeForce 8400 SE"
0421 = "NVIDIA GeForce 8500 GT"
0422 = "NVIDIA GeForce 8400 GS"
0423 = "NVIDIA GeForce 8300 GS"
0424 = "NVIDIA GeForce 8400 GS"
0425 = "NVIDIA GeForce 8600M GS"
0426 = "NVIDIA GeForce 8400M GT"
0427 = "NVIDIA GeForce 8400M GS"
0428 = "NVIDIA GeForce 8400M G"
0429 = "NVIDIA Quadro NVS 140M"
042A = "NVIDIA Quadro NVS 130M"
042B = "NVIDIA Quadro NVS 135M"
042C = "NVIDIA GeForce 9400 GT"
042D = "NVIDIA Quadro FX 360M"
042E = "NVIDIA GeForce 9300M G"
042F = "NVIDIA Quadro NVS 290"
053A = "NVIDIA GeForce 7050 PV / NVIDIA nForce 630a"
053B = "NVIDIA GeForce 7050 PV / NVIDIA nForce 630a"
053E = "NVIDIA GeForce 7025 / NVIDIA nForce 630a"
05E0 = "NVIDIA GeForce GTX 295"
05E1 = "NVIDIA GeForce GTX 280"
05E2 = "NVIDIA GeForce GTX 260"
05E3 = "NVIDIA GeForce GTX 285"
05E6 = "NVIDIA GeForce GTX 275"
05E7 = "NVIDIA Tesla C1060"
05EA = "NVIDIA GeForce GTX 260"
05EB = "NVIDIA GeForce GTX 295"
05F9 = "NVIDIA Quadro CX"
05FD = "NVIDIA Quadro FX 5800"
05FE = "NVIDIA Quadro FX 4800"
05FF = "NVIDIA Quadro FX 3800"
0600 = "NVIDIA GeForce 8800 GTS 512"
0601 = "NVIDIA GeForce 9800 GT"
0602 = "NVIDIA GeForce 8800 GT"
0603 = "NVIDIA GeForce GT 230"
0604 = "NVIDIA GeForce 9800 GX2"
0605 = "NVIDIA GeForce 9800 GT"
0606 = "NVIDIA GeForce 8800 GS"
0607 = "NVIDIA GeForce GTS 240"
0608 = "NVIDIA GeForce 9800M GTX"
0609 = "NVIDIA GeForce 8800M GTS"
060A = "NVIDIA GeForce GTX 280M"
060B = "NVIDIA GeForce 9800M GT"
060C = "NVIDIA GeForce 8800M GTX"
060F = "NVIDIA GeForce GTX 285M"
0610 = "NVIDIA GeForce 9600 GSO"
0611 = "NVIDIA GeForce 8800 GT"
0612 = "NVIDIA GeForce 9800 GTX/9800 GTX+"
0613 = "NVIDIA GeForce 9800 GTX+"
0614 = "NVIDIA GeForce 9800 GT"
0615 = "NVIDIA GeForce GTS 250"
0617 = "NVIDIA GeForce 9800M GTX "
0618 = "NVIDIA GeForce GTX 260M"
0619 = "NVIDIA Quadro FX 4700 X2"
061A = "NVIDIA Quadro FX 3700"
061B = "NVIDIA Quadro VX 200"
061C = "NVIDIA Quadro FX 3600M"
061D = "NVIDIA Quadro FX 2800M"
061E = "NVIDIA Quadro FX 3700M"
061F = "NVIDIA Quadro FX 3800M"
0621 = "NVIDIA GeForce GT 230"
0622 = "NVIDIA GeForce 9600 GT"
0623 = "NVIDIA GeForce 9600 GS"
0625 = "NVIDIA GeForce 9600 GSO 512"
0626 = "NVIDIA GeForce GT 130"
0627 = "NVIDIA GeForce GT 140"
0628 = "NVIDIA GeForce 9800M GTS"
062A = "NVIDIA GeForce 9700M GTS"
062B = "NVIDIA GeForce 9800M GS"
062C = "NVIDIA GeForce 9800M GTS    "
062D = "NVIDIA GeForce 9600 GT"
062E = "NVIDIA GeForce 9600 GT"
0631 = "NVIDIA GeForce GTS 160M"
0635 = "NVIDIA GeForce 9600 GSO"
0637 = "NVIDIA GeForce 9600 GT"
0638 = "NVIDIA Quadro FX 1800"
063A = "NVIDIA Quadro FX 2700M"
0640 = "NVIDIA GeForce 9500 GT"
0641 = "NVIDIA GeForce 9400 GT"
0643 = "NVIDIA GeForce 9500 GT"
0644 = "NVIDIA GeForce 9500 GS"
0645 = "NVIDIA GeForce 9500 GS"
0646 = "NVIDIA GeForce GT 120"
0647 = "NVIDIA GeForce 9600M GT"
0648 = "NVIDIA GeForce 9600M GS"
0649 = "NVIDIA GeForce 9600M GT"
064A = "NVIDIA GeForce 9700M GT"
064C = "NVIDIA GeForce 9650M GT"
0651 = "NVIDIA GeForce G 110M"
0652 = "NVIDIA GeForce GT 130M"
0653 = "NVIDIA GeForce GT 120M"
0654 = "NVIDIA GeForce GT 220M"
0655 = "NVIDIA GeForce GT 120"
0656 = "NVIDIA GeForce GT 120 "
0658 = "NVIDIA Quadro FX 380"
0659 = "NVIDIA Quadro FX 580"
065A = "NVIDIA Quadro FX 1700M"
065B = "NVIDIA GeForce 9400 GT"
065C = "NVIDIA Quadro FX 770M"
065F = "NVIDIA GeForce G210"
06C0 = "NVIDIA GeForce GTX 480"
06C4 = "NVIDIA GeForce GTX 465"
06CA = "NVIDIA GeForce GTX 480M"
06CD = "NVIDIA GeForce GTX 470"
06D1 = "NVIDIA Tesla C2050 / C2070"
06D2 = "NVIDIA Tesla M2070"
06D8 = "NVIDIA Quadro 6000"
06D9 = "NVIDIA Quadro 5000"
06DA = "NVIDIA Quadro 5000M"
06DC = "NVIDIA Quadro 6000"
06DD = "NVIDIA Quadro 4000"
06DE = "NVIDIA Tesla T20 Processor"
06DF = "NVIDIA Tesla M2070-Q"
06E0 = "NVIDIA GeForce 9300 GE"
06E1 = "NVIDIA GeForce 9300 GS"
06E2 = "NVIDIA GeForce 8400"
06E3 = "NVIDIA GeForce 8400 SE"
06E4 = "NVIDIA GeForce 8400 GS"
06E6 = "NVIDIA GeForce G100"
06E7 = "NVIDIA GeForce 9300 SE"
06E8 = "NVIDIA GeForce 9200M GS"
06E9 = "NVIDIA GeForce 9300M GS"
06EA = "NVIDIA Quadro NVS 150M"
06EB = "NVIDIA Quadro NVS 160M"
06EC = "NVIDIA GeForce G 105M"
06EF = "NVIDIA GeForce G 103M"
06F1 = "NVIDIA GeForce G105M"
06F8 = "NVIDIA Quadro NVS 420"
06F9 = "NVIDIA Quadro FX 370 LP"
06FA = "NVIDIA Quadro NVS 450"
06FB = "NVIDIA Quadro FX 370M"
06FD = "NVIDIA Quadro NVS 295"
06FF = "NVIDIA HICx16 + Graphics"
07E0 = "NVIDIA GeForce 7150 / NVIDIA nForce 630i"
07E1 = "NVIDIA GeForce 7100 / NVIDIA nForce 630i"
07E2 = "NVIDIA GeForce 7050 / NVIDIA nForce 630i"
07E3 = "NVIDIA GeForce 7050 / NVIDIA nForce 610i"
07E5 = "NVIDIA GeForce 7050 / NVIDIA nForce 620i"
0840 = "NVIDIA GeForce 8200M"
0844 = "NVIDIA GeForce 9100M G"
0845 = "NVIDIA GeForce 8200M G"
0846 = "NVIDIA GeForce 9200"
0847 = "NVIDIA GeForce 9100"
0848 = "NVIDIA GeForce 8300"
0849 = "NVIDIA GeForce 8200"
084A = "NVIDIA nForce 730a"
084B = "NVIDIA GeForce 9200"
084C = "NVIDIA nForce 980a/780a SLI"
084D = "NVIDIA nForce 750a SLI"
084F = "NVIDIA GeForce 8100 / nForce 720a"
0860 = "NVIDIA GeForce 9400"
0861 = "NVIDIA GeForce 9400"
0862 = "NVIDIA GeForce 9400M G"
0863 = "NVIDIA GeForce 9400M"
0864 = "NVIDIA GeForce 9300"
0865 = "NVIDIA ION"
0866 = "NVIDIA GeForce 9400M G  "
0867 = "NVIDIA GeForce 9400 "
0868 = "NVIDIA nForce 760i SLI"
0869 = "NVIDIA GeForce 9400  "
086A = "NVIDIA GeForce 9400"
086C = "NVIDIA GeForce 9300 / nForce 730i"
086D = "NVIDIA GeForce 9200"
086E = "NVIDIA GeForce 9100M G"
086F = "NVIDIA GeForce 8200M G"
0870 = "NVIDIA GeForce 9400M        "
0871 = "NVIDIA GeForce 9200"
0872 = "NVIDIA GeForce G102M"
0873 = "NVIDIA GeForce G102M   "
0874 = "NVIDIA ION"
0876 = "NVIDIA ION"
087A = "NVIDIA GeForce 9400"
087D = "NVIDIA ION"
087E = "NVIDIA ION LE"
087F = "NVIDIA ION LE"
08A0 = "NVIDIA GeForce 320M"
08A4 = "NVIDIA GeForce 320M    "
0A20 = "NVIDIA GeForce GT 220"
0A22 = "NVIDIA GeForce 315"
0A23 = "NVIDIA GeForce 210"
0A26 = "NVIDIA GeForce 405"
0A27 = "NVIDIA GeForce 405"
0A28 = "NVIDIA GeForce GT 230M"
0A29 = "NVIDIA GeForce GT 330M"
0A2A = "NVIDIA GeForce GT 230M"
0A2B = "NVIDIA GeForce GT 330M "
0A2C = "NVIDIA NVS 5100M"
0A2D = "NVIDIA GeForce GT 320M  "
0A34 = "NVIDIA GeForce GT 240M"
0A35 = "NVIDIA GeForce GT 325M"
0A38 = "NVIDIA Quadro 400"
0A3C = "NVIDIA Quadro FX 880M"
0A60 = "NVIDIA GeForce G210"
0A62 = "NVIDIA GeForce 205"
0A63 = "NVIDIA GeForce 310"
0A64 = "NVIDIA ION"
0A65 = "NVIDIA GeForce 210"
0A66 = "NVIDIA GeForce 310"
0A67 = "NVIDIA GeForce 315"
0A68 = "NVIDIA GeForce G105M "
0A69 = "NVIDIA GeForce G105M"
0A6A = "NVIDIA NVS 2100M"
0A6C = "NVIDIA NVS 3100M"
0A6E = "NVIDIA GeForce 305M"
0A6F = "NVIDIA ION "
0A70 = "NVIDIA GeForce 310M"
0A71 = "NVIDIA GeForce 305M   "
0A72 = "NVIDIA GeForce 310M"
0A73 = "NVIDIA GeForce 305M "
0A74 = "NVIDIA GeForce G210M"
0A75 = "NVIDIA GeForce 310M "
0A76 = "NVIDIA ION   "
0A78 = "NVIDIA Quadro FX 380 LP"
0A7A = "NVIDIA GeForce 315M"
0A7C = "NVIDIA Quadro FX 380M"
0CA0 = "NVIDIA GeForce GT 330"
0CA2 = "NVIDIA GeForce GT 320"
0CA3 = "NVIDIA GeForce GT 240"
0CA4 = "NVIDIA GeForce GT 340"
0CA5 = "NVIDIA GeForce GT 220"
0CA7 = "NVIDIA GeForce GT 330"
0CA9 = "NVIDIA GeForce GTS 250M"
0CAC = "NVIDIA GeForce GT 220"
0CAF = "NVIDIA GeForce GT 335M"
0CB0 = "NVIDIA GeForce GTS 350M"
0CB1 = "NVIDIA GeForce GTS 360M"
0CBC = "NVIDIA Quadro FX 1800M"
0DC0 = "NVIDIA GeForce GT 440"
0DC4 = "NVIDIA GeForce GTS 450"
0DC5 = "NVIDIA GeForce GTS 450"
0DC6 = "NVIDIA GeForce GTS 450"
0DCD = "NVIDIA GeForce GT 555M"
0DCE = "NVIDIA GeForce GT 555M"
0DD1 = "NVIDIA GeForce GTX 460M"
0DD2 = "NVIDIA GeForce GT 445M"
0DD3 = "NVIDIA GeForce GT 435M"
0DD6 = "NVIDIA GeForce GT 550M"
0DD8 = "NVIDIA Quadro 2000"
0DDA = "NVIDIA Quadro 2000M"
0DE0 = "NVIDIA GeForce GT 440"
0DE1 = "NVIDIA GeForce GT 430"
0DE2 = "NVIDIA GeForce GT 420"
0DE5 = "NVIDIA GeForce GT 530"
0DEC = "NVIDIA GeForce GT 525M"
0DED = "NVIDIA GeForce GT 520M"
0DEE = "NVIDIA GeForce GT 415M"
0DF0 = "NVIDIA GeForce GT 425M"
0DF1 = "NVIDIA GeForce GT 420M"
0DF2 = "NVIDIA GeForce GT 435M "
0DF3 = "NVIDIA GeForce GT 420M  "
0DF4 = "NVIDIA GeForce GT 540M"
0DF5 = "NVIDIA GeForce GT 525M "
0DF6 = "NVIDIA GeForce GT 550M"
0DF7 = "NVIDIA GeForce GT 520M"
0DF8 = "NVIDIA Quadro 600"
0DFA = "NVIDIA Quadro 1000M"
0E22 = "NVIDIA GeForce GTX 460"
0E23 = "NVIDIA GeForce GTX 460 SE"
0E24 = "NVIDIA GeForce GTX 460"
0E30 = "NVIDIA GeForce GTX 470M"
0E31 = "NVIDIA GeForce GTX 485M"
0E3A = "NVIDIA Quadro 3000M"
0E3B = "NVIDIA Quadro 4000M"
1040 = "NVIDIA GeForce GT 520"
1050 = "NVIDIA GeForce GT 520M  "
1054 = "NVIDIA GeForce 410M"
1056 = "NVIDIA NVS 4200M"
1057 = "NVIDIA NVS 4200M  "
1080 = "NVIDIA GeForce GTX 580"
1081 = "NVIDIA GeForce GTX 570"
1082 = "NVIDIA GeForce GTX 560 Ti"
1084 = "NVIDIA GeForce GTX 560"
1086 = "NVIDIA GeForce GTX 570"
1088 = "NVIDIA GeForce GTX 590"
1089 = "NVIDIA GeForce GTX 580"
1091 = "NVIDIA Tesla M2090"
109A = "NVIDIA Quadro 5010M "
109B = "NVIDIA Quadro 7000"
10C0 = "NVIDIA GeForce 9300 GS"
10C3 = "NVIDIA GeForce 8400GS"
10C5 = "NVIDIA GeForce 405"
10D8 = "NVIDIA NVS 300"
1200 = "NVIDIA GeForce GTX 560 Ti"
1201 = "NVIDIA GeForce GTX 560"
1241 = "NVIDIA GeForce GT 545"
1243 = "NVIDIA GeForce GT 545"
1244 = "NVIDIA GeForce GTX 550 Ti"
1245 = "NVIDIA GeForce GTS 450"
1251 = "NVIDIA GeForce GTX 560M "



B. Finding your graphics card hardware matching device ID number using Windows :

  1. Open Device Manager using:

  In Windows XP:

  Control Panel  >>>>  System  >>>>  Hardware >>>>  Device Manager

Control Panel >>>> Administrative Tools >>>> Computer Management >>>> Device Manager


  In Windows Vista:

Control Panel >>>> Classic View >>>> Device Manager

Control Panel  >>>> Default View >>>> System and Maintenance >>>> Device Manager


  In Windows 7:

  Control Panel  >>>>> View By:  either Large or Small icons >>>> Device Manager

  Control Panel  >>>>> View By:  Category  >>>> Hardware and Sound  >>>> Devices and Printers >>>> Device Manager

  Alternatively, in XP, Vista or Windows7, in the Run/Start search/Search programs and files box type devmgmt.msc., and additionally, for Vista and Windows7, in the Programs pop-up window, select and click on devmgmt.msc.

  2. In Device Manager window go to Display adapters and either click on the active triangle or + tab or double-click on the Display adapters icon.....your graphics card(s) icon(s) should appear

3. Right-click on the graphics card icon and in the pop-up window that appears select Properties

4. In the Properties pop-up window >>>> Details tab >>>> Property drop-down menu >>>> Matching device id

An alphanumeric string like pci\ven_10de&dev_0614 gives the information required......the complete hardware matching device ID number has two components:

Vendor ID number (prefixed with VEN)
Device ID number (prefixed with DEV)

In the example above, the Vendor ID is 10de and the Device ID is 0614.....


C. Finding your graphics card hardware matching device ID number using OS X :

This can be done from OS X as follows, depending on which version of OS X you are running on your OSX86 (Hackintosh) PC:

Install and run DPCIManager v0.3 by AnV (and cparm for resizeable window), which has versions that run on  Tiger, Leopard, and Snow Leopard (Snow Leopard version works in Lion too): Attached File  DPCIManager_v0.3_AnV_cparm.zip   662.8K   228 downloads
  The DPCIManager output is in the following form:

CODE
10de:0614 nVidia Corporation G92 [GeForce 9800 GT]


but unfortunately the output can only be saved as a "window capture" using Grab....

Alternatively, install the lspci port to Snow Leopard by the EvOX86 Team, lspci V1.1.pkg (which works in Lion too):
  Attached File  lspci_V1.1.zip   281.85K   147 downloads
  
and in Terminal type
CODE
lspci -nn


The Terminal
CODE
lspci -nn
command output is in the following form:

CODE
01:00.0 VGA compatible controller [0300]: nVidia Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2)


which can be very usefully copied/saved/exported as a text file.......


D. Relevant nVidia graphics kexts in OS X Lion (and OS X Snow Leopard) :

In OS X Lion, the nVidia graphics kexts are:

GeForce.kext
  GeForce7xxx.kext

NVDAGF100Hal.kext
NVDANV40HalG7xxx.kext
NVDANV50Hal.kext
NVDAResman.kext
NVDAResmanG7xxx.kext
NVSMU.kext

whereas  in Snow Leopard, they are:

GeForce.kext

NVDANV40Hal.kext
NVDANV50Hal.kext
NVDAResman.kext
NVSMU.kext

.......the older  NVDANV30Hal, NVDANV20Hal and NVDANV10Hal kexts are not present in Lion  (having already been removed from Snow Leopard).


E. nVidia graphics kexts functions :

GeForce.kext - enables CI/QE support for GeForce graphics cards (excluding in OS X Lion the same graphics cards as identified by NVDANV40HalG7xxx.kext in OS X Lion and NVDANV40Hal.kext in OS X Snow Leopard )

GeForce7xxx.kext - enables CI/QE support in OS X Lion for the same graphics cards as identified by NVDANV40HalG7xxx.kext in OS X Lion and NVDANV40Hal.kext in OS X Snow Leopard

NVDAGF100Hal.kext - provides support for nVidia graphics cards with hardware matching device ID numbers falling within its specified device ID & mask ID range under <key>IOPCIPrimaryMatch</key>

NVDANV40HalG7xxx.kext - provides support in OS X Lion for the same nVidia GeForce graphics cards with hardware matching  device ID numbers falling within the specified device ID & mask ID  range under <key>IOPCIPrimaryMatch</key> in NVDANV40Hal.kext

NVDANV50Hal.kext - provides support for nVidia graphics cards with hardware matching  device ID numbers falling within its specified device ID & mask ID  range under <key>IOPCIPrimaryMatch</key>

NVDANV40Hal.kext - provides support in OS X Snow Leopard for nVidia graphics cards with hardware matching  device ID numbers falling within its specified device ID & mask ID  range under <key>IOPCIPrimaryMatch</key>

NVDAResman.kext - provides display resolution change management for  GeForce graphics cards (excluding in OS X Lion the same graphics cards as identified by NVDANV40HalG7xxx.kext in OS X Lion and NVDANV40Hal.kext in OS X Snow Leopard )

NVDAResmanG7xxx.kext - provides display resolution change management in OS X Lion for the same graphics cards as identified by NVDANV40HalG7xxx.kext in OS X Lion and NVDANV40Hal.kext in OS X Snow Leopard
NVSMU.kext - provides firmware matching in a personality by specifying a value for the IONameMatch key, specifically:

pci10de,aa3 = nVidia Corporation MCP79 Co-processor
pci10de,7da = NVIDIA nForce System Management Controller

Thus, quoting for a real Mac:

QUOTE
Open Firmware Matching A PCI device driver can use Open Firmware matching in a personality by specifying a value for the IONameMatch  key. The value is either a single string or an array of strings, which  are compared against the values for the Open Firmware device properties  name, compatible, device_type, or model.

If any of the values for the IONameMatch  key match any of the Open Firmware properties, the match is considered  a success and an instance of the driver is created for the personality.  The name that resulted in a match is stored as a property in the  driver’s I/O Registry entry in the IONameMatched key (kIONameMatchedKey).

For more information on name matching, you should consult the documentation for the IOService class.



F. Understanding the device ID register and mask ID relationship in the <key>IOPCIPrimaryMatch</key> of the   NVDAGF100Hal.kext, NVDANV40HalG7xxx.kext, NVDANV50Hal.kext and NVDANV40Hal.kext (and also older NVDANVxxHal.kexts used in pre-Snow Leopard OS X versions)

In all these kexts, the Info.plist file will have in the <string></string> for <key>IOPCIPrimaryMatch</key> an array of strings:

NVDAGF100HAL

            <key>IOPCIPrimaryMatch</key>
            <string>
                0x06c010de&amp;0xffe0ffff
                0x0dc010de&amp;0xffc0ffff
                0x0e2010de&amp;0xffe0ffff
                0x0ee010de&amp;0xffe0ffff
                0x0f0010de&amp;0xffc0ffff
                0x104010de&amp;0xffc0ffff
                0x124010de&amp;0xffc0ffff
            </string>

NVDANV40HALG7xxx

            <key>IOPCIPrimaryMatch</key>
            <string>
                0x004010de&amp;0xfff0ffff
                0x00f010de&amp;0xfff0ffff
                0x022010de&amp;0xfff0ffff
                0x014010de&amp;0xfff0ffff
                0x016010de&amp;0xfff0ffff
                0x009010de&amp;0xfff0ffff
                0x01d010de&amp;0xfff0ffff
                0x039010de&amp;0xfff0ffff
                0x029010de&amp;0xfff0ffff
            </string>


NVDANV50HAL

            <key>IOPCIPrimaryMatch</key>
            <string>
                0x00f010de&amp;0xfff0ffff
                0x019010de&amp;0xfff0ffff
                0x040010de&amp;0xfff0ffff
                0x042010de&amp;0xfff0ffff
                0x05e010de&amp;0xfff8ffff
                0x05f010de&amp;0xfff0ffff
                0x060010de&amp;0xffe0ffff
                0x062010de&amp;0xffe0ffff
                0x064010de&amp;0xffe0ffff
                0x06e010de&amp;0xfff0ffff
                0x086010de&amp;0xffe0ffff
                0x08a010de&amp;0xffe0ffff
                0x0a2010de&amp;0xffa0ffff
                0x0ca010de&amp;0xffe0ffff
            </string>


NVDANV40HAL

            <key>IOPCIPrimaryMatch</key>
            <string>
                0x004010de&amp;0xfff0ffff
                0x00f010de&amp;0xfff0ffff
                0x022010de&amp;0xfff0ffff
                0x014010de&amp;0xfff0ffff
                0x016010de&amp;0xfff0ffff
                0x009010de&amp;0xfff0ffff
                0x01d010de&amp;0xfff0ffff
                0x039010de&amp;0xfff0ffff
                0x029010de&amp;0xfff0ffff
            </string>

so, now to the explanations:

1. Meaning of
CODE
&amp;


The mask ID is attached to the device ID register value using the bitwise AND operator, which is a single ampersand
CODE
&


However, the bitwise AND operator must be encoded as
CODE
&amp;
in XML if you are editing it directly as a XML Property List file, e.g. using TextEdit, Textmate, TextWrangler, Dashcode etc. If you are using Xcode or Property List Editor, the &amp; escape is represented simply as an ampersand (&). Thus, the device ID register value and the mask ID taken together via the bitwise AND operator.

2. Meaning of 0xffe0ffff, 0xffc0ffff, 0xfff0ffff, 0xfff8ffff, 0xffa0ffff

0xffe0ffff, 0xffc0ffff, 0xfff0ffff, 0xfff8ffff, 0xffa0ffff are mask IDs......simply put, they specify what range of device IDs related to the pivotal device ID register can be loaded by the kext, or as Krazubu says, "it is the 'tolerancy' of the device ID"

Thus, matching the device ID overhead the mask ID:

0x 06 c0 10 de
0x ff   e0    ff   ff

0x 0d c0 10 de
0x ff   c0  ff   ff

0x 00 40 10 de
0x ff   f0  ff  ff

0x 05 e0 10 de
0x ff  f8   ff  ff

 0x 0a 20 10 de
0x ff   a0 ff  ff

the scheme becomes clearer:

f - keep the same hexadecimal value as the pivotal device ID register digit value

0 - can be any hexadecimal value from 0 1 2 3 4 5 6 7 8 9 a b c d e f

a - can be +/- 1 or +/- 2 or +/- 3 or +/- 4 or +/- 5 value-steps added to the pivotal device ID register digit value

b - can be +/- 1 or +/- 2 or +/- 3 or +/- 4 value-steps added to the pivotal device ID register digit value

c - can be +/- 1 or +/- 2 or +/- 3 value-steps added to the pivotal device ID register digit value

d - can be +/- 1 or +/- 2 value-steps added to the pivotal device ID register digit value

e - can be +/- 1 value-step added to the pivotal device ID register digit value

  8 - can be any hexadecimal value from 0 1 2 3 4 5 6 7 8

Thus, for example, in:

0x06c010de&amp;0xffe0ffff, c could be replaced by b or d, and 0 by any one of 1 2 3 4 5 6 7 8 9 a b c d e f

0x0e2010de&amp;0xffe0ffff, 2 could be replaced by 1 or 3, and 0 by any one of 1 2 3 4 5 6 7 8 9 a b c d e f

0x0dc010de&amp;0xffc0ffff, c could be replaced by 9 or a or b or d or e or f, and 0 by any one of 1 2 3 4 5 6 7 8 9 a b c d e f

0x124010de&amp;0xffc0ffff, 4 could be replaced by 1 or 2 or 3 or 5 or 6 or 7, and 0 by any one of 1 2 3 4 5 6 7 8 9 a b c d e f

0x0f0010de&amp;0xffc0ffff, 0 could be replaced by 1 or 2 or 3, and 0 by any one of 1 2 3 4 5 6 7 8 9 a b c d e f (Could/would 0 here be replaced f or e or d as the - 1 or - 2 or - 3 value-steps......?)

My understanding as expressed above is based on my study of the list compiled by thorzine74, but I am happy to be corrected on this, as I want learn and have the correct understanding..... smile.gif

thorzine74 compiled the following list of what NVIDIA GPUs are supported in Snow Leopard 10.6.1 according to kexts, whose thinking was that it could be useful to know what is supported and what is not. It does not mean it should work, it just means their device IDs are recognized by the kexts, so with a proper injector method (kext, EFI string, DSDT modding, Chameleon with GraphicsEnabley = Yes) it may work.

CODE
List of NVIDIA GPUs supported in Snow Leopard 10.6.1



The list is formatted as:

Device id mask:

Code:
    Device-id  Core [Chipset name]

Chipsets Supported by NVDANV40Hal.kext [v1.6.2.35 (18.6.5f11)]:

0x004010de&0xfff0ffff

Code:
    0040  NV40 [GeForce 6800 Ultra]
    0041  NV40 [GeForce 6800]
    0042  NV40.2 [GeForce 6800 LE]
    0043  NV40.3 [GeForce 6800 XE]
    0044  NV40 [GeForce 6800 XT]
    0045  NV40 [GeForce 6800 GT]
    0046  NV45 [GeForce 6800 GT]
    0047  NV40 [GeForce 6800 GS]
    0048  NV40 [GeForce 6800 XT]
    0049  NV40GL
    004d  NV40GL [Quadro FX 4000]
    004e  NV40GL [Quadro FX 4000]

0x00f010de&0xfff0ffff

Code:
    00f0  NV40 [GeForce 6800 Ultra]
    00f1  NV43 [GeForce 6600 GT]
    00f2  NV43 [GeForce 6600]
    00f3  NV43 [GeForce 6200]
    00f4  NV43 [GeForce 6600 LE]
    00f5  G70 [GeForce 7800 GS]
    00f6  NV43 [GeForce 6800 GS]
    00f8  NV45GL [Quadro FX 3400/4400]
    00f9  NV45 [GeForce 6800 GTO]
    00fa  NV36 [GeForce PCX 5750]
    00fb  NV35 [GeForce PCX 5900]
    00fc  NV37GL [Quadro FX 330/GeForce PCX 5300]
    00fd  NV37GL [Quadro PCI-E Series]
    00fe  NV38GL [Quadro FX 1300]
    00ff  NV18 [GeForce PCX 4300]

0x022010de&0xfff0ffff

Code:
    0221  NV44A [GeForce 6200]
    0222  NV44 [GeForce 6200 A-LE]

0x014010de&0xfff0ffff

Code:
    0140  NV43 [GeForce 6600 GT]
    0141  NV43 [GeForce 6600]
    0142  NV43 [GeForce 6600 LE]
    0143  NV43 [GeForce 6600 VE]
    0144  NV43 [GeForce Go 6600]
    0145  NV43 [GeForce 6610 XL]
    0146  NV43 [Geforce Go 6600TE/6200TE]
    0147  NV43 [GeForce 6700 XL]
    0148  NV43 [GeForce Go 6600]
    0149  NV43 [GeForce Go 6600 GT]
    014a  NV43 [Quadro NVS 440]
    014c  NV43 [Quadro FX 540 MXM]
    014d  NV43GL [Quadro FX 550]
    014e  NV43GL [Quadro FX 540]
    014f  NV43 [GeForce 6200]

0x016010de&0xfff0ffff

Code:
    0160  NV44 [GeForce 6500]
    0161  NV44 [GeForce 6200 TurboCache™]
    0162  NV44 [GeForce 6200SE TurboCache ™]
    0163  NV44 [GeForce 6200 LE]
    0164  NV44 [GeForce Go 6200]
    0165  NV44 [Quadro NVS 285]
    0166  NV43 [GeForce Go 6400]
    0167  NV43 [GeForce Go 6200/6400]
    0168  NV43 [GeForce Go 6200/6400]
    0169  NV44 [GeForce 6250]
    016a  NV44 [GeForce 7100 GS]

0x009010de&0xfff0ffff

Code:
    0090  G70 [GeForce 7800 GTX]
    0091  G70 [GeForce 7800 GTX]
    0092  G70 [GeForce 7800 GT]
    0093  G70 [GeForce 7800 GS]
    0095  G70 [GeForce 7800 SLI]
    0098  G70 [GeForce Go 7800]
    0099  G70 [GeForce Go 7800 GTX]
    009d  G70GL [Quadro FX 4500]

0x01d010de&0xfff0ffff

Code:
    01d0  G72 [GeForce 7350 LE]
    01d1  G72 [GeForce 7300 LE]
    01d3  G72 [GeForce 7300 SE/7200 GS]
    01d6  G72M [GeForce Go 7200]
    01d7  G72M [Quadro NVS 110M/GeForce Go 7300]
    01d8  G72M [GeForce Go 7400]
    01da  G72M [Quadro NVS 110M]
    01db  G72M [Quadro NVS 120M]
    01dc  G72GL [Quadro FX 350M]
    01dd  G72 [GeForce 7500 LE]
    01de  G72GL [Quadro FX 350]
    01df  G71 [GeForce 7300 GS]

0x039010de&0xfff0ffff

Code:
    0390  G73 [GeForce 7650 GS]
    0391  G73 [GeForce 7600 GT]
    0392  G73 [GeForce 7600 GS]
    0393  G73 [GeForce 7300 GT]
    0394  G73 [GeForce 7600 LE]
    0395  G73 [GeForce 7300 GT]
    0397  G73 [GeForce Go 7700]
    0398  G73 [GeForce Go 7600]
    0399  G73 [GeForce Go 7600 GT]
    039b  G73 [GeForce Go 7900 SE]
    039c  Quadro FX 550M
    039e  G73GL [Quadro FX 560]

0x029010de&0xfff0ffff

Code:
    0290  G71 [GeForce 7900 GTX]
    0291  G71 [GeForce 7900 GT/GTO]
    0292  G71 [GeForce 7900 GS]
    0293  G71 [GeForce 7900 GX2]
    0294  G71 [GeForce 7950 GX2]
    0295  G71 [GeForce 7950 GT]
    0297  G71 [GeForce Go 7950 GTX]
    0298  G71 [GeForce Go 7900 GS]
    0299  G71 [GeForce Go 7900 GTX]
    029a  G71 [Quadro FX 2500M]
    029b  G71 [Quadro FX 1500M]
    029c  G71 [Quadro FX 5500]
    029d  G71GL [Quadro FX 3500]
    029e  G71 [Quadro FX 1500]
    029f  G70 [Quadro FX 4500 X2]


Chipsets supported by NVDANV50Hal.kext [v1.6.2.35 (18.6.5f11)]:

0x00f010de&0xfff0ffff

Code:
    00f0  NV40 [GeForce 6800 Ultra]
    00f1  NV43 [GeForce 6600 GT]
    00f2  NV43 [GeForce 6600]
    00f3  NV43 [GeForce 6200]
    00f4  NV43 [GeForce 6600 LE]
    00f5  G70 [GeForce 7800 GS]
    00f6  NV43 [GeForce 6800 GS]
    00f7  ?
    00f8  NV45GL [Quadro FX 3400/4400]
    00f9  NV45 [GeForce 6800 GTO]
    00fa  NV36 [GeForce PCX 5750]
    00fb  NV35 [GeForce PCX 5900]
    00fc  NV37GL [Quadro FX 330/GeForce PCX 5300]
    00fd  NV37GL [Quadro PCI-E Series]
    00fe  NV38GL [Quadro FX 1300]
    00ff  NV18 [GeForce PCX 4300]

0x019010de&0xfff0ffff

Code:
    0190  ?
    0191  G80 [GeForce 8800 GTX]
    0192  ?
    0193  G80 [GeForce 8800 GTS]
    0194  G80 [GeForce 8800 Ultra]
    0195  ?
    0196  ?
    0197  Tesla S870 (Compute Server Component)
    0198  ?
    0199  ?
    019a  ?
    019b  ?
    019c  ?
    019d  G80 [Quadro FX 5600]
    019e  G80 [Quadro FX 4600]
    019f  ?

0x040010de&0xfff0ffff

Code:
    0400  G84 [GeForce 8600 GTS]
    0401  G84 [GeForce 8600GT]
    0402  G84 [GeForce 8600 GT]
    0403  G84 [GeForce 8600 GS]
    0404  G84 [GeForce 8400 GS]
    0405  G84 [GeForce 9500M GS]
    0406  ?
    0407  G84 [GeForce 8600M GT]
    0408  G84 [GeForce 9650M GS]
    0409  G84 [GeForce 8700M GT]
    040a  G84 [Quadro FX 370]
    040b  Quadro NVS 320M
    040c  Quadro FX 570M
    040d  Quadro FX 1600M
    040e  G84 [Quadro FX 570]
    040f  G84 [Quadro FX 1700]

0x042010de&0xfff0ffff

Code:
    0420  G86 [GeForce 8400 SE]
    0421  G86 [GeForce 8500 GT]
    0422  G86 [GeForce 8400 GS]
    0423  G86 [GeForce 8300 GS]
    0424  G86 [GeForce 8400 GS]
    0425  G86 [GeForce 8600M GS]
    0426  G86 [GeForce 8400M GT]
    0427  G86 [GeForce 8400M GS]
    0428  G86 [GeForce 8400M G]
    0429  Quadro NVS 140M
    042a  Quadro NVS 130M
    042b  Quadro NVS 135M
    042c  G86 [GeForce 9400 GT]
    042d  Quadro FX 360M
    042e  G86 [GeForce 9300M G]
    042f  G86 [Quadro NVS 290]

0x05e010de&0xfff8ffff

Code:
    05e0  GT200b [GeForce GTX 295]
    05e1  GT200 [GeForce GTX 280]
    05e2  GT200 [GeForce GTX 260]
    05e3  GT200b [GeForce GTX 285]
    05e4  ?
    05e5  ?
    05e6  GT200b [GeForce GTX 275]
    05e7  GT200 [Tesla C1060]

0x05f010de&0xfff0ffff

Code:
    05f0  ?
    05f1  ?
    05f2  ?
    05f3  ?
    05f4  ?
    05f5  ?
    05f6  ?
    05f7  ?
    05f8  GT200GL [Quadro Plex 2200 S4]
    05f9  GT200GL [Quadro CX]
    05fa  ?
    05fb  ?
    05fc  ?
    05fd  GT200GL [Quadro FX 5800]
    05fe  GT200GL [Quadro FX 4800]
    05ff  ?

0x060010de&0xffe0ffff

Code:
    0600  G92 [GeForce 8800 GTS 512]
    0601  G92 [GeForce 9800 GT]
    0602  G92 [GeForce 8800 GT]
    0603  ?
    0604  G92 [GeForce 9800 GX2]
    0605  G92 [GeForce 9800 GT]
    0606  G92 [GeForce 8800 GS]
    0607  ?
    0608  G92 [GeForce 9800M GTX]
    0609  G92 [GeForce 8800M GTS]
    060a  GT200 [GeForce GTX 280M]
    060b  G92 [GeForce 9800M GT]
    060c  G92 [GeForce 8800M GTX]
    060d  G92 [GeForce 8800 GS]
    060e  ?
    060f  ?
    0610  ?
    [...]
    061f  ?

0x062010de&0xffe0ffff

Code:
    0620  ?
    0621  ?
    0622  G94 [GeForce 9600 GT]
    0623  G94 [GeForce 9600 GS]
    0624  ?
    0625  G94 [GeForce 9600 GSO 512]
    0626  G94 [GeForce GT 130]
    0627  G94 [GeForce GT 140]
    0628  G94 [GeForce 9800M GTS]
    0629  ?
    062a  G94 [GeForce 9700M GTS]
    062b  G94 [GeForce 9800M GS]
    062c  G94 [GeForce 9800M GTS]
    062d  ?
    062e  ?
    062f  ?
    0630  ?
    [...]
    063f  ?

0x064010de&0xffe0ffff

Code:
    0640  G96 [GeForce 9500 GT]
    0641  G96 [GeForce 9400 GT]
    0642  ?
    0643  G96 [GeForce 9500 GT]
    0644  G96 [GeForce 9500 GS]
    0645  G96 [GeForce 9500 GS]
    0646  G96 [GeForce GT 120]
    0647  G96 [GeForce 9600M GT]
    0648  G96 [GeForce 9600M GS]
    0649  G96 [GeForce 9600M GT]
    064a  G96 [GeForce 9700M GT]
    064b  G96 [GeForce 9500M G]
    064c  G96 [GeForce 9650M GT]
    064d  ?
    064e  ?
    064f  ?
    0650  ?
    0651  G96 [GeForce G 110M]
    0652  G96 [GeForce GT 130M]
    0653  G96M [GeForce GT 120M]
    0654  ?
    0655  ?
    0656  ?
    0657  ?
    0658  G96 [Quadro FX 380]
    0659  G96 [Quadro FX 580]
    065a  ?
    065b  G96 [GeForce 9400 GT]
    065c  G96M [Quadro FX 770M]
    065d  ?
    065e  ?
    065f  ?

0x06e010de&0xfff0ffff

Code:
    06e0  G98 [GeForce 9300 GE]
    06e1  G98 [GeForce 9300 GS]
    06e2  G98 [GeForce 8400]
    06e3  G98 [GeForce 8300 GS]
    06e4  G98 [GeForce 8400 GS]
    06e5  G98 [GeForce 9300M GS]
    06e6  G98 [GeForce G100]
    06e7  G98 [GeForce 9300 SE]
    06e8  G98 [GeForce 9200M GS]
    06e9  G98 [GeForce 9300M GS]
    06ea  G86M [Quadro NVS 150M]
    06eb  G98M [Quadro NVS 160M]
    06ec  G98M [GeForce G 105M]
    06ed  ?
    06ec  ?
    06ef  G98M [GeForce G 103M]

0x086010de&0xffe0ffff

Code:
    0860  C79 [GeForce 9300]
    0861  C79 [GeForce 9400]
    0862  C79 [GeForce 9400M G]
    0863  C79 [GeForce 9400M]
    0864  C79 [GeForce 9300]
    0865  C79 [GeForce 9300]
    0866  C79 [GeForce 9400M G]
    0867  C79 [GeForce 9400]
    0868  C79 [nForce 760i SLI]
    0869  ?
    086a  C79 [GeForce 9400]
    086b  ?
    086c  C79 [GeForce 9300 / nForce 730i]
    086d  C79 [GeForce 9200]
    086e  C79 [GeForce 9100M G]
    086f  C79 [GeForce 9200M G]
    0870  C79 [GeForce 9400M]
    0871  C79 [GeForce 9200]
    0872  C79 [GeForce G102M]
    0873  C79 [GeForce G102M]
    0874  ?
    0875  ?
    0876  ?
    0877  ?
    0878  ?
    0879  ?
    087a  C79 [Quadro FX 470]
    087b  ?
    087c  ?
    087d  ION VGA
    087e  ?
    087f  C79 [Quadro FX 470M]

0x0a2010de&0xffa0ffff

Code:
    0a20  GT200 [GeForce GT 220]
    [...]
    0a2f  ?
    0a30  ?
    [...]
    0a3f  ?
    0a60  GT200 [GeForce G210]
    0a61  ?
    0a62  ?
    0a63  ?
    0a64  ?
    0a65  GT200 [GeForce 210]
    [...]
    0a6f  ?
    0a70  ?
    [...]
    0a7f  ?

0x0ca010de&0xffe0ffff

(No device ids in the database from these ones at all,
so I googled around and found some info but its probably incorrect...)

Code:
    0ca0  GT215 [?]
    0ca1  ?
    0ca2  ?
    0ca3  GT230 [?]
    0ca4  D10P-40 [?]
    0ca5  D10P2-50 [?]
    0ca6  ?
    0ca7  ?
    0ca8  ?  [GeForce GTS 260M]
    0ca9  ?  [GeForce GTS 250M]
    0caa  ?
    0cab  ?
    0cac
    0cad  N10E-ES [?]
    0cae
    0caf  ? [GeForce GT 335M]
    0cb0  ? [GeForce GTS 350M]
    0cb1  ? [GeForce GTS 360M]
    0cb2
    0cb3
    0cb4
    0cb5
    0cb6
    0cb7
    0cb8
    0cb9
    0cba
    0cbb
    0cbc  N10P-GLM4 [?]
    0cbd
    0cbe
    0cbf

Edit 2009/10/15: added all device ids that match,
in case some cards exist with them but are not in the pci database.
"[...]" means everything between xxx0 to xxxf is missing from the db.

This understanding is that expressed I believe by VooD as  well, and here is his list of what he believes are NVDAGF100Hal.kext supported graphics cards (with no guarantees!):

CODE
0x06c010de&0xffe0ffff

06C0 = "NVIDIA GeForce GTX 480"
06C4 = "NVIDIA GeForce GTX 465"
06CD = "NVIDIA GeForce GTX 470"
06D1 = "NVIDIA Tesla C2050 / C2070"
06D2 = "NVIDIA Tesla M2070"
06D2 = "NVIDIA Tesla X2070"
06D8 = "NVIDIA Quadro 6000"
06D9 = "NVIDIA Quadro 5000"
06DC = "NVIDIA Quadro 6000 "
06DD = "NVIDIA Quadro 4000"
06DE = "NVIDIA Tesla T20 Processor"
06DE = "NVIDIA Tesla S2050"
06DE = "NVIDIA Tesla M2050"
06DE = "NVIDIA Tesla X2070 "
06DF = "NVIDIA Tesla M2070-Q"

0x0dc010de&0xffc0ffff

0DC0 = "NVIDIA GeForce GT 440"
0DC4 = "NVIDIA GeForce GTS 450"
0DC5 = "NVIDIA GeForce GTS 450 "
0DC6 = "NVIDIA GeForce GTS 450 "
0DD8 = "NVIDIA Quadro 2000"
0DE0 = "NVIDIA GeForce GT 440 "
0DE1 = "NVIDIA GeForce GT 430"
0DDA = "NVIDIA Quadro 2000M"
0DF0 = "NVIDIA GeForce GT 425M"
0DF4 = "NVIDIA GeForce GT 540M "
0DF5 = "NVIDIA GeForce GT 525M"
0DF7 = "NVIDIA GeForce GT 520M"
0DFA = "NVIDIA Quadro 1000M"
0DE2 = "NVIDIA GeForce GT 420"
0DE5 = "NVIDIA GeForce GT 530"
0DF8 = "NVIDIA Quadro 600"

0x0e2010de&0xffe0ffff
0E22 = "NVIDIA GeForce GTX 460"
0E23 = "NVIDIA GeForce GTX 460 SE"
0E24 = "NVIDIA GeForce GTX 460 "

0x104010de&0xffc0ffff
1040 = "NVIDIA GeForce GT 520"
1050 = "NVIDIA GeForce GT 520M "
1056 = "NVIDIA NVS 4200M"
1057 = "NVIDIA NVS 4200M "

0x124010de&0xffc0ffff
1241 = "NVIDIA GeForce GT 545"
1243 = "NVIDIA GeForce GT 545 "
1244 = "NVIDIA GeForce GTX 550 Ti"
1245 = "NVIDIA GeForce GTS 450 "

but while the above is interesting  from a knowledge and understanding perspective (at least to me anyway..... tongue.gif )...... the real point of this section is to show how to enter the nVidia graphics card directly into the <key>IOPCIPrimaryMatch</key> string array, and so, understanding how the mask ID argument functions is not a necessity..... wink.gif


F. Editing Info.plist files of nVidia graphics kexts in OS X Lion (and OS X Snow Leopard) :

NVEnabler64.kext as an example of an graphics injector kext that may require the inserting of your nVidia graphics card(s) hardware matching device ID numbers into the InFo.plist file <key>IOPCIPrimaryMatch</key> string array of one of the following kexts, if the NVEnabler64.kext placed in /Extra/Extensions/ does not function within OS X Lion without doing so: NVDAGF100Hal.kext or NVDANV40HalG7xxx.kext or NVDANV50Hal.kext

 Your nVidia graphics card(s) hardware matching device ID numbers will determine which of the above kexts it needs to be, by checking thorazine74's list to find a card whose matching device ID number is very similar to your card(s) number....see Part E. above.....

It is worth noting that, at least in OS X Snow Leopard (and OS X Leopard), if you attempt to use some other graphics injector kexts, you may have to also add your nVidia graphics card(s) hardware matching device ID numbers in the injector kext's Info.plist file, and at the same time, insert the correct NVCAP string for you graphics card(s) and change the IOProbeScore value to 0 in the injector kext's Info.plist file.....


To get to the Info.plist file in each kext:

1. Navigate to /System/Library/Extensions

2. Find each kext one at a time and make a backup copy in a safe location on your HDD

3. Right-click on the chosen kext icon, choosing "Show Package Contents", then open Contents folder to find Info.plist.

4. Open the Info.plist file via Terminal using sudo nano etc., or right-click, choosing "Open With", and selecting your preferred Text Editor app; e.g.Text Edit, TextMate, TextWrangler, Property List Editor, or PlistEdit Pro etc. that is capable of the string data in hexadecimal form.....

5. Make the changes to each Info.plist file and save the modified files......

So, using
CODE
10de:0614 nVidia Corporation G92 [GeForce 9800 GT]
as an example, the GeForce 9800 GT hardware matching device ID numbers have to be written in the following form for insertion into the Info.plist files:

0x061410de (the 0x denotes that the number that follows is in hexadecimal format)

as follows:

NVDAResman.kext in OS X Leopard

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>CFBundleDevelopmentRegion</key>
    <string>English</string>
    <key>CFBundleExecutable</key>
    <string>NVDAResman</string>
    <key>CFBundleGetInfoString</key>
    <string>NVDAResman 1.5.36.25 (17.3.5f14)</string>
    <key>CFBundleIdentifier</key>
    <string>com.apple.NVDAResman</string>
    <key>CFBundleInfoDictionaryVersion</key>
    <string>6.0</string>
    <key>CFBundleName</key>
    <string>NVIDIA Resman Kernel Extension</string>
    <key>CFBundlePackageType</key>
    <string>KEXT</string>
    <key>CFBundleShortVersionString</key>
    <string>1.5.36</string>
    <key>CFBundleSignature</key>
    <string>????</string>
    <key>CFBundleVersion</key>
    <string>5.3.6</string>
    <key>IOKitPersonalities</key>
    <dict>
        <key>NVidiaRM</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>com.apple.NVDAResman</string>
            <key>IOClass</key>
            <string>NVDA</string>
            <key>IOMatchCategory</key>
            <string>IOFramebuffer</string>
            <key>IONameMatch</key>
            <array>
                <string>MNCA,GeForce2MX</string>
                <string>NVDA,NVMac</string>
            </array>
            <key>IOProbeScore</key>
            <integer>60000</integer>
            <key>IOProviderClass</key>
            <string>IOPCIDevice</string>
        </dict>
        <key>NVidiaRMPCIMatch</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>com.apple.NVDAResman</string>
            <key>IOClass</key>
            <string>NVDA</string>
            <key>IOMatchCategory</key>
            <string>IOFramebuffer</string>
            <key>IONameMatched</key>
            <string>NVDA,NVMac</string>
            <key>IOPCIPrimaryMatch</key>
            <string>0x011010de&amp;0xfff8ffff 0x017010de&amp;0xfff8ffff 0x017910de 0x018010de&amp;0xfff8ffff 0x018810de 0x018910de 0x020010de&amp;0xfff8ffff 0x025010de&amp;0xfff8ffff 0x028010de&amp;0xfff8ffff 0x030010de&amp;0xfff8ffff 0x031010de&amp;0xfff8ffff 0x031910de 0x034910de</string>
            <key>IOProbeScore</key>
            <integer>50000</integer>
            <key>IOPropertyMatch</key>
            <dict>
                <key>name</key>
                <string>display</string>
            </dict>
            <key>IOProviderClass</key>
            <string>IOPCIDevice</string>
        </dict>
        <key>NVidiaRMTwinView</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>com.apple.NVDAResman</string>
            <key>IOClass</key>
            <string>NVDA</string>
            <key>IOMatchCategory</key>
            <string>IOFramebuffer</string>
            <key>IONameMatch</key>
            <array>
                <string>MNCA,GeForce2MX</string>
                <string>NVDA,NVMac</string>
            </array>
            <key>IOProbeScore</key>
            <integer>60000</integer>
            <key>IOProviderClass</key>
            <string>IONDRVDevice</string>
        </dict>
    </dict>
    <key>OSBundleCompatibleVersion</key>
    <string>1.2.0</string>
    <key>OSBundleLibraries</key>
    <dict>
        <key>com.apple.iokit.IOGraphicsFamily</key>
        <string>1.5</string>
        <key>com.apple.iokit.IONDRVSupport</key>
        <string>1.5</string>
        <key>com.apple.iokit.IOPCIFamily</key>
        <string>2.4</string>
        <key>com.apple.kpi.bsd</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.iokit</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.libkern</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.mach</key>
        <string>9.0.0</string>
    </dict>
    <key>OSBundleRequired</key>
    <string>Safe Boot</string>
</dict>
</plist>


 NVDAResman.kext in OS X Snow Leopard - note the absence of the <key>IOPCIPrimaryMatch</key> and its <string></string> below the <key>IONameMatch</key> string array

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>CFBundleDevelopmentRegion</key>
    <string>English</string>
    <key>CFBundleExecutable</key>
    <string>NVDAResman</string>
    <key>CFBundleGetInfoString</key>
    <string>NVDAResman 1.6.36.10 (256.00.35f11)</string>
    <key>CFBundleIdentifier</key>
    <string>com.apple.NVDAResman</string>
    <key>CFBundleInfoDictionaryVersion</key>
    <string>6.0</string>
    <key>CFBundleName</key>
    <string>NVIDIA Resman Kernel Extension</string>
    <key>CFBundlePackageType</key>
    <string>KEXT</string>
    <key>CFBundleShortVersionString</key>
    <string>1.6.36</string>
    <key>CFBundleSignature</key>
    <string>????</string>
    <key>CFBundleVersion</key>
    <string>6.3.6</string>
    <key>IOKitPersonalities</key>
    <dict>
        <key>NVRM</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>com.apple.NVDAResman</string>
            <key>IOClass</key>
            <string>NVDA</string>
            <key>IOMatchCategory</key>
            <string>IOFramebuffer</string>
            <key>IONameMatch</key>
            <array>
                <string>NVDA,NVMac</string>
            </array>
            <key>IOParentMatch</key>
            <dict>
                <key>IOPropertyMatch</key>
                <dict>
                    <key>NVCLASS</key>
                    <string>NVDA</string>
                </dict>
                <key>IOProviderClass</key>
                <string>IOPCIDevice</string>
            </dict>
            <key>IOProbeScore</key>
            <integer>60000</integer>
            <key>IOProviderClass</key>
            <string>IONDRVDevice</string>
        </dict>
    </dict>
    <key>OSBundleCompatibleVersion</key>
    <string>1.2.0</string>
    <key>OSBundleLibraries</key>
    <dict>
        <key>com.apple.iokit.IOGraphicsFamily</key>
        <string>1.5</string>
        <key>com.apple.iokit.IONDRVSupport</key>
        <string>1.5</string>
        <key>com.apple.iokit.IOPCIFamily</key>
        <string>2.4</string>
        <key>com.apple.kpi.bsd</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.iokit</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.libkern</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.mach</key>
        <string>9.0.0</string>
    </dict>
    <key>OSBundleRequired</key>
    <string>Safe Boot</string>
</dict>
</plist>


NVDAResman.kext in OS X Lion - note the absence of the <key>IOPCIPrimaryMatch</key> and its <string></string> below the <key>IONameMatch</key> string array
  
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>CFBundleDevelopmentRegion</key>
    <string>English</string>
    <key>CFBundleExecutable</key>
    <string>NVDAResman</string>
    <key>CFBundleGetInfoString</key>
    <string>NVDAResman 7.4.10 270.05.05f01</string>
    <key>CFBundleIdentifier</key>
    <string>com.apple.NVDAResman</string>
    <key>CFBundleInfoDictionaryVersion</key>
    <string>6.0</string>
    <key>CFBundleName</key>
    <string>NVIDIA Resman Kernel Extension</string>
    <key>CFBundlePackageType</key>
    <string>KEXT</string>
    <key>CFBundleShortVersionString</key>
    <string>7.4.10</string>
    <key>CFBundleSignature</key>
    <string>????</string>
    <key>CFBundleVersion</key>
    <string>7.0.4</string>
    <key>IOKitPersonalities</key>
    <dict>
        <key>NVRM</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>com.apple.NVDAResman</string>
            <key>IOClass</key>
            <string>NVDA</string>
            <key>IOMatchCategory</key>
            <string>IOFramebuffer</string>
            <key>IONameMatch</key>
            <array>
                <string>NVDA,NVMac</string>
            </array>
            <key>IOParentMatch</key>
            <dict>
                <key>IOPropertyMatch</key>
                <dict>
                    <key>NVCLASS</key>
                    <string>NVDA</string>
                </dict>
                <key>IOProviderClass</key>
                <string>IOPCIDevice</string>
            </dict>
            <key>IOProbeScore</key>
            <integer>60000</integer>
            <key>IOProviderClass</key>
            <string>IONDRVDevice</string>
        </dict>
    </dict>
    <key>OSBundleCompatibleVersion</key>
    <string>1.2.0</string>
    <key>OSBundleLibraries</key>
    <dict>
        <key>com.apple.iokit.IOGraphicsFamily</key>
        <string>1.5</string>
        <key>com.apple.iokit.IONDRVSupport</key>
        <string>1.5</string>
        <key>com.apple.iokit.IOPCIFamily</key>
        <string>2.4</string>
        <key>com.apple.kpi.bsd</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.iokit</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.libkern</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.mach</key>
        <string>9.0.0</string>
    </dict>
    <key>OSBundleRequired</key>
    <string>Safe Boot</string>
</dict>
</plist>


NVDAResmanG7xxx.kext in OS X Lion - note the absence of the <key>IOPCIPrimaryMatch</key> and its <string></string> below the <key>IONameMatch</key> string array

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>CFBundleDevelopmentRegion</key>
    <string>English</string>
    <key>CFBundleExecutable</key>
    <string>NVDAResmanG7xxx</string>
    <key>CFBundleGetInfoString</key>
    <string>NVDAResmanG7xxx 7.0.52 270.01.00f01</string>
    <key>CFBundleIdentifier</key>
    <string>com.apple.NVDAResman.G7xxx</string>
    <key>CFBundleInfoDictionaryVersion</key>
    <string>6.0</string>
    <key>CFBundleName</key>
    <string>NVIDIA Resman Kernel Extension</string>
    <key>CFBundlePackageType</key>
    <string>KEXT</string>
    <key>CFBundleShortVersionString</key>
    <string>7.0.52</string>
    <key>CFBundleSignature</key>
    <string>????</string>
    <key>CFBundleVersion</key>
    <string>7.0.0</string>
    <key>IOKitPersonalities</key>
    <dict>
        <key>NVRM</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>com.apple.NVDAResman.G7xxx</string>
            <key>IOClass</key>
            <string>NVDAG7xxx</string>
            <key>IOMatchCategory</key>
            <string>IOFramebuffer</string>
            <key>IONameMatch</key>
            <array>
                <string>NVDA,NVMac</string>
            </array>
            <key>IOParentMatch</key>
            <dict>
                <key>IOPropertyMatch</key>
                <dict>
                    <key>NVCLASS</key>
                    <string>NVDAG7xxx</string>
                </dict>
                <key>IOProviderClass</key>
                <string>IOPCIDevice</string>
            </dict>
            <key>IOProbeScore</key>
            <integer>70000</integer>
            <key>IOProviderClass</key>
            <string>IONDRVDevice</string>
        </dict>
    </dict>
    <key>OSBundleCompatibleVersion</key>
    <string>1.2.0</string>
    <key>OSBundleLibraries</key>
    <dict>
        <key>com.apple.iokit.IOGraphicsFamily</key>
        <string>1.5</string>
        <key>com.apple.iokit.IONDRVSupport</key>
        <string>1.5</string>
        <key>com.apple.iokit.IOPCIFamily</key>
        <string>2.4</string>
        <key>com.apple.kpi.bsd</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.iokit</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.libkern</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.mach</key>
        <string>9.0.0</string>
    </dict>
    <key>OSBundleRequired</key>
    <string>Safe Boot</string>
</dict>
</plist>

At present, I am not sure if OS X Lion or OS X Snow Leopard would ever require the insertion, below the <key>IONameMatch</key> string array, of the <key>IOPCIPrimaryMatch</key> and its <string></string> containing a graphics card hardware matching device ID, in order for NVEnabler64.kext to be loaded and to work with the given nVidia graphics card in either OS X Lion or OS X Snow Leopard, as shown here:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>CFBundleDevelopmentRegion</key>
    <string>English</string>
    <key>CFBundleExecutable</key>
    <string>NVDAResman</string>
    <key>CFBundleGetInfoString</key>
    <string>NVDAResman 7.4.10 270.05.05f01</string>
    <key>CFBundleIdentifier</key>
    <string>com.apple.NVDAResman</string>
    <key>CFBundleInfoDictionaryVersion</key>
    <string>6.0</string>
    <key>CFBundleName</key>
    <string>NVIDIA Resman Kernel Extension</string>
    <key>CFBundlePackageType</key>
    <string>KEXT</string>
    <key>CFBundleShortVersionString</key>
    <string>7.4.10</string>
    <key>CFBundleSignature</key>
    <string>????</string>
    <key>CFBundleVersion</key>
    <string>7.0.4</string>
    <key>IOKitPersonalities</key>
    <dict>
        <key>NVRM</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>com.apple.NVDAResman</string>
            <key>IOClass</key>
            <string>NVDA</string>
            <key>IOMatchCategory</key>
            <string>IOFramebuffer</string>
            <key>IONameMatch</key>
            <array>
                <string>NVDA,NVMac</string>
            </array>
<key>IOPCIPrimaryMatch</key>
            <string>0x061410de</string>
            <key>IOParentMatch</key>
            <dict>
                <key>IOPropertyMatch</key>
                <dict>
                    <key>NVCLASS</key>
                    <string>NVDA</string>
                </dict>
                <key>IOProviderClass</key>
                <string>IOPCIDevice</string>
            </dict>
            <key>IOProbeScore</key>
            <integer>60000</integer>
            <key>IOProviderClass</key>
            <string>IONDRVDevice</string>
        </dict>
    </dict>
    <key>OSBundleCompatibleVersion</key>
    <string>1.2.0</string>
    <key>OSBundleLibraries</key>
    <dict>
        <key>com.apple.iokit.IOGraphicsFamily</key>
        <string>1.5</string>
        <key>com.apple.iokit.IONDRVSupport</key>
        <string>1.5</string>
        <key>com.apple.iokit.IOPCIFamily</key>
        <string>2.4</string>
        <key>com.apple.kpi.bsd</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.iokit</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.libkern</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.mach</key>
        <string>9.0.0</string>
    </dict>
    <key>OSBundleRequired</key>
    <string>Safe Boot</string>
</dict>
</plist>

I say this because with my own GeForce 9800 GT graphics card, I can use NVEnabler64.kext in /Extra/Extensions/ in both OS X Lion and OS X Snow Leopard with full CI/QE and resolution switching, without having to insert the GeForce 9800 GT hardware matching device ID (0x061410de) into NVDANV50Hal.kext, let alone in NVDAResman.kext as well......thus, I cannot do any testing......if you would like to test, then let me know your results.....
  
NVDAGF100Hal.kext

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>CFBundleDevelopmentRegion</key>
    <string>English</string>
    <key>CFBundleExecutable</key>
    <string>NVDAGF100Hal</string>
    <key>CFBundleGetInfoString</key>
    <string>NVDAGF100Hal 7.4.10 270.05.05f01</string>
    <key>CFBundleIdentifier</key>
    <string>com.apple.nvidia.nvGF100hal</string>
    <key>CFBundleInfoDictionaryVersion</key>
    <string>6.0</string>
    <key>CFBundleName</key>
    <string>NVIDIA gf100 Resman Kernel Extension</string>
    <key>CFBundlePackageType</key>
    <string>KEXT</string>
    <key>CFBundleShortVersionString</key>
    <string>7.4.10</string>
    <key>CFBundleSignature</key>
    <string>????</string>
    <key>CFBundleVersion</key>
    <string>7.0.4</string>
    <key>IOKitPersonalities</key>
    <dict>
        <key>NVidiaRM</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>com.apple.nvidia.nvGF100hal</string>
            <key>IOClass</key>
            <string>NVDAGF100HAL</string>
            <key>IOMatchCategory</key>
            <string>IOService</string>
            <key>IOPCIPrimaryMatch</key>
            <string>
                0x061410de
                0x06c010de&amp;0xffe0ffff
                0x0dc010de&amp;0xffc0ffff
                0x0e2010de&amp;0xffe0ffff
                0x0ee010de&amp;0xffe0ffff
                0x0f0010de&amp;0xffc0ffff
                0x104010de&amp;0xffc0ffff
                0x124010de&amp;0xffc0ffff
            </string>
            <key>IOProbeScore</key>
            <integer>60000</integer>
            <key>IOProviderClass</key>
            <string>IOPCIDevice</string>
        </dict>
    </dict>
    <key>OSBundleCompatibleVersion</key>
    <string>1.2.0</string>
    <key>OSBundleLibraries</key>
    <dict>
        <key>com.apple.NVDAResman</key>
        <string>1.2.0</string>
        <key>com.apple.kpi.iokit</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.libkern</key>
        <string>9.0.0</string>
    </dict>
    <key>OSBundleRequired</key>
    <string>Safe Boot</string>
</dict>
</plist>

NVDANV40HalG7xxx.kext

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>CFBundleDevelopmentRegion</key>
    <string>English</string>
    <key>CFBundleExecutable</key>
    <string>NVDANV40HalG7xxx</string>
    <key>CFBundleGetInfoString</key>
    <string>NVDANV40HalG7xxx 7.0.52 270.01.00f01</string>
    <key>CFBundleIdentifier</key>
    <string>com.apple.nvidia.nv40hal.G7xxx</string>
    <key>CFBundleInfoDictionaryVersion</key>
    <string>6.0</string>
    <key>CFBundleName</key>
    <string>NVIDIA NV40 Resman Kernel Extension</string>
    <key>CFBundlePackageType</key>
    <string>KEXT</string>
    <key>CFBundleShortVersionString</key>
    <string>7.0.52</string>
    <key>CFBundleSignature</key>
    <string>????</string>
    <key>CFBundleVersion</key>
    <string>7.0.0</string>
    <key>IOKitPersonalities</key>
    <dict>
        <key>NVidiaRM</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>com.apple.nvidia.nv40hal.G7xxx</string>
            <key>IOClass</key>
            <string>NVDANV40HALG7xxx</string>
            <key>IOMatchCategory</key>
            <string>IOService</string>
            <key>IOPCIPrimaryMatch</key>
            <string>
                0x061410de
                0x004010de&amp;0xfff0ffff
                0x00f010de&amp;0xfff0ffff
                0x022010de&amp;0xfff0ffff
                0x014010de&amp;0xfff0ffff
                0x016010de&amp;0xfff0ffff
                0x009010de&amp;0xfff0ffff
                0x01d010de&amp;0xfff0ffff
                0x039010de&amp;0xfff0ffff
                0x029010de&amp;0xfff0ffff
            </string>
            <key>IOProbeScore</key>
            <integer>70000</integer>
            <key>IOProviderClass</key>
            <string>IOPCIDevice</string>
        </dict>
    </dict>
    <key>OSBundleCompatibleVersion</key>
    <string>1.2.0</string>
    <key>OSBundleLibraries</key>
    <dict>
        <key>com.apple.NVDAResman.G7xxx</key>
        <string>1.2.0</string>
        <key>com.apple.kpi.iokit</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.libkern</key>
        <string>9.0.0</string>
    </dict>
    <key>OSBundleRequired</key>
    <string>Safe Boot</string>
</dict>
</plist>


 NVDANV50Hal.kext

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>CFBundleDevelopmentRegion</key>
    <string>English</string>
    <key>CFBundleExecutable</key>
    <string>NVDANV50Hal</string>
    <key>CFBundleGetInfoString</key>
    <string>NVDANV50Hal 7.4.10 270.05.05f01</string>
    <key>CFBundleIdentifier</key>
    <string>com.apple.nvidia.nv50hal</string>
    <key>CFBundleInfoDictionaryVersion</key>
    <string>6.0</string>
    <key>CFBundleName</key>
    <string>NVIDIA NV50 Resman Kernel Extension</string>
    <key>CFBundlePackageType</key>
    <string>KEXT</string>
    <key>CFBundleShortVersionString</key>
    <string>7.4.10</string>
    <key>CFBundleSignature</key>
    <string>????</string>
    <key>CFBundleVersion</key>
    <string>7.0.4</string>
    <key>IOKitPersonalities</key>
    <dict>
        <key>NVidiaRM</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>com.apple.nvidia.nv50hal</string>
            <key>IOClass</key>
            <string>NVDANV50HAL</string>
            <key>IOMatchCategory</key>
            <string>IOService</string>
            <key>IOPCIPrimaryMatch</key>
            <string>
0x061410de
                0x00f010de&amp;0xfff0ffff
                0x019010de&amp;0xfff0ffff
                0x040010de&amp;0xfff0ffff
                0x042010de&amp;0xfff0ffff
                0x05e010de&amp;0xfff8ffff
                0x05f010de&amp;0xfff0ffff
                0x060010de&amp;0xffe0ffff
                0x062010de&amp;0xffe0ffff
                0x064010de&amp;0xffe0ffff
                0x06e010de&amp;0xfff0ffff
                0x086010de&amp;0xffe0ffff
                0x08a010de&amp;0xffe0ffff
                0x0a2010de&amp;0xffa0ffff
                0x0ca010de&amp;0xffe0ffff
            </string>
            <key>IOProbeScore</key>
            <integer>60000</integer>
            <key>IOProviderClass</key>
            <string>IOPCIDevice</string>
        </dict>
    </dict>
    <key>OSBundleCompatibleVersion</key>
    <string>1.2.0</string>
    <key>OSBundleLibraries</key>
    <dict>
        <key>com.apple.NVDAResman</key>
        <string>1.2.0</string>
        <key>com.apple.kpi.iokit</key>
        <string>9.0.0</string>
        <key>com.apple.kpi.libkern</key>
        <string>9.0.0</string>
    </dict>
    <key>OSBundleRequired</key>
    <string>Safe Boot</string>
</dict>
</plist>


6. Now reset the kext ownership and permissions and re-create the kernelcache....

Open Terminal and type:

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

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

IOKitPersonalities_i386.ioplist.gz
IOKitPersonalities_x86_64.ioplist.gz
kernelcache
KextPropertyValues_OSBundleHelper_i386.plist.gz
KextPropertyValues_OSBundleHelper_x86_64.plist.gz

7. Reboot.....


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

#3
verdant
Posted 29 July 2011 - 11:11 PM

verdant

    InsanelyMac V.I.P.

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

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

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


The modifications described below are what work 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 790i MOBO and a 680i MOBO.....

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

For gaining a clearer understanding of DSDT.aml modification procedures, be prepared to do a lot of reading in the DSDT Forum.....starting with MaLd0n's DSDT Auto-Patcher topic........this a very helpful approach (credit to el coniglio, who did the hard work writing the app) for those lacking the knowledge and/or confidence and/or time to manually do what DSDT Auto-Patcher does....... :)

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

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

A modified DSDT.aml is required to fix the CMOS reset bug 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 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:

Quote

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://forum.insanel...owtopic=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 need Leopard running on the PC onto which you plan to install Snow Leopard...or Snow Leopard running on the PC onto which you plan to install OS X Lion.....


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 Windows,  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:

Quote

GP49,   8
  }

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


  The DTGP Method patch needs to be inserted 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/ and 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.0 RC5 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

To enable native power management 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 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 DSDT.aml file has to have a LPC patch inserted as explained below:

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. Since the LPC bus has replaced the ISA bus, download and install Evosx86 Team's  Snow Leopard x64 version of the UNIX lspci utility, 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: Attached File  LPC_injector.kext.zip   2.33K   55 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 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 (0x02)
{
"device-id",
Buffer (0x04)
{
0xAE, 0x0A, 0x00, 0x00
}
}, Local0)
DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
Return (Local0)
}

Method (^_INI, 0, NotSerialized)


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


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
)
})
}

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

Construction on hold until more DSDT mods added...... :construction:

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

#4
verdant
Posted 30 July 2011 - 12:17 AM

verdant

    InsanelyMac V.I.P.

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

OS X Lion Installation / Boot / Operation Issues

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


Note: I will indicate if I have experienced any of these issues with a * in front of Issue, and hence will say which if any of the proposed solutions have worked for me......

If there is no * then because I may not be able to generate or replicate the issue on my system, I cannot vouch that any of the proposed solutions will work for you.......


Issue 1. [PCI configuration begin] bootup error


Some OSx86 / Hackintosh users see the following error when trying to install OS X Lion (note: some users have had the same issue after updating to version 10.6.8):

'MAC Framework successfully initialised using 16384 Buffer headers and 10240 cluster IO Buffer headers
IOAPIC: Version 0x20 Vectors 64:87
ACPI: System State [s0 s3 s4 s5] (s3)
PFM64 0xF10000000 0xF10000000
[PCI Configuration begin]'

the key element being the appearance of [PCI Configuration begin] on screen, followed by a freeze.....

However, regarding the  [PCI Configuration begin] problem, there are two distinct issues with different solutions:

Case 1. Computer freeze at PCI Bus Start message, [PCI Configuration begin].....

The apparent solution is given by THe KING in the Project OS X Forum in the Hp/compaq Mini 311, HP/Compaq Mini 311 Development topic (post #328)......it involves a DSDT mod......the _BBN method must be removed from the PCI0 device and added to the IXVE bridge and root ports, and FakeSMC plugins removed too.....

Case 2. There is a display freeze after "PCI Configuration Begin" but booting continues with a problem until the Desktop shows, meaning that you can no longer use Single User Mode nor follow the boot process in verbose mode.......nor see anything else onscreen until the Desktop appears......

Here in Issue 1. I am dealing with Case 2......

There are various proposed solutions, which I will list in order of being easiest to try:


Solution 1: Modify org.chameleon.Boot.plist

Insert npci=0x2000 (or if that does not work, try npci=0x3000) into Kernel Flags string of org.chameleon.Boot.plist in /Extra of the USB flash drive installer (and of the target OS X Lion HDD volume if the same problem is found to occur when later booting from the OS X Lion HDD volume).

Change Kernel Flags of org.chameleon.Boot.plist

<key>Kernel Flags</key>
<string>-v arch=x86_64</string>[/code]

to

<key>Kernel Flags</key>
<string>-v arch=x86_64 npci=0x2000</string>


Solution 2: Rollback 10.7 AppleACPIPlatform.kext and IOPCIFamily.kext to the 10.6.7 versions

1. Copy the 10.6.7 AppleACPIPlatform.kext and IOPCIFamily.kext to your Desktop

2. In Terminal type:

sudo mv /System/Library/Extensions/AppleACPIPlatform.kext /System/Library/Extension /AppleACPIPlatform.kext.orig
							  
 sudo mv sudo mv /System/Library/Extensions/IOPCIFamily.kext /System/Library/Extensions/IOPCIFamily.kext.orig
 exit

                    3. Then type 
sudo -s
at the $ prompt and at the resulting bash-3.2# prompt, type:

cp -R /Users/"User Name"/Desktop/AppleACPIPlatform.kext /System/Library/Extensions/
 chown -R root:wheel /System/Library/Extensions/AppleACPIPlatform.kext 
 chmod -R 755 /System/Library/Extensions/AppleACPIPlatform.kext
												 
 cp -R /Users/"User Name"/Desktop/IOPCIFamily.kext /System/Library/Extensions/
 chown -R root:wheel /System/Library/Extensions/IOPCIFamily.kext 
 chmod -R 755 /System/Library/Extensions/IOPCIFamily.kext 
												 
 touch /System/Library/Extensions
 exit


and back at the $ prompt, to force the next sudo command to be reauthenticated via a password check, type

sudo -k
 exit


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

IOKitPersonalities_i386.ioplist.gz
IOKitPersonalities_x86_64.ioplist.gz
kernelcache
KextPropertyValues_OSBundleHelper_i386.plist.gz
KextPropertyValues_OSBundleHelper_x86_64.plist.gz

and then reboot.....

Alternatively, you can use janek202's Kext Wizard for a Terminal-free life.......


Solution 3: Install Oleg's v2 Patched IOPCIFamily.kext

1. Download Oleg's v2 of his patched IOPCIFamily.kext : Attached File  IOPCIFamilyv2.kext.zip   130.25K   61 downloads onto your Desktop and install it as follows:

2. In Terminal type:

sudo mv /System/Library/Extensions/IOPCIFamily.kext /System/Library/Extensions/IOPCIFamily.kext.orig
 exit

                    3. Then type 
sudo -s
at the $ prompt and at the resulting bash-3.2# prompt, type:

  
cp -R /Users/"User Name"/Desktop/IOPCIFamily.kext /System/Library/Extensions/
 chown -R root:wheel /System/Library/Extensions/IOPCIFamily.kext
 chmod -R 755 /System/Library/Extensions/IOPCIFamily.kext
 touch /System/Library/Extensions
 exit


and back at the $ prompt, to force the next sudo command to be reauthenticated via a password check, type

sudo -k
 exit


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

IOKitPersonalities_i386.ioplist.gz
IOKitPersonalities_x86_64.ioplist.gz
kernelcache
KextPropertyValues_OSBundleHelper_i386.plist.gz
KextPropertyValues_OSBundleHelper_x86_64.plist.gz

  and then reboot.....
  
  Alternatively, you can use janek202's Kext Wizard for a Terminal-free life.......
  

Solution 4: Install nawcom's EvilIOPCIFamily.kext and EvilAppleACPIPlatform.kext

Download nawcom's two kexts onto your Desktop and install them into /Extra/Extensions/ by 'dragging and dropping' Attached File  legacy_kexts_by_nawcom.zip   488.26K   51 downloads

If that does, not work then try with them installed in /System/Library/Extensions/

type 
sudo -s
at the $ prompt and at the resulting bash-3.2# prompt, type:

cp -R /Users/"User Name"/Desktop/EvilIOPCIFamily.kext /System/Library/Extensions/
 chown -R root:wheel /System/Library/Extensions/EvilIOPCIFamily.kext
 chmod -R 755 /System/Library/Extensions/EvilIOPCIFamily.kext
												 
 cp -R /Users/"User Name"/Desktop/EvilAppleACPIPlatform.kext /System/Library/Extensions/
 chown -R root:wheel /System/Library/Extensions/EvilAppleACPIPlatform.kext
 chmod -R 755 /System/Library/Extensions/EvilAppleACPIPlatform.kext
												 
 touch /System/Library/Extensions
 exit


and back at the $ prompt, to force the next sudo command to be reauthenticated via a password check, type

sudo -k
 exit


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

IOKitPersonalities_i386.ioplist.gz
IOKitPersonalities_x86_64.ioplist.gz
kernelcache
KextPropertyValues_OSBundleHelper_i386.plist.gz
KextPropertyValues_OSBundleHelper_x86_64.plist.gz

and then reboot.....

Alternatively, you can use janek202's Kext Wizard for a Terminal-free life.......


Solution 5: Patch your DSDT.aml file

Some propose replacing Name (_ADR, Zero) with Name (_UID, Zero), while some propose adding Name (_ADR, Zero) before Name (_UID, Zero), below:

Device (PCI0)
{
    Name (_HID, EisaId ("PNP0A08"))
    Name (_CID, EisaId ("PNP0A03"))
    Name (_ADR, Zero)

but before
    
Name (_BBN, Zero)

to give

    Name (_HID, EisaId ("PNP0A08"))
     Name (_CID, EisaId ("PNP0A03"))
     Name (_ADR, Zero)
     Name (_UID, Zero)
    Name (_BBN, Zero)

rather than

    Name (_HID, EisaId ("PNP0A08"))
     Name (_CID, EisaId ("PNP0A03"))
     Name (_UID, Zero)
    Name (_BBN, Zero)

However, it is it is interesting to note that I have never experienced the [PCI Configuration begin] error with my Asus P5N32E SLI Plus (nForce 650i) MOBO, in either 10.6.8, or when installing OS X Lion 10.7, or when booting OS X Lion 10.7 on the HDD......and, that my DSDT.aml Device (PCI0) entry reads as follows:

        Device (PCI0)
        {
            Name (_HID, EisaId ("PNP0A08"))
            Name (_CID, EisaId ("PNP0A03"))
            Name (_ADR, Zero)
            Name (_UID, One)
            Name (_BBN, Zero)
            Name (PCIA, Zero)
            Method (_REG, 2, NotSerialized)
            {
                If (LEqual (Arg0, 0x02))
                {
                    Store (Arg1, PCIA)
                }
            }

and in my DSDT.aml is placed after

        Device (PWRB)
        {
            Name (_HID, EisaId ("PNP0C0C"))
            Method (_STA, 0, NotSerialized)
            {
                Return (0x0B)
            }
        }

and before

            OperationRegion (BRCR, PCI_Config, 0xA4, 0x04)
            Scope (\)
            {
                Field (\_SB.PCI0.BRCR, ByteAcc, NoLock, Preserve)
                {
                    GPUB,   32
                }
            }

            Device (MBIO)

Note that it contains both  Name (_UID, One) and not Name (_UID, Zero)....so, it may be worth you trying either:

        Device (PCI0)
         {
             Name (_HID, EisaId ("PNP0A08"))
             Name (_CID, EisaId ("PNP0A03"))
             Name (_ADR, Zero)
             Name (_UID, Zero)
             Name (_BBN, Zero)

or

        Device (PCI0)
         {
             Name (_HID, EisaId ("PNP0A08"))
             Name (_CID, EisaId ("PNP0A03"))
             Name (_ADR, Zero)
             Name (_UID, One)
             Name (_BBN, Zero)

To do the DSDT.aml patching you can use EVOSx86 Team's DSDTSE on OS X or Windows,  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......


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

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


Solution 1: Setting up an Ethernet device-properties string in org.chameleon.boot.plist

1. Boot into 64bit Snow Leopard system and run EFIStudio v1.1 (if not installed then download) and select Ethernet in 'Select Device' in place of Display:

Attached File  EFIStudio_V1.1_Ethernet.png   42.48K   119 downloads

2. With the the following highlighted under Device Type | Device Path

Ethernet      PciRoot(0x1)/.......

click on the Add Device button alongside 'Add your device:' and you should see the following Editor window appear:
Attached File  EFIStudio_Ethernet_Device.png   43.55K   127 downloads
which you should leave open.

3. Then click on the Save hex button to save the hexadecimal output in the bottom half of the Editor window to your chosen backup directory/folder, and then click on the Save XML window to save the XML output in the top half of the Editor window to the same chosen backup directory/folder (note they are equivalent).

4. Open org.chameleon.Boot.plist using your favourite your preferred Text Editor app; e.g.Text Edit, TextMate, TextWrangler, Property List Editor, or PlistEdit Pro etc. and then:

[1] Change

    <key>EthernetBuiltIn</key>
    <string>Yes</string>

to

    <key>EthernetBuiltIn</key>
    <string>No</string>

[2] Add the following entry

    <key>device-properties</key>
    <string>4b00000001000000010000003f0000000100000002010c00d041030a0100000001010600000f01.....</string>

and then between <string> and </string> add the hexadecimal string that you can copy from the bottom half of the open Editor window.......

For example, the following string:

4b00000001000000010000003f0000000100000002010c00d041030a0100000001010600000f01
01060000077fff0400160000006200750069006c0074002d0069006e0000000500000001

is equivalent to:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">
<plist version="1.0">
    <dict>
    <key>PciRoot(0x1)/Pci(0xf,0x0)/Pci(0x7,0x0)</key>
        <dict>
        <key>built-in</key>
        <string>0x01</string>
        </dict>
</dict>
</plist>

This solution is reported to solve both App Store and FaceTime issues.....


Solution 2: Adding Device LAN0 patch to your DSDT.aml (Under construction and testing....)

1. Boot into 64bit Snow Leopard system and run IORegistryExplorer (if not already available, then download and install XCode, then look in Developer folder in / directory, and go to Applications >>>> Utilities) and enter LAN in the Search box:
Attached File  IORegistryExplorer.png   113.33K   113 downloads

2. Search your dsdt.dsl or dsdt.aml files for the Device (XXXXX) sections containing your LAN Devices.....in this example, Device (MMAC) and Device (MAC1):

 Device (MMAC)
{
Name (_ADR, 0x00110000)
Name (_PRW, Package (0x02)
{
0x0B,
0x05
})
}

Device (MAC1)
{
Name (_ADR, 0x00120000)
Name (_PRW, Package (0x02)
{
0x0A,
0x05
})
}

which are within the Device (PCI0) section......

3. Now depending on which LAN port you connect to the internet with, you should change, in this example, either Device (MMAC) or Device (MAC1) to Device (LAN0) and insert the following patch after Name (_ADR, 0x00110000) or Name (_ADR, 0x00120000), respectively:

Name (_PRW, Package (0x02)
{
0x09,
0x03
})
Method (_DSM, 4, NotSerialized)
{
Store (Package (0x02)
{
"location",
Buffer (0x02)
{
"1"
}
}, Local0)
DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
Return (Local0)
}

giving in the case of Device (MMAC):

            Device (LAN0)
            {
                Name (_ADR, 0x00110000)
                Name (_PRW, Package (0x02)
                {
                    0x09,
                    0x03
                })
                Method (_DSM, 4, NotSerialized)
                {
                    Store (Package (0x02)
                        {
                            "location",
                            Buffer (0x02)
                            {
                                "1"
                            }
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }
            }
4. Now change all remaining occurrences of MMAC in the DSDT.aml file to LAN0, i.e. change

            Notify (\_SB.PCI0.MMAC, 0x02)

to

            Notify (\_SB.PCI0.LAN0, 0x02)


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

#5
verdant
Posted 30 July 2011 - 12:55 AM

verdant

    InsanelyMac V.I.P.

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

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

GETTING AUDIO WORKING IN LION

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


This guide will hopefully include in time, more reports of successful attempts to get different audio chipsets/codecs working on different nForce chipset + Intel CPU MOBOs.........but I am starting with what enables audio on my Asus P5N32-E SLI Plus MOBO......

1.   Audio through the Analog Devices AD1988B  8-Channel  High Definition Audio CODEC on the Asus SupremeFX II  Audio Card via DSDT Modding:

To enable sound from the Asus SupremeFX audio card in Lion.....except for the Front Panel Headphones port and the Front Microphone port......requires the following:

[1] Putting the AD1988b.Fix.kext in /Extra/Extensions/

The AD1988b.Fix.kext is a pseudo-kernel extension i.e. a pseudo-kext (as it contains only an Info.plist file) and is based on the AD2000b kext by THe KiNG as modified by Phoenix Wright in the  Project OSX Forum that no longer gives the single "sound assertion"  error) but with the AD1998b CodecID 299112843 inserted by me (it is included in my Lion_Support_Files_v1.0..........go to post #1 to download for a download link).

[2] The DTGP Method Patch inserted into the DSDT.aml file

The DTGP Method Patch enables the use of other patches in your DSDT.aml file.

To patch your DSDT.aml file, you can use EVOSx86 Team's DSDTSE on OS X or Windows,  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......

I have posted THe KiNG's generic audio (i.e. HDEF) HDAEnabler DSDT patch which should work for all audio codecs (and indeed works for me):

Quote

Method (_DSM, 4, NotSerialized)
                {
                    Store (Package (0x04)
                        {
                            "layout-id",
                            Buffer (0x04)
                            {
                                0x0C, 0x00, 0x00, 0x00
                            },

                            "PinConfigurations",
                            Buffer (Zero) {}

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


and his modified HDAEnabler patch for nForce MOBOs (which I use with the AD1988b.Fix.kext):

                

Quote

Method (_DSM, 4, NotSerialized)
                {
                    Store (Package (0x08)
                        {
                            "subsystem-id",
                            Buffer (0x04)
                            {
                                0x79, 0xCB, 0x00, 0x00
                            },

                            "subsystem-vendor-id",
                            Buffer (0x04)
                            {
                                0xDE, 0x10, 0x00, 0x00
                            },

                            "layout-id",
                            Buffer (0x04)
                            {
                                0x0C, 0x00, 0x00, 0x00
                            },

                            "PinConfigurations",
                            Buffer (Zero) {}
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }


which requires that any BuiltIn entry in the legacy i.e. Info.plist-only kext is removed.......

In the as-yet non-audio patched "CMOS reset fix" patched DSDT.aml file for my Asus P5N32-E SLI Plus MOBO, you will see near to the top of the dsdt.dsl file:

  

Quote

GP49,   8
      }

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

  where the DTGP method patch needs to be inserted between Name (OSFL, 0x01) and Method (STRC, 2, NotSerialized).

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

Quote

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] THe HDEF Method i.e. HDAEnabler Patch inserted in the DSDT.aml file

Scroll down to around the middle of the dsdt.dsl file:
  
    

Quote

Device (AZAD)
              {
                  Name (_ADR, 0x000F0001)
                  Name (_PRW, Package (0x02)
                  {
                      0x15,
                      0x05
                  })
              }

              Device (MMAC)
  
    where the lines in red need to be replaced with the _DSM patch......

You need to search your DSDT for the presence of either Device (AZA) or  Device (AZAL) or Device (AZAD) and replace AZA, AZAL, or AZAD with  HDEF, giving Device (HDEF) and insert the HDEF patch.

  In my Asus P5N32E SLI Plus MOBO's DSDT, the audio device address is  _ADR,  0x000F0001.......BUT your _ADR value here may be different, so find the Name (_ADR, "your _ADR value").......REMEMBER TO KEEP the line Name (_ADR, "your _ADR value") in the DSDT....

  If the device is not present, it must be added......according to THe  KiNG, in most other cases the audio device is apparently in DSDT on  _ADR 0x001B0000 and the device is often named Device (AZAL)......or  Device (AZA).   

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

    Device (HDEF)
                {
                    Name (_ADR, 0x000F0001)
                    Method (_DSM, 4, NotSerialized)
                    {
                    Store (Package (0x04)
                    {
                    "layout-id",
                    Buffer (0x04)
                    {
                    0x0C, 0x00, 0x00, 0x00
                    },

                    "PinConfigurations",
                    Buffer (Zero) {}

                    }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                    }    
                }
  
                Device (MMAC)                                      

[4] Replacement of all other occurrences of AZA, AZAL, or AZAD  with HDEF

Replace XXXX where XXXX is AZA, AZAL, or AZAD  with HDEF in "Notify (_SB.PCI0.XXXX, 0x02)" to give "Notify  (_SB.PCI0.HDEF, 0x02)"

[5] Confirming that in OS X Lion /System/Library/Extensions, the 10.7.0 AppleHDA.kext has been renamed via Terminal:

sudo mv /System/Library/Extensions/AppleHDA.kext /System/Library/Extension/AppleHDA.kext.1070_Orig

as AppleHDA.kext.1070_Orig, or similar......so that it becomes a folder in /S/L/E/

[6] Putting AppleHDA.1062.kext in /S/L/E/ (here it is: Attached File  AppleHDA1062Kext.zip   1.27MB   59 downloads  )  

[7] Re-setting /S/L/E/ kext ownership and permissions and forcing kernelcache recreation via Terminal by typing:

sudo chown -R 0:0 /System/Library/Extensions
	sudo chmod -R 755 /System/Library/Extensions
	sudo touch /System/Library/Extensions


[8] Rebooting.....and audio should now be working......

To show that audio is now working (except for Front Panel Headphones port and Front Microphone port):

Attached File  System_Information_Audio_Report.png   35.67K   68 downloads Attached File  Sound_Effects.png   59.8K   75 downloads
Attached File  Sound_Output.png   55.69K   72 downloads Attached File  Sound_Input.png   52.85K   60 downloads
Attached File  Audio_Devices_Input.png   69.69K   58 downloads Attached File  Audio_Devices_Output.png   73.45K   48 downloads

However, while the rear port picks up a microphone signal, it has a  low sensitivity......

Fortunately for me, this approach continues to work for the Analog Devices AD1988B codec in OS X Lion 10.7.1....... :)

All I had to do was roll back to the AppleHDA.kext from OS X 10.6.2 because the Apple Lion Update 10.7.1 (Client) installs a 10.7.1 version of the AppleHDA.kext, so I renamed the 10.7.1 AppleHDA.kext using Terminal to AppleHDA.kext.1071_Orig, making it a folder in /System/Library/Extensions/ :

sudo mv /System/Library/Extensions/AppleHDA.kext /System/Library/Extension/AppleHDA.kext.1071_Orig



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

2.   Audio through the Analog Devices AD1988B  8-Channel  High Definition Audio CODEC on the Asus SupremeFX II  Audio Card via oldnapalm's patched (for AD1988B 7.1) VoodooHDA.kext v2.7.2 Snow Leopard/Lion:

See here...... :) The results of oldnapalm's original version VooddoHDA.kext for AD1988B on my Asus P5N-32E SLI Plus MOBO and Asus SupremeFX II Audio Card are: No sound assertions on boot but I do get a 'pop' sound.....

No Built-in Audio in System Information

but  I do get sound, with working volume slider and can mute / unmute but  get a 'pop' sound doing it......also, decreasing the slider (volume)  to minimum (zero) volume causes a 'pop' sound and increasing slowly  generates a 'pop' just above zero level but increasing it quickly to  75% volume generates a 'pop' sound before going to 100% volume..... System Preferences displays:

Sound Output

- Line-out (green rear) - working
- Line-out (black rear) - not tested
- Line-out (orange rear) - not tested
- Line-out (grey rear) - not tested
- SPDIF-out (rear) - not tested

Sound Input

- Microphone (pink rear) - not tested
- Microphone (pink front)
- Line-in (blue rear) - not tested

Not working - Headphones (green front)
Not working - Microphone auto-detect (have to select between rear and front in preferences)           

As far as oldnapalm is aware, the "pop" sound on startup/shutdown and mute/unmute cannot be fixed by plist editing.....

However, setting a different default association of 0x02214050 for node 17 in the VoodooHDA.kext Info.plist file has enabled the front green port for headphones but not with autodetect.....

 <dict>
         <key>Codec</key>
         <integer>0</integer>
         <key>Config</key>
         <string>0x02214050</string>
         <key>Node</key>
         <integer>17</integer>
</dict>

My System Preferences then displays:

Sound Output:

- Line-out (green rear) - working via manual selection in sound prefs
- Headphones (green front) - working via manual selection in sound prefs
- Line-out (orange rear) - not tested
- Line-out (grey rear) - not tested
- SPDIF-out (rear) - not tested

Sound Input:

- Microphone (pink rear) - not tested fully as not convenient to use
- Microphone (pink front) - working via manual selection in sound prefs
- Line-in (blue rear) - not tested

Despite the sound 'pops' on on startup/shutdown and mute/unmute, having both the Front Headphones (green front) and the Front Microphone (pink front) working via manual selection in Sound Preferences is very useful should you want to use FaceTime and/or Skype etc..... :)
  

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

3.   Audio through the Realtek ALC885/889a 7.1+2 Channel High Definition Audio Codec via DSDT Modding:

To  enable sound from the Realtek ALC885 (but also ALC889a) in Lion.....including  the Front Panel audio......requires the following Device (HDEF) patch in your DSDT.aml file and the AppleHDA.kext (1.7.9a4), which is the OS X Snow Leopard 10.6.2 version

Attached File  AppleHDA.kext.zip   1.29MB   101 downloads and LegacyHDA.kext Attached File  LegacyHDA.kext.zip   7.77K   99 downloads

All thanks for this solution goes to abhilash who had been trying from the release of the Lion OS Developer Preview to get audio working in OS X Lion on his XFX nForce 680i LT SLI MOBO...... :)

1. abhilash Device (HDEF) patch:

Device (HDEF)
            {
                Name (_ADR, 0x000F0001) <------ Your _ADR value here may be different
                Method (_DSM, 4, NotSerialized)
                {
                    Store (Package (0x0A)
                        {
                            "built-in",
                            Buffer (One)
                            {
                                0x01
                            },

                            "codec-id",
                            Buffer (0x04)
                            {
                                0x85, 0x08, 0xEC, 0x10
                            },

                            "layout-id",
                            Buffer (0x04)
                            {
                                0x75, 0x03, 0x00, 0x00
                            },

                            "device-type",
                            Buffer (0x12)
                            {
                                "Realtek ALC889A"
                            },

                            "PinConfigurations",
                            Buffer (0x28)
                            {
                                /* 0000 */    0x10, 0x90, 0xA1, 0x01, 0x20, 0x90, 0xA1, 0x02,
                                /* 0008 */    0x80, 0x30, 0x81, 0x01, 0x90, 0x40, 0x21, 0x02,
                                /* 0010 */    0x30, 0x40, 0x11, 0x01, 0x40, 0x40, 0x01, 0x01,
                                /* 0018 */    0x50, 0x60, 0x01, 0x01, 0x60, 0x20, 0x01, 0x01,
                                /* 0020 */    0x70, 0x61, 0x4B, 0x01, 0xA0, 0x01, 0xCB, 0x01
                            }
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }

                Name (_PRW, Package (0x02)
                {
                    0x0D,
                    0x03
                })
            }

You need to search your DSDT for the presence of either Device (AZA) or Device (AZAL) or Device (AZAD) and replace AZA, AZAL, or AZAD with HDEF, giving Device (HDEF) and insert the HDEF patch.
If the device is not  present, it must be added......according to THe KiNG, in most other  cases the audio device is apparently in DSDT on _ADR 0x001B0000 and the  device is often named Device (AZAL)......or Device (AZA).

In abhilash's DSDT, the audio  device has this address: _ADR, 0x000F0001.....BUT your _ADR value here may be different, so find the Name (_ADR, "your _ADR value").......REMEMBER TO KEEP the line Name (_ADR, "your _ADR value") in the DSDT...

Replace all other other occurrences of AZA, AZAL, or AZAD in your DSDT.aml file with HDEF, e.g. replace XXXX, where XXXX is AZA, AZAL, or AZAD,  with HDEF in "Notify (_SB.PCI0.XXXX, 0x02)" to give "Notify  (_SB.PCI0.HDEF, 0x02)"

2. Install the OS X Snow Leopard v10.6.2 AppleHDA.kext (1.7.9a4) in /System/Library/Extensions/ and the repair the Extensions ownership and permissions and kernelcache recreation via Terminal by typing:

sudo chown -R 0:0 /System/Library/Extensions
	sudo chmod -R 755 /System/Library/Extensions
	sudo touch /System/Library/Extensions


3. Install LegacyHDA.kext in /Extra/Extensions/

4. Reboot and check in System report, OS X top menu bar (Loudspeaker should be 'black' not 'gray' and the volume slider should work) and System Preferences >>>> Sound to check that your audio is fully functioning.....

Attached File  sound.png   77.31K   74 downloads Attached File  input.png   57.59K   62 downloads Attached File  output.png   55.23K   43 downloads

Instead of abhilash's LegacyHDA.kext in /Extra/Extensions/, you can use the iLeopod  Info.plist-only ALC885.kext in /Extra/Extensions/......compared  withthis ALC885 llegacy kest, LegacyHDA has BuiltinHDA addition and  configdata is different.

  Here it is:   iLeopod_ALC885.kext.zip ( 7.78K )  Number of downloads: 8
  iLeopod's  update:  ALC885.kext_test.zip ( 8.65K )  Number of downloads: 2

  With this updated version, iLeopod says that hot-plugging should work  via auto-detect like before. Try if front mic is working maybe Built in  HDA its he solution for that (not yet added).    
  
  Should you see the following when booting up:

  

Quote

Kext com.apple.driver.AppleHDAController might not load - kextd is currently unavailable.
  Sound assertion "0 == pciVendorProductID" failed in  "/SourceCache/AppleHDA/AppleHDA-179.1.4/AppleHDAController/AppleHDAController.cpp"  at line 2682 goto Exit

  this sound assertion issue can be solved, according to iLeopod, by adding one of these subsystem ids to Device (HDEF) in your DSDT:    
  
      

Quote

"subsystem-id",
Buffer (0x04)
{
0x79, 0xCB, 0x00, 0x00
},

"subsystem-vendor-id",
Buffer (0x04)
{
0xDE, 0x10, 0x00, 0x00
},
    

  or
  
  

Quote

"subsystem-id",                            
Buffer (0x04)                            
{                              
0xA0, 0x00, 0x00, 0x00                          
},

"subsystem-vendor-id",                            
Buffer (0x04)                            
{                                
0x6B, 0x10, 0x00, 0x00                            
},


  The first version is preferred by iLeopod.......
  
  Be careful with Store (Package (0x08) entry of Device (HDEF).......just  remove the numbers and let the DSDT compiler deal with it......like  this:

Quote

Store (Package ()

giving as shown in iLeopod's Device (HDEF) section:

Device (HDEF)
            {
                Name (_ADR, 0x000F0001)  <------ Your _ADR value here may be different
                Method (_DSM, 4, NotSerialized)
                {
                    Store (Package ()
                        {

                            "built-in",
                            Buffer (One)
                            {
                                0x00
                            },
                            
                          
                            "subsystem-id",
                            Buffer (0x04)
                            {
                                0x79, 0xCB, 0x00, 0x00
                            },

                            "subsystem-vendor-id",
                            Buffer (0x04)
                            {
                                0xDE, 0x10, 0x00, 0x00
                            },

                          
                            "codec-id",
                            Buffer (0x04)
                            {
                                0x85, 0x08, 0xEC, 0x10
                            },

                            "platformFamily",
                            Buffer (One)
                            {
                                0x00
                            },

                            "layout-id",
                            Buffer (0x04)
                            {
                                0x75, 0x03, 0x00, 0x00
                            },

                            "device-type",
                            Buffer (0x0F)
                            {
                                "Realtek ALC885"
                            },

                            "PinConfigurations",
                            Buffer (Zero) {}
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }

                Name (_PRW, Package (0x02)
                {
                    0x0D,
                    0x03
                })
            }

            }


  N.B. According to abhilash, sound is not working with AppleHDA.kext version 10.6.7 (1.9.9f12) plus LegacyHDA or ALC885.......

I have noted the following:

AppleHDA version 10.6.2 = 1.7.9a4
AppleHDA version 10.6.3 = 1.8.4fc3
AppleHDA version 10.6.4 = 1.8.7f1
AppleHDA version 10.6.5 = 1.9.9f12
AppleHDA version 10.6.6 = 1.9.9f12
AppleHDA version 10.6.7 = 1.9.9f12
AppleHDA version 10.6.8 = 2.0.5f13/f14
AppleHDA version 10.7.0 = 2.1.1f11
AppleHDA version 10.7.1 = 2.1.1f12
  
  VCH888 has posted in his ALC889A (Gigabyte, Intel) topic here, that getting working sound in 10.6.8 and 10.7.x only requires putting his ALC885_889a.kext Info.plist-only kext in /S/L/E and copying layout885.xml  and Platforms.xml into the 10.7.x AppleHDA.kext, or AppleHDA.kext version  2.0.0 or higher (in /S/L/E/) Resources folder......but that method (replacing  LegacyHDA/ALC885 with ALC885_889a) is not working for abhilash on his nforce MOBO.......

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

N. B. iLeopod has posted some interesting information about the AppleHDA.kext.....

Quote

Interesting fact that that some boards Have Audio codec  with address 2 (Like the Gigabyte and original Apple ) and zero Like  mine and others. There are different Pros and Cons about using the old  open 10.6.2 AppleHDA (Open for All codecs, working Frontpanel) or a  later one (HDMI Audio for GFX with integrated HDMI audio). With codec  Address (first Number in pinconfig) 2 u can use the new AppleHDA. Using  the Lion Apple HDA is not recommend because there are a lot of sound  assertions and it take 1 min. or more till you hear sth.


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

Watch this section for further developments.......

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



#6
verdant
Posted 30 July 2011 - 02:56 AM

verdant

    InsanelyMac V.I.P.

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


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

How to Enable Natural Power Management ("vanilla SpeedStepping") in OS X Lion (and OS X Snow Leopard) 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 PatcherVersion 1.0.1e (also see post #3) because as well as extracting your original DSDT, it will also perform some basic fixes providing a good base for further DSDT modification: DSDT_Patcher1.0.1e.zip
Here is the DSDT Patcher Readme:

Quote

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://forum.insanel...owtopic=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

[4]  Modify the Device (HPET) section and insert the Device (LPCB) section into the DSDT.aml file as described in post #3 on Generating and Modifying the 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 #3 on Generating and Modifying the 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.0 RC5 r1191 or 1200, or even  later revision if it working 100% for you, when installing OS X Lion - you can if you wish download and use janek202's Chameleon Wizard to install a later revision etc……

[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 /Extra/Extensions/

[9] Reboot

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

Attached File  Info.png   17.28K   92 downloads Attached File  Status.png   31.39K   84 downloads Attached File  P_States.png   29.45K   61 downloads Attached File  Load_Test_Status.png   31.13K   79 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 universal binary.) Attached File  CPUTest.zip   378.45K   49 downloads

With thanks to aschar1, the mark-i application can also be used (32bit and 64bit mode): Attached File  mark_i.zip   333.56K   46 downloads

Quote

You can check if speedstepping is working with mark-i app (works in32bit and 64bit mode). Do not install the ringaccess.kext permanently in /S/L/E. Just kextload it in terminal.
download the attached zip file and unzip in a folder on your desktop.
in Terminal
a. type cd   then drag the folder with mark-i and ringacces.kext into the terminal  
b. in Terminal: sudo chown -R root:wheel ringaccess.kext
c. sudo chmod -R 755 ringaccess.kext
d. sudo kextload ringaccess.kext
e. start the mark-i app

Attached File  Mark_i_Idle.png   39.44K   139 downloads Attached File  Mark_i_Load.png   39.55K   109 downloads

#7
verdant
Posted 30 July 2011 - 09:29 AM

verdant

    InsanelyMac V.I.P.

  • Gurus
  • 5,398 posts
  • Gender:Male
  • Interests:At home, I have the following computers......
    >
    >
    >
*************************************************************
Resolving the "still waiting for root device" error message on bootup after updating to OS X Lion 10.7.2

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


To boot OS X 10.7.2 successfully, do the following:

1. Transfer ALL kexts in /Extra/Extensions/ to /System/Library/Extensions/, leaving /Extra/Extensions/ empty.

2. Modify your org.chameleon.Boot.plist file to include

<key>UseKernelCache</key>
  <string>Yes</string>

3. Reset /System/Library/Extensions/ kext ownership and permissions and force kernelcache re-creation via Terminal commands:

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

4. For good measure, manually delete the kernelcache and other cache files in /System/Library/Caches/com.apple.kext.caches/Startup/

5. Reboot into OS X 10.7.2.........and use Disk Utility to repair system permissions...... :)

BTW with 10.7.2, I am using Chameleon v2.1svn r1618........

#8
verdant
Posted 30 July 2011 - 06:00 PM

verdant

    InsanelyMac V.I.P.

  • Gurus
  • 5,398 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 AHCI Mode

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

2 port Serial ATA PHY for 1.5, 3.0 and 6.0GHz 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

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. The cards are showing up in System Report as follows: (I have added the numbers 1. to 4.fo clarity)

1. Unknown AHCI Standard Controller:
  Vendor: Unknown
  Product: AHCI Standard Controller
  Link Speed: 6 Gigabit
  Negotiated Link Speed: 3 Gigabit
  Description: AHCI Version 1.20 SupportedExternal Disk 0:
  Capacity: 1 TB (1,000,215,724,032 bytes)
  Model: External Disk 0						
  Revision: 1.157600
  Serial Number: AL25744_RogerDan_0_F
  Native Command Queuing: Yes
  Queue Depth: 32
  Removable Media: Yes
  Detachable Drive: No
  BSD Name: disk7
  Medium Type: Rotational
  Partition Map Type: MBR (Master Boot Record)
  S.M.A.R.T. status: Verified2. Unknown AHCI Standard Controller:
  Vendor: Unknown
  Product: AHCI Standard Controller
  Link Speed: 6 Gigabit
  Negotiated Link Speed: 3 Gigabit
  Description: AHCI Version 1.20 SupportedSAMSUNG HD103SJ:
  Capacity: 1 TB (1,000,204,886,016 bytes)
  Model: SAMSUNG HD103SJ						
  Revision: 1AJ10001
  Serial Number: S246J90ZB27616	
  Native Command Queuing: Yes
  Queue Depth: 32
  Removable Media: Yes
  Detachable Drive: No
  BSD Name: disk6
  Rotational Rate: 7200
  Medium Type: Rotational
  Partition Map Type: MBR (Master Boot Record)
  S.M.A.R.T. status: Verified3. Unknown AHCI Standard Controller:
  Vendor: Unknown
  Product: AHCI Standard Controller
  Link Speed: 6 Gigabit
  Negotiated Link Speed: 1.5 Gigabit
  Description: AHCI Version 1.20 SupportedTSSTcorp CDDVDW SH-S223B:
  Model: TSSTcorp CDDVDW SH-S223B			  
  Revision: SB02  
  Serial Number: 0j23454789ELMNOP  
  Native Command Queuing: No
  Removable Media: Yes
  Detachable Drive: No
  BSD Name: disk5
  Power Off: No
  Async Notification: No
  Partition Map Type: Unknown
  S.M.A.R.T. status: Not Supported4. Unknown AHCI Standard Controller:
  Vendor: Unknown
  Product: AHCI Standard Controller
  Link Speed: 6 Gigabit
  Negotiated Link Speed: 3 Gigabit
  Description: AHCI Version 1.20 SupportedSAMSUNG HD501LJ:
  Capacity: 500.11 GB (500,107,862,016 bytes)
  Model: SAMSUNG HD501LJ						
  Revision: CR100-10
  Serial Number: S0MUJ1MP852584	
  Native Command Queuing: Yes
  Queue Depth: 32
  Removable Media: Yes
  Detachable Drive: No
  BSD Name: disk8
  Medium Type: Rotational
  Partition Map Type: GPT (GUID Partition Table)
  S.M.A.R.T. status: Verified


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

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 "Unknown AHCI Standard Controller:" and "Vendor: Unknown".

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 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.2.0 in Windows, in order to create an MS-DOS bootable USB flash drive:



2. Download the following zipped folder:



3. Unzip it and you should see a folder called ASM1061, that contains the file 1b21-0611_v0951.exe
in a folder called v0.95.1 folder, which should extract to a file called 1b21-0611_v0951.bin, as well as a .zip file called asmedia_106_N095(www.station-drivers.com).zip, in a folder called v0.95, which should extract to a folder called asmedia_106_N095(www.station-drivers.com) containing:

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

4. Copy the contents of asmedia_106_N095(www.station-drivers.com) 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. Remove the file 106N095.BIN from the MS-DOS bootable flash drive and copy 1b21-0611_v0951.bin onto the the MS-DOS bootable flash drive

8. Repeat step 5. and step 6., and you should again see onscreen:

Asmedia 106x SATA Controller Ver 0.95 AHCI Mode

nevertheless you will have updated the ASM1061 firmware to revision 0.95.1


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
OMEGA_RAZER
Posted 31 July 2011 - 06:14 PM

OMEGA_RAZER

    InsanelyMac Protégé

  • Members
  • Pip
  • 25 posts
  • Gender:Male
  • Location:Ontario, Canada
Says it was deleted by the uploader so I'd say to expect a new version of the files. If you need them urgently though I put them up here.

verdant, if you would like me to remove these after you update please let me know and I will.

#10
verdant
Posted 31 July 2011 - 10:07 PM

verdant

    InsanelyMac V.I.P.

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

Sorry about the Download link going down.....it is up again..... :(

View PostOMEGA_RAZER, on Jul 31 2011, 07:14 PM, said:

Says it was deleted by the uploader so I'd say to expect a new version of the files. If you need them urgently though I put them up here.

verdant, if you would like me to remove these after you update please let me know and I will.

@ OMEGA_RAZER

Thanks for posting your link to help GTACRFreak when my download link was messed up....

You can remove your post and download link when I update to the next version after v1.0......

View PostGTACRFreak, on Jul 31 2011, 09:03 PM, said:

i din't found in you'r folder any DSDT.aml files.. and i don't know how to make some.. soo i just jumped over the step

@ GTACRFreak

There is no DSDT.aml file in my download folder because DSDT.aml files are MOBO specific......to generate your DSDT.aml file, see post #3 and see here.......

#11
verdant
Posted 31 July 2011 - 11:42 PM

verdant

    InsanelyMac V.I.P.

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

View PostGTACRFreak, on Aug 1 2011, 12:12 AM, said:

i Got the usb stick to boot.. Installation stops at:
[PCI Configuration begin] or something like that ;D (in verbose mode)



öhm.. Well i tried that program but nothing happened ;( (DSDT)

Since this thread is for nForce chipset + Intel CPU MOBOs, and you have a Asus P5Q Pro Turbo Intel P45 chipset MOBO, I will try to help you via PM......

#12
GTACRFreak
Posted 31 July 2011 - 11:45 PM

GTACRFreak

    InsanelyMac Protégé

  • Members
  • Pip
  • 48 posts
  • Gender:Male
Thx Verdant... it Worked... ;)
U'r are a good Helper :DD

#13
philby
Posted 02 August 2011 - 01:05 PM

philby

    InsanelyMac Protégé

  • Members
  • Pip
  • 9 posts
  • Gender:Male
  • Location:Mougins, France
Hi Verdant,

Many thanks for your great and detailed tutorial.
My Lion install is working great.

Now that I know it is working fine, I'll buy from Appstore.

Regards,

Philby

#14
verdant
Posted 02 August 2011 - 01:19 PM

verdant

    InsanelyMac V.I.P.

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

View Postphilby, on Aug 2 2011, 02:05 PM, said:

Hi Verdant,

Many thanks for your great and detailed tutorial.
My Lion install is working great.

Now that I know it is working fine, I'll buy from Appstore.

Regards,

Philby

Glad to help and that you found the guide detailed enough in terms of what to do step by step....... :)

It would be very helpful for me in keeping Part A. up to date, if you could please let me know what works or does not work for you when you attempt to purchase and download Lion from the App Store.....

It would also be good to see your system details in your signature......I am assuming you have an nForce chipset + Intel CPU MOBO......?

Cheers
verdant

#15
valyno
Posted 02 August 2011 - 03:07 PM

valyno

    InsanelyMac Protégé

  • Members
  • Pip
  • 29 posts
  • Gender:Male
  • Location:France
Hi Verdant,
first, thanks for this HUGE job you are doing for all of us...

[Noob Inside]

I am running a SL install updated to 10.6.8.
I am in the first stages of your tuto: Enabling the purchase of Lion on the AppStore...
For now, I have to:
- make the system to recognizemy CPU (Q6600) as a Xeon
- enable the 64 bits mode

For now, I can boot my system with the nForce123SATA*** cd-rom.
If I try to boot with other bootloaders, like Chameleon or iBoot, the system returns me "Still waiting for toor device..."
So my understanding is that since I need MeDevil's kext to handle properly my chipset and my SATA drives.
I canno't use the other bootloaders because the nForce kext is not present right?

I have installed the kexts you have selected for us with Kext Wizard in /S/L and in /E
However when I reboot, my SL is stll in 32 bits mode.
I suspect that it is because MeDevil's kext is already loaded, among others and it prevents the one freshly installed for 64 bit support to be loaded.

So my question is: can I modify the ISO file I use currently (nForce123...) and replace meDevil's kext with AppleNForceATA.imk64bit.kext, and do the same for the other kext that might be needed in the preboot.dmg along with the nForce kext, I will be able to load my system in 64 bits?

My ultimate goal being to have an EFI partition with the relevant kexts, but for now, I'll be happy to boot just with the CDROM..

I am reading a lot the various tutos in here to understand what is going on in the boot process and how to load the various required components, but sometimes, especially when you're not a computer engineer or software dev like me, it's a bit confusing...

Thanks again for the help...

Valyno

#16
verdant
Posted 02 August 2011 - 03:19 PM

verdant

    InsanelyMac V.I.P.

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

View Postvalyno, on Aug 2 2011, 04:07 PM, said:

Hi Verdant,
first, thanks for this HUGE job you are doing for all of us...

[Noob Inside]

I am running a SL install updated to 10.6.8.
I am in the first stages of your tuto: Enabling the purchase of Lion on the AppStore...
For now, I have to:
- make the system to recognizemy CPU (Q6600) as a Xeon
- enable the 64 bits mode

For now, I can boot my system with the nForce123SATA*** cd-rom.
If I try to boot with other bootloaders, like Chameleon or iBoot, the system returns me "Still waiting for toor device..."
So my understanding is that since I need MeDevil's kext to handle properly my chipset and my SATA drives.
I canno't use the other bootloaders because the nForce kext is not present right?

I have installed the kexts you have selected for us with Kext Wizard in /S/L and in /E
However when I reboot, my SL is stll in 32 bits mode.
I suspect that it is because MeDevil's kext is already loaded, among others and it prevents the one freshly installed for 64 bit support to be loaded.

So my question is: can I modify the ISO file I use currently (nForce123...) and replace meDevil's kext with AppleNForceATA.imk64bit.kext, and do the same for the other kext that might be needed in the preboot.dmg along with the nForce kext, I will be able to load my system in 64 bits?

My ultimate goal being to have an EFI partition with the relevant kexts, but for now, I'll be happy to boot just with the CDROM..

I am reading a lot the various tutos in here to understand what is going on in the boot process and how to load the various required components, but sometimes, especially when you're not a computer engineer or software dev like me, it's a bit confusing...

Thanks again for the help...

Valyno

Glad to help........ :)

It is going to take some time to complete the guide as I have do it in my very limited spare time within my "real life".......I was able to get Parts A. and B. out quickly because they are based on what I did to install Lion on my OSx86 PC........but people wanting a Lion CD/DVD installer and/or to install to an MBR HDD and/or install Lion to another volume from a running SL system etc. will have to be patient.......

To boot into 64bit mode you need to load AppleNForceATA.imk64bit.kext from /Extra/Extensions/ into the kernel......

So you need to have in /Extra/Extensions/ on your SL 10.6.8 HDD volume:

AppleNForceATA.imk64bit.kext
EvOreboot.kext or OpenHaltRestart.kext
FakeSMC.kext
NullCPUPowerManagement.kext or Disabler.kext

and you need to run the Chameleon 2.0 RC5 installer to install Chameleon on the HDD that  SL 10.6.8 is installed on.......

So is OS X SL 10.6.8 installed on its own HDD? Do you have Windows installed on another HDD in your PC?

To boot in 64bit mode and install OS X Lion:

1. I assume you are using my nForceSLBoot132DVD_for_SATA_DVDRW on DVD to boot SL.....?

If so, note that this Boot132DVD is using MeDevil's 32bit mode AppleNForceATA_TEST.kext which does not support more than 3GB RAM, requiring you to boot with maxmem=3072 or 2048 as a Chameleon boot flag.....

You should be aware that the required AppleNForceATA.imk64bit.kext will not support your two SATA DVDRWs........I recommend that you get a PATA (IDE) DVDRW that you jumper-set and connect to your MOBO as Master......the SATA DVDRWs are probably the main cause of your "Still waiting for root device" error problems.....

2. Temporarily remove your Creative Audigy Gamer sound card and your Asus WL-138 G v2 PCI WiFi card from your MOBO.....

#17
Kilopopo
Posted 02 August 2011 - 03:57 PM

Kilopopo

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 160 posts
verdant Hi,

I am following your guide using dp4 will your guide work with dp4

also does your tutorial install lion through an upgrade by clicking on the lion installer or do we have to boot to the installer partition to install lion?

im running 10.6.7 btw

thanks

I have not installed lion yet thanks

#18
valyno
Posted 02 August 2011 - 03:58 PM

valyno

    InsanelyMac Protégé

  • Members
  • Pip
  • 29 posts
  • Gender:Male
  • Location:France
Hi Verdant,

Thank you for your reply!!
I will follow your advices right away!!
V

#19
verdant
Posted 02 August 2011 - 04:05 PM

verdant

    InsanelyMac V.I.P.

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

View PostKilopopo, on Aug 2 2011, 04:57 PM, said:

verdant Hi,

I am following your guide using dp4 will your guide work with dp4

also does your tutorial install lion through an upgrade by clicking on the lion installer or do we have to boot to the installer partition to install lion?

im running 10.6.7 btw

thanks

I have not installed lion yet thanks

My guide is currently for a Mac OS X bootable USB OS X Lion Flash Drive Installer that you use to install OS X Lion to a blank Mac OS Extended (Journaled) volume on a GPT partitioned HDD.....

I have only personally tried my install procedure with the App Store downloaded OS X Lion app digital image file.......

#20
Kilopopo
Posted 02 August 2011 - 06:13 PM

Kilopopo

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 160 posts
Verdant
i Got the usb stick to boot.. Installation stops at:
[PCI Configuration begin] or something like that ;D (in verbose mode)
Back to OSx86 10.7 (Lion)



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

  1. InsanelyMac Forum
  2. → OSx86 Project
  3. → OSx86 Installation
  4. → OSx86 10.7 (Lion)
© 2013 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   Web hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy