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

[joeblough]

So here's where I'm stuck now: "There isn't a keyboard connected to your computer. Connect your keyboard now."

 

I'm using a PS2 keyboard, and that is almost certainly the problem. But Kalyway played nice with my keyboard, so I suspect there's going to be a way to get vanilla 10.5.6 to do so also. Anyone know what? Another kext? Use Kext Helper? Thanks as always. ;p

 

you do need some kexts to make the ps/2 keyboard work. look into applePS2controller.kext.

 

Ok guys.

 

I deleted the /Extras/dsdt.aml file. I tried to boot, but it suddenly restarts after I see the mac logo (chameleon still boots though) Also the pc speaker was beeping like crazy. Booting in verbose mode didnt help, because the computer already restarts after 2 seconds. Not enough time to read any on screen info !

 

So right after that I removed the old system.kext in system/library/extensions and replaced it as suggested with the newer 9.7.0 version from the extra folder. I didn't delete the 9.7.0 system kext in the extra folder. I opened disk ultilities and repaired permissions.

 

I just tried to boot again, but no luck ! The system still restarts after just a few seconds.

 

I know it's not the hardware, because I installed Vista 64 bit on another harddisk (I didn't attache this vista disk btw, all the time I was trying to install OSX I left the Vista disk out) and Vista works just as it should.

 

What can I try next ? Could it be I shouldn't remove the Extras/dsdt.aml file ?

 

Do I have to reinstall everything yet again ? Man ! :-(

 

if you ran the installer on a different machine you really can not use the dsdt.aml that was generated from that other machine's bios (unless it was another machine with the same motherboard, but that's not your situation). it definitely won't work.

 

are there any other dsdt.aml files hanging around? like in the root directory of the new boot disk?

[boogusboy]

This seems like an old issue as nobody has mentioned it for several pages now, although I'm still having the fast date/time problem. I'm using Wolfie's EFI script and D_D's latest 9.7.0 kernel and system.kext. Has anyone resolved this with the EFI method? Is anyone out there not having this issue with EFI method? If so, can you tell me what kexts you're using or any additional details? Thanks.

[tgintheworld]

This seems like an old issue as nobody has mentioned it for several pages now, although I'm still having the fast date/time problem. I'm using Wolfie's EFI script and D_D's latest 9.7.0 kernel and system.kext. Has anyone resolved this with the EFI method? Is anyone out there not having this issue with EFI method? If so, can you tell me what kexts you're using or any additional details? Thanks.

 

I'm having this issue still, I'm not sure anyone has actually found a solution for it.

[fuma]

This seems like an old issue as nobody has mentioned it for several pages now, although I'm still having the fast date/time problem. I'm using Wolfie's EFI script and D_D's latest 9.7.0 kernel and system.kext. Has anyone resolved this with the EFI method? Is anyone out there not having this issue with EFI method? If so, can you tell me what kexts you're using or any additional details? Thanks.

 

Well - i can't solve this - but from reading the other posts awhile back, and the amount of people that are using the same setup and install method without this problem, I'd have to say maybe its related to your overclocking settings in the bios.

 

The new architecture of the i7 chip with the integrated memory controller and the push away from FSB means there are a lot of new settings in the BIOS to mess up.

 

I'd start by doing a full BIOS reset, then as you change different settings, make note of any strange behavior and maybe you can narrow it down that way. Its better to unclock your components while you try to overclock the CPU... dont push everything at once... underclock the QPI, the Unicore and the memory by using the multiplier settings while keeping your bclck at a stable setting.

 

Also the guys at tweaktown may be of some help... make sure you are using the latest (non beta) BIOS revision too.. and always load the optimized defaults after a flash.

 

Ok guys.

(edit)

 

