Jump to content

[GUIDE] Retail OS X Install (10.5.8) on Gigabyte GA-EX58-UD5 (Core i7) Mobo


digital_dreamer
 Share

3,054 posts in this topic

Recommended Posts

Anyone with the EVGA X58 mobo got sleep working. I have mine set to S3 and when I attempt to sleep, everything does shut down I hit the space bar and the pc starts to come out of sleep but no display nothing working, no HD activity.

Link to comment
Share on other sites

Just insert the following text into your com.apple.boot.plist that resides in your /Extra folder.

 

<key>device-properties</key>
<string>6e0200000100000001000000620200000d00000002010c00d041030a010000000101060000090
01060000007fff04000e0000004e00560050004d0000002000000001000000000000000000000000
00000000000000000000000000000220000005600520041004d002c0074006f00740061006c00730
69007a006500000008000000000000141c0000006400650076006900630065005f00740079007000
50000000f0000004e5644412c506172656e740e0000006e0061006d00650000000b0000006469737
6c617922000000400030002c006400650076006900630065005f00740079007000650000000b0000
0646973706c617922000000400031002c006400650076006900630065005f0074007900700065000
000b000000646973706c6179100000006d006f00640065006c0000001b0000006e56696469612047
5466f72636520383830302047545320000000400031002c0063006f006d007000610074006900620
6c00650000000e0000004e5644412c4e564d616314000000400030002c006e0061006d0065000000
20000004e5644412c446973706c61792d4114000000400031002c006e0061006d006500000012000
004e5644412c446973706c61792d4220000000400030002c0063006f006d00700061007400690062
06c00650000000e0000004e5644412c4e564d6163100000004e00560043004100500000001800000
04000000000003000c00000000000007000000001e00000072006f006d002d007200650076006900
30069006f006e0000002f0000006e5669646961204765466f726365203838303020475453204f706
6e474c20456e67696e65205b4546495d</string>

 

Save, chmod/chown. Reboot. Sorry to be so brief but I'm late for dinner. Gotta run.

 

EDIT: I'm back and I think I replied to the wrong post. The above answer is for neils and his 8800 GTS 320mb.

 

 

I just did a fresh retail install again. Everything is working great (Chameleon 2.0 rc1, updated to 10.5.7, vanilla kernel) except for my videocard. I placed the string above in my boot.plist and repaired permissions. My videocard however still runs in VESA mode. I also downloaded EFI-studio, but EFI studio can't install the string to my extra folder, so I guess I really have to do this manually.

 

Can somebody please help me to get my card up and running ? On my last install I used nvinstaller. That one worked, but I prefer using the ef-string method.

 

I tried to install a string by using DD's script. I think I did something wrong there, cause the script didn't insert anything. I also copy/pasted the string above. Same story, doesn't work.

 

