Jump to content

Different solutions


Andy Vandijck
 Share

925 posts in this topic

Recommended Posts

hello Andy

 

i test the kext in 10.9 and it don't work..

 

maybe same issue @ wastez

 

i post in a few hours the kext and my ioreg to u take a look.. now i'm working.. no mac os x.. rsrsrsrs

 

maybe a lappy issue

 

thanks

Aargh... this sucks.

I don't have a laptop anymore so I can't test.

I wonder why it doesn't work on laptops.

This needs investigating.

Link to comment
Share on other sites

10.8/10.9 its worked you have copy & paste DisplayProductID-79d and 79e

/System/Library/Displays/Overrides/DisplayVendorID-4c2d

Link to comment
Share on other sites

10.8/10.9 its worked you have copy & paste DisplayProductID-79d and 79e

/System/Library/Displays/Overrides/DisplayVendorID-4c2d

Not with the kext?

In my case I don't use the displayoverride, only installed kext.

Gonna do some tests...

Link to comment
Share on other sites

with or without kext displayoverride worked. may be kext not worked 4 me Because 3 display I try like this

 

<key>IOProviderMergeProperties</key>

<dict>

<key>AppleDisplayType</key>

<integer>1</integer>

<key>AppleSense</key>

<integer>36864</integer>

<key>DisplayProductID</key>

<integer>37426</integer>

<key>DisplayVendorID</key>

<integer>1552</integer>

<key>IODisplayConnectFlags</key>

<data>

xEEAAA==

</data>

<key>IODisplayEDID</key>

<data>

AP///////wAGEDKSfJ8AAioQAQOAPCJ4Kv6Ho1dKnCUT

UFQjCACBgIFAgQCVALMAAQEBAQEBAjqAGHE4LUBYLEUA

VlAhAAAeAAAA/wBDWTY0MjBaNlVHMQoAAAAA/QAYSxpR

FwAKICAgICAgAAAA/ABDaW5lbWEgSEQKAAAAAUICAyjx

SZAfBBMFFAMSICMJBweDAQAA4gAPbgMMABAAAC0gkAQI

EBgQAR0AclHQHiBuKFUAVlAhAAAeAR0AvFLQHiC4KFVA

VlAhAAAeAR2AGHEcFiBYLCUAVlAhAACeAR2A0HIcFiAQ

LCWAVlAhAACeAAAAAAAAAAAAAAAAAAAA1g==

</data>

<key>IODisplayPrefsKey</key>

<string>IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEGP@3/IOPCI2PCIBridge/GFX0@0/NVDA,Display-A@0/NVDA/display0/AppleDisplay-610-9232</string>

</dict>

<key>IOProviderMergeProperties 2</key>

<dict>

<key>AppleDisplayType</key>

<integer>2</integer>

<key>DisplayProductID</key>

<integer>37415</integer>

<key>DisplaySerialNumber</key>

<integer>371392543</integer>

<key>DisplayVendorID</key>

<integer>1552</integer>

<key>IODisplayCapabilityString</key>

<data>

cHJvdChtb25pdG9yKSB0eXBlKExDRCkgbW9kZWwoVGh1

bmRlcmJvbHQgRGlzcGxheSkgY21kcygwMSAwMiAwMyBF

MyBGMykgVkNQKDAyIDA1IDEwIDUyIDYyIDY2IDhEIDkz

IEI2IEMwIEM4IEM5IENBIEQ2KDAxIDAyIDAzIDA0KSBE

RiBFOSBFQiBFRCBGRCkgbWNjc192ZXIoMi4yKQ==

</data>

<key>IODisplayConnectFlags</key>

<data>

AAAAAA==

</data>

<key>IODisplayControllerID</key>

<data>

AAAA/w==

</data>

<key>IODisplayEDID</key>

<data>

AP///////wAGECeSHwAjFiMWAQOAPCJ4Km+xp1VMniUM

UFQjCACBgIFAgQCVALMAAQEBAQEBAjqAGHE4LUBYLEUA

VlAhAAAeAAAA/wBDMDJKOTAwWEYyR0MKAAAA/QAYSxpR

FwAKICAgICAgAAAA/ABUaHVuZGVyYm9sdAogAaoCAyjx

