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

By verdant,
in OSx86 10.6 (Snow Leopard)

 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

verdant
verdant
Posted
  • Author
Posted
aquamac, probably best to simply post on his proboard; i shall do that too.

 

When i investigated w/ my linux live distros yesterday i did check LSPCI output; the basic addresses were the same output that i got w/ my 10.6 installations. Good idea though; I'll pull the extended info when i get a chance :D

 

Let's see what aqua-mac and haroot have to say..........hopefully, you can get it sorted........ :(

Link to comment
Share on other sites
djcoma1200
djcoma1200
Posted
Posted
Yes, with the proviso that if you are planning to using a graphics string to drive your graphics card(s), you have already generated the string using Leopard (based on the comment by aqua-mac in post #1)........

 

If you originally partitioned the HDD as GPT, then you should just have format the 2nd volume on it as HFS+........if not, then simply partition/format the entire HDD as GPT/HFS+ into as many volumes as you want.......I recommend 2 OS X SL systems; one main and other Backup.......

 

I personally always put a 10GB OS X Boot volume that works 100% at the start of my OS X HDDs, that I never "mess" with, plus OS X Main and OS X Backup volumes.

 

This is because I do a lot of installation testing for my nForce guides alternately on Main and Backup but always need a bootable working OS X system; both Leopard and Snow Leopard Boot volumes on separate HDDs.......a 500GB SATA HDD for Windows 7 and Vista; a 500GB SATA HDD for Ubuntu; a 500GB SATA HDD for Leopard; a 750GB SATA HDD for Snow Leopard (and 10.7 testing when it arrives....) and a 500GB SATA HDD for archiving......

 

All these HDDs are inside my PC but the 500GB SATA HDD for archiving is set up in an ODD WAY.....this is because I have 6 SATA ports but no native eSATA ports, yet have 5 internal SATA HDDs and a SATA DVDRW (and 2 PATA DVDRWs on my MOBO single IDE channel), PLUS a eSATA HDD enclosure that I use........so my 500GB SATA HDD for archiving is connected to an 1 x eSATA backplate and another 1 x eSATA backplate is connected to the only free MOBO SATA connector......I then use a short 0.5 m eSATA-eSATA cable to connect the 500GB SATA HDD to the MOBO when I want to use it for archiving........but when I want to use my eSATA HDD enclosure I just unplug the short eSATA loop-cable from the active eSATA port and plug in the eSATA HDD enclosure eSATA cable...... :(

 

So would the link below be the guide I should follow to get Leopard up and running on my 680i? And which release would you recommend I use?

 

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

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
So would the link below be the guide I should follow to get Leopard up and running on my 680i? And which release would you recommend I use?

 

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

 

Yes.....but you can save time in determining what Customise menu selections to make, by also following my iPC 10.5.6 nForce chipset MOBO install guide in my blog.........or, any of the other Leopard install guides in my blog if you already have the distro DVD(s)....... ;)

Link to comment
Share on other sites
breakingbad
breakingbad
Posted
Posted

Hi all.

I see a lot of activity here. :)

That's pretty nice.

I was following the last messages and gee, now I realize how difficult can be to have everything working fine in nForce chipsets. :)

When I was through it never thought it was that complicated.

 

But sometimes I miss my nForce mobo.

With it I could learn a lot.

 

I've read a lot of people talking about dual GFX's but I can't even give it a try.

My mobo doesn't support two GFX's. ;)

I'm pretty satisfied with one 9800 GT only, but 2 would be awesome. ;)

 

Cheers,

bb.

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
Hi all.

I see a lot of activity here. :)

That's pretty nice.

I was following the last messages and gee, now I realize how difficult can be to have everything working fine in nForce chipsets. :)

When I was through it never thought it was that complicated.

 

But sometimes I miss my nForce mobo.

With it I could learn a lot.

 

I've read a lot of people talking about dual GFX's but I can't even give it a try.

My mobo doesn't support two GFX's. :(

I'm pretty satisfied with one 9800 GT only, but 2 would be awesome. ;)

 

Cheers,

bb.

 

Hi bb,

 

Hope you well.

 

I guess that is why when we nForcers finally get something working in DSDT/OSx86/kext/hardware/apps etc. by having to act as detectives or forensic scientists:

 

:help::gathering:

 

and putting in hours/days/months of

 

;):shock::wallbash::);):hammer::moil::compress::pyth::stretcher: effort and at times feeling as if we are about to :blowup:

 

