Editing custom personalities for ATI Radeon HD[45]xx

atlee · April 3, 2011

@k540kk

Patched Ipomoea, Try this if nothing, Try changing flag 40 to 214.

Personality: Ipomoea

ConnectorInfo count in decimal: 3Disk offset in decimal 501244    

02  00  00  00  40 00  00  00  00  01  00  00  00 00 01  07 

00  08  00  00  04  02  00  00  00  01  00  00  11  02  04  02  (Try 01,12 or 01,02)

10  00  00  00  10  00  00  00  00  01  00  00  00  00  00  08

By refer to your quote :

(1) What kind of "enables LVDS screen" do you get?

Duplicated VGA output.

(2) This means there is no output on physical LVDS screen, right?

Yes and No, no real definetion in not working as screen is virtual on.

(3) How can you determine that LVDS is enabled and act as another VGA screen?

Each screen has there own EDID. Use SwitchResX and it will tell you how many monitors you have and also you can export EDID.

(4) No question, just want to see the interference(if possible).

As per below.

(5) I agree with you, connector does nothing.

True and not true depends how you look at it.

(6) SenseId is important for me, in my HDMI case, if SenseId is incorrect, screen is not detected.

Sense ID not sure why any values work

(7) Just FYI, not sure about this, in my HDMI case, There will be output on screen only when transmitter/encoder=2103. Please notice that if SenseId is correct, OSX will detect HDMI as we can see in System Profiler but will be no output on screen if transmitter/encoder is not 2103.

HDMI could be 01,02/21,03/11,02/01,12 according to how Apple use there certain combinations and referring also to mucha's guide and also results from Ubuntu.

(8) My VGA is only worked with 0000.

00,00 is dual connection so use 00,00 for LVDS as well.

(9) Only Control flag=14 can give corrupt output on LVDS (the only case that show something on screen).

Try 40, 100, 214 there are a few.

Try patching this personality which might work for your card.

Personality: Pithecia
ConnectorInfo count in decimal: 3
Disk offset in decimal 500508
00  04  00  00  04  03  00  00  00  01  00  00  21  03  02  04
04  00  00  00  14  02  00  00  00  01  00  00  00  00  04  03
10  00  00  00  10  00  00  00  00  01  00  00  00  00  00  01

Change to

Personality: Pithecia
ConnectorInfo count in decimal: 3
Disk offset in decimal 500508
00  08  00  00  04  02  00  00  00  01  00  00  21  03  02  04 (if 21,03 not work try the others i said)
02  00  00  00  14  02  00  00  00  01  00  00  00  00  04  03
10  00  00  00  10  00  00  00  00  01  00  00  00  00  00  01

kizwan · April 3, 2011

Based on this picture, I know the controller or framebuffer kexts is not loaded (ATI6000Controller.kext ???). If possible, setup remote connection. Connect remotely via vnc & check whether controller & framebuffer kexts are loaded or not.

k540kkk · April 3, 2011

@atlee, Have you got behavior like this on Windows?

Using Catalyst Control Center on Windows 7, It allows only 2 monitors activated at the same time. When I tried to activate 3rd monitor, It forced me to select one of active monitors to be disabled.

Just notice that this maybe limitation on this card. Only 2 monitors can be activated at the same time.

Right now,No matter what personality we have tried,we've got only HDMI and VGA working.

Perhaps the personality we used is correct, we may need a method to disable HDMI or VGA and then enable LVDS.

doof · April 3, 2011

@atlee, Have you got behavior like this on Windows?

You get two displays from any combo of the DVI and HDMI ports >2 requires using the MDP. Manual page 13

bcc9 · April 3, 2011

I forgot to update.

If you have time to do it, that would be wonderful. It will be useful for mobility card too.

I wasn't exactly volunteering, but if it turns out to be simple enough I could.

However first information needs to be sorted out: what's working, what are the minimal changes required for the various platform cards. If the normal case for desktop cards is that only the senseid needs to be fixed, then that could be automated. If there is no normal case, then a big list of the cards and their patches needs to be created first.

