563 replies to this topic

[wmarsh]

I have managed to modify and connect 10.7 kexts using Flicker. Consequently I have put my DSDT project on hold as the whole point was to connect with the Lion kexts. Ioreg is attached. The colors are messed up. QE/CI does not work as I get black screen with Front Row and cannot start Beach screensaver. Maybe it will with less preliminary kexts.

QE/CI does work if you combine these with 10.6.6 ATIRadeonX2000.kext, as DonKurdi did. Its a Frankenstein, but its the best I've got so far. Colors are strange still.

For those interested:
Lion ATI4600Controller has 3 Framebuffers:
Flicker at offset 74378 and 1ff10
Shrike at offset 743f8 and 1ff70
Gliff at 743a8 and 1ff40

I went looking for Peregrine -- it seems to be removed.

Lion ATI4800Controller has 3 Framebuffers:
Cardinal at offset 71338 and 1ef30
Motmot at offset 71358 and 1ef50
Quail at 71378 and 1ef70

I also patched a test 10.6.3 system, as mucha figured out the byte I was confused by. (It was pretty obvious in retrospect)
Once patched correctly, the system starts without KP; however, ATIFramebuffer has unresolved symbols related to screen timing. I think this was incomplete when released and is not worth putting more time into.

Still no progress on the hazy white lines unfortunately.

[sydlix]

To me the reason why me and people having hi res LVDS displays on their laptops ain't got it working is that we are missing some settings with the ati injector, being it trunk or kabyl. I mean that I am using the right values into the framebuffer, 10.6.6/10.7 kexts and still getting everything but LVDS, that's black with backlight on. It would be useful to talk with someone that knows how the injector works and how to modify it accordingly.

[KUGLee]

Does anybody else have color depth issue? I've tried color calibration with no success.

[wmarsh]

Does anybody else have color depth issue? I've tried color calibration with no success.

Yes, at this point it seems if you have display exceeding WXGA you have color/haze/interference issues

I think the aty_config settings may be helpful, but I have not found documentation.

[KUGLee]

Yes, at this point it seems if you have display exceeding WXGA you have color/haze/interference issues

I only have WXGA.

[pepito1]

And can it be "ported" to ATi Mobility Radeon HD 3xxx? It would be great to see my 3430 card with QE/CI.

[wmarsh]

And can it be "ported" to ATi Mobility Radeon HD 3xxx? It would be great to see my 3430 card with QE/CI.

Well, pepito, you can be my hero and be the 1st to do so.
3xxx is much better documented, so I would think you will have an easier time.

1st get your radeondump info and your Xorg.0.log.

I have all the offsets figured for the 10.6.6/7 Framebuffers, and will be glad to share if you tell me which one you want to use.

[pepito1]

Well, pepito, you can be my hero and be the 1st to do so.
3xxx is much better documented, so I would think you will have an easier time.

1st get your radeondump info and your Xorg.0.log.

I have all the offsets figured for the 10.6.6/7 Framebuffers, and will be glad to share if you tell me which one you want to use.

Buff, I don't have a clue about programming and advanced things that, but I hope someone to do it.

[wmarsh]

Buff, I don't have a clue about programming and advanced things that, but I hope someone to do it.

Don't need to.
Get your radeondump and dmesg or Xorg.0.log. We can figure it out together.

[pepito1]

Don't need to.
Get your radeondump and dmesg or Xorg.0.log. We can figure it out together.

I'm sorry, but I don't understand anything. I'm a noob, but if you explain me clearly what you need, I'll give it to you.

[foxzz]

Don't need to.
Get your radeondump and dmesg or Xorg.0.log. We can figure it out together.

please help me to enable QE/CI on a dell 1535 with a ATI 3450M card

this is my informations

Connector

ATOM BIOS Rom:
SubsystemVendorID: 0x1028 SubsystemID: 0x0254
IOBaseAddress: 0xee00
Filename: br28447.001
BIOS Bootup Message:
Dell_HepburnFM6 M82 GDDR2_32Mx16 64bit 256MB 500e/500m

Connector at index 0 type: VGA (1)
Connector's i2cid: 93
Connector at index 1 type: LVDS (7)
Connector's i2cid: 90
Connector at index 2 type: HDMI-A (11)
Connector's i2cid: 92

VGA : SenseLine = (93 & 0xf)+1 = 4
LVDS : SenseLine = (90 & 0xf)+1 = 1
HDMI-A : SenseLine = (92 & 0xf)+1 = 3


