nForce OS X Snow Leopard (10.6) RETAIL INSTALL GUIDE on a Series 6 or 7 nForce chipset / Intel CPU MOBO

artsin · November 6, 2009

Hi User,

German

Ich habe den Ruhezustand endlich auf dem Board Asus P5N-E SLI zum laufen bekommen . Ihr müst einfach nur die Treiber Installieren die ich ihr hochgeladen habe und dann noch ein paar Bios Einstellungen machen. Am besten wie ich auf eine anderen Partition erst Testen. Ich bin immer noch in der Test Phase, aber bis jetzt läuft es sehr gut. Vieleicht läuft es auch dann auf andere Board's. Ich Bitte um Feedback.

Der Ruhezustand geht nur wenn Snow Leopard auf einer IDE Platte Installiert ist. :thumbsup_anim:

Englisch

I finally got to sleep on the board Asus P5N-E SLI to run . It must be installed only the drivers that I've uploaded it and then make a few bios settings. Best as I only play on a different partition. I'm still in the testing phase, but so far it runs very well. Maybe it runs also on other's board. I am asking for feedback.

The sleep is only when Snow Leopard is installed on an IDE disk.

Asus_P5N-E_SLI.zip

/dsdt.aml

/Extra/com.apple.Boot.plist

/Extra/SMBIOS.plist

/System/Library/Extensions/AHCIPortInjector.kext

/System/Library/Extensions/AppleNForceATA.kext

/System/Library/Extensions/fakesmc.kext

/System/Library/Extensions/IOAHCIBlockStorageInjector.kext

/System/Library/Extensions/NullCPUPowerManagement.kext

/System/Library/Extensions/OpenHaltRestart.kext

/System/Library/Extensions/PlatformUUID.kext

/System/Library/Extensions/VoodooHDA.kext

Bios Setup

CPU Configuration

CPU Internal Thermal Control = Disable

Limit CPUID MaxVal = Disable

Enhanced C1 (C1E) = Disable

Execute Disable Bit = Enable

Enhanced Intel SpeedStepp = Disable

Onboard Divice Configuration

Onboard Lan = Disable

Onboard 1394 = Disable

JMicron SATA Controler = Disable

Asus_P5N_E_SLI.zip

artsin · November 7, 2009

German

Es Läuft jetzt in der IDE und S-ATA Variante. Es kommt leider noch sehr oft vor das der Ruhezustand erst nach ca. 2 Minuten aktiv wird. Darum Gedult haben.

Mein Test System:

Mobo : Asus P5N-E SLI

Speicher : 2 GB DDR2 SDRAM

Lan : Realtek 8139

GPU : NVIDIA GeForce 7600 GT 256 MB

CPU : Intel Core 2 Duo

Leider muss mann im Bios ein paar Sachen wie OnBoard Lan, OnBoard FireWire und JMicron S-ATA abschalten da sonst der Ruhezustand nicht geht. Darum ist es wichtig wenn mann den Ruhezustand nutzen will sich eine Externe Lan Karte zu besorgen. Die Treiber werde ich erst später nachreichen da ich noch was Testen möchte.

Englisch

It now expires in the IDE and S-ATA version. Unfortunately it happens very often before the rest of the state until after about 2 minutes is active. So have patience.

My test system:

Mobo : Asus P5N-E SLI

Memory : 2 GB DDR2 SDRAM

Lan : Realtek 8139

GPU : NVIDIA GeForce 7600 GT 256 MB

CPU : Intel Core 2 Duo

Unfortunately, man in the bios a few things like onboard lan, onboard FireWire and JMicron S-ATA as otherwise disable the hibernation does not work. Therefore it is important if man wants to use it to sleep to get an External LAN card. The drivers I will later to hand as I want to try something else.

Bios Setup

Load Setup Default

CPU Configuration

CPU Internal Thermal Control = Disable

Limit CPUID MaxVal = Disable

Enhanced C1 (C1E) = Disable

Execute Disable Bit = Enable

Enhanced Intel SpeedStepp = Disable

Onboard Divice Configuration

Onboard Lan = Disable

Onboard 1394 = Disable

JMicron SATA Controler = Disable

rama · November 7, 2009

any chance of someone upping the files from 2nd post somewhere else? rapid share keeps giving me full slots errors... been trying for 2 days

rama · November 8, 2009

nevermind... finally got them... took a couple of hours tho...

verdant · November 8, 2009

Temporary Cached Version (November 1, 2009) of my install guide......I am waiting to see if the admins have a much later backed-up version they can upload to post #1.......

This guide is:

1. Split into sections and sub-sections for ease of following and adding to....

2. A "live guide" that will evolve with both Snow Leopard 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 a printed-out static version successfully.....

3. How do I use this guide most efficiently?

Read Part A, then Part B......then:

Read Part C if you want to produce a USB flash drive installer......

and then

Part D if you want to install from a USB flash drive to a GPT HDD.....

OR

Part E if you want to install from a USB flash drive to a MBR HDD.....

OR

Part A, then Part B......then:

Read Part F if you want to install from a Retail Snow Leopard Mac OS X Install DVD to a GPT HDD using my nForceSLBoot132DVD......

THEN

Read Part I if you want to be able to boot into Snow Leopard from your Leopard Chameleon bootloader screen......

FINALLY

After successful installation read Parts G to K periodically to keep up to date with the development of non-Apple Snow Leopard 64bit kexts and their operation (e.g. audio, sleep etc.) and/or DSDT modding on nForce chipset/Intel CPU MOBOs....... (IMG:style_emoticons/default/smile.gif)

4. Are there any special points to note?

Yes.....remember that despite nForce chipset MOBOs now being able to run the Snow Leopard kernel, you still are dealing with the nForce chipset and OS X.......So:

[1] Check your BIOS settings against the recommended settings for OS X........depending on your MOBO nForce chipset, check in either my Series 7 nForce chipset + Intel CPU thread or in my Pre-Series 7 nForce chipset + Intel CPU thread......

Ensure that your IDE/SATA settings are set correctly e.g. enabling the SATA Controller or AHCI Mode depending on your BIOS options, and setting HPET Function/Support to [Enabled]....

[2] Despite a number of vanilla install guides for Snow Leopard saying that a SATA DVDRW is recommended/best/required for installing Snow Leopard.......this is not generally the case with nForce chipset MOBOs (unless the nForce MCP is fully AHCI compliant e.g. MCP73......see here)......

If the nForce MCP is not fully AHCI compliant, then a PATA (IDE) DVDRW is preferred/recommended to avoid issues with the now infamous "still waiting for root device" error.....

This is because we have to use the AppleNForceATA.kext.......currently still only available as 32bit compiled......

However, while slashhack's v0.1 AppleNForceATA.kext (32bit) supports 64bit memory addressing enabling the use of >3GB RAM, some SATA DVDRWs may have problems with this kext......e.g. not being recognized; a SAM Multimedia: Read or Write failed.....error; not being able to burn CDs/DVDs....

So, if this is the case you will need to use MeDevil's AppleNForceATA_Test.kext BUT this kext can only be used with maxmem=3072 in com.apple.Boot.plist or with > 3GB RAM as it does not support 64bit memory addressing.....you may still have issues with not being able to burn CDs/DVDs.......

[3] If you are using a IDE HDD and/or IDE DVDRW, then the IDE cable connections are very important.......

80-wire IDE cable with end Master connector and middle Slave connector

IDE HDD/DVDRW :

IDE HDD jumper set as Slave with IDE DVDRW jumper set as Master

SATA HDD/IDE DVDRW :

IDE DVDRW jumper set as Master

IDE HDD/SATA DVDRW :

IDE HDD jumper set as Master

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

BREAKING NEWS:

1. Aqua-mac has kindly provided a Snow Leopard HUD style ("transparent") "About this Mac" window fix.....see section K.

2. Audio has now been fixed for the Asus P5N32-E SLI Plus MOBO Asus SupremeFX audio card (except for Front Panel Headphones).....see post #2 in this thread...... (IMG:style_emoticons/default/biggrin.gif)

3. Booting into Snow Leopard from your Leopard volume's Chameleon 2.0 RC3 bootloader screen.....using netkas' PC-EFI v10.3 boot file......see Part I......

4. My two nForceSLBoot132DVD.iso files are now uploaded..... (IMG:style_emoticons/default/biggrin.gif)

Two versions are available:

One using slashack's v0.1 AppleNForceATA.kext for PATA DVDRW (now in Beta version)

One using MeDevil's AppleNForceATA_Test.kext for SATA DVDRW (now in Alpha version)......

For links to both versions and user instructions, please see Part F. below..........enjoy (IMG:style_emoticons/default/biggrin.gif)

N.B. Burn either .iso to DVD at the slowest possible speed ≤ x4

Please report any problems/issues with either .iso in this thread.......

Thank you......verdant (IMG:style_emoticons/default/smile.gif)

