Jump to content
fantomas1

Radeon HD 6770 FULL QE/CI ML/Mavericks/Yosemite/ElCapitan/Sierra

116 posts in this topic

Recommended Posts

------------------------

Update - 06.15.2016

------------------------

 

A minor update of this topic - Clover (r3561) patch on the fly works fine with macOS 10.12 Sierra.

 

 sierra.png

 


 

------------------------

Update - 08.18.2015

------------------------

 

ok

 

with Download-Fritz help, I’m finally able to patch my kexts with new method.

 

post-193719-0-96031100-1439918159_thumb.

 

it works fine with Clover r3259 + DB6

 

but in my case, I still have to use FakeSMC trick... I tried with ForceKextsToLoad feature but it didn’t work... not yet.

 


------------------------

Update - 08.17.2015

------------------------

 

Hi there!   :D

 

almost a year later, I'm about to update this topic, not because I was too lazy to do it but just because the "patch on the fly" method  has a little bit changed since Clover r3154  and which I was not able to make work.

 

not really happy with being unable to use this method, I decided to do some tests with older versions of OS X and Clover... Bla bla bla... bla bla Bla...

 

3758281-9136397911-8hour.JPG

 

 

 

... as I expected, the old method still work... and it works fine with ElCapitan DB1   :D

 

Capture d’écran 2015-08-17 à 16.31.24.png

 

 

 

fantomas1s-iMac:~ fantomas1$ kextstat | grep AMD

   54    2 0xffffff7f81f26000 0x125000   0x125000   com.apple.kext.AMDSupport (1.3.6) C96B4426-D45A-3988-8F77-D0599ABD7351
   55    0 0xffffff7f8208e000 0x5f0000   0x5f0000   com.apple.kext.AMD5000Controller (1.3.6) 243E5473-2D4E-364F-9039-1A31DF22125E
   94    0 0xffffff7f8288b000 0x45c000   0x45c000   com.apple.AMDRadeonX3000 (1.3.6) DBC4A87F-55D9-30A0-929F-A3F2D86DC6AD
   97    0 0xffffff7f82059000 0x22000    0x22000    com.apple.kext.AMDFramebuffer (1.3.6) 460D6D27-72F8-3EFE-8879-23EF4CAE4F55
fantomas1s-iMac:~ fantomas1$ ioreg | grep ATY
    | |   |   | +-o ATY,Hoolock@0  
    | |   |   | | +-o ATY_Hoolock  
    | |   |   | +-o ATY,Hoolock@1  
    | |   |   | | +-o ATY_Hoolock  
    | |   |   | +-o ATY,Hoolock@2  
    | |   |   | | +-o ATY_Hoolock  

 
I even was able to install ElCapitan with Clover r2850 and boot well on it   :)
 
 Capture d’écran 2015-08-17 à 16.36.15.png
 
but to have success with it, the most effective trick for now is to inject the details of my kexts (AMD5000Controller.kext and AMDRadeonX3000.kext) inside the FakeSMC Info.plist as additional IOKitPersonalities. With this trick, my kexts are always loaded.

 

