Jump to content

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


verdant
 Share

Snow Leopard on nForce + Intel CPU MOBO in Desktop  

213 members have voted

  1. 1. Have you successfully installed a working, bootable Snow Leopard system?

    • Yes, on a Series 7 (750i, 780i, or 790i) nForce chipset Intel CPU MOBO, using the USB flash drive installer method
      34
    • Yes, on a Series 6 (650i or 680i) nForce chipset Intel CPU MOBO, using the USB flash drive installer method
      50
    • Yes, on a Series 6 (610i or 630i) nForce chipset Intel CPU MOBO, using the USB flash drive installer method
      18
    • Yes, on a Series 7 (750i, 780i, or 790i) nForce chipset Intel CPU MOBO, using verdant's nForceSLBoot132DVD installer method
      14
    • Yes, on a Series 6 (650i or 680i) nForce chipset Intel CPU MOBO, using verdant's nForceSLBoot132DVD installer method
      13
    • Yes, on a Series 6 (610i or 630i) nForce chipset Intel CPU MOBO, using verdant's nForceSLBoot132DVD installer method
      6
    • Yes, on a Series 7 (750i, 780i, or 790i) nForce chipset Intel CPU MOBO using OSInstall.mpkg method from Leopard to another HDD/volume
      10
    • Yes, on a Series 6 (650i or 680i) nForce chipset Intel CPU MOBO, using OSInstall.mpkg method from Leopard to another HDD/volume
      9
    • Yes, on a Series 6 (610i or 630i) nForce chipset Intel CPU MOBO, using OSInstall.mpkg method from Leopard to another HDD/volume
      8
    • No, none of the above methods has worked for me
      35
    • I have sold or plan to sell my nForce chipset MOBO to go over to the "light" side....Intel chipset MOBO.....
      10
    • I have sold or plan to sell my nForce chipset MOBO to buy a "real" Mac
      6
  2. 2. Would you say that your Snow Leopard system is working to your satisfaction (e.g. compared to Leopard)

    • 100%
      60
    • 90%
      53
    • 80%
      20
    • 70%
      19
    • 60%
      4
    • 50%
      6
    • <50%
      18
    • Are you running 10.6.1 successfully , having auto-updated without any problems
      21
    • Are all the standard Apple applications running OK
      12
  3. 3. Is your Snow Leopard system working 100% on

    • SATA HDD
      173
    • SATA DVDRW including burning disks
      47
    • PATA (IDE) HDD
      42
    • PATA (IDE) DVDRW including burning disks
      51
    • Video
      146
    • Onboard LAN (Ethernet)
      131
    • USB devices (mounting/unmounting), plus USB keyboard and USB mouse
      161
    • Firewire
      54
    • PS/2 keyboard and mouse
      42
    • Audio including Front Panel headphones and microphone
      63
    • Audio except Front Panel headphones
      38
    • Audio except Front Panel microphone
      27
    • Sleep including waking from sleep
      24
    • PCI NIC
      24
    • eSATA
      20
    • Bluetooth
      41
    • WiFi
      38
    • Time Machine
      53
    • Overclocking
      35
    • Auto Software Update e.g. to 10.6.1
      90


2,142 posts in this topic

Recommended Posts

Hey Verdant,

 

For the advice given above about changing the drives ownership from the desktop...is there a way I could this from Windows 7? I don't have a leopard install on my desktop, but I do have a macbook. Also in the step where you ask to install osx86tools or the efi thing, how can I do that from Windows 7?

Link to comment
Share on other sites

Hey Verdant,

 

For the advice given above about changing the drives ownership from the desktop...is there a way I could this from Windows 7? I don't have a leopard install on my desktop, but I do have a macbook. Also in the step where you ask to install osx86tools or the efi thing, how can I do that from Windows 7?

 

 

I don't think your can do the GFX thing from windows. What graphics card do you have? How much memory does it have? I'll pm you with the string.

 

 

 

And thanks verdant! I totally didn't see that. Lol. I tried like four times to restore the snowleo disk to my flash drive but I Keely getting this one I/O error. So I ripped the DMG usuing the "new image" option in diskutility and I'm going to try and restore that onto the flash drive