we struggle to our feet for the next round.... :boxing: BECAUSE you just cannot put a good nForcer down! .......ready once again to deal with Intel MOBO owners telling us to give up and take the easy path...... :laser:

 

(only joking!!!!)

 

we :) from the OSx86 academy, and then

 

:yoji:

 

followed by :smoke: LOL.....

Link to comment
Share on other sites
breakingbad
breakingbad
Posted
Posted
Hi bb,

 

Hope you well.

 

I guess that is why when we nForcers finally get something working in DSDT/OSx86/kext/hardware/apps etc. by having to act as detectives or forensic scientists:

 

:help::gathering:

 

and putting in hours/days/months of

 

;):shock::wallbash::D:D:hammer::moil::compress::pyth::stretcher: effort and at times feeling as if we are about to :blowup:

 

we struggle to our feet for the next round.... :boxing: BECAUSE you just cannot put a good nForcer down! .......ready once again to deal with Intel MOBO owners telling us to give up and take the easy path...... :laser:

 

(only joking!!!!)

 

we :graduated: from the OSx86 academy, and then

 

:yoji:

 

followed by :smoke: LOL.....

Yeah mate.

I'm not despising my time with nForce mobos. It's totally the other way around. I have to thank a lot to my nForce mobo. Because of it I learned a lot. I'm just making a parallel between different mobos. :)

I changed because here where I live people just want Intel, Intel, Intel.... wherever you go you find Intel based mobos... so as I use my PC to work, couldn't wait till I find another nForce mobo and got an Intel.

As this is off topic, won't make it any longer. :)

 

Cheers,

bb.

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
Yeah mate.

I'm not despising my time with nForce mobos. It's totally the other way around. I have to thank a lot to my nForce mobo. Because of it I learned a lot. I'm just making a parallel between different mobos. ;)

I changed because here where I live people just want Intel, Intel, Intel.... wherever you go you find Intel based mobos... so as I use my PC to work, couldn't wait till I find another nForce mobo and got an Intel.

As this is off topic, won't make it any longer. :)

 

Cheers,

bb.

 

Hi bb

 

Do not worry about justifying your comments......I know you had to purchase an Intel MOBO in a hurry because your PC is your work for living......... :mellow: That is why I said I was joking........I having nothing against Intel chipset MOBOs.......in the same way, if Apple do something with AMD and/or nVidia.......no problem.......diversity of choice is good.....that is why I use OS X, Windows and Linux. It was late at night and I felt like seeing a cartoon but had to make it myself....... :)

 

Cheers

verdant

Link to comment
Share on other sites
breakingbad
breakingbad
Posted
Posted
Hi bb

 

Do not worry about justifying your comments......I know you had to purchase an Intel MOBO in a hurry because your PC is your work for living......... :mellow: That is why I said I was joking........I having nothing against Intel chipset MOBOs.......in the same way, if Apple do something with AMD and/or nVidia.......no problem.......diversity of choice is good.....that is why I use OS X, Windows and Linux. It was late at night and I felt like seeing a cartoon but had to make it myself....... :)

 

Cheers

verdant

LOL !!!

I know it was a joke. I don't mind. :)

Just for the record, Family Guy is a veeeeeery nice cartoon. ;)

 

By the way, let me tell you something... this is now OS X related... LOL !

I bought one of this IDE to SATA converter but it seems that OS X doesn't understand this conversion.

I installed it here to my IDE DVD ROM but OS X doesn't see it. System is saying there's no drives connected.

I believe it should work without problems.

 

Cheers,

bb.

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
LOL !!!

I know it was a joke. I don't mind. :D

Just for the record, Family Guy is a veeeeeery nice cartoon. :)

 

By the way, let me tell you something... this is now OS X related... LOL !

I bought one of this IDE to SATA converter but it seems that OS X doesn't understand this conversion.

I installed it here to my IDE DVD ROM but OS X doesn't see it. System is saying there's no drives connected.

I believe it should work without problems.

 

Cheers,

bb.

 

Things not always guaranteed......on Amazon, a IDE to SATA adapter/converter by 2-TECH was reported, by a buyer of it, to only work on 1 out of 3 optical DVD-RW drives it was tried on.........you need an adapter stated to work with OS X such as this one.......but even then it says "Convert any IDE hard drive and most ATAPI devices to Serial ATA device"....i.e. NOT all and says "compatible with any Serial ATA controller (ATAPI device may only work with host controller using Silicon Image chipset)".......