SZAfBBMFFAMSICMJBweDAQAA4gAPbgMMABAAAC0gkAQI

EBgQAR0AclHQHiBuKFUAVlAhAAAeAR0AvFLQHiC4KFVA

VlAhAAAeAR2AGHEcFiBYLCUAVlAhAACeAR2A0HIcFiAQ

LCWAVlAhAACeAAAAAAAAAAAAAAAAAAAA1g==

</data>

<key>IODisplayFirmwareLevel</key>

<data>

//8BOA==

</data>

<key>IODisplayMCCSVersion</key>

<data>

AP///////wAGEDKSfJ8AAioQAQOAPCJ4Kv6Ho1dKnCUT

UFQjCACBgIFAgQCVALMAAQEBAQEBAjqAGHE4LUBYLEUA

VlAhAAAeAAAA/wBDWTY0MjBaNlVHMQoAAAAA/QAYSxpR

FwAKICAgICAgAAAA/ABDaW5lbWEgSEQKAAAAAUICAyjx

SZAfBBMFFAMSICMJBweDAQAA4gAPbgMMABAAAC0gkAQI

EBgQAR0AclHQHiBuKFUAVlAhAAAeAR0AvFLQHiC4KFVA

VlAhAAAeAR2AGHEcFiBYLCUAVlAhAACeAR2A0HIcFiAQ

LCWAVlAhAACeAAAAAAAAAAAAAAAAAAAA1g==

</data>

<key>IODisplayPrefsKey</key>

<string>00020200 </string>

<key>IODisplayTechnologyType</key>

<string>IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEGP@3/IOPCI2PCIBridge/GFX0@0/NVDA,Display-A@0/NVDA/display0/AppleDisplay-610-9227</string>

</dict>

<key>IOProviderMergeProperties 3</key>

<dict>

<key>AppleDisplayType</key>

<integer>3</integer>

<key>AppleSense</key>

<integer>36864</integer>

<key>DisplayProductID</key>

<integer>37426</integer>

<key>DisplayVendorID</key>

<integer>1552</integer>

<key>IODisplayConnectFlags</key>

<data>

xEEAAA==

</data>

<key>IODisplayEDID</key>

<data>

AP///////wAGEDKSfJ8AAioQAQOAPCJ4Kv6Ho1dKnCUT

UFQjCACBgIFAgQCVALMAAQEBAQEBAjqAGHE4LUBYLEUA

VlAhAAAeAAAA/wBDWTY0MjBaNlVHMQoAAAAA/QAYSxpR

FwAKICAgICAgAAAA/ABDaW5lbWEgSEQKAAAAAUICAyjx

SZAfBBMFFAMSICMJBweDAQAA4gAPbgMMABAAAC0gkAQI

EBgQAR0AclHQHiBuKFUAVlAhAAAeAR0AvFLQHiC4KFVA

VlAhAAAeAR2AGHEcFiBYLCUAVlAhAACeAR2A0HIcFiAQ

LCWAVlAhAACeAAAAAAAAAAAAAAAAAAAA1g==

</data>

<key>IODisplayPrefsKey</key>

<string>IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG1@7/IOPCI2PCIBridge/GFX1@0/ATY,Gibba@0/ATIFramebufferNI/display0/AppleDisplay-4c2d-79e</string>

</dict>

</dict>

</dict>

<key>OSBundleRequired</key>

<string>Root</string>

</dict>

</plist>

Link to comment
Share on other sites

Now EDID get more Resolution good job.

Thanks.

Anybody working 3 displays? with kext?

post-413859-0-00943300-1372174012_thumb.png

Link to comment
Share on other sites

I found the issue.
It's in the kext.
I will need to make a new injector based on AppleUSBMergeNub.
Otherwise it won't separate the displays (injects first one in all).
Work continues... ;)

EDIT: Yamayo! Succes!...

Sources for the merging nub are attached here.

I'll compile it and modify the FixEDID app (new version V1.1) ;)

post-100023-0-48295900-1372183375_thumb.png

DisplayMergeNub.zip

Link to comment
Share on other sites

Thats good news

We need patch for 6950/6970 10.9 dp1 AMDRadeonX3000 crying ple do something

Link to comment
Share on other sites

New version V1.1

- Modified driver creation to use the new DisplayMergeNub

