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

[verdant]

I don't quite remember, something about osx not set up. I thought I had messed up my computer so I restarted my computer.

 

But I'm a little bit confused here. What is the process I'm trying to do here, because I obviously can't boot with a usb flash drive. Am I supposed to copy the sl image to a partition and make it bootable? or do I just copy it straight to the partition I'd created from the very beginning with my OSX_BACKUP and install from there. There's just so much information in your guide, and it's not tailored to my situation so I'm kind of stuck. Maybe if I understand the objective of what I'm supposed to do, then it'll easier.

 

In any case, thanks for being patient with me and still trying to help. I really appreciate it.

 

You are using your Leopard OS X system to:

 

1. Generate a RTC patched DSDT.aml file for SL [Part B]

 

2. Format a HFS+ volume as your target SL OS X volume (OSX_BACK) and format a temporary OS X SL Retail DVD volume (use OSX_BOOT or OSX_SL) on your MBR partitioned HDD using Disk Utility

 

"I would recommend you use OSX_SL so that there is no risk of messing up OSX_BOOT"

 

3. Use Disk Utility to get the UUID for your target SL OS X volume

 

4. Establish OS X target HDD ownership (Part D)

 

5. Run EFIStudio or OSx86Tools to generate the graphics string for your graphics card (Part D)

 

6. Install Chameleon 2.0 RC3 (or RC4) onto your target SL OS X volume (OSX_BACK) and in the process generate a /Extra directory.....

 

7. Follow Part D from section (6) to (13) inclusive

 

8. Use Disk Utility to restore a Retail Mac OS X 10.6 Install DVD .dmg/.iso image file to a temporary OS X SL Retail DVD Installer volume (use OSX_SL) from which to run the SL Installer

 

9. Get the OSInstall.mpkg and OSInstall Unix executable file for MBR installation and backup default versions in the Retail Mac OS X 10.6 Install DVD .dmg/.iso image file.......then replace them with the MBR versions......

 

From my post #1 Part E Procedure 1, modifed for installation using a running Leopard OS X system:

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 in all Leopard directories/folders using Terminal commands or Tinker Tool (see Part C.)

 

2. Go to Terminal and type

 

cd /Volumes/OSX_SL/System/Installation/Packages/

 sudo mv OSInstall.mpkg OSInstall.mpkg.GPT

 cd /Volumes/OSX_SL/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 :

 

cd /Volumes/OSX_SL/System/Installation/Packages/

 sudo mv OSInstall.mpkg.GPT OSInstall.mpkg

 cd /Volumes/OSX_SL/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_SL/System/Installation/Packages/

 

4. Then drag and drop (or use cp command via Terminal) OSInstall into /Volumes/OSX_SL/System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A/

 

 

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

10. Mount the Snow Leopard .dmg/.iso file......an installer pop-up window will appear......now click on any free-space region within the window/Desktop and then go to top menu bar and click on Go > Go to Folder......a pop-up window will appear….in the window entry box, type

 

Mac OS X Install DVD/System/Installation/Packages/

And click on Go......in the next window that appears, find the now modified OSInstall.mpkg file/icon and double-click this package file to start your Snow leopard Installation......

 

11. Now follow on from the last instruction in section (16) to section (18)......

[MasterTiiro]

I understand about the DSDT.aml file, graphics string, chameleon and osinstall.mpkg, so we'll put them aside for now. What I don't get is the partitioning part. Right now I have 3 partitions - 5,6 and 1(OSX_SL, OSX_BACK AND OSX_BOOT) on disk 1, respectively. As of right now OSX_SL is empty, as this is the volume I will eventually install SL on, OSX_BACK AND OSX_BOOT have exactly the same OS X(10.5.8). Tell me if I did this right. I shrunk down 10gb from windows' HDD(disk 0) to be used as a sl retail dvd installer volume(OSX_INSTALL). I then patched my DSDT.aml file and set it aside. I restored SL retail DVD image to OSX_INSTALL and placed the modified OSInstall.mpkg and OSInsall files onto it. I then also installed Chameleon onto OSX_INSTALL. So at this point the retail dvd image is on OSX_INSTALL with the modified OSInstall.mpkg and OSInstall files. Am I missing any step up until now?

 

Then out of curiosity, I clicked the modified OSInstall.mpkg within OSX_INSTALL volume while running Leopard(OSX_BACK), and it said "you can install from this volume". So ok, I'll just restart and boot from volume OSX_INSTALL then, I said. After reboot, I chose OSX_INSTALL from Chameleon menu and it got stuck on the loading screen.....