bc_url" href="http://www.apple.com/DTDs/PropertyList-1.0.dtd" title="External link">http://www.apple.com...yList-1.0.dtd">
BuildMachineOSBuild
13D65
CFBundleDevelopmentRegion
English
CFBundleExecutable
FakeSMC
CFBundleIdentifier
org.netkas.driver.FakeSMC
CFBundleInfoDictionaryVersion
6.0
CFBundleName
FakeSMC
CFBundlePackageType
KEXT
CFBundleShortVersionString
6.9.1315
CFBundleSignature
????
CFBundleVersion
1315
DTCompiler
com.apple.compilers.llvm.clang.1_0
DTPlatformBuild
5B1008
DTPlatformVersion
GM
DTSDKBuild
12F37
DTSDKName
macosx10.8
DTXcode
0511
DTXcodeBuild
5B1008
IOKitPersonalities
AMDBartsGraphicsAccelerator
ATIEnableWideBlitSupport
ATIUseTearingWideBlit
CFBundleIdentifier
com.apple.AMDRadeonX3000
GpuDebugPolicy
0
IOClass
AMDBartsGraphicsAccelerator
IODVDBundleName
AMDRadeonVADriver
IOKitDebug
0
IOMatchCategory
IOAccelerator
IOPCIMatch
0x67381002 0x67391002 0x67201002 0x67221002
IOProbeScore
200
IOProviderClass
IOPCIDevice
IOSourceVersion
0.0.0.0.0
IOVARendererID
16908288
AMDCaicosGraphicsAccelerator
ATIEnableWideBlitSupport
ATIUseTearingWideBlit
CFBundleIdentifier
com.apple.AMDRadeonX3000
GpuDebugPolicy
0
IOClass
AMDCaicosGraphicsAccelerator
IODVDBundleName
AMDRadeonVADriver
IOKitDebug
0
IOMatchCategory
IOAccelerator
IOPCIMatch
0x67681002 0x67701002 0x67791002 0x67601002 0x67611002
IOProbeScore
200
IOProviderClass
IOPCIDevice
IOSourceVersion
0.0.0.0.0
IOVARendererID
16908288
AMDCaymanGraphicsAccelerator
ATIEnableWideBlitSupport
ATIUseTearingWideBlit
CFBundleIdentifier
com.apple.AMDRadeonX3000
GpuDebugPolicy
0
IOClass
AMDCaymanGraphicsAccelerator
IODVDBundleName
AMDRadeonVADriver
IOKitDebug
0
IOMatchCategory
IOAccelerator
IOPCIMatch
0x67181002 0x67191002 0x67041002
IOProbeScore
200
IOProviderClass
IOPCIDevice
IOSourceVersion
0.0.0.0.0
IOVARendererID
16908288
AMDCedarGraphicsAccelerator
ATIEnableWideBlitSupport
ATIUseTearingWideBlit
CFBundleIdentifier
com.apple.AMDRadeonX3000
GpuDebugPolicy
0
IOClass
AMDCedarGraphicsAccelerator
IODVDBundleName
AMDRadeonVADriver
IOKitDebug
0
IOMatchCategory
IOAccelerator
IOPCIMatch
0x68E01002
IOProbeScore
200
IOProviderClass
IOPCIDevice
IOSourceVersion
0.0.0.0.0
IOVARendererID
16908288
AMDCypressGraphicsAccelerator
ATIEnableWideBlitSupport
ATIUseTearingWideBlit
CFBundleIdentifier
com.apple.AMDRadeonX3000
GpuDebugPolicy
0
IOClass
AMDCypressGraphicsAccelerator
IODVDBundleName
AMDRadeonVADriver
IOKitDebug
0
IOMatchCategory
IOAccelerator
IOPCIMatch
0x68981002 0x68991002
IOProbeScore
200
IOProviderClass
IOPCIDevice
IOSourceVersion
0.0.0.0.0
IOVARendererID
16908288
AMDJuniperGraphicsAccelerator
ATIEnableWideBlitSupport
ATIUseTearingWideBlit
CFBundleIdentifier
com.apple.AMDRadeonX3000
GpuDebugPolicy
0
IOClass
AMDJuniperGraphicsAccelerator
IODVDBundleName
AMDRadeonVADriver
IOKitDebug
0
IOMatchCategory
IOAccelerator
IOPCIMatch
0x68B81002 0x68B01002 0x68B11002 0x68A01002 0x68A11002
IOProbeScore
200
IOProviderClass
IOPCIDevice
IOSourceVersion
0.0.0.0.0
IOVARendererID
16908288
AMDLombokGraphicsAccelerator
ATIEnableWideBlitSupport
ATIUseTearingWideBlit
CFBundleIdentifier
com.apple.AMDRadeonX3000
GpuDebugPolicy
0
IOClass
AMDLombokGraphicsAccelerator
IODVDBundleName
AMDRadeonVADriver
IOKitDebug
0
IOMatchCategory
IOAccelerator
IOPCIMatch
0x68401002 0x68411002
IOProbeScore
200
IOProviderClass
IOPCIDevice
IOSourceVersion
0.0.0.0.0
IOVARendererID
16908288
AMDRedwoodGraphicsAccelerator
ATIEnableWideBlitSupport
ATIUseTearingWideBlit
CFBundleIdentifier
com.apple.AMDRadeonX3000
GpuDebugPolicy
0
IOClass
AMDRedwoodGraphicsAccelerator
IODVDBundleName
AMDRadeonVADriver
IOKitDebug
0
IOMatchCategory
IOAccelerator
IOPCIMatch
0x68D81002 0x68C01002 0x68C11002 0x68D91002
IOProbeScore
200
IOProviderClass
IOPCIDevice
IOSourceVersion
0.0.0.0.0
IOVARendererID
16908288
AMDTurksGraphicsAccelerator
ATIEnableWideBlitSupport
ATIUseTearingWideBlit
CFBundleIdentifier
com.apple.AMDRadeonX3000
GpuDebugPolicy
0
IOClass
AMDTurksGraphicsAccelerator
IODVDBundleName
AMDRadeonVADriver
IOKitDebug
0
IOMatchCategory
IOAccelerator
IOPCIMatch
0x67501002 0x67581002 0x67591002 0x67401002 0x67411002 0x67451002
IOProbeScore
200
IOProviderClass
IOPCIDevice
IOSourceVersion
0.0.0.0.0
IOVARendererID
16908288
Controller
ATY,Hoolock
aty_config
CFG_FORCE_ICLK
ATY,Langur
aty_config
CFG_FORCE_ICLK
ATY,Orangutan
aty_config
CFG_GPIO_HIGH
131104
ATY,Zonalis
aty_config
CFG_NO_PP
CFBundleIdentifier
com.apple.kext.AMD5000Controller
IOClass
AMD5000Controller
IOMatchCategory
IOFramebuffer
IOName
AMD5000Controller
IOPCIMatch
0x68981002 0x68991002 0x68E01002 0x68E11002 0x68D81002 0x68C01002 0x68C11002 0x68D91002 0x68B81002 0x68B01002 0x68B11002 0x68A01002 0x68A11002
IOProbeScore
65050
IOProviderClass
IOPCIDevice
aty_config
CFG_NO_PP
aty_properties
PP_ActivitySamplingInterval
1000
PP_DisableMCDownLoadFeature
1
PP_HighSamplingInterval
200000
PP_R600ActivityHysteresis
5
PP_R600LoweringHighPercentage
25
PP_R600LoweringMediumPercentage
10
PP_R600RaisingLowPercentage
10
PP_R600RaisingMediumPercentage
25
PP_UserMaxClockForMultiDisplays
1
                FakeSMC
