105 replies to this topic

[MACOSX123]

Hi Donator, what is the version of your lion? 10.7.4? I have same card as yours, it is much appreciated that you can add your kext here for us to download. Thanks a lot in advance!!!!!

[mediamac]

Hi,
I am using Sapphire Radeon 6850 on ML GM and i cannot get it worked with duckweed and atiports 5.I get stucked at ntfs version name please help me.

[polkaholga]

what you mean with "stucked at ntfs version"
try connector infos from other framebuffers, the guide in post#1 gives detailed info about all aspects... can't be explained better

@MACOSX123:
i'm on 10.7.2 but won't be at home for at least another 3 weeks, so i don't have access to my rig.
Just follow the guide, it took me only 2-3 hours to find the working configurations....

[mediamac]

I have fixed using the Pciroot=1 and using DP3 ati kexts thanks all.

[fffeee]

I updated my system to Mountain Lion 10.8, had some real struggles with installation until I upgraded my Chameleon to the trunk from yesterday, deleted the ML Installation Disc's ATI6000Controller and booted with GraphicsEnabler=No.  

The system was essentially unusable due to how bad the video performance was (as expected), and I hit a wall quickly on making edits to the ATI kexts needed to create my custom personality again.

In the mean time I am using the ATISupport and the ATI6000Controller (with my customizations to the Duckweed personality) and ATIFramebuffer kexts I used in Lion and it's working great with full acceleration now.

Obviously this isn't ideal, but until I get around to creating a new personality in the ML kexts that's what I needed to do.  (The methods for creating those needs to be changed a bit too since the binary inside the bundle is not called ATI* anymore, but AMD*, so the ati-personality.pl script will certainly need to be updated to address that or else it will fail to locate the driver blob that contains the personality names.)

The hex edits that I had done to the ATIController in Lion are too different for me to eyeball, so I'll have to either change the script to find new offsets or wait for someone smarter to figure it out

[TH3L4UGH1NGM4N]

The hex edits themselves in the case for me never changed as I've been using the same perl script since Lion but I had to change the ATI part into AMD or else it certainly wouldn't find an ATI6000Controller as it no long exists.

[fffeee]

The values will be the same I'm sure but the offsets are different absolutely.

I'll be cranking on mine this week, I see that there is an updated personality dumper now that has some extra goodies now like being able to specify one kext bundle.

See: http://www.insanelym...c=249642&st=600

[Nanael]

did you know why there is a so big difference with osX and Windows with my 6870 1Gb? QWith Windows i Got 55fps with cinebench andd on osX i got 33 fps

[TH3L4UGH1NGM4N]

@fffeee Ah, never knew the offsets changed because I reapplied the same perl command with no noticeable  Just peeped the last post by zhell and his enhanced version of the perl script seems quite easier to use I might give it a go with some mods of my own and see.  How was the system performance after you did the edit?  Real sluggish with a high cpu usage or just sluggish alone?

@antaeusIt is because the gpus don't play the same way in both OSs, Apple has only began to really incorporate gpu acceleration whereas Windows had it going for a while.  It's like comparing Apples and Windows, they just aren't the same.

[Nanael]

@TH3L4UGH1NGM4N thx, so there is nothing to do?

[xDougz]

Hi, I tried the tutorial but didn't work ... :/
I have one of these XFX HD6850, mobo Z68X-UD3-B3, Intel i5 2500, 4GB 1333MHz RAM running Mountain Lion.

I've tried several other tutorials and boot flags like GraphicEnabler=Yes, AtiConfig=Duckweed/Uakari/Bulrushes, AtiPorts=4/5, Use Ati ROM, set the IOPCIMatch the info.plist and the ATIRadeonAcelerator ATI6000Controller.kext but without success.

If I boot with GraphicsEnabler=No it works, but the OS does not recognize the card and uses a 3 MB video card memory.

I don't know what else to do, someone help me? : D

Thanks and sorry for bad english ^ ^

[Nanael]

@xDougz, did you try PCIRootUID=1 and GraphicsEnabler=Yes ?

[xDougz]

antaeus, on 31 July 2012 - 07:01 AM, said:

@xDougz, did you try PCIRootUID=1 and GraphicsEnabler=Yes ?

Hey antaeus thanks for help, it's worked but it still using the 3MB video card.

I tried some boot configs combinations like Duckweed, AtiPorts=4 and when i use it don't work :/

