[Openchrome-devel] [Bug 91966] No signal to monitor with X and openchrome using VX855 chipset graphics

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jan 25 17:09:13 PST 2016


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

--- Comment #159 from Kevin Brace <kevinbrace at gmx.com> ---
Hi Christopher,

I am writing this from a tablet computer, so it will be short.
Thank you very much for further troubleshooting the bug.
I read the Xorg.0.log you just attached, and it appears that VT1632A TMDS
transmitter is attached to VX855 chipset.
Several weeks ago when I was changing the code so that OpenChrome relies less
and less on a predefined display output table, I noticed that one developer
(Christian Jung) donated several hundred lines of code to support VT1632A in
January 2015.
Interestingly, VT1632A initialization was invoked only when P4M800 Pro and
related chipsets (i.e., VN800 and CN700 chipsets) were in use.
The reason why DVI did not work at all previously is due to this.
I removed this restriction so that VT1632A is initialized regardless of which
chipset is in use.
Actually, there was a showstopper bug in the donated code, but I did already
fixed that issue (I forgot to mention this in one of the patch I uploaded for
you to try.).
VT1632A is detectable via I2C bus, and the donated code does that.
    It appears that using I2C bus 2 for VGA detection has number of problems at
this point.
Earlier today, I was testing your patches with an ASRock mainboard with P4M900
chipset (I do not recall the exact name, but it is something like
P4VM900-SATA2.), and it did cause a freeze of the system.
However, the same patches worked fine with K8M800 chipset (ABIT KV-80).
I will try to make adjustments to the I2C bus timings to see if it improves the
situation.
The patches that will deal with this situation might take several days since I
have some stuff planned for the next several days.
I ended up writing quite a bit.

Regards,

Kevin Brace

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


More information about the Openchrome-devel mailing list