[How To] Install Leopard Retail DVD on ASUS P6T Deluxe LGA 1366 (core i7)

[jaydee48]

I installed everything and did exactly as your tutorial said. But i'm having problems with my processor when i enable all cores and HT... my osx is then unstable and crashes every 5 to 10 minutes... sometimes it gives also a kp.I attached an picture of the crash.

Also what i get in the profile is 1 processor and 4 cores and the bus is @ 533.

 

 

 

 

I'm giving you my specs:

 

I7 processor 920

8gb corsair at 1333 mhrz

500gb HDD

Asus 8800 GTX

asus P6T (regular)

DVD

PCI Wireless card

 

Thx for guides and replies !!

[AiBear]

I'm curious why your system still hasn't behaved compared to others. Have you done a full CMOS clear (via the motherboard jumper, with power supply off) followed by a load defaults? What BIOS version? Also, did you take care to make sure the partitions all got cleared? I did this by switching to a different partition map in Disk Utility, formatting like that, and then switching back to GUID just to be sure it really nuked it.

 

Note that I didn't get my system to boot with all cores either when using MAJ's awesome script, only a single core -- I don't know whether it would have or not had I tried again, but this tutorial suddenly worked perfectly when I finally built the EFI correctly so I stopped fiddling.

Don't worry, I'm asking myself the same question.. Apart from the CMOS clear, I pretty much tried everything.

Currently, I'm working on BIOS revision 1303, recently updated from the 10xx version, but it behaves the same. I have practically all older revisions on disk, so I might try if that will change anything. Furthermore, I tried installing on a local disk as well as an external USB disk, but it keeps flunking.

What's interesting though, is the following: I used to be able to boot a iAtkos v5 (10.5.5) install with a patched DSDT file, but it refused to do that this morning... I might have overlooked something, but I'll certainly be looking into that.

And indeed, the DSDT needs EFI to be built right, otherwise it won't use the file (as far as I know at least..)

 

Hey, AiBear,