Link to comment
Share on other sites
breakingbad
breakingbad
Posted
Posted
Things not always guaranteed......on Amazon, a IDE to SATA adapter/converter by 2-TECH was reported, by a buyer of it, to only work on 1 out of 3 optical DVD-RW drives it was tried on.........you need an adapter stated to work with OS X such as this one.......but even then it says "Convert any IDE hard drive and most ATAPI devices to Serial ATA device"....i.e. NOT all and says "compatible with any Serial ATA controller (ATAPI device may only work with host controller using Silicon Image chipset)".......

I think I'll have to go back to the horrible IDE cable I own. LOL !

 

Cheers,

bb.

Link to comment
Share on other sites
kbosselman
kbosselman
Posted
Posted
It might be worth you trying the following commands I came across in the Project OS X forum in a post by THe KiNG; although he said that fixing AHCI mode in DSDT only works for ICH7-M or ICH7-R............but you have nothing to lose by seeing what info the following commands throw up......

 

sudo -s

 

lspci -s 00:1f.2 -nnvvxxx // this it will show the actual registers and controller mode

 

setpci -s 00:1f.2 90.b // Double check the value of the register

 

setpci -s 00:1f.2 90.b=40 // Set the new value of the register

 

setpci -s 00:1f.2 90.b // Check if it changed, if yes then you are lucky, if not gave up u can't set it

 

lspci -s 00:1f.2 -nnvvxxx // run again to see how is controller set, if success should be in AHCI mode

 

I ran the lspci commands (ubuntu 10.4 live cd) however things look pretty different on my machine. The address in the first command (00:1f.2) doesn't exist.

 

If I just do an lspci I get the following:

 

</SPAN><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt">00:00.0 Host bridge: nVidia Corporation C55 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.2 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.3 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.4 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.5 RAM memory: nVidia Corporation C55 Memory Controller (rev a2)
00:00.6 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.7 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.0 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.1 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.2 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.3 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.4 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.5 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.6 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:02.0 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:02.1 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:02.2 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:03.0 PCI bridge: nVidia Corporation C55 PCI Express bridge (rev a1)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
00:0e.0 RAID bus controller: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
00:0f.0 RAID bus controller: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
01:00.0 VGA compatible controller: ATI Technologies Inc RV770 [Radeon HD 4850]
01:00.1 Audio device: ATI Technologies Inc HD48x0 audio
02:05.0 FireWire (IEEE 1394): Agere Systems FW322/323 (rev 70)</SPAN><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt">

 

If I run lspci -s 00:0f.0 -nnvvxxx I get the following:

 

</SPAN><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt">00:0f.0 RAID bus controller [0104]: nVidia Corporation MCP51 Serial ATA Controller [10de:0267] (rev a1) (prog-if 85)
Subsystem: Dell Device [1028:0249]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 23
Region 0: I/O ports at 09e0 [size=8]
Region 1: I/O ports at 0be0 [size=4]
Region 2: I/O ports at 0960 [size=8]
Region 3: I/O ports at 0b60 [size=4]
Region 4: I/O ports at f300 [size=16]
Region 5: Memory at efffc000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [b0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/2 Enable-
 Address: 0000000000000000  Data: 0000
Capabilities: [cc] HyperTransport: MSI Mapping Enable- Fixed+
Kernel driver in use: sata_nv
Kernel modules: sata_nv
00: de 10 67 02 07 00 b0 00 a1 85 04 01 00 00 00 00
10: e1 09 00 00 e1 0b 00 00 61 09 00 00 61 0b 00 00
20: 01 f3 00 00 00 c0 ff ef 00 00 00 00 28 10 49 02
30: 00 00 00 00 44 00 00 00 00 00 00 00 0a 01 03 01
40: 28 10 49 02 01 b0 02 00 00 00 00 00 00 00 00 00
50: 07 00 00 00 00 00 00 00 a8 20 a8 a8 a6 00 20 99
60: 00 c7 00 00 51 0c 00 00 00 0f 06 42 00 00 00 00
70: 2c 78 c4 40 01 10 00 00 01 10 00 00 20 00 20 00
80: 00 00 00 c0 02 6c 18 e6 00 00 4e 05 00 10 4d 33
90: 00 00 20 80 00 00 00 00 06 00 06 10 00 00 04 01
a0: 14 10 00 2b 80 00 00 00 00 00 00 00 33 33 00 02
b0: 05 cc 84 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 0a 00 0a 00 08 00 02 a8
d0: 0a 00 02 06 42 00 00 00 00 00 00 00 0f 00 00 00
e0: 0a 00 02 06 42 00 00 00 00 00 00 00 0f 00 00 e0
f0: 00 00 00 00 00 00 00 00 00 00 0c 00 00 00 00 00

 

Any thoughts? I see from your signature you have a nForce 650i also. What does your lspci dump look like?

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted

@ kbosselman

 

My SATA controller is the nVidia Corporation MCP55 SATA Controller (rev a2), not the MCP51 that you have.....

 

Using lspci -nn I get as follows:

 

00:00.0 Host bridge [0600]: nVidia Corporation C55 Host Bridge [10de:03a3] (rev a2)

00:00.1 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03ac] (rev a1)

