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

So I've just got my brand new i7 machine, with EX58-UD5. I'd pre-prepared a USB hard drive with Leopard 10.5.7 by following DD's instructions. All was fine, and I figured I'd just plug in and be ready to go.

 

However, the problem I'm getting isn't even related to Mac OS! Whenever I have (either of the two) USB hard drives plugged in at boot, it won't get past the line about the processor in the BIOS. USB Legacy Storage is on btw, and I updated the BIOS to the latest f9b to see if that would fix it.

 

Has anyone else had this issue with their board? Struggling to think of a way around it since I don't have a Mac Pro laying about to install it directly to a hard drive.

Link to comment
Share on other sites

I have it working. I use an inexpensive Trendnet GigE adapter which is recognized natively by SL. I use VoodooHDA.kext for sound. My video os Nvidia 9600GT with EFI string installed from DD's script. As well as the DSDT generated using the script.

 

fakesmc.kext

IOAHCIBlockStorageInjector.kext

NullCPUPowerManagement.kext

OpenHaltRestart.kext

PlatformUUID.kext

SleepEnabler.kext

VoodooHDA.kext

 

are my sole non-standard .kext files, all residing in /S/L/E

 

Sound, Video, Sleep, Wake, Network, Time Machine, Bonjour print/scan all working in 64-bit goodness.

 