Let me know what you find out on your system. Hope it's running! If you don't want to bother with the DSDT file comparison, just sent me the script-updated version (that doesn't work) and I'll compare it with a "hand-edited" version. On the other hand, I just hope it wasn't the DSDT file that contributed to your issues. Thanks for your help.

 

Regarding EFI v8: At the time, that version was already scripted and easy to reuse. Version 9 is generally on a GUI installer and I didn't want to bother. But, as it turns out, I've just rewrote the installer script for EFI v9 Chameleon (v1.0.11) and uploaded it in my tutorial. It supports boot graphics, as well.

It's been an interesting process. The EFI v8 required all partitions unmounted, so that created a little bit of work to guarantee that they all get unmounted. The newer EFI v9 bootloader doesn't require that, so I stripped out all that code. However, it turns out I still needed the same process for separate feature I added - drive activation - all partitions need to be unmounted to write to the boot block with fdisk. The reason why I had to add the activation feature with unmounted partitions was because it was normally done during the pre-patch, when all partitions were unmounted anyway. Now, because unmounting is not needed for the bootloader install, I had to add the unmounting process for activation.

I've kept the activation process separate from the pre-patch so that the user can choose to activate a different partition.

Hope that all makes sense. I had to re-read it and re-write it to make it more clear.

 

regards,

MAJ

Thanks for all your help MAJ I'll be looking into the DSDT file myself anyway, as there might just be something wrong with my system at the moment, and I'd like to resolve that. If you want to, I can put the file online for you, so you'll be able to check for yourself.

Also, many thanks to take the time to explain the EFI case, and moreso - letting me know there's been an update What I still can't stand is the fact I keep having difficulties finding good info on how the efi booters exactly work (too much of a nerd to accept it as it is and using it, I feel I *must* know! haha)

 

In any case, I'll keep you posted on developments.

Greetings and thanks to all!

AiBear

 

ps: anyone notice the new ASUS site? Talk about changing...

[david_osx]

Hi M J!

 

I've finally got marvell yukon 88E8056 to work on leopard check out my post...

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

 

Enjoy guys

[M J]

Hi M J!

 

I've finally got marvell yukon 88E8056 to work on leopard check out my post...

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

 

Enjoy guys

 

empty post anyway, doesn't the new way written in the guide work?

 

JD: what you get in the profiler is normal. what programs where you running? i remember having a similar problem, and then i solved it in some way but i can't recollect exactly what i did and what was the cause...

[AiBear]

Situation update:

- Booted iAtkos 10.5.5 system from USB drive with patched DSDT. System very unstable ('beach ball' hang ups during normal use) - but this could very well be due to the fact it's running from a slow external drive (although iDeneb worked just fine)

- Just managed to boot on Retail install in safe mode, with only one core running. System seems to be stable but somewhat slow; graphics (HD4870) are not working great (slow and choppy graphics in Finder, haven't tried any other programs yet; and no other res than 4x3). The place at which the system often hangs during boot now shows a "Jettisoning Kernel Linker"

>> system just hang on me while typing this (on another computer obiously); reboot leads to Waiting for root device again, although the *exact same* flags have been used. A second reboot keeps hanging again, but the next works again..

>> systems hangs second time around during normal use (trying to patch DSDT again, move it to root and efi partition).

>> I was able to get into the system a few times now, but:

- system is extremely slow, reason unknown as of now

- unable to mount EFI partition ("resource busy")

- graphics card recognized (although at half memory, but the only 4870 available to Macs has 512Megs, so that might be it), but acceleration is far from working, QE not supported

- system hangs after a few minutes of use

 

I'm not sure what's happening. To be entirely honest: I'm at a loss.. I'm not about to give up, but I must say it's quite disheartening that it still refuses to work correctly.

 

On a side note: could a second harddrive disrupt the working process somehow? I remember having trouble using the boot-132 Retail method when my other drive was connected (My win-drive is on s-ata 1, my osx-drive on 3, but when booting to X, I just disable the win-drive in AHCI. It's recognized in Finder, but it doesn't - visibly - cause any problems. But maybe...?)

 

In any case, I will now try to reinstall (again), using MAJ' new script, it might just work.

 

More to follow, as usual

AiBear

[AiBear]

Hey, AiBear,

Let me know what you find out on your system. Hope it's running! If you don't want to bother with the DSDT file comparison, just sent me the script-updated version (that doesn't work) and I'll compare it with a "hand-edited" version. On the other hand, I just hope it wasn't the DSDT file that contributed to your issues. Thanks for your help.

*snip*

regards,

MAJ

*major edit*

Just realized I made a few mistakes checking the files. Redid the thing, and they're the exact same, with exception of the time, of course.

But, here's the weird thing: although the dsdt.dsl files match, the dsdt.asl files are different. As I'm quite bad at reading that code, I can't say if the differences matter in any way, but fact is: they differ (the scripted on is almost 200bytes longer...?). As I can't really find anything in your script, I'm afraid I can't help you any further. By the way: I just looked through the log, it mentions four aliases in the errors, but these are not in the .dsl file..

 

Right, anyway - let me know if I can do anything more (post .aml files, or logs), if you're interested at all. I can imagine this is past tense, as you've got a new script now Which I'll be trying to run as soon as I get my system working... (it won't even boot correctly from a iDeneb 10.5.5 now, from the external disk; if I get the same thing while trying to boot from my main disk, then something in my system is just majorly b0rked.. )

 

Greets,

AiBear

[jaydee48]

empty post anyway, doesn't the new way written in the guide work?

 

JD: what you get in the profiler is normal. what programs where you running? i remember having a similar problem, and then i solved it in some way but i can't recollect exactly what i did and what was the cause...

 

I was using Firefox... but sometimes it happens when i open finder. Doesn't need the profiler to have 4cpu and 8 cores ? i read it somewhere...

[krypto]

Hello guys , Ive been hanging around this topic for the last 2 days , making sure I do it right. After a few failed attempts I got it all to work and thanks MJ and everyone else who have contributed to this thread.

 

Issues that I faced :

1. Kernel panics due to ACPI not being supported : You would run into this if your not following the instructions correctly while booting off the Boot-132 iso . Make sure after you press [F8] and before you insert the Retail Leopard DVD you have to hit ESC and then after you have insterted the Retail DVD wait for 10 seconds and then press enter.

(The above is the exact instructions in MJs first post but am just linking the issues you may run into and what may have caused it.)

 

2. Waiting for Root Devices : You would run into this if either of the below is wrong :

A. You have More than One HDDs (Make sure you disconnect all other HDD physically not just in the BIOS , OSX would still find the HDDs even if you set these to NOT INSTALLED in the BIOS. (You can reconnect the HDDs later , once your done with the install , so dont worry about disconnecting them now.

B. If in this command "rd(0,1)/mach_kernel.voodoo busratio=20 -v -f rd=disk[n]s3" the value of n or 3 is incorrect. Try diffrent numbers as suggested by MJ starting from 0. From retail Leopard its almost always s3.

 

3. Mac OS X cannot install on the HDD error while selecting the partition you want this installed on : This would normally show up while using the Retail Leopard DVD and you have a HDD that has NTFS partitions on it.

In this case make sure you have a dedicated HDD for such an install .

 

4. Repartition it so that it uses a GUID partition table : This is what you have to do on a new/dedicated HDD if you still get the above error saying " Cannot Install repartition in GUID mode" This is done using the diskutil app , select the HDD (not the partitions) right click and say partition , choose the number of partitions you would like and on the laft corner you click on Advanced and select GUID. Then Apply. That should do the trick if you run into " Cannot install on the HDD error asking you to use GUID partition table.

 

MJ a suggestion here :

 

If you could replace the below :

 

F. [setup your EFI partition]:

Tired of using the Boot-132 CD every time you want to start your PC? Just follow this guide. In Phase 4 step 3 use the extensions you find attached to this post in the EFI_pack_V3.zip. Then copy mach_kernel.voodoo, com.apple.Boot.plist and the patched DSDT.aml in /Volumes/EFI as in Phase 4 step 4. Also modify the com.apple.Boot.plist file, setting the right UUID and busratio to the bt(0,0)/mach_kernel.voodoo busratio=20 boot-uuid=UUID line. As the last thing, copy mach_kernel.voodoo to the system root directory as well.

 

with

 

F. [setup your EFI partition]:

Tired of using the Boot-132 CD every time you want to start your PC?

 

1. Follow this GUIDE (Link to Guide)

2. While following the above guide under Phase 4 step 3 , which asks you to copy necessary extensions into /Volumes/EFI/Extensions , copy the Extensions found in EFI_pack_V3.zip in the Extensions folder.

EG :

cd /EFI_pack_V3/Extensions/

cp -R *.kext /Volumes/EFI/Extensions)

3. Modify com.apple.Boot.plist file (available in the attached EFI_pack_V3.zip), setting the right UUID and busratio to the : bt(0,0)/mach_kernel.voodoo busratio=20 boot-uuid=UUID line

EG : bt(0,0)/mach_kernel.voodoo busratio=XX boot-uuid=UUID

Replace XX in the above line to 20 for the Core i7 920 , 22 for the 940 and 24 for the 960.

Replace UUID with the UUID string , to find this follow the below :

A. Open Disk Utility.app and click on the partition containing your fresh install. Click the blue 'I' information icon and look for Universal Unique Identifier. This should be a fairly long hex string.

4. Then copy mach_kernel.voodoo, com.apple.Boot.plist and the patched DSDT.aml in /Volumes/EFI as in Phase 4 step 4.

5. Copy mach_kernel.voodoo to the system root directory as well

6. Test boot! (Once you reboot sucessfully , go to the next step G. [update to 10.5.6]

 

I feel this would help a lot of us follow this guide better with the above tweaks.

 

Looks like quite a few cant get the Network going.

Make sure you fix permissions after you follow MJs guide on getting the LAN fixed.

chown -R root:wheel /System/Library/Extensions

 

MJ I guess you need to add this as well to your Guide, this would help a lotta of folks who just forget to get this done.

 

sudo nano /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleYukon2.kext/Contents/Info.plist



find and change <key>Yukon-88E8053</key> to <key>Yukon-88E8056</key> (change 53 to 56)


find and change <string>0x436211AB</string> to <string>0x436411AB</string></key> (change 62 to 64)


find and change <string>Yukon Gigabit Adapter 88E8053 Singleport Copper SA</string> to <string>Yukon Gigabit Adapter 88E8056 Singleport Copper SA</string> (change 53 to 56)



Press Ctrl+O (that's the letter "o") and [ENTER] to save file, then press Ctrl+X to close nano.



Fix permissions with : chown -R root:wheel /System/Library/Extensions

 

Now... next issue : Try to get my GTX 260 Core 216 working properly ! any one know of where I can get help with this? I do know this GPU isnt supported yet , but there just may be some way !

[krypto]

Alright my search for getting GTX 260 isnt goin any where.... I did find this though http://netkas.org/?p=86

 

Its Supported on Snow Leopard and not on leopard. Darn

 

Does ny one know what kinda luck we ve had using Snow leopard on Hackintoshs?

[jaydee48]

MJ,

 

I removed the wireless lan of my computer (D-Link DWA-547) and i didn't get any crashes yet...

But if it is my wireless lan could it be solved, the card works perfect on vista.

 

No internet so far, because i only got wireless connection at home.

[AiBear]

Finally... It seems like it's working

 

I began entirely cleaning my base, meaning re-flashing BIOS (latest - 1303), removing the battery and clearing CMOS.

After this - nicely following the guide. The system worked well under a fresh 10.5.0, booting quite rapidly - although still on a single core.

Update went smoothly as well, as did the installations of the graphics and audio drivers.

 

The only thing that did *not* work accordingly to the guide, is the network installation. I had to install a kext I had from a previous install package to get ethernet working.

Also, I seem to be unable to use USB or FireWire discs. This is not a 10.5.6 bug, as I couldn't access my USB-stick in 10.5 either, which made installation of packages without access to internet quite annoying (had to burn it to optical discs..). According to System Profiler, FireWire works just fine; and USB clearly works, as I use a USB keyboard and mouse.

 

Benching the system gives nice results, no denying (like: WOW!)

 

Side note: I'm not using SAS, ATA, or my second Ethernet plug, so these have been turned off in the BIOS. I therefor have no clue whether these work with the provided drivers.

 

Also: I encountered one problem, which resulted in a Waiting hang, namely: when filling in the UUID, I automatically ommited the dashes.. Booting up with help of the 132disc allowed me to add the dashes - and the system works fine since.

Still, this does not explain the previous hangs, as booting from boot-132 didn't help anymore either.. And the hangs were not consistent.

 

So, all that's left for me to do is get external drives to work. Anyone have an idea?

Oh, and I presume that by the time 10.5.7 comes, and we work with vanilla kernels, removing the kernel from the Boot.plist will suffice? (and optionally from the EFI as well, although I presume that's not mandatory).

 

edit: tested a few things:

• shutdown gives a kernel panic because of the use of AppleHDA (as predicted)

• wake from sleep gives video garbage, some problems with resolution switches (known bugs for HD48xx cards, although the solutions don't seem to work or even worsen the stability of the system)

• still unable to load USB or FireWire drives, though USB drives are correctly mentioned as connected in the System Profiler

• can't mount EFI partition (resource busy)

But still: most things work, so I'm really thrilled!

I would like to thank all the people who take their precious time to answer the likes of the ones like me; I bow to your knowledge!

 

edit: USB drive recognized when connected at boot; I believe I saw something about this earlier in this thread or the main i7 thread, I'll just look into that

[krypto]

For some of us using a GTX 260 , would it be possible to plug in a 9600 GT or a 9400 GT GPU into the 2nd PCIE slot and use this GPU in OSX?

 

Kinds best of both worlds senario until Snow leopard comes by.

 

Any one knows how to set the 2nd GPU as Primary in OSX?

 

The best part is you can use the 2nd GPU (9600 GT / 9400 GT) in windows as a dedicated PHYSX card.

 

Just an Idea I have no clue to how to implement this? Suggestions are welcome.

[ciparis]

Finally... It seems like it's working

 

Congrats!

 

The main reason I asked about the CMOS clear was because I had previously run into some bizarre instability (in Windows 7) that I finally traced to a corrupted CMOS (diagnosed by clearing it and restoring the same settings ). I had always thought that "load defaults" was equivalent to "clear CMOS then load defaults", but I was wrong: corruption can linger.

 

My final issue was getting Time Machine to work. It always complained that the network interface was not detected. I tried a few things; I think the one that finally fixed it was adding the ethernet controller to the boot.plist using EFIStudio. I found the instructions on this site by searching for the exact error message.

[jaydee48]

MJ,

 

I removed the wireless lan of my computer (D-Link DWA-547) and i didn't get any crashes yet...

But if it is my wireless lan could it be solved, the card works perfect on vista.

 

No internet so far, because i only got wireless connection at home.

 

UPDATE:

 

I got the crash again even if my Wireless PCI card not enabled... this time i was using Logic Studio when i got the panic kernel.

Please is there someone who can help me ? When i Disable the cores and HT it didn't happen

[krypto]

Ok here is what am trying GTX260 in the first PCIE slot and 9500 GT in the 2nd PCIE slot.(Edited NVRESMAN.KEXT and NVDA50.KEXT with the 9500 GT ids and NVCAPS . I now have full graphics support with 9500 GT but I can only boot to OSX if i remove my GTX 260 ..... is there a way of making both work...i mean the GTX 260 could be there sitting and doin nothing....

 

If I delete NVRESMAN.KEXT i can boot with both GPUs but with no full graphics support...... any thing else I could use here?

[clesch]

quick info for the people that are stuck with "still waiting for root device" before installing: make sure your Optical and Hard Drive are plugged into SATA Port 1 & 2 (thats the port-stack closest to the RAM on my P6T-D V2).

 

I got these errors for the longest time because my drives were plugged into 3 & 4.

[digital_dreamer]

Finally... It seems like it's working

So glad it's finally working for you!

 

If you happen to still have the hand-edited dstd and original dstd file, I'd like to check it out. 200 bytes is 200 characters - a lot! (if it's just plain text and not UTF-8). I got a text editor that can compare and highlight the differences. However, if you don't want to fool with it because you got a working system finally, I understand!

 

best regards,

MAJ

[clesch]

Is it normal for the installer to hang ~10 minutes because AppleIntelCPUPowerManagement.kext timed out?

 

As soon as that message disappears I first get the grey screen (while the installer GUI first should load), then the Leopard Background with a Beachball and then the process freezes entirely. Other people had that same issue on page 3 or so, but using their modified iso didn’t help.

I suspect that it might have something to do with the kext mentioned above so I’ll try to make a boot132 that doesn’t load it. (just need to figure out how )

[Mad_noob]

Hey guy's i'm back

 

I've a solution to a problem, i cannot have usb support until i've a usb device plug in at boot time, the solution to this problem is to put a system kext in the EFI Partition, i followed the step to mount this EFI partition but :

 

I do this

 

1) open a terminal

2) sudo -s

* enter your password when prompted

3) mkdir /Volumes/EFI

4) mount_hfs /dev/disk[Y]s1 /Volumes/EFI -> here it tells me "resource busy" and i'm stuck here

 

*Y is the disk number you booting from, could be either 0 or 1, you can find out from disk utility.

*edit the files you need'

 

5) umount /Volumes/EFI

 

Please help

 

Thanks

[sensite]

Anyone tried snow leopard on this? will it be an easy upgrade? or does not work yet?

[Mad_noob]

Hey guy's i'm back

 

I've a solution to a problem, i cannot have usb support until i've a usb device plug in at boot time, the solution to this problem is to put a system kext in the EFI Partition, i followed the step to mount this EFI partition but :

 

I do this

 

1) open a terminal

2) sudo -s