radeondump
[RadeonHD]: Mapping DIG2 encoder to KLDSKP_LVTMA
[RadeonHD]: Crtc[0]: found native mode from Monitor[LVDS Panel]:
[RadeonHD]: Modeline "1440x900" 96 1440 1488 1520 1734 900 903 909 926[RadeonHD]:
[RadeonHD]: Connector "PANEL" uses Monitor "LVDS Panel":
[RadeonHD]: RHDValidateScaledToMode
[RadeonHD]: rhdModeValidateCrtc
[RadeonHD]: DxModeValid: CRTC 1
[RadeonHD]: DigModeValid
[RadeonHD]: LVTMATransmitterModeValid
[RadeonHD]: EncoderModeValid
[RadeonHD]: Listing modesetting layout:
[RadeonHD]: CRTC 1: tied to PLL 1 and LUT A:
[RadeonHD]:
Outputs: UNIPHY_KLDSKP_LVTMA (PANEL)[RadeonHD]:
[RadeonHD]: CRTC 2: unused
[RadeonHD]:
Unused Outputs: DAC A[RadeonHD]:
[RadeonHD]: RHDModesPoolCreate
[RadeonHD]: rhdCreateModesListAndValidate
[RadeonHD]: Validating Modes from Monitor "LVDS Panel" on "PANEL"
[RadeonHD]: rhdModeValidateCrtc
[RadeonHD]: FUNCTION: DxFBValid: CRTC 1
[RadeonHD]: rhdModeValidateCrtc


[ 23.020] (II) RADEON(0): Output VGA-0 has no monitor section
[ 23.020] (II) RADEON(0): I2C bus "VGA-0" initialized.
[ 23.020] (II) RADEON(0): Output LVDS has no monitor section
[ 23.020] (II) RADEON(0): I2C bus "LVDS" initialized.
[ 23.020] (II) RADEON(0): Output HDMI-0 has no monitor section
[ 23.020] (II) RADEON(0): I2C bus "HDMI-0" initialized.
[ 23.020] (II) RADEON(0): Port0:
[ 23.020] XRANDR name: VGA-0
[ 23.020] Connector: VGA
[ 23.020] CRT1: INTERNAL_KLDSCP_DAC1
[ 23.020] DDC reg: 0x7e20
[ 23.020] (II) RADEON(0): Port1:
[ 23.020] XRANDR name: LVDS
[ 23.020] Connector: LVDS
[ 23.020] LCD1: INTERNAL_KLDSCP_LVTMA
[ 23.020] DDC reg: 0x7e40
[ 23.020] (II) RADEON(0): Port2:
[ 23.020] XRANDR name: HDMI-0
[ 23.020] Connector: HDMI-A
[ 23.020] DFP1: INTERNAL_UNIPHY
[ 23.020] DDC reg: 0x7e60

personality
CRTC2>DAC > DACA >VGA　　Encoder = 0x10　　Transmitter = 0x10
　　CRTC1>DIG2>LVTMA>LVDS　　Encoder = 0x01　　Transmitter = 0x00

then
02 00 00 00 40 00 00 00 09 00 00 00 00 01 01 01 LVDS
　　10 00 00 00 10 00 00 00 00 00 00 00 00 10 00 04 VGA
　　00 08 00 00 00 02 00 00 00 00 00 00 00 01 02 03 HDMI

I changed the FB with the oranginal Megalodon and Iago with 10.6.6 kexts
with modified ati3800control.text.

the monitor LVDS keep dark with the code
02 00 00 00 40 00 00 00 09 00 00 00 00 01 01 01 LVDS

but works and right display resolutions with this code
02 00 00 00 14 00 00 00 09 00 00 00 00 01 01 01 LVDS
04 00 00 00 14 00 00 00 09 00 00 00 00 01 01 01 LVDS
02 00 00 00 14 00 00 00 09 00 00 00 00 01 01 01 LVDS
04 00 00 00 14 00 00 00 09 00 00 00 00 01 01 01 LVDS
02 00 00 00 14 00 00 00 09 01 00 00 00 01 01 01 LVDS
04 00 00 00 14 00 00 00 09 01 00 00 00 01 01 01 LVDS
02 00 00 00 14 00 00 00 09 00 00 00 00 02 01 01 LVDS
04 00 00 00 14 00 00 00 09 00 00 00 00 02 01 01 LVDS
02 00 00 00 14 00 00 00 09 00 00 00 00 02 01 01 LVDS
04 00 00 00 14 00 00 00 09 00 00 00 00 02 01 01 LVDS
02 00 00 00 14 00 00 00 09 01 00 00 00 02 01 01 LVDS
04 00 00 00 14 00 00 00 09 01 00 00 00 02 01 01 LVDS

