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

Just proves how MOBO-specific DSDT files are! Glad you got Audio sorted by replacing all instances of AZA with HDEF plus the mods in post #2......... :) What about sleep/waking......does that work for you?

 

Nope, no luck with sleep. I have tried a few off the shelf sleep enablers with no luck. I'm making a noobish assumption that it's related to the oddball drivers that we are running for nforce boards or something fixable in a dsdt or the other acpi tables or. . .*shrug* outside of my skillset to try to figure that out unless i get lucky.

 

That vanilla audio stuff, although functional, spams a few applehda errors; specifically one related to using a generic codec and missing sources although everything is working. I will investigate it and sleep further over spring break i suppose.

 

I have a few off the cuff questions :

-Does anyone running/booting using the various nforce sata drivers have functional sleep under 10.6?

 

-I am using PlatformUUID at the moment, i noticed you can put a UUID into chameleon now; does using just chameleon not break iTunes + Pro App serialization etc. if i remove PlatformUUID?

 

-Is anyone with a nForce board (hopefully something MCP55 based) running two video cards successfully via EFI string injection? (GraphicsEnabler=Yes only picks up 1 card); the listed methods for easily finding your address involves switching slots around and using your 2nd slot as a primary display to pull the pciroot address, and my motherboard does not allow the 2nd slot to be the boot screen (thus making gfxutil useless given that it only picks up the first video display, and only searches the device tree for 1 instance of display or ethernet, not all of them)

 

I have been staring at ioreg trying to sluth it out. I really don't want to hand convert a bunch of hex tables to get that notation that the bootloaders require if i don't have to. ( but i will probably have to ) Just wondering if anyone has had success with that.

EDIT : I read the gfxutil documentation and the author of the tool lists how the conversion between ioreg data and pciroot stuff works. I guess i have to do it by hand. I shall post more information on how this works once i get around to doing it.

 

 

 

EDIT : I attached my fixed DSDT w/ the usual rtc,etc fixes + my mobo specific audio fix for legacyhda. Anyone with an EVGA i680 or a motherboard with similar DSDT should be able to see the patches from verdant's guide in it plus my small change. Do a search for HDEF to find the simple change i made elsewhere. This isn't perfect, the attached KEXT spams errors on boot but works. I have *not* yet tested the Digital audio, although it shows up in my audio outputs. I was using a current version if iaslme (1.2) for my compile / decompile, i did not have to force compile.

 

If anyone has questions about what i did here, post them to the board so i can publicly reply where others can read it. :D

dsdt_fixedaudiolegacy.zip

Link to comment
Share on other sites

Nope, no luck with sleep. I have tried a few off the shelf sleep enablers with no luck. I'm making a noobish assumption that it's related to the oddball drivers that we are running for nforce boards or something fixable in a dsdt or the other acpi tables or. . .*shrug* outside of my skillset to try to figure that out unless i get lucky.

 

That vanilla audio stuff, although functional, spams a few applehda errors; specifically one related to using a generic codec and missing sources although everything is working. I will investigate it and sleep further over spring break i suppose.

 

I have a few off the cuff questions :

-Does anyone running/booting using the various nforce sata drivers have functional sleep under 10.6?

 

According to the thread poll entries, it would appear so but I have seen no posts in this thread or elsewhere confirming success and explaining how.....

 

-I am using PlatformUUID at the moment, i noticed you can put a UUID into chameleon now; does using just chameleon not break iTunes + Pro App serialization etc. if i remove PlatformUUID?

 

I currently use RC3 and PlatformUUID as I am waiting for RC5........

 

-Is anyone with a nForce board (hopefully something MCP55 based) running two video cards successfully via EFI string injection? (GraphicsEnabler=Yes only picks up 1 card); the listed methods for easily finding your address involves switching slots around and using your 2nd slot as a primary display to pull the pciroot address, and my motherboard does not allow the 2nd slot to be the boot screen (thus making gfxutil useless given that it only picks up the first video display, and only searches the device tree for 1 instance of display or ethernet, not all of them)

 

