Jump to content

Mobility Radeon - 10.6.6/7 guide for QE/CI - testing 10.7

wmarsh

By wmarsh,
in ATi

 Share
564 posts in this topic

Recommended Posts

mojtabazarei
mojtabazarei
Posted
Posted
QE/CI, DVD Player, Frontrow...yeah seems good. I'm guessing maybe it might be the new ATIRadeonX3000 from 10.6.7. Because i remember testing 10.7 Uakari and Vervet and they gave me no QE/CI. But now I have it again.

 

ATI5000Controller is 10.7

ATIFramebuffer is 10.7

ATISupport is 10.7

ATIRadeonX3000 is v1.6.26.31 stock new from 10.6.7 upgrade.

 

I haven't tried to patch 10.6.7 files, i'm happy with the extended and mirroring, qe/ci under Uakari. I can work on swapping T/E until HDMI is working but during my uni work i will eventually get around to it today :(

 

 

 

 

 

i tried another time my laptop screen is on but black screen?

 

this is not perfect support because it doesn't recognize

 

display name and ...

 

can you put these four kexts from 10.6.7 upgrade maybe this

 

update work better for us

Link to comment
Share on other sites
atlee
atlee
Posted
Posted
i tried another time my laptop screen is on but black screen?

 

this is not perfect support because it doesn't recognize

 

I did state its not perfect but until we get more hard evidence with transmitters and encoders all i can do, and anybody else with these mobility is fiddle around with numbers and just maybe a perfect match will come out of this testing.

Link to comment
Share on other sites
checcco
checcco
Posted
Posted

Guys I'm gonna give up... I've spent most of the last three weeks figuring out how to make my lvds to work...

Last night I even dreamed of kizwan fixing my DSDT :) I think this is a clear sign I have to stop for a while... :D

Anyway, I think there's nothing I haven't tried... I'm happy for all of you guys who have managed to get proper support for mobility

 

Someone has reported success on 5650m too but only on ACER or MSI laptop... I think probably things aren't working for me beacuse HP makes something different.

 

It's been very nice to feel part of this successful project :) thanks bcc9, mucha, kizwan, hjs89, wmarsh. I've learnt a lot.

 

Good luck atlee, now I think you're the only active user left for fixing 5650m.

 

I'm gonna treat my "Nomascus Syndrome" then I'll be back :)

 

EDIT: for people asking me via PM what my avatar is... The 6th of April Berlusconi will go to trial... Fingers crossed.

Link to comment
Share on other sites
c0ke
c0ke
Posted
Posted

Hi all, I'm still trying to let correctly work both my mobility hd4330 internal lvds and external vga output.

 

Actually I had success with 2 configurations:

 

  • 10.7 ati kexts giving me perfect output on external vga and flickering wrong color images on the internal.
  • 10.6.6 ati kexts modded following kizwan, mucha and crazybirdy info giving me perfect output on internal lvds, with the vga connected monitor perfectly recognized, but without any output displayed.

 

I tried also to get dmesg data loading different versions of RadeonHD kext, but when I had no KP, the Encoder.txt obtained was filled only with error messages.

 

Following the crazybirdy guide, finally I've got these info from ubuntu:

 