5. An original kext/modified kext/driver "Developers/Contributors Corner" has been set up in Part K (the originator/developer is acknowledged together with the contributor when the developer is known...if any reader can add such information please post the information so that the developers can be properly credited....thank you, verdant...... (IMG:style_emoticons/default/smile.gif)

6. Snow_Support_Files_V2.2 now includes netkas' Snow Leopard dsmos.kext and Kabyl's Leopard Disabler.kext to use if required in place of fakesmc.kext (v1 or v2) and NullCPUPowerManagement.kext, as well as fakesmc V1 and V2 and nForceLAN plus modified IONetworkingFamily.kext, AnV's and slashack's AppleNForceATA kexts....other necessary stuff plus useful uitilities... (IMG:style_emoticons/default/wink_anim.gif)

7. Modified advice regarding kexts in /Extra/Extensions and Extensions.mkext.....

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

WARNING: May apply to nForce chipset MOBOs too

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

QUOTE

@d00m42

Found a BIG issue for those running a drive or partition with windows 7 installed and formated with NTFS!

Remove or disconnect your Windows 7 drive, or you will be getting OSX crashes, *ntfs corruption*, possible KP's!

I have plowed through my logs looking for possible reasons for random crashing, kp's (prior to Realtek1000.ktext removal)

One of the symptoms I was seeing was sata devices became delayed, even paused for up to 10secs before a sata device would respond.. this would repeat about 3 times then.. crashed to the GSOD screen. The other symptom was slow overall disk reads / writes

Looking back through my logs I found the following in regards to WINDOWS 7 NTFS ONLY

Below was the findings:

Aug 29 14:07:49 Brians-Mac-Pro kernel[0]: NTFS-fs error (device /dev/disk1s2, pid 25): ntfs_inode_data_sync(): ubc_msync() of data for mft_no 0x69 failed (error 30).

Aug 29 14:07:49 Brians-Mac-Pro kernel[0]: NTFS-fs error (device /dev/disk1s2, pid 25): ntfs_vnop_pageout(): Failed (error 30).

Aug 29 14:07:55 Brians-Mac-Pro kernel[0]: NTFS-fs error (device /dev/disk1s2, pid 13078): ntfs_mft_record_sync(): Failed to write mft record 0xe5e8 (error 13).

Aug 29 14:07:55 Brians-Mac-Pro kernel[0]: NTFS-fs error (device /dev/disk1s2, pid 13078): ntfs_inode_sync(): Failed to sync mft_no 0xe5e8 (error 13). Run chkdsk.

Aug 29 14:07:55 Brians-Mac-Pro kernel[0]: NTFS-fs error (device /dev/disk1s2, pid 13078): ntfs_vnop_inactive(): Failed to sync mft_no 0xe5e8, type 0x80, name_len 0xc (error 13).

Aug 29 14:20:49 Brians-Mac-Pro kernel[0]: NTFS-fs error (device /dev/disk1s2, pid 90): ntfs_mft_record_sync(): Failed to write mft record 0xe5e8 (error 13).

Aug 29 14:20:49 Brians-Mac-Pro kernel[0]: NTFS-fs error (device /dev/disk1s2, pid 90): ntfs_inode_sync(): Failed to sync mft_no 0xe5e8 (error 13). Run chkdsk.

Aug 29 14:20:49 Brians-Mac-Pro kernel[0]: NTFS-fs error (device /dev/disk1s2, pid 90): ntfs_vnop_inactive(): Failed to sync mft_no 0xe5e8, type 0x80, name_len 0x0 (error 13).

and the following errors regarding NTFS version issues:

ntfs_inode_afpinfo_cache(): AFP_AfpInfo data attribute of mft_no 0x8e0c contains invalid data (wrong signature, wrong version, or wrong size), ignoring and using defaults.

Aug 29 14:22:36 Brians-Mac-Pro kernel[0]: NTFS-fs warning (device /dev/disk1s3, pid 25): ntfs_inode_afpinfo_cache(): AFP_AfpInfo data attribute of mft_no 0x8e0e contains invalid data (wrong signature, wrong version, or wrong size), ignoring and using defaults.

Aug 29 14:22:36 Brians-Mac-Pro kernel[0]: NTFS-fs warning (device /dev/disk1s3, pid 25): ntfs_inode_afpinfo_cache(): AFP_AfpInfo data attribute of mft_no 0x8e0f contains invalid data (wrong signature, wrong version, or wrong size), ignoring and using defaults.

Aug 29 14:22:36 Brians-Mac-Pro kernel[0]: NTFS-fs warning (device /dev/disk1s3, pid 25): ntfs_inode_afpinfo_cache(): AFP_AfpInfo data attribute of mft_no 0x8e10 contains invalid data (wrong signature, wrong version, or wrong size), ignoring and using defaults.

Aug 29 14:27:56 Brians-Mac-Pro kernel[0]: NTFS-fs error (device /dev/disk1s2, pid 13220): ntfs_vnop_pageout(): Failed (error 30).

So, without haste I booted into my windows 7... BLUE SCREEN OF DEATH 3 times @ boot

Had to repair the disk and found TONS of errors!

*********

Head the warning, remove the drive or disable OSX from mounting that drive/partition...

Until further information can be found regarding this problem**********

Since I have removed the drive completely I have noticed night and day speed difference on the sata performance.

I have had ZERO system errors / GSOD or KP's since..

A. How much of a "64bit" OS is Snow Leopard?

See this interesting and useful article.

Key points:

Snow Leopard is completely backwards-compatible with 32-bit applications
Snow Leopard runs 64-bit applications regardless of whether it boots into a 64-bit or a 32-bit kernel
Boots by default into 32bit on all Macs except Xserve
Only a CPU with SSE3 can run 64-bit kernel and applications
A Core 2 Duo or better multicore CPU (will become the Core i3 family)......or a Core iX (X= 3, 5, 7, 9....) multicore CPU.....is required for GCD
nVidia GeForce 8600 GT or better......nVidia Quadro FX.......ATI Radeon 4850, Radeon 4870.....etc. for OpenCL

System Requirements

1GB of memory
5GB of available disk space
DVD drive for installation......(or bootable USB....... (IMG:style_emoticons/default/wink_anim.gif) )

B. Generating and modifying the DSDT.aml file specifically for your MOBO:

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.

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 to later use in your / directories on the USB stick and HDD......For this you need Leopard running on the PC onto which you plan to install Snow Leopard.....

To create the DSDT.aml file and modify to fix the CMOS reset issue, proceed as follows:

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 ($ being the default shell prompt - DO NOT TYPE the $ !)

CODE

$ 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.

DSDT_FIles.png ( 10.97K ) Number of downloads: 163

Stage 2. To edit the dsdt.dsl file:

4. Type in the same Terminal window:

CODE

$ 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.......

QUOTE

Device (RTC)

{

Name (_HID, EisaId ("PNP0B00"))

Name (ATT0, ResourceTemplate ()

{

IO (Decode16,

0x0070, // Range Minimum

0x0070, // Range Maximum

0x00, // Alignment

0x04, // Length -> change 0x04 to 0x02

)

})

Name (ATT1, ResourceTemplate ()

{

IO (Decode16,

0x0070, // Range Minimum

0x0070, // Range Maximum

0x00, // Alignment

0x04, // Length -> change 0x04 to 0x02

)

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:

CODE

$ ./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

CODE

$ 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........ (IMG:style_emoticons/default/smile.gif)

C. Making a bootable GPT partition USB flash drive OS X 10.6 Installer:

1. You will need:

(1) Access to a working Mac or Hack x86 OS X Leopard system

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

(3) Your new Retail Mac OS X 10.6 Install DVD from which to make its .dmg image file, OR a pre-existing Retail Mac OS X 10.6 Install DVD dmg/.iso image fileTo make the OS X Install DVD image [.dmg] (or indeed any CD or DVD image) in Disk Utility by highlighting the disk in the sidebar -> File -> New -> Disk Image from diskXsY (Mac OS X Install DVD)....leaving Image Format as Compressed and Encryption as None....... (IMG:style_emoticons/default/smile.gif)

(4) A DSDT.aml file generated for your MOBO/system (e.g. e.g. fassl's DSDT Patcher)

(5) The Chameleon 2.0 RC1 Installer, or RC2 Installer, or an RC3 Installer (see below)

2. Procedure to follow:

In Leopard OS X, you should

(1) Plug in the USB flash drive and then using Disk Utility, partition/format it as a single GPT/HFS+ volume named OSX_10.6_USB_Installer (or your chosen name without spaces)

To partition/format it as a single GPT/HFS+ volume, go to Disk Utility -> in the sidebar highlight your USB flash drive device icon -> in main window, click on the Partition tab -> select to partition as 1 volume, with a name with no spaces and format as Mac OS Extended (Journaled) -> click on Options button -> select GUID Partition Table (GPT) -> click Apply.......

(2) Use Disk Utility to get the UUID for the OSX_10.6_USB_Installer volume by going to Info tab in top menu bar after highlighting the OSX_10.6_USB_Installer volume in the side bar........you need to highlight the USB GPT/HFS+ volume icon NOT the USB device icon in the Disk Utility side bar........

The UUID number is against the Universal Unique Identifier : CF2E12F1-2459-3DAF-B3D5-CA05B4B65A52

Your USB UUID will be in this format but obviously different!

(3) Run the Chameleon 2.0 RC1 Installer

"Presently IMHO Chameleon 2.0 RC1 bootloader with the netkas PC_EFI v10.1 boot file (and using -x32 kernel flag) is still the tried and tested method (that I personally have used) to use and/or fall back on should the following alternatives be problematic on your MOBO/system; e.g. failed installation, kernel panics, "bombing" of the system etc.....ESPECIALLY for the USB Flash drive OS 10.6. Installer which you definitely want to boot and work reliably...... (IMG:style_emoticons/default/wink_anim.gif) "

OR Alternative 1: Run the Chameleon 2.0 RC2 Installer

OR Alternative 2: Use Dr. Hurt's UNOFFICIAL installer to install Chameleon 2.0 RC3 completely

OR Alternative 3: Run dj nitehawk's Pre-Install Automator v1.1 script just to install Chameleon 2.0 RC3 completely

OR Alternative 4: Just use the Chameleon 2.0 RC3 boot file as explained below.... and after installing whichever Chameleon bootloader you have chosen, i.e. RC1 or RC2 or RC3, in the / directory of the OSX_10.6_USB_Installer volume, you will see, either with the "hidden and system files" unhidden (see below how to do this) or listed in Terminal using

CODE

cd /Volumes/OSX_10.6_USB_Installer

ls

the following:

boot file

Extra folder

Library folder

usr folder

plus some ."name" files.....

(4) Now depending on what Chameleon 2.0 bootloader you have installed, you will have to choose the appropriate boot file to use and install it if not already installed......the boot file is normally a hidden file but you can unhide it, or use Terminal commands to overwrite it with a replacement boot file when you change from the "username" directory to the directory containing the replacement boot file....

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

UNHIDING HIDDEN FILES:

The Terminal commands to show/hide hidden and system files are:

QUOTE

To show hidden and system files:

CODE

defaults write com.apple.finder AppleShowAllFiles TRUE

killall Finder

To hide hidden and system files

CODE

defaults write com.apple.finder AppleShowAllFiles FALSE

killall Finder

or you can download and run TinkerTool 3.96......

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

Either delete the now visible Chameleon 2.0 RC1 boot file and then drag and drop the PC_EFI v10.1 (RECOMMENDED ONLY if Chameleon 2.0 RC1 has been installed) into the / directory.....and use the -x32 kernel flag in com.apple.Boot.plist.....

OR

If you have installed Chameleon 2.0 RC2, or prefer to install Chameleon 2.0 RC1 overlaid with the Chameleon 2.0 RC3 boot file, then go to the Chameleon website.....and look under Latest Releases for Chameleon-2.0-RC3-r658-bin.tar.gz [736.38KB]).......

Download and unarchive Chameleon-2.0-RC3-r658-bin.tar.gz to Chameleon-2.0-RC3-r658-bin and copy the RC3 boot file from the i386 folder over either the Chameleon 2.0 RC2 boot file or the Netkas PC_EFI v10.1 boot file in the / directory......and use the arch=i386 kernel flag in com.apple.Boot.plist.....

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

EXAMPLE OF OVERWRITING THE HIDDEN BOOT FILE

To copy the RC3 boot file across into the / directory of the OSX_10.6_USB_Installer (see below), open Terminal, type the following commands ($ being the default shell prompt - DO NOT TYPE!)

cd followed by a space, and then drag and drop the i386 folder into the Terminal window

cp -f boot /Volumes/OSX_10.6_USB_Installer/

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

OR

If you have installed Chameleon 2.0 RC3, then you can choose to use the installed RC3 boot file, or you can overwrite it with the netkas PC_EFI v10.3 boot file....and use the arch=i386 kernel flag in com.apple.Boot.plist.....

IMHO the Chameleon 2.0 RC2 bootloader is not to be recommended -

so, USE ONLY Chameleon 2.0 RC1 bootloader + PC_EFI v10.1 boot file.....

OR

Chameleon 2.0 RC3 bootloader with the RC3 boot file

OR

Chameleon 2.0 RC1 bootloader + RC3 boot file......

OR

Chameleon 2.0 RC3 bootloader with the netkas PC_EFI v10.3 boot file.....

as RC2 seems to only work with only a few PCs....

Interesting comment from Kabyl at netkas.org

QUOTE

People were having issues with the pkg installer in RC2, and it wasn't fixed yet, so until then there is no pkg installer for RC3. You can use the old installers and replace /boot if you don't want to install manually, and if you already are using Chameleon, you don't need the installer at all, just replace /boot with the new one.

BUT remember that to boot the mach_kernel into 32bit mode using the Chameleon 2.0 RC3 boot file requires you to use the arch=i386 kernel flag rather than -x32 as used with the netkas PC_EFI v10.1 boot file.....

If you have any problems booting from your HDD partition, then put either arch=i386 if using RC3 bootfile or -x32 if using PC_EFI v10.1 or V10.2 under Kernel Flags in /Library/Preferences/SystemConfiguration/com.apple.Boot.plist as well....

So, later in

/Extra/com.apple.Boot.plist and in /Library/Preferences/SystemConfiguration/com.apple.Boot.plist

find:

<key>Kernel Flags</key>

and change it to

<key>Kernel Flags</key>

(5) MODIFIED ADVICE: Many forum readers are having problems with the /Extra/Extensions cache file, i.e. Extensions.mkext not loading/working properly.....hence

If in the /Extra/Extensions, you installed all the kexts included in Chameleon 2.0 RC1 or RC2 or RC3 /Extra/Extensions,

OR if you only loaded one or two kexts in order for the /Extra/Extensions/ directory to be set up by the Chameleon Installer,

then delete them and from the downloaded Snow_Support_Files_V2.2,

that I have conveniently compiled in one folder for myself (NOTE: ALL CREDIT goes the developers of the included applications/kexts/bootloaders and boot files etc.; David Elliott, netkas, Superhai, Psystar, eno, slashack, AnV, Dr. Hurt.....),

copy across the following kexts:

ESSENTIAL

fakesmc.kext (32bit and 64bit compatible) -> emulates SMC to provide the information required for the Don't Steal Mac OS X.kext to decrypt the Apple encrypted files

"Choose either V2 or V1.......whichever "works" for you.......see Changelog for V2.1...."

NullCPUPowerManagement.kext (32bit and 64bit compatible) -> A problem with running OS X running on non-Apple hardware (both physically and in VM) is that the AppleIntelCPUPowerManagement.kext invariably causes a kernel panic or at bootup generates endless messages regarding the HPET and links to the CPU. AFAIK the NullCPUPowerManagement.kext plays a couple of tricks with the IOKit service registration process to take over the role of the AppleIntelCPUPowerManagement.kext, essentially disabling it. Also deals with heat issues.....

OpenHaltRestart.kext (32bit and 64bit compatible) -> fixes reboot and shutdown on PC-based machines without binary patching or recompiling the kernel

LESS ESSENTIAL

PlatformUUID.kext (32bit and 64bit compatible) -> Fixes some Time Machine related errors by providing a UUID from bootup (fixes UUID 35 errors)

ESSENTIAL FOR nForce Chipset MOBOs

AppleNForceATA.kext (32bit only at present - slashack's v0.1 kext or AnV's kext)

OPTIONAL FOR nForce Chipset MOBOs

Modified IONetworkingFamily.kext (from Snow Leopard but with nvenet.kext in Plugins renamed) - found in Snow_Support_Files_v2.1

plusnForceLAN.kext (64bit - eno's kext) ONLY IF YOU ARE USING ONBOARD LAN (Enabled in BIOS)

"Other kexts (32bit or 32/64bit or 64bit) if/when available may be used and/or essential if they work on nForce chipset + Intel multicore CPU MOBOs with OS X 10.6......e.g. for enabling sleep, audio, graphics etc......"

(6) Drag and drop your previously modded and saved DSDT.aml file into the / directory

(7) Use TextEdit, Property List Editor, TextMate or your favourite .plist file text editor to modify the SMBIOS.plist template included in the Snow Support Files, to suit your system hardware/RAM etc.......

A further modification is to insert your OSX_10.6_USB_Installer volume UUID number under/against SMUUID......and save the modified SMBIOS.plist (renamed from SMBIOS_MacPro21.plist if you are using this file, i.e. only if you wish to rename it.....) and put it in /Extra

(8) Then go to PlatformUUID.kext, and Show Package Contents -> Contents -> Info.plist.....use TextEdit, Property List Editor, TextMate or your favourite .plist file text editor to modify the Info.plist and go to IOKitPersonalities -> PlatformUUID and insert your OSX_10.6_USB_Installer volume UUID number under/against PlatformUUID and save the modified Info.plist file

(9) MODIFIED ADVICE: Many forum readers are having problems with the /Extra/Extensions cache file, i.e. Extensions.mkext not loading/working properly.....hence

If you get a kernel panic during booting as follows:[/font]

QUOTE

Kernel Extensions in backtrace (with dependencies):

com.apple.driver.AppleIntelCPUPowerManagement) and then some random numbers and letters or with references to HPET not being assigned to the CPU etc.

BSD process name corresponding to current thread: kernel_task

this indicates that for some reason NullCPUPowerManagement.kext is not taking over from the AppleIntelCPUPowerManagement.kext, as it should be, by being loaded into the kernel before the AppleIntelCPUPowerManagement.kext residing in /System/Library/Extensions, with its pathway inExtensions.mkext located at /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext......

This is because the Kext Utility.app did not build the the Extensions.mkext cache file pathway to NullCPUPowerManagement.kext in /Extra/Extensions properly properly (although it is probably setting the kext permissions correctly which is important).....so that NullCPUPowerManagement.kext is not being loaded into the kernel from Extenstions.mkext.....

Advice:

1. Delete the Extensions.mkext cache file from /Extra on your USB flash drive OS X Installer AND from /Extra on your target OS X volume.....

2. Copy "fresh" extensions across from Snow_Support_Files _V2.2 into the /Extra directories

AppleNForceATA.AnV or AppleNForceATA.slash

fakesmc.V2 or fakesmc.V1

NullCPUPowerManagement

OpenHaltRestart

PlatformUUID (although even different UUIDs in SMBIOS.plist and PlatformUUID Info.plist does not appear to cause any problems because according to Superhai the UUID in SMBIOS is not used for anything.....)

If an Extensions.mkext file is not present in /Extra the kexts in /Extra/Extensions will be loaded directly......the Extensions.mkext cache file being more of a convenience than a necessity at bootup in terms of a somewhat reduced bootup time; being a cached version of all the kexts in the Extensions folder, resulting in faster loading of the extensions at boot.

OS X continues to use the Extensions.mkext file until its modified date is different from that of the Extensions folder itself; at which point, it reverts to loading them from the Extensions folder and then re-creates the Extensions.mkext file......in Leopard (BUT NOT Snow Leopard at present) booting with -f forces the kexts to be loaded from the Extensions folder at bootup and then recreates the Extensions.mkext file....

(10) Use TextEdit, Property List Editor, TextMate or your favourite .plist file text editor to modify the com.apple.Boot.plist template included in the Snow Support Files to boot the kernel into 32bit mode using either the arch=i386 kernel flag with the Chameleon 2.0 RC3 boot file OR the -x32 kernel flag with the PC_EFI v10.1 boot file (ONLY RECOMMENDED if Chameleon 2.0 RC1 has been installed) and save the modified com.apple.Boot.plist and put it in /Extra....

(11) Now use Disk Utility -> Restore function to load the Retail Mac OS X 10.6 Install DVD (or its .dmg/.iso image file) onto the OSX_10.6_USB_Installer volume.....

(12) Check that the folders/files now present are:

USB_Installer_All.png ( 91.08K ) Number of downloads: 304

D. Installing OS X to your target HDD volume partitioned/formatted as GPT/HFS+

(1) Use Disk Utility to partition/format your target HDD volume for OS X 10.6 as GPT/HFS+ volume named OSX_10.6_GPT_A (or your chosen name without spaces)

(2) Use Disk Utility to get the UUID for the OSX_10.6_GPT_A volume by going to Info tab in top menu bar after highlighting the OSX_10.6_GPT_A volume in the side bar, and making a careful note of the Universal Unique Identifier number:

It will be in this format (but obviously different!): CF2E12F1-2459-3DAF-B3D5-CA05B4B65A52

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

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 equiavlent to using root:wheel)

CODE

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.6 hard drive........

(3) Run EFIStudio or OSx86Tools to generate the graphics string for your graphics card assuming that it is OpenCL compatible.....save to clipboard (or in a text file) for later use in Section D Part 11B on modifying the com.apple.Boot.plist file......

(4) Run the Chameleon 2.0 RC1 Installer

"Presently IMHO Chameleon 2.0 RC1 bootloader with the netkas PC_EFI v10.1 boot file (and using -x32 kernel flag) is still the tried and tested method (that I personally have used) to use and/or fall back on should the following alternatives be problematic on your MOBO/system; e.g. failed installation, kernel panics, "bombing" of the system etc.....ESPECIALLY for the USB Flash drive OS 10.6. Installer which you definitely want to boot and work reliably...... (IMG:style_emoticons/default/wink_anim.gif) "

OR Alternative 1: Run the Chameleon 2.0 RC2 Installer

OR Alternative 2: Use Dr. Hurt's UNOFFICIAL installer to install Chameleon 2.0 RC3 completely

OR Alternative 3: Run dj nitehawk's Pre-Install Automator v1.1 script just to install Chameleon 2.0 RC3 completely

OR Alternative 4: Just use the Chameleon 2.0 RC3 boot file as explained below....

and after installing whichever Chameleon bootloader you have chosen, i.e. RC1 or RC2 or RC3, in the / directory of the OSX_10.6_GPT_A volume, you will see, either with the "hidden and system files" unhidden (see below how to do this) or listed in Terminal using

CODE

cd /Volumes/OSX_10.6_GPT_A

ls

the following:

boot file

Extra folder

Library folder

usr folder

plus some ."name" files.....

(5) Now depending on what Chameleon 2.0 bootloader you have installed, you will have to choose the appropriate boot file to use and install it if not already installed......the boot file is normally a hidden file but you can unhide it, or use Terminal commands to overwrite it with a replacement boot file when you change from the "username" directory to the directory containing the replacement boot file....

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

UNHIDING HIDDEN FILES:

The Terminal commands to show/hide hidden and system files are:

QUOTE

To show hidden and system files:

CODE

defaults write com.apple.finder AppleShowAllFiles TRUE

killall Finder

To hide hidden and system files

CODE

defaults write com.apple.finder AppleShowAllFiles FALSE

killall Finder

or you can download and run TinkerTool 3.96......

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

Either delete the now visible Chameleon 2.0 RC1 boot file and then drag and drop the PC_EFI v10.1 (RECOMMENDED ONLY if Chameleon 2.0 RC1 has been installed) into the / directory.....and use the -x32 kernel flag in com.apple.Boot.plist.....

OR

If you have installed Chameleon 2.0 RC2, or prefer to install Chameleon 2.0 RC1 overlaid with the Chameleon 2.0 RC3 boot file, then go to the Chameleon website.....and look under Latest Releases for Chameleon-2.0-RC3-r658-bin.tar.gz [736.38KB]).......

Download and unarchive Chameleon-2.0-RC3-r658-bin.tar.gz to Chameleon-2.0-RC3-r658-bin and copy the RC3 boot file from the i386 folder over either the Chameleon 2.0 RC2 boot file or the Netkas PC_EFI v10.1 boot file in the / directory......and use the arch=i386 kernel flag in com.apple.Boot.plist.....

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

EXAMPLE OF OVERWRITING THE HIDDEN BOOT FILE

To copy the RC3 boot file across into the / directory of the OSX_10.6_USB_Installer (see below), open Terminal, type the following commands ($ being the default shell prompt - DO NOT TYPE!)

cd followed by a space, and then drag and drop the i386 folder into the Terminal window

cp -f boot /Volumes/OSX_10.6_GPT_A/

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

OR

If you have installed Chameleon 2.0 RC3, then you can choose to use the installed RC3 boot file, or you can overwrite it with the netkas PC_EFI v10.3 boot file....and use the arch=i386 kernel flag in com.apple.Boot.plist.....

IMHO the Chameleon 2.0 RC2 bootloader is not to be recommended -

so, USE ONLY Chameleon 2.0 RC1 bootloader + PC_EFI v10.1 boot file.....

OR

Chameleon 2.0 RC3 bootloader with the RC3 boot file

OR

Chameleon 2.0 RC1 bootloader + RC3 boot file......

OR

Chameleon 2.0 RC3 bootloader with the netkas PC_EFI v10.3 boot file.....

as RC2 seems to only work with only a few PCs....

Interesting comment from Kabyl at netkas.org

QUOTE

People were having issues with the pkg installer in RC2, and it wasn't fixed yet, so until then there is no pkg installer for RC3. You can use the old installers and replace /boot if you don't want to install manually, and if you already are using Chameleon, you don't need the installer at all, just replace /boot with the new one.

BUT remember that to boot the mach_kernel into 32bit mode using the Chameleon 2.0 RC3 boot file requires you to use the arch=i386 kernel flag rather than -x32 as used with the netkas PC_EFI v10.1 boot file.....

If you have any problems booting from your HDD partition, then put either arch=i386 if using RC3 bootfile or -x32 if using PC_EFI v10.1 or V10.2 under Kernel Flags in /Library/Preferences/SystemConfiguration/com.apple.Boot.plist as well....

So, later in

/Extra/com.apple.Boot.plist and in /Library/Preferences/SystemConfiguration/com.apple.Boot.plist

find:

<key>Kernel Flags</key>

and change it to

<key>Kernel Flags</key>

(6) MODIFIED ADVICE: Many forum readers are having problems with the /Extra/Extensions cache file, i.e. Extensions.mkext not loading/working properly.....hence

If in the /Extra/Extensions, you installed all the kexts included in Chameleon 2.0 RC1 or RC2 or RC3 /Extra/Extensions,

OR if you only loaded one or two kexts in order for the /Extra/Extensions/ directory to be set up by the Chameleon Installer,

then delete them and from the downloaded Snow_Support_Files_V2.2,

that I have conveniently compiled in one folder for myself (NOTE: ALL CREDIT goes the developers of the included applications/kexts/bootloaders and boot files etc.; David Elliott, netkas, Superhai, Psystar, eno, slashack, AnV, Dr. Hurt.....),

copy across the following kexts:

ESSENTIAL

fakesmc.kext (32bit and 64bit compatible) -> emulates SMC to provide the information required for the Don't Steal Mac OS X.kext to decrypt the Apple encrypted files

"Choose either V2 or V1.......whichever "works" for you.......see Changelog for V2.2...."

NullCPUPowerManagement.kext (32bit and 64bit compatible) -> A problem with running OS X running on non-Apple hardware (both physically and in VM) is that the AppleIntelCPUPowerManagement.kext invariably causes a kernel panic or at bootup generates endless messages regarding the HPET and links to the CPU. AFAIK the NullCPUPowerManagement.kext plays a couple of tricks with the IOKit service registration process to take over the role of the AppleIntelCPUPowerManagement.kext, essentially disabling it. Also deals with heat issues.....

OpenHaltRestart.kext (32bit and 64bit compatible) -> fixes reboot and shutdown on PC-based machines without binary patching or recompiling the kernel

LESS ESSENTIAL

PlatformUUID.kext (32bit and 64bit compatible) -> Fixes some Time Machine related errors by providing a UUID from bootup (fixes UUID 35 errors)

ESSENTIAL FOR nForce Chipset MOBOs

AppleNForceATA.kext (32bit only at present - slashack's v0.1 kext or AnV's kext)

OPTIONAL FOR nForce Chipset MOBOs

Modified IONetworkingFamily.kext (from Snow Leopard but with nvenet.kext in Plugins renamed) - found in Snow_Support_Files_v2.2

plus

nForceLAN.kext (64bit - eno's kext) ONLY IF YOU ARE USING ONBOARD LAN (Enabled in BIOS)

"Other kexts (32bit or 32/64bit or 64bit) if/when available may be used and/or essential if they work on nForce chipset + Intel multicore CPU MOBOs with OS X 10.6......e.g. for enabling sleep, audio, graphics etc......"

(7) Drag and drop your previously modded and saved DSDT.aml file into the / directory

(8) Use TextEdit, Property List Editor, TextMate or your favourite .plist file text editor to modify the SMBIOS.plist template included in the Snow Support Files, to suit your system hardware/RAM etc.......

A further modification is to insert your OSX_10.6_GPT_A volume UUID number under/against SMUUID......and save the modified SMBIOS.plist (renamed from SMBIOS_MacPro21.plist if you are using this file, i.e. only if you wish to rename it.....) and put it in /Extra

(9) Then go to PlatformUUID.kext, and Show Package Contents -> Contents -> Info.plist.....use TextEdit, Property List Editor, TextMate or your favourite .plist file text editor to modify the Info.plist and go to IOKitPersonalities -> PlatformUUID and insert your OSX_10.6_GPT_A volume UUID number under/against PlatformUUID and save the modified Info.plist file

(10) MODIFIED ADVICE: Many forum readers are having problems with the /Extra/Extensions cache file, i.e. Extensions.mkext not loading/working properly.....hence

If you get a kernel panic during booting as follows:

QUOTE

Kernel Extensions in backtrace (with dependencies):

com.apple.driver.AppleIntelCPUPowerManagement) and then some random numbers and letters or with references to HPET not being assigned to the CPU etc.

BSD process name corresponding to current thread: kernel_task

this indicates that for some reason NullCPUPowerManagement.kext is not taking over from the AppleIntelCPUPowerManagement.kext, as it should be, by being loaded into the kernel before the AppleIntelCPUPowerManagement.kext residing in /System/Library/Extensions, with its pathway inExtensions.mkext located at /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext......

This is because the Kext Utility.app did not build the the Extensions.mkext cache file pathway to NullCPUPowerManagement.kext in /Extra/Extensions properly properly (although it is probably setting the kext permissions correctly which is important).....so that NullCPUPowerManagement.kext is not being loaded into the kernel from Extenstions.mkext.....

Advice:

1. Delete the Extensions.mkext cache file from /Extra on your USB flash drive OS X Installer AND from /Extra on your target OS X volume.....

2. Copy "fresh" extensions across from Snow_Support_Files _V2.2 into the /Extra Directories

AppleNForceATA.AnV or AppleNForceATA.slash

fakesmc.V2 or fakesmc.V1

NullCPUPowerManagementOpenHaltRestart

PlatformUUID (although even different UUIDs in SMBIOS.plist and PlatformUUID Info.plist does not appear to cause any problems because according to Superhai the UUID in SMBIOS is not used for anything.....)

If an Extensions.mkext file is not present in /Extra the kexts in /Extra/Extensions will be loaded directly......the Extensions.mkext cache file being more of a convenience than a necessity at bootup in terms of a somewhat reduced bootup time; being a cached version of all the kexts in the Extensions folder, resulting in faster loading of the extensions at boot.

OS X continues to use the Extensions.mkext file until its modified date is different from that of the Extensions folder itself; at which point, it reverts to loading them from the Extensions folder and then re-creates the Extensions.mkext file......in Leopard (BUT NOT Snow Leopard at present) booting with -f forces the kexts to be loaded from the Extensions folder at bootup and then recreates the Extensions.mkext file....

(11) Use TextEdit, Property List Editor, TextMate or your favourite .plist file text editor to modify the com.apple.Boot.plist 32bit template included in the Snow Support Files to:

A. Boot the kernel into 32bit mode by entering either the arch=i386 kernel flag with the Chameleon 2.0 RC3 boot file installed OR the -x32 kernel flag with the PC_EFI v10.1 boot file installed under/against Kernel Flags in com.apple.Boot.plist

B. Provide graphics functionality for your PCI-E graphics card place the graphics string for your graphics card under/against device-properties in com.apple.Boot.plist

(12) Now save the modified com.apple.Boot.plist and put it in /Extra....

The folders/files present (including normally hidden ."name" files) prior to installing OS X 10.6 are:

PreOSX_Folders.png ( 27.76K ) Number of downloads: 21

(13) Now close all open windows on the Desktop and any open applications...

(14) 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......"

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

OR

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

I have given these two options because I have Chameleon bootloaders installed on different HDDs and OS X volumes......BUT the Leopard OS X systems are using mach_kernel.voodoo in com.apple.Boot.plist, whereas the Snow Leopard OS X systems are using the vanilla mach_kernel in com.apple.Boot.plist........That is different /Extra directories need to be used by Chameleon depending on the volume being booted from........hopefully Chameleon 2.0 RC3 can address this situation successfully......

(16) The Green Chameleon should appear together the text "Darwin loading"......and hopefully the Apple boot image......

When the OS X Installer window opens REMEMBER to open the Installer Log window too........and choose Show Errors and Progress......or Show All Logs......it is GOOD PRACTICE to do so when running any Installer package..... (IMG:style_emoticons/default/smile.gif)

(17) Thereafter follow the OS X Installer on-screen instructions and choose your required installation components in the Customize menu....and be careful about using Migration Assistant to migrate across from Leopard to Snow Leopard because I have found that non-Apple or 3rd Party kexts or renamed kexts (folders) such as kext.orig, kext.bad etc. are copied across into /S/L/E.....if this happens you will need to weed them out !

I thus recommend that after booting into 10.6, you type in Terminal

CODE

kextstat

to see the kexts currently loaded into the kernel......to see if there are any unwanted kexts.....

(18) When the installation has finished successfuly, restart......and boot successfully into OS X 10.6.....run Disk Utility to repair permissions......then auto Software Update to 10.6.1....... (IMG:style_emoticons/default/biggrin.gif)

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

Note: If during installation of OS X 10.6, the Installer fails to complete successfully

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

If during installation, the Installer fails to complete successfully due to a package extraction problem (as happend during my first attempt at installation), when an Installer Log listing similar to:

QUOTE

Sep 4 19:02:04 ubuntu-quadcore payloadExtractor[1834]: Initializing new flat-package receipt.

Sep 4 19:02:04 ubuntu-quadcore payloadExtractor[1834]: Extracting...

Sep 4 19:02:07 ubuntu-quadcore payloadExtractor[1834]: BomFileError 13: Permission denied - /Volumes/OS_X_10.6//System/Library/Extensions/hp_Photosmart_io_enabler.kext

Sep 4 19:02:07 ubuntu-quadcore payloadExtractor[1834]: 179 of 179 files written in 2.61 seconds.

Sep 4 19:02:07 ubuntu-quadcore payloadExtractor[1834]: 28852 kilobytes installed at 10.8 MB/s.

Sep 4 19:02:07 ubuntu-quadcore payloadExtractor[1834]: Error extracting archive.

Sep 4 19:02:07 ubuntu-quadcore payloadExtractor[1834]: pkgExtractor exited with error 1 while processing package '/Volumes/Mac OS X Install DVD/System/Installation/Packages/HP_Photosmart.pkg'

Sep 4 19:02:07 ubuntu-quadcore Installer[1440]: Install failed: The Installer could not install some files in ¾ï¿½ï¿½' ‚º/Volumes/OS_X_10.6 '¢ï¿½ï¿½ï¿½ï¿½â €š

Contact the software manufacturer for assistance.

Sep 4 19:02:07 ubuntu-quadcore Installer[1440]: IFDInstallController 68C7BA0 state = 7

Sep 4 19:02:07 ubuntu-quadcore Installer[1440]: Displaying 'Install Failed' UI.

Sep 4 19:02:07 ubuntu-quadcore Installer[1440]: 'Install Failed' UI displayed message:'The Installer could not install some files in ¾ï¿½ï¿½' ‚º/Volumes/OS_X_10.6 '¢ï¿½ï¿½ï¿½ï¿½â €š Contact the software manufacturer for assistance.'.

then re-run the Installer BUT DO NOT choose any Printer options in the Installer Customize menu.......these can be installed after your OS X 10.6 installation by re-running the Installer from within your running OS X 10.6 system.......

If even this does not work, then I have personally found the following to also work:

1. Install to an external USB single partition GPT/HFS+ HDD and install Chameleon 2.0 RC3 either try using Dr. Hurt's Installer, or run dj nitehawk's Pre-Install Automator v1.1 script just to install Chameleon 2.0 RC3 completely, or just use its /boot file as explained earlier......it is still best that you sort out your DSDT.aml file and extensions in /Extra, as well as com.apple.Boot.plist and SMBIOS.plist because this script is geared towards full vanilla (Intel) MOBOs rather than towards nForce MOBOs.....

2. Do not keep any generated Extension.mkext files in /Extra on your USB flash driver installer or on your target OS X 10.6.x HDD /Extra directories......

3. The HDD kexts in /Extra are:AppleNForceATA.AnV or AppleNForceATA.slash

fakesmc.V2 or fakesmc.V1NullCPUPowerManagementOpenHaltRestart

PlatformUUID (although even different UUIDs in SMBIOS.plist and PlatformUUID Info.plist does not appear to cause any problems because according to Superhai the UUID in SMBIOS is not used for anything.....)

4. When installing OS X 10.6 choose only the base system in the Customize menu

5. Once you have booted into OS X 10.6 on your HDD, use Disk Utility to repair permissions.....then auto Software update to 10.6.1......and only then run the Retail OS X DVD in your DVDRW to run the Optional Installs.mpkg to install Additional fonts, Language Transaltions, Printers, X11, Rosetta and/or Quicktime 7......

E. Installing OS X to your target HDD volume partitioned/formatted as MBR/HFS+

Procedure 1. (No pre-existing Snow Leopard OS installation)

In order for you to install or upgrade OS X 10.6 on MBR partitioned hard drive volumes you need a modified OSInstall.mpkg and OSInstall Unix executable file....to obtain these, I can do no better than point you to the links from Prasys' Blog....

There are two versions of OSInstall.mpkg......

Version 1. Prasys believes this version was made by Kabyl, modbin and ToH crew....

Version 2. This version removes checks on CPU , RAM requirements and other things as well, i.e. essentially skips all checks......

The procedure is as follows:

1. Unhide the hidden and systems files on your USB flash drive OSX_10.6_USB_Installer (or your chosen name without spaces) using Terminal commands ot Tinker Tool (see Part C.)

2. Go to Terminal and type

CODE

cd /Volumes/"OSX_10.6_USB_Installer (or your chosen name without spaces)"/System/Installation/Packages/

sudo mv OSInstall.mpkg OSInstall.mpkg.GPT

cd /Volumes/"OSX_10.6_USB_Installer (or your chosen name without spaces)"/System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A

sudo mv OSInstall OSInstall.GPT

exit

"I have renamed the original files as shown, 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 again via Terminal :

CODE

cd /Volumes/"OSX_10.6_USB_Installer (or your chosen name without spaces)"/System/Installation/Packages/

sudo mv OSInstall.mpkg.GPT OSInstall.mpkg

cd /Volumes/"OSX_10.6_USB_Installer (or your chosen name without spaces)"/System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A/

sudo mv OSInstall.GPT OSInstall

exit

3. Then either drag and drop (or use cp command via Terminal) the chosen version of OSInstall.mpkg into /Volumes/"OSX_10.6_USB_Installer (or your chosen name without spaces)"/System/Installation/Packages/

4. Then drag and drop (or use cp command via Terminal) OSInstall into /Volumes/"OSX_10.6_USB_Installer (or your chosen name without spaces)"/System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A/

5. Close all windows.......and then boot from the USB flash drive as normal......

Procedure 2. (Pre-existing Snow Leopard OS installation)

1. Simply use Disk utility or Carbon Copy Cloner 3.3 to clone a OX 10.6. 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 RC3 bootoader + PC_EFI V10.3 files to your SL MBR/HFS+ partition after cloning SL to it

3. Boot into the SL MBR/HFS+ partition with -v -f.....

F. Installing OS X to your target HDD volume partitioned/formatted as GUID Partition Table/HFS+ [specifically Mac OS X Extended (Journaled)] using verdant's nForceSLBoot132DVD.iso burned to DVD-R or DVD+RW using Disk Utility

1. Points to Note:

{a} My nForceSLBoot132DVD.iso is still a Beta version and my nForceSLBoot132DVD_for_SATA_DVDRW.iso is still an Aplha version until I get many reports of their being reliably successful on different nForce chipset MOBOs........so please post your experience (successful or otherwise [with helpful details for debug purposes........]) in this thread......

Thank you, verdant......... (IMG:style_emoticons/default/smile.gif)

{b} The nForceSLBoot132DVD.iso when burned to a DVD-R or DVD+RW will produce a Boot132 DVD named Legacy Boot CD.......this is because I have decided to use Trauma!'s BootCDMaker v1.1f, which is a simple BUT fantastic utility application to create a Chameleon BootCD as the basis for my nForceSLBoot132DVD.iso.... See here for a description of BootCDMaker in English......

N.B. Burn the DVD at the slowest possible speed ≤ x4

A key reason for choosing BootCDMaker is its great looking custom boot volume theme which includes on-screen boot prompt instructions and the fact that it saved me some time when sorting out what was needed for a successful, i.e. modified nForceSLBoot132DVD, which is different from the .ISO's produced as standard by BootCDMaker...... (IMG:style_emoticons/default/smile.gif)

So, remember to write "nForceSLBoot132DVD" on the DVD disk....... (IMG:style_emoticons/default/wink_anim.gif)

{c} Since not all nForce MOBOs have the same DSDT.aml file loaded from /Extra, the nForceSLBoot132DVD.iso DOES NOT include a DSDT.aml file and hence DOES NOT include the DSDT CMOS reset fix........

{d} I have included kexts that are compiled for x86_x64 architecture (i.e. Snow Leopard only) to hopefully allow the use of a PS/2 keyboard and PS/2 mouse (BUT I could not test if they work because I have a USB keyboard and USB mouse)......so please let me know if you are able to use a PS/2 keyboard and PS/2 mouse when typing after booting from the nForceSLBoot132DVD....... (IMG:style_emoticons/default/smile.gif)

2. Procedure to follow: ( Same as Part D from step (1) to step (13) )

(1) Use Disk Utility to partition/format your target HDD volume for OS X 10.6 as GPT/HFS+ volume named OSX_10.6_GPT_A (or your chosen name without spaces)

(2) Use Disk Utility to get the UUID for the OSX_10.6_GPT_A volume by going to Info tab in top menu bar after highlighting the OSX_10.6_GPT_A volume in the side bar, and making a careful note of the Universal Unique Identifier number:

It will be in this format (but obviously different!): CF2E12F1-2459-3DAF-B3D5-CA05B4B65A52

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

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 equiavlent to using root:wheel)

CODE

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.6 hard drive........

(3) Run EFIStudio or OSx86Tools to generate the graphics string for your graphics card assuming that it is OpenCL compatible.....save to clipboard (or in a text file) for later use in Section D Part 11B on modifying the com.apple.Boot.plist file......

(4) Run the Chameleon 2.0 RC1 Installer

"Presently IMHO Chameleon 2.0 RC1 bootloader with the netkas PC_EFI v10.1 boot file (and using -x32 kernel flag) is still the tried and tested method (that I personally have used) to use and/or fall back on should the following alternatives be problematic on your MOBO/system; e.g. failed installation, kernel panics, "bombing" of the system etc.....ESPECIALLY for the USB Flash drive OS 10.6. Installer which you definitely want to boot and work reliably...... (IMG:style_emoticons/default/wink_anim.gif) "

OR Alternative 1: Run the Chameleon 2.0 RC2 Installer

OR Alternative 2: Use Dr. Hurt's UNOFFICIAL installer to install Chameleon 2.0 RC3 completely

OR Alternative 3: Run dj nitehawk's Pre-Install Automator v1.1 script just to install Chameleon 2.0 RC3 completely

OR Alternative 4: Just use the Chameleon 2.0 RC3 boot file as explained below....

and after installing whichever Chameleon bootloader you have chosen, i.e. RC1 or RC2 or RC3, in the / directory of the OSX_10.6_GPT_A volume, you will see, either with the "hidden and system files" unhidden (see below how to do this) or listed in Terminal using

CODE

cd /Volumes/OSX_10.6_GPT_A/

ls

the following:

boot file

Extra folder

Library folder

usr folder

plus some ."name" files.....

(5) Now depending on what Chameleon 2.0 bootloader you have installed, you will have to choose the appropriate boot file to use and install it if not already installed......the boot file is normally a hidden file but you can unhide it, or use Terminal commands to overwrite it with a replacement boot file when you change from the "username" directory to the directory containing the replacement boot file....

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

UNHIDING HIDDEN FILES:

The Terminal commands to show/hide hidden and system files are:

QUOTE

To show hidden and system files:

CODE

defaults write com.apple.finder AppleShowAllFiles TRUE

killall Finder

To hide hidden and system files

CODE

defaults write com.apple.finder AppleShowAllFiles FALSE

killall Finder

or you can download and run TinkerTool 3.96......

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

Either delete the now visible Chameleon 2.0 RC1 boot file and then drag and drop the PC_EFI v10.1 (RECOMMENDED ONLY if Chameleon 2.0 RC1 has been installed) into the / directory.....and use the -x32 kernel flag in com.apple.Boot.plist.....

OR

If you have installed Chameleon 2.0 RC2, or prefer to install Chameleon 2.0 RC1 overlaid with the Chameleon 2.0 RC3 boot file, then go to the Chameleon website.....and look under Latest Releases for Chameleon-2.0-RC3-r658-bin.tar.gz [736.38KB]).......

