Jump to content

[Guide] Getting XFX HD6850 connectors to work


Alexander Martinez
 Share

112 posts in this topic

Recommended Posts

Thanks a lot, very informative topic.

Based on your guide i had a success :thumbsup_anim: with

ASUS EAH6850 DC/2DIS/1GD5/V2 1GB

Layout:

 

|__DVI-I__| /_HDMI_\ |_DP_|

 

|__DVI-D__|

 

In my case it was..

 

Personality: Duckweed

ConnectorInfo count in decimal: 4

Disk offset in decimal 176800

0000000 00 04 00 00 04 03 00 00 00 01 00 00 12 04 04 01

0000010 04 00 00 00 14 00 00 00 00 01 00 00 11 02 01 06

0000020 00 08 00 00 00 02 00 00 00 01 00 00 22 05 03 04

0000030 00 02 00 00 14 02 00 00 00 01 00 00 00 00 06 05

0000040

  • Like 1
Link to comment
Share on other sites

Thanks fffeee for a tip about relation between hot plug id an mouse lag (high cpu load from Windowserver) I was battling for three days with Asus EAH 6850 1GB with no luck in terms of getting rid of famous mouse lag, I was changing encoders etc but in the end - its all down to hot plug id. If you interested here is my Duckweed frame buffer witch works perfectly.

 

0000000 00 04 00 00 04 03 00 00 00 01 00 00 12 04 04 01

0000010 00 08 00 00 04 02 00 00 00 01 00 00 22 05 06 04

0000020 04 00 00 00 14 02 00 00 00 01 00 00 00 00 05 05

0000030 00 02 00 00 04 00 00 00 00 01 00 00 11 02 03 06

0000040

  • Like 1
Link to comment
Share on other sites

XFX 6850 --- I try to figure out why it does not work.

 

XFX 6850 ZNFC works OOB. 2 DVI ports work, HDMI also works

http://www.newegg.com/Product/Product.aspx?Item=N82E16814150505

Inserting XFX 6850 ZCFC, Nothing works, neither of 2 DVI, nor 2 mini DisplayPorts.

http://www.newegg.com/Product/Product.aspx?Item=N82E16814150573

 

The same company, what makes above 2 cards a huge difference to Apple Lion?

If someone has any suggestions, please give me a post

Really appreciated

Link to comment
Share on other sites

These are all 6850 cards, supported by latest Chameleon, (ati.c source code)

 

619 { 0x6739,0xAA881002, CHIP_FAMILY_BARTS,"AMD Radeon HD 6850",kDuckweed},

620 { 0x6739,0x03B41043, CHIP_FAMILY_BARTS,"AMD Radeon HD 6850",kDuckweed},

621 { 0x6739,0x21F81458, CHIP_FAMILY_BARTS,"AMD Radeon HD 6850",kBulrushes},

622 { 0x6739,0x24411462, CHIP_FAMILY_BARTS,"AMD Radeon HD 6850",kDuckweed},

623 { 0x6739,0x31101682, CHIP_FAMILY_BARTS,"AMD Radeon HD 6850",kDuckweed},

624 { 0x6739,0x67391002, CHIP_FAMILY_BARTS,"AMD Radeon HD 6850",kDuckweed},

625 { 0x6739,0xE177174B, CHIP_FAMILY_BARTS,"AMD Radeon HD 6850",kDuckweed},

 

XFX 6850 ZNFC is inside :623 { 0x6739,0x31101682, ...}

XFX 6850 ZCFC is not { 0x6739,0x31171682}

Link to comment
Share on other sites

This is XFX 6850 ZCFC Bios decoding information:

 

ATOM BIOS Rom:

SubsystemVendorID: 0x1682 SubsystemID: 0x3117

IOBaseAddress: 0x0000

Filename: 685XZCF4

BIOS Bootup Message:

BARTS PROH ELIPDA GDDR5 32Mx32 BIOS

 

PCI ID: 1002:6739

Connector at index 0

Type [@offset 44350]: DisplayPort (10)

Encoder [@offset 44354]: INTERNAL_UNIPHY2 (0x21)

i2cid [@offset 44478]: 0x90, OSX senseid: 0x1

Connector at index 1

Type [@offset 44360]: DisplayPort (10)

Encoder [@offset 44364]: INTERNAL_UNIPHY2 (0x21)

i2cid [@offset 44505]: 0x91, OSX senseid: 0x2

Connector at index 2

Type [@offset 44370]: HDMI-A (11)

Encoder [@offset 44374]: INTERNAL_UNIPHY1 (0x20)

i2cid [@offset 44532]: 0x93, OSX senseid: 0x4

Connector at index 3

Type [@offset 44380]: DVI-D (3)

Encoder [@offset 44384]: INTERNAL_UNIPHY1 (0x20)

i2cid [@offset 44559]: 0x95, OSX senseid: 0x6

Connector at index 4

Type [@offset 44390]: DVI-I (2)

Encoder [@offset 44394]: INTERNAL_UNIPHY (0x1e)

i2cid [@offset 44596]: 0x94, OSX senseid: 0x5

Connector at index 5

Type [@offset 44400]: DVI-I (2)

Encoder [@offset 44404]: INTERNAL_KLDSCP_DAC1 (0x15)

i2cid [@offset 44596]: 0x94, OSX senseid: 0x5

Link to comment
Share on other sites

