Jump to content

[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos


4,696 posts in this topic

Recommended Posts

Hi everyone,

 

I just updated to 10.6.4 from 10.6.2. I updated my boot cache before restarting after the update, and after booting back up I got a black screen. This was an issue I had with 10.6.3 and I am almost certain it has something to do with the HDMI on my graphics card as Apple either dropped support for that or has an issue with HDCP. I was hoping that after the Mac Mini update, 10.6.4 would offer support for my card to connect to my LCD TV. Right now I am using a DVI to HDMI cable to my LCD TV but that did not fix the problem. I'm not sure where to go from here of if anyone else has been able to get around this "little" problem as I know many people are experiencing this issue. Short of getting a new graphics card, I have no clue what to do. Please see signature for my setup. Thanks

Link to comment
Share on other sites

Ahh fixed the afp share not workning. I forgot in my raid installation the Boot OSX partition's mach_kernel was not getting updated so the kernel was still 10.3, putting the correct mach_kernel in fixed this. 10.4 kernel now!

 

Thanks

Yeah weird that we always have to go in and mount the drive and move and replace the kernel, I have no idea why the update doesnt just overwrite the old Kernel.

 

DD can you please shed some light on this issue?

Hmmmm. I can see the issue here. Our RAID setups don't use the same kernel that's installed by the OS. The OS installed version is in /Volumes/Boot OSX/com.apple.boot.P/mach_kernel

For our bootloader setups, they are installed at root of each RAID helper partition.

The script has no way of knowing the kernel has been updated, so it doesn't copy them over for RAID.

The solution would be to always have the script copy the kernel over on every kext install, or check the OS installed kernel binary for the Darwin Kernel Version and compare that the RAID version and set the kernel update flag on version mismatch.

 

More stuff to do.

 

MAJ

 

P.S. The current solution around this right now is simply delete the kernels in the RAID helper partitions (at root). The script will copy new ones over.

 

EDIT: This issue has been fixed in the latest version - 4.52

Link to comment
Share on other sites

Just wanted to be 100% sure -- does 10.6.4 work fine without any modifications if you've followed this Cruisar guide?

 

Thanks.

Yup it does provided you are using a supported GPU card. ATI users will still need to install the Exotic pkg from Netkas. Other than that, you are 100% safe.

 

Charles

Link to comment
Share on other sites

Yup it does provided you are using a supported GPU card. ATI users will still need to install the Exotic pkg from Netkas. Other than that, you are 100% safe.

 

Charles

 

Good to hear. Thanks.

Link to comment
Share on other sites

I ran the 10.6.4 update - mostly flawlessly. I deleted my "Stored_Kexts" to replace with the ones in the new Hackinstaller, then updated boot caches.

 

Network and Sound did not work after that, but I replaced RealtekR1000SL.kext with AppleRTL8169Ethernet.kext from another installer and network is fine.

 

I'm still not sure why I'm having no luck with audio. I'm using the GA-X58A-UD5 motherboard. The only audio that worked for me on 10.6.3 VoodooHDA - and even then I had no digital SPDIF, which I really need.

 

Are most people just using the Hackinstaller's LegacyHDA/HDAEnabler with a stock AppleHDA?

Link to comment
Share on other sites

I ran the 10.6.4 update - mostly flawlessly. I deleted my "Stored_Kexts" to replace with the ones in the new Hackinstaller, then updated boot caches.

 

Network and Sound did not work after that, but I replaced RealtekR1000SL.kext with AppleRTL8169Ethernet.kext from another installer and network is fine.

 

I'm still not sure why I'm having no luck with audio. I'm using the GA-X58A-UD5 motherboard. The only audio that worked for me on 10.6.3 VoodooHDA - and even then I had no digital SPDIF, which I really need.

 

Are most people just using the Hackinstaller's LegacyHDA/HDAEnabler with a stock AppleHDA?

Are you installing these audio and Ethernet kexts in /System (S/L/E)? They don't work in /Extra.

 

MAJ

Link to comment
Share on other sites

Anyone having issues with a second monitor displaying odd colors since upgrading to 10.6.4? My GA-EX58-UD5 has been working flawlessly until ...

 

I have a GTX 285 and it's been working great. Updating to 10.6.4 did give me a very slight drop in FPS in World of Warcraft, but no biggy. Everything else has been working great.... except....

 

My 50" external LCD I use as a second monitor has its colors all screwed up. Prior to upgrading it worked fine.

 

I tried changing the cable, reseting the color profiles, deleting all the color profiles, even hooking the LCD up to another computer (worked fine). I also tried resetting the Display Options under Universal Access .... nothing. It's something to do with 10.6.4 and I haven't been able to narrow it down.

 

Anyone have any suggestions or insights?

 

EDIT : Fixed! I installed nVidia's latest Mac drivers from June 20th and now my secondary monitor has perfect color again.

Link to comment
Share on other sites

Are you installing these audio and Ethernet kexts in /System (S/L/E)? They don't work in /Extra.

 

MAJ

 

I'm using the audio and ethernet kexts in /Extra and they work fine. I am using the Crusair method w/your script. For some reason my audio and ethernet would not work unless I had them in /Extra. I am using the RealtekR1000SL kext and the HDAEnabler and LegacyHDA kexts as well.

Link to comment
Share on other sites

Are you installing these audio and Ethernet kexts in /System (S/L/E)? They don't work in /Extra.

 

MAJ

 

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.

Link to comment
Share on other sites

Wow. this process if kicking my ass..

 

I was able to install Leopard just fine but Snow Leopard is killing me..

 

anyway, I get this error when using the 5th menu -- kexts installation -- Normal mode

"324 of 3 kexts failed to make it into cache!

See logs for details."

 

logs say stuff like:

"kextcache: found invalid extension AppleStorageDrivers.kext/Contents/PlugIns/OxfordSemiconductor.kext

kextcache: kext /Volumes/SnowL/System/Library/Extensions/AppleStorageDrivers.kext/Contents/PlugIns/PioneerSuperDrive.kext is not valid

kextcache: found invalid extension AppleStorageDrivers.kext/Contents/PlugIns/PioneerSuperDrive.kext"

Link to comment
Share on other sites

Wow. this process if kicking my ass..

 

I was able to install Leopard just fine but Snow Leopard is killing me..

 

anyway, I get this error when using the 5th menu -- kexts installation -- Normal mode

"324 of 3 kexts failed to make it into cache!

See logs for details."

 

logs say stuff like:

"kextcache: found invalid extension AppleStorageDrivers.kext/Contents/PlugIns/OxfordSemiconductor.kext

kextcache: kext /Volumes/SnowL/System/Library/Extensions/AppleStorageDrivers.kext/Contents/PlugIns/PioneerSuperDrive.kext is not valid

kextcache: found invalid extension AppleStorageDrivers.kext/Contents/PlugIns/PioneerSuperDrive.kext"

LOL! It's the new math.

 

Seriously, the script is failing to include all the kexts in the plugins folder, so the total is off. But, that's not the real problem here.

Are you doing the kext installation from Leopard (10.5)? There are x86_64 (64-bit) kexts that will not properly build into the boot cache. (I'm assuming that's why the "kext is not valid.")

I need more information: Would you supply both the Install.log and Boot_cache.log for me to view?

 

MAJ

Link to comment
Share on other sites

Hey,

 

im using the UD5 mainboard, only SATA hdds and a nVidia 9800GT. wat is the minimal kext configuration i could use?

So wich kext do i reall nead??

 

 

Thanks!

 

 

Pcace

Check my guide out in my signature.

Link to comment
Share on other sites

LOL! It's the new math.

 

Seriously, the script is failing to include all the kexts in the plugins folder, so the total is off. But, that's not the real problem here.

Are you doing the kext installation from Leopard (10.5)? There are x86_64 (64-bit) kexts that will not properly build into the boot cache. (I'm assuming that's why the "kext is not valid.")

I need more information: Would you supply both the Install.log and Boot_cache.log for me to view?

 

MAJ

 

lol.

 

Yeah, I'm doing it from my Leopard install -- installed using your method for Leopard --

 

Install.log: http://tinypaste.com/dd594

 

Boot_cache.log: http://tinypaste.com/b960f

Link to comment
Share on other sites

lol.

 

Yeah, I'm doing it from my Leopard install -- installed using your method for Leopard --

 

Install.log: http://tinypaste.com/dd594

 

Boot_cache.log: http://tinypaste.com/b960f

LeifErikson,

I'd suggest, for now, to direct your kexts to be installed into /System, not extra. Do this from the script.

Then, boot into your install in Safe Mode using the "-s" flag (without quotes), type "buildcache" at the prompt (without quotes), then reboot.

 

MAJ

Link to comment
Share on other sites

LeifErikson,

I'd suggest, for now, to direct your kexts to be installed into /System, not extra. Do this from the script.

Then, boot into your install in Safe Mode using the "-s" flag (without quotes), type "buildcache" at the prompt (without quotes), then reboot.

 

MAJ

 

I did that, but when I type in -s in the Cham 2.0 RC4 official release bootloader, I get no prompt after that and I get this:

61093332.jpg

 

Im installing OSX from the 10.6.0 dvd release the initial release.

 

EDIT:

 

I also get this:

DSDT compiling failed both attempts!

See DSDT output log for details.

 

Can I use the DSDT from Leopard on this?

Link to comment
Share on other sites

I did that, but when I type in -s in the Cham 2.0 RC4 official release bootloader, I get no prompt after that and I get this:

61093332.jpg

 

Im installing OSX from the 10.6.0 dvd release the initial release.

 

EDIT:

 

I also get this:

DSDT compiling failed both attempts!

See DSDT output log for details.

 

Can I use the DSDT from Leopard on this?

Okay, since you don't have a DSDT file generated, you're going to have to use the PC_EFI bootloaders. Those bootloaders by netkas allow you to boot without a DSDT file. The kernel panic you have is from not using a DSDT file on the Chameleon 2 bootloader.

But, you can try the one from Leopard, first. It should be the same.

 

BTW, the -s flag is SIngle-User mode, not Safe Mode, as I had written earlier.

 

I'll need the DSDT log to figure out what's going on there.

 

As for the other logs on the boot caches, I'm looking into that.

 

MAJ

Link to comment
Share on other sites

Okay, since you don't have a DSDT file generated, you're going to have to use the PC_EFI bootloaders. Those bootloaders by netkas allow you to boot without a DSDT file. The kernel panic you have is from not using a DSDT file on the Chameleon 2 bootloader.

But, you can try the one from Leopard, first. It should be the same.

 

BTW, the -s flag is SIngle-User mode, not Safe Mode, as I had written earlier.

 

I'll need the DSDT log to figure out what's going on there.

 

As for the other logs on the boot caches, I'm looking into that.

 

MAJ

 

 

Alright, I'll try to EFI bootloader.

 

Also, if -s is single-user, what's Safe mode? lol

 

DSDT log:

[H[2Jdyld: unknown required load command 0x80000022
[H[2JDSDT Patcher 1.0.1e -- report Bugs to superfassl@gmail.com
enclose "DSDT Patcher/Debug/USER.tar"


Press any key to continue...


Getting the DSDT through ioreg...



Decompiling the DSDT...



Done, now start the Patching!

Could not open file ./dsdt.dsl

There were errors pacthing the RTC

Compiling failed second attempt! Procedure aborted.

Link to comment
Share on other sites

Check my guide out in my signature.

 

Hey Thank you very much!

Right now i have only Realtec and fakesmc installed, and the system boots in 64 bit mode.

Also poweroff / restart works, BUT sleep doesnt't work.

Any Idea what wthere could be wrong?

        ################################################################
        #                       HackInstaller                        #
         #       Chameleon Bootloader & Kext/Kernel Installer       #
         #                                                          #
        #                  v4.52 by digital_dreamer                  #
       ################################################################

Files to be installed from
the script's folders to MacOSX - Extra:

ATA				      VERSION      ARCH    SIZE  DESTINATION
  (No files present to install)

Audio
  (No files present to install)

Graphics
  (No files present to install)

Networking
1) RealtekR1000SL.kext               2.0.0d1    x86_64    256K      /System

Misc Patches
2) fakesmc.kext                      2          x86_64    124K       /Extra

Kernel & matching kext
   (No files present to install)

 

And here my 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>device-properties</key>        
<string>cd0300000100000001000000.......gpu-efi-string.........736f722d706172656e74</string>
       <key>Kernel</key>
       <string>mach_kernel</string>
       <key>Kernel Flags</key>
       <string>arch=x86_64 -v boot-uuid=B255AB20-C785-4AA8-85BA-5E4FCD21BDAE</string>
       <key>Timeout</key>
       <string>10</string>
</dict>
       </plist>

 

 

 

Any Idea?

 

 

Thanks!

 

Pcace

Link to comment
Share on other sites

Hey Thank you very much!

Right now i have only Realtec and fakesmc installed, and the system boots in 64 bit mode.

Also poweroff / restart works, BUT sleep doesnt't work.

Any Idea what wthere could be wrong?

 

Any Idea?

Thanks!

 

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.

Link to comment
Share on other sites

 Share

×
×
  • Create New...