Jump to content
About Just Joined group Read more... ×
Sign in to follow this  
Followers 0

Strange display issues - external monitor listed as internal (Asus K73sv)

7 posts in this topic

Recommended Posts

Hello there, 

here is my spec:


Asus 15" K73sv

1600x900 internal screen is completely destroyed

i5 Sandy 2410M

NVidia 540M 1GB

Display output via HDMI & VGA


Using 10.9.3 and latest Chameleon (78)


No custom DSDT



I have really strange display issues.

When I connect a display via HDMI everything just works perfect and I can use a resolution up to 1080p on my BenQ.

Put I'am setting this Asus up for a friend and he only got a VGA Screen with a reso auf 1600x1050. When I connect the laptop via VGA the screen is stretched and flickering like hell. This does not appear with a HDMI display. After I started looking where the problem is coming from I noticed that in the systemsettings the external monitor is listed as an internal so I can set a maximum resolution of 1600x900. While the bootloaders GUI is shown in the native resolution of 1600x1050 but as soon as the loading sun disappears the resolution is setted to 1600x900.


So there are different ways to help me. First thing will be to set the internal resolution easily to 1600x1050 or say the bootloader to load the whole system in this resolution. Second thing is to get the 540M fully functional (what is impossible i think?). Third thing would be loading a custom EDID into the system. (I could extract the EDID via VGA with a other Mac)


Here is the EDID from the external screen extracted with the Asus and the screen is clearly listed as "AppleDisplay":

ioreg -l | grep -5 IODisplayEDID
    | |   | | |     {
    | |   | | |       "IOClass" = "AppleDisplay"
    | |   | | |       "CFBundleIdentifier" = "com.apple.iokit.IOGraphicsFamily"
    | |   | | |       "IOProviderClass" = "IODisplayConnect"
    | |   | | |       "DisplayProductID" = 721
    | |   | | |       "IODisplayEDID" = <00ffffffffffff0030e4d1020000000000140103802615780a88a59d5f579c261c5054000000010101010101010101010101010101012f2640b860840c30303023007ed710000019000000000000000000000000000000000000000000fe004c4720446973706c61790a2020000000fe004c503137335744312d544c4e32002b>
    | |   | | |       "IODisplayPrefsKey" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/GFX0@2/AppleIntelFramebuffer@0/display0/AppleDisplay-30e4-2d1"
    | |   | | |       "IOPowerManagement" = {"MaxPowerState"=3,"CurrentPowerState"=3}
    | |   | | |       "IOProbeScore" = 2000
    | |   | | |       "IODisplayParameters" = {"bgsc"={"min"=0,"max"=65536,"value"=65536},"rgsc"={"min"=0,"max"=65536,"value"=65536},"bklt"={"min"=0,"max"=1808,"value"=0},"ggsc"={"min"=0,"max"=65536,"value"=65536}}
    | |   | | |       "IOMatchCategory" = "IODefaultMatchCategory"

Thanks to everyone who read my rock of a post :)

Share this post

Link to post
Share on other sites

Yeah I mean "read" ^^ It's not my native language.


I will try out the injected EDID tomorrow but I don't think that this will change anything, cause problems caused by wrong EDIDs doesn't show this behavior. 

Share this post

Link to post
Share on other sites

Hmm maybe look for internal screen code in DSDT and strip it?


And/or try using a non-laptop model identifier..? Except that could have undesirable side effects on power management..


Thanks for your reply. Where can I find the internal display in the DSDT? Sorry I'am a newb at editing the DSDT.

The power management is not that important because a external screen is necessary so the "mobility" is not there :D



Here is a patched DSDT (patched with rehabmans patches and others found in the download of "DSDT Editor") and the raw one.



Patched DSDT

Share this post

Link to post
Share on other sites

IF there is code for the screen in DSDT (I guess there is - have never hackintoshed a laptop) you can try to find it with IOJones or IORegistryExplorer (comes with Apple dev tools). Find the GPU in the device tree, the screen will be attached to that.. obviously.. then try to find a three or four letter abbreviation for the screen "device" and look for that in your DSDT.

Share this post

Link to post
Share on other sites
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.


  • Similar Content

    • By Sudo User
      My configuration is:
      Dell XPS 13 9300 Core i7-1065g7 (G7 Iris plus graphics) 16 GB RAM UHD+ monitor (4k: 3840x2400 Touchscreen)  
      The problem that i am currently experiencing is that the internal display is recognised but for some reason is not functioning the way it should. The internal display becomes partially fragmented after few seconds of not doing anything, Although the internal monitor is not functioning, when i connect an external monitor (with FHD resolution) It becomes fully recognised and functioning. When i connect the external monitor the internal monitor becomes blank. With the external monitor i can confirm that i have acceleration.
      Here is a log Boot log.
      Here is the config.
      Here is a picture of the fragmentation.
      Here is a picture when there is an external monitor connected.
    • By b2550
      Currently my install is 100% working except that so far I have only been able to get one of my 1080p monitors working with a MiniDP to HDMI cable. I currently am getting a second MiniDP to HDMI cable but for now I am stuck with a DVI to HDMI cable.

      The monitor that is working is plugged in via the MiniDP to HDMI. The monitor that isn't working is using the DVI cable. However I also tried switching it to HDMI to HDMI which had the same result. The monitor wakes up but it's black. However for whatever reason, both monitors are still recognized in system preferences and hackintool.

      I know all my cables are good and work because I updated from an install of El Capitan (which I still have on it's original SSD just in case this install fails) as well as a Windows install. Both monitors worked fine on El Capitan for literally years. El Capitan is just too old now and I need to update to keep up with software updates.

      Problem reporting files should provide needed info about how I've configured this install. Build is in my signature.