Do I have to reinstall everything yet again ? Man ! :-(

 

Welcome to our world! Haha.. thats how we learn!

 

 

I wouldnt be using the 9.7.0 kernel, its not released yet and is from a beta dev build of 10.5.7 (It will change before final release!) and it shouldn't be discussed on this forum or distributed, IMO. The latest isn't always the greatest.

 

 

Go back to 9.6.3 if you're using a core i7 (the stock kernel from a i7 MacPro running 10.5.6)

 

and perhaps resinstall Chameleon.

[boogusboy]

Well - i can't solve this - but from reading the other posts awhile back, and the amount of people that are using the same setup and install method without this problem, I'd have to say maybe its related to your overclocking settings in the bios.

 

The new architecture of the i7 chip with the integrated memory controller and the push away from FSB means there are a lot of new settings in the BIOS to mess up.

 

I'd start by doing a full BIOS reset, then as you change different settings, make note of any strange behavior and maybe you can narrow it down that way. Its better to unclock your components while you try to overclock the CPU... dont push everything at once... underclock the QPI, the Unicore and the memory by using the multiplier settings while keeping your bclck at a stable setting.

 

I'm not overclocking, and I haven't messed with any of those settings in the BIOS. My BIOS settings should be a mirror of DD's in the screens of the first post I believe. The fast clock started when I switched to the Vanilla kernel.

[joeblough]

I'm not overclocking, and I haven't messed with any of those settings in the BIOS. My BIOS settings should be a mirror of DD's in the screens of the first post I believe. The fast clock started when I switched to the Vanilla kernel.

 

this is just a guess, but i think that somehow, when booting from EFI, the bootloader is not successfully passing the flags to the kernel. my understanding is that the voodoo kernel can figure out what the CPU multiplier must be on its own, but the vanilla kernel must be told. i know when i was using EFI, i could never pass in the macmodel string successfully, so i'm guessing that busratio was similarly not taken. assuming that the kernel is just counting CPU clock cycles to determine when 1 second has elapsed, if the busratio is wrong it's going to count too fast (or too slow).

[digital_dreamer]

That's the impression I got from the countless threads discussing the issue. Because the ambiguous message could mean any of a thousand things, the "fix" is almost always to fiddle around with everything until suddenly OSX likes it.

 

And that's how it went with me. In the end, my "fix" was to change the SATA drive mode from "IDE" (which Kalyway liked) to ACHI. This allowed OSX to boot, but I did lose video when it normally would have brought up the gray screen. I suspected this was the fault of my 48x0 driver install, and indeed it was, as a clean install of your script gave me a more fully bootable drive. I do wonder how I'm going to get my 4870 working if the guide only results in a loss of video output.

 

So here's where I'm stuck now: "There isn't a keyboard connected to your computer. Connect your keyboard now."

 

I'm using a PS2 keyboard, and that is almost certainly the problem. But Kalyway played nice with my keyboard, so I suspect there's going to be a way to get vanilla 10.5.6 to do so also. Anyone know what? Another kext? Use Kext Helper? Thanks as always. ;p

 

PS: Before somebody suggests getting a USB keyboard.. not really an option. I hit a financial ceiling with the hardware I've got, and besides, I have yet to see a USB keyboard with the fat return key, the backslash beneath it, a normal insert/home/etc. area, a small spacebar, and a small backspace. They all seem to want to prove they're modern by altering the traditional keyboard layout.

Try these files for the PS/2 Keyboard and Mouse. There are several files, depending on the type of keyboard and mouse hookup - mouse plugged into keyboard, keyboard plugged into mouse, etc. There are some instructions included, but don't ask me anything about them because I'm just the messenger and have never used them.

 

Ok guys.

 

I deleted the /Extras/dsdt.aml file. I tried to boot, but it suddenly restarts after I see the mac logo (chameleon still boots though) Also the pc speaker was beeping like crazy. Booting in verbose mode didnt help, because the computer already restarts after 2 seconds. Not enough time to read any on screen info !

 

So right after that I removed the old system.kext in system/library/extensions and replaced it as suggested with the newer 9.7.0 version from the extra folder. I didn't delete the 9.7.0 system kext in the extra folder. I opened disk ultilities and repaired permissions.

 

I just tried to boot again, but no luck ! The system still restarts after just a few seconds.

 

I know it's not the hardware, because I installed Vista 64 bit on another harddisk (I didn't attache this vista disk btw, all the time I was trying to install OSX I left the Vista disk out) and Vista works just as it should.

 

What can I try next ? Could it be I shouldn't remove the Extras/dsdt.aml file ?

 