I am not aware of anyone so far......

 

I have been staring at ioreg trying to sluth it out. I really don't want to hand convert a bunch of hex tables to get that notation that the bootloaders require if i don't have to. ( but i will probably have to ) Just wondering if anyone has had success with that.

EDIT : I read the gfxutil documentation and the author of the tool lists how the conversion between ioreg data and pciroot stuff works. I guess i have to do it by hand.

 

Yes and like with DSDT.......it all takes time.......not something I have much of at present.....

 

EDIT : I attached my fixed DSDT w/ the usual rtc,etc fixes + my mobo specific audio fix for legacyhda

 

Thanks for that......it will be a great help to readers of this thread with the same MOBO...... :)

Link to comment
Share on other sites

First off, I can't seem to see your blog! It's saying "You do not have permission"? But anyway....

 

Let me see if I got this all correct:

 

1. create 2 partitions (probably name it OSX_SL and OSX_SL_Backup)

2. install leopard on both using one of the install DVD distros. (do I just google these?) Since Mysticus C's tutorial on installing leopard is so old, I'm guessing that SATA DVD drive is OK to use now, correct?

3. install chameleon on both OSX on both partitions and EasyBCD on Windows. (or maybe EZBCD on Windows before installing OSX)

4. Follow part B, C and E in this tutorial

 

One thing I don't understand is when you said make sure your MOBO BIOS allow booting from a USB flash drive. Don't all MOBOs allow booting from a USB flash drive?

Link to comment
Share on other sites

First off, I can't seem to see your blog! It's saying "You do not have permission"? But anyway....

 

You may be able to see it when you have more posts......but PM admins/mods to ask....

 

Let me see if I got this all correct:

 

1. create 2 partitions (probably name it OSX_SL and OSX_SL_Backup) Y

2. install leopard on both using one of the install DVD distros. (do I just google these?) Since Mysticus C's tutorial on installing leopard is so old, I'm guessing that SATA DVD drive is OK to use now, correct? N, only install leopard on OSX_SL_Backup and SATA DVD issue remains because AppleNForceATA kexts are the same....

3. install chameleon on both OSX on both partitions and EasyBCD on Windows. (or maybe EZBCD on Windows before installing OSX) Y

4. Follow part B, C and E in this tutorial Y

 

One thing I don't understand is when you said make sure your MOBO BIOS allow booting from a USB flash drive. Don't all MOBOs allow booting from a USB flash drive? Unfortunately not from some reports I have had......

 

