Jump to content

[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos


4,696 posts in this topic

Recommended Posts

Are you running on a 4870?

Yep. The 4870 X2, actually.

Right now, it shows up in SP and I have all the resolutions, but no QE/CI.

I've added the device ID to ATI4800Controller.kext (0x94411002) and am using the older (1.6.6) ATIFramebuffer.kext and ATISupport.kext.

I haven't spent too much time on it.

 

MAJ

Link to comment
Share on other sites

Yep. The 4870 X2, actually.

Right now, it shows up in SP and I have all the resolutions, but no QE/CI.

I've added the device ID to ATI4800Controller.kext (0x94411002) and am using the older (1.6.6) ATIFramebuffer.kext and ATISupport.kext.

I haven't spent too much time on it.

 

MAJ

 

Just wait until netkas comes out with a exotic package for your card :). He already had one, but it seems that it caused a lot of kernel panics... so he doesn't recommend installing the package now and is searching for a fix. You can still try the old package though... but I wouldn't do it if I were you, just wait ;).

Link to comment
Share on other sites

Just wait until netkas comes out with a exotic package for your card :) . He already had one, but it seems that it caused a lot of kernel panics... so he doesn't recommend installing the package now and is searching for a fix. You can still try the old package though... but I wouldn't do it if I were you, just wait ;) .

Yeah, noticed he had one posted, but it's been struckthrough and pulled. I, also, noticed the KPs mentioned in the comments. LOL!

 

MAJ

Link to comment
Share on other sites

Thanks, do i just simply copy the dsdt.aml file from CruiSAR's guide? then reboot and pray? =)

 

In all honesty it really is as simple as it looks. You use his DSDT move/delete the kexts, and reboot. You can use DD's script to do it all actually, just stop before you make the DSDT with his script.

 

And as a side note there is a new version of fakesmc.kext out that shows fan speeds, NB temp and Gpu temp for many Gpu's. Over in d00ds thread its been modified to work with the ex58-ud5 boards. I'm actually using it now and its reporting great.

 

Here is the latest Rev thats been modified Fakesmc Post

 

And here is aschar1's explanation of how to implements it since it takes a little more care to install it Description. That being said, I've found that using DD's script and doing a combo build seems to work without having to do the process aschar1 says.

Link to comment
Share on other sites

using Crus' dsdt file, do i need the fakesmc.kext in /Extra/Stored_Kexts or /Extra/Stored_Kext/_For_System

 

right now i have no files but the fakesmc.kext in both locations..

 

also my S/L/E/ still contains PlatformUUID.kext, OpenHaltRestart.kext, NullCPUPowerManagement.kext and AppleIntelPIIXATA.kext...

can i remove those files from SLE ?

 

thanks!

Link to comment
Share on other sites

installed Crus' DSDT.aml file and worked fine under 10.6.3...after i updated to 10.6.4 using the combo updater...i'm not able to boot up to video...can only VNC into the box.

using ATI 4870 sapphire card.

 

anyone know what i need to do? any help is appreciated!

Link to comment
Share on other sites

installed Crus' DSDT.aml file and worked fine under 10.6.3...after i updated to 10.6.4 using the combo updater...i'm not able to boot up to video...can only VNC into the box.

using ATI 4870 sapphire card.

 

anyone know what i need to do? any help is appreciated!

Since your using an ATI card you probably still need the graphics card kext for your card you were using before.

Link to comment
Share on other sites

Since your using an ATI card you probably still need the graphics card kext for your card you were using before.

