Jump to content

[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos


4,696 posts in this topic

Recommended Posts

ATI 4870 fixed!!! on 10.6.4..

looks like i'm stuck using the old 10.6.2 ATI files..

 

had to copy the following three ATI4800controller, ATIFramebuffer and ATISupport (all 3 are on 1.6.6 version) to S/L/E.

also needed LegacyATI4800Controller.Kext in /Extra/Stored_Kexts

 

that did the trick...without the LegacyATI file in Stored_Kexts video did not work!

 

thanks all, hope this helps.

 

 

Hi bbchucks

 

I was hoping you could elaborate how you got 10.6.4 to get setup with the 4870 card. I just got booted int SL. Where to I get the mysterious 1.6.6 version?

 

-allan

Link to comment
Share on other sites

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

 

Tried all three versions of iasl files with 4.53 script, all failed with one error.

went back to 4.10 and dsdt patcher worked.

tried putting that iasl file with 4.53 , no luck, still one error.

so the problem seems to be not with iasl file but with patcher?

attaching the dsdt output for iaml 5_32 dsdt_output32.log, 5_64 dsdt_output64.log , 3_32 dsdt_outputv3.log, and finally succesful dsdt patch output dsdt_output.log.

hope its useful.

 

dsdtoutput.zip

 

Hi Dude!

 

After 10.6.4 update shut-down does'nt work!

:)

 

me too had the same problem , using the old openhaltrestart.kext solved the issue for me.

Link to comment
Share on other sites

weaana,

Thanks for the logs. I'm finding the iasl code is being clipped at the end. So, when/if you are able, would be you be able to post for me the actual dsdt_fixed.txt file (in ~/extra/DSDT_Patcher/Debug) after you have run the recent scripts that fails?

 

BTW, are you running a ASUS board?

 

best regards,

MAJ

Link to comment
Share on other sites

Tried all three versions of iasl files with 4.53 script, all failed with one error.

..... zip ... zip ... zip

 

me too had the same problem , using the old openhaltrestart.kext solved the issue for me.

 

Great weaana!

It works now.

I used july 3 09 (1.0.3) version and all ok!

 

Thanks guy!

Link to comment
Share on other sites

DD I'm getting a file not found when I try to download the latest installer.

 

Also the 4.5.1 installer is telling me I have more than 9 hard drives/partitions and is refusing to install. Initially I had 5 hd + SATA dvd, but I cut that down to 3 hd and it's still giving me that error. All only have 1 partition on them.

 

BTW thanks again for all your hard work with this.

Link to comment
Share on other sites

Hi Boss!

 

i'm tuning the system now and some things appears no good

 

###################### 2 of 13 kexts in /Extra failed to make it into cache!

LegacyATI4800Controller.kext does not match OSBundleRequired conditions; omitting from mkext.

VoodooHDA.kext does not match OSBundleRequired conditions; omitting from mkext.

 

VoodooHDA i dont remember why is there, but i leave it (for tryng ?!?) ( i use an external USb Roland mixer for audio)

surely now i try to cut it

 

LegacyATI4800 is used in conjunction with EVOenabler (it is 64bit, ATYInit is 32)

video works fine but i read more lot of posts about GPU - nothing is clear - and after test GL 3.0 is wrong

 

i'm waiting for your light: D_D :P

Link to comment
Share on other sites

DD I'm getting a file not found when I try to download the latest installer.

 

Also the 4.5.1 installer is telling me I have more than 9 hard drives/partitions and is refusing to install. Initially I had 5 hd + SATA dvd, but I cut that down to 3 hd and it's still giving me that error.

 

BTW thanks again for all your hard work with this.

Hmmm. The download links appear to work for me. Which specific link are you referring to?

 

Any mounted disk/ISO will increase the drive count.

You'll need to reboot without the extra drives attached, because even if you remove them after the boot, various drives will still have a >9 ID attached to them.

I can't guarantee the accuracy of the script when it needs to check all drives, with some having an identifier over 9.

 

If you only have 3 HD attached and less than 9 partitions each (LOL), there shouldn't be a problem. Send me the Install.log or post your "diskutil list" from Terminal and we'll see what it's hanging up on.

Sorry for the hassle.

 

EDIT: I think that issue has been fixed the the later versions (4.52 and up). Certain devices create a double-digit ID and I've had to account for this and have the script ignore it.

 

MAJ

Link to comment
Share on other sites

Hi Boss!

 