Hope you are successful....... :(

Link to comment
Share on other sites

Hope you are successful....... :(

 

 

OK, now i'm confused. If I only install leopard on the "backup" partition, how am I going to upgrade to SL on the main partition(OSX_SL) since it will be empty.

 

Also, I'm thinking of using iPC 10.5.6 distro. Is this OK? I also saw you mentioned in some of your posts that we should leave out video, audio and network on the initial installation. How do we add it later after everything is OK?

Link to comment
Share on other sites

OK, now i'm confused. If I only install leopard on the "backup" partition, how am I going to upgrade to SL on the main partition(OSX_SL) since it will be empty.

 

Also, I'm thinking of using iPC 10.5.6 distro. Is this OK? I also saw you mentioned in some of your posts that we should leave out video, audio and network on the initial installation. How do we add it later after everything is OK?

 

You will do a clean SL install not an ugrade.......you are only using the Leopard installation to generate and patch your DSDT.aml file for SL, prepare the USB flash drive SL installer and be able to run Chameleon installer etc. to install the Chameleon bootloader onto OSX_SL and to download any additional kexts you need etc......and add them to SL using Kext Helper b7......

 

iPC10.5.6 is fine......I use it as my Leopard distro.......add them using Kext Helper b7......

 

BTW as my guide says for safety, disconnect your Windows 7 HDD from the MOBO before installing SL......

Link to comment
Share on other sites

OK, I've finished installing leopard, but I can't seem to get into the desktop for the first time. I just don't see any option to go into leopard! If I boot from the windows hdd, it will take me to windows 7. If I boot from my extra drive, which is where osx_sl_backup is on, then it gives me a boot error. If I leave the installation DVD in the drive, it takes me back to the installation process. I wonder what am I missing?

Link to comment
Share on other sites

OK, I've finished installing leopard, but I can't seem to get into the desktop for the first time. I just don't see any option to go into leopard! If I boot from the windows hdd, it will take me to windows 7. If I boot from my extra drive, which is where osx_sl_backup is on, then it gives me a boot error. I wonder what am I missing?

 

What is the boot error you are seeing.......? Do you see the Darwin/Chameleon boot prompt:?

 

If not, you should install Leopard on the 1st HDD volume so that the BIOS boot menu finds the Chameleon bootloader....

 

Have you installed EasyBCD 2.0 Beta on Windows 7 and added the OS X entry.....?

 

Boot with the Install DVD and at the boot: prompt, type

-v rd=diskXsY

where the value for X in rd=diskXsY or rd=diskXsY is dependent on the number of storage/media read/write devices connected to the MOBO.......X starts from 0 and Y starts from 1. For example, the first volume on the first internal HDD will have the Disk Indentifier of disk0s1, while the second volume will be disk0s2 and so on.

Link to comment
Share on other sites

What is the boot error you are seeing.......? Do you see the Darwin/Chameleon boot prompt:?

 

If not, you should install Leopard on the 1st HDD volume so that the BIOS boot menu finds the Chameleon bootloader....

 

Have you installed EasyBCD 2.0 Beta on Windows 7 and added the OS X entry.....?

 

Boot with the Install DVD and at the boot: prompt, type

-v rd=diskXsY

where the value for X in rd=diskXsY or rd=diskXsY is dependent on the number of storage/media read/write devices connected to the MOBO.......X starts from 0 and Y starts from 1. For example, the first volume on the first internal HDD will have the Disk Indentifier of disk0s1, while the second volume will be disk0s2 and so on.

 

 

boot error is "boot0: error". I only see Darwin/Chameleon when the install DVD is in the dvd drive, otherwise no.

 

My extra internal HDD is really a storage drive, where I keep my data. I just shrink it down by 100GB so I could install OSX. So the two extra volumes I created is actually the 4th and 5th volume on the HDD.

 

Untitled_7.jpg

 

 

The 39.06GB partition is the OSX_SL_Backup that leopard is on right now.....

 

 

maybe I didn't tick the requirement kexts at the start of the installation. can you verify which ones are absolutely important because I think I got most of them.

Link to comment
Share on other sites

boot error is "boot0: error". I only see Darwin/Chameleon when the install DVD is in the dvd drive, otherwise no.

 

My extra internal HDD is really a storage drive, where I keep my data. I just shrink it down by 100GB so I could install OSX. So the two extra volumes I created is actually the 4th and 5th volume on the HDD.

 

Untitled_7.jpg

 

 

The 39.06GB partition is the OSX_SL_Backup that leopard is on right now.....

 

OK then see here to make the OS volume partition active.....

 

EDIT Just noticed that you have OS X Main on a logical volume.......to be a bootable volume OS X has to be on a primary partition AFAIK......

Link to comment
Share on other sites

OK then see here to make the OS volume partition active.....

 

EDIT Just noticed that you have OS X Main on a logical volume.......to be a bootable volume OS X has to be on a primary partition AFAIK......

 

 

Thanks for the link. I'll try it out later because I have to go to work right now.

 

yeah, I know about the osx main volume. I was testing out the backup volume first before I "erase" the osx main. Or maybe I'll just do it later tonight. thanks.

Link to comment
Share on other sites

Thanks for the link. I'll try it out later because I have to go to work right now.

 

yeah, I know about the osx main volume. I was testing out the backup volume first before I "erase" the osx main. Or maybe I'll just do it later tonight. thanks.

 

OK........suggest you install EasyBCD 2.0 Beta ( I am using build 76 with Windows 7 with no problems) in Windows 7 anyhow and set up an OS X entry....the current build is 82......

Link to comment
Share on other sites

OK........suggest you install EasyBCD 2.0 Beta ( I am using build 76 with Windows 7 with no problems) in Windows 7 anyhow and set up an OS X entry....the current build is 82......

 

 

I've installed EasyBCD 2.0 beta but I can't seem to add osx as an entry because both volumes don't have a drive letter. Also, I've tried to follow the guide through your link but I can't find the partition for osx_backup. This is starting to be a pain.....

 

But as you can see from my current setup, the "osx_back" volume(39.6GB) is already active and primary. Yet, I can't get it to boot up chameleon. There is something else wrong here.

 

Untitled-1_1.jpg

Link to comment
Share on other sites

I've installed EasyBCD 2.0 beta but I can't seem to add osx as an entry because both volumes don't have a drive letter. Should I have created it with a drive letter? Also, I've tried to follow the guide through your link but I can't find the partition for osx_backup. This is starting to be a pain.....

 

But as you can see from my current setup, the "osx_back" volume(39.6GB) is already active and primary. Yet, I can't get it to boot up chameleon. There is something else wrong here.

 

Untitled-1_1.jpg

 

1. In EasyBCD, are you able to add a new boot entry, select MacOS > Generic X86 > Add > Save......?

 

2. When you boot from the OS X Install DVD, go to Terminal under Utilities, and type

diskutil list

and post the output.......

 

3. Then assuming the disk identifier is found for your OS X system volume, boot from the OS X Install DVD with

-v rd=diskXsY

using X and Y values identified from the diskutil list.....

 

BTW you cannot expect the process to be as pain-free as with OS X the first volume on a HDD...........but hopefully I can help you get OS X running on your PC....... :rolleyes:

Link to comment
Share on other sites

1. In EasyBCD, are you able to add a new boot entry, select MacOS > Generic X86 > Add > Save......?

 

2. When you boot from the OS X Install DVD, go to Terminal under Utilities, and type

diskutil list

and post the output.......

 

3. Then assuming the disk identifier is found for your OS X system volume, boot from the OS X Install DVD with

-v rd=diskXsY

using X and Y values identified from the diskutil list.....

 

BTW you cannot expect the process to be as pain-free as with OS X the first volume on a HDD...........but hopefully I can help you get OS X running on your PC....... :rolleyes:

 

 

This is what my easybcd entry looks like:

 

Untitled-1_14.jpg

 

I then write MBR in the "bootloader manager" option. And then I restart the computer........sure enough there are 2 entries, but only the windows 7 work. The mac osx option does not. It just said something about bootloader is missing.....or something like that, and told me to put the windows DVD in to repair.

 

I already know the osx_back volume. It is disk1s6. Do I do the -v rd=disk1s6? what is that going to do?

 

 

 

Update: OK, using your -v rd=disk1s6 command, I got into the desktop. Now what do I do from there? Do I set up chameleon from there, or do I start the part b, c and e of this tutorial?

Link to comment
Share on other sites

This is what my easybcd entry looks like:

 

Untitled-1_14.jpg

 

I then write MBR in the "bootloader manager" option. And then I restart the computer........sure enough there are 2 entries, but only the windows 7 work. The mac osx option does not. It just said something about bootloader is missing.....or something like that, and told me to put the windows DVD in to repair.

 

I already know the osx_back volume. It is disk1s6. Do I do the -v rd=disk1s6? what is that going to do?

 

 

 

Update: OK, using your -v rd=disk1s6 command, I got into the desktop. Now what do I do from there? Do I set up chameleon from there, or do I start the part b, c and e of this tutorial?

 

You should not have to press the "Write MBR" button since you are already booting from the Windows 7 MBR on the HDD......and the OS X volumes are on another HDD......in fact, pressing the "Write MBR" button probably overwites the modified MBR (i.e. with the OS X entry just added).......

 

Yes, reinstall Chameleon 2.0, using RC4 or RC3 via Dr Hurt's unofficial RC3 installer or RC4 installer.....as you want OS X Leopard to be bootable directly without using the Install DVD and working 100% before you start installing SL......

Link to comment
Share on other sites

What drive letter should the mac os x be on? Because as you know, osx volumes don't have any letter. Is your easybcd setup similar to mine? do you mind posting it?

 

 

I've installed chameleon 2.0 rc4, but it's still the same. I still can't boot from osx volume.

 

But I think for now I'm going to go to sleep. I've been up the whole night trying to figure this out. I thought it would be hard, but I didn't think I'd be stuck at such an early stage.

 

Thanks a lot for trying to help.....

Link to comment
Share on other sites

What drive letter should the mac os x be on? Because as you know, osx volumes don't have any letter. Is your easybcd setup similar to mine? do you mind posting it?

 

 

I've installed chameleon 2.0 rc4, but it's still the same. I still can't boot from osx volume.

 

But I think for now I'm going to go to sleep. I've been up the whole night trying to figure this out. I thought it would be hard, but I didn't think I'd be stuck at such an early stage.

 

Thanks a lot for trying to help.....

 

Glad to help...... :)

 

EasyBCD will show the OS X entry as having a drive letter because it gives it one.......in my case it is Drive C:\ with Bootloader Path: \NST\nst_mac.mbr.......the drive letter associated with OS X is not fixed......it all depends on the number of storage/drive devices that Windows sees as being connected to the MOBO.......

 

I suggest you put

 

-v rd=disk1s6

 

under Kernel Flags in com.apple.Boot.plist as follows:

 

Boot into your OS X HDD system, then

 

1. Go to the Terminal, and at the $ prompt, type in

 

sudo nano /Library/Preferences/SystemConfiguration/com.apple.Boot.plist

 

2. Enter your password when requested. Use the arrow keys on the keyboard to move the cursor within the Terminal window.

 

3. Type in (without any spaces anywhere except where there are spaces)

 

"-v rd=disk1s6"

between <string> and </string> under <key>Kernel Flags</key>.

 

4. Move the cursor the Terminal window down until it no longer moves, then press Ctrl O and then Enter, to save the modified com.apple.Boot.plist file.

 

5. Press Ctrl X to Exit and type "exit" at the $ prompt to log out of the Terminal and then close and quit Terminal.

BTW in BIOS have you set the boot order to include both HDDs as well your DVDRW(s).....?

 

What happens when you choose to boot from the OS X volume HDD by going into the BIOS Boot Menu by pressing F8 (or perhaps F12) immediately you see the bootscreen message to enter the BIOS setup by pressing DEL?......do you boot into the Chamelelon bootloader......?

Link to comment
Share on other sites

BTW in BIOS have you set the boot order to include both HDDs as well your DVDRW(s).....?

 

What happens when you choose to boot from the OS X volume HDD by going into the BIOS Boot Menu by pressing F8 (or perhaps F12) immediately you see the bootscreen message to enter the BIOS setup by pressing DEL?......do you boot into the Chamelelon bootloader......?

 

 

I'm going to try your steps......

 

 

 

I can't boot into osx hdd because it would only gives me "boot0: error". I tried to set it as "active" but can't seem to find the partition to set. Last time I blindly set partition 4 it just gave me " boot 0: MBR" and below that "boot 0: done" and the cursor kept blinking. It also messed up my windows bootmanager and I had to repair it with my windows DVD.

 

 

IMAGE_007.jpg

 

IMAGE_008.jpg

 

As you can see, none of the partitions look remotely close to any osx partition.

Link to comment
Share on other sites

Omg it works! All I can say is don't give up. Thanks to Verdant that man knows his S&%^!

verdant.png

 

Mobo and extras (1) asus striker 2 nse 790i with both built-in ether nets working 100%

(1) q6600 core 2 quad

(1) pata samsung dvd/cd burner working

(1) sata WD 160 gb hard drive

(1) adesso RF keyboard and mouse tochpad combo

(1) gtx280 nvidia

(2) 1Gig 1333 ddr3 ocz sticks

(2) 2Gig 1600 ddr3 ocz sticks

(1) Highpoint rcoketraid 2302 with esata trayless raid 10 4tb 1 ntfs partition

 

Current Os with kexts

 

10.6.2 Snow leopard using myhack installer to complete most of the dirty work

using these kexts in system/library/extensions then using kext utility to repair permissions

 

ad1988bfix obsolete 32bit

slackshacks applenforceata

nforcelan.kext

 

Virtualbox=Virtualizing ubuntu, win 7, and backtrack 3

 

What doesn't work

1. Sleep obviously

 

2. Audio over hdmi via gtx280 from spdif from mobo internally. Would be nice for audio via hdmi on my tv. Looking into finding a way to get a spdif inserted via optical cable on back of mobo to hdmi via dvi &s/pdif digital coax / optical toslink audio to hdmi converter. Maybe i hooked it up wrong on mobo just dont have win7 running as dual boot to check hdmi audio yet.

 

3. highpoint 2302 rocketraid drops out and makes 2302 pci-e cards alarm go off when heavy usage occurs such as adding music collection to itunes or copying large file to or from esata array.

 

need to fix my signature sorry for the long post

 

yes you are seeing it correctly mac host with 2 linux guests and win 7 ;)