Link to comment
Share on other sites

Hey Verdant,

 

For the advice given above about changing the drives ownership from the desktop...is there a way I could this from Windows 7? I don't have a leopard install on my desktop, but I do have a macbook. Also in the step where you ask to install osx86tools or the efi thing, how can I do that from Windows 7?

 

When you run the installer on the USB Flash Drive go into Disk Utilities as usual because it should see the HDD you are installing to.....

 

You can initially try booting without the EFI string under device-properties in com.apple.Boot.plist by booting the HDD with -v -x.....

 

I don't think your can do the GFX thing from windows. What graphics card do you have? How much memory does it have? I'll pm you with the string.

 

 

 

And thanks verdant! I totally didn't see that. Lol. I tried like four times to restore the snowleo disk to my flash drive but I Keely getting this one I/O error. So I ripped the DMG usuing the "new image" option in diskutility and I'm going to try and restore that onto the flash drive

 

I normally make my OS X Install DVD images [.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....... ;)

Link to comment
Share on other sites

haha so i got image ripped to my desktop on osx and then restored it with out any errors

and then i boot to the flash drive on chameleon and i boot into Verbose mode

and then i get a KP, and this time i followed all your directions from the start!.

 

right before the kp it says

 

Kernel Extensions in backtrace (with dependencies):

com.apple.driver.AppleIntelCpupowermanagement) and then some random numbers and letters

 

BSD process name corresponding to current thread: kernel_task

 

what should i do?

i am dualbooting snow/leo

with cham rc1 on my flash drive with the netkasefi10 boot file

 

PS

could this be used for future purposes?

http://www.insanelymac.com/forum/index.php?showtopic=185823

 

 

EDIT:

/\

i used that thing and i got the same error :/

Link to comment
Share on other sites

I don't think your can do the GFX thing from windows. What graphics card do you have? How much memory does it have? I'll pm you with the string.

 

 

 

And thanks verdant! I totally didn't see that. Lol. I tried like four times to restore the snowleo disk to my flash drive but I Keely getting this one I/O error. So I ripped the DMG usuing the "new image" option in diskutility and I'm going to try and restore that onto the flash drive

 

Thanks Rohizzle,

 

I have a Geforce 8800 Ultra with 768mb

Link to comment
Share on other sites

Thanks Rohizzle,

 

I have a Geforce 8800 Ultra with 768mb

 

7e0200000100000001000000720200000d00000002010c00d041030a010000000101060000030101

060000000101060000000101060000007fff04000e0000004e00560050004d0000002000000001000

000000000000000000000000000000000000000000000000000220000005600520041004d002c0074

006f00740061006c00730069007a006500000008000000000000301c0000006400650076006900630

065005f00740079007000650000000f0000004e5644412c506172656e740e0000006e0061006d0065

0000000b000000646973706c617922000000400030002c006400650076006900630065005f0074007

9007000650000000b000000646973706c617922000000400031002c00640065007600690063006500

5f00740079007000650000000b000000646973706c6179100000006d006f00640065006c0000001d0

000006e5669646961204765466f726365203838303020556c74726120000000400031002c0063006f

006d00700061007400690062006c00650000000e0000004e5644412c4e564d6163140000004000300

02c006e0061006d0065000000120000004e5644412c446973706c61792d4114000000400031002c00

6e0061006d0065000000120000004e5644412c446973706c61792d4220000000400030002c0063006

f006d00700061007400690062006c00650000000e0000004e5644412c4e564d6163100000004e0056

0043004100500000001800000004000000000003000c00000000000007000000001e00000072006f0

06d002d007200650076006900730069006f006e000000310000006e5669646961204765466f726365

203838303020556c747261204f70656e474c20456e67696e65205b4546495d

Link to comment
Share on other sites

7e0200000100000001000000720200000d00000002010c00d041030a010000000101060000030101

060000000101060000000101060000007fff04000e0000004e00560050004d000000200000000100

0

000000000000000000000000000000000000000000000000000220000005600520041004d002c007

4

006f00740061006c00730069007a006500000008000000000000301c000000640065007600690063

0

