[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos

[VirusX]

any issues with updating to 10.6.7? I have only my main system right now which I can't afford to destroy

[CruiSAr]

any issues with updating to 10.6.7? I have only my main system right now which I can't afford to destroy

Those using my short guide can update to 10.6.7 without issues. Remember to backup your ATI kexts if you use any.

 

Cheers

[epitaphic]

Can confirm update to 10.6.7 was flawless (using CruiSAr's method). No need to touch/change/update anything. Just install the update, reboot, you're good to go! (my gfx card is nVidia)

 

Interesting tho, my kernel version is listed as 10.7.0

[Z4g0r]

Hi D_D

I boot with Cham with lion on a Usb-flash maded by Your script (by typing "-v -usecache" after spacebar pressing)

after some few times my hackintosh (that running normally 10.6.4) REBOOT

i record the last message when "Starting Darwin X86_64"

MOBO EX58-UD5 12GB ATI HD4870 like in my signature

here the picture

[digital_dreamer]

Hi all

 

Thanks to DD script, my machine is working like a charm with OSX but I am planning to replace my video card (nvidia GT9500) with a new one which can perform Bluray playback (when running windows 7) with audio ouput on HDMI (so my home theater amplifier could decode HD audio streams)

 

The GT430/GT440 seems to be good choices for the job, but do they run fine with OSX as no "real mac" uses these cards. (The GT9500 was se same as the GT130 that Apple was using at this time in mac pro and iMacs)

 

With OSX, I need DVI and VGA output only (I am using 2 screens) as HDMI output will be used only on Windows

 

Do some of you own these cards ? Do they work flawlessly on OSX or do they require some hacking to work ?

 

Thanks

You may find better answers to your graphics-related questions in the Graphics forum. I don't really have any answers, but others may chime in.

 

Looks like you are booted in, but with no graphics support. So close, but so far.

 

Can confirm update to 10.6.7 was flawless (using CruiSAr's method). No need to touch/change/update anything. Just install the update, reboot, you're good to go! (my gfx card is nVidia)

 

Interesting tho, my kernel version is listed as 10.7.0

Yeah, odd version numbering. I noticed someone had posted the version number of the System.kext being 10.7

So, is it really the Lion kernel or is it just a version number slip?

<brain fart>

 

Hi D_D

I boot with Cham with lion on a Usb-flash maded by Your script (by typing "-v -usecache" after spacebar pressing)

after some few times my hackintosh (that running normally 10.6.4) REBOOT

i record the last message when "Starting Darwin X86_64"

MOBO EX58-UD5 12GB ATI HD4870 like in my signature

here the picture

That's a very common KP. You'll just have to keep trying.

I keep my hand by the reset button each time I boot into Lion.

Edit: Wrong. I looked at that picture wrong. It looks like it's trying to load kexts, which it's not supposed to. It's supposed to load the kernelcache immediately, just like it would load a kernel before, but this time it already includes the kexts. No kext loading should appear. Make sure you are not using the -f flag (check boot plist), which forces system to reload kexts and dump boot cache.

 

There is a DUET based bootloader called [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] that can boot into Lion without the KP. Incorporating the [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] bootloader into the existing script was going to create more work that I wanted to get into (very different install procedures), especially when you consider that when the Chameleon solution was released, I would need to remove it. So, I opted to wait for the Chameleon version - more compatible, less work. However, I expected that the DF KP would be fixed shortly.

 

Keep in mind that this is the FIRST developer release, so don't expect too much at this time, whether from Apple or from the Chameleon team. Give it time and it'll all work out. Additionally, this is a DEVELOPER release and not for public consumption. So, we're on the bleeding, leading edge here trying a developer release on a PC. Changes are going to be needed to make this work smoothly.

 

FYI:

Lion doesn't boot from the kext cache (mkext file) anymore, so it doesn't look like we'll be creating them. Instead, we'll be booting from a pre-linked kernel or kernelcache. This is a cache that contains the binary of the kernel, plus the kexts. Makes booting even faster as the kexts have been parsed and linked to the kernel.

 

I don't know how the Chameleon team is going to handle this, as the kernelcache in the /System location changes based on the contents of S/L/E. I notice a compressed plist in that cache directory that contains the contents of /S/L/E and their paths. Perhaps it can be manipulated to include kexts in /Extra. Even so, it will get overwritten by the OS at some time. My best guess is that we'll be needing to install a pre-made kernelcache in /Extra for the bootloader to boot from, before it gets handed over to the system.

 

The main advantage of this kernelcache is that once it's created, it will always be there and available to boot from. Problem kexts won't get included, because they have to be parsed, verified and linked first, and that seems to only reliably happen when the system is running in Lion. So, if they fail that process, it doesn't get included in the kernelcache and, therefore, doesn't create booting problems. No more will you need to delete a cache, because it fails to boot. The cache that is available for booting is the same cache that was in use when you were running the system. So, if the system was working, then the system will boot. It's a bit more complicated than that, but that's the basics.

 

kind regards,

MAJ

[d00d]

Yeah, odd version numbering. I noticed someone had posted the version number of the System.kext being 10.7

So, is it really the Lion kernel or is it just a version number slip?

`Darwin Kernel Version 10.7.0' in kernel.log would equate to 10.6.7.

This has been consistent in SL, L used 9.x.x.

[digital_dreamer]

`Darwin Kernel Version 10.7.0' in kernel.log would equate to 10.6.7.

This has been consistent in SL, L used 9.x.x.

You're right. I don't know what I was thinking.

Funny, when I saw that you posted here, I figured you would be correcting me about the kernel version. Ha!

 

MAJ

[VirusX]

Those using my short guide can update to 10.6.7 without issues. Remember to backup your ATI kexts if you use any.

Can confirm update to 10.6.7 was flawless (using CruiSAr's method). No need to touch/change/update anything. Just install the update, reboot, you're good to go! (my gfx card is nVidia)

Interesting tho, my kernel version is listed as 10.7.0

thanks you two. Just installed the update. Everything is fine. Have to update my sig now

[ClemsonJeeper]

I was wondering if anyone had experience with using an internal SATA 3 (6.0GB/s) card with a drive attached to it as the boot drive for OSX on this motherboard?

 

I'm currently running with a SSD (3GB/s interface) tied into the on-board SATA connectors, but am wanting to upgrade to a faster SSD this season and it seems all the new ones are 6GB/s interface drives, which means I need to get an add-on card to control them.

 

I was just wondering if there is any issue with getting OSX to boot up off a drive attached to a external add-on SATA card.

 

Likely the card I'm going to get is the Highpoint Rocket 620 PCI express card which (supposedly) is fully supported under OSX.

[Z4g0r]

You may find better answers to your graphics-related questions in the Graphics forum. I don't really have any answers, but others may chime in.

 

 

Looks like you are booted in, but with no graphics support. So close, but so far.

 

 

Yeah, odd version numbering. I noticed someone had posted the version number of the System.kext being 10.7

So, is it really the Lion kernel or is it just a version number slip?

<brain fart>

 

 

That's a very common KP. You'll just have to keep trying.

I keep my hand by the reset button each time I boot into Lion.

Edit: Wrong. I looked at that picture wrong. It looks like it's trying to load kexts, which it's not supposed to. It's supposed to load the kernelcache immediately, just like it would load a kernel before, but this time it already includes the kexts. No kext loading should appear. Make sure you are not using the -f flag (check boot plist), which forces system to reload kexts and dump boot cache.

 

There is a DUET based bootloader called [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] that can boot into Lion without the KP. Incorporating the [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] bootloader into the existing script was going to create more work that I wanted to get into (very different install procedures), especially when you consider that when the Chameleon solution was released, I would need to remove it. So, I opted to wait for the Chameleon version - more compatible, less work. However, I expected that the DF KP would be fixed shortly.

 

Keep in mind that this is the FIRST developer release, so don't expect too much at this time, whether from Apple or from the Chameleon team. Give it time and it'll all work out. Additionally, this is a DEVELOPER release and not for public consumption. So, we're on the bleeding, leading edge here trying a developer release on a PC. Changes are going to be needed to make this work smoothly.

 

FYI:

Lion doesn't boot from the kext cache (mkext file) anymore, so it doesn't look like we'll be creating them. Instead, we'll be booting from a pre-linked kernel or kernelcache. This is a cache that contains the binary of the kernel, plus the kexts. Makes booting even faster as the kexts have been parsed and linked to the kernel.

 

I don't know how the Chameleon team is going to handle this, as the kernelcache in the /System location changes based on the contents of S/L/E. I notice a compressed plist in that cache directory that contains the contents of /S/L/E and their paths. Perhaps it can be manipulated to include kexts in /Extra. Even so, it will get overwritten by the OS at some time. My best guess is that we'll be needing to install a pre-made kernelcache in /Extra for the bootloader to boot from, before it gets handed over to the system.

 

The main advantage of this kernelcache is that once it's created, it will always be there and available to boot from. Problem kexts won't get included, because they have to be parsed, verified and linked first, and that seems to only reliably happen when the system is running in Lion. So, if they fail that process, it doesn't get included in the kernelcache and, therefore, doesn't create booting problems. No more will you need to delete a cache, because it fails to boot. The cache that is available for booting is the same cache that was in use when you were running the system. So, if the system was working, then the system will boot. It's a bit more complicated than that, but that's the basics.

 

kind regards,

MAJ

 

Yep, i think i have a misalign because may cham is 2.0 RC3 r658b and is Darwinboot 5.0.132

i'm workn' on

 

PS: A good news from 1.6.7 : In the last update comes the support for a lot of new ATI Graphic Cards: ATI Radeon HD 5630, ATI Radeon HD 5670, ATI Radeon HD 5730, ATI Radeon HD 5770, ATI Radeon HD 5850, ATI Radeon HD 5870, AMD Radeon HD 6850, AMD Radeon HD 6870, AMD Radeon HD 6970

[scott_donald]

Yep, i think i have a misalign because may cham is 2.0 RC3 r658b and is Darwinboot 5.0.132

i'm workn' on

 

PS: A good news from 1.6.7 : In the last update comes the support for a lot of new ATI Graphic Cards: ATI Radeon HD 5630, ATI Radeon HD 5670, ATI Radeon HD 5730, ATI Radeon HD 5770, ATI Radeon HD 5850, ATI Radeon HD 5870, AMD Radeon HD 6850, AMD Radeon HD 6870, AMD Radeon HD 6970

 

 

interesting... so with 10.6.7 i would have to use kabyl boot file and have the 30 spins before booting???

 

HD5870 here...

[Z4g0r]

interesting... so with 10.6.7 i would have to use kabyl boot file and have the 30 spins before booting???

 

HD5870 here...

 

mmmhhh..

only way is to try with a clone partition ...

in the 10.6.7 those cards must be working..

i'm thinking to update mine 4870

[scott_donald]

mmmhhh..

only way is to try with a clone partition ...

in the 10.6.7 those cards must be working..

i'm thinking to update mine 4870

 

i have a test drive... will try it over the weekend when i have time...

[ZoroLives]

mmmhhh..

only way is to try with a clone partition ...

in the 10.6.7 those cards must be working..

i'm thinking to update mine 4870

I updated to 10.6.7. Two issues, First, my machine is hanging at reboot. Restart goes through all the kill process stuff, then it gets to a black screen, and it sits there... Finally I have to hit the hard restart button on the case. I have had this effect after running applejack and typing “R”, after booting into single user and typing “reboot” and after selecting restart from the menu (normal restart mode).

 

THe second problem that may or may not be related is I have no sound any longer. This may have been starting to happen intermittently before, not sure. I had a game that controls sound that may have had an impact. I have also been trying a new timer that has a separate sound control that was working the other day, and now nothing is working.

 

If anyone has insights or my observation helps others look at the restart problem, thanks.

[isirpaul]

Hi all, I have a problem with the 10.6.6 combo update, I tried to install it on a New hdd with 10.6.0 /Extra method with DSDT patched and sleepenabler 10.6.x booting with chameleon r700 or pci efi 10.6 but I always have KPs (com.Apple.driver.appleACPIPlayform

Dependency ioacpifamily iopcifamily) and after few seconds debugger called <double panic> backtrace continues..

I don't know why i have this kp, I tried to boot with pmversion=0/21, to' remove sleepenabler kext, to remove dsdt.aml.. Always same problem.. But the other hdd with 10.6.4 works like a charm.. How i can Fix that? Could you help me please? Thanks,

Paul

 

Ps my rig is in my signature, i7, ud5, 4870 toxic

[mangopeach]

Hi all

 

Thanks to DD script, my machine is working like a charm with OSX but I am planning to replace my video card (nvidia GT9500) with a new one which can perform Bluray playback (when running windows 7) with audio ouput on HDMI (so my home theater amplifier could decode HD audio streams)

 

The GT430/GT440 seems to be good choices for the job, but do they run fine with OSX as no "real mac" uses these cards. (The GT9500 was se same as the GT130 that Apple was using at this time in mac pro and iMacs)

 

With OSX, I need DVI and VGA output only (I am using 2 screens) as HDMI output will be used only on Windows

 

Do some of you own these cards ? Do they work flawlessly on OSX or do they require some hacking to work ?

 

Thanks

 

 

From all the banter over the past few weeks.. 10.6.7 has added native support for many modern AMD cards like the 6850/6870. I would skip nvidia for now.. especially with the crappy performance on the mac side.

[digital_dreamer]

isirpaul,

PM sent.

 

I updated to 10.6.7. Two issues, First, my machine is hanging at reboot. Restart goes through all the kill process stuff, then it gets to a black screen, and it sits there... Finally I have to hit the hard restart button on the case. I have had this effect after running applejack and typing “R”, after booting into single user and typing “reboot” and after selecting restart from the menu (normal restart mode).

 

THe second problem that may or may not be related is I have no sound any longer. This may have been starting to happen intermittently before, not sure. I had a game that controls sound that may have had an impact. I have also been trying a new timer that has a separate sound control that was working the other day, and now nothing is working.

 

If anyone has insights or my observation helps others look at the restart problem, thanks.

 

Make sure you have a restart kext installed, like OSXRestart.kext or OpenHaltRestart.kext. That should help with the rebooting issue.

 

As for the sound, if you were using a modified AppleHDA.kext that was installed in /System, it may have been overwritten in the 10.6.7 update. If, however, your sound issues are unrelated to the OS update, then it may have been affected by the other programs you mentioned. Have you checked the System Perferences/Sound/Output selection? Should be on "Internal Speakers" if you are using the green jack.

 

MAJ

[bbchucks]

so was 10.6.7 upgrade successful for ppl who use dd's script?

[NoskireFiel]

Hey guys, Im having a bit of trouble... I updated to 10.6.7 from 10.6.6 and now it wont boot at all, it wont even get to the boot loader screen. this is what I see: http://i.imgur.com/E1oFR.jpg

 

My hardware is as follows: Core i7 920, 7 hdds, nvidia 9800GTX+, 12gb 1066 ram, Gigabyte EX58-UD5 mobo on the latest bios version 13j (is it?) and im using the PCI-EFI 10.6 boot loader

 

I've tried to reset the bios and just enabled AHCI and try to get it to work but nothing. I tried to Spinrite the hard drive to see if it was somehow messed up but nothing either. Any ideas?

 

thanks in advance for any help

[tsunoo]

so was 10.6.7 upgrade successful for ppl who use dd's script?

no problem for me like a real mac

[bbchucks]

no problem for me like a real mac

 

what video card are u using?

 

any success with ati 4870 cards on 10.6.7?

[digital_dreamer]

Hey guys, Im having a bit of trouble... I updated to 10.6.7 from 10.6.6 and now it wont boot at all, it wont even get to the boot loader screen. this is what I see: http://i.imgur.com/E1oFR.jpg

 

My hardware is as follows: Core i7 920, 7 hdds, nvidia 9800GTX+, 12gb 1066 ram, Gigabyte EX58-UD5 mobo on the latest bios version 13j (is it?) and im using the PCI-EFI 10.6 boot loader

 

I've tried to reset the bios and just enabled AHCI and try to get it to work but nothing. I tried to Spinrite the hard drive to see if it was somehow messed up but nothing either. Any ideas?

 

thanks in advance for any help

Now, that's a new one.

Can you reinstall the bootloader and make sure a valid theme (at least "Default") is getting installed? Check the install.log during the install for anything amiss. You certainly can try the newer RC5 version, unless you depend on certain features netkas has in PC-EFI 10.6.

The contents in /Extra will be left unaltered during the install.

 

RE: picture

Are the two "blocks" the only thing that's visible? Do they stay that way?

 

best regards,

MAJ

[tsunoo]

what video card are u using?

 

any success with ati 4870 cards on 10.6.7?

NVidia 9800 GTX+ a very loud card but also a very apple compatible one :-)

[@ROBASEFR]

EX58-UD5 mobo on the latest bios version 13j (is it?)

 

Latest Bios is F13q !

 

http://www.station-drivers.com/page/gigabyte/ga-ex58-ud5.htm

 

Working for me since 10.6.5 and up.

 

By the way I have a lot of trouble going to 10.6.7 because of my ATI 4850 GC.

Going to try the Kabyl bootloader but not shure that supports my 4850 !

 

Thanks for your thoughts

[NoskireFiel]

Now, that's a new one.

Can you reinstall the bootloader and make sure a valid theme (at least "Default") is getting installed? Check the install.log during the install for anything amiss. You certainly can try the newer RC5 version, unless you depend on certain features netkas has in PC-EFI 10.6.

The contents in /Extra will be left unaltered during the install.

 

RE: picture

Are the two "blocks" the only thing that's visible? Do they stay that way?

 

best regards,

MAJ

 

I fixed it. The problem was the bootloader, I tried using netkas's PC-EFI 10.2 instead of 10.6 and it worked fine. After, it would kernel panic on boot... so I installed the kexts from your latest script (thanks a lot btw) and it booted perfectly fine.

 

In regards to the picture, yes it would stay like that indefinitely and yes, that was the only thing visible. In other occasions, when booting it would be an underscored backslash or forward slash.