Do I have to reinstall everything yet again ? Man ! :-(

Can you type into Terminal the following and post your system log? (if it's long, you can just post a txt file.)

open /Volumes/YOUR_BOOT_DRIVE/private/var/log/system.log

That is, if you haven't erased it already and started over.

 

This seems like an old issue as nobody has mentioned it for several pages now, although I'm still having the fast date/time problem. I'm using Wolfie's EFI script and D_D's latest 9.7.0 kernel and system.kext. Has anyone resolved this with the EFI method? Is anyone out there not having this issue with EFI method? If so, can you tell me what kexts you're using or any additional details? Thanks.

 

I'm having this issue still, I'm not sure anyone has actually found a solution for it.

 

 

I'm not overclocking, and I haven't messed with any of those settings in the BIOS. My BIOS settings should be a mirror of DD's in the screens of the first post I believe. The fast clock started when I switched to the Vanilla kernel.

Can you guys with the clock issue post what mobo and BIOS version you're using? And, what install method you're using? EFI boot or boot-132.

Additionally, are you guys using a dsdt.aml file created on your mobo or one at all?

 

regards,

MAJ

[Asterra]

Success, part 1. Thank you, Digital Dreamer, for your time and effort in writing the script. I hope the various hurdles I encountered along the way (complete with the solutions I researched or stumbled upon) will help some other Google user in the future. And for the record, the package I used to enable PS/2 keyboard support after performing the Digital Dreamer vanilla install was: PS2FixKeyboard.

 

And now I undertake to finalize the process, including multiple cores, hyperthreading, Audigy 2 ZS, and the now-dreaded 4870 driver. With history as my guide, I fully expect to come crawling back for more help. ;p

 

Update: A second attempt to install the 48x0 driver (Motmot) has given the same result upon rebooting: A black, sleep-like screen, at approximately the point where it would have gone to the gray screen. Necessitates a reinstall each time.

[tgintheworld]

Can you guys with the clock issue post what mobo and BIOS version you're using? And, what install method you're using? EFI boot or boot-132.

Additionally, are you guys using a dsdt.aml file created on your mobo or one at all?

 

MAJ,

 

I'm running 9.7.0 on one install, 9.6.3 on another, and they both have fast clocks.

I have the GA-EX58-UD5 board with BIOS F6.

 

Both installs are using Wolfienuke's script (EFI Partition boot). I installed both installs on this same machine with the same motherboard, and I assume wolfie's script creates a dsdt.aml file.

[cyonix]

@ digital dreamer

 

I have the UD4P board and two 8600 GT. I cant run both cards at one time with efi strings.. i tried the nvinject 0.2.0 dual cards kext but then i havent QE/CI.

I read the thread about running two and three cards, but if i put only one card in 2nd pcie i get the same pci infos like if i do this in the 1st one pcie. I also set the initial card to PEG2.

have you an idea how can i fix it? the cards are 100% the same.

[Asterra]

I don't suppose anyone here who used Digital Dreamer's script has managed to get a 4870 fully working? I've followed the 48x0 guide in the ATI forum. Four times. It seems obvious to me that the results that guide produces are not compatible with Digital Dreamer's installation.

 

If it matters, I'm not using multiple monitors. My setup is 4870 -> DVI -> VGA -> monitor. Right now, the only graphics mode I can choose is 1280x1024x32x60, and QE/IC are not working.

[sock]

No messages other than "process completed?" With the Terminal window still open, can you scroll up the history and see any error messages?

Is your Mac partition formated as HFS? Looking at the script again, it is expected that at least one drive be Apple HFS. I'll need to add some checks for that portion, so that it responds gracefully.

 

Post the results of diskutil list from the Terminal. That will help us.

 

As for the 128GB limit, where do you have the IDE drive plugged in (Is this your 1TB drive)? Do you have SATA Port0-3 Native Mode enabled for your SATA drive?

 

regards,

MAJ

 

 

Thanks for the quick reply, I'll check the details tonight both the kalyway disk and the blank disk are HFS+ (both ATA) the 1TB drive is SATA (4 partitions, 99.9 GB NTFS, 100MB system reserved for windows, 100GB unformatted & the rest is NTFS storage space).

[boogusboy]

Can you guys with the clock issue post what mobo and BIOS version you're using? And, what install method you're using? EFI boot or boot-132.

Additionally, are you guys using a dsdt.aml file created on your mobo or one at all?

 

regards,

MAJ

 

I have the GA-EX58-UD3R mb and bios F5 on Wofie's EFI latest script. There is a dsdt.aml file in W's script but I dont know if it's being used. If it is, I've never run the script on anything other than my hardware. I guess I'll have to mount the partition to be sure, I can do that if you'd like.

[Hakintos]

LOL! You got it!

So, does that mean you got the system running, or that you got the script running? :

 

I did not know that the password could not see for security.

Running the script. I am waiting for a second SATA disk to install, and comment as you go.

 

regards,

Hakintos

[adhir]

FWIW - I also have the fast clock problem on my P6T (non deluxe) w the 920 chip. This is with the 9.7.0 9j56 kernel and associated System.kext. I've tried with and without various levels of overclocking with no change.

 

I also get these messages repeatedly in the system.log:

 

Apr 29 16:13:28 dante kernel[0]: WARNING: AppleUSBAudio has detected that clock_get_uptime () value changed radically from previous values

 

My suspicion is that that's related to the clock timing being off.

 

I have tried booting with a correct value of fsb= in the kernel flags. I've also verified that the machines is correctly detecting the proper value by looking at the output of "sysctl hw.busfrequency" - take what you get from that and divide by 4,000,000 (4 million), and you'll get what you have your BCLK set to in your BIOS.

 

Let me know if you get anywhere with this.

[sdstever]

Got 10.5.6 working with Wolfienuke's latest script. Had to reinstall to fix some hard drive formatting and sound issues, and now also it sleeps and wakes from sleep just fine. But this time, I lost all networking.

 

No firewire or ethernet devices recognized. I've tried a couple different IOnetworkingfamily kexts, substituting in MAJ's kext as well. I'm not sure what else to do. Which kexts are affecting the OS's ability to recognize the networking devices? How can I get some internet up in here?

 

Also, NVinject got my GeForce 9800 GT looking great at full resolution, but my toolbars are still not translucent. Any ideas on how I can get that working all the way?

 

Thanks for all your help so far; you guys are great!

[bernito]

I don't suppose anyone here who used Digital Dreamer's script has managed to get a 4870 fully working? I've followed the 48x0 guide in the ATI forum. Four times. It seems obvious to me that the results that guide produces are not compatible with Digital Dreamer's installation.

 

If it matters, I'm not using multiple monitors. My setup is 4870 -> DVI -> VGA -> monitor. Right now, the only graphics mode I can choose is 1280x1024x32x60, and QE/IC are not working.

 

I have the HD4870 working with both DD's retail method and Wolfienuke's boot from EFI method. All I needed was to run the 48x0 drivers and use the latest Netkas Natit kext. I get full 1080p (1920 x 1080) and both QE and IC. I am not running QE in my main Wolfie setup however, because it causes issues with Microsoft Entourage 2008. For some reason Entourage crawls when opened if you have QE enable and also slows every other application down dramatically, but there are zero problems if you leave QE off.

[joeblough]

FWIW - I also have the fast clock problem on my P6T (non deluxe) w the 920 chip. This is with the 9.7.0 9j56 kernel and associated System.kext. I've tried with and without various levels of overclocking with no change.

 

what boot method are you using? i have not seen this problem with the original D_D script or the new one using /Extra. i've only seen it when using the EFI partition install (wolfienuke)

[neils]

Can you type into Terminal the following and post your system log? (if it's long, you can just post a txt file.)

CODE

open /Volumes/YOUR_BOOT_DRIVE/private/var/log/system.log

 

I named the partition I installed 10.5.6 on MACOSX

 

I opened terminal and typed

open /Volumes/MACOSX/private/var/log/system.log

 

I get this error message. The file /Volumes/MACOSX/private/var/log/system.log does not exist.

 

??? DD ?

[bernito]

I was able to boot with Wolfienuke's EFI-Partition script and the new 9.7.0 kernel and System.kext, but I needed some additional kexts to get it to work. I will post a step-by-step of what I did to get it to work later tonight, including all the kexts I used. I got netflix to work too, which I was happy about.

 

My question now is: which is the superior method for install with regards to maintaining an install that works right and updates easily? DD's new script or the EFI Parition method? Or is it the case that DD's new script utilizes the EFI Partition and stores the modded kexts there in case an update blows away needed kexts on the system drive?

 

tgintheworld - can you post all the kexts as I do not want to brick my otherwise good install? Thanks!

[Asterra]

I have the HD4870 working with both DD's retail method and Wolfienuke's boot from EFI method. All I needed was to run the 48x0 drivers and use the latest Netkas Natit kext.

Is there any chance I could get a somewhat more detailed outline of what steps you took with which files? I'll explain my points of confusion:

 

1) The guide says to grab 7_radeon_hd_48x0_drivers.pkg and run it. Afterwards, it instructs to grab ATY_Motmot.kext and install that with Kext Helper. Is this (Motmot) the latest Netkas Natit kext?

 

2) A natit kext seems to have been installed a-la Digital Dreamer's scripted OSX installation. Does one need to do something with this preexisting natit kext?

 

3) The guide says to replace the OpenGL.framework in the case of the 4870. Skip this? Or, if you don't skip this, is it important to do this step before the first reboot? (The Guide's chronology isn't 100% clear on this point.)

 