post-291122-1268794318_thumb.png

Link to comment
Share on other sites

I'm going to try your steps......

 

 

 

I can't boot into osx hdd because it would only gives me "boot0: error". I tried to set it as "active" but can't seem to find the partition to set. Last time I blindly set partition 4 it just gave me " boot 0: MBR" and below that "boot 0: done" and the cursor kept blinking. It also messed up my windows bootmanager and I had to repair it with my windows DVD.

 

 

IMAGE_007.jpg

 

IMAGE_008.jpg

 

As you can see, none of the partitions look remotely close to any osx partition.

 

Hi there,

 

Here is my current Diskutil list:

 

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *465.8 Gi disk0

1: Linux 957.0 Mi disk0s1

2: Linux_LVM 231.9 Gi disk0s5

3: Windows_NTFS SHARED 232.9 Gi disk0s2

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: Apple_partition_scheme *465.8 Gi disk1

1: Apple_partition_map 31.5 Ki disk1s1

2: Apple_Driver43 28.0 Ki disk1s2

3: Apple_Driver43 28.0 Ki disk1s3

4: Apple_Driver_ATA 28.0 Ki disk1s4

5: Apple_Driver_ATA 28.0 Ki disk1s5

6: Apple_FWDriver 256.0 Ki disk1s6

