[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos

[borissatan]

The plist you are concerned with is the one in /Extra. Using DDs script the plist in his plist folder is loaded when you first load the bootloader (option 1). After the initial bootloader install, if you reload a bootloader, his script will ask if you want to change the plists by default if you hit return at this point it will not overwrite the existing /Extra plist. You also have the option here to overwrite the plist if desired.

You can also modify the plist in /Extra from DDs script, there is a specific option to do so.

 

With arch=i386 as a boot flag, SL will boot into 32 bit mode - remove that flag and it will boot into 64 bit mode.

 

To straighten out the booting process be sure the OSX install that has the boot loader is set in BIOS as the first HD to boot.

 

XP will install in AHCI mode - I've done it. When you are ready to install XP, unplug the drive with Mac (if possible have only the target XP drive connected). Once XP is installed, reconnect the Mac drive (set to boot first). When you boot the computer the chameleon bootloader screen will appear, during the 'countdown' hit the space bar and you will presented with a choice of bootable drives. If you want XP use the arrow keys to highlight its icon and then hit return. You will boot into XP.

 

Much appreciating all this help guys!

 

Ok so I'm booting in 64 bit mode cos I removed the two arch=i386 bits from the two plists disk0s1 and disk0s2.

 

My boot disk is plugged to SATA_0 and is first option in BIOS (I tried the other way around with the empty disk first and I don't get to bootloader).

 

The specific error I get trying to boot off the boot disk with the empty disk present is "Could not load mach kernel", but that's clearly cos it's looking on the wrong drive.

 

So I'm guessing the bootloader is looking in the wrong place.

 

How can I reinstall the bootloader on my bootdisk without destroying everything?

 

Infact, if I wanted to change to a different bootloader how would I go about it?

 

I tried this before and caused an EFI apocalypse...

[septicdeath]

does the address etc of your PCI Firewire card match that in your DSDT?

 

Could you cut and paste your DSDT entry for Firewire here?

 

I'm very much a n00b when it comes to the DSDT and editing it. First, I should let you know that I went back and rebooted from the install that was locking up on the firewire error message, and it just booted fine the 2nd time. The message still gets spit out, I also was able to notice that the card is actually two devices, the firewire 400 had a GUID that looked to make sense, but the FW800 side is the one thats a flood of 000000000000000.

 

I also have another disk in the system that has 10.6.2 installed from using the kakewalk installer, which I am under the impression doesn't give the error messages, I used DSDT-SE to compare the DDST from the kakewalk install against the install from the script attached to this thread, and there were no differences. I don't have and FRWR entries in either of the DDST's.

 

Always, I decided to connect the ext firewire drive that will be connected to this system, (had not up to this point) and low and behold, it was recognized and mounted in finder. About this Mac shows both the 400 and the 800 bus, and the Ext drive connected to the 800 port. Im starting to wonder if the error messages are because the gigabyte has a fw 400 on board and my pci board has a fw400 as well as the 800.

 

anyways, I can't produce the entries from the ddst because I don't think they exist and Im a total N00b with the ddst work, will spend some time looking over the other tutorials, as it doesn't make much sense to be stuck relying on others for their DDST's even if I got lucky and did get one that was the correct one for my system.

 

 

here is the lspci -nn output with reference to IEEE 1394 on my box.

 

I believe this is from the 4 port pci-e x4 card:

01:00.0 PCI bridge [0604]: Texas Instruments Unknown device [104c:823e] (rev 01)

02:00.0 FireWire (IEEE 1394) [0c00]: Texas Instruments Unknown device [104c:823f] (rev 01)

 

and Im guessing the onboard gigabyte port

0a:06.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) [104c:8024]

 

off to go search out some ddst tutorials, any recommendations for a starting thread?

[LocusOfControl]

I'm very much a n00b when it comes to the DSDT and editing it. First, I should let you know that I went back and rebooted from the install that was locking up on the firewire error message, and it just booted fine the 2nd time. The message still gets spit out, I also was able to notice that the card is actually two devices, the firewire 400 had a GUID that looked to make sense, but the FW800 side is the one thats a flood of 000000000000000.

 

I also have another disk in the system that has 10.6.2 installed from using the kakewalk installer, which I am under the impression doesn't give the error messages, I used DSDT-SE to compare the DDST from the kakewalk install against the install from the script attached to this thread, and there were no differences. I don't have and FRWR entries in either of the DDST's.

 

Always, I decided to connect the ext firewire drive that will be connected to this system, (had not up to this point) and low and behold, it was recognized and mounted in finder. About this Mac shows both the 400 and the 800 bus, and the Ext drive connected to the 800 port. Im starting to wonder if the error messages are because the gigabyte has a fw 400 on board and my pci board has a fw400 as well as the 800.

 

anyways, I can't produce the entries from the ddst because I don't think they exist and Im a total N00b with the ddst work, will spend some time looking over the other tutorials, as it doesn't make much sense to be stuck relying on others for their DDST's even if I got lucky and did get one that was the correct one for my system.

 

 

here is the lspci -nn output with reference to IEEE 1394 on my box.

 

I believe this is from the 4 port pci-e x4 card:

01:00.0 PCI bridge [0604]: Texas Instruments Unknown device [104c:823e] (rev 01)

02:00.0 FireWire (IEEE 1394) [0c00]: Texas Instruments Unknown device [104c:823f] (rev 01)

 

and Im guessing the onboard gigabyte port

0a:06.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) [104c:8024]

 

