Jump to content

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


majuss
 Share

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 :)

Link to comment
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. 

Link to comment
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.

 

Raw DSDT

Patched DSDT

Link to comment
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.

Link to comment
Share on other sites

 Share

×
×
  • Create New...