no luck =( i wasn't using any ATY kext or EVOEnabler.kext at the time of 10.6.3...i did have an old 10.6.2 LegacyATI kext on my 10.6.3 which i've copied back in but no luck..

 

my screen just goes to power save mode. =(

Link to comment
Share on other sites

And as a side note there is a new version of fakesmc.kext out that shows fan speeds, NB temp and Gpu temp for many Gpu's. Over in d00ds thread its been modified to work with the ex58-ud5 boards. I'm actually using it now and its reporting great.

 

Here is the latest Rev thats been modified Fakesmc Post

 

And here is aschar1's explanation of how to implements it since it takes a little more care to install it Description. That being said, I've found that using DD's script and doing a combo build seems to work without having to do the process aschar1 says.

Interesting post, read about it earlier on netkas' site but didnt want to try it cos of reported KP's and also I hate putting third party kext in S/L/E.

 

I think I will let this one lie

Link to comment
Share on other sites

I tried the New FakeSMC rev.171 +plugins on my Hack (GA-EX58-UD5)

 

and it works great !

** Updated to rev.190 !! **

 

Update to 10.6.4:

 

No problems at all !

 

 

I'm going to like updates !

 

:)

Link to comment
Share on other sites

So after updating from 10.6.3 with Crusair's dsdt file to 10.6.4, i'm getting a black screen, goes into PowerSave mode..and i'm only left to VNC into the PC.

 

I've tried adding my deviceID to ATI4800Controller kext

 

when i go into the software list this is what i get below for the ATI 4870 card.

ATI Radeon 4870 Series:

 

Name: ATY,Motmot

Type: display

Driver Installed: Yes

Bus: PCI

Slot: Slot-1

Vendor ID: 0x1002

Device ID: 0x9440

Subsystem Vendor ID: 0x174b

Subsystem ID: 0xe114

Revision ID: 0x0000

Link Width: x16

Link Speed: 2.5 GT/s

 

ATI Radeon 4870 Series:

 

Chipset Model: ATI Radeon 4870 Series

Type: GPU

Bus: PCIe

Slot: Slot-1

PCIe Lane Width: x16

VRAM (Total): 1024 MB

Vendor: ATI (0x1002)

Device ID: 0x9440

Revision ID: 0x0000

ROM Revision: 113-B7710C-176

EFI Driver Version: 01.00.318

Displays:

Display Connector:

Display Connector:

Link to comment
Share on other sites

So after updating from 10.6.3 with Crusair's dsdt file to 10.6.4, i'm getting a black screen, goes into PowerSave mode..and i'm only left to VNC into the PC.

 

I've tried adding my deviceID to ATI4800Controller kext

 

when i go into the software list this is what i get below for the ATI 4870 card.

ATI Radeon 4870 Series:

<snip>

It may be too late to ask, but are you using the older version of ATIFramebuffer.kext and ATISupport.kext? They should be 1.6.6, I think.

 

MAJ

Link to comment
Share on other sites

It may be too late to ask, but are you using the older version of ATIFramebuffer.kext and ATISupport.kext? They should be 1.6.6, I think.

 

MAJ

 

i think i'm using the ATIFramebuffer & ATISupport from 10.6.2...

so i should make sure it says: 1.6.6 ?could you PM me yours? =)

Link to comment
Share on other sites

It may be too late to ask, but are you using the older version of ATIFramebuffer.kext and ATISupport.kext? They should be 1.6.6, I think.

 

MAJ

just checked, all three files: ATI4800controller, Framebuffer and ATISupport where using 1.6.6...

those three do NOT boot up with 10.6.4...

 

anyone have ideas i can try to get the ati4870 to work with 10.6.4?

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Happy you got it working, sorry I couldnt be of any help as I have no experience of ATI GPU's

Link to comment
Share on other sites

Hello

Just upgraded to 10.6.4 via combo update and am using RealtekR1000SL for network and it has worked flawlessly since 10.6.4. Under 10.6.4 I cannot connect to afp shares, it sees them and bonjour is working but cannot connect, even if I try to connect manually to the afp ip address still not luck. Anyone have any ideas on how to fix this or what could be causing this? But smb share do work.

 

Thanks

rx7boy

Link to comment
Share on other sites

An update is posted on front page. :)

(six months is a long time, eh?)

 

MAJ

 

 

Hey MAJ,

 

Thanks for the update. Quick question: For those of us using v4.22 of your script, can we just immediately use this instead or do you recommend a clean install?

 

Thanks,

Hisham

Link to comment
Share on other sites

Hey MAJ,

 

Thanks for the update. Quick question: For those of us using v4.22 of your script, can we just immediately use this instead or do you recommend a clean install?

 

Thanks,

Hisham

it is safe: you don't need a clean install.

Link to comment
Share on other sites

Hello

Just upgraded to 10.6.4 via combo update and am using RealtekR1000SL for network and it has worked flawlessly since 10.6.4. Under 10.6.4 I cannot connect to afp shares, it sees them and bonjour is working but cannot connect, even if I try to connect manually to the afp ip address still not luck. Anyone have any ideas on how to fix this or what could be causing this? But smb share do work.

 

Thanks

rx7boy

 

 

Sorry I can't really help except to say that I can connect to afp shares using 10.6.4 and the realtek1000.

BTW I've noticed performance problems with half life under my nvidia 285 since. Apparently this is a know problem that will take new nvidia drivers to fix. (Steam are currently advising not to upgrade 10.6.4)

Jon

Link to comment
Share on other sites

Hey MAJ,

 

Thanks for the update. Quick question: For those of us using v4.22 of your script, can we just immediately use this instead or do you recommend a clean install?

 