4) How is your 4870 connected to your monitor(s)? The Guide's thread has a lot of evidence suggesting that this actually makes a difference, despite how baffling that may sound.

 

I'm just trying to narrow things down. You say you got it working, but unless Motmot is not the same thing as the latest Netkas Natit kext, I've already undertaken those steps five different times with the same failure each time, necessitating a full reinstall.

[digital_dreamer]

I have the GA-EX58-UD3R mb and bios F5 on Wofie's EFI latest script. There is a dsdt.aml file in W's script but I dont know if it's being used. If it is, I've never run the script on anything other than my hardware. I guess I'll have to mount the partition to be sure, I can do that if you'd like.

I'm pretty sure that file is on there, so no need to confirm. I know wolfienuke's script checks for the presence of that file and, if missing, places a patched version there.

The clock issue appears to be only on the EFI boot systems and it might be a issue with the older bootloader. It's the Munky-Turbo bootloader and is described as not Chameleon, so I guess that means version 8.0 at the latest.

 

Got 10.5.6 working with Wolfienuke's latest script. Had to reinstall to fix some hard drive formatting and sound issues, and now also it sleeps and wakes from sleep just fine. But this time, I lost all networking.

 

No firewire or ethernet devices recognized. I've tried a couple different IOnetworkingfamily kexts, substituting in MAJ's kext as well. I'm not sure what else to do. Which kexts are affecting the OS's ability to recognize the networking devices? How can I get some internet up in here?

 