CFBundleIdentifier
org.netkas.driver.FakeSMC
Configuration
Clover
BEMB
BEMB
flag
EPCI
EPCI
ui32
RBr
RBr
ch8*
REV
REV
{rev
RPlt
RPlt
ch8*
Keys
$Adr
ui32
AAADAA==
$Num
ui8
AQ==
FNum
ui8
AA==
LsNM
ui8
AQ==
LsbV
{rev
AQQKAAY=
MSSD
si8
BQ==
MSSP
si8
BQ==
NATJ
ui8
AA==
OSK0
ch8*
b3VyaGFyZHdvcmtieXRoZXNld29y
ZHNndWFyZGVkcGw=
OSK1
ch8*
ZWFzZWRvbnRzdGVhbChjKUFwcGxl
Q29tcHV0ZXJJbmM=
REV
{rev
ATAPAAAD
RVBF
{rev
ATAPAAAD
RVUF
{rev
ATAPAAAD
Types
BEMB
flag
CLKC
{clc
CLKH
{clh
CLKT
ui32
CLWK
ui32
EPCI
flag
LSSS
{lso
MSDS
ui8
MSDW
flag
MSPS
{msp
RPlt
ch8*
debug
smc-compatible
smc-napa
trace
IOClass
FakeSMC
IOMatchCategory
FakeSMC
IOProviderClass
AppleACPIPlatformExpert
IOResourceMatch
FakeSMCKeyStore
FakeSMCKeyStore
CFBundleIdentifier
org.netkas.driver.FakeSMC
IOClass
FakeSMCKeyStore
IOMatchCategory
FakeSMCKeyStore
IOProviderClass
IOResources
IOResourceMatch
IOKit
IOUserClientClass
FakeSMCKeyStoreUserClient
NSHumanReadableCopyright
Copyright © 2014 netkas. All rights reserved.
OSBundleCompatibleVersion
1212
OSBundleLibraries
com.apple.iokit.IOACPIFamily
1.0.0d1
com.apple.kpi.bsd
10.6
com.apple.kpi.iokit
10.6
com.apple.kpi.libkern
10.6
com.apple.kpi.mach
10.6
com.apple.kpi.unsupported
10.6
OSBundleRequired
Root

 
with the standard loading method, the patch doesn't work   :(
 

 

 

 

------------------------

Update - 08.27.2014

------------------------

 

Clover's KernelAndKextPatches tweak still works fine on OS X 10.10 DP's, PB's and OS X 10.9.x, nothing changed in the patch.

 

If there's something new, this topic will be updated.

 


------------------------

Update - 08.21.2014

------------------------

 

Clover's KernelAndKextPatches tweak still works fine on OS X 10.10 Public Beta 2

 


------------------------

Update - 08.18.2014

------------------------

 

Clover's KernelAndKextPatches tweak works fine on OS X 10.10 DP6

 


------------------------

Update - 08.14.2014

------------------------

 

Clover's KernelAndKextPatches tweak works fine on OS X 10.9.5 Build 13F14

 


 

------------------------

Update - 08.04.2014

------------------------

 

Clover's KernelAndKextPatches tweak works fine on OS X 10.10 DP5

 


 

------------------------

Update - 07.31.2014

------------------------

 

Clover's KernelAndKextPatches tweak works fine on OS X 10.9.5 Build 13F7

 


 

------------------------

Update - 07.24.2014

------------------------

 

Clover's KernelAndKextPatches tweak still works fine on OS X 10.10 Public Beta

 


 

 

------------------------

Update - 07.21.2014

------------------------

 

Clover's KernelAndKextPatches tweak still works fine on OS X 10.10 DP4

 


 

 

------------------------

Update - 07.08.2014

------------------------

 

Clover's KernelAndKextPatches tweak still works fine on OS X 10.10 DP3

 


 

 

------------------------

Update - 06.17.2014

------------------------

 

Clover's KernelAndKextPatches tweak still works fine on OS X 10.10 DP2

 


 

------------------------

Update - 06.02.2014

------------------------

 

Clover's KernelAndKextPatches tweak still works fine on OS X 10.10 DP1

 

the proof:

 

HD6770_QECI_Yos_Clover.png

 


 

------------------------

Update - 03.31.2014

------------------------

 

I can confirm, we never needed those 3 kexts, only 2 of them are enough (ATI5000Controller.kext and AMDRadeonAccelerator.kext for ML) to enable QE_CI for HD 6770 cards on Mountain Lion and Mavericks!!!

 

the proof:

 

HD6770_QECI_ML_Clover.png

 

 

 


 

------------------------

Update - 03.28.2014

------------------------

 

just to tell that since Mavericks, we need no more those 3 kexts, only 2 of them (AMD5000Controller.kext and AMDRadeonX3000.kext) to enable QE_CI for HD6770 cards

 

even if you use those 3 kexts, AMD6000Controller.kext will not be loaded

 

626807AMDkextsloading.png

 

to do this with chameleon, use GraphicsEnabler=Yes and edit 0x68B81002 -> 068BA1002 in both kexts

 

if you want to do this with clover, use clover configurator and KernelAndKextPatches tweak:

 

515400KernelAndKextPatches.png

 

don't forget to put 'Inject Kexts' to 'Yes'

 

154119Injectkexts.png

 

if it does not work, it is because the kexts are not presents in kernel cache. 

 

The most effective trick for now is to inject the details of your kexts inside the FakeSMC Info.plist as additional IOKitPersonalities. With this trick, your kexts will be always loaded.

 

I did it with QE_CI Exotic patch for HD48xx series cards with my old HD4830 and it works!

 

see here for more details: http://www.insanelymac.com/forum/topic/296949-tuto-qe-ci-exotic-patch-via-clover/

 

p.s:

 

here, more screens

 

370434HD6770QECIwithClover.png

 

452323HD6770MavericksOpenGL41fullsupport

 

 

Method 3: if you're using Clover, you can make this card work with a Fake ID injection

<key>Devices</key>
<dict>
        <key>FakeID</key>
        <dict>
            <key>ATI</key>
            <string>0x68B81002</string>
        </dict>
</dict>


 

Method 2: since OS X 10.8, you no longer have to edit those kexts, just inject your ID via dsdt: http://www.insanelymac.com/forum/topic/282687-radeon-hd-6770-full-qeci-mountain-lion/?p=1902721 (credits go to RampageDev)

 

*This method also works very well with OS X Mavericks
 
 

 
 

Method 1: i can confirm it, with the last Chameleon-2.1svn-r2054.pkg, it work well on 10.8.2 Build 12C43 !!! :thumbsup_anim:

No more need to flashing HD 6770 into HD 5770 to have QE/CI !!!

So just add your ID (0x68BA1002) into ATI5000Controller.kext and AMDRadeonAccelerator.kext
 

<key>AMDJuniperGraphicsAccelerator</key>
<dict>
*
*
*
<key>IOPCIMatch</key>
<string>0x68BA1002 0x68B81002 0x68B01002 0x68B11002 0x68A01002 0x68A11002</string>

hd6770fullqecimountainl.png

 

 

 

 

* the story started with this original topic

Edited by fantomas1
topic updated!

Share this post


Link to post
Share on other sites
Advertisement

unfortunately not !

 

there's no AMDRadeonAccelerator.kext in OS X Lion

 

I was tried with ATIConnector patching but it's not the way to have QE/CI enabled. I think it needs to patching the binaries parts, but i haven't be able to do it yet! :(

Share this post


Link to post
Share on other sites

Thought that you could add the DSDT injection code:

 

Device (PEGP)

{

Name (_ADR, 0x00010000)

Method (_PRW, 0, NotSerialized)

{

Return (GPRW (0x09, 0x04))

}

Device (GFX0)

{

Name (_ADR, Zero)

Method (_DSM, 4, NotSerialized)

{

Store (Package (0x10)

{

 

"AAPL,slot-name",

Buffer (0x07)

{

"Slot-1"

},

"@0,name",

Buffer (0x0D)

{

"ATY,

Juniper

"

},

"@1,name",

Buffer (0x0D)

{

"ATY,

Juniper

"

},

"@2,name",

Buffer (0x0D)

{

"ATY,

Juniper

"

},

"@3,name",

Buffer (0x0D)

{

"ATY,

Juniper

"

},

"@4,name",

Buffer (0x0D)

{

"ATY,

Juniper

"

},

"model",

Buffer (0x13)

{

"AMD Radeon HD 6770"

},

"hda-gfx",

Buffer (0x0A)

{

"onboard-1"

}

}, Local0)

DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))

Return (Local0)

}

}

Device (HDAU)

{

Name (_ADR, One)

Method (_DSM, 4, NotSerialized)

{

Store (Package (0x04)

{

 

"name",

Buffer (0x0B)

{

"HDMI Audio"

},

"hda-gfx",

Buffer (0x0A)

{

"onboard-1"

}

}, Local0)

DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))

Return (Local0)

}

}

 

}

Share this post


Link to post
Share on other sites

I'm sorry for reviveing this thread,but i want my GPU to be detected as a HD6770 again.

How can i edit the kexts? and add 0x68BA1002 to them?

 

Bitcore

Share this post


Link to post
Share on other sites

I'm sorry for reviveing this thread,but i want my GPU to be detected as a HD6770 again.

How can i edit the kexts? and add 0x68BA1002 to them?

 

Bitcore

 

 

hey bro you have AMD cpu do you have amd kernel for ML then please give me.................

 

Hi !

 

i just saw that : http://www.osx86.net...ntain_lion.html

 

according to the testimonies, it works well!

 

I also have a HD6770 I flashed into HD5770, but I didn't have time to try it!

 

I will do it in a few minutes!

 

Tell me if it works for you!

 

Good luck !

 

 

EDIT: i can confirm it, with the last Chameleon-2.1svn-r2054.pkg, it work well on 10.8.2 Build 12C43 !!! :thumbsup_anim:

 

No more need to flashing HD 6770 into HD 5770 to have QE/CI !!!

 

So just add your ID (0x68BA1002) into ATI5000Controller.kext, ATI6000Controller.kext and AMDRadeonAccelerator.kext

 

 

<key>AMDJuniperGraphicsAccelerator</key>

<dict>

<key>ATIEnableWideBlitSupport</key>

<true/>

<key>ATIUseTearingWideBlit</key>

<false/>

<key>CFBundleIdentifier</key>

<string>com.apple.AMDRadeonAccelerator</string>

<key>GpuDebugPolicy</key>

<integer>0</integer>

<key>IOClass</key>

<string>AMDJuniperGraphicsAccelerator</string>

<key>IODVDBundleName</key>

<string>AMDRadeonVADriver</string>

<key>IOKitDebug</key>

<integer>0</integer>

<key>IOMatchCategory</key>

<string>IOAccelerator</string>

<key>IOPCIMatch</key>

<string>0x68BA1002 0x68B81002 0x68B01002 0x68B11002 0x68A01002 0x68A11002</string>

 

 

 

hd6770fullqecimountainl.png

 

 

What to for the HD Redeon 6770m 2GB graphics for laptop ?

Share this post


Link to post
Share on other sites

Hi,

with the upcoming 10.8.3 release I would like to ask, if a method exits to inject the device id into the system instead of editing the plists again.

 

cheers

Share this post


Link to post
Share on other sites

I don't think so

 

GraphicsEnabler injects the info of your graphics card but for this one, it isn't enough

 

the DSDT method doesn't works, this is the only way to get this card work (as hd6770) under ML

 

at the same time, it's not so hard to put your ID into the Info.plist, it takes 2 minutes -_-

Share this post


Link to post
Share on other sites
Thought it might be possible with some sort of legacy kext.

 

not sure it's possible

 

HD6770 needs to have its ID into the 3 kexts, not just one :)

 

 

only possibility, that Apple put directly ID into these kexts :P

 

there we would have a graphics card recognized OOB :D

Share this post


Link to post
Share on other sites

Hi,fantomas1 Can you upload on this page all modified file for ati 6770?

thanks

 

You can just add them to the 2 ATI/AMD kexts. Drivers have changed since this was posted. Or what really should be done is for you to add a different device ID in the DSDT so that you never have to edit any kexts which would be the proper solution.

Share this post


Link to post
Share on other sites

hi the -hackintosh :)

 

pls see the initial post :)

 

tell me if there's something that you don't understand

 

 

You can just add them to the 2 ATI/AMD kexts. Drivers have changed since this was posted. Or what really should be done is for you to add a different device ID in the DSDT so that you never have to edit any kexts which would be the proper solution.

 

this method still works good with all 10.8's updates, don't worry, just add your ID to this 3 kexts.

 

the DSDT method doesn't do all, on this card it's not enough. This is the only way to get this card work (as hd6770) under ML

 

:)

Share this post


Link to post
Share on other sites

hi the -hackintosh :)

 

pls see the initial post :)

 