My biggest hurdle was the day of my life (that I'll never get back) wasted on trying to get the ATI HD 4850 working properly.

 

-bob

 

Hi

 

I have a very similar test instlall, although I have not managed yet to get Networking working.

 

By default, my machine seems to boot in 64 bit modus.

 

Now when i enter -x32 in the bootscreen, this does not have any affect, SL is still booted in 64 bit mode. Hmm, now what?

 

Sorry, this seems like a dummy question but I am stuck here.

 

Mike

Link to comment
Share on other sites

So I've just got my brand new i7 machine, with EX58-UD5. I'd pre-prepared a USB hard drive with Leopard 10.5.7 by following DD's instructions. All was fine, and I figured I'd just plug in and be ready to go.

 

However, the problem I'm getting isn't even related to Mac OS! Whenever I have (either of the two) USB hard drives plugged in at boot, it won't get past the line about the processor in the BIOS. USB Legacy Storage is on btw, and I updated the BIOS to the latest f9b to see if that would fix it.

 

Has anyone else had this issue with their board? Struggling to think of a way around it since I don't have a Mac Pro laying about to install it directly to a hard drive.

I noticed the same thing the other day. Mine gets stuck at the initial boot picture. I am currently on F8 Bios.

 

I know this used to work with earlier BIOSs as I used a Kalyway install on the USB drive to do my original install.

 

Afraid I don't have a fix yet.

Link to comment
Share on other sites

Hi does anyone know why when the Chameleon screen comes up, it quickly says Error Parsing file....

i can still select the 3 different Harddrives that are available.

anyone have ideas how to fix this?

 

From my experience, you might be missing the com.Apple.boot.plist file in /Extra.

Link to comment
Share on other sites

Just wanted to say thanks to DD/MAJ for all the work & support he has given on this.

 

DD's 4.0 RC1 script works great with our UD5 motherboard, the key to everything is having a working VideoCARD!

Here is a simple rundown of steps i took to get everything up.

Load up my disk2 HD with 10.5.7 (or 10.5.6)

Run DD's RC1 script and select Disk1 (which is already formatted)

go thru all the steps and complete SL installation.

I'm using ATI 4870 card, so i copied the EVOenabler.kext to disk1's - s/l/e directory with proper permissions.

Rebooted the machine.

Load up with Disk1 with these flags

-s -x32

then mount your disk by /sbin/mount -uw /

and execute buildcache

for me the buildcache could not mount the EFI partition. said mount_Hfs command failed or incorrect.

i ignored and rebooted the PC.

load up with disk1 with the flag:

-v -x32

after you go thru setting up your login information + keyb setup...quick disable the SPOTLIGHT as instructed by DD.

Now run DD's 4.0 RC1 script again and follow DD's instructions on changing MISC kext to /EXTRA.

I also toggled the AUDIO kext from System to /Extra to get my sound working.

Reboot again.

Load up disk1 with -v -x32 and everything should be working.

 

i was able to boot up with -x64 but i have VMWare fusion and some other apps that did not work.

 

i am VERY VERY new to the process so if i can do it...everyone can! with DD's script and support.

Link to comment
Share on other sites

Hi does anyone know why when the Chameleon screen comes up, it quickly says Error Parsing file....

i can still select the 3 different Harddrives that are available.

anyone have ideas how to fix this?

Sounds like a bad boot plist or smbios plist. I'd check the plists in /Extra to check if it's properly built/tagged.

 

Hi

 

I have a very similar test instlall, although I have not managed yet to get Networking working.

 

By default, my machine seems to boot in 64 bit modus.

 

Now when i enter -x32 in the bootscreen, this does not have any affect, SL is still booted in 64 bit mode. Hmm, now what?

 

Sorry, this seems like a dummy question but I am stuck here.

 

Mike

The 64-bit mode message will appear on all systems, regardless of whether you're booting a 32-bit or 64-bit kernel. But, you're correct, the bootloaders will boot the 64-bit kernel by default, until you send it a -x32 flag.

 

Seems we have a number of different RealtekR1000 kexts around that have been recompiled by various individuals, so it's hard to tell what the networking issue is. Have you lost networking entirely, or just in 64-bit mode?

 

MAJ

Link to comment
Share on other sites

By default, my machine seems to boot in 64 bit modus.

 

Now when i enter -x32 in the bootscreen, this does not have any affect, SL is still booted in 64 bit mode. Hmm, now what?

 

 

Try this. Boot to single user mode and edit com.apple.boot.plist to make sure:

 

<key>Kernel Flags</key>

<string>-x32</string>

 

is in the mix.

 

You can also use this chance to rebuild the cache:

 

kextcache -v 1 -t -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions/ /Extra/Stored_Kexts

 

That should have you booting in 32 bit mode.

Link to comment
Share on other sites

Sounds like a bad boot plist or smbios plist. I'd check the plists in /Extra to check if it's properly built/tagged.

 

 

The 64-bit mode message will appear on all systems, regardless of whether you're booting a 32-bit or 64-bit kernel. But, you're correct, the bootloaders will boot the 64-bit kernel by default, until you send it a -x32 flag.

 

Seems we have a number of different RealtekR1000 kexts around that have been recompiled by various individuals, so it's hard to tell what the networking issue is. Have you lost networking entirely, or just in 64-bit mode?

 

MAJ

 

Hi DD

 

Forgot which of the many kext here is used but I could not get the network in 64bit to work at all.

I have probably tried all the kexts here for Realtek1000 with various configurations (either in Extra or System folder)

Some of the compiled kexts here are so incompatible, that the Networking Hardware is completely frozen in a way that I have to take off my computer from the power source to have a Mainboard without current for a couple of seconds.

After that procedure, I could rewake the networking again. That was really confusing for me. I already suspected a network hardware problem and was ready to replace my Mainboard!!

 

I could reproduce that several times.

If I would reboot into Windows Vista after a Network hang in SL, my networking would still not work, unless I completely shut off my computer as just described above.

 

Some hours ago, I found out that VMware is not working in 64bit mode yet, so I gave up my plans on having a core 64 bit system with SL. VMware is too important for me.

 

Well, I managed to boot into 32bit mode by having kernel args arch=i386 (changed in apple com.apple.boot.plist)

As I said, the -x32 option did not work for me.

 

At least I have now everything working good and stable as it seems.

 

My conclusion for the moment: 64 bit might be nice, but probably too early and experimental, especially since VMware does not support it yet and there might be other applications still with similar problems.

 

@HawgGuy

 

Thanks also for your suggestions. Rebuild kext cache, all seems good now :)

 

Cheers Mike

Link to comment
Share on other sites

DD is awesome!

 

I got my i7 system (Gigabyte UD5 + 4879 2GB video card + etc) up and running 10.5.8 (vanilla) a few weeks ago and bought the Snow Leopard DVD. I'm hesitant to upgrade because the system is stable right now. If I were to upgrade - should I:

 

1) Upgrade the existing OS in place.

2) Do a clean install to a new HD.

 

I hate to think of redo-ing all work to transfer the apps to Snow Leopard. I'd much prefer clone the existing drive to a new drive and an attempt an SL upgrade.