7: Apple_Driver_IOKit 256.0 Ki disk1s7

8: Apple_Patches 256.0 Ki disk1s8

9: Apple_HFS FAT32_SHARED 465.6 Gi disk1s10

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *465.8 Gi disk2

1: Windows_NTFS Vista64_System 232.9 Gi disk2s1

2: Windows_NTFS Win7_64_System 232.9 Gi disk2s2

/dev/disk3

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *698.6 Gi disk3

1: Apple_HFS OSX_1056_BootB 10.1 Gi disk3s1

2: Apple_HFS OSX_1061_Backup 125.1 Gi disk3s2

3: Apple_HFS OSX_1062_Main 125.1 Gi disk3s3

4: Apple_HFS OSX_10.5.2 125.1 Gi disk3s5

5: Apple_HFS OSX_10.5.5 125.1 Gi disk3s6

6: Apple_HFS OSx86_Archive 188.0 Gi disk3s7

/dev/disk4

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *465.8 Gi disk4

1: Apple_HFS OSX_1056_BootA 10.9 Gi disk4s1

2: Apple_HFS OSX_1056_Main 175.1 Gi disk4s2

3: Apple_HFS OSX_1056_Backup 175.1 Gi disk4s3

4: Apple_HFS OS_X_Software 104.6 Gi disk4s5