tell me if there's something that you don't understand

 

 

 

 

this method still works good with all 10.8's updates, don't worry, just add your ID to this 3 kexts.

 

the DSDT method doesn't do all, on this card it's not enough. This is the only way to get this card work (as hd6770) under ML

 

:)

 

Why does not changing the device ID in the DSDT not work for this card? Thanks.

Share this post


Link to post
Share on other sites

I'm not sure, it's pretty bizarre

 

HD6770 is an authentically HD5770 card, only ID's differ (0x68BA1002 / 0x68B81002)

 

if we follow this logic, there's only need to add HD6770 ID to ATI6000Controller.kext or ATI5000Controller.kext + AMDRadeonAccelerator.kext

 

but strangely, this card has to call these both kexts to work perfectly

 

So because of this "call" to these both kexts in the same time, the dsdt method has no effect

 

I know, it can appears as a wacky explanation, but I don't see nothing else

 

IMHO

Share this post


Link to post
Share on other sites

Got it working using this device id insert in dsdt.

Original kexts from 10.8.3 and GraphicsEnabler=Yes

 

Device (GFX0)

{

Name (_ADR, Zero)

Name (_SUN, One)

Method (_DSM, 4, NotSerialized)

{

Store (Package (0x02)

{

"device-id",

Buffer (0x04)

{

0xB8, 0x68, 0x00, 0x00

}

}, Local0)

DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))