Download and unarchive Chameleon-2.0-RC3-r658-bin.tar.gz to Chameleon-2.0-RC3-r658-bin and copy the RC3 boot file from the i386 folder over either the Chameleon 2.0 RC2 boot file or the Netkas PC_EFI v10.1 boot file in the / directory......and use the arch=i386 kernel flag in com.apple.Boot.plist.....

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

EXAMPLE OF OVERWRITING THE HIDDEN BOOT FILE

To copy the RC3 boot file across into the / directory of the OSX_10.6_GPT_A volume (see below), open Terminal, type the following commands ($ being the default shell prompt - DO NOT TYPE!)

cd followed by a space, and then drag and drop the i386 folder into the Terminal window

cp -f boot /Volumes/OSX_10.6_GPT_A/

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

OR

If you have installed Chameleon 2.0 RC3, then you can choose to use the installed RC3 boot file, or you can overwrite it with the netkas PC_EFI v10.3 boot file....and use the arch=i386 kernel flag in com.apple.Boot.plist.....

IMHO the Chameleon 2.0 RC2 bootloader is not to be recommended -

so, USE ONLY Chameleon 2.0 RC1 bootloader + PC_EFI v10.1 boot file.....

OR

Chameleon 2.0 RC3 bootloader with the RC3 boot file