* enter your password when prompted

3) mkdir /Volumes/EFI

4) mount_hfs /dev/disk[Y]s1 /Volumes/EFI -> here it tells me "resource busy" and i'm stuck here

 

*Y is the disk number you booting from, could be either 0 or 1, you can find out from disk utility.

*edit the files you need'

 

5) umount /Volumes/EFI

 

Please help

 

Thanks

 

Ok i manage to mount the EFI partition, the mistake was i wanted to mount the disk 0s1 and the EFI partition was on disk 1s1 because i've a dual boot with Vista...

 

So i manage to put the system kext in the EFI partition too, but my problem is the same, i cannot access a usb device until is it not plug in at boot time, if i don't plug my usb stick before i boot up, the system will not mount it on the desktop but the device manager see it as an usb device...

 

It's weird, everyone help

 

@sensite: I didn't do the update but i guess it will working, do it at your own risk

[david_osx]

Hello M J

 

I've changed my post now.. I hope the guide will help you guys, enjoy.

 

 

Btw there is a better AppleHDA kext by XyZ and it's a legacy kext so giv it a try... Unfortunately the mic is not woriking well but mute dose and more info is shown at the system prefs...

 

http://www.insanelymac.com/forum/index.php...7819&st=220

[clesch]

I’m trying to get all of this installed on a RAID0 array (apple software raid of course, not ich10r/intel matrix raid).

 

