DavidRocha Posted July 11, 2013 Share Posted July 11, 2013 My VBIOS ATY_Bin_to_DSDT.rar Link to comment Share on other sites More sharing options...
deschutes Posted July 12, 2013 Share Posted July 12, 2013 @deschutes Try this DSDT at your own risk, framebuffer is set to Ipomoea. DSDT.aml.zip Replaced, sorry for the wrong model name. Hi Trucker, Thanks - I tried with DSDT but had no luck. Now I cleaned up all files and started from the beginning. With pure 10.8.4 ATI6000Controller.kext + Clean latest Chameleon v2.2svn r2254 + No DSDT If I bood with GraphicsEnabler=Yes, HDMI output is always working nicely without any ATIConfig flags. LVDS is always black with backlight turned on. Now I am starting to edit ATI6000Controller.kext. I think it would be better to start with a personality which has same number of connectors (for me, it was five connectors based on vbios extraction) For LVDS, I guss I can just edit first line of the hex values. These are personalities with five connectors : Personality: Hydrilla ConnectorInfo count in decimal: 5 Disk offset in decimal 179664 0000000 02 00 00 00 00 01 00 00 09 01 00 00 12 04 03 03 0000010 00 04 00 00 04 03 00 00 00 01 00 00 11 02 01 01 0000020 00 04 00 00 00 01 00 00 00 09 10 00 21 03 02 02 0000030 00 04 00 00 00 01 00 00 00 09 10 00 22 05 05 04 0000040 00 04 00 00 04 03 00 00 00 01 00 00 10 00 04 05 0000050 Personality: Elodea ConnectorInfo count in decimal: 5 Disk offset in decimal 179872 0000000 02 00 00 00 00 01 00 00 09 01 00 00 12 04 03 03 0000010 00 04 00 00 04 03 00 00 00 01 00 00 10 00 05 05 0000020 00 04 00 00 04 03 00 00 00 01 00 00 11 02 01 01 0000030 00 04 00 00 00 01 00 00 00 09 10 00 21 03 02 02 0000040 00 04 00 00 00 01 00 00 00 09 10 00 22 05 04 04 0000050 Personality: Elodea ConnectorInfo count in decimal: 5 Disk offset in decimal 179872 0000000 02 00 00 00 00 01 00 00 09 01 00 00 12 04 03 03 0000010 00 04 00 00 04 03 00 00 00 01 00 00 10 00 05 05 0000020 00 04 00 00 04 03 00 00 00 01 00 00 11 02 01 01 0000030 00 04 00 00 00 01 00 00 00 09 10 00 21 03 02 02 0000040 00 04 00 00 00 01 00 00 00 09 10 00 22 05 04 04 0000050 Personality: Typha ConnectorInfo count in decimal: 5 Disk offset in decimal 180464 0000000 00 04 00 00 04 03 00 00 00 01 01 00 11 02 04 01 0000010 00 04 00 00 04 03 00 00 00 01 02 00 21 03 05 02 0000020 00 04 00 00 00 01 00 00 00 09 03 00 10 00 02 05 0000030 00 04 00 00 00 01 00 00 00 09 04 00 20 01 03 06 0000040 04 00 00 00 14 02 00 00 00 01 05 00 02 04 01 03 0000050 ----------------------------------------------------------------------------------------------- From these, I chose this Hydrilla, since it is already starting with 02 00 00 00 (LVDS) Personality: Hydrilla ConnectorInfo count in decimal: 5 Disk offset in decimal 179664 0000000 02 00 00 00 00 01 00 00 09 01 00 00 12 04 03 03 0000010 00 04 00 00 04 03 00 00 00 01 00 00 11 02 01 01 0000020 00 04 00 00 00 01 00 00 00 09 10 00 21 03 02 02 0000030 00 04 00 00 00 01 00 00 00 09 10 00 22 05 05 04 0000040 00 04 00 00 04 03 00 00 00 01 00 00 10 00 04 05 0000050 For this first line, I editied based on following vbios information for LVDS : PCI ID: 1002:6841 Connector at index 0 Type [@offset 44650]: LVDS (7) = Encoder [@offset 44654]: INTERNAL_UNIPHY (0x1e) i2cid [@offset 44760]: 0x90, OSX senseid: 0x1 Connector at index 1 Type [@offset 44660]: DisplayPort (10) Encoder [@offset 44664]: INTERNAL_UNIPHY1 (0x20) i2cid [@offset 44783]: 0x94, OSX senseid: 0x5 Connector at index 2 Type [@offset 44670]: DisplayPort (10) Encoder [@offset 44674]: INTERNAL_UNIPHY1 (0x20) i2cid [@offset 44810]: 0x91, OSX senseid: 0x2 Connector at index 3 Type [@offset 44680]: DisplayPort (10) Encoder [@offset 44684]: INTERNAL_UNIPHY2 (0x21) i2cid [@offset 44837]: 0x92, OSX senseid: 0x3 Connector at index 4 Type [@offset 44690]: VGA (1) Encoder [@offset 44694]: INTERNAL_KLDSCP_DAC1 (0x15) i2cid [@offset 44864]: 0x97, OSX senseid: 0x8 HP/Foxconn Casper Thames Pro GDDR5 128Mx16 64bit 500e/600m 0.9V Subsystem Vendor ID: 103c Subsystem ID: 17a9 Object Header Structure Size: 332 Connector Object Table Offset: 48 Router Object Table Offset: 0 Encoder Object Table Offset: f3 Display Path Table Offset: 12 Connector Object Id [14] which is [LVDS] encoder obj id [0x1e] which is [iNTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false Connector Object Id [19] which is [DISPLAY_PORT] encoder obj id [0x20] which is [iNTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false Connector Object Id [19] which is [DISPLAY_PORT] encoder obj id [0x20] which is [iNTERNAL_UNIPHY1 (osx txmit 0x21 [duallink 0x1] enc 0x3)] linkb: true Connector Object Id [19] which is [DISPLAY_PORT] encoder obj id [0x21] which is [iNTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false Connector Object Id [5] which is [VGA] encoder obj id [0x15] which is [iNTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false Hydrilla 02 00 00 00 40 00 00 00 09 01 00 00 10 00 01 01 Not sure about this control flag part. I think this ATI/AMD ROM Output Features is set correctly to LVDS and Internal : 0x01 and 0x09 For Transmitter and Encoder, I used 10 and 00. Not sure if this is correct. This is my current situation Still having no luck with LVDS. If you have and advice, it would be really appreciated. Thanks! Link to comment Share on other sites More sharing options...
freeuser16 Posted July 13, 2013 Share Posted July 13, 2013 @deschutes, try transmitter 10 + encoder 01. But if it works, probably you will have gradients. Control flags 40 00 00 00 usually work the best, but if the trick with encoder doesn't work you can try control flags from different framebuffers. Link to comment Share on other sites More sharing options...
Flix1337 Posted July 15, 2013 Share Posted July 15, 2013 Hi, I want to get the AMD Radeon 6550M working on my Laptop. I managed to install and start OSX. My Problem is now the native Resolution. I tried many kexts I found but nothing works. Can anyone help? VBios Dump and my DSDT extracted with AIDA64 are in the Attachment. I hope they are the right files. Files.zip Link to comment Share on other sites More sharing options...
Trucker MK Posted July 17, 2013 Author Share Posted July 17, 2013 Hi Trucker, Thanks - I tried with DSDT but had no luck. Now I cleaned up all files and started from the beginning. With pure 10.8.4 ATI6000Controller.kext + Clean latest Chameleon v2.2svn r2254 + No DSDT If I bood with GraphicsEnabler=Yes, HDMI output is always working nicely without any ATIConfig flags. LVDS is always black with backlight turned on. Now I am starting to edit ATI6000Controller.kext. I think it would be better to start with a personality which has same number of connectors (for me, it was five connectors based on vbios extraction) For LVDS, I guss I can just edit first line of the hex values. These are personalities with five connectors : Personality: Hydrilla ConnectorInfo count in decimal: 5 Disk offset in decimal 179664 0000000 02 00 00 00 00 01 00 00 09 01 00 00 12 04 03 03 0000010 00 04 00 00 04 03 00 00 00 01 00 00 11 02 01 01 0000020 00 04 00 00 00 01 00 00 00 09 10 00 21 03 02 02 0000030 00 04 00 00 00 01 00 00 00 09 10 00 22 05 05 04 0000040 00 04 00 00 04 03 00 00 00 01 00 00 10 00 04 05 0000050 Personality: Elodea ConnectorInfo count in decimal: 5 Disk offset in decimal 179872 0000000 02 00 00 00 00 01 00 00 09 01 00 00 12 04 03 03 0000010 00 04 00 00 04 03 00 00 00 01 00 00 10 00 05 05 0000020 00 04 00 00 04 03 00 00 00 01 00 00 11 02 01 01 0000030 00 04 00 00 00 01 00 00 00 09 10 00 21 03 02 02 0000040 00 04 00 00 00 01 00 00 00 09 10 00 22 05 04 04 0000050 Personality: Elodea ConnectorInfo count in decimal: 5 Disk offset in decimal 179872 0000000 02 00 00 00 00 01 00 00 09 01 00 00 12 04 03 03 0000010 00 04 00 00 04 03 00 00 00 01 00 00 10 00 05 05 0000020 00 04 00 00 04 03 00 00 00 01 00 00 11 02 01 01 0000030 00 04 00 00 00 01 00 00 00 09 10 00 21 03 02 02 0000040 00 04 00 00 00 01 00 00 00 09 10 00 22 05 04 04 0000050 Personality: Typha ConnectorInfo count in decimal: 5 Disk offset in decimal 180464 0000000 00 04 00 00 04 03 00 00 00 01 01 00 11 02 04 01 0000010 00 04 00 00 04 03 00 00 00 01 02 00 21 03 05 02 0000020 00 04 00 00 00 01 00 00 00 09 03 00 10 00 02 05 0000030 00 04 00 00 00 01 00 00 00 09 04 00 20 01 03 06 0000040 04 00 00 00 14 02 00 00 00 01 05 00 02 04 01 03 0000050 ----------------------------------------------------------------------------------------------- From these, I chose this Hydrilla, since it is already starting with 02 00 00 00 (LVDS) Personality: Hydrilla ConnectorInfo count in decimal: 5 Disk offset in decimal 179664 0000000 02 00 00 00 00 01 00 00 09 01 00 00 12 04 03 03 0000010 00 04 00 00 04 03 00 00 00 01 00 00 11 02 01 01 0000020 00 04 00 00 00 01 00 00 00 09 10 00 21 03 02 02 0000030 00 04 00 00 00 01 00 00 00 09 10 00 22 05 05 04 0000040 00 04 00 00 04 03 00 00 00 01 00 00 10 00 04 05 0000050 For this first line, I editied based on following vbios information for LVDS : PCI ID: 1002:6841 Connector at index 0 Type [@offset 44650]: LVDS (7) = Encoder [@offset 44654]: INTERNAL_UNIPHY (0x1e) i2cid [@offset 44760]: 0x90, OSX senseid: 0x1 Connector at index 1 Type [@offset 44660]: DisplayPort (10) Encoder [@offset 44664]: INTERNAL_UNIPHY1 (0x20) i2cid [@offset 44783]: 0x94, OSX senseid: 0x5 Connector at index 2 Type [@offset 44670]: DisplayPort (10) Encoder [@offset 44674]: INTERNAL_UNIPHY1 (0x20) i2cid [@offset 44810]: 0x91, OSX senseid: 0x2 Connector at index 3 Type [@offset 44680]: DisplayPort (10) Encoder [@offset 44684]: INTERNAL_UNIPHY2 (0x21) i2cid [@offset 44837]: 0x92, OSX senseid: 0x3 Connector at index 4 Type [@offset 44690]: VGA (1) Encoder [@offset 44694]: INTERNAL_KLDSCP_DAC1 (0x15) i2cid [@offset 44864]: 0x97, OSX senseid: 0x8 HP/Foxconn Casper Thames Pro GDDR5 128Mx16 64bit 500e/600m 0.9V Subsystem Vendor ID: 103c Subsystem ID: 17a9 Object Header Structure Size: 332 Connector Object Table Offset: 48 Router Object Table Offset: 0 Encoder Object Table Offset: f3 Display Path Table Offset: 12 Connector Object Id [14] which is [LVDS] encoder obj id [0x1e] which is [iNTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false Connector Object Id [19] which is [DISPLAY_PORT] encoder obj id [0x20] which is [iNTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false Connector Object Id [19] which is [DISPLAY_PORT] encoder obj id [0x20] which is [iNTERNAL_UNIPHY1 (osx txmit 0x21 [duallink 0x1] enc 0x3)] linkb: true Connector Object Id [19] which is [DISPLAY_PORT] encoder obj id [0x21] which is [iNTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false Connector Object Id [5] which is [VGA] encoder obj id [0x15] which is [iNTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false Hydrilla 02 00 00 00 40 00 00 00 09 01 00 00 10 00 01 01 Not sure about this control flag part. I think this ATI/AMD ROM Output Features is set correctly to LVDS and Internal : 0x01 and 0x09 For Transmitter and Encoder, I used 10 and 00. Not sure if this is correct. This is my current situation Still having no luck with LVDS. If you have and advice, it would be really appreciated. Thanks! 1. Boot with clean ATI6000Controller.kext with GE=Yes and check in IORegExplorer which framebuffer is loaded by default (maybe its better to start with this one) 2. Change back the HotplugID from 01 to 03, you already have 01 in Hydrilla on the second port Personality: Hydrilla ConnectorInfo count in decimal: 5 Disk offset in decimal 179664 0000000 02 00 00 00 00 01 00 00 09 01 00 00 12 04 03 03 (02 00 00 00 40 00 00 00 09 01 00 00 10 00 01 01) 0000010 00 04 00 00 04 03 00 00 00 01 00 00 11 02 01 01 0000020 00 04 00 00 00 01 00 00 00 09 10 00 21 03 02 02 0000030 00 04 00 00 00 01 00 00 00 09 10 00 22 05 05 04 0000040 00 04 00 00 04 03 00 00 00 01 00 00 10 00 04 05 0000050 3. Try different Transmitter/Encoder values (in my VBIOS i also have transmitter/encoder 10/00 but its working with 20/01 when i use GE=Yes 4. Try with AtiPorts=X flag, where X is the number of the ports you have. Good luck. Hi, I want to get the AMD Radeon 6550M working on my Laptop. I managed to install and start OSX. My Problem is now the native Resolution. I tried many kexts I found but nothing works. Can anyone help? VBios Dump and my DSDT extracted with AIDA64 are in the Attachment. I hope they are the right files. Do you have switchable graphics? Link to comment Share on other sites More sharing options...
Trucker MK Posted July 18, 2013 Author Share Posted July 18, 2013 My VBIOSI will take a look this weekend. Link to comment Share on other sites More sharing options...
freeuser16 Posted July 18, 2013 Share Posted July 18, 2013 @Trucker, I did some research on gradients problem. My original EDID decoded with DarwinDumper: Extracted contents: header: 00 ff ff ff ff ff ff 00 serial number: 30 e4 dc 02 00 00 00 00 00 14 version: 01 03 basic params: 80 22 13 78 0a chroma info: a9 05 9f 5e 58 9c 26 19 50 54 established: 00 00 00 standard: 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 descriptor 1: 58 1b 56 7e 50 00 0e 30 24 30 35 00 58 c2 10 00 00 19 descriptor 2: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 descriptor 3: 00 00 00 fe 00 4c 47 20 44 69 73 70 6c 61 79 0a 20 20 descriptor 4: 00 00 00 fe 00 4c 50 31 35 36 57 48 34 2d 54 4c 41 31 extensions: 00 checksum: 79 And the one which works without gradients: Extracted contents: header: 00 ff ff ff ff ff ff 00 serial number: 06 af 2c 12 00 00 00 00 00 16 version: 01 04 basic params: 90 1d 10 78 02 chroma info: 19 c5 a0 58 52 95 26 0d 50 54 established: 00 00 00 standard: 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 descriptor 1: 26 1b 56 64 50 00 16 30 30 20 36 00 25 a4 10 00 00 18 descriptor 2: 00 00 00 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 20 descriptor 3: 00 00 00 fe 00 41 55 4f 0a 20 20 20 20 20 20 20 20 20 descriptor 4: 00 00 00 fe 00 42 31 33 33 58 54 46 30 31 2e 32 20 0a extensions: 00 checksum: 25 Obviously, key parameters are "basic params" and "chroma info". Firstly, I tried replacing "chroma info" values in my EDID with the ones found in new EDID - no difference. Then I left "chroma info" the same, but replaced "basic params" instead and it worked without gradients! I looked deeper and compared "basic params" in both EDIDs: My original: 80 22 13 78 0a New EDID: 90 1d 10 78 02 It's enough to replace only the first byte in original EDID (=> 90 22 13 78 0A) and it works without gradients! From Wikipedia (http://en.wikipedia.org/wiki/Extended_display_identification_data) we know, what are bits in this byte responsible for. 80 == 10 00 00 00, 90 == 10 01 00 00. So, only the 4th bit is different. And this is very weird. Since 7th bit is 1, this is a digital display. Thus, Bit 7=1 Digital input. If set, the following bit definitions apply: Bits 6–1 Reserved, must be 0 But if bits 6-1 are 0's (as in my original EDID), I have wrong colors or gradients when wrong encoder is set. I checked some EDID's from Apple monitors - they also don't have 0's in bits 6-1! Anyway, original EDID now works for me if I replace only one number there. Next thing I did was replacing "chroma info" with the one from Apple display. They say (http://www.insanelymac.com/forum/topic/290077-get-your-display-recognized-and-working-as-imac-thunderbolt-macbook-pro-or-cinema-hd-display/) colors are better then. Personally, I saw no difference, but it's working good so I left it. I also changed serial number to the one from Apple display and added descriptor with monitor name. Result is cosmetic, but looks good, doesn't it? 2 Link to comment Share on other sites More sharing options...
Trucker MK Posted July 18, 2013 Author Share Posted July 18, 2013 Well done, congrats. I will try the same for the weekend, last time i tried to inject different EDID with DSDT i had some success, i was getting black screen, i guess this should work. Thanks for sharing and once again, well done. Link to comment Share on other sites More sharing options...
freeuser16 Posted July 18, 2013 Share Posted July 18, 2013 You still have to inject EDID to make it work. If DSDT injection doesn't work, you can try DisplayMergeNub.kext. Maybe it works this way BTW, I forgot to say - to get this "Built-in LG Display" line I had to replace one of descriptors with "00 00 00 FC 00 4C 47 0A 20 20 20 20 20 20 20 20 20 20" (FC means it's display name and 4C 47 are letters "LG". 0A shows this is the end of string and the rest of the space is filled with 20). Also it works only if you have serial number from Apple display. All in all, my new EDID looks like this: 00 FF FF FF FF FF FF 00 06 10 12 A0 00 00 00 00 1C 16 <= Serial from Apple iMac display 01 04 90 22 13 78 0A <= Gradients fix 6F B1 A7 55 4C 9E 25 0C 50 54 <= Apple Colors 00 00 00 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 58 1B 56 7E 50 00 0E 30 24 30 35 00 58 C2 10 00 00 19 00 00 00 FC 00 4C 47 0A 20 20 20 20 20 20 20 20 20 20 <= Descriptor for Built-in LG Display 00 00 00 FE 00 38 4C 1E 53 11 00 0A 20 20 20 20 20 20 00 00 00 FF 00 4C 50 31 35 36 57 48 0A 20 20 20 20 20 00 0D Link to comment Share on other sites More sharing options...
deschutes Posted July 19, 2013 Share Posted July 19, 2013 Hi Trucker, With pure ATI6000Controller.kext and GraphicsEnabler=Yes, I got this IOReg (attached) As I mentioned, external display port is working with this (I am writing this post with external monitor now:) ). LVDS is black+backlight Under GFX, AMD6000Controller, I see ATY,Gibba, ATY,Lotus, ATY,Muskgrass. And there are three ATY,Pondweed elements under GFX. Does this mean one of these personality has been used for display port with correct framebuffer? And I can tweak it for LVDS? Thanks! 7570M.ioreg.zip Link to comment Share on other sites More sharing options...
Trucker MK Posted July 19, 2013 Author Share Posted July 19, 2013 Pondweed is loaded as default framebuffer, you should start editing this one. Link to comment Share on other sites More sharing options...
grexai926 Posted July 20, 2013 Share Posted July 20, 2013 Hey @Trucker MKDo you have any idea why power off doesn't work correctly? My problem is ( you remember ati 6470M i use dsdt that you written + os x 10.8.3 patched kext) when i go to switch off computer its starts to shut down, and then the computer doesn't swich off only black screen.Other question does My DSDT works with mavericks10.9? Link to comment Share on other sites More sharing options...
Trucker MK Posted July 20, 2013 Author Share Posted July 20, 2013 Is it like this from the monent you started to use the DSDT, try to apply the shutdown patch with DSDTParser, and yes, your DSDT will work with Mavericks, but you need patched kext. Link to comment Share on other sites More sharing options...
czar Posted July 20, 2013 Share Posted July 20, 2013 Need help on my 6650m.. I don't understand all of this but did made a dump. Been trying all i could but came up a black screen during boot everytime. :/ vgabios.dmp.zip GPUReport.txt Link to comment Share on other sites More sharing options...
Trucker MK Posted July 21, 2013 Author Share Posted July 21, 2013 Need help on my 6650m.. I don't understand all of this but did made a dump. Been trying all i could but came up a black screen during boot everytime. :/ You have different VBIOS, that's why you get black screen. Let me know your OS X version, i will patch a new kext for you if you can't do it your self. I also need your DSDT, EDID and IORegistryExplorer dump. ATOM BIOS Rom: SubsystemVendorID: 0x144d SubsystemID: 0xc0ac IOBaseAddress: 0xd000 Filename: BR39495.928 BIOS Bootup Message: Samsung Veyron3D HRV Whistler Pro DDR3 64Mx16/128Mx16 600E/800M PCI ID: 1002:6741 Connector at index 0 Type [@offset 44848]: eDP (14) Encoder [@offset 44852]: INTERNAL_UNIPHY2 (0x21) i2cid [@offset 44922]: 0x92, OSX senseid: 0x3 Connector at index 1 Type [@offset 44858]: HDMI-A (11) Encoder [@offset 44862]: INTERNAL_UNIPHY1 (0x20) i2cid [@offset 44949]: 0x90, OSX senseid: 0x1 Connector at index 2 Type [@offset 44868]: VGA (1) Encoder [@offset 44872]: INTERNAL_KLDSCP_DAC1 (0x15) i2cid [@offset 44976]: 0x97, OSX senseid: 0x8 device-1e2c4e:VBIOS trucker$ Samsung Veyron3D HRV Whistler Pro DDR3 64Mx16/128Mx16 600E/800M Subsystem Vendor ID: 144d Subsystem ID: c0ac Object Header Structure Size: 226 Connector Object Table Offset: 34 Router Object Table Offset: 0 Encoder Object Table Offset: 9d Display Path Table Offset: 12 Connector Object Id [20] which is [EDP] encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false Connector Object Id [12] which is [HDMI_TYPE_A] encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false Connector Object Id [5] which is [VGA] encoder obj id [0x15] which is [INTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false Hi, I want to get the AMD Radeon 6550M working on my Laptop. I managed to install and start OSX. My Problem is now the native Resolution. I tried many kexts I found but nothing works. Can anyone help? VBios Dump and my DSDT extracted with AIDA64 are in the Attachment. I hope they are the right files. No AtomBios signature found in this VBIOS. you probably have switchable graphics and your integrated GPU is not disabled. Can't help you. can anyone help me? Can you attach a file from IORegistryExplorer ? Link to comment Share on other sites More sharing options...
Trucker MK Posted July 21, 2013 Author Share Posted July 21, 2013 @ freeuer16 I tried the DisplayMergeNub.kext, it still does not inject my modified EDID (i can see in IOREg my original EDID) but i definitely see some improvement. Without DisplayMergeNub.kext With DisplayMergeNub.kext You can see here the gradients all over the lower part on the X Edit. I managed to inject the modified EDID with DisplayMergeNub.kext + Display Override file (DisplayVendorID and DisplayProductID in Display Overrides) but the result is the same. I would say that now we are from 16-bit color Pixel Depth to 24-bit color Pixel Depth, but not yet at 32-bit color Pixel Depth. I will do some more tests. Link to comment Share on other sites More sharing options...
freeuser16 Posted July 21, 2013 Share Posted July 21, 2013 Great news! If you see an improvement, then probably EDID is at least somehow injected. You probably just need a bit different "basic params" value than me. Values from your original EDID: 80 26 15 78 0A I think only the first and last bytes (80 and 0A) might have effect on gradients. 26 and 15 are dimensions of your screen (38 x 21 cm if you convert these numbers to decimal) and 78 is display gamma, but it was 78 on all EDIDs I have seen so far. Link to comment Share on other sites More sharing options...
Trucker MK Posted July 21, 2013 Author Share Posted July 21, 2013 I also used serial from MacBookPro and i did not replaced the Chroma info, i will try to change these and report back. Link to comment Share on other sites More sharing options...
Trucker MK Posted July 21, 2013 Author Share Posted July 21, 2013 @ freeuser16 Any suggestions for the "Basic Parameters" value? I will keep looking but this now is much better then it was before, maybe i can live with this. Link to comment Share on other sites More sharing options...
Trucker MK Posted July 21, 2013 Author Share Posted July 21, 2013 Do you have this at the end of the DarwinDumper Report? EDID block does NOT conform to EDID 1.3! Missing monitor ranges Detailed block string not properly terminated Link to comment Share on other sites More sharing options...
freeuser16 Posted July 21, 2013 Share Posted July 21, 2013 Do you have this at the end of the DarwinDumper Report? EDID block does NOT conform to EDID 1.3! Missing monitor ranges Detailed block string not properly terminated Yes, I have both warnings. And you know what.. Adding those monitor ranges actually gave me gradients back, so I left it without them Don't know what's wrong with Detailed block string though, it looks correct to me. @ freeuser16 Any suggestions for the "Basic Parameters" value? I will keep looking but this now is much better then it was before, maybe i can live with this. As I said, you should try different values for the first and last byte, the middle ones are ok. It's a good idea to try something from Apple monitors: iMac: B5 30 1B 78 22 => B5 26 15 78 22 MBP: A5 1D 12 78 02 => A5 26 15 78 02 Cinema HD: 80 40 28 78 2A => 80 26 15 78 2A Thunderbolt: B5 3C 22 78 22 => Same as iMac Led Cinema: A5 34 20 78 26 => A5 26 15 78 26 Link to comment Share on other sites More sharing options...
Trucker MK Posted July 21, 2013 Author Share Posted July 21, 2013 OK thanks, i will try these, but later, i had enough for today . Link to comment Share on other sites More sharing options...
freeuser16 Posted July 21, 2013 Share Posted July 21, 2013 Wait, it might also depend on injected properties! I, for example, still have gradients with the same EDID if I enable the card with Clover graphics injector instead of DSDT (I use device-properties string, but it's the same). Thus you should also try basic params 90 26 15 78 0A + injection of the same properties as me. Except "AAPL00,override-no-connect" maybe, since this is my EDID injection. I attach plist file with these properties. device-properties.plist.zip Link to comment Share on other sites More sharing options...
Trucker MK Posted July 21, 2013 Author Share Posted July 21, 2013 Thanks man, i will try this tomorrow. Now i am already in the bed, i need to be "up & running" tomorrow at 5 AM. Link to comment Share on other sites More sharing options...
Trucker MK Posted July 22, 2013 Author Share Posted July 22, 2013 I've made two quick tests, i added these strings to my DSDT ( these are relevant for the gradients issue). The result is the same. "@0,display-link-component-bits", Buffer (0x04) { 0x06, 0x00, 0x00, 0x00 }, "@0,display-pixel-component-bits", Buffer (0x04) { 0x06, 0x00, 0x00, 0x00 }, "@0,display-dither-support", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "AAPL00,Dither", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, I also tried all the strings you use but i get black screen. EDIT. Except "AAPL00,override-no-connect" , i already tried some time ago but it did not inject the EDID. Next thing i will try to add the string one by one and test with every new string added. Link to comment Share on other sites More sharing options...
Recommended Posts