OR

Chameleon 2.0 RC1 bootloader + RC3 boot file......

OR

Chameleon 2.0 RC3 bootloader with the netkas PC_EFI v10.3 boot file.....

as RC2 seems to only work with only a few PCs....

Interesting comment from Kabyl at netkas.org

QUOTE

People were having issues with the pkg installer in RC2, and it wasn't fixed yet, so until then there is no pkg installer for RC3. You can use the old installers and replace /boot if you don't want to install manually, and if you already are using Chameleon, you don't need the installer at all, just replace /boot with the new one.

BUT remember that to boot the mach_kernel into 32bit mode using the Chameleon 2.0 RC3 boot file requires you to use the arch=i386 kernel flag rather than -x32 as used with the netkas PC_EFI v10.1 boot file.....

If you have any problems booting from your HDD partition, then put either arch=i386 if using RC3 bootfile or -x32 if using PC_EFI v10.1 or V10.2 under Kernel Flags in /Library/Preferences/SystemConfiguration/com.apple.Boot.plist as well....

So, later in

/Extra/com.apple.Boot.plist and in /Library/Preferences/SystemConfiguration/com.apple.Boot.plist

find:

<key>Kernel Flags</key>

and change it to

<key>Kernel Flags</key>

(6) MODIFIED ADVICE: Many forum readers are having problems with the /Extra/Extensions cache file, i.e. Extensions.mkext not loading/working properly.....hence