Link to comment
Share on other sites

Finally got some working audio on a GA-EX58-UD3R! And it's pretty good. I had to patch DSDT, and add a few legacy kexts but it works really well.

 

If there's enough demand I'll make a little guide or something.

 

I would be intrested in that right now I am using the voodoohda

Link to comment
Share on other sites

Could someone please take the time to create a noob walkthrough and a kext package to get this working. I have a EX58-DS4, and I used to be really into Mac, but I've gone to Windows 7 for the last few months and I can't figure out any of the new terminology you people are using anymore. I always like to follow guides that are written for COMPLETE noobs. as in, write a guide on how to do it as if I have no clue how to do anything without you telling me how to. Most guides that people write assume that the user knows what he/she is doing. When in reality, if we knew what we were doing, we wouldn't need your guide.

 

So again, can someone write a noob guide on how to install, and post an easy package.

Link to comment
Share on other sites

Could someone please take the time to create a noob walkthrough and a kext package to get this working. I have a EX58-DS4, and I used to be really into Mac, but I've gone to Windows 7 for the last few months and I can't figure out any of the new terminology you people are using anymore. I always like to follow guides that are written for COMPLETE noobs. as in, write a guide on how to do it as if I have no clue how to do anything without you telling me how to. Most guides that people write assume that the user knows what he/she is doing. When in reality, if we knew what we were doing, we wouldn't need your guide.

 

So again, can someone write a noob guide on how to install, and post an easy package.

 

I totally understand where you are coming from because all this terminology, etc. got me confused.

 

Basically to install "vanilla" (no modification) OS X Leopard, you need a working OS X system already (another Mac or another OSX86 distro lika Kalway, iDeneb, iPC, etc. on the same system).

 

Using the working OS X system you now can build a "clean install" that will run OSX86 on a PC - bypassing Apple/OSX things like EFI (PCs use BIOS).

 

1) Install the bootloader onto a portable HD or your final HD. This is required because OSX normally boots off of EFI-based hardware.

 

2) Install the retail/clean OS X 10.5.6 on this portable/final HD then patch it to 10.5.7/10.5.8 (download .dmg file from Apple). It sounds weird, because you can't "install the OS onto a portable HD within the OS" on Windows.

 

3) Add the OSX86 items like kext (drivers/DLLs essentially) into /Extras (which loaded before anything in /System/Library/Extensions) and modify the boot settings.

 

You can now run the OS off this portable HD or final HD. The key part, I didn't fully understand is why you need a working OSX system in the first place. DD provides OSX-based scripts to perform steps 1 to 3 above and it's essential for tweaking purposes. I receommend installing OSX86 onto a laptop (which I did) or an older PC.

Link to comment
Share on other sites

I totally understand where you are coming from because all this terminology, etc. got me confused.

 

Basically to install "vanilla" (no modification) OS X Leopard, you need a working OS X system already (another Mac or another OSX86 distro lika Kalway, iDeneb, iPC, etc. on the same system).

 

Using the working OS X system you now can build a "clean install" that will run OSX86 on a PC - bypassing Apple/OSX things like EFI (PCs use BIOS).

 

1) Install the bootloader onto a portable HD or your final HD. This is required because OSX normally boots off of EFI-based hardware.

 

2) Install the retail/clean OS X 10.5.6 on this portable/final HD then patch it to 10.5.7/10.5.8 (download .dmg file from Apple). It sounds weird, because you can't "install the OS onto a portable HD within the OS" on Windows.

 

3) Add the OSX86 items like kext (drivers/DLLs essentially) into /Extras (which loaded before anything in /System/Library/Extensions) and modify the boot settings.

 

You can now run the OS off this portable HD or final HD. The key part, I didn't fully understand is why you need a working OSX system in the first place. DD provides OSX-based scripts to perform steps 1 to 3 above and it's essential for tweaking purposes. I receommend installing OSX86 onto a laptop (which I did) or an older PC.

I still have my old (10.5.7 i believe) hard drive, with mac still working fine. as well as an older install of 10.5.2 on another hard drive as well. I have a 80GB external USB hard drive thats blank. I'm just looking for a simple way to install Snow Leopard. I was reading a few posts back and the OP said something about needing to disable spotlight. Can you still use spotlight on Snow Leopard? I used to use spotlight for everything. For example, if i needed to use terminal, I'd go to spotlight and type "ter" and click terminal.

 