This feature would be great too. So the i2cid value is not hardware dependent?

I should think it is. I wouldn't want to flash the i2cid to some new value unless I was sure of what I was doing.

Fjtorsol · April 3, 2011

I should think it is. I wouldn't want to flash the i2cid to some new value unless I was sure of what I was doing.

It is safe, I flashed the iMac 8,1 VBIOS to my Mobility Radeon HD 2600 XT and it booted perfectly the problem is that the changes compared to my VBIOS included different indexes for the connector types resulting in a working VGA without I2CID, as the matching connector I2CID was intended for ANALOG I2CID-less S-VIDEO, so it worked without EDID. Anyway this demonstrates that it at least can be tried as the I2C ID's seem to be only numerical indexes asociated to each connector with the only intention of enumerating. It would involve getting rid of the binnary patching in many cases after each OSX update, I think It does worth a try.

atlee · April 3, 2011

@atlee, Have you got behavior like this on Windows?

If you read mobility graphics cannot do triple monitors unless it has the ports, if only VGA and HDMI, thats it 2 at a time. but LVDS and HDMI or LVDS and VGA should work.

Final conclusion based on 5650m card only.

21,03 is HDMI, 01,02 causes interference with laptop screen, 11,02 also fuzzy, 01,12 also.

MBP2011 drivers LVDS 00,00 create black, 10,00 create black, 20,01 create fuzzy. conclusion here is it's either 10,00 or 00,00. i doubt 20,01 but might be. using Lion DP2 kexts all 3 combos are black.

VGA is 00,10, or you can use 00,00 for VGA and 00,00 for LVDS because it's a dual connection.

Now 2 major concerns regarding Controlflags and Features.

Changing ControlFlags can activate or deactivate certain screens. Changing Features can also do the same behaviour. I think overtime after study more newer version kexts that the features and flags will make sense. Example LVDS features 09,01 makes the screen not work, just 09 still not work. Just 01 then it makes a huge difference.

Using Lion DP2 kexts I can use Langur/Hoolock/Baboon/Eulemur without patching and LVDS and VGA turn on. duplicate VGA but it show's and looks like it's working and also QE/CI works. You might need SwitchResX to change res.

I think if our cards would or could work fully then it would auto detect and load using DP2 kexts but it doesn't, forcing the RadeonFramebuffer only activates 2 connections and not LVDS so again i think if our cards could work then it would auto connect the interface.

bcc9 · April 4, 2011

Ok, I've made a new version of radeon_bios_dump, version 0.2 in post #1. This new version reports the byte offsets in decimal for the type/encoder/i2cid fields that I'm decoding. The new version also prints the PCI vendor&device ID (not just the sub-ids) so I think there's now enough information being printed for someone to start a patch database...

doof · April 4, 2011

Ok, I've made a new version of radeon_bios_dump, version 0.2 in post #1. This new version reports the byte offsets in decimal for the type/encoder/i2cid fields that I'm decoding. The new version also prints the PCI vendor&device ID (not just the sub-ids) so I think there's now enough information being printed for someone to start a patch database...

Thanks for making this. I'm game. Dumping the rom from xfx 6870 with your new version gives me:

ATOM BIOS Rom:

SubsystemVendorID: 0x1682 SubsystemID: 0x3100

IOBaseAddress: 0x0000

Filename: 687AZNF.BIN

BIOS Bootup Message:

BARTS XT HYNIX/SAMSUNG GDDR5 32Mx32 BIOS

PCI ID: 1002:6738

Connector at index 0

Type [@offset 44824]: DisplayPort (10)

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

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

Connector at index 1

Type [@offset 44834]: DisplayPort (10)

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

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

Connector at index 2

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

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

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

Connector at index 3

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

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

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

Connector at index 4

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

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

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

Connector at index 5

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

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

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

There are two personalities that are close

Personality: Duckweed

ConnectorInfo count in decimal: 4

Disk offset in decimal 500828

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 04 02 00 00 00 01 00 00 00 00 06 05