i'm tuning the system now and some things appears no good

 

###################### 2 of 13 kexts in /Extra failed to make it into cache!

LegacyATI4800Controller.kext does not match OSBundleRequired conditions; omitting from mkext.

VoodooHDA.kext does not match OSBundleRequired conditions; omitting from mkext.

 

VoodooHDA i dont remember why is there, but i leave it (for tryng ?!?) ( i use an external USb Roland mixer for audio)

surely now i try to cut it

 

LegacyATI4800 is used in conjunction with EVOenabler (it is 64bit, ATYInit is 32)

video works fine but i read more lot of posts about GPU - nothing is clear - and after test GL 3.0 is wrong

 

i'm waiting for your light: D_D :)

 

That appears normal for the LegacyATI4800Controller.kext, as it has a "OSBundleRequired" string of "Safe Boot" and has nothing to include in the boot cache for a normal boot. Only kexts that have "Root" or "Local Root" OSBundleRequired requirements get included in the boot cache.

I don't know about the VoodooHDA.kext, but I believe it also contains OSBundleRequired conditions that make it necessary that it be installed in /System or S/L/E.

If you get these warnings, it simply means that, due to the way the kext was created, its information wasn't required at boot time. There are lots of kexts in S/L/E that don't get included in the main boot cache either (about half), because the info is not needed at boot. The script ignores all those, as they are too many and the info is useless.

 

These warnings are actually reported by the OS. The script just parses them and logs them for you to see and be aware of. So, the script really has little to do with this, but is simply a messenger. I've reworked the logging and reporting of the boot cache setup and it's catching lots of stuff that you normally don't see. So, this is really handy, as it lets you know that the kext did not get included in the boot cache for one reason or another. In cases like this, it may mean that it's better suited in /System, where the system can access it and load it after boot. Additionally, the script will ignore it there.

 

Are you using something else for audio? Because that's what the VoodooHDA.kext is for. But, it needs to be in /System to work.

Additionally, do you have a ATI 48XX series graphics card? If you don't, you can safely remove that LegacyATI4800Controller.kext. Nevermind, I see your signature. LOL!

 

MAJ

Link to comment
Share on other sites

I seem to have hit an impasse. I have no access to OS X, so I used the pre-boot procedure. All of that, and install, went fine. I could use the preboot CD to boot into OS X again, run the hackinstaller script, etc. However, when I try to boot I get the dreaded "still waiting for root device". I moved my SATA cables from port 5 to port 2 (or 1, if you count from 0), but that changed nothing.

 

Any ideas? I've also already tried re-installing from scratch. I haven't tried to use the pre-boot CD again. Right now I'm going to try and force it to boot by putting "rd=disk1" in the <string></string> line in com.apple.Boot.plist . I've also tried booting without caches.

 

My first install was an EFI, then I decided to try /Extra . I used the Chameleon RC4 bootloader included with v4.53 of the Hackinstaller script.

 

Edit: I should mention I'm using a DFI X58-t3eh8. But aside from booting, everything seemed to work. Though my resolution was stuck at 1024x768, but I simply assumed that was because I hadn't run the Hackinstaller script. I'm running an 8800GTS. I also have the logs from the installer script, if they would help.

 

Image: http://farm5.static.flickr.com/4142/476696...8986b9705_b.jpg

Link to comment
Share on other sites

weaana,

Thanks for the logs. I'm finding the iasl code is being clipped at the end. So, when/if you are able, would be you be able to post for me the actual dsdt_fixed.txt file (in ~/extra/DSDT_Patcher/Debug) after you have run the recent scripts that fails?

 

BTW, are you running a ASUS board?

 

best regards,

MAJ

 

dd,

my hackintosh rig is dell xps 435 mt , so must be a dell x58 mobo

heres the log and dsdtfixed.txt after running with iaml v3 which fails.

i would love to provide more info if needed.

 

dsdt_fixed.txt

DSDT_output.log.txt

Link to comment
Share on other sites

AutumnJazz,

Your system is not able to find your OS install for some reason. Did you get the same error when you installed via EFI?

I suspect the real issue is your system is not in AHCI mode and cannot boot your HD drives. Make sure AHCI is enabled.

 

 

weaana,

Thanks for those files. I'm realizing I'm going to have to implement a more robust checksum routine to make sure DSDT fixes are implemented correctly. This is my next big project. Your logs reveals a need for more changes and a need to be more flexible in handling the DSDT routines.

 