[verdant]

I understand about the DSDT.aml file, graphics string, chameleon and osinstall.mpkg, so we'll put them aside for now. What I don't get is the partitioning part. Right now I have 3 partitions - 5,6 and 1(OSX_SL, OSX_BACK AND OSX_BOOT) on disk 1, respectively. As of right now OSX_SL is empty, as this is the volume I will eventually install SL on, OSX_BACK AND OSX_BOOT have exactly the same OS X(10.5.8). Tell me if I did this right. I shrunk down 10gb from windows' HDD(disk 0) to be used as a sl retail dvd installer volume(OSX_INSTALL). I then patched my DSDT.aml file and set it aside. I restored SL retail DVD image to OSX_INSTALL and placed the modified OSInstall.mpkg and OSInsall files onto it. I then also installed Chameleon onto OSX_INSTALL. So at this point the retail dvd image is on OSX_INSTALL with the modified OSInstall.mpkg and OSInstall files. Am I missing any step up until now?

 

Then out of curiosity, I clicked the modified OSInstall.mpkg within OSX_INSTALL volume while running Leopard(OSX_BACK), and it said "you can install from this volume". So ok, I'll just restart and boot from volume OSX_INSTALL then, I said. After reboot, I chose OSX_INSTALL from Chameleon menu and it got stuck on the loading screen.....

 

Yes......when it says you can "you can install from this volume" it means that you can run the Installer from OSX_INSTALL (using OSX_BACK)........

[MasterTiiro]

haha, I feel so foolish. What I meant was "you CAN'T install from this volume". Can we really run the installer from the desktop of osx of another partition?

 

And the DSDT.aml file is for placing in the root of SL after it's installed, correct?

[verdant]

haha, I feel so foolish. What I meant was "you CAN'T install from this volume". Can we really run the installer from the desktop of osx of another partition?

 

And the DSDT.aml file is for placing in the root of SL after it's installed, correct?

 

 

Make a .dmg image of the now modified SL Retail DVD files on OSX_INSTALL and mount it on the Desktop in OSX_BACK and try running the installer directly from OSX_BACK.....

 

DSDT.aml can be put in / or in /Extra......or in both, so long as the DSDT.aml files are identical.....that way it will get loaded no matter what........

[MasterTiiro]

Making an image seemed to work, but once the installer got up to about 60%, it gave me "Installation Error"

 

[verdant]

Making an image seemed to work, but once the installer got up to about 60%, it gave me "Installation Error"

 

 

Did you open the Installer Log window........and choose Show Errors and Progress......or Show All Logs......? It is GOOD PRACTICE to do so when running any Installer package.....

 

See Part D. below section (18).......this method WILL give you errors and possibly kernel panics!.......that is why my guide recommends the USB flash drive install method OR my nForceSLBoot132DVD install method.......and does not cover the OSInstall.mpkg method in any detail except in Part E for MBR partition installation......I view it as a last-resort method........it can be made to work, see See Part D. below section (18) with the heading

 

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

[MasterTiiro]

Alright, I think I'll try out your nForceSLBoot132DVD method. I'll report back on my progress with that....

[gateway69]

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.

 

anyone ever get the LAN driver working with this motherboard, or did you insert a new one, if so which nic card?

[verdant]

anyone ever get the LAN driver working with this motherboard, or did you insert a new one, if so which nic card?

 

Use eno's nForceLAN kext......see here........alternatively, use a Gigabit NIC with a Realtek RTL8169 chipset, such as the Netgear GA311.......

 

As for onboard LAN affecting sleep, disabling Wake on LAN in BIOS may solve the issue......

[lottomotto]

Hello,

 

tahnks a lot for your work. is amazing, clear and professional.

 

I have my striker ii extreme runnig sl for few months now.

 

what I was trying to do now is run in 64bit mode. I used the program 32- or 64-bit Kernel Startup Mode Selector

http://www.ahatfullofsky.comuv.com/English...ms/SMS/SMS.html

but it tells me that I have a 32bit efi.

what should I do to change it to 64-bit?

 

thanks in advance

[verdant]

Hello,

 

tahnks a lot for your work. is amazing, clear and professional.

 

I have my striker ii extreme runnig sl for few months now.

 

what I was trying to do now is run in 64bit mode. I used the program 32- or 64-bit Kernel Startup Mode Selector

