652 replies to this topic

[bcc9]

wmarsh, on Mar 20 2011, 06:35 PM, said:

Do you know anything about 10.6.2 Framebuffer? I am applying method to that -- I think the older drivers with ATI4500Controller.kext will work better on lower end Mobility Radeons - like my notebook. The ConnectorInfo strings look to be 20 bytes not 16. Most of it looks like filler though. I'm reinstalling on a usb disk to make a 10.6.2 test platform.

I had never looked back at older versions until just now.  Yes, looks like you're right, ConnectorInfo is 20 bytes in 10.6.x until 10.6.4 when it became 16 bytes.

[1120]

atlee, on Mar 21 2011, 05:12 AM, said:

wmarsh i was looking for Eulemur inside ATI5000Controller in 10.7 would you know where it is? or where it starts? or do i have to restart all the calculations again?

atlee, look HERE. checcco already found all patterns. Just look for them in hex ​​editor.

[Funky frank]

bcc9, on Mar 21 2011, 03:08 AM, said:

But probably it's a simple matter of getting the right values for NVCAP and perhaps display-cfg.  nvenabler trys to compute these dynamically for you, unfortunately it's closed source.  Are you sure nobody has figured out working NVCAP/display-cfg for your hardware?

Thanks bcc9. It's already well known that nvcap is completly useless for the internal screen on Sony Vaios. Krazubu, the developer of nvenabler believes this, too. The correct nvcap also is available, but has no effect to the problem.

[bcc9]

Funky frank, on Mar 21 2011, 07:32 AM, said:

Thanks bcc9. It's already well known that nvcap is completly useless for the internal screen on Sony Vaios. Krazubu, the developer of nvenabler believes this, too. The correct nvcap also is available, but has no effect to the problem.

I wonder how you know it's actually the correct nvcap.  For example the NVCAP for a mac with a 9400m is different than the NVCAP for a dell with a 9400m because the dell has more/better external video ports.

In addition to all the other methods for figuring out what's going on, surely the linux open source driver works with your hardware and you could look there to see what is different vs a macbook.  It's like playing sesame street's one-of-these-things-is-not-like-the-other

[kizwan]

bcc9, on Mar 22 2011, 02:13 AM, said:

I wonder how you know it's actually the correct nvcap.

The nvcap was derived from graphic card's ROM file. The same method works for other notebook model but not on sony. The internal LCD doesn't detected at all (in IORegistry).

I agree with you, to solved this problem they need to look to linux open source driver. Learn how the linux driver detect & intialized the internal LCD.  

[bcc9]

kizwan, on Mar 21 2011, 11:56 AM, said:

The nvcap was derived from graphic card's ROM file. The same method works for other notebook model but not on sony. The internal LCD doesn't detected at all (in IORegistry).

Hmm, a lot of unknown/guess fields described in those posts.  Not as far along as we are here with the ATI  driver
PS: I'd love to know what field to set in NVCAP or NVMT or display-cfg to get the connector-type to come out as HDMI (0x00000800).

[uukk]

I have a little trouble, my DP doesn't work.
This is my edited ATIFramebuffer:

Mac-Pro-di-fabry:tmp fabry$ od -Ax -tx1 /tmp/uakari3
0000000	00  04  00  00  00  04  00  00  00  01  00  00  12  04  04  03
0000010	04  00  00  00  14  00  00  00  00  01  00  00  01  12  01  01
0000020	04  00  00  00  14  00  00  00  00  01  00  00  00  00  06  05
0000030	00  08  00  00  00  02  00  00  00  01  00  00  22  05  05  04
0000040

and this is my ioreg of the bad connector:



my radeondump:

Mac-Pro-di-fabry:Desktop fabry$ ./radeondump < 1002_6898.rom
ATOM BIOS Rom: 
	SubsystemVendorID: 0x1043 SubsystemID: 0x0346
	IOBaseAddress: 0x0000
	Filename: SV36460.107 
	BIOS Bootup Message: 
6898.12.20.0.5.AS02 U126							  
					  
Connector at index 0 type: DisplayPort (10)
Connector's i2cid: 92
Connector at index 1 type: HDMI-A (11)
Connector's i2cid: 93
Connector at index 2 type: DVI-I (2)
Connector's i2cid: 94
Connector at index 3 type: DVI-I (2)
Connector's i2cid: 94

and the stock Uakari ATIFramefuffer:

Mac-Pro-di-fabry:tmp fabry$ od -Ax -tx1 /tmp/uakari2
0000000	00  04  00  00  00  04  00  00  00  01  00  00  12  04  04  01
0000010	04  00  00  00  14  00  00  00  00  01  00  00  01  12  01  03
0000020	00  02  00  00  14  00  00  00  00  01  00  00  00  00  06  05
0000030	00  08  00  00  00  02  00  00  00  01  00  00  22  05  05  04
0000040