00:00.2 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03aa] (rev a1)

00:00.3 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03a9] (rev a1)

00:00.4 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03ab] (rev a1)

00:00.5 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03a8] (rev a2)

00:00.6 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03b5] (rev a1)

00:00.7 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03b4] (rev a1)

00:01.0 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03ad] (rev a1)

00:01.1 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03ae] (rev a1)

00:01.2 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03af] (rev a1)

00:01.3 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03b0] (rev a1)

00:01.4 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03b1] (rev a1)

00:01.5 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03b2] (rev a1)

00:01.6 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03b3] (rev a1)

00:02.0 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03b6] (rev a1)

00:02.1 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03bc] (rev a1)

00:02.2 RAM memory [0500]: nVidia Corporation C55 Memory Controller [10de:03ba] (rev a1)

00:03.0 PCI bridge [0604]: nVidia Corporation C55 PCI Express bridge [10de:03b7] (rev a1)

00:06.0 PCI bridge [0604]: nVidia Corporation C55 PCI Express bridge [10de:03b9] (rev a1)

00:07.0 PCI bridge [0604]: nVidia Corporation C55 PCI Express bridge [10de:03bb] (rev a1)

00:09.0 RAM memory [0500]: nVidia Corporation MCP55 Memory Controller [10de:0369] (rev a1)

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

00:0a.1 SMBus [0c05]: nVidia Corporation MCP55 SMBus [10de:0368] (rev a2)

00:0b.0 USB Controller [0c03]: nVidia Corporation MCP55 USB Controller [10de:036c] (rev a1)

00:0b.1 USB Controller [0c03]: nVidia Corporation MCP55 USB Controller [10de:036d] (rev a2)

00:0d.0 IDE interface [0101]: nVidia Corporation MCP55 IDE [10de:036e] (rev a1)

00:0e.0 IDE interface [0101]: nVidia Corporation MCP55 SATA Controller [10de:037f] (rev a2)

00:0e.1 IDE interface [0101]: nVidia Corporation MCP55 SATA Controller [10de:037f] (rev a2)

00:0e.2 IDE interface [0101]: nVidia Corporation MCP55 SATA Controller [10de:037f] (rev a2)

00:0f.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI bridge [10de:0370] (rev a2)

00:0f.1 Audio device [0403]: nVidia Corporation MCP55 High Definition Audio [10de:0371] (rev a2)

00:11.0 Bridge [0680]: nVidia Corporation MCP55 Ethernet [10de:0373] (rev a2)

00:12.0 Bridge [0680]: nVidia Corporation MCP55 Ethernet [10de:0373] (rev a2)

00:13.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge [10de:0376] (rev a2)

00:14.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge [10de:0374] (rev a2)

00:15.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge [10de:0374] (rev a2)

00:16.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge [10de:0378] (rev a2)

00:17.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge [10de:0375] (rev a2)

00:18.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge [10de:0377] (rev a2)

01:00.0 VGA compatible controller [0300]: nVidia Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1)

04:06.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet [10ec:8169] (rev 10)

04:0b.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller [1106:3044] (rev c0)

 

 

The address in the first command (00:1f.2) doesn't exist because it is a device address for the ICH7-M or ICH7-R chipset.........

 

00:1f.2 SATA controller [0106]: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller [8086:27c5] (rev 01) (prog-if 01)

Subsystem: Dell Device [1028:01cd]

Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step

ping- SERR- FastB2B- DisINTx+

Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort

- <MAbort- >SERR- <PERR- INTx-

Latency: 0

Interrupt: pin B routed to IRQ 28

Region 0: I/O ports at 01f0

Region 1: I/O ports at 03f4

Region 2: I/O ports at 0170

Region 3: I/O ports at 0374

Region 4: I/O ports at bfa0

Region 5: Memory at e0200000 (32-bit, non-prefetchable)

Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0

Enable+

Address: fee0300c Data: 4181

Capabilities: [70] Power Management version 2

Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)

Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Kernel driver in use: ahci