/dev/disk5

#: TYPE NAME SIZE IDENTIFIER

0: USB_Boot *245.9 Mi disk5

 

As you can see, there is nothing apparently wrong with your OS X partitions comparing yours to mine......how is the Windows_NTFS Swap volume set up.....? If you could move the contents of the Windows_NTFS Swap volume elswhere, I would recommend installing a basic OS X Leopard system on the 10.2 GiB volume as a OS X Boot volume, as I have done.......see post #1:

 

1st volume at the start of HDD is a small 10GB volume (choose a name without spaces e.g. Leopard_Boot or OS_X_Boot etc) to use as a OS X boot volume with ONLY a basic fully working OS X install from your chosen OS X Install DVD (which enables you to use its Disk Utility functions on the other OS X volumes), together with these installers or apps:

 

Kext Helper b7

OSx86Tools

Chameleon 2.0 RC1

Chameleon 2.0 RC2

Chameleon 2.0 RC3

Chameleon 2.0 RC4

PC_EFI v10.1 - 10.6

 

and any other Utility software you find very useful for OS X system installation/maintenace/repair etc., to enable you to modify/test OS X updates on the Main and Backup OS X volumes without ever risking not being able to boot into OS X on this HDD.......

 

@ dubz

 

Glad my install guide helped you to install and enjoy SL..... ;)