I have only change the senseid of firsth row from 01 to 03 and the connector of DVI at row 3 from 200 to 4 (DVI) but the DP still not work and the active flags don't match.

What I missing?

many regards

[jsl]

Hi, bcc9
After using a true DP-->DP cable or DP-->HDMI active Eyefinity convertor I can activate DP audio, HDMI audio and DVI 3 ports at the same time now with Uakari or Vervet FB in Asus EAH 5850 or MSI Hawk 5770 card.
Also I can Sleep/Wake by USB mouse/keyboard at the main dispaly either DVI or HDMI.
Thanks again without your and mucha's guides I can not do it so well.

uukk, on Mar 22 2011, 11:17 PM, said:

I have a little trouble, my DP doesn't work.
This is my edited ATIFramebuffer:

Mac-Pro-di-fabry:tmp fabry$ od -Ax -tx1 /tmp/uakari3
0000000	00  04  00  00  00  04  00  00  00  01  00  00  12  04  04  03
0000010	04  00  00  00  14  00  00  00  00  01  00  00  01  12  01  01
0000020	04  00  00  00  14  00  00  00  00  01  00  00  00  00  06  05
0000030	00  08  00  00  00  02  00  00  00  01  00  00  22  05  05  04
0000040

and this is my ioreg of the bad connector:



my radeondump:

Mac-Pro-di-fabry:Desktop fabry$ ./radeondump < 1002_6898.rom
ATOM BIOS Rom: 
	SubsystemVendorID: 0x1043 SubsystemID: 0x0346
	IOBaseAddress: 0x0000
	Filename: SV36460.107 
	BIOS Bootup Message: 
6898.12.20.0.5.AS02 U126							  
					  
Connector at index 0 type: DisplayPort (10)
Connector's i2cid: 92
Connector at index 1 type: HDMI-A (11)
Connector's i2cid: 93
Connector at index 2 type: DVI-I (2)
Connector's i2cid: 94
Connector at index 3 type: DVI-I (2)
Connector's i2cid: 94

and the stock Uakari ATIFramefuffer:

Mac-Pro-di-fabry:tmp fabry$ od -Ax -tx1 /tmp/uakari2
0000000	00  04  00  00  00  04  00  00  00  01  00  00  12  04  04  01
0000010	04  00  00  00  14  00  00  00  00  01  00  00  01  12  01  03
0000020	00  02  00  00  14  00  00  00  00  01  00  00  00  00  06  05
0000030	00  08  00  00  00  02  00  00  00  01  00  00  22  05  05  04
0000040

I have only change the senseid of firsth row from 01 to 03 and the connector of DVI at row 3 from 200 to 4 (DVI) but the DP still not work and the active flags don't match.

What I missing?

many regards

Change to :
0000000 00  04  00  00  04  06  00  00  00  01  00  00  12  04  04  03
and using a true DP-->DP cable for DP monitor or DP-->HDMI active Eyefinity convertor for HDMI monitor.
Please read my posts for Asus EAH 5850 and MSI Hawk 5770.

[uukk]

jsl, on Mar 23 2011, 12:30 PM, said:

Change to :
0000000 00  04  00  00  04  06  00  00  00  01  00  00  12  04  04  03
and using a true DP-->DP cable for DP monitor or DP-->HDMI active Eyefinity convertor for HDMI monitor.
Please read my posts for Asus EAH 5850 and MSI Hawk 5770.

I use a true DP-->DP cable (I have a DELL U2711P) but the display port still not work after your configuration...

[bcc9]

uukk, on Mar 23 2011, 11:58 AM, said:

I use a true DP-->DP cable (I have a DELL U2711P) but the display port still not work after your configuration...

Check the transmitter/encoder values per mucha's thread?

[jsl]

uukk, on Mar 23 2011, 07:58 PM, said:

I use a true DP-->DP cable (I have a DELL U2711P) but the display port still not work after your configuration...

Please try :
0000000 00 04 00 00 00 05 00 00 00 01 00 00 12 04 04 03
That means 0x400 0x500 instead of 0x400 0x604 for Connector-type and ATY-ControlFlag
I found this because in 10.6.4 which used these different values for DP display port.

[VCH888]

bcc9, on Mar 22 2011, 02:50 AM, said:

Hmm, a lot of unknown/guess fields described in those posts.  Not as far along as we are here with the ATI  driver
PS: I'd love to know what field to set in NVCAP or NVMT or display-cfg to get the connector-type to come out as HDMI (0x00000800).

Off the topic

add these lines in dsdt for getting HDMI audio.  Credit to toleda.

								"@1,connector-type", 
								Buffer (0x04)
								{
									0x00, 0x08, 0x00, 0x00
								},

[kizwan]

Hi tmongkol,

Finally I got HDMI audio working. So, ATI HDMI audio on notebook works. The legacy kext which responsible in injecting my HD4570's device ID is causing the problem. Removed the legacy kext & add HD4570's device ID in ATI4600Controller.kext fixed the problem.