00: 86 80 c5 27 07 04 b0 02 01 01 06 01 00 00 00 00

10: f1 01 00 00 f5 03 00 00 71 01 00 00 75 03 00 00

20: a1 bf 00 00 00 00 20 e0 00 00 00 00 28 10 cd 01

30: 00 00 00 00 80 00 00 00 00 00 00 00 05 02 00 00

40: 0f e3 0b e3 00 00 00 00 05 00 01 02 00 00 00 00

50: 00 00 00 00 f0 10 00 00 00 00 00 00 00 00 00 00

60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

70: 01 00 02 40 00 00 00 00 00 00 00 00 00 00 00 00

80: 05 70 01 00 0c 30 e0 fe 81 41 00 00 00 00 00 00

90: 40 00 15 00 80 01 80 5a 00 00 00 00 00 00 00 00

a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

c0: 00 00 00 00 05 00 00 00 00 00 00 00 00 00 00 00

d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

f0: 00 00 00 00 00 00 00 00 86 0f 02 00 00 00 00 00

 

You need the equivalent nForce addresses.......

Link to comment
Share on other sites
kbosselman
kbosselman
Posted
Posted
@ kbosselman

 

My SATA controller is the nVidia Corporation MCP55 SATA Controller (rev a2), not the MCP51 that you have.....

 

 

Did you do a sudo -s before running the lspci? On mine it dumped more info after a sudo (ie. address info went to f0 instead of stopping at 30, among other things). Could you repost if you get more detail.

 

Thanks

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
Did the data get chopped? I'm not seeing the SATA ones?

 

They are here one by one......with IDE one (00:0d.0) for comparison......

 

00:0d.0 IDE interface [0101]: nVidia Corporation MCP55 IDE [10de:036e] (rev a1) (prog-if 8a [Master SecP PriP])

Subsystem: ASUSTeK Computer Inc. Device [1043:cb84]

Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-

Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

Latency: 0 (750ns min, 250ns max)

Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [disabled]

Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [disabled]

Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [disabled]

Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [disabled]

Region 4: I/O ports at fc00

Capabilities: [44] Power Management version 2

Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)

Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Kernel driver in use: pata_amd

Kernel modules: pata_amd

00: de 10 6e 03 05 00 b0 00 a1 8a 01 01 00 00 00 00

10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

20: 01 fc 00 00 00 00 00 00 00 00 00 00 43 10 84 cb

30: 00 00 00 00 44 00 00 00 00 00 00 00 00 00 03 01

40: 43 10 84 cb 01 00 02 00 00 00 00 00 00 00 00 00

50: 02 f0 00 00 00 00 00 00 99 99 99 99 aa 00 a8 a8

60: 00 00 c0 c5 00 00 00 00 00 00 00 00 00 00 00 00

70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

80: 00 00 00 00 00 90 00 20 00 00 02 18 00 00 00 00

90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 01

a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

f0: 00 00 00 00 00 00 00 00 10 00 00 00 00 00 00 00

 

00:0e.0 IDE interface [0101]: nVidia Corporation MCP55 SATA Controller [10de:037f] (rev a2) (prog-if 85 [Master SecO PriO])

Subsystem: ASUSTeK Computer Inc. Device [1043:cb84]

Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-

Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

Latency: 0 (750ns min, 250ns max)

Interrupt: pin A routed to IRQ 23

Region 0: I/O ports at 09f0

Region 1: I/O ports at 0bf0

Region 2: I/O ports at 0970

Region 3: I/O ports at 0b70

Region 4: I/O ports at f700

Region 5: Memory at efffd000 (32-bit, non-prefetchable)