Last time I used OSX on this desktop, It was extremely hard to install mac onto core i7 systems. It took me a good 2 days to get 10.5.7 running. Before that, you couldn't use anything but 10.5.2

Link to comment
Share on other sites

Hey DD,

 

I'm running a system installed with your 10.5.7 script and it's perfect! For SL, I'm hoping to do an install that boots from a USB stick so I can use a drive that can be booted in a Mac as well as be able to boot a drive from a Mac. Is this something you have planned for your new script?

Link to comment
Share on other sites

Mike,

 

Vmware 2.0.6 wil support 64 bit host, so finding the right kexts now is not a waste of time..

 

 

Well thats good news then.

 

When I read the infos on the VMware site, I just think this might take a little bit longer still.

 

Let's hope for the best.

 

Cheers, Mike

Link to comment
Share on other sites

is it necessary to have 5) SMserial SECRETNUMBER entered in smbios.plist ?

 

 

 

Sounds like a bad boot plist or smbios plist. I'd check the plists in /Extra to check if it's properly built/tagged.

using your script here are the options i have.

 

for SMBIos: i dont have an option to add for my "RetailOS" harddrive (see below)

 

Boot Plists:

Partition Directory

1) For Kext Installer Script

2) leopard Extra

3) retailos System

4) WDC WD5000AAKS-75YGA0 (disk1) EFI

(retailos: disk1s2)

|

SMBIOS Plists

Partition Directory

5) For Kext Installer Script

6) leopard Extra

7) WDC WD5000AAKS-75YGA0 (disk1) EFI

(retailos: disk1s2)

Link to comment
Share on other sites

Hi DD

 

Forgot which of the many kext here is used but I could not get the network in 64bit to work at all.

I have probably tried all the kexts here for Realtek1000 with various configurations (either in Extra or System folder)

Some of the compiled kexts here are so incompatible, that the Networking Hardware is completely frozen in a way that I have to take off my computer from the power source to have a Mainboard without current for a couple of seconds.

After that procedure, I could rewake the networking again. That was really confusing for me. I already suspected a network hardware problem and was ready to replace my Mainboard!!

 

I could reproduce that several times.

If I would reboot into Windows Vista after a Network hang in SL, my networking would still not work, unless I completely shut off my computer as just described above.

 

Some hours ago, I found out that VMware is not working in 64bit mode yet, so I gave up my plans on having a core 64 bit system with SL. VMware is too important for me.

 

Well, I managed to boot into 32bit mode by having kernel args arch=i386 (changed in apple com.apple.boot.plist)

As I said, the -x32 option did not work for me.

 

At least I have now everything working good and stable as it seems.

 

My conclusion for the moment: 64 bit might be nice, but probably too early and experimental, especially since VMware does not support it yet and there might be other applications still with similar problems.

 

@HawgGuy

 

Thanks also for your suggestions. Rebuild kext cache, all seems good now ;)

 

Cheers Mike

 

Same issue with network here!

Tried all the network kexta but without any results!

Link to comment
Share on other sites

Finally got some working audio on a GA-EX58-UD3R! And it's pretty good. I had to patch DSDT, and add a few legacy kexts but it works really well.

 

If there's enough demand I'll make a little guide or something.

 

I would really appreciate a guide for the EX58-UD3R. Especially if you can have snow leopard and GTX 260 support!

 

thanks

Link to comment
Share on other sites

I haven't seen this issue on here. I did the life hacker install on this board, then went through google to hunt down graphics drivers and drivers for the wireless card I bought WL ADPT ENCORE|ENLWI-N. When I rebooted it wouldn't boot, just locked after verifying DMI Pool Data. No big deal I figure.

 

I put my 10.6.0 flash key back in and I get absolutely zero response the exact same way.

 

So I figure, might as well blow away the drive completely. Off to gentoo land I go and kill the partition map and GUID partition.

 

Still nothing.

 

Where can I go from here?

 

-edit-

Just created a raid set up, deleted everything, then set it to not be raid anymore. Completely wiped the disks that way and was able to boot off my usb key. here goes round number two.

Link to comment
Share on other sites

Hi maj,

your box is full, so thought i'd post it herE

 