If in the /Extra/Extensions, you installed all the kexts included in Chameleon 2.0 RC1 or RC2 or RC3 /Extra/Extensions,

OR if you only loaded one or two kexts in order for the /Extra/Extensions/ directory to be set up by the Chameleon Installer,

then delete them and from the downloaded Snow_Support_Files_V2.2,

that I have conveniently compiled in one folder for myself (NOTE: ALL CREDIT goes the developers of the included applications/kexts/bootloaders and boot files etc.; David Elliott, netkas, Superhai, Psystar, eno, slashack, AnV, Dr. Hurt.....),

copy across the following kexts:

ESSENTIAL

fakesmc.kext (32bit and 64bit compatible) -> emulates SMC to provide the information required for the Don't Steal Mac OS X.kext to decrypt the Apple encrypted files

"Choose either V2 or V1.......whichever "works" for you.......see Changelog for V2.2...."

NullCPUPowerManagement.kext (32bit and 64bit compatible) -> A problem with running OS X running on non-Apple hardware (both physically and in VM) is that the AppleIntelCPUPowerManagement.kext invariably causes a kernel panic or at bootup generates endless messages regarding the HPET and links to the CPU. AFAIK the NullCPUPowerManagement.kext plays a couple of tricks with the IOKit service registration process to take over the role of the AppleIntelCPUPowerManagement.kext, essentially disabling it. Also deals with heat issues.....