How should I install this ? (I have searched for topics about how to install efi-strings, but most people refer to efi-studio. Efi-studio however is unable to install to my extra folder.

 

Is NVinstaller ok to use ? Would it make any difference perfomance wise to use that instead of an efi-string ?

Link to comment
Share on other sites

I just did a fresh retail install again. Everything is working great (Chameleon 2.0 rc1, updated to 10.5.7, vanilla kernel) except for my videocard. I placed the string above in my boot.plist and repaired permissions. My videocard however still runs in VESA mode. I also downloaded EFI-studio, but EFI studio can't install the string to my extra folder, so I guess I really have to do this manually.

 

Can somebody please help me to get my card up and running ? On my last install I used nvinstaller. That one worked, but I prefer using the ef-string method.

 

I tried to install a string by using DD's script. I think I did something wrong there, cause the script didn't insert anything. I also copy/pasted the string above. Same story, doesn't work.

 

How should I install this ? (I have searched for topics about how to install efi-strings, but most people refer to efi-studio. Efi-studio however is unable to install to my extra folder.

 

Is NVinstaller ok to use ? Would it make any difference perfomance wise to use that instead of an efi-string ?

For those long strings, you'll have to insert them manually via text editor. The script will only permit text inputs up to 1022 characters. That's a limitation of bash, nothing I can do about that.

 

EFI-studio allows you to copy to clipboard, so that you can copy to the "device-properties" string in a boot plist.

An EFI string will always be faster than an injector. Additionally, using the EFI string will allow the system to have this information much sooner in the boot process, rather than later. This can resolve issues with other processes that need this information earlier than an injector can provide it.

 

MAJ

Link to comment
Share on other sites

I did add them manually twice already, repaired permissions, but it doesn't work.

 

I repaired permissions using this commands:

 

chmod -R 755 /Volumes/Osx/Extra/

chown -R root:wheel /Volumes/Osx/Extra

 

(I have installed my retail copy on the Osx volume.

 

This is what my boot.plist in the extra folder looks like:

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>Boot Graphics</key>

<string>Yes</string>

<key>deviceproperties<key>

<string>6e0200000100000001000000620200000d00000002010c00d041030a010000000101060000090

1060000007fff04000e0000004e00560050004d00000020000000010000000000000000000000000

000000000000000000000000000220000005600520041004d002c0074006f00740061006c0073069

07a006500000008000000000000141c0000006400650076006900630065005f00740079007000500

0000f0000004e5644412c506172656e740e0000006e0061006d00650000000b00000064697376c61

922000000400030002c006400650076006900630065005f00740079007000650000000b000006469

3706c617922000000400031002c006400650076006900630065005f0074007900700065000000b00

000646973706c6179100000006d006f00640065006c0000001b0000006e566964696120475466f72

36520383830302047545320000000400031002c0063006f006d0070006100740069006206c006500

0000e0000004e5644412c4e564d616314000000400030002c006e0061006d006500000020000004e

644412c446973706c61792d4114000000400031002c006e0061006d006500000012000004e564441

c446973706c61792d4220000000400030002c0063006f006d0070006100740069006206c00650000

00e0000004e5644412c4e564d6163100000004e00560043004100500000001800000040000000000

3000c00000000000007000000001e00000072006f006d002d00720065007600690030069006f006e

000002f0000006e5669646961204765466f726365203838303020475453204f7066e474c20456e67

96e65205b4546495d</string>

 

<key>Kernel</key>

<string>mach_kernel</string>

<key>Kernel Flags</key>

<string>boot-uuid=E3131436-30BC-3E3A-9FA3-44337BCFA3D5</string>

<key>Timeout</key>

<string>5</string>

<key>device-properties</key>

</dict>

</plist>

 

 

It doesn't work however.

Link to comment
Share on other sites

I did add them manually twice already, repaired permissions, but it doesn't work.

 

I repaired permissions using this commands:

 

chmod -R 755 /Volumes/Osx/Extra/

chown -R root:wheel /Volumes/Osx/Extra

 

(I have installed my retail copy on the Osx volume.

 

This is what my boot.plist in the extra folder looks like:

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>Boot Graphics</key>

<string>Yes</string>

<key>deviceproperties<key>

<string>6e0200000100000001000000620200000d00000002010c00d041030a010000000101060000090

1060000007fff04000e0000004e00560050004d00000020000000010000000000000000000000000

000000000000000000000000000220000005600520041004d002c0074006f00740061006c0073069

07a006500000008000000000000141c0000006400650076006900630065005f00740079007000500

0000f0000004e5644412c506172656e740e0000006e0061006d00650000000b00000064697376c61

922000000400030002c006400650076006900630065005f00740079007000650000000b000006469

3706c617922000000400031002c006400650076006900630065005f0074007900700065000000b00

000646973706c6179100000006d006f00640065006c0000001b0000006e566964696120475466f72

36520383830302047545320000000400031002c0063006f006d0070006100740069006206c006500

0000e0000004e5644412c4e564d616314000000400030002c006e0061006d006500000020000004e

644412c446973706c61792d4114000000400031002c006e0061006d006500000012000004e564441

c446973706c61792d4220000000400030002c0063006f006d0070006100740069006206c00650000

00e0000004e5644412c4e564d6163100000004e00560043004100500000001800000040000000000

3000c00000000000007000000001e00000072006f006d002d00720065007600690030069006f006e

000002f0000006e5669646961204765466f726365203838303020475453204f7066e474c20456e67

96e65205b4546495d</string>

 

<key>Kernel</key>

<string>mach_kernel</string>

<key>Kernel Flags</key>

<string>boot-uuid=E3131436-30BC-3E3A-9FA3-44337BCFA3D5</string>

<key>Timeout</key>

<string>5</string>

<key>device-properties</key>

</dict>

</plist>

It doesn't work however.

 

 

Neils. Your data and tags are wrong. It should be

 

<key>device-properties</key>

 

You're missing the dash and a slash.

Link to comment
Share on other sites

Use this niels

 

 

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "[url="http://www.apple.com/DTDs/PropertyList-1.0.dtd"]http://www.apple.com/DTDs/PropertyList-1.0.dtd[/url]">
<plist version="1.0">
<dict>
<key>Boot Graphics</key>
<string>Yes</string>
       <key>device-properties<key>
<string>6e0200000100000001000000620200000d00000002010c00d041030a010000000101060000090
1060000007fff04000e0000004e00560050004d00000020000000010000000000000000000000000
000000000000000000000000000220000005600520041004d002c0074006f00740061006c0073069
07a006500000008000000000000141c0000006400650076006900630065005f00740079007000500
0000f0000004e5644412c506172656e740e0000006e0061006d00650000000b00000064697376c61
922000000400030002c006400650076006900630065005f00740079007000650000000b000006469
3706c617922000000400031002c006400650076006900630065005f0074007900700065000000b00
000646973706c6179100000006d006f00640065006c0000001b0000006e566964696120475466f72
36520383830302047545320000000400031002c0063006f006d0070006100740069006206c006500
0000e0000004e5644412c4e564d616314000000400030002c006e0061006d006500000020000004e
644412c446973706c61792d4114000000400031002c006e0061006d006500000012000004e564441
c446973706c61792d4220000000400030002c0063006f006d0070006100740069006206c00650000
00e0000004e5644412c4e564d6163100000004e00560043004100500000001800000040000000000
3000c00000000000007000000001e00000072006f006d002d00720065007600690030069006f006e
000002f0000006e5669646961204765466f726365203838303020475453204f7066e474c20456e67
96e65205b4546495d</string>

<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>boot-uuid=E3131436-30BC-3E3A-9FA3-44337BCFA3D5</string>
<key>Timeout</key>
<string>5</string>
</dict>
</plist>

Link to comment
Share on other sites

Anyone with the EVGA X58 mobo got sleep working. I have mine set to S3 and when I attempt to sleep, everything does shut down I hit the space bar and the pc starts to come out of sleep but no display nothing working, no HD activity.

 

i had a lot of problems with resume from S3 sleep on the X58-UD4P. only the most recent beta bios (F9a) has been solid on wake. everything before F8a was pretty flaky when trying to wake up, and even F8a would not wake if the system was overclocked at all. F9a is okay with my BCLK=166Mhz/3GHz overclock.

 

i have a friend with an asus X58 mobo and he had the same problems (windows xp) with wake from S3 until he installed the very latest bios.

 

it seems likely that all the board/bios vendors are all still fixing bugs. so you might try updating to the latest bios. i dont know if there's the equivalent of tweaktown for evga, but gigabyte releases their beta bioses there...

Link to comment
Share on other sites

Use this niels

 

 

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "[url="http://www.apple.com/DTDs/PropertyList-1.0.dtd"]http://www.apple.com/DTDs/PropertyList-1.0.dtd[/url]">
<plist version="1.0">
<dict>
<key>Boot Graphics</key>
<string>Yes</string>
<key>device-properties<key>
<string>6e0200000100000001000000620200000d00000002010c00d041030a010000000101060000090
1060000007fff04000e0000004e00560050004d00000020000000010000000000000000000000000
000000000000000000000000000220000005600520041004d002c0074006f00740061006c0073069
07a006500000008000000000000141c0000006400650076006900630065005f00740079007000500
0000f0000004e5644412c506172656e740e0000006e0061006d00650000000b00000064697376c61
922000000400030002c006400650076006900630065005f00740079007000650000000b000006469
3706c617922000000400031002c006400650076006900630065005f0074007900700065000000b00
000646973706c6179100000006d006f00640065006c0000001b0000006e566964696120475466f72
36520383830302047545320000000400031002c0063006f006d0070006100740069006206c006500
0000e0000004e5644412c4e564d616314000000400030002c006e0061006d006500000020000004e
644412c446973706c61792d4114000000400031002c006e0061006d006500000012000004e564441
c446973706c61792d4220000000400030002c0063006f006d0070006100740069006206c00650000
00e0000004e5644412c4e564d6163100000004e00560043004100500000001800000040000000000
3000c00000000000007000000001e00000072006f006d002d00720065007600690030069006f006e
000002f0000006e5669646961204765466f726365203838303020475453204f7066e474c20456e67
96e65205b4546495d</string>

<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>boot-uuid=E3131436-30BC-3E3A-9FA3-44337BCFA3D5</string>
<key>Timeout</key>
<string>5</string>
</dict>
</plist>

 

Thanks for your help :( It still doesn't work though :( . I'm not even sure if this is the proper string. How can I use the hex from DD's script ? It's a different one than the one posted for me.

 

I repaired permissions using this commands:

 

chmod -R 755 /Volumes/Osx/Extra/

chown -R root:wheel /Volumes/Osx/Extra

Link to comment
Share on other sites

So I'm trying to fix the fact that I can't get hardware info under System Profiler.

 

There have been hints that the 10.5.7 update is being tailored to one's Mac, and that this may be the cause of the problems I've been seeing. Although I have changed my smbios.plist to reflect that I have a "MacPro 3.1" with ram type 24, I did this after the 10.5.7 update, and my guess is that it's too late at that point.

 

So I've done a clean install to 10.5.6 and I want to change the smbios.plist before the update. The problem? I can't locate smbios.plist! Before, after the update to 10.5.7, I found it in the /Extra folder. (Incidentally, this may or may not have been the correct smbios.plist.) Well, it's not there. I can't find it anywhere.

 

I just need to change "MacPro 4.1" to "MacPro 3.1" and ram type 19 to 24, wherever these settings happen to be. Maybe I need to somehow do this before I even install 10.5.6? I wouldn't know where to look for these settings in the script either.

 

Anyone have a guess?

Link to comment
Share on other sites

Thanks for your help :( It still doesn't work though :( . I'm not even sure if this is the proper string. How can I use the hex from DD's script ? It's a different one than the one posted for me.

 

I repaired permissions using this commands:

 

chmod -R 755 /Volumes/Osx/Extra/

chown -R root:wheel /Volumes/Osx/Extra

 

Please make sure it says <key>device-properties</key> exactly. The example that was posted by mac kid from jersey was missing the slash.

 

Please try that. Now if by chance that doesn't work. Please download OSx86Tools and install it on the computer that has the graphics card that you are trying to fix. This will not work otherwise.

 

These instructions are from memory so they might not be perfect.

 

1) Run OSx86Tools

 

2) Select Add EFI string

 

3) Select Custom Nvidia...

 

4) Enter the Name of Your card

 

5) Select the amount of memory the card has

 

6) Select the kind of ports the card has

 