0000040

which works but its missing the DVI-I connector info which results in no output from the lower connector. The other personality that looks similar is Gibba.

Personality: Gibba

ConnectorInfo count in decimal: 5

Disk offset in decimal 501084

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

Gibba enables all the ports but the performance drops >50% and this part

0000030 00 02 00 00 04 02 00 00 00 01 00 00 00 00 03 05

looks wrong to me. I read Mucha's thread but wasn't clear on the port ids. Is 02 an lvds connector or a dvi connector. Also I'm not clear on why there are 6 outputs from the dump on 5 connecters. How do I deal with the analog vga >dac output on the same connector as the single link dvi?

Any idea whats killing the performance with Gibba?

atlee · April 4, 2011

In regards to DP2 Lion Kexts, Also along with these kexts using ATIRadeonX3000 files from MBP2011 stock.

Hoolock Personality

02  00  00  00  40  00  00  00  00  01  00  00  00  00  05  07

10  00  00  00  10  00  00  00  00  01  00  00  00  00  04  08

00  08  00  00  00  02  00  00  00  01  00  00  21  03  01  01

This get's me 2x VGA, LVDS acting as VGA and VGA as CRT.

HDMI works.

QE/CI.

But I know it's not perfect, but it works as it should except LVDS not actually detecting as it should and LVDS screen activating because of VGA EDID. wierd but hey.

I can replicate to Baboon, Langur, Eulemur.

Also this setup doesn't allow mirroring or extended. Unless you play around with the Controlflags of course.

That's it from me, i will be waiting for 10.6.8 beta so i can get to the gfx drivers to see if anything new.

Quote from AMD site:

iMac Games on ATI Radeon HD graphics
ATI Radeon™ graphics solutions offer feature rich graphics performance enabling an immersive, life-like gaming experience while playing HD content with incredible visual fidelity.
ATI Radeon™ HD 5750 graphics are available in the new 27” iMac.
ATI Radeon™ HD 5650 graphics are available in the new 21.5” and 27” iMac.
ATI Radeon™ HD 4670 graphics are available in the new 21.5” iMac.

Would love to find out more information :huh: Apparently 5650's went in Core i3 models, maybe 5650's were short and they went with 5670's? hmmm looking more into it.

Fjtorsol · April 4, 2011

Ok, I've made a new version of radeon_bios_dump, version 0.2 in post #1. This new version reports the byte offsets in decimal for the type/encoder/i2cid fields that I'm decoding. The new version also prints the PCI vendor&device ID (not just the sub-ids) so I think there's now enough information being printed for someone to start a patch database...

It works, it gives the ability to change I2CID's easily but still (as you said before) it requires a checksum update.

PD: I am currently searching netkas' forums for some info over it.

Luke1995 · April 5, 2011