OpenHaltRestart.kext (32bit and 64bit compatible) -> fixes reboot and shutdown on PC-based machines without binary patching or recompiling the kernel

LESS ESSENTIAL

PlatformUUID.kext (32bit and 64bit compatible) -> Fixes some Time Machine related errors by providing a UUID from bootup (fixes UUID 35 errors)

ESSENTIAL FOR nForce Chipset MOBOs

AppleNForceATA.kext (32bit only at present - slashack's v0.1 kext or AnV's kext)

OPTIONAL FOR nForce Chipset MOBOsModified IONetworkingFamily.kext (from Snow Leopard but with nvenet.kext in Plugins renamed) - found in Snow_Support_Files_v2.2

plus

nForceLAN.kext (64bit - eno's kext) ONLY IF YOU ARE USING ONBOARD LAN (Enabled in BIOS)

"Other kexts (32bit or 32/64bit or 64bit) if/when available may be used and/or essential if they work on nForce chipset + Intel multicore CPU MOBOs with OS X 10.6......e.g. for enabling sleep, audio, graphics etc......"

(7) Drag and drop your previously modded and saved DSDT.aml file into the / directory

(8) Use TextEdit, Property List Editor, TextMate or your favourite .plist file text editor to modify the SMBIOS.plist template included in the Snow Support Files, to suit your system hardware/RAM etc.......

A further modification is to insert your OSX_10.6_GPT_A volume UUID number under/against SMUUID......and save the modified SMBIOS.plist and put it in /Extra

(9) Then go to PlatformUUID.kext, and Show Package Contents -> Contents -> Info.plist.....use TextEdit, Property List Editor, TextMate or your favourite .plist file text editor to modify the Info.plist and go to IOKitPersonalities -> PlatformUUID and insert your OSX_10.6_GPT_A volume UUID number under/against PlatformUUID and save the modified Info.plist file

(10) MODIFIED ADVICE: Many forum readers are having problems with the /Extra/Extensions cache file, i.e. Extensions.mkext not loading/working properly.....hence

If you get a kernel panic during booting as follows:

QUOTE

Kernel Extensions in backtrace (with dependencies):

com.apple.driver.AppleIntelCPUPowerManagement) and then some random numbers and letters or with references to HPET not being assigned to the CPU etc.

BSD process name corresponding to current thread: kernel_task

this indicates that for some reason NullCPUPowerManagement.kext is not taking over from the AppleIntelCPUPowerManagement.kext, as it should be, by being loaded into the kernel before the AppleIntelCPUPowerManagement.kext residing in /System/Library/Extensions, with its pathway in Extensions.mkext located at /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext......

This is because the Kext Utility.app did not build the the Extensions.mkext cache file pathway to NullCPUPowerManagement.kext in /Extra/Extensions properly properly (although it is probably setting the kext permissions correctly which is important).....so that NullCPUPowerManagement.kext is not being loaded into the kernel from Extenstions.mkext.....

Advice:

1. Delete the Extensions.mkext cache file from /Extra on your USB flash drive OS X Installer AND from /Extra on your target OS X volume.....

2. Copy "fresh" extensions across from Snow_Support_Files _V2.2 into the /Extra Directories

AppleNForceATA.AnV or AppleNForceATA.slash

fakesmc.V2 or fakesmc.V1

NullCPUPowerManagementOpenHaltRestart

PlatformUUID (although even different UUIDs in SMBIOS.plist and PlatformUUID Info.plist does not appear to cause any problems because according to Superhai the UUID in SMBIOS is not used for anything.....)

If an Extensions.mkext file is not present in /Extra the kexts in /Extra/Extensions will be loaded directly......the Extensions.mkext cache file being more of a convenience than a necessity at bootup in terms of a somewhat reduced bootup time; being a cached version of all the kexts in the Extensions folder, resulting in faster loading of the extensions at boot.

OS X continues to use the Extensions.mkext file until its modified date is different from that of the Extensions folder itself; at which point, it reverts to loading them from the Extensions folder and then re-creates the Extensions.mkext file......in Leopard (BUT NOT Snow Leopard at present) booting with -f forces the kexts to be loaded from the Extensions folder at bootup and then recreates the Extensions.mkext file....

(11) Use TextEdit, Property List Editor, TextMate or your favourite .plist file text editor to modify the com.apple.Boot.plist 32bit template included in the Snow Support Files to:

A. Boot the kernel into 32bit mode by entering either the arch=i386 kernel flag with the Chameleon 2.0 RC3 boot file installed OR the -x32 kernel flag with the PC_EFI v10.1 boot file installed under/against Kernel Flags in com.apple.Boot.plist

B. Provide graphics functionality for your PCI-E graphics card place the graphics string for your graphics card under/against device-properties in com.apple.Boot.plist

(12) Now save the modified com.apple.Boot.plist and put it in /Extra....

(13) Now close all open windows on the Desktop and any open applications...

(14) Download my nForceSLBoot132DVD.iso (Beta version) for PATA DVDRW OR my nForceSLBoot132DVD_for_SATA_DVDRW.iso (Alpha version)......

and use Disk Utility to burn either .iso file to a DVD-R or DVD+RW disk (because these are what I had and worked......) and when the DVDRW tray containing the burned DVD opens, close the DVDRW tray again.....

N.B. Burn the DVD at the slowest possible speed ≤ x4

(15) 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......" and when the PC BIOS "Boot Menu" window appears on-screen, select your DVDRW drive containing the Legacy Boot CD, i.e. nForceSLBoot132DVD from the list of bootable drives presented in the "Boot Menu", and press Enter......

(16) When the custom boot volume theme appears follow the onscreen instructions........namely when the Legacy Boot CD icon appears framed to the left of the display.........remove the nForceSLBoot132DVD from the DVDRW tray.......insert your Retail Snow Leopard Mac OS X Install DVD in the DVDRW tray and close...........wait for the initial DVDRW activity to occur (flashing DVDRW light) for a while to allow the DVD to be recognised......then press F5..........the Mac OS X Install DVD icon should then appear "framed" to the right of the display...

(17) Now type -v (space) -f at the boot: prompt that will appear (as usual with the Chameleon bootloader) in the bottom lefthand corner of the display.......I have asked to you use -v so that you can see what is happening (even though it messes up the friendly green Chameleon desktop) AND YOU MUST PRESS -f too.......

QUOTE

boot: -v -f

(18) After all the kexts have been loaded in the kernel, the OS X boot process should occur as normal and boot the Retail Snow Leopard Mac OS X Install DVD into the Installer screen..........where you can select your install destination and make you Customize menu choices.......

(19) REMEMBER that when you reboot your PC after install OS X, the BIOS in the CMOS memory will be reset to the default BIOS settings.......so press Del to enter your BIOS Setup and reload your custom BIOS settings into CMOS (hopefully from a saved BIOS profile......)

(20) When the PC reboots again into the Chameleon bootloader, choose the HDD volume onto which you have just installed Snow Leopard OS X 10.6 to boot from and your DSDT.aml file (with the CMOS reset fix) in /Extra will be loaded.......enjoy Snow Leopard......... (IMG:style_emoticons/default/biggrin.gif)

G. Points to note about running Snow Leopard (SL)

If choosing to do the following, first please note the advice about NOT generating an Extensions.mkext cache file for the kexts in /Extra/Extensions on the USB flash drive OS X Installer nor for the kexts in /Extra/Extensions on the OS X 10.6 installation(s) on your HDD(s)......

The number of kexts in /Extra/Extensions is small enough to have no significant impact on boot times but the benefits of loading the kexts directly from /Extra/Extensions are evident; e.g avoiding problems with kextcaching to generate the Extensions.mkext cache files properly, resulting in essential kexts not being loaded, such as NullCPUPowerManagement.kext......

Once you have installed and can boot SL on your HDD.......

1. If you, for whatever reason, have added a kext to /System/Library/Extensions, then to make sure that all your kext dependencies will be included in the /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext, re-create your /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext by booting into single user mode with:

-x32 -s or arch=i386 -s (whichever one you are using), and at the prompt:

CODE

mount -uw /

kextcache -v 1 -t -l -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions

("Type kextcache command line all in one line")

exit

2. To ensure that all your kext dependencies will be included in the /Extra/Extensions.mkext, re-create your /Extra/Extensions.mkext by booting into single user mode with:

x32 -s or arch=i386 -s (whichever one you are using), and at the prompt:

CODE

mount -uw /

kextcache -v 1 -t -l -m /Extra/Extensions.mkext /Extra/Extensions /System/Library/Extensions

("Type kextcache command line all in one line")

exit

Or if both steps are required....

CODE

mount -uw /

kextcache -v 1 -t -l -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions

("Type kextcache command line all in one line")

kextcache -v 1 -t -l -m /Extra/Extensions.mkext /Extra/Extensions /System/Library/Extensions

("Type kextcache command line all in one line")

exit

H. nForce chipset MOBO issues, including 32bit versus 64bit driver (kext) compatibility/availability

1. If you have a SATA DVDRW rather than a PATA DVDRW, and you have have some problems getting it to work......you could substitute MedDevil's AppleNForceATA Test kext for slashack's AppleNForceATA v0.1 kext or AnV's modified slashack AppleNforceATA kext to see if it works for you......

2. nForceLAN.kext may be problematic.......if you find that your installed OS X system has a kernel panic when booting, then reboot in verbose mode (-v flag) and look for problems linked to nForceLAN.kext loading....e.g. could not load early enough in boot process etc....

If there are problems with the nForceLAN.kext, then remove it from /Extra/Extensions and rebuild Extensions.mkext based on the new Extensions folder, as explained in step (10) above.....then try other nForceLAN.kext versions......

POSSIBLE Solution:

The nvenet.kext is problematic......this because nvenet loads even when another Ethernet/LAN kext has already been loaded for the hardware. In 10.5.7, and 10.5.8 and 10.6, it is located in

/System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns....

So, take a COPY of the IONetworkingFamily.kext from Snow Leopard, and go to its PlugIns folder to either remove nvenet.kext or rename it to nvenet.kext.bad.....then put this IONetworkingFamily.kext in /Extra....

Alternatively, the Netgear GA311 PCI NIC (Realtek RTL8169S chipset) works OTB giving instant internet/network access.....

3. If you are having unexplained kernel panics, then try netkas' Snow Leopard dsmos.kext and Kabyl's Leopard Disabler.kext in place of fakesmc.kext (v1 or v2) and NullCPUPowerManagement.kext.......they are in Snow_Support_Files_V2.2.......

4. Audio has now been fixed for the Asus P5N32E SLI Plus MOBO Asus SupremeFX audio card (except for Front Panel Hedaphones).....see post #2 in this thread...... (IMG:style_emoticons/default/biggrin.gif)

5. Sleep is still an issue to be dealt with......watch this space...... (IMG:style_emoticons/default/smile.gif)

I. Booting Snow Leopard from Leopard volume Chameleon 2.0 RC3 bootloader screen

Here is my procedure for booting SL from a Leopard volume Chameleon bootloader screen......

1. Install Chameleon 2.0 RC3 onto your Leopard volume using Dr. Hurt's Installer or run dj nitehawk's Pre-Install Automator v1.1 script just to install Chameleon 2.0 RC3

2. Google search for netkas' PC_EFI v10.3 boot file and download it

3. Replace the Chameleon 2.0 RC3 boot file with netkas' PC_EFI v10.3 boot file

4. In your Leopard volume, you will now have an /Extra directory, containing an Extensions folder (containing Disabler.kext.....?) and a Themes folder (as usual when installing the Chameleon bootloader.....)

5. Now into the /Extra directory on your Leopard volume, add a new folder named 10.6

6. Inside 10.6 add a folder named Extra, and inside this folder add a folder named Extensions

7. Inside /Extra/10.6/Extra/Extensions, place copies of the kexts from the /Extra/Extensions folder on your SL volume

8. Inside /Extra on your Leopard volume, place a copy of the com.apple.boot.plist from the /Extra directory on your SL volume, which should contain the graphics EFI string for your video card to enable full functioning with hardware acceleration, multiple resolutions and resolution switching etc. in SL.......

Note: When booting into Leopard, the com.apple.Boot.plist file in Library/Preferences/SystemConfiguration is loaded over this com.apple.Boot.plist......this is my guess......

You should now have something similar to this (although you may have additional kexts as required for your MOBO....):

10.6_in_Extra.png ( 25.54K ) Number of downloads: 4

9. To boot into your Leopard volume......do so as normal.......the Leopard volume icon will be framed.......so just press Return.....

10. To boot into your SL volume, use your arrow keys to frame the SL icon.....then press Return

To see what is happening, you can boot with -v......

IF you have error messages and/or KPs appearing then boot with

CODE

mach_kernel arch=i386

(the KP may have occured because you are running Leopard with the Voodoo kernel......the bootloader will/may look for mach_kernel.voodoo...... it depends how your Leopard com.apple.Boot.plist has been set up to load the Voodoo kernel.......also arch=i386 will ensure that SL boots in 32bit mode.......)

so that the boot: prompt appears in the bottom left-hand corner of the screen....

CODE

boot: mach_kernel arch=i386

then press Return......

Hopefully, you will now boot into SL from your Leopard volume's Chameleon bootloader.. (IMG:style_emoticons/default/thumbsup_anim.gif)

ALTERNATIVELY if you don't like typing in the "mach_kernel arch=i386" boot flags to boot SL, then you can install, set up and use (hopefully successfully....) xiezhy's Boot Think (version 2.3.18 currently......), which is an alternative bootloader to Chameleon 2.0.....

J. Previous Versions of Snow_Support_Files

Snow_Support_Files (V1.0)

Snow_Support_Files_V1.1 (includes Changelog V1.1)

Snow_Support_Files_V2.0 (includes Changelog V2.0)

Snow_Support_Files V2.1 (includes Changelog V2.1)

K. Developers/Contributors Corner

1. aqua-mac / aqua-mac http://rapidshare.com/files/300483215/Snow...ut_This_Mac.zip

QUOTE

By the way, here is a link to the Snow Leopard fixed HUD style "About this Mac" window as I see a few of you have asked the question - is it available. There is a backup of the original file as well as some that I made. Thanks to Toastido.

The modified AboutThisMac.nib file will make your "About this Mac" window "transparent".....

Here is my About This Mac to show that it works:

TransparentAboutThisMac.png ( 261.29K ) Number of downloads: 5

2. Giorgio_multi / Giorgio_multi NVinject_SLI

QUOTE

I send you my modified nvinject.kext working with 2 Graphics card in Snow. (only 32 bit)

It works also with 1 graphic card and in Leopard.

I'm working for 64 bit version, but I have some problems.

If you want add this kext to your guide, there is no problem.

The 2 graphics cards must have the same amount of RAM, but can have different CPUs (i.e a 8500GT and a 9600GT)

3. Developer....? / j o e l http://rapidshare.com/files/281901335/speedupsl_nforce.zip

QUOTE

I managed to speed up the boot time by using this nForceIOATAFamily.kext

I think the kext is 32bit so you would need to use arch=i386 or -x32 when booting, depending on your bootloader....

Installation: Place nForceIOATAFamily.kext in the same folder as AppleNForceATA.kext (Unix executable file in the folder is not run)

Note: I have compared the Info.plist of nForceIOATAFamily.kext with that from the IOATAFamily.kext from 10.5.6.....the only apparent difference is in the OSBundleRequired property value.....

IOATAFamily.kext from 10.5.6 value is Local-Root

nForceIOATAFamily.kext value is Root

QUOTE

Usage of OSBundleRequired property value:

Root -> This KEXT is required to mount root, regardless of where root comes from; for example, platform drivers and families, PCI, or USB.

Network-Root -> This KEXT is required to mount root on a remote volume; for example, the network family, Ethernet drivers, or NFS.

Local-Root -> This KEXT is required to mount root on a local volume; for example, the storage family, disk drivers, or file systems.

Console -> This KEXT is required to provide character console support (single-user mode); for example, keyboard drivers or the ADB family.

Safe Boot -> This KEXT is required even during safe-boot (unnecessary extensions disabled); for example, mouse drivers or graphics drivers.

BUT be aware that when a kext's OSBundleRequired property is set to “Root”, it will always be loaded by BootX, even in single-user or safe-boot modes.....so, should the kext panic, the system itself may panic, requiring reinstallation of the OS or booting off the Mac OS X Install DVD.....therefore, unless a KEXT is absolutely required to mount root, its OSBundleRequired property should not be set to 'Root'.....

Plus that in PlugIns of nForceIOATAFamily.kext you have:

nForceAppleGenericPCATA.kext

nForceAppleIntelPIIXATA.kext

nForceIOATABlockStorage.kext

nForceIOATAPIProtocolTransport.kext

all with their OSBundleRequired property value set as 'Root', whereas in PlugIns of the 10.5.6 IOATAFamily.kext you only have:

AppleIntelPIIXATA.kext

IOATABlockStorage.kext

IOATAPIProtocolTransport.kext

all with their OSBundleRequired property value set as 'Local-Root'.....

Nevertheless, the nForceIOATAFamily.kext reduces the boot time to about 30 seconds on my SL system..... (IMG:style_emoticons/default/smile.gif)

Attached File(s)

Chameleon_Root_Pre_OSX_Install_H.png ( 58.67K ) Number of downloads: 69

Picture_1.png ( 136.32K ) Number of downloads: 97

Chameleon_Root_Pre_OSX_Install_U.png ( 47.95K ) Number of downloads: 115

juanmacrack93 · November 8, 2009

This is terrible! I hate it when information is lost. Hope you can get everything back quickly.

verdant · November 8, 2009

This is terrible! I hate it when information is lost. Hope you can get everything back quickly.

Thanks.

You can imagine my shock on seeing the 100% OK preview information not appearing after I pressed "Submit".....and no way back.....

I wish the IM system saved backups and allowed post auto-recovery when editing......saving local text copies and browser cached versions is not as time-saving.....

Here is a modified voodoohda.kext by slice with fixed nids by me for complete ad1988b support. Everything works, even 7.1 surround (using midi utility). The only things that doesn't work is auto sensing/switching between front headphone e back green line-out, so I kept them separeted. Enjoy