http://www.ahatfullofsky.comuv.com/English...ms/SMS/SMS.html

but it tells me that I have a 32bit efi.

what should I do to change it to 64-bit?

 

thanks in advance

 

Glad you find my guide clear and helpful.....

 

It probably tells you this because your PC like the vast majority, uses a BIOS, whereas EFI is what Apple uses instead of a BIOS......OSx86 PCs use EFI emulation via the Chameleon bootloader for example......but only Intel CPUs with SSSE3 can run 64bit kernel/apps e.g. Core2 / Core i7 etc. CPUs......using arch=x86_64 in com.apple.Boot.plist etc.

 

To boot into 64bit mode, you need to ensure that all of your 3rd-party, i.e. non-Apple Snow Leopard kexts are 64bit kexts, or can run in either 64bit or 32bit modes.....however, I am not yet aware of a proven 64bit AppleNforceATA kext........the current slashack AppleNForceATA v0.1 kext is 32bit only......

[lottomotto]

Hello,

 

 

thanks a lot for your reply.

I was thinking to try the Applenforceata of your braking news that could work.

I think is the only third party not 64 bit.

can you help me to double check?

 

in about his mac, more info, software, extentions I have only this files with the NO under 64-bit intel

 

applNorceATA.Anv

BSDKernel6.0

IOKit6.0

Libkern6.0

Ispicdrv

Mach6.0

System6.0

 

one more question and sorry to bother so much

If I add the flag arch=x86_64 what happens if some kext is x86?

it doesn't boot anymore or, boots in x86 mode?

 

thanks a lot a really appreciate your work, is actually becaus of your effort that my main system is Snow Leo

 

Simone

 

Glad you find my guide clear and helpful.....

 

It probably tells you this because your PC like the vast majority, uses a BIOS, whereas EFI is what Apple uses instead of a BIOS......OSx86 PCs use EFI emulation via the Chameleon bootloader for example......but only Intel CPUs with SSSE3 can run 64bit kernel/apps e.g. Core2 / Core i7 etc. CPUs......using arch=x86_64 in com.apple.Boot.plist etc.

 

To boot into 64bit mode, you need to ensure that all of your 3rd-party, i.e. non-Apple Snow Leopard kexts are 64bit kexts, or can run in either 64bit or 32bit modes.....however, I am not yet aware of a proven 64bit AppleNforceATA kext........the current slashack AppleNForceATA v0.1 kext is 32bit only......

[verdant]

Hello,

 

 

thanks a lot for your reply.

I was thinking to try the Applenforceata of your braking news that could work.

I think is the only third party not 64 bit.

can you help me to double check?

 

in about his mac, more info, software, extentions I have only this files with the NO under 64-bit intel

 

applNorceATA.Anv

BSDKernel6.0

IOKit6.0

Libkern6.0

Ispicdrv

Mach6.0

System6.0

 

one more question and sorry to bother so much

If I add the flag arch=x86_64 what happens if some kext is x86?

it doesn't boot anymore or, boots in x86 mode?

 

thanks a lot a really appreciate your work, is actually becaus of your effort that my main system

is Snow Leo

 

Simone

 

Hi Simone

 

Thanks for the appreciation......glad my guide helped you to make SL your main system...

 

On my system, I currently have these non-64bit kexts:

 

AppleNForceATA.64AnV (all the AppleNForceATA I have tried have only functioned in 32bit mode)

BSDKernel6.0

CHUDKernLib

CHUDProf

CHUDUtils

IOKit6.0

Libkern6.0

Ispicdrv

Mach6.0

System6.0

 

All the AppleNForceATA kext versions (even so-called 64bit kexts) I have tried have only functioned in 32bit mode......thus, I have not been ablle to boot using arch=x86_64.......

 

In Terminal type:

ioreg -l -p IODeviceTree | grep firmware-abi

and if the response is

"firmware-abi" = <"EFI32">

rather than

"firmware-abi" = <"EFI64">

then your system cannot be booted into a 64bit kernel.......

 

However, do not be too worried by this, as you can run your 64bit-aware applications as 64bit and they will take advantage of all the RAM you have installed, even up to 32GB (see below).....this has been/is true even in the case of Leopard 10.5.x......

 

Obviously, in the case of nForce chipset MOBOs with >3GB RAM installed, you have to run slashack's AppleNForceATA.kext or AnV's variant of it (unless the MCP is fully AHCI-compliant; see here)

 