Return (Local0)

}

 

In my DSDT I had to insert the above at P0P2

post-52582-0-24533500-1363680055_thumb.jpg

post-52582-0-21128600-1363680066_thumb.png

Share this post


Link to post
Share on other sites

Hi !

 

i just saw that : http://www.osx86.net...ntain_lion.html

 

according to the testimonies, it works well!

 

I also have a HD6770 I flashed into HD5770, but I didn't have time to try it!

 

I will do it in a few minutes!

 

Tell me if it works for you!

 

Good luck !

 

 

EDIT: i can confirm it, with the last Chameleon-2.1svn-r2054.pkg, it work well on 10.8.2 Build 12C43 !!! :thumbsup_anim:

 

No more need to flashing HD 6770 into HD 5770 to have QE/CI !!!

 

So just add your ID (0x68BA1002) into ATI5000Controller.kext, ATI6000Controller.kext and AMDRadeonAccelerator.kext

 

 

<key>AMDJuniperGraphicsAccelerator</key>

<dict>

<key>ATIEnableWideBlitSupport</key>

<true/>

<key>ATIUseTearingWideBlit</key>

<false/>

<key>CFBundleIdentifier</key>

<string>com.apple.AMDRadeonAccelerator</string>

<key>GpuDebugPolicy</key>