My Sapphire 4-port Duckweed 6870 100314-3L model with [ DVI-Dual ] [ HDMI ] [ DP ] and then a lower [ DVI ] single-link port is now working trouble-free with DVI-D and HDMI using the following values:

 

0000000	00  02  00  00  04  00  00  00  00  01  00  00  11  02  01  06	  // dvi-d  
0000010	00  08  00  00  00  02  00  00  00  01  00  00  22  05  06  04	  // hdmi  
0000020	00  04  00  00  04  03  00  00  00  01  00  00  12  04  04  01	  // dp	  
0000030	04  00  00  00  14  02  00  00  00  01  00  00  10  00  03  05	  // dvi-i	
0000040

 

I can't test the Display Port and I don't care about the other DVI port, but I'm happy now and these values I'm using for Trans/Encode have eliminated my stuttering and graphical hesitations. This has been a great learning experience for me.

 

Thank you, this worked great for my Sapphire 6850 using two DVI screens under Mountain Lion DP3 with the software update "OS X 10.8 (12A193i)"

Link to comment
Share on other sites

  • 3 weeks later...

dohnuts: I was curious why you even needed to do Hex editing on DP3 given that there is supposedly native support for the 6850 (Barts) as of DP3.

 

http://en.wikipedia....X_Mountain_Lion (System Requirements last bullet)

http://netkas.org/?p=1084

 

On my previous build with a Core 2 Duo CPU I had to do editing to get anything to work besides a single DVI output, but only got as far as adding Dual Link and VGA output after hours of frustrating editing leading nowhere.

 

On my current build with a Core i7 2700k the support seemed much better with dual DVI working using AtiConfig=Pithecia GraphicsEnabler=No on boot, as per a recommendation I saw in the tonymac database. Interestingly those same settings didn't work on my previous build (maybe because that was a SL build).

 

More interestingly these settings don't seem to work if I want to make them permanent in my Boot file using Chameleon Wizard - instead I just get gray screens! But if I type AtiConfig=Pithecia GraphicsEnabler=No by hand at the Chameleon boot loader screen the dual DVI output works fine. My benchmark drops ever so slightly but it's fine I guess.

 

So I thought then my three choices are:

 

1) maybe to start up the Hex editing again (I really don't want to unless I feel I have a good chance to succeed, but maybe now that I'm on Lion then other people's ATI6000.kext like the OP's will finally work for me???),

 

2) figure out why AtiConfig=Pithecia GraphicsEnabler=No doesn't work if put permanently into the Boot file (maybe I should edit it by hand?), or

 

3) give ML DP3 a shot, but I'm worried about other issues I might face (mostly software compatibility) since I have a stable 10.7.3 and I was waiting so long for dual DVI, I only want to upgrade if there's little to no risk of trading one problem for another (or several).

 

So my questions are:

How is software compatibility in ML DP3?

Same benchmarks, if you're doing them?

 

Questions for anyone:

Does it matter which vendor's 6850 you have? I have the Powercolor one.

 

A heads up to anyone working on their card who tried everything but can't get it to work:

On my first build, my offset was different than the one everyone seems to have in this thread. But maybe it's because it was an SL build? So if you're on SL, double check you are using the right offset if you're working on Duckweed, because mine was different for both 32bit and 64bit.

 

Thanks for any help from anyone.

Link to comment
Share on other sites

  • 1 month later...

I have a problem with the ati-personalities, i can't use it ^^ i have the last DP of Mountain Lion. Did i Need xCode 4.5 and the Command Line Tools package?

 

EDIT/ prob solved,

but there is a mistake when you create a connector. You say DVI SL an you write

0x00000200

and the text that you wrote before says

0x00000004.

 

 

But thx for the guide, it's awesome!!

 

 

sorry for my english...

Link to comment
Share on other sites

  • 3 weeks later...

I've finally got a new XFX HD6850, not knowing all the work that I would need to put in for all the

connectors to work, but it was worth it.

 

Thank you so much for all your & the others work !!!

I just had bought a Sapphire HD6850 and following your impressive guide i got

( DV1+VGA ) + DP + DV2 + HDMI (can't confirm audio yet) up and running for SL & Lion

 

GREAT FINDING & WORK

 

:thumbsup_anim:

 

Edit:

 

I used "Duckweed" aswell and changed Binary to

 

Port 0 : 00 04 00 00 04 03 00 00 00 01 00 00 12 04 04 01 → DP

Port 1 : 00 02 00 00 04 00 00 00 00 01 00 00 11 02 03 06 → DVI-S

Port 2 : 00 08 00 00 04 02 00 00 00 01 00 00 22 05 04 04 → HDMI

Port 3 : 04 00 00 00 14 02 00 00 00 01 00 00 00 00 06 05 → DVI-D

 

SnowLeo_DiskOffset_x86_64 in dec: 172768

SnowLeo_DiskOffset_i386 in dec: 502332

 

Lion_DiskOffset_x86_64 in dec: 176800

Lion_DiskOffset_i386 in dec: 523912

  • Like 1
Link to comment
Share on other sites

what you mean with "stucked at ntfs version" :unsure:

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.... :wink2:

Link to comment
Share on other sites

  • 2 weeks later...

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 :)

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

@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. :P

Link to comment
Share on other sites

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 ^ ^

Link to comment
Share on other sites

@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 :/

Link to comment
Share on other sites

@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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

 Share

×
×
  • Create New...