[	3.139578] [drm] Initialized drm 1.1.0 20060810
[	3.188500] [drm] radeon defaulting to kernel modesetting.
[	3.188503] [drm] radeon kernel modesetting enabled.
[	3.189610] [drm] initializing kernel modesetting (RV710 0x1002:0x9552).
[	3.189736] [drm] register mmio base: 0xF6DF0000
[	3.189738] [drm] register mmio size: 65536
[	3.189915] [drm] Clocks initialized !
[	3.189951] [drm] Detected VRAM RAM=512M, BAR=256M
[	3.189953] [drm] RAM width 64bits DDR
[	3.190050] [drm] radeon: 512M of VRAM memory ready
[	3.190053] [drm] radeon: 512M of GTT memory ready.
[	3.190151] [drm] radeon: irq initialized.
[	3.190154] [drm] GART: num cpu pages 131072, num gpu pages 131072
[	3.190809] [drm] Loading RV710 Microcode
[	3.242896] [drm] ring test succeeded in 1 usecs
[	3.243053] [drm] radeon: ib pool ready.
[	3.243129] [drm] ib test succeeded in 0 usecs
[	3.243131] [drm] Enabling audio support
[	3.243164] [drm] Default TV standard: NTSC
[	3.243582] [drm] Radeon Display Connectors
[	3.243584] [drm] Connector 0:
[	3.243586] [drm]   VGA
[	3.243588] [drm]   DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
[	3.243590] [drm]   Encoders:
[	3.243591] [drm]	 CRT1: INTERNAL_KLDSCP_DAC1
[	3.243593] [drm] Connector 1:
[	3.243594] [drm]   LVDS
[	3.243596] [drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
[	3.243598] [drm]   Encoders:
[	3.243600] [drm]	 LCD1: INTERNAL_UNIPHY2

 

than my radeondump infos are:

 

ATOM BIOS Rom: 
SubsystemVendorID: 0x1028 SubsystemID: 0x02aa
IOBaseAddress: 0xde00
Filename: BR32831.001 
BIOS Bootup Message: 
BR32831-001 M92 DDR2 64bit 450e/500m										

Connector at index 0 type: VGA (1)
Connector's i2cid: 91
Connector at index 1 type: LVDS (7)
Connector's i2cid: 90

 

It seems that VGA is connected to port 0 and LVDS on port 1;

Could you help me to figure out how to set the offset for both 64 and 32 bit to make some more trials?

I would prefer to work with the 10.6.6 kexts, but maybe is better to try with the lion's.. who knows..

How could I extract correct encoder and transmitter values from the ubuntu printout above?

 

@checcco, I fear that in the end he's going to win another dirty war and will not be judged.... Riposati un po' e tieniti aggiornato :)

Link to comment
Share on other sites
crazybirdy
crazybirdy
Posted
Posted
Hi all, I'm still trying to let correctly work both my mobility hd4330 internal lvds and external vga output.

 

Connector at index 0 type: VGA (1)

Connector's i2cid: 91

Connector at index 1 type: LVDS (7)

Connector's i2cid: 90

 

It seems that VGA is connected to port 0 and LVDS on port 1;

Could you help me to figure out how to set the offset for both 64 and 32 bit to make some more trials?

I would prefer to work with the 10.6.6 kexts, but maybe is better to try with the lion's.. who knows..

How could I extract correct encoder and transmitter values from the ubuntu printout above?

 

I think, you may try to use this patch with Peregrine and the Kabyl's boot on my post in mucha's thread post#20.

02 00 00 00 40 00 00 00 09 01 00 00 12 00 01 01 LVDS

10 00 00 00 10 00 00 00 00 01 00 00 00 10 00 02 VGA

Link to comment
Share on other sites
c0ke
c0ke
Posted
Posted
I think, you may try to use this patch with Peregrine and the Kabyl's boot on my post in mucha's thread post#20.

02 00 00 00 40 00 00 00 09 01 00 00 12 00 01 01 LVDS

10 00 00 00 10 00 00 00 00 01 00 00 00 10 00 02 VGA

 

 

mmmh... tried these combinations

 

from kizwan's guide:

02 00 00 00 40 00 00 00 09 01 00 00 02 01 00 01 (LVDS)

10 00 00 00 10 00 00 00 00 01 00 00 00 10 00 02 (VGA)

 

modified by me

02 00 00 00 40 00 00 00 09 01 00 00 02 01 00 01 (LVDS)

10 00 00 00 10 00 00 00 00 01 00 00 00 10 01 02 (VGA)

and

02 00 00 00 40 00 00 00 09 01 00 00 02 01 01 01 (LVDS)

10 00 00 00 10 00 00 00 00 01 00 00 00 10 00 02 (VGA)

 

from crazybirdy

02 00 00 00 40 00 00 00 09 01 00 00 12 00 01 01 (LVDS)

10 00 00 00 10 00 00 00 00 01 00 00 00 10 00 02 (VGA)

 

 

all of them giving good output on LVDS, but external VGA monitor OFF although recognized by the system

 

Maybe looking at the 10.7 framebuffer could help, in fact the vga output is perfect with them. How could I know the offset where these info are stored in the 10.7 ATIFramebuffer?

Link to comment
Share on other sites
hjs89
hjs89
Posted
Posted

I've the same issue than cOke. LVDS is working but and external monitors detected, but without signal. I've done one more test. I've patches all the Bird FB with this code:

 