<integer>0</integer>

<key>IOClass</key>

<string>AMDJuniperGraphicsAccelerator</string>

<key>IODVDBundleName</key>

<string>AMDRadeonVADriver</string>

<key>IOKitDebug</key>

<integer>0</integer>

<key>IOMatchCategory</key>

<string>IOAccelerator</string>

<key>IOPCIMatch</key>

<string>0x68BA1002 0x68B81002 0x68B01002 0x68B11002 0x68A01002 0x68A11002</string>

 

 

 

hd6770fullqecimountainl.png

 

Any thing for AMD 6770M 2GB laptop version Graphics Card ??????

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      Clover r5050 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r5050 for VMware.zip". Mount Clover-v2.5k-5050-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  AptioMemory --> (consigliato) ->  Link download
       Può essere solo aggiunto manualmente scaricando dal link sopra e collocandolo nella rispettiva cartella
       NOTA: in questo caso non selezionare nessun OsxAptioFixDRV durante l'installazione di clover oppure rimuovetelo                        successivamente. 
                               : Driver64UEFI  ApfsDriverLoader --> (consigliato) --> sostituisce l'uso del driver apfs.efi
                               : Selezionate l'altri driver come da successiva immagine,
       
      *Nota: Altri driver che si possono usare  al suo posto  sono:
       informazioni 
       
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione, nel caso può essere usato anche per effettuare aggiornamenti...
      nel caso guardate...
       Mojave in HFS 
       Oppure direttamente da usb  
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      C_I_M.zip
       
       
       
       
       
       
       
       
       
       
       
       
       
    • By fantomas1
      Hi InsanelyMacaholics   

      Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS Sierra.
       
      10.12.6
      Nvidia Web Driver - 378.05.05.25f18 --> build 16G2028 (thanks to Riley Freeman) New!
      Nvidia Web Driver - 378.05.05.25f16 --> build 16G2016 (thanks to Cyberdevs)
      Nvidia Web Driver - 378.05.05.25f15 --> build 16G1918 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f14 --> build 16G1917 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f13 --> build 16G1815 (thanks to flowrider)
      Nvidia Web Driver - 378.05.05.25f12 --> build 16G1710 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f11 --> build 16G1618 (thanks to Frank Nitty)
      Nvidia Web Driver - 378.05.05.25f10 --> build 16G1510 (thanks to BreBo) 
      Nvidia Web Driver - 378.05.05.25f09 --> build 16G1408 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f08 --> build 16G1314 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f07 --> build 16G1314 (thanks to haring)
      Nvidia Web Driver - 378.05.05.25f06 --> build 16G1212 (thanks to WeBeRiO)
      Nvidia Web Driver - 378.05.05.25f04 --> build 16G1114 (thanks to lukazm)
      Nvidia Web Driver - 378.05.05.25f03 --> build 16G1036 (thanks to Gradou)
      Nvidia Web Driver - 378.05.05.25f01 --> build 16G29 (thanks to Badruzeus)
       
       
      10.12.5
      Nvidia Web Driver - 378.05.05.15f01 --> build 16F73 (see this post)
       
       
      10.12.4
      Nvidia Web Driver - 378.05.05.05f02 --> build 16E195(thanks to crachmaster4999)
      Nvidia Web Driver - 378.05.05.05f01 --> build 16E195 (thanks to Moviemakergr)  Pascal support!!!
      Nvidia Web Driver - 367.15.10.45f01 --> build 16E195 (thanks to Lanc)
       
       
      10.12.3

      Nvidia Web Driver - 367.15.10.35f01 --> build 16D32 (thanks to shatterhenner)
       
       
      10.12.2
      Nvidia Web Driver - 367.15.10.25f02 --> build 16C68 (see this post)
      Nvidia Web Driver - 367.15.10.25f01 --> build 16C67 (see this post)
      Nvidia Web Driver - 367.15.10.25b06 --> build 16C60b/16C63a (see this post)
       
       
      10.12.1
      Nvidia Web Driver - 367.15.10.15f03 --> build 16B2657/16B2659 (thanks to Moviemakergr).
      Nvidia Web Driver - 367.15.10.15f01 --> build 16B2555 (thanks to Moviemakergr)
       
       
      10.12.0
      Nvidia Web Driver - 367.15.10.05f01 --> build 16A323 (thanks to phi777)
       
       
      GM
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A323 (same driver since DP4/PB3)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A322 (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A320 (see this post)
       
       
      DP/PB
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A313a (DP8 & PB7) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A304a (DP7 & PB6) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A294a (DP6 & PB5) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A286a (DP5 & PB4) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A270f (DP4 & PB3) (thanks to TheRacerMaster)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A254g (DP3 & PB2) (see this post)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A238m (PB1) (thanks to Faun) 
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A239j (DP2) (thanks to Faun)
      Nvidia Web Driver - 367.05.10.05b03 --> build 16A201w (DP1) (thanks to Xmedik)
       
    • By tragediana150
      Hi everyone!
      Long time no see guys!
      As you can see I am not new user of Insanely and do not want to post in incorrect section, but I can not find any similiar topic at all. I,ve searched the forum and the web and I can't find a solution.
      My question is that is there any possibility to install Mavericks 10.9.5 on external drive on the newest Macbook Pro 13 from 2018? I know that the Intel Coffee Lake is new generation of CPU's and there is no drivers in Mavericks system to run this CPU, but I was thinking about it alot and I decided to write here. Because if we can install all the newest OSX, macOS on older machines then maybe we can install older systems on newer builds?
       
      P.S. If I wrote in incorrect topic then please move this thread to the right section, I will be grateful
×