Also, NVinject got my GeForce 9800 GT looking great at full resolution, but my toolbars are still not translucent. Any ideas on how I can get that working all the way?

 

Thanks for all your help so far; you guys are great!

You probably got the infamous dead LAN, I got that twice this week as I was testing BIOS settings. You'll need to shut off system and unplug for 10 seconds or so. Or, you can clear the CMOS. If you do the CMOS clear, make sure you saved your BIOS settings, so you can reloaded them.

 

what boot method are you using? i have not seen this problem with the original D_D script or the new one using /Extra. i've only seen it when using the EFI partition install (wolfienuke)

What I was thinking. I'm inclined to think it's the older bootloader.

 

I named the partition I installed 10.5.6 on MACOSX

 

I opened terminal and typed

open /Volumes/MACOSX/private/var/log/system.log

 

I get this error message. The file /Volumes/MACOSX/private/var/log/system.log does not exist.

 

??? DD ?

Well, if it's missing it means that it never got built or got erased. Did you already reinstall? If so, and if the system hasn't been booted, yet, then no log has been built.

No biggie, just trying to get some clues regarding what's going on.

 

MAJ

[neils]

I didn't reinstall yet. This is the actual partion I tried to boot with yesterday.

 

What should I try now ? I mean, why should I reinstall again with setting I know from dont work ?

 

What is your advice ? Should I try to install a distro on my i7 and install the retail install from there ? Would that make a difference ?

[tgintheworld]

tgintheworld - can you post all the kexts as I do not want to brick my otherwise good install? Thanks!

 

@bernito yes sorry I didn't get the chance the other night, I'll let you know how I did it when I get home from work

 

Edit: Here's my list of kexts that I used for the EFI 9.7.0 install. I recommend against using 9.7.0 with wolfie's EFI Partition script until the fast clock issue is sorted out, but regardless, the kexts that worked are mainly the same ones that DD posted in his script package:

 

efi_970_kexts.tiff

 

That's obviously the 9.7.0 System.kext. Other than that, I think that's the exact set of kexts DD uses (minus a video driver). Hope that helps.

[mangopeach]

on both my ipc distro drive and my Dreamer driver (retail 9.7 + extra) I can't make a software raid in diskutility. Anyone else not able to make a RAID in diskutility? Could it be a bios setting... I have it set to AHCI and I'm using only the intel sata ports. I tried softraid but it seems a tad buggy too... any ideas out there?

 

 

---btw---

I have full video working at 1920x1200 on two monitors. Framerate seems great. evga 9800gtx+ using graphics string from aquamac.