Gliff, Kakapo, Quail, Raven and Shrike:

02 00 00 00 40 00 00 00 09 01 00 00 12 00 00 07
10 00 00 00 10 00 00 00 00 01 00 00 00 10 01 01
00 08 00 00 00 02 00 00 00 01 00 00 10 01 02 02

 

Cardinal, Motmot and Peregrine:

02 00 00 00 40 00 00 00 09 01 00 00 12 00 00 07
00 08 00 00 00 02 00 00 00 01 00 00 10 01 02 02

 

With the 2 output FB I've signal in LVDS and the external display is detected, but it doesn't detect any signal.

 

With Gliff, Quail and Raven the displays are detected, but without signal. Before being black the LVDS turns half gray one second.

 

With Kakapo and Shrike the graphic system doesn't start.

Link to comment
Share on other sites
wmarsh
wmarsh
Posted
  • Author
Posted
Do you ever try to exchange the first line and second line like this? My LVDS is port 0, I alway put it on the first line. I don't know if it woks or not.

10 00 00 00 10 00 00 00 00 01 00 00 00 10 01 01
02 00 00 00 40 00 00 00 09 01 00 00 12 00 00 07

I think you may need the other Control Flag for LVDS 2nd, 

10 00 00 00 10 00 00 00 00 01 00 00 00 10 01 01
02 00 00 00 00 01 00 00 09 01 00 00 12 00 00 07

There are Apple FB using that Control flag on 2nd port

Link to comment
Share on other sites
wmarsh
wmarsh
Posted
  • Author
Posted
all of them giving good output on LVDS, but external VGA monitor OFF although recognized by the system

 

Maybe looking at the 10.7 framebuffer could help, in fact the vga output is perfect with them. How could I know the offset where these info are stored in the 10.7 ATIFramebuffer?

This is very interesting and confusing.

 

My hardware is closer to c0ke than anyone elses. But I get hazy (white lines over screen) output on both LVDS and VGA

I thought the ports might be interfering, so I tried 00 out VGA, but did not help LVDS

ATOM BIOS Rom: 
SubsystemVendorID: 0x1028 SubsystemID: 0x02aa
IOBaseAddress: 0xde00
Filename: BR31245C.001
BIOS Bootup Message: 
Dell_Roberts_M92S_GDDR3 M92 GDDR3 64bit 450e/600m						   

Connector at index 0 type: VGA (1)
Connector's i2cid: 91
Connector at index 1 type: LVDS (7)
Connector's i2cid: 90

