hello i ve found this link about vaio laptop may be a part of the solution:
http://www.popies.net/sonypi/

http://www.linux.it/~malattia/wiki/index.php/Sony_drivers.

that s all i hope it can help

http://www.linux.it/~malattia/wiki/index.p...ny-laptop_note3

this is all backlight/function key/acpi stuff as far as I can tell. I don't think it's useful to the edid issue we are all facing.

actualy in vaio laptop webcam;backlight screen and some keyboard fonction are not enable and those with all kind of driver and because they are linked to screen detection and also laptop display kext don t work on vaio
i saw linux user dont have the problem so did they have the solution for osx .i don t know linux language i mean the problem is we need a kext for vaio to detect the edid i think the manufacturer from the screen should phoenix maybe we had asking them or can it be a problem of dlna i think we must find someone who know osx and linux system to find the solution or someone who know how to code injecter with adress 0 for the screen
can it be a bios problem:don t know can it be smbios problem :in osx description i read macbookpro are able to find themselves internal screen but i can never made mine recognized
like this and not a lot applesmbios work on my machine
i wish hope to all of us in finding help
regards

my point is, the sony pi stuff is for getting the function keys to work (backlight, volume, etc.). These are simply mapping acpi events/controls to keyboard input. It does not appear to have ANY thing to do with our detection issues.

krazubu seems to confirm what i ve posted in september :

http://forum.insanelymac.com/index.php?showtopic=137685

now anybody can do something?

I think he is wrong too. these drivers are mapping acpi events for things like hardware brightness keys, jog dial, etc. it does not "appear" to have anything to do with the display or edid.

Hi guys! Salvation on the way..hopefully..
Development is already on!

Help out by contribute anything useful to the project.

Project Home page: http://code.google.com/p/sonypi-macosx/

Direct to the updates:
http://code.google.com/p/sonypi-macosx/updates/list

Spread the word!

Looks like a good start, but we need to update it with the work that others have already done: adding important ACPI commands like SODV (switch output device) and GDDI (get desktop display interface?).

Maybe try something like with no external screen plugged in, execute the command to send SODV '1' or whatever is necessary to switch to internal display. This could be accomplished remotely or with some kind time delayed script.

Also, does anyone know what clicking Detect Monitors in the system preferences does? Maybe we need to send the command, and then allow the computer to update what interfaces it sees as available.

Finally, will we also need to change the EDID for the internal LCD?

have toshiba p25 (p20 series) and have same problem as vaio users. geforce 5200 fx go 32 MB. Think the problem is:

1. Laptop have soft EDID meaning EDID is injected with the windows drivers. Can you confirm this using softMCCS under windows? (The thing you should look for is DDC communication failure, and/or software monitor enumeration)

i have this in my log

21:25:25.09331...Found device on NVIDIA GeForce FX Go 5200
21:25:25.09332...Monitor ID = NVD Nvidia Defaul
21:25:25.09333...Raw EDID = 00FFFFFFFFFFFF003AC40009000000002D0C010380201400EAA8E099574B92251C50540000000101
01010101010101010101010101019525A04051840C304020330042C910000018000000FC004E76696
469612044656661756C000000FC007420466C61742050616E656C00000000FD00003C1D370A000020
20202020000043
21:25:25.46834...Error: failed to obtain driver output mask
.
.
.
21:25:27.18738...NVD0900 on NVIDIA GeForce FX Go 5200 does not respond to DDC/CI
21:25:27.18739...*******************************************
21:25:27.1873A...Software monitor enumeration
21:25:27.1873B...Monitor #1: NVD Nvidia Defaul


2. try NVidiaEFI.kext version 1.2.3 and boot with -v flag. Look at the output of the driver. my toshiba reports HEAD B display, and apple looks for primary display at HEAD A, thus we see vga and external monitor working with full qe/ci.
Another thing you should investigate using this kext is that it recognizes internal display and switches to full resolution, waits ~5 sec, and again goes on external display. (I have turned off display stretching in bios so i can see when the display goes fullres)

if you confirm those two, then writing the driver mentioned in previous posts .... think it wont help.