Capabilities: [44] Power Management version 2

Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)

Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Capabilities: [b0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/2 Enable-

Address: 0000000000000000 Data: 0000

Capabilities: [cc] HyperTransport: MSI Mapping Enable- Fixed+

Kernel driver in use: sata_nv

Kernel modules: sata_nv

00: de 10 7f 03 07 00 b0 00 a2 85 01 01 00 00 80 00

10: f1 09 00 00 f1 0b 00 00 71 09 00 00 71 0b 00 00

20: 01 f7 00 00 00 d0 ff ef 00 00 00 00 43 10 84 cb

30: 00 00 00 00 44 00 00 00 00 00 00 00 0b 01 03 01

40: 43 10 84 cb 01 b0 02 00 00 00 00 00 00 00 00 00

50: 0f 68 08 80 00 00 00 00 a8 a8 20 20 5a 00 99 20

60: 00 00 c5 c5 41 0c 00 00 00 0f 06 42 00 00 00 00

70: 2c 78 c4 40 01 10 00 00 01 10 00 00 20 00 20 00

80: 00 00 00 c0 00 60 c1 20 00 00 20 80 00 60 c5 20

90: 00 00 08 80 00 00 00 00 06 00 06 10 7f 03 01 01

a0: 12 0a 00 19 00 00 00 00 00 00 00 00 33 31 00 02

b0: 05 cc 84 00 00 00 00 00 00 00 00 00 00 00 00 00

c0: 00 00 00 00 00 00 00 00 0a 00 0a 00 08 00 02 a8

d0: 0a 00 02 76 42 00 00 00 00 00 00 00 ff f7 f7 e3

e0: 0a 00 02 66 42 00 00 00 00 00 00 00 0f 00 90 e7

f0: 00 00 00 00 00 00 00 00 10 00 0c 00 00 00 00 00

 

00:0e.1 IDE interface [0101]: nVidia Corporation MCP55 SATA Controller [10de:037f] (rev a2) (prog-if 85 [Master SecO PriO])

Subsystem: ASUSTeK Computer Inc. Device [1043:cb84]

Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-

Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

Latency: 0 (750ns min, 250ns max)

Interrupt: pin B routed to IRQ 22

Region 0: I/O ports at 09e0

Region 1: I/O ports at 0be0

Region 2: I/O ports at 0960

Region 3: I/O ports at 0b60

Region 4: I/O ports at f200

Region 5: Memory at efffc000 (32-bit, non-prefetchable)

Capabilities: [44] Power Management version 2

Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)

Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Capabilities: [b0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/2 Enable-

Address: 0000000000000000 Data: 0000

Capabilities: [cc] HyperTransport: MSI Mapping Enable- Fixed+

Kernel driver in use: sata_nv

Kernel modules: sata_nv

00: de 10 7f 03 07 00 b0 00 a2 85 01 01 00 00 80 00

10: e1 09 00 00 e1 0b 00 00 61 09 00 00 61 0b 00 00

20: 01 f2 00 00 00 c0 ff ef 00 00 00 00 43 10 84 cb

30: 00 00 00 00 44 00 00 00 00 00 00 00 05 02 03 01

40: 43 10 84 cb 01 b0 02 00 00 00 00 00 00 00 00 00

50: 0f 68 08 80 00 00 00 00 a8 a8 20 20 5a 00 99 20

60: 00 00 c5 c5 41 0c 00 00 00 0f 06 42 00 00 00 00

70: 2c 78 c4 40 01 10 00 00 01 10 00 00 20 00 20 00

80: 00 00 00 c0 00 00 c3 20 00 00 10 88 00 90 42 22

90: 00 00 08 80 00 00 00 00 06 00 06 10 7f 03 01 01

a0: 12 0a 00 19 00 00 00 00 00 00 00 00 33 31 00 02

b0: 05 cc 84 00 00 00 00 00 00 00 00 00 00 00 00 00

c0: 00 00 00 00 00 00 00 00 0a 00 0a 00 08 00 02 a8

d0: 0a 00 02 56 42 00 00 00 00 00 00 00 18 14 56 e0

e0: 0a 00 02 35 42 00 00 00 00 00 00 00 00 00 f0 e7

f0: 00 00 00 00 00 00 00 00 10 00 0c 00 00 00 00 00

 

00:0e.2 IDE interface [0101]: nVidia Corporation MCP55 SATA Controller [10de:037f] (rev a2) (prog-if 85 [Master SecO PriO])

Subsystem: ASUSTeK Computer Inc. Device [1043:cb84]

Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-

Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

Latency: 0 (750ns min, 250ns max)

Interrupt: pin C routed to IRQ 21

Region 0: I/O ports at f100

Region 1: I/O ports at f000

Region 2: I/O ports at ef00

Region 3: I/O ports at ee00

Region 4: I/O ports at ed00

Region 5: Memory at efffb000 (32-bit, non-prefetchable)

Capabilities: [44] Power Management version 2

Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)

Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Capabilities: [b0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/2 Enable-

Address: 0000000000000000 Data: 0000

Capabilities: [cc] HyperTransport: MSI Mapping Enable- Fixed+

Kernel driver in use: sata_nv

Kernel modules: sata_nv

00: de 10 7f 03 07 00 b0 00 a2 85 01 01 00 00 80 00

10: 01 f1 00 00 01 f0 00 00 01 ef 00 00 01 ee 00 00

20: 01 ed 00 00 00 b0 ff ef 00 00 00 00 43 10 84 cb

30: 00 00 00 00 44 00 00 00 00 00 00 00 0a 03 03 01

40: 43 10 84 cb 01 b0 02 00 00 00 00 00 00 00 00 00

50: 0f 68 08 80 00 00 00 00 a8 a8 20 20 5a 00 99 20

60: 00 00 c5 c5 41 0c 00 00 00 0f 06 42 00 00 00 00

70: 2c 78 c4 40 01 10 00 00 01 10 00 00 20 00 20 00

80: 00 00 00 c0 00 a0 c8 23 00 00 10 90 00 00 c5 20

90: 00 00 08 80 00 00 00 00 06 00 06 10 7f 03 01 01

a0: 12 0a 00 19 00 00 00 00 00 00 00 00 33 31 00 02

b0: 05 cc 84 00 00 00 00 00 00 00 00 00 00 00 00 00

c0: 00 00 00 00 00 00 00 00 0a 00 0a 00 08 00 02 a8

d0: 0a 00 02 43 42 00 00 00 00 00 00 00 01 00 c0 87

e0: 0a 00 02 35 42 00 00 00 00 00 00 00 00 04 c1 e0

f0: 00 00 00 00 00 00 00 00 10 00 0c 00 00 00 00 00

 

Unfortunately, I have not come across the nForce MCP 55 or 51 chipset equivalent of, for example, the Intel® 631xESB/632xESB I/O Controller Hub "Southbridge" chipset datasheet......which probably will give details on how to switch the chipset mode from IDE to ACHI to RAID by writing to a specific address or something......

Link to comment
Share on other sites
djcoma1200
djcoma1200
Posted
Posted

I'm making some progress.

 

Got the iPC PPF5 Final 10.5.6 Leopard release installed with working audio and graphics card.

 

I was able to get the graphics string which I saved. I also made the modified DSDT file no problem.

 

I installed Dr. Hurt's Chameleon RC3 release to the volume that I will be installing Snow Leopard to. I'm confused as to what I do from here. Using that version/install of the bootloader do I need to replace or edit the boot file at all at this point?

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
I'm making some progress.

 

Got the iPC PPF5 Final 10.5.6 Leopard release installed with working audio and graphics card.

 

I was able to get the graphics string which I saved. I also made the modified DSDT file no problem.

 

I installed Dr. Hurt's Chameleon RC3 release to the volume that I will be installing Snow Leopard to. I'm confused as to what I do from here. Using that version/install of the bootloader do I need to replace or edit the boot file at all at this point?

 

No because RC3 works fine......here is a brief checklist for you to tick off as you go.......

 

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

 

2. Format a HFS+ volume as your target Snow Leopard OS X volume (OSX_MAIN) and any other volumes your require on the GPT partitioned HDD using Disk Utility

 

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

 

4. Establish OS X target HDD ownership

 

5. Run EFIStudio or OSx86Tools to generate the graphics string for your graphics card

 

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

 

7. Put all the necessary kexts in /Extra/Extensions/, sort out the com.apple.Boot.plist and SMBIOS.plist files to put in /Extra, as well as putting DSDT.aml in / or in /Extra......

 

8. Carry out Part F step 14.

 

Then follow Part F steps 15. to 20. and after you have a working Snow Leopard system you can clone it to the Leopard volume as a backup system......or, keep both the Leopard and Snow Leopard systems.......

 

If anything is not clear, I will try to clarify matters for you....... ;)

 