off to go search out some ddst tutorials, any recommendations for a starting thread?

 

OK, I only use firewire for a Nikon scanner and it worked out of the box without any fiddling, but it did show

some warnings in the kernel error log. There is a DSDT 'fix' that eliminates these errors but as far as I'm

concerned it's only cosmetic as everything worked without it - mind you putting it in and getting it wrong

does mess things up!

[iLLNESS]

Here is a link to an USB boot image for EX58A-UD7 very similar to your mobo!

http://www.kexts.com/view/216-gigabyte_ga-...%28v1.2%29.html

 

There are some kext working for your MOBO so pick theme up for de Extra folder !

Good luck

[everdone]

Much appreciating all this help guys!

 

Ok so I'm booting in 64 bit mode cos I removed the two arch=i386 bits from the two plists disk0s1 and disk0s2.

 

My boot disk is plugged to SATA_0 and is first option in BIOS (I tried the other way around with the empty disk first and I don't get to bootloader).

 

The specific error I get trying to boot off the boot disk with the empty disk present is "Could not load mach kernel", but that's clearly cos it's looking on the wrong drive.

 

So I'm guessing the bootloader is looking in the wrong place.

 

How can I reinstall the bootloader on my bootdisk without destroying everything?

 

Infact, if I wanted to change to a different bootloader how would I go about it?

 

I tried this before and caused an EFI apocalypse...

 

From your statements I assume you used EFI for the bootloader rather than Extra. I decided on using Extra because every time I tried the EFI method strange things happened. I much prefer Extra. In any event, to change bootloaders rerun DDs script and once you have selected the drive you want to use and you get to the options list, select Option 1 Bootloaders. this brings up the list of available bootloaders and allows you to choose the one you want.

 

You can also change kexts by changing the kexts in the various kext folders, rerunning the script and select the kext install option.

 

If you want to change from EFI to Extra then you need to erase the EFI partition and rerun DDs script and select Extra as the bootloader install location. This option occurs right after you select the disk to install on.

[borissatan]

From your statements I assume you used EFI for the bootloader rather than Extra. I decided on using Extra because every time I tried the EFI method strange things happened. I much prefer Extra. In any event, to change bootloaders rerun DDs script and once you have selected the drive you want to use and you get to the options list, select Option 1 Bootloaders. this brings up the list of available bootloaders and allows you to choose the one you want.

 

You can also change kexts by changing the kexts in the various kext folders, rerunning the script and select the kext install option.

 

If you want to change from EFI to Extra then you need to erase the EFI partition and rerun DDs script and select Extra as the bootloader install location. This option occurs right after you select the disk to install on.

 

Cool yeah I get that bit. What I meant (and I didn't explain very well again) was how would I install a different bootloader altogether, as opposed to one in the DD script? eg Empire EFI or something? I'm just curious really as I'm planning to stick with the DD EFI bootloader for now.

 

I'll try reinstalling the one I'm using and see if that untangles it

 

M

 

... some time later ...

 

If in doubt reinstall the bootloader

 

I'd still like to know how to install a different one though.

 

I'm also wondering what will happen when I install ubuntu.

 

Oh if only I could get my bloody sound card to work, I could ditch windows for ever...

[pookeye]

Alright, I have a question....

 

maybe I did this wrong.. (I am running 64 bit btw, I have a UD5 gigabyte board, with a geforce 6600 GT..)

 

 

1.) I installed 10.6 with a boot CD and used DD's script to install the kext and add my graphics card in.. so it worked perfectly.

 

2.) I then went and upgrade to 10.6.2..

 