- Fixed a bug to get 2nd / 3rd / etc display with button (caused crash)

- Added basic params override for display to be set as LCD

- Fixed Info.plist creation code

 

Everyone, please test and report back.

It should be fixed now ;)

Also some additional fixes done.

Remove Monitor_Apple.kext before you install the new DisplayMergeNub.kext :D

 

For download and sources, see first post :)

 

EDIT: Ooops... forgot to add the OSBundleLibraries to the Info.plist generation.

V1.1b attached in opening post will work right now ;)

I've remove the injector, made an override and I'm gonna test now :D

Yeah! Bingo! Now it works fine!

Below is with auto-generated driver...

 

post-100023-0-20391000-1372189704_thumb.png

  • Like 1
Link to comment
Share on other sites

Thank you Andy, great job, about the .kext generation in V1.1b:

Inside Contents -- Info.plist is generated correctly -- but MacOS folder is empty (no binary), that's ok... or need the "DisplayMergeNub" file inside?

 

Can copy it from here and install the .kext?

/Users/juanerson/Downloads/FixEDID/DisplayMergeNub/Release 10.7/DisplayMergeNub.kext/Contents/MacOS

 

Edited: Worked fine in the second attempt. Please sorry, and thank you again.

Link to comment
Share on other sites

Its worked All In One

post-413859-0-75384300-1372211175_thumb.png

Link to comment
Share on other sites

hello Andy

 

is working

 

retina display.. rsrsrsrsrs

 

null

 

null

 

thanks

You can copy the kext e.g. to documents.

Run the app again.

Change the value from 1 to 2 and click the top right button.

Open the second edid

Set it to Thunderbolt display.

Click make.

It will generate the new driver.

Open the Info.plist of the one in documents and the new one.

Copy the key under IOKitPersonalities and add it under IOKitPersonalities of the second Info.plist.

Save it and install the driver.

Enjoy one display as integrated and one as Thunderbolt :D

EDIT: I'll fix the binary copy.

I forgot to add \" around the %s parts

EDIT: Fixed in the new version

Link to comment
Share on other sites

Now on your desktop you will get the following new files:

- A displayoverride for your display which is patched (probably don't want to use this).

- A EDID binary which is patched (handy for 2nd check with edie-decode).

- DisplayMergeNub.kext auto tailored for your config (probably want to install this).

Hello. I have questions.

1) Should I set up DisplayOverride together with DisplayMergedNub.kext? Or I can set up Either Displayoverride or DisplayMergedNub separately?

2) Do you know the recipe how to get rid of glimmer?

http://www.insanelymac.com/forum/topic/287289-blinking-strips-of-ati-card/

Regards, 

 

Alex.

Link to comment
Share on other sites

Hello. I have questions.

1) Should I set up DisplayOverride together with DisplayMergedNub.kext? Or I can set up Either Displayoverride or DisplayMergedNub?

2) Do you know the recipe how to get rid of glimmer?

http://www.insanelymac.com/forum/topic/287289-blinking-strips-of-ati-card/

Regards,

 

Alex.

1: No I recommend just kext

2: no but I'll check

It's framebuffer patch, not EDID patch.

Clover or ATI****Controller patch will do this just fine ;)

Link to comment
Share on other sites

1: No I recommend just kext

2: no but I'll check

It's framebuffer patch, not EDID patch.

Clover or ATI****Controller patch will do this just fine ;)

Did you mean that glimmer is connected to framebuffer. In this case I cannot find any mistakes at my framebuffer. :(

Link to comment
Share on other sites

Made a new version: V1.2

- Fixed driver file copy bug in case of spaces in path

- Added Apple LED Cinema display data and option

- Added option for only EDID injection (unpatched)

 

Please test, driver copy should work now and extra options added.

If somebody has IORegs with other Apple displays connected (that are worth adding), upload them here.

I can add them to the app. ;)

 

Enjoy the new version :D

Link to comment
Share on other sites

Pardon me Andy, i don't know to post this information so I'm posting here , see the AppleKextExcludeList on /s/l/e on Mavericks DP1 & DP2, i found this http://cl.ly/image/0b3y1z3M120v

 

Why those little Apple engineers...

Apparently they don't like my kexts lol.

They still work at the moment but in the future it might be needed to change the name of the driver...

  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...