i booted into Snow leo! so here were the steps i took.

1) Did a clean install with your script

2) deleted ati1000.kext-ati3000.kext (forgot the numbers, but i deleted all of it)

3) opened efi partion thru option 7 in your script.

4) moved all the kext located in Efi/extra/stored_kext over to Sytems/library/extensions. Okay so now i know what E/e stands for and S/L/E. even after i've moved the kexts, E/e folder still has a copy of them and S/L/E has a copy of them. This is probably not the best way, but i got it to boot this way without any know how or reasoning behind it. just plain trial and error.

5) went back to your script and updated the boot cache

6) booted in SL using -x32 command and wala...

7) turned off spotlight using terminal command

8) i think i had to run script and toggle the kexts somewhere, but the instructions weren't very clear so i didn't know how to do it. You mean to say run kext/kernel installer and when the script asks you "Install KExts/kernels, Y/N?" you just type the numbers corresponding to the kexts instead "8 enter, 9 enter, 10 enter"

9) rebooted the first time i got KP

10) went back into my 10.5.8 drive and checked that the snow leo S/L/E had duplicates of all the MISC kexts. Deleted the duplicates and rebooted SL. now i can reboot everytime

 

[b]Issues

1) ati 3870 resolution goes up to onli 2048X1152. in leopard it goes to 2560X1600 (that's what i use)

2) There are no icons visible on desktop. I can't see macintosh HD, or anything i drag to desktop. When i copy a file, the time remaining thing doesn't show. not sure why but a pretty bad problem to have

3) OSX86 tools doesn't work. I can't install kexts with it or repair permissions. it might be my SL install that's causing it. it says there are "no installers/packages available". i might have moved or deleted something i'm not supposed to.

 

Questions

1) I guess i have to learn the proper way to build this bootcache thingy and toggle kexts to it's proper place. you think u can give me some instructions for that? instructions for a retard?

 

2) Need to fix the invisible icons on the desktop. any idea how?

 

3) I looked around the web and found some ppl getting the nvidia 9800Gt to work. Its a 100 dollar card. i read something about efi string and have no idea about that. I 'll research more on it but if you happen to know that this card does work on SL can you provide me a link or a string or something to help me install this card? i can't live with 2048x1152 resolution. ha!

 

4) GTx 285 is just way to expensive but i might go for a 4870. everything works for the 4870? if it is a easy install, can you tell me how to do it?

 

5) now that SL is booting pretty good on my system (god forbid anything happen to it) i noticed that you told some body else to include -x32 in the bootlist so you don't have to type it all the time? can you give me some instructions for that?

 

Things I Plan to do

 

I was wondering if deleting atix2000.kext and so on enables my 3870 to work and actually work pretty good barring the resolution thingy, what if i replaced all the ATI kext in my SL with the ones in my 10.5.8 install and install natit again? maybe u tried that and it didn't work?

 

 

 

 

Regarding upgrading - are you referring to upgrading from 10.5.7 to 10.5.8 (you mentioned upgrading from 10.5.8)? No problems there. There were a few hiccups, but they were in regards to the ATA kexts for the JMicron controller. They had caused KPs on boot. Using a different one now.

 

 

i mean upgrading from 10.5.8 to 10.6. i'm going to do this next to see wether it works since now i know SL CAN work on my mobo and it was just the 3870 messing it up

 

 

 

I've heard that SL doesn't boot on >1 partition drive, but I've never confirmed that myself. I am, however, running SL on a drive by itself, so never experienced any issues there. Might be tempted to make 2 partitions and see if I can install it and see what's up about that. Sounds to be a real limitation, if you ask me.

 

I know SL can run on >1 partition on a REAL mac cos i'm doing it here with my MACPRO. i'm not sure what the issue is but more trial and error on my part will verify this soon and you can probably post it in your new thread sometime about partitions and such. every couple of pages in the forum seems to have some sort of frustration with this .

 

 

I think the install methods are mature, but the implementation may need to be tweaked for best results. The setup I have in the script can be clumsy (limited cache build to get into SL, then full cache build and reboot) and I'm not the only one using this method.

 

good to know! now i have to tweak my systems around these things.

 

hope to hear from you soon,

 

ed

Link to comment
Share on other sites

 Share

×
×
  • Create New...