Thanks,

Hisham

 

 

it is safe: you don't need a clean install.

 

As tsunoo said, it's safe.

Just make sure you consider the SleepEnabler.kext issue and, if the script contains a different set of kexts than what you are currently using, you may wish to remove them and place yours in their place.

 

Also, speaking of clean installs:

I really can't think of any situation where a clean install would ever be necessary or advantageous. Particularly in the case of a hackintosh, where there are just a few, if any, modified kexts installed in S/L/E, returning the system to a vanilla state is a simple task, provided my script was used to install them. The only other kexts are in /Extra, which not part of the OS install.

 

As far as the script is concerned, if one wishes to remove all modified kexts from S/L/E, they can simply remove all the kexts from /Stored_Kexts/_For_System and update boot caches. The script will then uninstall whatever kexts were previously in the _For_System folder and restore the original, vanilla versions.

 

Of course, this process ignores any installs that were made by other installers, like Kext Helper, and install packages like QE_CI_Exotic_cards installer, etc. These installers will actually replace the vanilla version when present with same name, so returning to a vanilla state will require digging for the original, vanilla kexts from the OS install packages. If there wasn't a vanilla version, you would need to know what that kext's name is/was to remove or uninstall it.

 

The script makes these modified kexts in S/L/E easy to spot:

1. If the kext has the same name as vanilla, the vanilla original gets renamed with a ".original" suffix (i.e. somename.kext.original), so that it can be tracked by script if one wishes to uninstall it (find the kext with ".original" suffix, remove kext without the ".original" suffix, then rename original by removing ".original" suffix).

2. If there is no kext in S/L/E with same name, a duplicate is made with ".duplicate" suffix (i.e. somename.kext.duplicate), again, so that it can be tracked by the script if one wishes to uninstall it (find the kext with ".duplicate" suffix and remove that and kext without ".duplicate" suffix).

 

best of wishes,

MAJ

Link to comment
Share on other sites

Also, speaking of clean installs:

I really can't think of any situation where a clean install would ever be necessary or advantageous. Particularly in the case of a hackintosh, where there are just a few, if any, modified kexts installed in S/L/E, returning the system to a vanilla state is a simple task, provided my script was used to install them. The only other kexts are in /Extra, which not part of the OS install.

 

I forgot this from your first article ("Update boot caches (menu #6)"). I updated and removed the special AppleHDA from System (if I remember good) but it was always started! It was weird! :D Rebuilding ALL the caches (combo, system and normal) removed this ghost. And now the sound is perfectly intergrated without kext, using d00d solution (and your script!)

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

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?

Link to comment
Share on other sites

Thanks tsunoo, MAJ!

 

 

 

As tsunoo said, it's safe.

Just make sure you consider the SleepEnabler.kext issue and, if the script contains a different set of kexts than what you are currently using, you may wish to remove them and place yours in their place.

 

Also, speaking of clean installs:

I really can't think of any situation where a clean install would ever be necessary or advantageous. Particularly in the case of a hackintosh, where there are just a few, if any, modified kexts installed in S/L/E, returning the system to a vanilla state is a simple task, provided my script was used to install them. The only other kexts are in /Extra, which not part of the OS install.

 

As far as the script is concerned, if one wishes to remove all modified kexts from S/L/E, they can simply remove all the kexts from /Stored_Kexts/_For_System and update boot caches. The script will then uninstall whatever kexts were previously in the _For_System folder and restore the original, vanilla versions.

 

Of course, this process ignores any installs that were made by other installers, like Kext Helper, and install packages like QE_CI_Exotic_cards installer, etc. These installers will actually replace the vanilla version when present with same name, so returning to a vanilla state will require digging for the original, vanilla kexts from the OS install packages. If there wasn't a vanilla version, you would need to know what that kext's name is/was to remove or uninstall it.

 

The script makes these modified kexts in S/L/E easy to spot:

1. If the kext has the same name as vanilla, the vanilla original gets renamed with a ".original" suffix (i.e. somename.kext.original), so that it can be tracked by script if one wishes to uninstall it (find the kext with ".original" suffix, remove kext without the ".original" suffix, then rename original by removing ".original" suffix).

2. If there is no kext in S/L/E with same name, a duplicate is made with ".duplicate" suffix (i.e. somename.kext.duplicate), again, so that it can be tracked by the script if one wishes to uninstall it (find the kext with ".duplicate" suffix and remove that and kext without ".duplicate" suffix).

 

best of wishes,

MAJ

Link to comment
Share on other sites

 Share

×
×
  • Create New...