but no QE/CI at all.

and the VGA not works

the 34xx chips
the LVTMA
the right FB

this is the problem now I have, who can hlep me figure out the resolution？

[wmarsh]

please help me to enable QE/CI on a dell 1535 with a ATI 3450M card

It looks like you do your homework well

5 Thoughts:
1) What bootloader are you using? I had to download Chameleon Trunk, modify ati.c, and recompile to get it to work.
Type "GraphicsEnabler"="y" at bootup. Remember Chameleon ignores com.apple.Boot.plist in /Extra if the partition is not set active.

2) You might try different FB. Not all work the same. For your controller, Megalodon and Triakis are the two in the Lion kext, so they are probably best choices.

3) Try different encoder values. I find the documentation excellent for everything else -- especially the ConnectorType and ControlFlags which you already tried changing. But for me the encoder that should work did not. The two possibilities are 00 and 01.

4) The 2nd digit of Transmitter is probably correct, but you could be using only 1 link, as the HDMI might use the other. Again the documentation here is sketchy. Try changing the 1st digit to 1 or 2 -- ie transmitter 10 or 10 instead of 00.

5) Like me, you have a 1400x900 display. This is at present an unsolved problem. Mine works, QE works, but there is interference -- white lines -- I do not know from where. We can keep working on this together once you have everything else functional.

[pepito1]

Will there be an easy way to have QE/CI working, like just installing a .kext?

[wmarsh]

Will there be an easy way to have QE/CI working, like just installing a .kext?

Once we have a modified kext that would work, yes.
Since no other 3xxx people have volunteered, you have the opportunity to be 1st.

Thats why they call it "the bleeding edge"

[mojtabazarei]

10.6.6 Uakari

00 04 00 00 00 04 00 00 00 01 00 00 12 04 04 01
04 00 00 00 14 00 00 00 00 01 00 00 01 12 01 03
00 02 00 00 14 00 00 00 00 01 00 00 00 00 06 05
00 08 00 00 00 02 00 00 00 01 00 00 22 05 05 04

10.7 Uakari

00 04 00 00 00 04 00 00 00 71 00 00 12 04 04 01
04 00 00 00 14 00 00 00 00 71 00 00 01 12 01 03
00 02 00 00 14 00 00 00 00 71 00 00 00 00 06 05
00 08 00 00 00 02 00 00 00 71 00 00 22 05 05 04

10.7 Uakari - Patched

00 04 00 00 00 04 00 00 00 71 00 00 12 04 04 00 - DP not sure if works
02 00 00 00 14 00 00 00 00 71 00 00 11 02 01 07 - shows as CRT but works, change to 40 and it will not work properly, you will lose extended and it will force cloning also.
10 00 00 00 10 00 00 00 00 71 00 00 00 00 06 08 - shows as CRT, working as extended, can also do mirror if i wish.
00 08 00 00 00 02 00 00 00 71 00 00 20 01 05 01 - Still changing around, combos 22,05/02,04/12,04/21,03/20,01 do not work.

I have LVDS as CRT, cannot get it to change it's name no matter what i do. VGA as CRT. DP cannot test. Might try swapping HDMI to either 01,02/11,02 as they are the last combos left, don't have access to that monitor as my wife is still awake

And yes i have tested booting without the VGA plugged in, LVDS switches res and turns on. VGA switch on and off when plugging in and out so the behavior seems ok to me.

If you change the LVDS T/E sometimes you lose the Extended desktop and it will force cloning, So i have kept it on something that works. default also works. but i was playing around to see what i could do.

Don't know if i'm right but i'm enjoying the results i'm getting now anyway.

Also note i do not really consider DP port of any use so i will not intend to play around and fix it, as it is not a requirement for me.

atlee i changed the line 3

10 00 00 00 10 00 00 00 00 71 00 00 00 00 06 08

08 to 01(my sense id for vga ) my LGT710PU now recognized fully in system profiler but LVDS doesn't work it recognized as svga and black screen dont have HDMI monitor to test

now see the two ioreg

1st. when i just set Graphic Enabeler =yes in plist :