Since the faulty "fixed" file is clipped, would you provide your current fixed one, so I can work with it and use it as a test file?

 

best regards,

MAJ

Link to comment
Share on other sites

AutumnJazz,

Your system is not able to find your OS install for some reason. Did you get the same error when you installed via EFI?

I suspect the real issue is your system is not in AHCI mode and cannot boot your HD drives. Make sure AHCI is enabled.

Yes, I got the same error when I installed via EFI. And my system is definitely in AHCI...I'm in my Windows partition right now, and I can mount/dismount my drives at will. I have a feeling that there is something wonky going on with my motherboard...I am no longer able to get into the boot device selection menu anymore, so the only way to boot via a CD is for me to enter my BIOS and change the boot order. And it seems to set itself back to IDE emulation mode whenever I install OS X, so I have to set it back.

 

But what I don't understand was how I was able to reboot via the pre-boot CD, as instructed by the install instructions, before I ran the Hackinstaller script. I'm going to try booting again via the pre-boot CD, but I can't right this second.

 

Edit:

boot_cache.log http://tinypaste.com/9586e

DSDT_output.log http://tinypaste.com/ee47a

Install.log http://tinypaste.com/30a4b

Link to comment
Share on other sites

weaana,

Thanks for those files. I'm realizing I'm going to have to implement a more robust checksum routine to make sure DSDT fixes are implemented correctly. This is my next big project. Your logs reveals a need for more changes and a need to be more flexible in handling the DSDT routines.

 

Since the faulty "fixed" file is clipped, would you provide your current fixed one, so I can work with it and use it as a test file?

 

best regards,

MAJ

heres the dsdtfixed.txt from succesful dsdt patch with 4.10

keep up the goodwork and all the best on the new big project!

dsdt_fixed.txt

Link to comment
Share on other sites

Allan,

i'm using the ati4870 (1dvi,1hdmi,1vga port) and for 10.6.4 i have to use the following kexts from 10.6.2:

 

S/L/E:

ATI4800Controller.kext

ATIFramebuffer.kext

ATISupport.kext

 

/Extra/Stored_Kext/LegacyATI4800Controller.kext

 

I've tried numerous combos, and none would boot up until i did the above. Tried using EVO, aty, editing kexts, etc...nothing would let me boot up successfully. the best i could do was to boot up then VNC into the machine, other times i wasn't even able to VNC in.

 

good luck!!

 

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

Link to comment
Share on other sites

Yes, I got the same error when I installed via EFI. And my system is definitely in AHCI...I'm in my Windows partition right now, and I can mount/dismount my drives at will. I have a feeling that there is something wonky going on with my motherboard...I am no longer able to get into the boot device selection menu anymore, so the only way to boot via a CD is for me to enter my BIOS and change the boot order. And it seems to set itself back to IDE emulation mode whenever I install OS X, so I have to set it back.

 

But what I don't understand was how I was able to reboot via the pre-boot CD, as instructed by the install instructions, before I ran the Hackinstaller script. I'm going to try booting again via the pre-boot CD, but I can't right this second.

 

Edit:

boot_cache.log http://tinypaste.com/9586e

DSDT_output.log http://tinypaste.com/ee47a

Install.log http://tinypaste.com/30a4b

I updated my BIOS, which seems to have fixed the weirdness it was exhibiting before.

 

I tried booting via the pre-boot CD...no luck. It got stuck at the same place as it did via the installed Chameleon.

 

What I cannot understand is why it worked before I ran the Hackinstaller script.

 

Man, I just want Final Cut Pro. :) I'm so close to just getting the Gigabyte board that is the focus of this thread...not to mention USB 3, eSATA, and SATA 3 support. Delicious.

Link to comment
Share on other sites

AutumnJazz,

I see a serious DSDT error in the log.

Try booting without installing the DSDT patch. Make sure you use the PC-EFI versions of the bootloaders, as they will allow you to boot without a DSDT patch.

This should get you up and going.

 

MAJ

Link to comment
Share on other sites

Hmmm. The download links appear to work for me. Which specific link are you referring to?

 

Any mounted disk/ISO will increase the drive count.

You'll need to reboot without the extra drives attached, because even if you remove them after the boot, various drives will still have a >9 ID attached to them.

I can't guarantee the accuracy of the script when it needs to check all drives, with some having an identifier over 9.

 

