It's a long shot but please test this ATIFramebuffer.kext:
10.6.7_ATIFramebuffer_for_0x9480.zip 103.7KB
91 downloads
10.6.7_ATIFramebuffer_for_0x9480.zip 103.7KB
91 downloads
@almuras,
It's a long shot but please test this ATIFramebuffer.kext:10.6.7_ATIFramebuffer_for_0x9480.zip 103.7KB 91 downloads
I think the kext or one of the ATI kexts is not loaded. Please check.Kizwan, unfortunately the new framebuffer gave black screens for VGA, LVDS and HDMI.
Any news on VAIO laptops? As I said I have a 4650 in a VAIO FW 4650 (full HD LVDS) and can't get it to work, I get no signal...
The kext is not loaded, but when it is loaded, I have black screens, and no VNC (that how I know it is loaded)I think the kext or one of the ATI kexts is not loaded. Please check.
You should be able to connected remotely via VNC. If you unable to connected remotely via VNC, it means something wrong is going on, usually some kexts is not loaded.The kext is not loaded, but when it is loaded, I have black screens, and no VNC (that how I know it is loaded)
You should be able to connected remotely via VNC. If you unable to connected remotely via VNC, it means something wrong is going on, usually some kexts is not loaded.
Please post IORegistry dump.I finally tested the new framebuffer. The interesting thing, I could see HDMI screen via VNC. Unfortunately all screens remained black.
02 00 00 00 40 00 00 00 09 01 00 00 12 01 00 07 10 00 00 00 10 00 00 00 00 01 00 00 00 10 01 06 00 08 00 00 00 02 00 00 00 01 00 00 20 01 02 01
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 06 00 08 00 00 00 02 00 00 00 01 00 00 20 01 02 01
this moded shrike for hp pavilion-dv6
you can compare it02 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 06 00 08 00 00 00 02 00 00 00 01 00 00 20 01 02 01
02 00 00 00 40 00 00 00 09 01 00 00 12 [color="#FF0000"]00[/color] 00 07 10 00 00 00 10 00 00 00 00 01 00 00 00 10 01 06 00 08 00 00 00 02 00 00 00 01 00 00 20 01 02 01
The only difference is
02 00 00 00 40 00 00 00 09 01 00 00 12 [color="#FF0000"]00[/color] 00 07 10 00 00 00 10 00 00 00 00 01 00 00 00 10 01 06 00 08 00 00 00 02 00 00 00 01 00 00 20 01 02 01
and I have 01, but it does not matter because I have this issue both with 00 and 01.
The strange is that screenshots are normal. Here is a sample.
dv7 has native resolution 1600x900. maybe this cause a problem.
02 00 00 00 40 00 00 00 09 01 00 00 02 02 00 07 10 00 00 00 10 00 00 00 00 01 00 00 00 10 01 06 00 08 00 00 00 02 00 00 00 01 00 00 20 01 02 01
QUOTE (Misha Vakulich @ Apr 10 2011, 07:28 PM)
finally it works
changed the Shrike personality to
CODE
02 00 00 00 40 00 00 00 09 01 00 00 02 02 00 07
10 00 00 00 10 00 00 00 00 01 00 00 00 10 01 06
00 08 00 00 00 02 00 00 00 01 00 00 20 01 02 01
and fixed the issue with monitor according this guides
http://www.insanelym...howtopic=208410
http://www.insanelym...p;#entry1362685
Now I have 1600x900 with full qe/ci on my internal display.
laptop: hp dv7 2130 with ATI HD4650 [1002:9480]
I was used a tricky method to get it work. I have 2 hdd on my laptop.
On the first drive I have Fedora 14. So for the MacOsX installation and Driver manipulation I'm using VirtualBox that has access to my 2nd hdd.
This method is good for investigating the problems with videocard. because modified ATI framebuffer will not be loading in VirtualBox.
The exact method I was using:
1. I tried ti find a control flags. Tried this values(0x14,0x40,0x100,0x214) this is a control that could be. So if you have a simple black screen you are on right way
2. The same way I was trying the values for transmitter and encoder. when I put encoder 0x00 or 0x01 I can see the desktop but the image was broken.
3. I insert my edid value, make a dsdt patch for dual link. I still had a problems with display.
4. then I start to patch EDID again. in the http://www.insanelym...howtopic=208410 in step 6
Reboot, wait a while, or do whatever it takes to boot so the display is NOT right
so I tried encoder 0x02 and it start work.
maybe you should try other encoders. because it looks like that laptops with resolution higher than 1280x1024 could use other encoders than 0x01 and 0x00