7) OSx86Tools will generate a string for your card. Select the string with your mouse and hit command-C to copy to clipboard.

 

8) carefully paste this string into your com.apple.boot.plist that is in your /Extra folder with the appropriate tags from my example boot.plist.

 

That's how I did it for my 9600 GSO. This should work for you.

Link to comment
Share on other sites

Hi,

Total Newbie. I'm trying to do the retail DVD install using DD method. After I run RUN-PATCH_INSTALLER.command and reboot, I get the following error during bootup:

 

Boot0: GPT

Boot0: Testing

Boot0: Testing

Boot0: Error

 

Then the system just hangs. This happens right after the system restarts and the BIOS posts. It looks like the kernel doesn't execute. Am I missing something? I read thru the posts and it looks like no one else is having this problem.

 

Any help is greatly appreciated!!

Link to comment
Share on other sites

Thanks .. its warm (of course) and OK for benching :( .. need to get a case too.

 

Got to the other machine (non X58) and created a fresh drive using Script 3.5 / RC1 / 10.5.6 DVD retail... running up the drive CPU=4 ... dsdt had only 4 lines for the CPU... no Alias comments.

 

 

   Scope (_PR)
  {
   Processor (CPU0, 0x00, 0x00000410, 0x06) {}
   Processor (CPU1, 0x01, 0x00000410, 0x06) {}
   Processor (CPU2, 0x02, 0x00000410, 0x06) {}
   Processor (CPU3, 0x03, 0x00000410, 0x06) {}
}

 

Again adding in the additional lines for CPU 4-7 did not open up the extra HT CPUs...

 

Finally adding the parameter "_PR." to each CPU line allowed all CPUs to open up....

 

	Scope (_PR)
{
	Processor (_PR.CPU0, 0x00, 0x00000410, 0x06) {}
	Processor (_PR.CPU1, 0x01, 0x00000410, 0x06) {}
	Processor (_PR.CPU2, 0x02, 0x00000410, 0x06) {}
	Processor (_PR.CPU3, 0x03, 0x00000410, 0x06) {}
	Processor (_PR.CPU4, 0x04, 0x00000410, 0x06) {}
	Processor (_PR.CPU5, 0x05, 0x00000410, 0x06) {}
	Processor (_PR.CPU6, 0x06, 0x00000410, 0x06) {}
	Processor (_PR.CPU7, 0x07, 0x00000410, 0x06) {}
}

 

I do not understand this and may be there is something you can see but at least I know what to do for this machine... now to get to move up to 10.5.7

 

 

thxs

 

Man, you're up to 4.2Ghz on that system!!
Link to comment
Share on other sites

I have KP after waking up from sleep and then shutdown!

I already changed the MacPro4,1 identifier to MacPro3,1.

I have NO System.kext, NO Applesmbios.kext and NO "LegacyAppleAHCIPort.kext" in /extra.

I am using vanilla 9.7.0 Kernel from 10.5.7 .

And I already have the new F7d Bios.

 

 

Does someone have a solution/ any ideas for this?

Link to comment
Share on other sites

Does someone have a solution/ any ideas for this?

 

Hello Masterlen,

 

I used to have the same problem...

 

Solutions:

 

1/ Disable sleep

 

or

 

2/ Go back to 9,6 Kernel with all related kext (LegacyAppleAHCIPort.kext, AppleSMBIOS.kext in "Extra-Stored_Kexts") using DD script...and System.kext in "S/L/E" putted with OSX86Tools or KextHelper.

 

 

That's what I've done, basicaly. And no more KP.

 

Let us know.

 

ps: my bios is F5

Link to comment
Share on other sites

hey guys, does sleep work in 10.5.7 for anyone?

it goes to sleep but when i press the power button the PC everything loads but screen still in powersaving mode.

what settings am i missing in the bios? or wrong ktexT?

Link to comment
Share on other sites

Hi,

Total Newbie. I'm trying to do the retail DVD install using DD method. After I run RUN-PATCH_INSTALLER.command and reboot, I get the following error during bootup:

 

Boot0: GPT

Boot0: Testing

Boot0: Testing

Boot0: Error

 

Then the system just hangs. This happens right after the system restarts and the BIOS posts. It looks like the kernel doesn't execute. Am I missing something? I read thru the posts and it looks like no one else is having this problem.

 

Any help is greatly appreciated!!

Your BIOS is not set to look at the right drive. This will happen if it's looking at a flash drive, for example, that doesn't have a bootable OS installed.

 

MAJ

Link to comment
Share on other sites

I've tried different versions of Digital Dreamer's script. I've tried 10.5.6 and 10.5.7. Everything is working fine, except sometimes I get Kernel Panics. I use to get one when I try to install MS Office 2008. Anyone has experienced it? Any solution?

 

Ok, I answer myself. The problem was LegacyJMicronATASATAIDE.kext. Without that kext Leopard works perfect.

 

I think its the same Jmicron problem explained earlier. Is LegacyJMicronATASATAIDE.kext only for 32 bits? Is there other kext I could use to see my IDE Hds?

 

 

Thank everybody, specially DD for his wonderful job!

Link to comment
Share on other sites

hey guys, does sleep work in 10.5.7 for anyone?

it goes to sleep but when i press the power button the PC everything loads but screen still in powersaving mode.

what settings am i missing in the bios? or wrong ktexT?

I got the same issue. Sleep "works", but doesn't wake. Monitor doesn't wake and there's no evidence the system is awake, either.

Looking at the logs, there's no evidence it actually went to sleep - no "System sleep" or "System wake", just a gap in activity.

 

Hopefully, there may be an update to OpenHaltRestart.kext or some other solution soon.

 

MAJ

Link to comment
Share on other sites

So I'm trying to fix the fact that I can't get hardware info under System Profiler.

 

The problem is an incompatible Plugin for System-Profiler which shows you the extensions of your cpu. Delete in folder /System/Library/SystemProfiler/ the file SPiPlatformReporter.spreporter.

 

After that Sytem-Profiler works but doesn't show cpu extensions like:

FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM SSE3 MON DSCPL VMX EST TM2 SSSE3 CX16 TPR PDCM

 

Regards

Link to comment
Share on other sites

I got the same issue. Sleep "works", but doesn't wake. Monitor doesn't wake and there's no evidence the system is awake, either.

Looking at the logs, there's no evidence it actually went to sleep - no "System sleep" or "System wake", just a gap in activity.

 

Hopefully, there may be an update to OpenHaltRestart.kext or some other solution soon.

 

MAJ

 

Hey guys. As far as I can tell my sleep/wake is working with 10.5.7. It's S3 for sure because both lights go out on the front of my case. Take a look at my sig and let me know if you need any additional info to troubleshoot.

 

On a side note. I fixed my UUID error #35 by putting UUID.kext in the /Extra folder.

Link to comment
Share on other sites

Hey guys. As far as I can tell my sleep/wake is working with 10.5.7. It's S3 for sure because both lights go out on the front of my case. Take a look at my sig and let me know if you need any additional info to troubleshoot.

 

On a side note. I fixed my UUID error #35 by putting UUID.kext in the /Extra folder.

 

Hey,

 

Mine was "kind of" working sometimes. KP only occur few minutes (1 or 2) after, but not correctly.

 

You say you'e on 10.5.7, but wich Kernel version ? Have you run the script after updating ? If so, did you remove the kernel from the folder "to install" to "repository" ? Any other Kext ?

 

regards

Link to comment
Share on other sites

 Share

×
×
  • Create New...