If you only have 3 HD attached and less than 9 partitions each (LOL), there shouldn't be a problem. Send me the Install.log or post your "diskutil list" from Terminal and we'll see what it's hanging up on.

Sorry for the hassle.

 

EDIT: I think that issue has been fixed the the later versions (4.52 and up). Certain devices create a double-digit ID and I've had to account for this and have the script ignore it.

 

MAJ

 

I'm able to download the file now. IIRC, it was the 4.5.2 version of the installer, perhaps you were changing it to the 4.5.3 version when I was trying to download it or something like that

 

I'm still getting the disk error with the 4.5.3 version though. I ran the diskutil list as you suggested and this is what I get.

 

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *160.0 GB disk0

1: EFI 209.7 MB disk0s1

2: Apple_HFS Orbital Ring 159.7 GB disk0s2

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: Apple_partition_scheme *160.0 GB disk1

1: Apple_partition_map 32.3 KB disk1s1

2: Apple_Driver43 28.7 KB disk1s2

3: Apple_Driver43 28.7 KB disk1s3

4: Apple_Driver_ATA 28.7 KB disk1s4

5: Apple_Driver_ATA 28.7 KB disk1s5

6: Apple_FWDriver 262.1 KB disk1s6

7: Apple_Driver_IOKit 262.1 KB disk1s7

8: Apple_Patches 262.1 KB disk1s8

9: Apple_HFS Von Braun 159.9 GB disk1s10

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *150.0 GB disk2

1: EFI 209.7 MB disk2s1

2: Apple_HFS Anahime Electronics 149.7 GB disk2s2

 

For some reason the Orbital Ring disk seems to have a ton of partitions? on it. Only one shows when I look at it withe the GUI Disk util. Not sure why. It is my system disk and I did it about 9 months ago with what ever version of the installer you had then. I'm trying to get SL server installed on the Anahime Electronics disk and then transition to that as the os on this machine, since it's in a server case with room for a ton of HD (if I can ever get that thrice dammed Areca Raid card to work).

Link to comment
Share on other sites

AutumnJazz,

I see a serious DSDT error in the log.

Try booting without installing the DSDT patch. Make sure you use the PC-EFI versions of the bootloaders, as they will allow you to boot without a DSDT patch.

This should get you up and going.

 

MAJ

Do you have any idea how I can fix this? Thanks, though.

Link to comment
Share on other sites

Hello,

 

1) I'm using Cruisar's modified dsdt file and Realtek1000SL.kext and recently got into the following problem:

 

Somehow, os-x does not see internet cable plugged into "en1" (top socket, "cable unplugged" in system preferences) whereas it works for "en0" (socket closer to audio card in/out's).

It used to be ok for both and i didn't do anything to the system (no updates, no change of kext's, dsdt, etc).

 

It's not a big deal since i just plugged the cable in "en0" but still it's somehow strange.

I guess it can stop working the other socket too.

 

btw, it works fine in Windows, so it's not a hardware problem.

 

2) Sorry to repeat, but

does anyone have Line-In/Mic-In working with EX58-ud5 ?

It does not work for me with HDAEnabler and LegacyHDA kexts.

 

so, no microphone in Skype and no chats :thumbsup_anim:

 

Thanks.

 

p/s/ Thanks everyone for keep working on hakintosh, sharing information and giving advices.

Link to comment
Share on other sites

AutumnJazz,

I see a serious DSDT error in the log.

Try booting without installing the DSDT patch. Make sure you use the PC-EFI versions of the bootloaders, as they will allow you to boot without a DSDT patch.

This should get you up and going.

 

MAJ

 

Thanks! Everything is working perfectly now. I got my graphics card working as well with osx86 tools.

 

I suppose now I need to go set up my DSDT...but I don't really know how. The wiki says there are a few tools, so I'll start there.

 

Seriously though, thank you.

Link to comment
Share on other sites

I have 10.6.4 up and running, but have lost my video and ethernet.

 

I can only display 1024 x 768

 

and ethernet isn't working.

 

Is this a kext issue?

I notice you have a GeForce 9800 GTX+ 512MB. This particular card has been troublesome in getting QE/CI in SL, unfortunately.

However, are you using a EFI string or some injector for the nVidia card?

 

As for ethernet, sounds like you need to reinstall the kext in /System. I don't know why it wouldn't be working, as it shouldn't get overwritten by any updates, unless you were using a IONetworkingFamily.kext that had the Realtek kext inside the Plugins folder.