VoodooHDA.kext.zip

Thanks, I have tried it now......

I have put your modded slice VoodooHDA.kext in /E/E and created a sym link in /S/L/E......but it needs to have its permissions set as 755........

The Front Panel Headphones (Green) work now and I can manually switch to Rear Panel Green Line-Out......cannot test Front Panel Microphone......but in System Profiler under Audio (Built In) I see

Intel High Definition Audio:

Device ID: 0x104381F2

Audio ID: 12

Audio Devices:

i.e. no devices are showing....

Cheers

verdant

eldub · November 8, 2009

Hi User,

German

Ich habe den Ruhezustand endlich auf dem Board Asus P5N-E SLI zum laufen bekommen . Ihr müst einfach nur die Treiber Installieren die ich ihr hochgeladen habe und dann noch ein paar Bios Einstellungen machen. Am besten wie ich auf eine anderen Partition erst Testen. Ich bin immer noch in der Test Phase, aber bis jetzt läuft es sehr gut. Vieleicht läuft es auch dann auf andere Board's. Ich Bitte um Feedback.

Der Ruhezustand geht nur wenn Snow Leopard auf einer IDE Platte Installiert ist.

Englisch

I finally got to sleep on the board Asus P5N-E SLI to run . It must be installed only the drivers that I've uploaded it and then make a few bios settings. Best as I only play on a different partition. I'm still in the testing phase, but so far it runs very well. Maybe it runs also on other's board. I am asking for feedback.

The sleep is only when Snow Leopard is installed on an IDE disk.

Asus_P5N-E_SLI.zip

/dsdt.aml

/Extra/com.apple.Boot.plist

/Extra/SMBIOS.plist

/System/Library/Extensions/AHCIPortInjector.kext

/System/Library/Extensions/AppleNForceATA.kext

/System/Library/Extensions/fakesmc.kext

/System/Library/Extensions/IOAHCIBlockStorageInjector.kext

/System/Library/Extensions/NullCPUPowerManagement.kext

/System/Library/Extensions/OpenHaltRestart.kext

/System/Library/Extensions/PlatformUUID.kext

/System/Library/Extensions/VoodooHDA.kext

Hi, I had a question...

I have everything running on my dell XPS 720 (nvidia nforce 680i), except sleep...

I'm using SATA drives... what exactly do I need to do to try this out? (in other words, which kexts/dsdt do i need to replace)...

is there any harm in me trying?? I've been working all day making this work and don't want to lose my setup now

and also, thank you SO MUCH for this guide and all your work. I used your kexts with a USB install method i found at http://prasys.co.cc/2009/08/installing-sno...pard-for-osx86/

I have to say, SL works muuuuch better than the iPC 10.5.6 i was using previously!

ehh · November 8, 2009

Any luck with sleep?

verdant · November 8, 2009

@ eldub

Not sure if your question is for artsin or myself.....

@ ehh

At present I just do not sufficient time to sit down and focus just on modding my DSDT further, so no progress on sleep yet.....losing post #1 is a time-taker too and getting it fixed will have to be done first too.....

ehh · November 8, 2009

Totally understandable. Thanks

eldub · November 8, 2009

@ eldub

Not sure if your question is for artsin or myself.....

@ ehh

At present I just do not sufficient time to sit down and focus just on modding my DSDT further, so no progress on sleep yet.....losing post #1 is a time-taker too and getting it fixed will have to be done first too.....

sorry yeah, it was for either of you...

i believe you answered it by saying you were finishing redoing the guide before working on sleep....

jallardyce · November 10, 2009

Hi,

Please help, i have problems!

my setup is as follows;

xfx nforce 650i ultra motherboard

intel quad core 2.66 gHz cpu

geforce 8600 GTS grapics card

8Gb RAM

I followed this guide to install snow leopard 10.6 http://lifehacker.com/5351553/hackintosh-b...lery//gallery/1 using, where required, a friends borrowed macbook for the terminal bits. I have set up an external HD as the snowleopard install disk.

After some initial display problems, i managed to set up my graphics card using the "snow leopard support files 2.2" archive, allowing me to view the install process via the vga output from the graphics card.

However, during the darwin/install process, i am still encountering some problems...

Using the verbose-mode install, the following is stated:

>> boot cache control could not unlink playlist\var\bootcache.playlist read only file system

- this is inspite of returning to the mac to set the file as read/write for all users

>> panic cpu caller ( 0x...) "CPU 1 has no HPET assigned to it"\sourcecache\appleintelcpupowermanagement\appleintelcpupowermanagement-90\pmthread.c:164

followed by output from the debugger.

>> BSD process name corressponding current thread-kernel_task

>> Mac OS Version

>> 10A432

>> kernel version:

>> Darwin Kernel version 10.0.0: Fri Jul 31 22:46:25 PDT 2009: too:xnu-1456.1.25~1/RELEASE_X86_64

>> system model name: MacPro3.1

>> system uptime in nano seconds: ....

and at this point the process hangs.

Any help in identifing what has gone wrong, and how to correct it would be appreciated. Thanks.

ehh · November 10, 2009

Isn't the Lifehacker guide for the Gigabyte UD3P motherboard?

Anyways, successfully updated to 10.6.2. Proceeded with caution and followed http://prasys.co.cc/2009/11/tutorial-upgra...-to-osx-10-6-2/

macman12 · November 10, 2009

Hi!

updated to 10.6.2 without problems

from software update

about losing the topic..

What A disaster!!!!

BTW Thanks to google Cache system..

i have a much later backup :

"This is Google's cache of http://www.insanelymac.com/forum/index.php?showtopic=184224. It is a snapshot of the page as it appeared on 5 Nov 2009 18:39:53 GMT"

I dont think this will help very much but dunno may help

Link:

http://209.85.229.132/search?q=cache:jzxpN...=en&ct=clnk

or text:

This guide is:

1. Split into sections and sub-sections for ease of following and adding to....

2. A "live guide" that will evolve with both Snow Leopard 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 a printed-out static version successfully.....

3. How do I use this guide most efficiently?

Read Part A, then Part B......then:

Read Part C if you want to produce a USB flash drive installer......

and then

Part D if you want to install from a USB flash drive to a GPT HDD.....

OR

Part E if you want to install from a USB flash drive to a MBR HDD.....

OR

Part A, then Part B......then:

Read Part F if you want to install from a Retail Snow Leopard Mac OS X Install DVD to a GPT HDD using my nForceSLBoot132DVD......

THEN

Read Part I if you want to be able to boot into Snow Leopard from your Leopard Chameleon bootloader screen......

FINALLY

After successful installation read Parts G to K periodically to keep up to date with the development of non-Apple Snow Leopard 64bit kexts and their operation (e.g. audio, sleep etc.) and/or DSDT modding on nForce chipset/Intel CPU MOBOs....... (IMG:style_emoticons/default/smile.gif)

4. Are there any special points to note?

Yes.....remember that despite nForce chipset MOBOs now being able to run the Snow Leopard kernel, you still are dealing with the nForce chipset and OS X.......So:

[1] Check your BIOS settings against the recommended settings for OS X........depending on your MOBO nForce chipset, check in either my Series 7 nForce chipset + Intel CPU thread or in my Pre-Series 7 nForce chipset + Intel CPU thread......

Ensure that your IDE/SATA settings are set correctly e.g. enabling the SATA Controller or AHCI Mode depending on your BIOS options, and setting HPET Function/Support to [Enabled]....

[2] Despite a number of vanilla install guides for Snow Leopard saying that a SATA DVDRW is recommended/best/required for installing Snow Leopard.......this is not generally the case with nForce chipset MOBOs (unless the nForce MCP is fully AHCI compliant e.g. MCP73......see here)......

If the nForce MCP is not fully AHCI compliant, then a PATA (IDE) DVDRW is preferred/recommended to avoid issues with the now infamous "still waiting for root device" error.....

This is because we have to use the AppleNForceATA.kext.......currently still only available as 32bit compiled......

However, while slashhack's v0.1 AppleNForceATA.kext (32bit) supports 64bit memory addressing enabling the use of >3GB RAM, some SATA DVDRWs may have problems with this kext......e.g. not being recognized; a SAM Multimedia: Read or Write failed.....error; not being able to burn CDs/DVDs....

So, if this is the case you will need to use MeDevil's AppleNForceATA_Test.kext BUT this kext can only be used with maxmem=3072 in com.apple.Boot.plist or with > 3GB RAM as it does not support 64bit memory addressing.....you may still have issues with not being able to burn CDs/DVDs.......

[3] If you are using a IDE HDD and/or IDE DVDRW, then the IDE cable connections are very important.......

80-wire IDE cable with end Master connector and middle Slave connector

IDE HDD/DVDRW :

IDE HDD jumper set as Slave with IDE DVDRW jumper set as Master

SATA HDD/IDE DVDRW :

IDE DVDRW jumper set as Master

IDE HDD/SATA DVDRW :

IDE HDD jumper set as Master

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

BREAKING NEWS:

1. Aqua-mac has kindly provided a Snow Leopard HUD style ("transparent") "About this Mac" window fix.....see section K.

2. Audio has now been fixed for the Asus P5N32-E SLI Plus MOBO Asus SupremeFX audio card (except for Front Panel Headphones).....see post #2 in this thread...... (IMG:style_emoticons/default/biggrin.gif)

3. Booting into Snow Leopard from your Leopard volume's Chameleon 2.0 RC3 bootloader screen.....using netkas' PC-EFI v10.3 boot file......see Part I......

4. My two nForceSLBoot132DVD.iso files are now uploaded..... (IMG:style_emoticons/default/biggrin.gif)

Two versions are available:

One using slashack's v0.1 AppleNForceATA.kext for PATA DVDRW (now in Beta version)

One using MeDevil's AppleNForceATA_Test.kext for SATA DVDRW (now in Alpha version)......

For links to both versions and user instructions, please see Part F. below..........enjoy (IMG:style_emoticons/default/biggrin.gif)

N.B. Burn either .iso to DVD at the slowest possible speed ≤ x4

Please report any problems/issues with either .iso in this thread.......

Thank you......verdant (IMG:style_emoticons/default/smile.gif)

5. An original kext/modified kext/driver "Developers/Contributors Corner" has been set up in Part K (the originator/developer is acknowledged together with the contributor when the developer is known...if any reader can add such information please post the information so that the developers can be properly credited....thank you, verdant...... (IMG:style_emoticons/default/smile.gif)

6. Snow_Support_Files_V2.2 now includes netkas' Snow Leopard dsmos.kext and Kabyl's Leopard Disabler.kext to use if required in place of fakesmc.kext (v1 or v2) and NullCPUPowerManagement.kext, as well as fakesmc V1 and V2 and nForceLAN plus modified IONetworkingFamily.kext, AnV's and slashack's AppleNForceATA kexts....other necessary stuff plus useful uitilities... (IMG:style_emoticons/default/wink_anim.gif)

7. Modified advice regarding kexts in /Extra/Extensions and Extensions.mkext.....

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

WARNING: May apply to nForce chipset MOBOs too

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

QUOTE

@d00m42