065005f00740079007000650000000f0000004e5644412c506172656e740e0000006e0061006d006

5

0000000b000000646973706c617922000000400030002c006400650076006900630065005f007400

7

9007000650000000b000000646973706c617922000000400031002c0064006500760069006300650

0

5f00740079007000650000000b000000646973706c6179100000006d006f00640065006c0000001d

0

000006e5669646961204765466f726365203838303020556c74726120000000400031002c0063006

f

006d00700061007400690062006c00650000000e0000004e5644412c4e564d616314000000400030

0

02c006e0061006d0065000000120000004e5644412c446973706c61792d4114000000400031002c0

0

6e0061006d0065000000120000004e5644412c446973706c61792d4220000000400030002c006300

6

f006d00700061007400690062006c00650000000e0000004e5644412c4e564d6163100000004e005

6

0043004100500000001800000004000000000003000c00000000000007000000001e00000072006f

0

06d002d007200650076006900730069006f006e000000310000006e5669646961204765466f72636

5

203838303020556c747261204f70656e474c20456e67696e65205b4546495d

 

 

Awesome Thank You!

Link to comment
Share on other sites

haha so i got image ripped to my desktop on osx and then restored it with out any errors

and then i boot to the flash drive on chameleon and i boot into Verbose mode

and then i get a KP, and this time i followed all your directions from the start!.

 

right before the kp it says

 

 

 

what should i do?

i am dualbooting snow/leo

with cham rc1 on my flash drive with the netkasefi10 boot file

 

PS

could this be used for future purposes?

http://www.insanelymac.com/forum/index.php?showtopic=185823

 

 

EDIT:

/\

i used that thing and i got the same error :/

 

Your KP referring to com.apple.driver.AppleIntelCPUPowerManagement is indicating that for some reason NullCPUPowerManagement.kext is not taking over from the AppleIntelCPUPowerManagement.kext......?

 

Let me try a couple of things and get back to you when I can......

Link to comment
Share on other sites

Your KP referring to com.apple.driver.AppleIntelCPUPowerManagement is indicating that for some reason NullCPUPowerManagement.kext is not taking over from the AppleIntelCPUPowerManagement.kext......?

 

Let me try a couple of things and get back to you when I can......

 

 

 

ok thanks :)

does have anything to do with leo and snowleo being on the same HDD but different partitions

Link to comment
Share on other sites

ok thanks :blink:

does have anything to do with leo and snowleo being on the same HDD but different partitions

 

My view is that the kext utility did not build the the Extensions.mkext cache file pathway to NullCPUPowerManagement.kext in /Extra/Extensions properly (although it is probably setting the kext permissions correctly which is important)......so delete the Extensions.mkext cache file from /Extra on your USB flash drive OS X Installer.....

 

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

Link to comment
Share on other sites

OK...

 

I went ahead and reinstalled Leopard to a 25gb partition to do Step D of this guide. I followed every step for the USB installer, and every step for the Snow Leopard HDD and went to install it got stuck about 5% in permanently. I had the installer log open and there thousands of errors. I am not sure what I did wrong but I am getting stuck on the actual installer.

 

I went to reboot to try to install again, and it showed something about the CMOS resetting and all of my bios settings go back to default. Does this mean I did something wrong with the whole DSDT patcher?

Link to comment
Share on other sites

OK...

 

I went ahead and reinstalled Leopard to a 25gb partition to do Step D of this guide. I followed every step for the USB installer, and every step for the Snow Leopard HDD and went to install it got stuck about 5% in permanently. I had the installer log open and there thousands of errors. I am not sure what I did wrong but I am getting stuck on the actual installer.

 

I went to reboot to try to install again, and it showed something about the CMOS resetting and all of my bios settings go back to default. Does this mean I did something wrong with the whole DSDT patcher?

 

That means that your DSDT.aml file has not been patched correctly.......check your dsdt.dsl file that you have changed the two device (RTC) IO segment length values to 0x02....and make a new DSDT.aml file....

Link to comment
Share on other sites

My view is that the kext utility 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 delete the Extensions.mkext cache file from /Extra on your USB flash drive OS X Installer.....

 

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

 

 

ok so that fixed my problem!

