[Openchrome-devel] [Bug 94277] driver does not detect VGA monitor, but there is one

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=94277

--- Comment #3 from Kevin Brace <kevinbrace at gmx.com> ---
(In reply to Benno Schulenberg from comment #0)

Hi Benno,

> Created attachment 121938 [details]
> Xorg.0.log with forcibly "detected" output
> 
> Version 0.3.3 of the openchrome driver (or the one from git) does not detect
> any monitor being connected to the VGA port.  But it has a TFT monitor
> connected to it, that apparently does not have an EDID.  See below the
> snippet where it tries to detect the output.  Setting the option
> "ActiveDevice" to "CRT", or "VBEModes" to "True" doesn't help.
> 
> Attached is an Xorg.0.log where I have forced the output to being seen as
> connected, with the attached brute-force patch.  Then I get an image on the
> screen.  Things appear to work, but feel more sluggish than with the vesa
> driver, probably because there is no drm support in the kernel.
> 
> [    22.058] (II) CHROME(0): ViaOutputsDetect
> [    22.058] (**) CHROME(0): Option "PanelSize" "1280x1024"
> [    22.058] (==) CHROME(0): LVDS-0 : Digital output bus width is 12 bits.
> [    22.058] (==) CHROME(0): LVDS-0 : DVI Center is disabled.
> [    22.058] (==) CHROME(0): LVDS Panel will not be forced.
> [    22.058] (II) CHROME(0): ViaPanelGetNativeModeFromOption
> [    22.058] (**) CHROME(0): LVDS Panel mode index is 4
> [    22.058] (**) CHROME(0): Selected Panel Size is 1280x1024
> [    22.058] (II) CHROME(0): Entered via_analog_init.
> [    22.059] (II) CHROME(0): Output VGA-1 using monitor section Panel
> [    22.059] (II) CHROME(0): Exiting via_analog_init.
> [    22.059] (II) CHROME(0): Entered via_tv_init.
> [    22.059] (--) CHROME(0): Did not detect a TV encoder.
> [    22.059] (II) CHROME(0): Exiting via_tv_init.
> [    22.059] (II) CHROME(0): Entered via_dvi_init.
> [    22.060] (--) CHROME(0): VT1632A not found on I2C Bus 2 or I2C Bus 3.
> [    22.060] (II) CHROME(0): Exiting via_dvi_init.
> [    22.060] (II) CHROME(0): I2C device "I2C Bus 1:ddc2" registered at
> address 0xA0.
> [    22.067] (--) CHROME(0): Test for CRT with VSYNC
> [    22.067] (II) CHROME(0): EDID for output VGA-1
> [    22.067] (II) CHROME(0): Output VGA-1 disconnected
> [    22.067] (WW) CHROME(0): No outputs definitely connected, trying again...
> [    22.067] (II) CHROME(0): Output VGA-1 disconnected
> [    22.067] (WW) CHROME(0): Unable to find connected outputs - setting
> 1024x768 initial framebuffer
> [    22.067] (II) CHROME(0): Using default gamma of (1.0, 1.0, 1.0) unless
> otherwise stated.
> [    22.067] (**) CHROME(0): Display dimensions: (375, 300) mm
> [    22.067] (**) CHROME(0): DPI set to (69, 65)

I read the log, and I am starting to think that maybe the VGA connector's I2C
bus is connected to I2C bus 2.
I just uploaded a patch I originally uploaded for Bug 91966.
If the patch works, then it confirms my hypothesis.
    Just to let you know, I also have a mainboard with KM400 chipset from
Foxconn, and this one works fine with the current OpenChrome.
Of course, in that mainboard, I2C bus 1 is connected to the VGA connector.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/openchrome-devel/attachments/20160225/fb6ead15/attachment-0001.html>