Oh. Convenient but obvious website for sleuthing out hardware I'd stuff.

 

Pci database

 

Thanks. Agreed.......same as this one...... ;)

Link to comment
Share on other sites
djcoma1200
djcoma1200
Posted
Posted

Thanks again verdant. I did run into one roadblock but managed to get around it by installing Leopard on a completely different hard drive than the one that I'm going to have Snow Leopard on. What happened was I had formatted the drive originally as Master Boot Record like your 10.5.6 guide told me to do. When I got to the step where I was supposed to install Snow Leopard it wouldn't let me because the drive wasn't GUID partitioned.

 

I took another drive and then installed Leopard to that, saving the image I had made of the drive that was to have Snow Leopard installed on it. Then I repartitioned the original drive so it was GUID and loaded the image to one of the new partitions. I went back and adjusted the UUID's to reflect the change since I had to repartition.

 

I just tried to install Snow Leopard and it said install failed when it was almost complete. I ran into this same issue when I was trying to install Leopard on a drive that wasn't completely erased to begin with so I think that may be my issue. Can I install Snow Leopard on to a blank partition, and then add in the files from my image of the drive afterwards through Leopard? That should work just the same right?

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
Thanks again verdant. I did run into one roadblock but managed to get around it by installing Leopard on a completely different hard drive than the one that I'm going to have Snow Leopard on. What happened was I had formatted the drive originally as Master Boot Record like your 10.5.6 guide told me to do. When I got to the step where I was supposed to install Snow Leopard it wouldn't let me because the drive wasn't GUID partitioned.

 