[fffeee]

TH3L4UGH1NGM4N, on 30 July 2012 - 10:30 PM, said:

@fffeee Ah, never knew the offsets changed because I reapplied the same perl command

Heh, yeah, they're different for Duckweed at least.

I applied my edits to the ML ATI6000Controller kext, but couldn't get the windowserver to start up.  I didn't have time to troubleshoot so I'm back on my Lion kext until the weekend.

[jzhang18]

xDougz, on 31 July 2012 - 12:05 PM, said:

Hey antaeus thanks for help, it's worked but it still using the 3MB video card.

I tried some boot configs combinations like Duckweed, AtiPorts=4 and when i use it don't work :/

What's the model of your XFX HD6850?  ZNFC or ZCFC.

[xDougz]

jzhang18, on 02 August 2012 - 05:23 PM, said:

What's the model of your XFX HD6850?  ZNFC or ZCFC.

Hi jzhang18, the model is ZNFC.

[jzhang18]

xDougz, on 02 August 2012 - 07:39 PM, said:

Hi jzhang18, the model is ZNFC.

You are lucky, ZNFC works OOB. I am looking for someone's experience with ZCFC.

Sapphire HD 6850 vapor-x   looks like the same as   XFX 6850 ZCFC (2 mini DP, 2 DVI, 1 HDMI) .  If someone has successful story on Sapphire HD 6850 vapor-x with Lion, it will be really appreciated to share your experience here.

[xDougz]

jzhang18, on 03 August 2012 - 03:07 PM, said:

You are lucky, ZNFC works OOB. I am looking for someone's experience with ZCFC.

Sapphire HD 6850 vapor-x   looks like the same as   XFX 6850 ZCFC (2 mini DP, 2 DVI, 1 HDMI) .  If someone has successful story on Sapphire HD 6850 vapor-x with Lion, it will be really appreciated to share your experience here.

good to know but someone can explain to me what OOB means and how i do that?
sorry i'm newbie XD

[polkaholga]

xDougz, on 03 August 2012 - 04:36 PM, said:

good to know but someone can explain to me what OOB means and how i do that?
sorry i'm newbie XD

OOB ➜ Out Of the Box  

[lionheartk]

VCH888, on 31 December 2011 - 02:37 PM, said:

Thanks for the good guide (rewritten).  After I read this topic, I thought to get all working connectors of my PowerColor HD6870 (AX6870 1GBD5-2DH) last night.  Finally, I got all connectors today.

ATOM BIOS Rom:
SubsystemVendorID: 0x1787 SubsystemID: 0x2305
IOBaseAddress: 0x0000
Filename: B6A25BCA.HGZ
BIOS Bootup Message:
BARTS XT 1GB GDDR5 BIOS B6A25BCA.HGZ								  

PCI ID: 1002:6738
Connector at index 0
Type [@offset 44499]: DisplayPort (10)
Encoder [@offset 44503]: INTERNAL_UNIPHY2 (0x21)	---- DP1
i2cid [@offset 44627]: 0x90, OSX senseid: 0x1
Connector at index 1
Type [@offset 44509]: DisplayPort (10)
Encoder [@offset 44513]: INTERNAL_UNIPHY2 (0x21)	---- DP2
i2cid [@offset 44654]: 0x91, OSX senseid: 0x2
Connector at index 2
Type [@offset 44519]: HDMI-A (11)
Encoder [@offset 44523]: INTERNAL_UNIPHY1 (0x20)	 ---- HDMI
i2cid [@offset 44681]: 0x93, OSX senseid: 0x4
Connector at index 3
Type [@offset 44529]: DVI-D (3)
Encoder [@offset 44533]: INTERNAL_UNIPHY1 (0x20)	---- DVI 2
i2cid [@offset 44708]: 0x95, OSX senseid: 0x6
Connector at index 4
Type [@offset 44539]: DVI-I (2)
Encoder [@offset 44543]: INTERNAL_UNIPHY (0x1e)	---- DVI 1
i2cid [@offset 44745]: 0x94, OSX senseid: 0x5
Connector at index 5
Type [@offset 44549]: DVI-I (2)
Encoder [@offset 44553]: INTERNAL_KLDSCP_DAC1 (0x15)	---- DVI 1
i2cid [@offset 44745]: 0x94, OSX senseid: 0x5

Physical layout:

