529 replies to this topic

[MACinized]

[updated: 29 September 2009]

Constructive comments/suggestions/recommendations are welcome to improve this guide.

Important Note: This guide is based on personal experience of running an "untouched" retail Snow Leopard. See signature below for my computer's specifications.

Pre-requirement: a computer with working Mac OS X.
(Preferably, you are following this guide using your existing OSx86 Leopard)
Download this MacLoader_SL kit.
(uses DSDT Patcher by fassl, Chameleon 2 RC3 by the Chameleon Team, & a number of kexts from Stell's Blog)

Phase 1.1: Pre-Installation (DSDT.aml)

1. Open unzipped MacLoader_SL folder downloaded from above.

2. Open 1_DSDT_Patcher folder and double-click the "1_GetDSDT" file.

3. When "dsdt-fixed.dsl" file is opened, look for the "Device (RTC" line. (If it's not automatically opened, go to the Tools folder and open the dsdt-fixed.dsl manually with TextEdit).

4. Edit accordingly: (i.e. "//Length" should be "0x02,")


5. Save "dsdt-fixed.dsl" file then double-click the "2_DSDTpatcher" file.

6. Press [ENTER] then you should now have your "DSDT.aml".


Phase 1.2: Pre-Installation (Snow Leopard Installer)

1. Use an 8GB-flashdisk or (external)HDD-partition. Let's call it SnowLeoInstaller.

2. Restore your retail Snow Leopard DVD Installer to SnowLeoInstaller. Uncheck "Erase destination".


3. Go to MacLoader_SL folder again.

4. Put any extra kext you need for your computer inside the "KEXTs" folder.

5. Double-click "2_SnowLeoInstaller" file then follow prompts.


6. Carry a copy of the MacLoader_SL with you (e.g. save it to a usb-flashdisk).

Phase 2: Installation

1. With your SnowLeoInstaller plugged-in, make it the 1st boot device thru your bios.


2. At restart, if retail Snow Leopard was properly restored and the bootloader installed, you should now be able to boot with your SnowLeoInstaller.

3. After the "Select Language" screen, open Disk Utility.


4. Select target harddisk and partition it using GUID Partition Table.

5. Install Snow Leopard to the the target disk you prepared in step 4.


6. After successful installation, reboot with your SnowLeoInstaller again but interrupt it by pressing any key.


7. Select the partition of your newly-installed Snow Leopard then press [ENTER].


Phase 3: Post-Installation

1. Hopefully you're now able to boot to your newly-installed Snow Leopard.


2. Fill-in necessary information to get to your Snow Leopard desktop.


3. Open again the MacLoader_SL folder then double-click the "3_MacLoader" file and follow prompts.

4. Unplug your SnowLeoInstaller then reboot. If all is well, you should now be able to boot with your vanilla Snow Leopard.

5. If you need to update the MacLoader (i.e. add/remove kext, use an updated DSDT.aml, change Timeout), just go to MacLoader_SL folder and double-click the 4_Updater file.

Done!
__________

here's an updated MacLoader_SL kit:  MacLoader_SL_0.4.zip   1.33MB   4392 downloads

Attached Files

•  MacLoader_SL.zip   1.83MB   912 downloads
•  MacLoader_SL_0.1.zip   1.69MB   403 downloads
•  MacLoader_SL_0.2.zip   1.93MB   551 downloads
•  MacLoader_SL_0.3.zip   1.26MB   1205 downloads
•  MacLoader_SL_old_readme.rtfd.zip   10.46K   343 downloads

[Beto2k7]

This is what I was waiting for. Man I've been following u since ur original Leopard guide. Thx!!!


PS. It works!

[MACinized]

Beto2k7, on Sep 3 2009, 12:44 PM, said:

This is what I was waiting for. Man I've been following u since ur original Leopard guide. Thx!!!


PS. It works!

good to hear that.

now i'm wondrin' why "boot-uuid" flag won't work.

[noob766]

MACinized, on Sep 2 2009, 09:56 PM, said:

good to hear that.

now i'm wondrin' why "boot-uuid" flag won't work.

theres no reason to have it unless you are upgrading.

[kitmac]

Thanx to your guide i was finally able to create my own dsdt and not use someone else's...

I thought the newly created dsdt would correct my audio but it didn't.. guess im missing something else for my alc888

Do you find nvenabler to be better than efi strings or do you use both???

[MACinized]

noob766, on Sep 3 2009, 01:01 PM, said:

theres no reason to have it unless you are upgrading.

i usually prefer to use uuid since it's a more "stable/constant" partition identifier compared to "hd(x,y)" which can variably change especially if an external flashdisk/hdd is plugged-in.

kitmac, on Sep 3 2009, 01:07 PM, said:

Thanx to your guide i was finally able to create my own dsdt and not use someone else's...

I thought the newly created dsdt would correct my audio but it didn't.. guess im missing something else for my alc888

Do you find nvenabler to be better than efi strings or do you use both???

i believe there's another method of patching dsdt to get audio to work (as built-in). that's what i'm also trying to look for. presently, i'm using voodoohda to get my alc888 to work, but no mic-in though.

nvenabler works great for me. i'm not using any efi-string.

[noob766]

MACinized, on Sep 2 2009, 10:08 PM, said:

i usually prefer to use uuid since it's a more "stable/constant" partition identifier compared to "hd(x,y)" which can variably change especially if an external flashdisk/hdd is plugged-in.

only if you have other things booting before your HDD, in your boot sequence.

but that does make sense.
Interestingly enough it appears that string wasn't implemented into RC2
heres the boothelp file from it
 BootHelp.txt   3.64K   459 downloads

[MACinized]

noob766, on Sep 3 2009, 01:13 PM, said:

only if you have other things booting before your HDD, in your boot sequence.

but that does make sense.
Interestingly enough it appears that string wasn't implemented into RC2
heres the boothelp file from it
BootHelp.txt

i'm sorry but what exactly do you mean by this?

Quote

only if you have other things booting before your HDD, in your boot sequence.

does the "-x32" boot-flag negates the "boot-uuid" flag?

[noob766]

MACinized, on Sep 2 2009, 10:15 PM, said:

i'm sorry but what exactly do you mean by this?

does the "-x32" boot-flag negates the "boot-uuid" flag?

my bad, i thought you were inserting the uuid flag into chameleon. not into somewhere else.

Its the boothelp.txt from the chameleon 2.0 rc2 binaries.

[AzN_DJ]

Hey I am having trouble with my installation of snow. So far I haven't used this guide, but I will try this guide next (slightly modified).
First attempt - upgrading straight from 10.5 to Snow, failed, came up with "Generic Error" (very helpful) but corrupted my leopard installation before I could open the log file.
Formatted the drive, burnt a boot-132 disk, put in snow Leopard disk, booted fine, installed, failed at last stage when it tried to bless the disk - apparently it couldn't.

Will this guide fix up the bless problem? And if not, is there another way to?

[MACinized]

noob766, on Sep 3 2009, 01:18 PM, said:

my bad, i thought you were inserting the uuid flag into chameleon. not into somewhere else.

Its the boothelp.txt from the chameleon 2.0 rc2 binaries.

i have "-x32 boot-uuid=[SnowLeo UUID]" as strings to "Kernel Flags" of the com.apple.Boot.plist in my /Volumes/MacLoader/Extra.

[noob766]

MACinized, on Sep 2 2009, 10:28 PM, said:

i have "-x32 boot-uuid=[SnowLeo UUID]" as strings to "Kernel Flags" of the com.apple.Boot.plist in my /Volumes/MacLoader/Extra.

maybe the chameleon team removed support for the UUID strings?

[MACinized]

noob766, on Sep 3 2009, 01:54 PM, said:

maybe the chameleon team removed support for the UUID strings?

or it must be netkas' snowleo-boot file that does not support uuid. coz chameleon 2 rc2 boots fine with the uuid of my leopard-partition.

[noob766]

MACinized, on Sep 2 2009, 11:26 PM, said:

or it must be netkas' snowleo-boot file that does not support uuid. coz chameleon 2 rc2 boots fine with the uuid of my leopard-partition.

well netkas's snowleo-boot file is based off chameleon rc1 so it's possible

[Ger Teunis]

Great tutorial.
A question though, by dsdt-fixed.dsl Device (RTC) section looks completely different.

				Device (RTC)
				{
					Name (_HID, EisaId ("PNP0B00"))
					Name (_CRS, ResourceTemplate ()
					{
						IO (Decode16,
							0x0070,			 // Range Minimum
							0x0070,			 // Range Maximum
							0x01,			   // Alignment
							0x08,			   // Length
							)
						IRQNoFlags ()
							{8}
					})
				}

Do I need to completely replace my Device (RTC) with the one you posted?

[MACinized]

Ger Teunis, on Sep 3 2009, 03:32 PM, said:

Great tutorial.
A question though, by dsdt-fixed.dsl Device (RTC) section looks completely different.

				Device (RTC)
				{
					Name (_HID, EisaId ("PNP0B00"))
					Name (_CRS, ResourceTemplate ()
					{
						IO (Decode16,
							0x0070,			 // Range Minimum
							0x0070,			 // Range Maximum
							0x01,			   // Alignment
							0x08,			   // Length
							)
						IRQNoFlags ()
							{8}
					})
				}

Do I need to completely replace my Device (RTC) with the one you posted?

u don't need to. the only edit u need is the // Length entry. instead of "0x08,", change it to "0x02,".

[Ger Teunis]

Thanks for the reply.

I always seem to get an error when using the DSDT patcher

./dsdt_fixed.txt  3085:					 "33DB4D5B-1FF7-401C-9657-7441C03DD766"
Error	4095 -				  syntax error, unexpected PARSEOP_STRING_LITERAL ^

An AML file is created though, is this expected behaviour?
Sorry for the questions, but I am new at this. Starting from a clean sleet using your tutorial!

Ahh. Too bad, just inspecting the complete tutorial made clear this only works for a GUID partitioned HDD.
Currently on an MBR. Thanks anyways.

[AzN_DJ]

Ok I have followed this guide and am still having issues with the installer being able to bless the drive
Here is a sample of the log file

Finalize disk "Snow" for OS Installation
Finalizing Disk for OS Install
Unable to set 'Snow' as boot disk: The bless tool was unable to set the current boot disk
Install failed: The installer could not start up the computer from the disk "Snow". Try selecting your disk using the Startup Disk Utility.

Then in the main screen it says pretty much the same thing.
My hardware: ASUS P5-KPL-CM
Intel Q6600
2GB ram
250GB Sata Hard drive

I am not sure where the problem lies - I had no issue installing Leopard using vanilla install, apart from the quad core not working by default and having to change the install file, but I just used a boot-132 disk. Is anybody else having this problem with bless?

[BrumBrum74]

Trying this method as all runs until finishing of Create Your Account.

Hangs on

Talking with Apple.

Have internet connection.

How can I finish this step? I know there's some terminal command to get past this, but do not remember what to search for.

[BrumBrum74]

Managed to get in to desktop. Have a GeForce 7800 Go gfx card and the mouse pointer stutters when moving around on the desktop.