[bcc9]

tmongkol, on Mar 24 2011, 07:46 PM, said:

add these lines in dsdt for getting HDMI audio.

Thanks, I had tried that and it isn't sufficient to get working audio in my 9400m case.  It's good to hear that setting connector-type is sufficient for some other nvidia cases (fermi cards).

A few weeks ago when I digged further into NVDAResman, I saw that in the nvidia case, av-signal-type must also be set correctly, where 0x8 is the working hdmi value, but it turns up as 0x2 for the 9400m.  Unfortunately av-signal-type is set by NVDAResman and injecting the working value has no effect.  I was able to patch NVDAResman to cause av-signal-type to come out with the expected value, at which point the HDMI audio option finally did automatically hotplug on my 9400m.  However audio doesn't actually pass thru

If I could figure out the logic NVDAResman is using to set av-signal-type (based upon NVMT? NVCAP? display-cfg?) then I think I might have a working solution.

av-signal-type is coming up as 0x8 automatically in the fermi case?

[VCH888]

kizwan, on Mar 25 2011, 10:18 AM, said:

Hi tmongkol,

Finally I got HDMI audio working. So, ATI HDMI audio on notebook works. The legacy kext which responsible in injecting my HD4570's device ID is causing the problem. Removed the legacy kext & add HD4570's device ID in ATI4600Controller.kext fixed the problem.

@ kizwan

That's great.  So, most of HD 4xxx that have HDMI port should be able to get HDMI audio. (edited)



@ bcc9

I asked toledo to answer your fermi question since I didn't have it.  

update: got av-signal-type <08 00 00 00>
 GT220.jpg   208.71K   18 downloads
 GT240.jpg   242.4K   13 downloads

[frostxx]

Now remains someone to do *dmg package with all the settings for HD4570

[uukk]

jsl, on Mar 25 2011, 02:04 AM, said:

Please try :
0000000 00 04 00 00 00 05 00 00 00 01 00 00 12 04 04 03
That means 0x400 0x500 instead of 0x400 0x604 for Connector-type and ATY-ControlFlag
I found this because in 10.6.4 which used these different values for DP display port.

Thank you jls but does't work...
I have switched to MBPro 10.6.7 ATI kext and all three connector are full recognized (i see in the ioreg).
The ATY_ActiveFlags match the DP but the monitor still black.
I connect DVI and DP both and set the "clone mode", i can see in System Preference panel the DP monitor and I can configure it (changing resolution ecc.) but every thing I change it's still black...
I'm very frustrating...
Have you a idea?

many regards

[kizwan]

uukk, on Mar 26 2011, 05:03 PM, said:

Thank you jls but does't work...
I have switched to MBPro 10.6.7 ATI kext and all three connector are full recognized (i see in the ioreg).
The ATY_ActiveFlags match the DP but the monitor still black.
I connect DVI and DP both and set the "clone mode", i can see in System Preference panel the DP monitor and I can configure it (changing resolution ecc.) but every thing I change it's still black...
I'm very frustrating...
Have you a idea?

many regards

Probably transmitter is wrong. Try get RadeonHD's log in linux.

[uukk]

kizwan, on Mar 26 2011, 10:18 AM, said:

Probably transmitter is wrong. Try get RadeonHD's log in linux.

How can I get this detailed log?
I have search in dmesg and /var/log/Xorg.0.log but seems not very detailed.

many regards

[kizwan]

uukk, on Mar 26 2011, 11:02 PM, said:

How can I get this detailed log?
I have search in dmesg and /var/log/Xorg.0.log but seems not very detailed.

many regards

The log should look like this or similar:-

[ 7.528400] [drm] Loading RV710 Microcode
[ 7.583699] [drm] ring test succeeded in 1 usecs
[ 7.583941] [drm] radeon: ib pool ready.
[ 7.584065] [drm] ib test succeeded in 0 usecs
[ 7.584069] [drm] Enabling audio support
[ 7.667456] [drm] Unknown TV standard; defaulting to NTSC
[ 7.667603] [drm] Radeon Display Connectors
[ 7.667606] [drm] Connector 0:
[ 7.667609] [drm] LVDS
[ 7.667613] [drm] DDC: 0x7f68 0x7f68 0x7f6c 0x7f6c 0x7f70 0x7f70 0x7f74 0x7f74
[ 7.667616] [drm] Encoders:
[ 7.667619] [drm] LCD1: INTERNAL_UNIPHY2
[ 7.667622] [drm] Connector 1:
[ 7.667624] [drm] VGA
[ 7.667628] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
[ 7.667630] [drm] Encoders:
[ 7.667633] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[ 7.667636] [drm] Connector 2:
[ 7.667638] [drm] HDMI-A
[ 7.667641] [drm] HPD1
[ 7.667644] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
[ 7.667647] [drm] Encoders:
[ 7.667649] [drm] DFP1: INTERNAL_UNIPHY

Please post the log here. Thank you.