-o ATY,ATY,RadeonFramebuffer@1  <class AtiFbStub, id 0x100000346, registered, matched, active, busy 0 (13 ms), retain 7>
	| |   |   | | | {
	| |   |   | | |   "display-type" = "CRT"
	| |   |   | | |   "compatible" = <"ATY,Megalodon">
	| |   |   | | |   "connector-type" = 16
	| |   |   | | |   "ATY,ActiveFlags" = 16
	| |   |   | | |   "IOFBDependentIndex" = 1
	| |   |   | | |   "IOFBDependentID" = 117486592
	| |   |   | | |   "device_type" = "display"
	| |   |   | | |   "VRAM,memsize" = <0000000000000010>
	| |   |   | | |   "AAPL,gray-page" = <01000000>
	| |   |   | | |   "ATY,ControlFlags" = 16
	| |   |   | | |   "av-signal-type" = 1
	| |   |   | | |   "AAPL,iokit-ndrv" = <8002c25e>
	| |   |   | | |   "AAPL,gray-value" = <c38c6400>
	| |   |   | | |   "display-connect-flags" = <00000000>
	| |   |   | | |   "name" = "ATY,ATY,RadeonFramebuffer"
	| |   |   | | |   "port-number" = 2

2nd : when i edited Uakari and used that :

+-o ATY,Uakari@0  <class AtiFbStub, id 0x100000345, registered, matched, active, busy 0 (432 ms), retain 7>
	| |   |   | | | {
	| |   |   | | |   "port-number" = 2
	| |   |   | | |   "display-type" = "CRT"
	| |   |   | | |   "connector-type" = 16
	| |   |   | | |   "ATY,ActiveFlags" = 16
	| |   |   | | |   "IOFBDependentIndex" = 0
	| |   |   | | |   "IOFBDependentID" = 117276800
	| |   |   | | |   "ATY,ControlFlags" = 16
	| |   |   | | |   "AAPL,gray-page" = <01000000>
	| |   |   | | |   "device_type" = "display"
	| |   |   | | |   "av-signal-type" = 1
	| |   |   | | |   "AAPL,iokit-ndrv" = <8002b95e>
	| |   |   | | |   "AAPL,gray-value" = <c38c6400>
	| |   |   | | |   "display-connect-flags" = <00000000>
	| |   |   | | |   "name" = "ATY,Uakari"
	| |   |   | | |   "AAPL,boot-display" = <01000000>

so what you think?

[wmarsh]

Modified injector for dual link LVDS posted attached to 1st post.

[EDIT -- see attached ioreg. It injects successfully the 12 new properties I saw in the 2011 MBP ioreg.
I now have a black screen with Flicker and either the "incorrect" encoder that worked before and with the one Mucha's guide predicts.

I am thinking that perhaps Gliff -- which gave me a garbled mess before -- is the FB for dual link LVDS
So ... more testing, but I think I'm past a major obstacle. I knew GraphicsEnabler was not right before.]

[KUGLee]

Modified injector for dual link LVDS posted attached to 1st post.

Thank you wmarsh! My color issue is solved.

[wmarsh]

Thank you wmarsh! My color issue is solved.

Can you please post your specs, FB, and patch. I am still working on mine.

[hjs89]

Modified injector for dual link LVDS posted attached to 1st post.

[EDIT -- see attached ioreg. It injects successfully the 12 new properties I saw in the 2011 MBP ioreg.
I now have a black screen with Flicker and either the "incorrect" encoder that worked before and with the one Mucha's guide predicts.

I am thinking that perhaps Gliff -- which gave me a garbled mess before -- is the FB for dual link LVDS
So ... more testing, but I think I'm past a major obstacle. I knew GraphicsEnabler was not right before.]

Can you say something more about your mod? What are the properties that you saw in 2011 mbp? Did that mods only affect to lvds dual link?

[wmarsh]

Can you say something more about your mod? What are the properties that you saw in 2011 mbp? Did that mods only affect to lvds dual link?

Sure! I found 12 properties in MacBookPro8_3 ioreg that were not being injected by GraphicsEnabler. So I added them.

Dual Link
Link Format
Link Type
Dither
Inverter
Pixel Format
display-dual-link
display-pixel-component-bits
display-link-type
display-inverter
display-inverter-default-cycle
display-link-component-bits

Incidently, KUGLee says it also fixed his color depth issue.

It has definitely changed my system. I connect, but screen is still black. But part of the issue is the encoder/decoder did not work as predicted by dmesg before -- so I am debugging several issues at once. This may not be final version.