but then another one came up :/

after it boots, my tv says theres no signal. im assuming its becuase of a GFX problem, becuase when i use -x it works but i get a KP when i try and install. any suggestions?

Link to comment
Share on other sites

ok so that fixed my problem!

but then another one came up :/

after it boots, my tv says theres no signal. im assuming its becuase of a GFX problem, becuase when i use -x it works but i get a KP when i try and install. any suggestions?

 

Did you put an graphics EFI string in the com.apple.Boot.plist on the USB flash drive.....? If you did then remove it......

Link to comment
Share on other sites

That means that your DSDT.aml file has not been patched correctly.......check your dsdt.dsl file that you have changed the two device (RTC) IO segment length values to 0x02....and make a new DSDT.aml file....

 

 

Ok...I might have been confused with the directions. Am I simply copy and pasting this whole quote into the editor?

 

 

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

)

 

Or am I actually changing the 0x04 values to 0x02 manually after I paste it? I just copy and pasted the whole thinking that this (change 0x04 to 0x02) was going to change it for me. Was I right or wrong?

Link to comment
Share on other sites

Ok...I might have been confused with the directions. Am I simply copy and pasting this whole quote into the editor?

 

 

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

)

 

Or am I actually changing the 0x04 values to 0x02 manually after I paste it? I just copy and pasted the whole thinking that this (change 0x04 to 0x02) was going to change it for me. Was I right or wrong?

 

There is no cutting and pasting involved at all!

 

The steps yoiu 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 device (RTC) section and change the two IO segment length values 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......

Link to comment
Share on other sites

There is no cutting and pasting involved at all!

 

The steps yoiu 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 device (RTC) section and change the two IO segment length values 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......

 

 

Ok now I see that i actually had to scroll through and find those numbers. One thing I did notice is I don't have that 2nd section with (ATT1). Under my RTC Device I only have one number to change and it was 0x08...so i changed it to 0x02. It just didn't look anything like your instructions.

Link to comment
Share on other sites

i didnt put in the one on the flash drive only on the one on my HDD

 

i actually tried putting the EFI string and it worked!

but

and theres always a but

 

 

it freezes during install. about two min in and when i looked at the log, and all it said was installed ichat. or somthing.

 

anyidea?

Link to comment
Share on other sites

i actually tried putting the EFI string and it worked!

but

and theres always a but

 

 

it freezes during install. about two min in and when i looked at the log, and all it said was installed ichat. or somthing.

 

anyidea?

 

Does it say failed to extract package or or could not install support files.....?

Link to comment
Share on other sites

verdant,

 

Ok now I see that i actually had to scroll through and find those numbers. One thing I did notice is I don't have that 2nd section with (ATT1). Under my RTC Device I only have one number to change and it was 0x08...so i changed it to 0x02. It just didn't look anything like your instructions.

 

I tried installing again, it froze at about 10% in the install with lots of errors showing up on the bottom, and then on reboot it said the cmos stuff reset again. So i know it is the DSDR.aml file, but I just can't find the same numbers to change as your directions show.

Link to comment
Share on other sites

Does it say failed to extract package or or could not install support files.....?

 

i get

"retrying files://localhost/system/installation/packages/ADDITIONALSPEECHVOICE.PKG"

and then fails

 

 

i took out all of the drivers

 

i found i get the same thing in -x

 

im sorry for asking so many questions i just really want snowleo!

 

thanks for your patience

Link to comment
Share on other sites

i get both

i get it sometimes

at java tools

and then addition speech voices

and then

i found i get the same thing in -x

 

im sorry for asking so many questions i just really want snowleo!

 

thanks for your patience

 

It sounds like your Mac OS X Install DVD image is corrupted and/or the Retail OS X Install DVD source itself is possibly corrupted.....see here.....

Link to comment
Share on other sites

It sounds like your Mac OS X Install DVD image is corrupted and/or the Retail OS X Install DVD source itself is possibly corrupted.....see here.....

 

i just checked in leo and it says its ok.

i am really confused:/ i think i am going to rerip the disc and start over fresh

 

*crosses fingers*

Link to comment
Share on other sites

 Share

×
×
  • Create New...