sooo once i did that, i got a kernel panic, but lucky for me i had a nice lenovo S10 hackintosh with 10.6.1 and i was able to take out the Geforce Kext and run snow leopard on safe mode, and basically installed geforce 10.6.1 kext back into the 10.6.2 install.. and rebooted the machine.. and it worked perfect..

 

but i noticed something... problems i noticed..

 

1.) Voodoo Kext would not load..

2.) Shut down doesn't shut down...

3.) Restart doesnt restart

 

 

so i was wondering if anyone can tell me which kext would help me..

 

I'm guessing the restart and shut down is probably cause i need that EVO reboot thing...

 

but what about the voodoo kext? why doesnt it run? and do i need to re do the DSDT after 10.6.2 install?

 

 

thanks

 

-Pookeye

[septicdeath]

I checked my logs through console, and both installs (kakewalk and this threads method) have the same error messages in them. Seems a line gets hit every couple of minutes or so, I'll see what I can do to get it recognized, but I agree, at this point its just cosmetic, albeit, TONS of log entries taking place.

 

 

 

OK, I only use firewire for a Nikon scanner and it worked out of the box without any fiddling, but it did show

some warnings in the kernel error log. There is a DSDT 'fix' that eliminates these errors but as far as I'm

concerned it's only cosmetic as everything worked without it - mind you putting it in and getting it wrong

does mess things up!

[CruiSAr]

Alright, I have a question....

 

1.) Voodoo Kext would not load..

2.) Shut down doesn't shut down...

3.) Restart doesnt restart

 

 

so i was wondering if anyone can tell me which kext would help me..

 

I'm guessing the restart and shut down is probably cause i need that EVO reboot thing...

 

but what about the voodoo kext? why doesnt it run? and do i need to re do the DSDT after 10.6.2 install?

 

 

thanks

 

-Pookeye

Wyy are you using a kext for your graphics card? I will recommend you use Efi strings instead or automatic string injection by using the latest chameleon bootloader or PCEfi bootloader.

 

Add GraphicsEnabler to your com.apple.boot.plist and set the string to Yes.

 

VoodooHda will not load if you have HDAEnabler in your S/L/E folder. I will also recommend you to read this GUIDE as it will help you to get rid of third party kexts and tun your machine close to real MAC.

 

Hope this helps

[fruitbat04]

Can anyone give me a bit of help with getting sleep going on the EX58-UD3R?

 

I'm tried various combinations of S1/3 in BIOS and allowing/disallowing wakeup on PCI event but to no avail.

 

I'm not sure if it's the same problem as other people get, but for me, it looks like it's going to work - The drives and fans spin down and the screen goes black as it all should. However after that, it imediately spins back up again.

 

Thanks

[LocusOfControl]

Can anyone give me a bit of help with getting sleep going on the EX58-UD3R?

 

I'm tried various combinations of S1/3 in BIOS and allowing/disallowing wakeup on PCI event but to no avail.

 

I'm not sure if it's the same problem as other people get, but for me, it looks like it's going to work - The drives and fans spin down and the screen goes black as it all should. However after that, it imediately spins back up again.

 

Thanks

 

You need to provide a lot more information eg all your hardware, kexts, configuration, are you using native power

management, system preference settings, DSDT etc

 

all these factors and more can affect sleep, unfortunately there isn't a one off magic bios tweak

 

do you use bluetooth, wake on ethernet etc ?

[fruitbat04]

No worries, sorry I should have included a lot more detail.

 

I'm running the UD3R with latest BIOS

i7 920

6GB RAM

GTX 275

 

I'm using a Revo 5.1 sound card with the internal sound disabled

 

Other hardware is a BT USB dongle and an mbox 2, a Axiom Pro 49 Midi controller and a Numark DJ midi controller (However I've tried with all those things unplugged incase it was a problem with them).

 

I'm using the DD script as per page 1 of this tutorial.

 

Using 32bit rather than 64 bit kernel as this is a requirement of Pro Tools

 

Attached is a screengrab of the kexts in my Extra. I have tried using own DSDT and also the patched one in this post http://www.insanelymac.com/forum/index.php...97&st=2000# which is the same mobo as mine.

 

Thanks

[pookeye]

Wyy are you using a kext for your graphics card? I will recommend you use Efi strings instead or automatic string injection by using the latest chameleon bootloader or PCEfi bootloader.

 

Add GraphicsEnabler to your com.apple.boot.plist and set the string to Yes.

 

VoodooHda will not load if you have HDAEnabler in your S/L/E folder. I will also recommend you to read this GUIDE as it will help you to get rid of third party kexts and tun your machine close to real MAC.

 

Hope this helps

 

Hi CruiSar, thanks for responding, actually i am using the EFI strings, its just that i have an older geforce card and 10.6.2 drivers screwed up old geforce cards.. so i had to use the 10.6.1 kexts to make it work.. kernel panics if i didnt... so the graphics is working perfectly... with 10.6.1 kexts. :-)

 