I took another drive and then installed Leopard to that, saving the image I had made of the drive that was to have Snow Leopard installed on it. Then I repartitioned the original drive so it was GUID and loaded the image to one of the new partitions. I went back and adjusted the UUID's to reflect the change since I had to repartition.

 

I just tried to install Snow Leopard and it said install failed when it was almost complete. I ran into this same issue when I was trying to install Leopard on a drive that wasn't completely erased to begin with so I think that may be my issue. Can I install Snow Leopard on to a blank partition, and then add in the files from my image of the drive afterwards through Leopard? That should work just the same right?

 

Glad to help...... :)

 

Oops, sorry....I forgot to tell you to use GPT when following my blog iPC 10.5.6 Lepard install guide (which used MBR rather than GPT because doing so raised fewer booting issues with BIOS based PCs versus EFI based Intel Macs and so made multi-booting Windows easier in the pre-Chameleon and pre-EasyBCD 2.0 days).......... -_-

 

Ignore the 'Install Failed' message because the Retail Mac OS X Install DVD is attempting to restart your PC after having installed Snow leopard to the target volume, thinking it is a Mac with EFI and GPT HDD partitioning!........just reboot the PC and select your HDD Snow Leopard volume icon in the Chameleon bootloader menu......

Link to comment
Share on other sites
djcoma1200
djcoma1200
Posted
Posted

Oh snap I assumed it was a fail so I have been trying to reinstall it and cant even get back to that point. It will like freeze up but if I click one of the menus up top it will start going again. Kinda weird. Can I just install it straight from inside Leopard?

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
Oh snap I assumed it was a fail so I have been trying to reinstall it and cant even get back to that point. It will like freeze up but if I click one of the menus up top it will start going again. Kinda weird. Can I just install it straight from inside Leopard?

 

Since you have Leopard on another HDD, why not just use its Disk Utility to erase the SL OS X target volume, set up /Extra/ directory again etc. and then use the nForce132DVD to run the Retail OS X Install DVD again.....?

Link to comment
Share on other sites
djcoma1200
djcoma1200
Posted
Posted

I did end up doing that but what I did was copy over the Extra folder and all that stuff AFTER snow leopard was installed to the HD. Would this have some sort of effect on the process?

 

Also, I had the sound and graphics working on Leopard but how would I go about getting it to work with Snow Leopard now? Besides adding the graphics string do I also need to go in and copy the NVDarwin kext that matched my graphics card that I chose during the Leopard install? Same with the audio?

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
I did end up doing that but what I did was copy over the Extra folder and all that stuff AFTER snow leopard was installed to the HD. Would this have some sort of effect on the process?

 

Also, I had the sound and graphics working on Leopard but how would I go about getting it to work with Snow Leopard now? Besides adding the graphics string do I also need to go in and copy the NVDarwin kext that matched my graphics card that I chose during the Leopard install? Same with the audio?

 

1. Adding the /Extra directory etc. after Snow Leopard Retail DVD installation should have no adverse effect........they are independent installations.....

 

2. Are you now able to boot into SL on your HDD?

 

3. Please put your system details in your signature as it saves me from having to ask questions.....

 

4. The graphics string and the injector kext and the Chameleon 2.0 GraphicsEnabler methods for injecting your video card details are mutually exclusive.........so only one should be used........see post #1

 

5. To help you sort out your audio, I need to know what your MOBO audio/chipset codec is.......

Link to comment
Share on other sites
djcoma1200
djcoma1200
Posted
Posted

Ok so I ended up totally redoing the install. I can boot into SL.

 

Specs for my PC:

XFX nForce 680i LT SLI MOBO

Quad Core 2.4 Ghz

4GB RAM

Geforce 8800 GTS 320 MB Video Card

ALC 885 was the audio codec that worked for me in Leopard and after checking around it looks like the 889a is the same thing or works with the 885.

 

EDIT: Video is now working great. As I suspected I didn't enter in the graphics string correctly so I fixed that and it now works.

 

Doing some research now on how I can get the sound to work...

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...