Vilczech18 i have no lines on launchpad whatsoever, so i might not have the the 16bit collor problem, which version are you running? 10.7.3?
what frambeuffer are you using? it makes a diference, i am using Hoolock
111 replies to this topic
#101
Posted 13 March 2012 - 08:02 PM
#102
Posted 14 March 2012 - 03:53 AM
I think the display is running in millions of colours correctly because the corruption occurs only on some textures. 3D games are really bad, launchpad too (depending on the wallpaper you use) - but an image open in Chrome will be rendered correctly. It's perplexing. My best guess, the frame buffer isn't a perfect fit and is mangling texture compression.
#103
Posted 14 March 2012 - 08:48 AM
#104
Posted 14 March 2012 - 09:28 AM
ok try changing your framebuffer to Hoolock using chameleon wizard.
if it doesnt work, and you can't boot back into desktop, boot with GraphicsEnabler=No and then change back to Orangutan.
But right now, Hoolock seems to have the best performance yet.
if it doesnt work, and you can't boot back into desktop, boot with GraphicsEnabler=No and then change back to Orangutan.
But right now, Hoolock seems to have the best performance yet.
#105
Posted 15 March 2012 - 03:39 AM
I was looking at ioreg explorer last night, and the connected display type shows up as crt. That would mess up a few things... I'll post details when I get home.
#106
Posted 16 March 2012 - 05:59 PM
so any news on your crt problem? ill see to post a ioreg dump here later as well maybe we can compare some stuff and see where the problem is.
#107
Posted 17 March 2012 - 09:25 PM
Sounds like a good idea, just hadn't had time to look into it. Will post up relevant bits soon as I can.
#108
Posted 02 April 2012 - 05:38 PM
Pockets69, on 13 March 2012 - 08:02 PM, said:
Vilczech18 i have no lines on launchpad whatsoever, so i might not have the the 16bit collor problem, which version are you running? 10.7.3?
what frambeuffer are you using? it makes a diference, i am using Hoolock
what frambeuffer are you using? it makes a diference, i am using Hoolock
Are you saying that using Hoolock as frame buffer, your laptop's built-in display is showing SMOOTH GRADIENT, unlike everyone else with AMD 5650 and 6550? Well then, set your wallpaper to either "Ladybug" or "Eagle & Waterfall", then run Launchpad and see if you don't see the same 10-bit type banding effect as these screenies*:
P1060492.JPG 206.65K
114 downloads
P1060493.JPG 208.85K
107 downloadsThe above are shot with a camera instead of screen-captured because once output to a proper display capable of 32 bit color, the banding artifact will be gone.
BTW, Hoolock isn't the only frame buffer to use, not at all, or at least not on my 6550 card. Before this, I always held on to the superstition (thanks to this thread and others) that Hoolock is where it's at. Last weekend I sat down with 2 pints and went through every goddamn ATI frame buffer on the list. My finding is nothing short of amazing.
There are plenty of frame buffers that work EXACTLY LIKE Hoolock: Same exact performance, same 10-bit banding on the built in display, same blank output on external display. I sat patiently through it all, typing "GraphicsEnabler-Y AtiConfig=xxxxx" on each reboot, spell checking carefully each time. I really thought I could strike gold and find the perfect frame buffer that will give me that elusive 32-bit color on the internal display.
Sadly, I came up with none. I think the ATI5000Controller KEXT is to blame. After all, if the KEXT is working right, then we should be able to use the display ports for external output.
Fortunately, my effort wasn't completely wasted. I found one frame buffer that manages to do what others wouldn't. So without further ado, try and set this on your Chameleon Wizard:
AtiConfig=Langur
#109
Posted 05 April 2012 - 12:22 PM
Thx man, I'll try.
#110
Posted 12 May 2012 - 07:38 AM
Langur made no difference for me... I still think kext works fine, just the display parameters are messed up.
#111
Posted 21 May 2012 - 06:24 PM
I am able to get to the screen with GraphicsEnabler=No 100% times with FULL Resolution 1920x1080 but with No QE/CI but the moment I change it to Yes I get sometimes blank display with little backlight, sometimes little blurred display, sometimes overlapped display and sometimes mindblowing fully working display.. Framebuffer can be Hoolock or Eulemur doesn't make any difference. I am using all vanila kexts with vanila boot file from Chimera 1.9. Using the boot file from famous r875 makes no difference either.
EDID is extracted using Win7 and put in place of overrides directory properly. I am able to see all supported resolutions and change them when GE is set to Yes. With GE=No only one resolution appears and that is final. I am thinking of changing ATI5000Controller.kext to try and change the connector info but I am not able to get the senseid using radeon bios decode so the possible permutations are very huge to use trial and error method.
I just need right directions or hint to proceed from here..
Please help I am very close to get a nearly working hackintosh laptop
EDID is extracted using Win7 and put in place of overrides directory properly. I am able to see all supported resolutions and change them when GE is set to Yes. With GE=No only one resolution appears and that is final. I am thinking of changing ATI5000Controller.kext to try and change the connector info but I am not able to get the senseid using radeon bios decode so the possible permutations are very huge to use trial and error method.
I just need right directions or hint to proceed from here..
Please help I am very close to get a nearly working hackintosh laptop
#112
Posted 27 January 2013 - 10:36 PM
Some progress here)
I have successfully avoid problem of 16bit colors
I'm using Clover bootloader
So the recipe is:
Try to injecting EDID with clover, I have found that an editing DisplayProductID-717 causing wrong definition of LVDS. OS X shows it as an external display.
For this you must delete or return original DisplayProductID-717
And configure clover <key>CustomEDID</key> with your EDID
then
<key>InjectEDID</key>
<string>Yes</string>
That's it. This solves my problem with correct connectors and 16bit colors(gradients) on my ATI 5470m
I have successfully avoid problem of 16bit colors
I'm using Clover bootloader
So the recipe is:
Try to injecting EDID with clover, I have found that an editing DisplayProductID-717 causing wrong definition of LVDS. OS X shows it as an external display.
For this you must delete or return original DisplayProductID-717
And configure clover <key>CustomEDID</key> with your EDID
then
<key>InjectEDID</key>
<string>Yes</string>
That's it. This solves my problem with correct connectors and 16bit colors(gradients) on my ATI 5470m
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users



Sign In
Create Account