i finally got the sound to work, i got rid of all the other kexts and just used the voodoo kexts, and also used 64 bit voodoo kexts so thats working great..

 

 

now about the restart and power down kext... does anyone know which ones i should use? EvoReboot?

 

anything else? I'm almost perfect :-P

 

-pookeye

[LocusOfControl]

No worries, sorry I should have included a lot more detail.

 

I'm running the UD3R with latest BIOS

i7 920

6GB RAM

GTX 275

 

I'm using a Revo 5.1 sound card with the internal sound disabled

 

Other hardware is a BT USB dongle and an mbox 2, a Axiom Pro 49 Midi controller and a Numark DJ midi controller (However I've tried with all those things unplugged incase it was a problem with them).

 

I'm using the DD script as per page 1 of this tutorial.

 

Using 32bit rather than 64 bit kernel as this is a requirement of Pro Tools

 

Attached is a screengrab of the kexts in my Extra. I have tried using own DSDT and also the patched one in this post http://www.insanelymac.com/forum/index.php...97&st=2000# which is the same mobo as mine.

 

Thanks

 

Since you aren't running NullCPUPowerManagement.kext and some kind of DSDT (couldn't see which) I assume

you are running native power management

 

Do you see something like

 

Feb 19 09:25:52 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready

Feb 19 09:25:52 localhost kernel[0]: AppleIntelCPUPowerManagement: Turbo Ratios 1112

Feb 19 09:25:52 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete

 

in kernel log?

 

If so things should be simpler.

 

If that is the case try sleep with all extra hardware off or wake enabling off

eg

ethernet cards have wake on lan, this can stop sleep as can wake using bluetooth e.g using magic mouse with

exactly same symptoms, if you turn off wake using BT, sleep is fine

 

disable all your sharing options in system prefs, these can stop sleep

 

and also in energy saver, make sure your settings are similar to these. Hitting restore defaults twice before helps

as does deleting /Library/Preferences/SystemConfiguration/com.apple.PowerManagement.plist and rebooting

 

My own feeling is that sleep in 64 bit is reliable, although I don't use 32 bit anymore I had a couple of issues

once in a while so I feel it is less reliable - could be me though

 

 

you should be able to see what is causing the wake by looking in system.log

[ryansimms]

Using 32bit rather than 64 bit kernel as this is a requirement of Pro Tools

 

Thanks

 

I've been using Pro Tools in 64 bit for a while now with no problems on a EX58-UD3R, rev 1.0, BIOS F8. I have much less kexts in /Extra though. I'm down to fakesmc, OSXRestart, IONetworkingFamily, and AppleHDA (with the last two in S/L/E). The rest of the fixes were done using d00d's DSDT editing guide. What revision of the MoBo do you have, 1.0, 1.6, or 1.7?

 

Ryan!

[fruitbat04]

Thanks LoC. I will try that when I'm back home. Thinking about it, I have both printer,iTunes and screen sharing turned on so it could be something to do with that.

 

ryansimms - Pro Tools 8 will start in 64 bit, but the mbox 2 won't power up (I assume there is no driver?) and my version validates the license against the MBbox 2.

 

I'm on the 1.6 rev btw.

[CruiSAr]

Hi CruiSar, thanks for responding, actually i am using the EFI strings, its just that i have an older geforce card and 10.6.2 drivers screwed up old geforce cards.. so i had to use the 10.6.1 kexts to make it work.. kernel panics if i didnt... so the graphics is working perfectly... with 10.6.1 kexts. :-)

 

i finally got the sound to work, i got rid of all the other kexts and just used the voodoo kexts, and also used 64 bit voodoo kexts so thats working great..

 

 

now about the restart and power down kext... does anyone know which ones i should use? EvoReboot?

 

anything else? I'm almost perfect :-P

 

-pookeye

Evoreboot or openhaltrestart will do

[pookeye]

Evoreboot or openhaltrestart will do

 

 

whats the difference? anyways, i added EvoReboot and it works great!

 

now i am trying to get clonezilla to clone this drive and the EFI drive so i dont have to keep doing this!

 

but thanks SO MUCH!!! it seems to be working almost perfectly now!

[Obiwantje]

Wyy are you using a kext for your graphics card? I will recommend you use Efi strings instead or automatic string injection by using the latest chameleon bootloader or PCEfi bootloader.

 

Add GraphicsEnabler to your com.apple.boot.plist and set the string to Yes.

 

VoodooHda will not load if you have HDAEnabler in your S/L/E folder. I will also recommend you to read this GUIDE as it will help you to get rid of third party kexts and tun your machine close to real MAC.

 

Hope this helps

 

@CruiSAr I notice in your signature you say you only use FakeSMC, is there any way you could update your guide to reflect your current setup - I have applied most of the suggested DSDT patches, but can't seem to get as close to "real" as you do - I would be really interested to see what yours looks like!

 

Thanks!

[callumj09]

@CruiSAr I notice in your signature you say you only use FakeSMC, is there any way you could update your guide to reflect your current setup - I have applied most of the suggested DSDT patches, but can't seem to get as close to "real" as you do - I would be really interested to see what yours looks like!

 

Thanks!

It depends mostly on your hardware and how close it is to Apple's. With boards like the UD5 working audio can be achieved with no additional kexts, whereas on my board I do.

 

I'm currently using 2 kexts in my E/E dir; fakesmc.kext and legacyhda.kext, then in S/L/E realtekr1000sl.kext. However, I do know with a later revision of my board that kext isn't necessary. Again, it can be very specific.

 

You can cut down the requirements for OS X to run properly by using the correct combination of things. DSDT being the main one - I have patches for the following:

 

• Audio (ALC888)
  
• Shutdown
  
• Orange icon fix
  
• Correct power management (from d00d's thread)
  

I'm also using Asere's bootloader which allows the removal of platformuuid.kext and restart kexts.

 

PS. if anyone with the EX58-UD3R (rev 1.0) would like some help achieving the same as I have I am more than happy to help. I put a lot of time into it so far...

[CruiSAr]

@CruiSAr I notice in your signature you say you only use FakeSMC, is there any way you could update your guide to reflect your current setup - I have applied most of the suggested DSDT patches, but can't seem to get as close to "real" as you do - I would be really interested to see what yours looks like!

 

Thanks!

Obi, I have two setups as you can see in my signature. The raid uses my current guide. I use this one because it boots faster than my other setup and I have all my stuff on it.

 

The one with the extensively patched DSDT is for testing purposes only, I got it working with Steve's help but if it will prove useful to you and anyone else, I will update the guide with it. Note that I am not using any third party sound kexts in this setup, just the original AppleHDA. I am using the SPDIF on our board and it works in surround mode as well but I will elaborate on this when I update the guide.

 

It will take sometime before i update the guide but it should be ready before wednesday . I am on a weekend holiday at the moment so my Hack is asleep at home

[dark4181]

I know this is a Gigabyte thread, but since there isn't an EVGA thread that I can find...

 

Anyone had success in running SL on an EVGA Classified e760 with a w3520 cpu, an xfx 5870 gpu and an OCZ vertex 120gb as system drive? If so, pm me a link to the proper place, as I get no results when I try to search the forums.

[atlee]

I know this is a Gigabyte thread, but since there isn't an EVGA thread that I can find...

 

Anyone had success in running SL on an EVGA Classified e760 with a w3520 cpu, an xfx 5870 gpu and an OCZ vertex 120gb as system drive? If so, pm me a link to the proper place, as I get no results when I try to search the forums.

 

look at all the chipsets of your board and not the brand like eVGA, does not tell us anything, do a search on the forum.

[macbank]

This is an awesome script. Installed without issues. I did need to install nvidia kexts to get my 9800GT working, but everything else works perfectly.

 

There is one question I have. When the computer is booting up, it displays all the text as when you choose verbose mode. It does not display the apple logo on the grey screen.

 

I saw that there is an option to select a boot picture in the script, but when I select it, nothing happens. After I select option 14 and press enter, the screen flashes for a second and then puts me right back at the script menu.

 

Any ideas? I tried doing a search within this topic, but no results come back. I also paged through the start of this thread, but didn't see anything related to this.

 

Thanks

[callumj09]

Is there a way of preventing my other HDD from mounting when I start up?

 

Because it's not in use it goes to sleep, then when you use something like Spotlight or you go to save something the computer lags because it's waking up the HDD. I don't just want to turn off "Put the hard disk(s) to sleep when possible", because I still want that. I just want it to be one drive recognised through OS X.

 

Is there a way to do that?

 

Thanks!