Well, the installation actually worked but I’m unable to boot it now with the boot132 disk. 80, 81, 82 - nothing shows a bootable partition so I assume software raid doesn’t work with the boot132 method.

 

Is there an alternative way of getting this to work somehow (chameleon, pc_efi, whatever - i don’t really have a clue what the differences are)?

[Mad_noob]

I'm ok i've got full USB support, now i've to make my 9800GTX fully recognize, cuz OSX only see 256MB of ram instead of 512 and it doesn't recognize the name of the card

[clesch]

I think i fixed the problem with the kernel having to be in the root directory of the root partition. It was quite a big issue for me because the bootloader couldn’t read the root partition at first (due to software raid).

 

the com.apple.Boot.plist from the EFI pack is:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel</key>
<string>mach_kernel.voodoo</string>
<key>Kernel Flags</key>
<string>bt(0,0)/mach_kernel.voodoo busratio=20 boot-uuid=UUID</string>
<key>Quiet Boot</key>
<string>No</string>
</dict>
</plist>

 

but it should be:

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel</key>
<string>bt(0,0)/mach_kernel.voodoo</string>
<key>Kernel Flags</key>
<string>busratio=20 boot-uuid=UUID</string>
<key>Quiet Boot</key>
<string>No</string>
</dict>
</plist>

 

I’m able to boot from the mach_kernel.voodoo on the EFI partition now (with the /mach_kernel.voodoo on the root partition deleted).

Can anyone confirm that this works?