and here is my dmesg from RadeonHD (I don't find need to change plist to debug mode or change verbose to 2)

bash-3.2# dmesg
tomBIOS returned 3 Grey Levels
Get BL level: 0x0
Attaching Output AtomOutput UniphyE to Connector PANEL
ObjectTable - size: 136, BIOS - size: 65536 TableOffset: 42 object_header_end: 178
DisplayPathObjectTable: entries: 2 version: 1
 DisplaPathTable[0]: size: 10 DeviceTag: 0x1 ConnObjId: 0x3105 NAME: VGA GPUObjId: 0x1100
  GraphicsObj[0] ID: 0x2115 Type: 0x2 ObjID: 0x15 ENUM: 0x1 NAME: INTERNAL_KLDSCP_DAC1
  DeviceIndex: 0x0
 DisplaPathTable[1]: size: 10 DeviceTag: 0x2 ConnObjId: 0x310e NAME: LVDS GPUObjId: 0x1100
  GraphicsObj[0] ID: 0x2121 Type: 0x2 ObjID: 0x21 ENUM: 0x1 NAME: UNIPHY2
  DeviceIndex: 0x1
Output: AtomOutput DACA[0x 1] - adding devices:
Output: AtomOutput UniphyE[0x b] - adding devices:
Sensing DACA on Output AtomOutput DACA
DAC_LoadDetection Successful
BIOSScratch_0: 0x40000
rhdAtomBIOSScratchDACSenseResults: RHD_SENSED_NONE
I2C device "RHD I2C line 0:ddc2" registered at address 0xA0.
rhdAtomLvdsTimings: LVDS Modeline: 1600x900  97750  1600 (1600) 1648 1680 (1760) 1760  900 (900) 903 908 (926) 926
Mapping DIG1 encoder to KLDSKP_UNIPHYE
Crtc[0]: found native mode from Monitor[LVDS Panel]: 
Modeline "1600x900"  97  1600 1648 1680 1760  900 903 908 926
Connector "PANEL" uses Monitor "LVDS Panel":
DxModeValid: ATOM CRTC 1
Listing modesetting layout:
ATOM CRTC 1: tied to Atom PLL 1 and LUT A:
Outputs: AtomOutput UniphyE (PANEL)
ATOM CRTC 2: unused
Unused Outputs: AtomOutput DACA
Validating Modes from Monitor "LVDS Panel" on "PANEL"

I posted my RadeonHD at top of thread for consistency

 

I tried yesterday 16 different bytes for byte 14 (hotplugID), none of which mattered as long as they were not the same -- yes mucha said this but I was checking.

 

As far as the offsets for 10.7, there are no ConnectInfo strings in ATIFramebuffer anymore.

Motmot, Quail and Cardinal have migrated to the ATI4800Controller.kext, where they do us no good

You will find Shrike and Gliff in ATI4600Controller.kext

Shrike is at 1ff70 and 743f8

Gliff is at 1ff40 and 743a8

 

I have not found Peregrine anywhere. (I have not looked in the 3xxx Controller -- would do us no good there).

 

I did figure all the offsets for 10.6.7 -- they are exactly the same as 10.6.6

 

 

Cardinal, Motmot and Peregrine:

02 00 00 00 40 00 00 00 09 01 00 00 12 00 00 07
00 08 00 00 00 02 00 00 00 01 00 00 10 01 02 02

 

With the 2 output FB I've signal in LVDS and the external display is detected, but it doesn't detect any signal.

I don't think you can share links when both are connected. Try:

02 00 00 00 40 00 00 00 09 01 00 00 12 00 00 07
00 08 00 00 00 02 00 00 00 01 00 00 20 01 02 02

See this from mucha:

/* Transmitter Bits 4-7 (LinkID) */

#define DUAL_LINK 0x00

#define LINK_A 0x10

#define LINK_B 0x20

Link to comment
Share on other sites
hjs89
hjs89
Posted
Posted
This is very interesting and confusing.

 

My hardware is closer to c0ke than anyone elses. But I get hazy (white lines over screen) output on both LVDS and VGA

I thought the ports might be interfering, so I tried 00 out VGA, but did not help LVDS

ATOM BIOS Rom: 
SubsystemVendorID: 0x1028 SubsystemID: 0x02aa
IOBaseAddress: 0xde00
Filename: BR31245C.001
BIOS Bootup Message: 
Dell_Roberts_M92S_GDDR3 M92 GDDR3 64bit 450e/600m						   

Connector at index 0 type: VGA (1)
Connector's i2cid: 91
Connector at index 1 type: LVDS (7)
Connector's i2cid: 90

and here is my dmesg from RadeonHD (I don't find need to change plist to debug mode or change verbose to 2)

bash-3.2# dmesg
tomBIOS returned 3 Grey Levels
Get BL level: 0x0
Attaching Output AtomOutput UniphyE to Connector PANEL
ObjectTable - size: 136, BIOS - size: 65536 TableOffset: 42 object_header_end: 178
DisplayPathObjectTable: entries: 2 version: 1
 DisplaPathTable[0]: size: 10 DeviceTag: 0x1 ConnObjId: 0x3105 NAME: VGA GPUObjId: 0x1100
  GraphicsObj[0] ID: 0x2115 Type: 0x2 ObjID: 0x15 ENUM: 0x1 NAME: INTERNAL_KLDSCP_DAC1
  DeviceIndex: 0x0
 DisplaPathTable[1]: size: 10 DeviceTag: 0x2 ConnObjId: 0x310e NAME: LVDS GPUObjId: 0x1100
  GraphicsObj[0] ID: 0x2121 Type: 0x2 ObjID: 0x21 ENUM: 0x1 NAME: UNIPHY2
  DeviceIndex: 0x1
Output: AtomOutput DACA[0x 1] - adding devices:
Output: AtomOutput UniphyE[0x b] - adding devices:
Sensing DACA on Output AtomOutput DACA
DAC_LoadDetection Successful
BIOSScratch_0: 0x40000
rhdAtomBIOSScratchDACSenseResults: RHD_SENSED_NONE
I2C device "RHD I2C line 0:ddc2" registered at address 0xA0.
rhdAtomLvdsTimings: LVDS Modeline: 1600x900  97750  1600 (1600) 1648 1680 (1760) 1760  900 (900) 903 908 (926) 926
Mapping DIG1 encoder to KLDSKP_UNIPHYE
Crtc[0]: found native mode from Monitor[LVDS Panel]: 
Modeline "1600x900"  97  1600 1648 1680 1760  900 903 908 926
Connector "PANEL" uses Monitor "LVDS Panel":
DxModeValid: ATOM CRTC 1
Listing modesetting layout:
ATOM CRTC 1: tied to Atom PLL 1 and LUT A:
Outputs: AtomOutput UniphyE (PANEL)
ATOM CRTC 2: unused
Unused Outputs: AtomOutput DACA
Validating Modes from Monitor "LVDS Panel" on "PANEL"

I posted my RadeonHD at top of thread for consistency

 

I tried yesterday 16 different bytes for byte 14 (hotplugID), none of which mattered as long as they were not the same -- yes mucha said this but I was checking.

 

As far as the offsets for 10.7, there are no ConnectInfo strings in ATIFramebuffer anymore.

Motmot, Quail and Cardinal have migrated to the ATI4800Controller.kext, where they do us no good

You will find Shrike and Gliff in ATI4600Controller.kext

Shrike is at 1ff70 and 743f8

Gliff is at 1ff40 and 743a8

 

I have not found Peregrine anywhere. (I have not looked in the 3xxx Controller -- would do us no good there).

 

I did figure all the offsets for 10.6.7 -- they are exactly the same as 10.6.6

 

 

 

I don't think you can share links when both are connected. Try:

02 00 00 00 40 00 00 00 09 01 00 00 12 00 00 07
00 08 00 00 00 02 00 00 00 01 00 00 20 01 02 02

See this from mucha:

 

I tried this at the beginning. But it didn't work. Thanks for your idea.

 

About the fan's noise that we talked some post before. now I've native CPU Power Management with Speedsteep and my Temperatures are lower than before and my laptop is less noisy.

Link to comment
Share on other sites
kizwan
kizwan
Posted
Posted
I've the same issue than cOke. LVDS is working but and external monitors detected, but without signal. I've done one more test. I've patches all the Bird FB with this code:

 

Gliff, Kakapo, Quail, Raven and Shrike:

02 00 00 00 40 00 00 00 09 01 00 00 12 00 00 07
10 00 00 00 10 00 00 00 00 01 00 00 00 10 01 01
00 08 00 00 00 02 00 00 00 01 00 00 10 01 02 02

 

Cardinal, Motmot and Peregrine:

02 00 00 00 40 00 00 00 09 01 00 00 12 00 00 07
00 08 00 00 00 02 00 00 00 01 00 00 10 01 02 02

 

With the 2 output FB I've signal in LVDS and the external display is detected, but it doesn't detect any signal.

 

With Gliff, Quail and Raven the displays are detected, but without signal. Before being black the LVDS turns half gray one second.

 

With Kakapo and Shrike the graphic system doesn't start.

Using HDMI to DVI dongle can give false positive result. To make sure whether HDMI working or not, you'll need to test it with external monitor connected directly to HDMI port. OR you can try change the HDMI connection in the table to DVI instead.

Link to comment
Share on other sites
c0ke
c0ke
Posted
Posted
...

As far as the offsets for 10.7, there are no ConnectInfo strings in ATIFramebuffer anymore.

Motmot, Quail and Cardinal have migrated to the ATI4800Controller.kext, where they do us no good

You will find Shrike and Gliff in ATI4600Controller.kext

Shrike is at 1ff70 and 743f8

Gliff is at 1ff40 and 743a8

 

I have not found Peregrine anywhere. (I have not looked in the 3xxx Controller -- would do us no good there).

 

I did figure all the offsets for 10.6.7 -- they are exactly the same as 10.6.6

...

 

 

Great infos!

The ATI4600Controller.kext offset couples you posted are related to 64bit and 32bit versions or maybe to the vga and lvds connections?

 

I was thinking about copying the vga part from there and brutally paste it in the 10.6.6 atiframebuffer...

I will report results, maybe it could help you with the annoying white lines..

Link to comment
Share on other sites
crazybirdy
crazybirdy
Posted
Posted
I decided to apply this method to the Lion kexts in the hope of eliminating those annoying white lines.

I connect nicely with mod Lion kext.

However, it does not recognize booting with Shrike bootloader or change in plist

(Still says ATY,Peregrine) and the colors are very odd.

 

My test is somthing differet. By using 10.7 kexts (ATI4600Controller.kext, ATIFramebuffer.kext, ATISupport.kext) ,10.6.7 kexts (all ATIRadeonX2000 kexts) and trunk r749 boot, I get a clear output of LVDS but the colors become very odd like yours after a wake from display sleep.

 

I think maybe something is wrong with display sleep.

 

Use Shrike, and is not changed. As I remember, the result of (10.6.6 kexts + 10.7 kexts + kabyl boot) is just the same as your test, the colors are very odd after boot start.

 

[EDIT] after a normal start.

post-61100-1300912568_thumb.jpgpost-61100-1300912581_thumb.jpgpost-61100-1300912593_thumb.jpg

Link to comment
Share on other sites
mucha
mucha
Posted
Posted
My test is somthing differet. By using 10.7 kexts (ATI4600Controller.kext, ATIFramebuffer.kext, ATISupport.kext) ,10.6.7 kexts (all ATIRadeonX2000 kexts) and trunk r749 boot, I get a clean output of LVDS but the colors become very odd like yours after display sleep.

 

what about this combination;

1- ATI4600Controller.kext, ATIFramebuffer.kext, ATISupport.kext : from 2011 Macbook Pro 10.6.7 Update,

2- ATIRadeonX2000 kexts : from 10.6.7.

did you tried it ?

Link to comment
Share on other sites
hjs89
hjs89
Posted
Posted
Using HDMI to DVI dongle can give false positive result. To make sure whether HDMI working or not, you'll need to test it with external monitor connected directly to HDMI port. OR you can try change the HDMI connection in the table to DVI instead.

:wub: When I was using Lion's fb it was detected like HDMI port (0x800). I'll try setting the port like DVI, I don't lose anything checking it.

Link to comment
Share on other sites
wmarsh
wmarsh
Posted
  • Author
Posted
My test is somthing differet. By using 10.7 kexts (ATI4600Controller.kext, ATIFramebuffer.kext, ATISupport.kext) ,10.6.7 kexts (all ATIRadeonX2000 kexts) and trunk r749 boot, I get a clean output of LVDS but the colors become very odd like yours after display sleep.

 

I think maybe something is wrong with display sleep.

 

Use Shrike, and is not changed. As I remember, the result of (10.6.6 kexts + 10.7 kexts + kabyl boot) is just the same as your test, the colors are very odd after boot start.

post-61100-1300912568_thumb.jpgpost-61100-1300912581_thumb.jpgpost-61100-1300912593_thumb.jpg

Yours doesn't look quite as odd as mine.

The problem might be initialization not sleep. But clearly related.

 

I think the real problem is we are not injecting right.

I looked thru the code and GraphicsEnabler is what forces my boot display to be @0, whereas with RadeonHD of nothing it is @1

And I think the confusion is giving the interference I see as hazy white lines.

And since the initialization is in BIOS (or DSDT) we need to attach those routines to the correct device.

Graphics Enabler is not magic, and the programmers did not have any mobility Radeons to test as nobody cracked it before.

 

So I am working on DSDT patch to inject -- should give us as many ports as you want to add and should inject properly.

 

Attached is IOREG with current dsdt patch

As you will see, ATI4600Controller attaches properly @1, but the FB does not load.

I think I may need a different FB patch to make LVDS attach to FB@1 like you were suggesting earlier.

And I may need Shrike with a dummy connection@0 -- which would also help with Lion as Peregrine does not exist in Lion

Link to comment
Share on other sites
crazybirdy
crazybirdy
Posted
Posted
what about this combination;

1- ATI4600Controller.kext, ATIFramebuffer.kext, ATISupport.kext : from 2011 Macbook Pro 10.6.7 Update,

2- ATIRadeonX2000 kexts : from 10.6.7.

did you tried it ?

 

Not yet, I test kexts below, but can't reach the desktop.

1- ATI4600Controller.kext, ATIFramebuffer.kext, ATISupport.kext : from 2011 Macbook Pro 10.6.6 oem dmg

2- ATIRadeonX2000 kexts : from 10.6.7 (which is updated from 10.6.3).

 

 

Yours doesn't look quite as odd as mine.

The problem might be initialization not sleep. But clearly related.

 

I think the real problem is we are not injecting right.

 

So I am working on DSDT patch to inject -- should give us as many ports as you want to add and should inject properly.

 

Last post is clear colors, the odd picture is like what I test before as attached.

 

[EDIT] after a wake from sleep.

post-61100-1300916269_thumb.jpg

Link to comment
Share on other sites
mucha
mucha
Posted
Posted
Post #315 is after a normal start, and post #319 is after a wake from sleep.

I don't know why.

 

It's a good progress, in a 10.6.6 system with 10.7 framebuffer i was getting the inverted colors straight after the start with working external vga screen,

 

Update : i just tried 2 combinations:

 

1- ATIFrambuffer,ATISupport,ATI4600 from 2011 MBP 10.6.7 + ATIRadeonX2000* from vanilla 10.6.7.

2- All ATI kexts from 2011 MPB 10.6.7

So far no succes in both cases i get the old scrambled screen.

Link to comment
Share on other sites
wmarsh
wmarsh
Posted
  • Author
Posted

Mucha -- thank you for all your help

 

I wanted any comments you have on the dsdt patch I am working on to connect correctly. I think it is good and the problem is the FB does not load yet.

http://www.insanelymac.com/forum/index.php?showtopic=253113

 

I also wanted your comments on encoder/decoder. I get output on LVDS with encoder 02 and decoder 01 but it is garbled I think due to interference. This is connected with Graphics Enabler so my LVDS appears on @0 although physically it is @1. However, by my radeondump and dmesg I think it ought to be 12 00. Do you have any thoughts? It needs to be right to verify the dsdt patch.

 

Thanks! wmarsh

Link to comment
Share on other sites
kizwan
kizwan
Posted
Posted
:( When I was using Lion's fb it was detected like HDMI port (0x800). I'll try setting the port like DVI, I don't lose anything checking it.

Yes, you don't lose anything from it. Just to be sure that the HDMI to DVI converter doesn't caused false result. In hackintosh world, the converter sometime can make display working & sometime don't. It depend on the driver I guess. During testing/troubleshooting better connect directly the external monitor to HDMI port. But you don't have monitor with HDMI port. So, either borrow one from your friend OR if you have extra money, just buy one.

 

____________________________________________________________________________

 

I think we can start compare notes here.

So far I got these results for LVDS:-

  • On my Dell Studio 1557, it has a dual-link LVDS transmitter* and can support up to WUXGA panel resolution (1920x1280). But right now it only fitted with WXGA panel resolution (1366x768). LVDS is working.
  • Dell Studio 1747 (almuras), SXPS 1640 (sydlix) & SXPS 1645 (jvilla), also has dual-link LVDS transmitter*. I got all three of RadeonHD's log from them & I found all three have Full HD LCD panel. Also RadeonHD's log said all three have single-link LVDS transmitter which is weird. Based on the notebooks specification (LVDS "port" support dual-link LVDS transmitter & LCD panel required dual-link LVDS transmitter), it should be dual-link (transmitter: DUAL_LINK). LVDS is NOT working.
  • Acer Aspire 5738ZG (hjs89) has single-link LVDS transmitter*. LVDS is working.
  • Dell Inspiron 1545 (wmarsh & c0ke), based on the hardware specification, I'm sure it has single-link LVDS transmitter*. LVDS is working.

Note:-

  • * Referring to LVDS technology on the motherboard (we can called it LVDS "port"), not on the LCD panel.

Link to comment
Share on other sites
kizwan
kizwan
Posted
Posted

Ladies & Gentlemen,

 

I has open new thread. As suggested by mucha here, the purpose of this new thread is to collect working & tested configuration with ATIFramebuffer patching solution. This will keep us track which notebooks has been tested & whether it is working or not.

(Collection) ATI Mobility Radeon HD - Tested ATIFramebuffer Solution, Collection of tested & working ATI Mobility Radeon HD

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...