x11/nvidia-driver cannot obtain EDID under 8.0-BETA3/i386

[Mel Flynn]

Hi!
Fresh install of 8.0-BETA2 upgraded to 8.0-BETA3 using source,
x.org installed from fresh ports tree. It cannot read EDID from
Samsung 959NF CRT monitor. The same time, it can read EDID under 7.2-STABLE
just fine. I've tried older nvidia-driver-180.60 (downgrading port)
and current port's version 185.18.29, no change.
(WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-1

Can't reproduce this with FreeBSD 8.0-BETA2 #10 r196398M both 180.60 and
185.18.29 driver. World/kernel as of today is building, so I'll report back if
I can reproduce it then.
Different (laptop) monitor though.

[Eugene Grosbein]

Fresh install of 8.0-BETA2 upgraded to 8.0-BETA3 using source,
x.org installed from fresh ports tree. It cannot read EDID from
Samsung 959NF CRT monitor. The same time, it can read EDID under 7.2-STABLE
just fine. I've tried older nvidia-driver-180.60 (downgrading port)
and current port's version 185.18.29, no change.
(WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-1

Just for archives: Samsung 959NF has two inputs, D-Sub and BNC.
For D-Sub, it presents EDID and it does not for BNC that I used.
So, the problem was with monitor connection, not with FreeBSD nor nvidia-driver.

Eugene Grosbein

[Torfinn Ingolfsen]

On Thu, 05 Nov 2009 13:06:55 +0700

Post by Eugene Grosbein
Just for archives: Samsung 959NF has two inputs, D-Sub and BNC.
For D-Sub, it presents EDID and it does not for BNC that I used.
So, the problem was with monitor connection, not with FreeBSD nor nvidia-driver.

Figures. EDID[1] uses DDC2B[2] which is an I2C bus, implemented on two
specific pins of the VGA[3] connector, or the DVI[4] connector.

References:
1) http://en.wikipedia.org/wiki/EDID
2) http://en.wikipedia.org/wiki/Display_Data_Channel#DDC2B
3) http://en.wikipedia.org/wiki/VGA_connector
4) http://en.wikipedia.org/wiki/Digital_Visual_Interface

HTH