|__DVI 1__|  /_HDMI_\  |_DP2_|  |_DP1_|

|__DVI 2__|

Based on Chameleon Boot loader, it will use Duckweed as default when GraphicsEnabler is yes.  Duckweed supports DVI 1 + HDMI + DP1 + DP2 natively.  However, Dvi 2's not working at all.

Based on 10.7.2 combo update:

Personality: Duckweed
ConnectorInfo count in decimal: 4
Disk offset in decimal 523688
0000000 00  04  00  00  04  03  00  00  00  01  00  00  12  04  04  01
0000010 00  04  00  00  04  03  00  00  00  01  00  00  22  05  05  02
0000020 00  08  00  00  04  02  00  00  00  01  00  00  11  02  03  04
0000030 00  02  00  00  14  02  00  00  00  01  00  00  00  00  06  05
0000040

I looked personalities and got Gibba that is similar to Duckweed.  Gibba has 5 connectors while Duckweed has 4 connectors.  I booted with AtiConfig=Gibba and got DVI 1 and HDMI working.  So, I tried to change as following

from

Personality: Gibba
ConnectorInfo count in decimal: 5
Disk offset in decimal 523928
0000000 00  04  00  00  04  03  00  00  00  01  00  00  12  04  05  01
0000010 00  04  00  00  04  03  00  00  00  01  00  00  22  05  04  02
0000020 00  08  00  00  04  02  00  00  00  01  00  00  11  02  06  04
0000030 00  02  00  00  14  02  00  00  00  01  00  00  00  00  03  05
0000040 04  00  00  00  04  02  00  00  00  01  00  00  11  02  01  03
0000050

to

Personality: Gibba
ConnectorInfo count in decimal: 5
Disk offset in decimal 523928
0000000 00  04  00  00  04  03  00  00  00  01  00  00  12  04  04  01 ---- DP 1
0000010 00  04  00  00  04  03  00  00  00  01  00  00  22  05  05  02 ---- DP 2
0000020 00  08  00  00  04  02  00  00  00  01  00  00  11  02  06  04 ---- HDMI
0000030 00  02  00  00  14  02  00  00  00  01  00  00  00  00  03  05 ---- DVI 1
0000040 04  00  00  00  04  02  00  00  00  01  00  00  11  02  01  06 ---- DVI 2
0000050

Then, I could use combination of either DVI 1 + DVI 2 + DP 1 + DP 2 or DVI 1 + HDMI + DP 1 + DP 2 as maximum four connectors.  Also, I could use DVI 1 + DVI 2 or DP 1 + DVI 2 or DP 2 + DVI 2, for example. All connectors can be plugged and unplugged (detectable).

Note: DVI 2 will be disable when HDMI is active. I was using HexEdit to edit the personality. Using PowerColor active mini DisplayPort / DisplayPort to DVI adaptors.


----------------------------------------------------------------------------
Update: 2012-01-05
Another ATi HD5770 Sapphire vapor-x


Before patching:

Personality: Vervet
ConnectorInfo count in decimal: 4
Disk offset in decimal 485112
0000000 00 04 00 00 00 04 00 00 00 71 00 00 12 04 04 02  got black screen on DP2DVI
0000010 04 00 00 00 14 00 00 00 00 71 00 00 01 12 01 04
0000020 00 02 00 00 14 00 00 00 00 71 00 00 00 00 06 03
0000030 00 08 00 00 00 02 00 00 00 71 00 00 22 05 05 01
0000040


After patching

OK --- change only 71 to 01 for DP line
Personality: Vervet
ConnectorInfo count in decimal: 4
Disk offset in decimal 485112
0000000 00  04  00  00  00  04  00  00  00  01  00  00  12  04  04  02
0000010 04  00  00  00  14  00  00  00  00  71  00  00  01  12  01  04
0000020 00  02  00  00  14  00  00  00  00  71  00  00  00  00  06  03
0000030 00  08  00  00  00  02  00  00  00  71  00  00  22  05  05  01
0000040

Got maximum working three monitors properly.

DP2DVI + HDMI + DVI
DP2DVI + DVI + DVI
DP2DVI + DVI2VGA + DVI2V, etc.
must use DP to get the third monitor.
also
DP2DVI + HDMI
DP2DVI + DVI, etc

I tried this on AMD6000Controller on Mountain Lion GM, using a PowerColor just like yours, but the DVI2 port still wont work. Anyone have a clue on why?