DIskUtilList.rtf

post-200327-1268798348_thumb.png

Link to comment
Share on other sites

I've moved the swap files volume over so I can setup osx on the first volume as you had suggested. Hopefully this time chameleon will show. *fingers crossed*

 

 

Update: I got chameleon to come up after installing osx to boot volume. However, after choosing any osx volume( osx_boot or osx_back) that has leopard on it, it automatically restarts my computer. why? Does it have anything to do with my BIOS settings? Or maybe I should have included or left out certain kexts?

Link to comment
Share on other sites

I've moved the swap files volume over so I can setup osx on the first volume as you had suggested. Hopefully this time chameleon will show. *fingers crossed*

 

 

Update: I got chameleon to come up after installing osx to boot volume. However, after choosing any osx volume( osx_boot or osx_back) that has leopard on it, it automatically restarts my computer. why? Does it have anything to do with my BIOS settings? Or maybe I should have included or left out certain kexts?

 

I do not have much time right now to help but with OS X Leopard, it could be wrong BIOS settings and/or kernel.......if there is a problem with kexts you would generally see a kernel panic rather than a automatic restart.......so use Voodoo 9.5.0 kernel......

 

While with OS X Snow Leopard, it could be wrong BIOS settings and/or kernel and/or no RTC DSDT patch.......if there is a problem with kexts you would generally see a kernel panic rather than an automatic restart.......use vanilla 10.6 kernel.......

 

For now, all I do is to suggest that you read post #1 in my threads again......

Link to comment
Share on other sites

I do not have much time right now to help but with OS X Leopard, it could be wrong BIOS settings and/or kernel.......if there is a problem with kexts you would generally see a kernel panic rather than a automatic restart.......so use Voodoo 9.5.0 kernel......

 

While with OS X Snow Leopard, it could be wrong BIOS settings and/or kerne and/or no RTC DSDT patch.......if there is a problem with kexts you would generally see a kernel panic rather than a automatic restart.......use vanilla 10.6 kernel.......

 

For now, all I do is to suggest that you read post #1 in my threads again......

 

 

That's alright I understand. I'll just ask around, I'm in no hurried anyway. Thanks for helping up to this point!

Link to comment
Share on other sites

That's alright I understand. I'll just ask around, I'm in no hurried anyway. Thanks for helping up to this point!

 

Glad to help......also see my Leopard distro install guides in my blog...... :wacko:

Link to comment
Share on other sites

 Share

×
×
  • Create New...