In fact, booting into a 64bit kernel is only really advantageous with >32GB RAM, my understanding from reading around is that while a 32bit kernel and 32bit applications can work with >32GB RAM, the 32bit kernel/applications can only address 4GB of RAM at a time.....and since kernel structures e.g. the page table, expand as RAM increases, when the 32bit kernel structures hit the 4GB RAM access limit during kernel operation, the system will experience a kernel panic and crash......this RAM limit is apparently at some level not too far above 32GB, hence the stated 32GB limit (because no current "real" Mac can support more than 32GB RAM)........

 

But is is very beneficial (according to testing done by others), even in Leopard, when running 64bit aware applications, to uncheck the “Open in 32 Bit Mode” option in the application's "Get Info" pop-up window.......

[lottomotto]

Thanks a lot for your replyonce again.

I have 8gb of ram, so if I undestand well I might get kernel panics if I use lot of programs?

didnt know about the 64bit option in get info.

will do it now.

 

 

 

so we have to wait for the proper applenforceata to tryout the 64bit kernel.

 

thanks again

 

Simone:)

 

Hi Simone

 

Thanks for the appreciation......glad my guide helped you to make SL your main system...

 

On my system, I currently have these non-64bit kexts:

 

AppleNForceATA.64AnV (all the AppleNForceATA I have tried have only functioned in 32bit mode)

BSDKernel6.0

CHUDKernLib

CHUDProf

CHUDUtils

IOKit6.0

Libkern6.0

Ispicdrv

Mach6.0

System6.0

 

All the AppleNForceATA kext versions (even so-called 64bit kexts) I have tried have only functioned in 32bit mode......thus, I have not been ablle to boot using arch=x86_64.......

 

In Terminal type:

ioreg -l -p IODeviceTree | grep firmware-abi

and if the response is

"firmware-abi" = <"EFI32">

rather than

"firmware-abi" = <"EFI64">

then your system cannot be booted into a 64bit kernel.......

 

However, do not be too worried by this, as you can run your 64bit-aware applications as 64bit and they will take advantage of all the RAM you have installed, even up to 32GB (see below).....this has been/is true even in the case of Leopard 10.5.x......

 

Obviously, in the case of nForce chipset MOBOs with >3GB RAM installed, you have to run slashack's AppleNForceATA.kext or AnV's variant of it (unless the MCP is fully AHCI-compliant; see here)

 

In fact, booting into a 64bit kernel is only really advantageous with >32GB RAM, my understanding from reading around is that while a 32bit kernel and 32bit applications can work with >32GB RAM, the 32bit kernel/applications can only address 4GB of RAM at a time.....and since kernel structures e.g. the page table, expand as RAM increases, when the 32bit kernel structures hit the 4GB RAM access limit during kernel operation, the system will experience a kernel panic and crash......this RAM limit is apparently at some level not too far above 32GB, hence the stated 32GB limit (because no current "real" Mac can support more than 32GB RAM)........

 

But is is very beneficial (according to testing done by others), even in Leopard, when running 64bit aware applications, to uncheck the “Open in 32 Bit Mode” option in the application's "Get Info" pop-up window.......

[verdant]

Thanks a lot for your replyonce again.

I have 8gb of ram, so if I undestand well I might get kernel panics if I use lot of programs?

didnt know about the 64bit option in get info.

will do it now.

 

 

 

so we have to wait for the proper applenforceata to tryout the 64bit kernel.

 

thanks again

 

Simone:)

 

Not quite........if you boot in 32bit mode and use slashack's AppleNForceATA kext, you should be able to use 8GB RAM without any issues.......possibly even up to 32GB.....but if there are any issues with the amount of RAM, it will be with the AppleNForceATA kext rather than OS X and its own kexts.....you could do a memory test using Memory Tester......other options are Rember and Memtest......

 

Yes, we need a proven fully functioning 64bit version of AppleNForceATA before we can boot into 64bit mode......

[lottomotto]

I have a doubt the applenforceata is the kext for just ATA or also controls the usb?

 

SImone

 

Not quite........if you boot in 32bit mode and use slashack's AppleNForceATA kext, you should be able to use 8GB RAM without any issues.......possibly even up to 32GB.....but if there are any issues with the amount of RAM, it will be with the AppleNForceATA kext rather than OS X and its own kexts.....you could do a memory test using Memory Tester......other options are Rember and Memtest......

 