Hello (:

I need your help :censored2:

I have and ATI Mobility Radeon HD4570, and cannot get QE or CI to work.

I have tried using multiple Ati4600controller kexts, and also ATIFramebuffer kexts that were patched for the Dell Studio 1545 (same graphics card - 0x95531002)

Can you help me to get the right kexts to enable QE and CI on the internal display? (LVDS I believe)

I can get into SL through safe boot.

Thanks in advance

atlee · April 6, 2011

weird behaviour in Lion DP2, well Eulemur i forced it to load it only gives 2 outputs lol and the output goes to my LVDS as CRT, no modified kexts at this stage, no qe/ci so i guess i have to rumble through the list of monkeys to find the right FB, what a batch VGA not working because i haven't tried patching.

LVDS was scrambled to begin with had to VNC in. will do more testing, seems like i get diff results in Lion DP2 then i do using DP2 kexts inside of snow leopard.

Eulemur give me 1 screen.

Hoolock 1 screen.

Baboon 2 screens, 2 clones but can change.

Langur 2 screens but 1 screen cloned. not the same as baboon.

NO QE/CI, might dump mbp2011 kexts inside my DP2 setup to enable it

RadeonFramebuffer gives 2 working outputs, LVDS blank.

What is weird is if i force either 4 framebuffers it shows only 2 outputs, if i force RadeonFramebuffer it detects the 3 outputs inside IOReg. ***FIXED THIS ISSUE by editing and adding an output to evoenabler***

Still no QE/CI damn

If it don't work in Lion, there is no way for SL drivers are just not there yet i don't think. maybe they have deliberately made 5650 not work but 5670 work and 5630 work. not sure why they would but hey doesn't make sense. Like Checcco once said maybe the wiring is different comparing an Apple version of ATI to a Windows version of ATI, different card diff setup. Also another could be the manufacturer of the laptop wiring it differently.

Fjtorsol · April 6, 2011

I managed to understand how ATOMBIOS connector tables work thanks to the i2C ID offsets. The attached document contains a simple description of the tables and items and what they mean all based in hex strings. Hope it helps for a better understanding of personalities...

ATOMBIOS_connector_information_tables_description.rtf

382jsl881 · April 6, 2011

Did you inject "hda-gfx" in DSDT? (The name of the devices can be different in your DSDT)

Hi! Thanks, but I don't have a GFX0 device, i normally use GraphicsEnabler+VoodooHDA, but VoodooHDA doesn't work here. I don't get sound output (even if it's shown in the sound devices)

It seems as if bcc9 also had this problem a while ago?

-> Can i use this DTST patch?

atlee · April 7, 2011

I managed to understand how ATOMBIOS connector tables work thanks to the i2C ID offsets. The attached document contains a simple description of the tables and items and what they mean all based in hex strings. Hope it helps for a better understanding of personalities...

I had a quick look at the document. if i2C ID offsets were modified would this change the behavior in being able to get a screen which is black to a screen which switches on? I understand a little bit of that document however maybe yourself or Bcc9 can give me a better understanding in laymen terms, what if we compare ATOMBIOS from an Apple ATI card model to a Windows ATI ATOMBIOS model and see if the routing is different and encoders being selected is different and then see if we can make modifications to the Windows ATOMBIOS to make it detect right in MacOSX.

kizwan · April 7, 2011

Hi! Thanks, but I don't have a GFX0 device, i normally use GraphicsEnabler+VoodooHDA, but VoodooHDA doesn't work here. I don't get sound output (even if it's shown in the sound devices)
It seems as if bcc9 also had this problem a while ago?

-> Can i use this DTST patch?

First of all I don't know whether HDMI audio will works with VoodooHDA but I know it works with AppleHDA. So, just get rid the VoodooHDA.

The one I posted supposed to be an example. What you need to do is inject the HDAU device. You also need to add the "Method (_DSM, 4, NotSerialized)" in your graphic card device in DSDT. You'll need to figure out which device in DSDT is your graphic card. You can find the information by looking in your IORegistry.

toleda · April 7, 2011

Hi! Thanks, but I don't have a GFX0 device, i normally use GraphicsEnabler+VoodooHDA, but VoodooHDA doesn't work here. I don't get sound output (even if it's shown in the sound devices)
It seems as if bcc9 also had this problem a while ago?

-> Can i use this DTST patch?

Max22, the code you linked to contains an entry specifically for Nvidia Graphics Cards. The DSDT edit for generic hda-gfx is noted in the code box below.

Special considerations:

AppleHDA (10.6.5 or newer, v 1.9.9)

Voodoo (HDA, prepane and any other audio enabler) must be removed

Verify PCIE display address (usually 0x00010000 or 0x00030000)

