[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos

[Denis Davydov]

My guide isnt about dsdt patching, it is about using the patched DSDT so you can eliminate some kexts. Yes you can just replace the DSDT you have now, install the recommended bootLoader and remove the necessary kexts, the DSDT works from Bios f9 to f12.

 

Hi,

 

I moved all kext's except for fakesmc from Stored_Kexts/_For_System to Stored_Kexts, replaced original dsdt.aml with your version and then run Update boot caches.

But I guess I still have all these kext's running at the beginning (at least I see JMicronAta during start).

 

Could you advise what have I done wrong?

Thanx.

 

Denis.

[digital_dreamer]

Hi,

 

I moved all kext's except for fakesmc from Stored_Kexts/_For_System to Stored_Kexts, replaced original dsdt.aml with your version and then run Update boot caches.

But I guess I still have all these kext's running at the beginning (at least I see JMicronAta during start).

 

Could you advise what have I done wrong?

Thanx.

 

Denis.

You should remove all the kexts from Stored_Kexts.

Update boot caches creates a boot cache in /Extra from kexts in Stored_Kexts. The kexts in _For_System get installed into S/L/E.

 

This is the first time I've heard this misunderstanding of what these folders are for and what they do. But, I understand the confusion, now. Some probably feel the Stored_Kexts are just a repository, but not so. They are actually used to build the boot cache in /Extra.

 

I wonder if the Stored_Kexts folder should be renamed to _For_Extra to lesson the confusion.

 

MAJ

[Windows04]

You should remove all the kexts from Stored_Kexts.

Update boot caches creates a boot cache in /Extra from kexts in Stored_Kexts. The kexts in _For_System get installed into S/L/E.

 

This is the first time I've heard this misunderstanding of what these folders are for and what they do. But, I understand the confusion, now. Some probably feel the Stored_Kexts are just a repository, but not so. They are actually used to build the boot cache in /Extra.

 

I wonder if the Stored_Kexts folder should be renamed to _For_Extra to lesson the confusion.

 

MAJ

 

Or maybe it's better if you rename it to _For_Bootcache or something

[CruiSAr]

I wonder if the Stored_Kexts folder should be renamed to _For_Extra to lesson the confusion.

 

MAJ

Lol yeah as simple as it is, it is not easily understandable to some. Probably renamaing it should help a bit, maybe _For_BootCache_Extra?

 

Hi,

 

I moved all kext's except for fakesmc from Stored_Kexts/_For_System to Stored_Kexts, replaced original dsdt.aml with your version and then run Update boot caches.

But I guess I still have all these kext's running at the beginning (at least I see JMicronAta during start).

 

Could you advise what have I done wrong?

Thanx.

 

Denis.

Like DD said, kext in the stored_kexts folder are used in building the bootCache. Remove all of them and leave only fakeSMC and then update bootCaches using the script. See attached screen dump.

[Denis Davydov]

Thank you DD and CruiSAr for quick answers,

now it did remove all .kexts and I really thought that "stored-kexts" is a kind of repository.

 

Like DD said, kext in the stored_kexts folder are used in building the bootCache. Remove all of them and leave only fakeSMC and then update bootCaches using the script. See attached screen dump.

 

the thing is my audio does not work in this setup (no input/output device)

So I have to use two kexts from DD's setup (HDAEnabler and LegacyHDA).

 

The only problem is I can't make mic-In/line-In work.

I recall, somebody mentioned this problem here as well.

Has anyone succeeded ?

 

I had the audio and ethernet kexts installed in /Extra. I moved them to S/L/E without a change. After that I went for the Crusair method, using his DSDT - Realtek in S/L/E and just fakesmc in /Extra. Everything worked, except audio. After that I tried adding HDAEnabler and LegacyHDA back into /Extra - still nothing.

 

I'm sure I'll get this, just have to fiddle around some more.

 

HDAENabler should be in "_For_System" folder whereas LegacyHDA in "StoredKexts",

i had same problems with audio in CruiSAr method and that made it work.

[pcace]

Did u remember to go into system settings under power management and check start up automatically after a power failure? If you dont do this, the system will reboot instead of waking up from sleep. I noted this in the guide.

 

Hey, thank you!

Right Now im only using fakeSMC in the /extra folder, BUT i still can not use sleep, and there is no ethernet shown.

Any Idea?

 

What informtion do you need to help?

 

Thanks,

 

Pcace

[Sidewinder33]

Hey, thank you!

Right Now im only using fakeSMC in the /extra folder, BUT i still can not use sleep, and there is no ethernet shown.

Any Idea?

 

What informtion do you need to help?

 

Thanks,

 

Pcace

 

I believe you still need the realtek kext to get your ethernet up and running. What issues are you having with sleep? won't auto sleep after a certain time of inactivity or wont sleep period, even when you tell it to sleep?

[crankygonzo]

I just wanted to say thanks to everyone on InsanelyMac, and especially to DD and Cruisair and everyone else that has helped me along the way. I finally have a fully working Hackintosh. Buying a new graphics card was the key to my last remaining problems. This hobby is so rewarding! Now time to try and hone the craft so I can try and be the go to guy.

[pcace]

I believe you still need the realtek kext to get your ethernet up and running. What issues are you having with sleep? won't auto sleep after a certain time of inactivity or wont sleep period, even when you tell it to sleep?

 

Hey,

 

the issue is that it simply doesn't sleep. The screens turn black, but fans continue rotating. After forcing shutdown then (because its not waking up...) i looked into the console but there were nothing like kernelpanic etc...

 

Now i use the realtek Kext for ethernet. It works nice!

 

 

Thank you,

 

 

pcace

[student_al]

Hey All,

 

So I am still having problems getting in to 10.6.4 using the flash drive *boot drive method. I am not positive which kexts to use or how to configure the EFI stings for my box using the Flash Drive install method. I am a little bit rusty on how to do all this. BTW, the new version of the script is pretty cool DigitalDreamer. I think it is awesome that you added the boot drive method. Also, how do I update my BIOS on the mobo?

 

This is what I am planning on doing.

1. Set up flash drive install disk...* I am still unsure of which kexts to load. Last time i tried to install it timed out during install

2. Install Chameleon boot loader v2 RC4

3. Insert the flash drive install disk

 

Motherboard: Gigabyte GA-EX58-UD5

Processor: Intel Core i7-920 2.66 GHz

Video Card: Sapphire RADEON HD4870 1 GB

[digital_dreamer]

Hey All,

 

So I am still having problems getting in to 10.6.4 using the flash drive *boot drive method. I am not positive which kexts to use or how to configure the EFI stings for my box using the Flash Drive install method. I am a little bit rusty on how to do all this. BTW, the new version of the script is pretty cool DigitalDreamer. I think it is awesome that you added the boot drive method. Also, how do I update my BIOS on the mobo?

 

This is what I am planning on doing.

1. Set up flash drive install disk...* I am still unsure of which kexts to load. Last time i tried to install it timed out during install

2. Install Chameleon boot loader v2 RC4

3. Insert the flash drive install disk

 

Motherboard: Gigabyte GA-EX58-UD5

Processor: Intel Core i7-920 2.66 GHz

Video Card: Sapphire RADEON HD4870 1 GB

By default, the boot drive install will include the kexts from /Kexts_10.6/ Boot_Disk/Extra/Extensions

These are just the basics to get one up and running. However, one is free to use what they wish for their install.

The kexts assigned for the UD5 board are the ones in each kext category in Kexts_10.6 (outside the repository folders).

 

As for the BIOS updates, copy the BIOS binary to a FAT32 formatted drive (flash is fine). Boot into the BIOS and follow the instructions for flashing. (I forget the keyboard shortcut, but it will be listed on the screen.)

 

BTW, getting QE/CI in 10.6.4 on the 4870 is a bit more work. I know some have gotten it on a 4890. I'm still playing with my 4870 X2

EDIT: I just got QE/CI in 10.6.4 on my 4870 X2. I'm using the following 1.6.10 versions (from 10.6.3):

ATI4800Controller.kext (Updated)

ATIRadeonX2000.kext (Updated)

ATIFramebuffer.kext

ATISupport.kext

ATIRadeonX2000GA.plugin

ATIRadeonX2000GLDriver.bundle

ATIRadeonX2000VADriver.bundle

ATY_Init.kext

 

I know two of the kexts are modified, but don't know about the others. Anyhow, I'll be including them in the script for the next release.

I had to rework the script to accept the non-kext files (.bundle and .plugin). This will be in the next update, too.

 

And, don't use the fakesmc.kext v2.6.2 (monitoring). I tried using it and never got video. It may be different on the one core 4870, though.

 

Let us know how it goes.

 

MAJ

[student_al]

By default, the boot drive install will include the kexts from /Kexts_10.6/ Boot_Disk/Extra/Extensions

These are just the basics to get one up and running. However, one is free to use what they wish for their install.

The kexts assigned for the UD5 board are the ones in each kext category in Kexts_10.6 (outside the repository folders).

 

As for the BIOS updates, copy the BIOS binary to a FAT32 formatted drive (flash is fine). Boot into the BIOS and follow the instructions for flashing. (I forget the keyboard shortcut, but it will be listed on the screen.)

 

BTW, getting QE/CI in 10.6.4 on the 4870 is a bit more work. I know some have gotten it on a 4890. I'm still playing with my 4870 X2

EDIT: I just got QE/CI in 10.6.4 on my 4870 X2. I'm using the following 1.6.10 versions (from 10.6.3):

ATI4800Controller.kext (Updated)

ATIRadeonX2000.kext (Updated)

ATIFramebuffer.kext

ATISupport.kext

ATIRadeonX2000GA.plugin

ATIRadeonX2000GLDriver.bundle

ATIRadeonX2000VADriver.bundle

ATY_Init.kext

 

I know two of the kexts are modified, but don't know about the others. Anyhow, I'll be including them in the script for the next release.

I had to rework the script to accept the non-kext files (.bundle and .plugin). This will be in the next update, too.

 

And, don't use the fakesmc.kext v2.6.2 (monitoring). I tried using it and never got video. It may be different on the one core 4870, though.

 

Let us know how it goes.

 

MAJ

 

Thanks DD,

 

Just a couple more questions. Are you suggesting that I try to use all of the following kexts to enable the 4870 single core?:

 

ATI4800Controller.kext (Updated)

ATIRadeonX2000.kext (Updated)

ATIFramebuffer.kext

ATISupport.kext

ATIRadeonX2000GA.plugin

ATIRadeonX2000GLDriver.bundle

ATIRadeonX2000VADriver.bundle

ATY_Init.kext

 

 

If I were to get a new graphics card, does it matter which manufacturer makes the 4890 graphics card? Newegg has only an XFX board.

 

-allan

[digital_dreamer]

allan,

I think, but am not sure, that you'll get video, but just not QE/CI without the mentioned kexts/files. Someone else has the 4870 and was able to get it working. Look a few posts back.

I don't believe the updated kexts are included in the current version of the script. For the 4870 single core, you may get by with fewer kexts, I don't know. I just know what I needed for the X2.

 

Strictly speaking, the brand is not the issue, but whether they are using a reference design as it relates to the type of video output ports. Some may be DVI/DVI or DVI/VGA or DVI/HDMI, etc. Some of the kexts are designed to work with a specific set of output ports and you may experience issues if the ports you have are not typical. Generally, having HDMI ports are a bit tricky, but the gang is gathering more and more experience as time goes by.

 

As for those files with .bundle or .plugin extensions, you'd have to install them manually, for the time being.

 

MAJ

[ral2108]

just wanted to say I used this script to install 10.6.2 sometime last year on my ex58-ud3r. I am extremely grateful for all the work put into this. because of this, I actually bought a Macbook Pro, which i never would have done without first knowing that I would like the OS and be fully functional/capable with it.

 

i have not installed any OS updates because I was in school and did not want to risk screwing things up. just from glancing at the first page, it looks like the only thing to worry about when installing the 10.6.4 update is sleepenabler. if anyone know of any other issues and would like to point them out, that would be awesome.

 

Thanks again!

[L3B3R]

I'm trying to do a fresh install from my distro installed drive and DDs script is giving me an error saying that "there may be two duplicate mount points." I have verified via Terminal that there are not two duplicate mount points. Anyone know how to get around this so that I can continue?

[digital_dreamer]

L3B3R,

Can you provide me a output from mount and one from ls /Volumes from the Terminal?

 

I want to make sure there are no false positives and this isn't a false alarm. If it's false, I need to fix it.

 

In the meantime, you can open the script in a text document and search for check_duplicate_mtpts and put a "#" in front of it (commenting it out).

Sorry about the hassle. However, duplicate mount points can wreak havoc on the system if a script is writing to fake volume.

 

MAJ

[weaana]

I'm trying to do a fresh install from my distro installed drive and DDs script is giving me an error saying that "there may be two duplicate mount points." I have verified via Terminal that there are not two duplicate mount points. Anyone know how to get around this so that I can continue?

 

got the very same problem, but on vmware workstation in windows. tried script 4.51 - no problem reported.

Thanks DD for the quick reply to the issue , cant thank you enough for your work.

 

heres my mount output

/dev/disk1s2 on / (hfs, local, journaled)

devfs on /dev (devfs, local, nobrowse)

map -hosts on /net (autofs, nosuid, automounted, nobrowse)

map auto_home on /home (autofs, automounted, nobrowse)

.host:/ on /Volumes/VMware Shared Folders (vmhgfs)

/dev/disk0s2 on /Volumes/snow (hfs, local, journaled)

/dev/disk0s4 on /Volumes/big (ntfs, local, read-only, noowners)

 

and heres ls volumes

ls /Volumes

VMware Shared Folders macvm

big snow

 

couldnt try the hashing out check duplicate mtpts as there as many lines with this and am a total noobie to code.

 

thNX again

[digital_dreamer]

Sorry about that, guys.

Here's v4.53 beta with that portion hashed out.

Note that these are just the shell scripts, they replace the two in ~extra/Resources.

 

 

weaana,

Are you saying you are running Mac OS X as a VM? Interesting stuff.

 

The duplicate mount point check is triggered by any volume listed in ls /Volumes that's not also in mount.

 

MAJ

 

EDIT:

weaana,

What does the script install log report as your "working volume?"

And, when the duplicate mount point error showed up, what did it report as the duplicate mount point?

 

I can't see anything wrong with the information, except to say that the working volume info may have been incorrect, for whatever reason.

Additionally, I notice there is a space in front of " snow" for the ls /Volumes result, but it is not present in the mount results. I assume it wasn't a straight copy and paste.

 

I'll have to make this error check one that can be ignored at the user's request.

[L3B3R]

EDIT:

weaana,

What does the script install log report as your "working volume?"

And, when the duplicate mount point error showed up, what did it report as the duplicate mount point?

 

I can't see anything wrong with the information, except to say that the working volume info may have been incorrect, for whatever reason.

Additionally, I notice there is a space in front of " snow" for the ls /Volumes result, but it is not present in the mount results. I assume it wasn't a straight copy and paste.

Mine said something about .DS_Store. Sorry I can't be of any more help; I don't know all that much about Terminal stuff.

[digital_dreamer]

Mine said something about .DS_Store. Sorry I can't be of any more help; I don't know all that much about Terminal stuff.

Ah! That's could be it. That's helpful. I'll try to make sure it doesn't pop up again.

 

MAJ

[L3B3R]

Ah! That's could be it. That's helpful. I'll try to make sure it doesn't pop up again.

 

MAJ

I replaced the files that you posted and everything is working so far. Now time for the install. Thanks for the quick update!

 

EDIT: Hey I duplicated the results. I got the "duplicate mount points" error again. A the bottom it states "The suspect mount points on your system are as follows: .DS_Store." I am trying to install using the modified DSDT method and DD's script. Can someone verify for me the path to where the modified DSDT needs to be. After installing and running the script I booted in -v and got a panic regarding AppleIntelCPUPowerManagement.kext. I went into my distro install and deleted that kext and rebooted. Then I got an error saying that it needed that kext. I went back and placed it back in its destination, ran DD's script, and then it gave me the "duplicate mount points" error.

[weaana]

Sorry about that, guys.

Here's v4.53 beta with that portion hashed out.

Note that these are just the shell scripts, they replace the two in ~extra/Resources.

 

 

weaana,

Are you saying you are running Mac OS X as a VM? Interesting stuff.

 

The duplicate mount point check is triggered by any volume listed in ls /Volumes that's not also in mount.

 

MAJ

 

EDIT:

weaana,

What does the script install log report as your "working volume?"

And, when the duplicate mount point error showed up, what did it report as the duplicate mount point?

 

I can't see anything wrong with the information, except to say that the working volume info may have been incorrect, for whatever reason.

Additionally, I notice there is a space in front of " snow" for the ls /Volumes result, but it is not present in the mount results. I assume it wasn't a straight copy and paste.

 

I'll have to make this error check one that can be ignored at the user's request.

 

thanks dd for the reply.

snow leopard works well in vmware except for qe/ci

 

parts of install.log of significance

 

Working Volume: macvm (disk1s2)

 

WARNING! There appears to be duplicate mount points!

Suspect mount points are as follows:

.DS_Store

 

and i dont get this error when running the script in my hackintosh install than vmware

[digital_dreamer]

EDIT: Hey I duplicated the results. I got the "duplicate mount points" error again. A the bottom it states "The suspect mount points on your system are as follows: .DS_Store."

<SNIP>

<SNIP>

.DS_Store

Okay, thanks, guys. This has been resolved and a update will be released shortly.

I never thought that a .DS_Store would be in the /Volumes list.

 

MAJ

[weaana]

Okay, thanks, guys. This has been resolved and a update will be released shortly.

I never thought that a .DS_Store would be in the /Volumes list.

 

MAJ

 

dsdt patcher used to work well on my dell xps 435mt rig.

but in 4.51 and 4.52 , dsdt patcher fails with one error and system fails to boot.

it worked in v4.10 but dont know from which version it stopped working for my mobo.

 

does dsdt patchers in new versions offer advantages or is it good to go with the patcher

in 4.10?

[digital_dreamer]

dsdt patcher used to work well on my dell xps 435mt rig.

but in 4.51 and 4.52 , dsdt patcher fails with one error and system fails to boot.

it worked in v4.10 but dont know from which version it stopped working for my mobo.

 

does dsdt patchers in new versions offer advantages or is it good to go with the patcher

in 4.10?

The newer version actually catches some errors the older one doesn't see, which is why it's probably failing for you.

However, you can switch to the older one:

Go to ~/extra/DSDT_Patcher/Tools

Put the current iasl file in the "5_28_10_32-bit" folder.

Pull out the iasl file from "3_9_10_32-bit" and make sure it's directly in the /Tools directory where the previous one was.

 

Provide me the DSDT log (before you run it again with the older version) and I'll see what it's hanging up on.

I may have to script up something to fix this error.

 

Thanks for the heads up on this!

 

MAJ