I have the RealtekR1000SL.kext installed in /System.

 

 

SCRIPT UPDATE:

(front page is not updated)

I have a updated HackInstaller shell script for use.

It incorporates a new DSDT fix selector: Just use the up and down arrow keys to navigate the list and enable/disable the fixes using the right and left keys.

Plus, it incorporates some handy troubleshooting routines (really needed with all the variables in DSDT codes) where failed fixes are simply aborted and the script continues with the next fix. Additionally, on failed fixes, the script will dump the results in a folder for the user to email to me to analyze.

Those who've had DSDT issues with the recent script are encouraged to try this new version and report back.

 

Plus, the issue with "too many partitions/drives" is partially resolved, as the user is given the choice to continue.

 

Just replace the current shell script in ~extra/Resources with this version.

 

MAJ

Link to comment
Share on other sites

I actually have several partitions on my hackintosh. I'm currently on a partition that is running 10.6.4 and my resolution is working at 1920 x 1200, but I can't play WOW. Says it can't launch 3D.

 

Is there a way to get my video card to work or do i need to revert back to 10.6.3 or even 10.6.2 Here is what i have in the semi-working boot.plist

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
 <key>Graphics Mode</key>
 <string>1920x1200x32</string>
 <key>Kernel</key>
 <string>mach_kernel</string>
 <key>Kernel Flags</key>
 <string>-v pmVersion=20 -x32 boot-uuid=4B2A9A3E-0456-3DD8-8EFB-CDFB4074215E</string>
 <key>Timeout</key>
 <string>1</string>
 <key>device-properties</key>
 <string>d20300000100000001000000c60300001500000002010c00d041030a010000000101060000030101060000007fff040014000000400032002c006e0061006d00650000001100000073656e736f722d706172656e74220000005600520041004d002c0074006f00740061006c00730069007a0065000000080000000000002036000000400032002c00680077006300740072006c002d0070006100720061006d0073002d00760065007200730069006f006e00000008000000000000021c0000006400650076006900630065005f0074007900700065000000100000004e5644412c4765466f7263650e0000006e0061006d00650000000f0000004e5644412c506172656e7422000000400030002c006400650076006900630065005f00740079007000650000000b000000646973706c6179100000006d006f00640065006c0000001f0000004e5649444941204765466f7263652039383030204754582044444c22000000400031002c006400650076006900630065005f00740079007000650000000b000000646973706c617912000000400032002c007200650067000000080000000000000222000000400032002c006400650076006900630065005f0074007900700065000000120000004e5644412c6770752d64696f646520000000400032002c0063006f006d00700061007400690062006c0065000000160000004e5644412c73656e736f722d706172656e7422000000400032002c002300730069007a0065002d00630065006c006c0073000000080000000000000020000000400031002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d616314000000400030002c006e0061006d0065000000120000004e5644412c446973706c61792d413a000000400032002c0068007700730065006e0073006f0072002d0070006100720061006d0073002d00760065007200730069006f006e000000080000000000000226000000400032002c0023006100640072006500730073002d00630065006c006c0073000000080000000000000114000000400031002c006e0061006d0065000000120000004e5644412c446973706c61792d4220000000400030002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d61631e00000072006f006d002d007200650076006900730069006f006e000000090000003331373261100000004e00560043004100500000001800000004000000000003000c00000000000007000000000e0000004e00560050004d0000002000000001000000000000000000000000000000000000000000000000000000</string>
</dict>
</plist>

Link to comment
Share on other sites

SCRIPT UPDATE:

(front page is not updated)

I have a updated HackInstaller shell script for use.

It incorporates a new DSDT fix selector: Just use the up and down arrow keys to navigate the list and enable/disable the fixes using the right and left keys.

Plus, it incorporates some handy troubleshooting routines (really needed with all the variables in DSDT codes) where failed fixes are simply aborted and the script continues with the next fix. Additionally, on failed fixes, the script will dump the results in a folder for the user to email to me to analyze.

Those who've had DSDT issues with the recent script are encouraged to try this new version and report back.

 

Plus, the issue with "too many partitions/drives" is partially resolved, as the user is given the choice to continue.

 

Just replace the current shell script in ~extra/Resources with this version.

 

MAJ

 

dsdt patcher works perfectly with the new script v4.54beta on my dell studio xps 435mt rig

 

thanks dd

Link to comment
Share on other sites

 Share

×
×
  • Create New...