Yes, we need a proven fully functioning 64bit version of AppleNForceATA before we can boot into 64bit mode......

[verdant]

I have a doubt the applenforceata is the kext for just ATA or also controls the usb?

 

SImone

 

There are separate kexts for USB I/O and for SATA/PATA I/O.......but the MOBO nForce Southbridge chipset controls data storage I/O.......see end of post #1 here and here......

[tnap1979]

i have prepared to take a jump at this myself,

if you look at my sig, that is the hardware im testing on,

i followed the post #1 according to my hardware,

 

ive used updated stuff like chameleon RC5 pre8 V2 and EFI 10.6

applenforceata.kext from breaking news,

modified smbios.plist and com.apple.Boot.plist

nullcpupowermanagement.kext

openhaltrestart.kext

nforcelan.kext

fakesmc.v2.kext

my generated DSDT.aml file made from my succesful osx 10.5.6 install

 

will post success or failure when i test it out in a bit

[verdant]

i have prepared to take a jump at this myself,

if you look at my sig, that is the hardware im testing on,

i followed the post #1 according to my hardware,

 

ive used updated stuff like chameleon RC5 pre8 V2 and EFI 10.6

applenforceata.kext from breaking news,

modified smbios.plist and com.apple.Boot.plist

nullcpupowermanagement.kext

openhaltrestart.kext

nforcelan.kext

fakesmc.v2.kext

my generated DSDT.aml file made from my succesful osx 10.5.6 install

 

will post success or failure when i test it out in a bit

 

Hi there,

 

It would be good to know how the chameleon RC5 pre8 V2 and EFI 10.6 work for you......the reason I have not updated my Software_Support_Files is that what is currently included works, enabling SL to be installed and then run successfully.....users can then update as far as they wish.....when the release version of RC5 is out I will do a test install and then update the guide......as I will only include stuff that is proven to work for myself and others......

[tnap1979]

well here is the news

 

i rebooted, and choose to manually boot from the usb made device,

i did not use any kernel flags at boot, only what was put into the modified plist

and it booted me into my monitor telling me that i had no hdmi signal,

but my usb stick was still flashing for activity, the led light stopped flashing,

i assumed i had booted into something, and i restarted and loaded my 10.5.6

 

i cannot see therefore i cannot conclude if it was a successful boot or not,

 

any ideas as to why my graphics just gave out..

[verdant]

well here is the news

 

i rebooted, and choose to manually boot from the usb made device,

i did not use any kernel flags at boot, only what was put into the modified plist

and it booted me into my monitor telling me that i had no hdmi signal,

but my usb stick was still flashing for activity, the led light stopped flashing,

i assumed i had booted into something, and i restarted and loaded my 10.5.6

 

i cannot see therefore i cannot conclude if it was a successful boot or not,

 

any ideas as to why my graphics just gave out..

 

It is likely that your video is not set up correctly.........boot with -v -x........

[tnap1979]

ok i will try that right now,

will update as to what happens

 

no luck,

still same effect, but i did notice a few things mentioning 64bit, and such, and something about dsmos just before the screen went blank to no hdmi signal again....

i thought i had the kernel flag set to 32bit via the instructions in post #1

but im not worried about that, more worried bout the no signal problem,

and blank video after the dsmos thing shows up in -v -x boot flag mode

[verdant]

ok i will try that right now,

will update as to what happens

 

no luck,

still same effect, but i did notice a few things mentioning 64bit, and such, and something about dsmos just before the screen went blank to no hdmi signal again....

i thought i had the kernel flag set to 32bit via the instructions in post #1

but im not worried about that, more worried bout the no signal problem,

and blank video after the dsmos thing shows up in -v -x boot flag mode

 

Try switching your monitor cable to the other port on your graphics card as the graphics string you put in com.apple.Boot.plist may not have the correct setting for the port you are connected to.....can you also connect in simple DVI mode (i.e. without additional audio signal carried via HDMI).......?

[tnap1979]

i havent injected any string into the file you mentioned,?

i wasnt sure if i had to or not,

 

if so, what steps to do such,

and ill try the cable swap next to be sure,

ill report back on cable swap in a few minutes

rebooting now...

 

oh and my cable is just a simple dvi to hdmi cable, no audio signal involved

 

ive tried the cable swap to second dvi port,

and still failure,

im thinking maybe i need to inject that string or something,

im not sure as to why this is happening,

how can i do such a thing.... ??

i forgot if i had to do it for leo or not, i dont believe i did