Not clear what system you are working with, difficult to make specific edit suggestions

			
		Device (PEGP)
		{
			Name (_ADR, 0x00030000)
			Name (_PRW, Package (0x02)
			{
				0x09, 
				0x05
			})

			Device (GFX0)
			{
				Name (_ADR, Zero)
				Method (_DSM, 4, NotSerialized)
				{
					Store (Package (0x02)
						{
							"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 (0x02)
						{
							"hda-gfx", 
							Buffer (0x0A)
							{
								"onboard-1"
							}
						}, Local0)
					  DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
					Return (Local0)
				}
			}
		}

atlee · April 7, 2011

Max22, the code you linked to contains an entry specifically for Nvidia Graphics Cards. The DSDT edit for generic hda-gfx is noted in the code box below.

Also look inside the DSDT carefully to position this new code, there can be more then one reference to PEGP.

@bcc9 back on topic any more information that could be taken from ATOMBIOS or anything that we could get from the BIOS to create a DSDT trick so we could somehow reroute connections, wondering if it could be done? hope im clear enough.

382jsl881 · April 7, 2011

Thanks a lot all for your help!

According to IORegistryExplorer, i think PEGP is NBPG, GFX0 is PCE1 in the Asrock world. It did work!

Fjtorsol · April 7, 2011

I had a quick look at the document. if i2C ID offsets were modified would this change the behavior in being able to get a screen which is black to a screen which switches on? I understand a little bit of that document however maybe yourself or Bcc9 can give me a better understanding in laymen terms, what if we compare ATOMBIOS from an Apple ATI card model to a Windows ATI ATOMBIOS model and see if the routing is different and encoders being selected is different and then see if we can make modifications to the Windows ATOMBIOS to make it detect right in MacOSX.

After doing a comparison between Apple ATI VBIOS and their respective personalities I discovered that the personality SenseID isn't always the result of (being I2C ID 0xNS) S+1 in ATI QUAIL FB the SenseID is 07 and the matching I2CID is 0x91 as in my case where the SenseID was supposedly 0x05 (being the I2C ID 0x14) and the only working one was 0x07.

redsockosx · April 7, 2011

Greets to all, and a huge thanks to all of you, you're legends for getting this far, haha

I have spent the last several days of my life sitting here plodding away with some trial and error based on my[your] understanding of the personality table...

I have a Sapphire 1GB Flex 5770 that will run 3 displays without active displayport adapter...

OTB I can get QE/CI/OpenCL no sweat with Baboon, Vervet framebuffers, Hoolock if I modify the personality to include the dual DVI 0x200 connector type...

Anyway, I have made progress... I haven't really spent much time attempting to get any of the other ports to work other than the HDMI and the dual link DVI port (which works fine).

Here is my radeon_bios_decode:

./radeon_bios_decode <image.bin

ATOM BIOS Rom:

SubsystemVendorID: 0x174b SubsystemID: 0x1484

IOBaseAddress: 0xde00

Filename: 148X0300.DP3

BIOS Bootup Message:

JUNIPER BIOS UCODEv:126

PCI ID: 1002:68b8

Connector at index 0

Type [@offset 44326]: DisplayPort (10)

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

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

Connector at index 1

Type [@offset 44336]: DisplayPort (10)

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

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

Connector at index 2

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

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

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

Connector at index 3

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

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

i2cid [@offset 44535]: 0x92, OSX senseid: 0x3

Connector at index 4

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

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

i2cid [@offset 44535]: 0x92, OSX senseid: 0x3

So armed with all of your information I modified my HDMI personality line and get signal no sweat... problem is: it is always a mirror display of my primary. (Noting here that OSX thinks it is extended and not mirrored, despite it really being mirrored).

I have attempted several things here... your connectorInfo description/struct is of course not exactly in line with mucha's, and admittedly the discrepancy between them gives a bit of pause.. specifically, your OP says:

byte link_i2cid; /* Bits 0-3: i2cid

Bits 4-7: link transmitter link */

byte dac_digidx; /* Bits 0-3: link encoder number

Bits 4-7: link dac number */

and Mucha's says transmitter & encoder bytes with UNIPHY, etc.

Your dac_digidx appears ot be inline with Muchas, but the link_i2cid one is the one I am unsure of. Looking at the entire list of personality info, I'd say that mucha's appears to be correct.

This however doesn't really get me closer to figuring out why HDMI output, sensing, EDID detction, and everything is working, but it is reading it from the wrong spot in vram... hmmmm It would appear that nothing I can really do to the two important bytes there (transmitter/encoder) have anything to do with it..

Does this mean that instead of using the Vervet framebuffer as I have been that there is some other better suited one?

The reading I have done suggests that in evergreen based ati cards that the DIG encoders are hardwired to outputs, so I can't really mess with them... and the transmitter itself seems pretty straightforward...

The thought occurs to me that maybe I am going a bit cross-eyed having stared at all of this and taken too many notes and that maybe I am just missing something stupid, hahah

my "working" vervet personality (working == dual link dvi port and HDMI output but 'falsely' cloned) looks like:

Personality: Vervet

ConnectorInfo count in decimal: 4

Disk offset in decimal 80000

0000000 00 04 00 00 00 04 00 00 00 01 00 00 12 04 04 02 (haven't messed with DP yet)

0000010 04 00 00 00 14 00 00 00 00 01 00 00 01 12 01 04 (ATY,ActiveFlags = 1)

0000020 00 02 00 00 14 00 00 00 00 01 00 00 00 00 06 03 (Working fine)

0000030 00 08 00 00 00 02 00 00 00 01 00 00 02 04 05 01 (HDMI, incorrectly cloned)

also, the second DVI port "should" work too right? In looking at my radeon_bios_decode, it says the same senseid and i2cid as the working DL-DVI port which is weird, and I wasn't sure how the INTERNAL_KLDSCP_DAC1 maps to any of the UNIPHY/DACA/DACB & corresponding transmitter/encoder values...

Ideally, I am hoping to get three single-link DVI monitors hanging off this card... and I am pleasantly optimistic I can get it to work... must be missing something stupid, heheh, hoping you guys might be able to steer me in a better/more efficient direction...

Thx again to all of you... I am not sure most people appreciate how many fine hours all of this really represents.. haha

Cheers!

rominator · April 8, 2011

Hi, I usually have better luck with Nvidia cards but I think you guys are on to some really useful stuff here.

For the life of me I can't get anything out of radeon_bios_decode. I have tried numerous ROMs and i put them in my home folder along with R_B_D, open a terminal window and drop them, it either stops or says "No Atombios signature found"

So obviously I am overlooking some crucial step that any moron who got through 1st grade should know but I must have been chewing pencils that day.

Anyhow, to encourage someone to help me without using words like "noob" or "try googling", I thought I could contribute some needed pieces.

fixrom.py is a python script written by pipomolo42 at MR. fixrom.py <filetofix.rom> <fixedfile.rom> will give you correct checksum and allow rom to load, flash, etc.

I will also attach the Mac OEM Apple 5870, 5770, 4870 and 3870 ROMs so that they may be analyzed.

atlee · April 8, 2011

Hi, I usually have better luck with Nvidia cards but I think you guys are on to some really useful stuff here.

For the life of me I can't get anything out of radeon_bios_decode. I have tried numerous ROMs and i put them in my home folder along with R_B_D, open a terminal window and drop them, it either stops or says "No Atombios signature found"

Normally all i did was open terminal place both rom and script on desktop or inside your chosen directory.

type:

./radeon_bios_decode > nameoffile.rom

OR

./radeon_bios_decode < nameoffile.rom

this should print out info below. not sure which way <> brackets go

Fjtorsol · April 8, 2011

Normally all i did was open terminal place both rom and script on desktop or inside your chosen directory.

type:

./radeon_bios_decode > nameoffile.rom

OR

./radeon_bios_decode < nameoffile.rom

this should print out info below. not sure which way <> brackets go

It is <, and bad news changing I2C ID's in VBIOS is useless as they are references to hardwired I2C buses. And respect to my ATOMBIOS connector tables descriptions it is a bit different for RV7XX:

- The secondary table (the one that uses items ending in 0xFF) has a diferent order for it's items and ads new values

- The third table with encoder ID's and an a unknwon value different for each encoder doesn't exist.

Editing custom personalities for ATI Radeon HD[45]xx

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites