View All Attachments for Bug 91966

Obsolete attachments are hidden. To view all attachments (including obsolete) click here.

Attachment #118249
Xorg.0.log from initial bootup	text/plain	2015-09-14 00:40:33 UTC	21.32 KB	no flags	Details

Attachment #118250
xerrs.log from initial bootup	text/plain	2015-09-14 00:41:17 UTC	3.18 KB	no flags	Details

Attachment #118274
xerrs.log from Precise 5.7.1 Retro first boot	text/plain	2015-09-15 00:55:35 UTC	1.43 KB	no flags	Details

Attachment #118275
Xorg.0.log from Precise 5.7.1 Retro first boot	text/plain	2015-09-15 00:56:06 UTC	54.57 KB	no flags	Details

Attachment #118329
xerrs.log from Git-built driver	text/plain	2015-09-17 19:34:54 UTC	4.20 KB	no flags	Details

Attachment #118330
Xorg.0.log from Git-built driver	text/plain	2015-09-17 19:35:25 UTC	19.65 KB	no flags	Details

Attachment #118331
enable lcd for VIA VT8562C	patch	2015-09-17 20:15:52 UTC	610 bytes	no flags	Details

Attachment #118332
enable dp for VIA VT8562C	patch	2015-09-17 20:56:30 UTC	610 bytes	no flags	Details

Attachment #119354
xorg.conf from initial boot	text/plain	2015-11-02 19:40:03 UTC	4.63 KB	no flags	Details

Attachment #119406
xerrs.log from TahrPup/Precise Hybrid	text/plain	2015-11-04 17:25:54 UTC	2.00 KB	no flags	Details

Attachment #119407
Xorg.0.log from TahrPup/Precise Hybrid	text/plain	2015-11-04 17:26:36 UTC	56.73 KB	no flags	Details

Attachment #119411
Epic 1314 laptop (MSI VR321 laptop equivalent) dmesg	text/plain	2015-11-04 20:29:48 UTC	49.92 KB	no flags	Details

Attachment #119415
Epic 1314 laptop (MSI VR321 laptop equivalent) Xorg.0.log	text/plain	2015-11-04 20:34:37 UTC	39.65 KB	no flags	Details

Attachment #120696
xerrs.log from initial bootup, DVI-D cable and monitor	text/plain	2015-12-26 21:32:17 UTC	3.62 KB	no flags	Details

Attachment #120697
Xorg.0.log from initial bootup, DVI-D cable and monitor	text/plain	2015-12-26 21:32:41 UTC	21.28 KB	no flags	Details

Attachment #120698
xerrs.log, DVI-D cable and monitor, openchrome driver manually specified in xorg.conf	text/plain	2015-12-26 21:33:26 UTC	1.42 KB	no flags	Details

Attachment #120699
Xorg.0.log, DVI-D cable and monitor, openchrome driver manually specified in xorg.conf	text/plain	2015-12-26 21:33:52 UTC	1.65 KB	no flags	Details

Attachment #120700
xerrs.log, DVI-D cable and monitor, openchrome driver specified through xorgwizard	text/plain	2015-12-26 21:34:31 UTC	3.53 KB	no flags	Details

Attachment #120701
Xorg.0.log, DVI-D cable and monitor, openchrome driver specified through xorgwizard	text/plain	2015-12-26 21:34:57 UTC	18.31 KB	no flags	Details

Attachment #121244
Photo of effect from patched driver	image/jpeg	2016-01-24 15:45:05 UTC	895.64 KB	no flags	Details

Attachment #121253
Xorg.0.log from crashing patched driver	text/plain	2016-01-25 03:26:32 UTC	5.03 KB	no flags	Details

Attachment #121285
Xorg.0.log from crashing patched driver, "full" install	text/plain	2016-01-25 22:24:56 UTC	13.66 KB	no flags	Details

Attachment #121544
Xorg.0.log from crashing patched driver, "full" install -- does not include 2 most recent patches	text/plain	2016-02-06 00:23:23 UTC	14.55 KB	no flags	Details

Attachment #121872
Using I2C bus 2 to detect a VGA monitor	patch	2016-02-21 21:54:38 UTC	5.65 KB	no flags	Details

Attachment #121881
attachment-11453-0.html	text/html	2016-02-22 11:18:32 UTC	12.12 KB	no flags	Details

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><base href="https://bugs.freedesktop.org/"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:å®ä½;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:å®ä½;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@å®ä½";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:å®ä½;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:å®ä½;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML é¢è®¾æ ¼å¼ Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:å®ä½;}
span.vcard
	{mso-style-name:vcard;}
span.fn
	{mso-style-name:fn;}
span.HTMLChar
	{mso-style-name:"HTML é¢è®¾æ ¼å¼ Char";
	mso-style-priority:99;
	mso-style-link:"HTML é¢è®¾æ ¼å¼";
	font-family:"Courier New";}
span.quote
	{mso-style-name:quote;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1193148805;
	mso-list-template-ids:-474582262;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:ï·;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:ï§;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:ï§;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:ï§;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:ï§;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:ï§;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:ï§;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:ï§;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=ZH-CN link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Kevin,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>Â Â Â Â Â Â Â Â  Glad to receive your response so quickly.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>Â Â Â Â Â Â Â Â  For I2C probe EDID information, generally there are several the I2C HW pair lines as you said. And they can be routed to VGA connector/DVI connector, even for HDMI connector. It depends on HW schematic. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>Â Â Â Â Â Â Â Â  So for this Wyse C90LE case, do we know which I2C HW pair lines are used for chipset? If there is no EDID information probed out, we can try a fixed mode to see if that is the reason for this issue. I know how to do it in DRM instead of UMS driver. And I think there is a way to try a fixed mode in UMS driver too.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>Frank<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:10.0pt'>åä»¶äºº<span lang=EN-US>:</span></span></b><span lang=EN-US style='font-size:10.0pt'> Openchrome-devel [mailto:openchrome-devel-bounces@lists.freedesktop.org] </span><b><span style='font-size:10.0pt'>ä»£è¡¨ </span></b><span lang=EN-US style='font-size:10.0pt'>bugzilla-daemon@freedesktop.org<br></span><b><span style='font-size:10.0pt'>åéæ¶é´<span lang=EN-US>:</span></span></b><span lang=EN-US style='font-size:10.0pt'> 2016</span><span style='font-size:10.0pt'>å¹´<span lang=EN-US>2</span>æ<span lang=EN-US>22</span>æ¥<span lang=EN-US> 17:36<br></span><b>æ¶ä»¶äºº<span lang=EN-US>:</span></b><span lang=EN-US> openchrome-devel@lists.freedesktop.org<br></span><b>ä¸»é¢<span lang=EN-US>:</span></b><span lang=EN-US> [Openchrome-devel] [Bug 91966] No signal to monitor with X and openchrome using VX855 chipset graphics<o:p></o:p></span></span></p></div></div><p class=MsoNormal><span lang=EN-US><o:p>&nbsp;</o:p></span></p><div><p class=MsoNormal><b><span lang=EN-US><a href="https://bugs.freedesktop.org/show_bug.cgi?id=91966#c202" title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics">Comment # 202</a> on <a href="https://bugs.freedesktop.org/show_bug.cgi?id=91966" title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics">bug 91966</a> from <span class=vcard><a href="mailto:kevinbrace@gmx.com" title="Kevin Brace &lt;kevinbrace@gmx.com&gt;"><span class=fn>Kevin Brace</span></a> </span></span></b><span lang=EN-US><o:p></o:p></span></p><pre><span lang=EN-US>(In reply to HuangRan from <a href="show_bug.cgi?id=91966#c201">comment #201</a>)<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>Hi Frank,<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span class=quote><span lang=EN-US>&gt; Hi Guys,<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; <o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt;Â Â Â  Returning from my holiday and looking at this thread from the start to<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; the end takes me several hours to do so although I have to skip some content<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; for your chat becuase it is so long.<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt;Â Â Â  As I replied the mail to Kevin, I prefer to put my more time on<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; OpenChrome and has several guys invovled on this project. So I hope I can<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; provide some useful informaiton on this bug too.<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt;Â Â Â  So is this bug fixed or not? Does I2C 2 probe EDID information from DVI<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; interface?<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; <o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; Thanks,<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; Frank</span></span><span lang=EN-US><o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>The way the code works right now with the patch is that I2C bus 1 and 2 are<o:p></o:p></span></pre><pre><span lang=EN-US>used for VGA related monitor detection.<o:p></o:p></span></pre><pre><span lang=EN-US>xserver's API returns a structure that tells the caller if the monitor type is<o:p></o:p></span></pre><pre><span lang=EN-US>analog or digital.<o:p></o:p></span></pre><pre><span lang=EN-US>I use this information to see if I2C bus 1 or 2 is connected to an analog<o:p></o:p></span></pre><pre><span lang=EN-US>monitor (i.e., VGA monitor).<o:p></o:p></span></pre><pre><span lang=EN-US>I read the Intel DDX UMS code, and they apparently do this.<o:p></o:p></span></pre><pre><span lang=EN-US>As for DVI, I2C bus 2 or 3 are used for communicating with the monitor and an<o:p></o:p></span></pre><pre><span lang=EN-US>external TMDS transmitter chip.<o:p></o:p></span></pre><pre><span lang=EN-US>In other words, I2C bus 2 can be used for VGA, DVI, or even a TV encoder chip.<o:p></o:p></span></pre><pre><span lang=EN-US>The code that handles an external TMDS transmitter for DVI (i.e., VT1632A chip)<o:p></o:p></span></pre><pre><span lang=EN-US>is still relatively unproven.<o:p></o:p></span></pre><pre><span lang=EN-US>It was donated in early 2015, but there was a bug in it, and I help fix it with<o:p></o:p></span></pre><pre><span lang=EN-US>the person who reported it (<a href="show_bug.cgi?id=93675" title="RESOLVED FIXED - Segfault in xf86DestroyI2CDevRec">Bug 93675</a>).<o:p></o:p></span></pre><pre><span lang=EN-US>I do own about 10 or so VIA Technologies IGP based mainboards / computers at my<o:p></o:p></span></pre><pre><span lang=EN-US>place, but I do not really have a functional mainboard / computer with DVI<o:p></o:p></span></pre><pre><span lang=EN-US>coming out of it at this point that is not a thin client.<o:p></o:p></span></pre></div><div class=MsoNormal align=center style='text-align:center'><span lang=EN-US><hr size=2 width="100%" align=center></span></div><p class=MsoNormal><span lang=EN-US>You are receiving this mail because: <o:p></o:p></span></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span lang=EN-US>You are the assignee for the bug.<o:p></o:p></span></li></ul></div></div></body></html>

Attachment #121897
DVI on the DVI-D port on HP T5550	text/plain	2016-02-22 20:26:55 UTC	23.54 KB	no flags	Details

Attachment #121898
DVI on the DVI-I port on HP T5550	text/plain	2016-02-22 20:27:46 UTC	23.54 KB	no flags	Details

Attachment #121899
VGA on the DVI-I port with VGA adapter HP T5550	text/plain	2016-02-22 20:29:22 UTC	28.79 KB	no flags	Details

Attachment #121922
Modified T5550 Entry	patch	2016-02-23 14:41:37 UTC	953 bytes	no flags	Details

Attachment #121923
DVI on the DVI-I port on HP T5550 with modified ID	text/plain	2016-02-23 14:42:49 UTC	22.84 KB	no flags	Details

Attachment #121924
VGA on the DVI-I port with VGA adapter HP T5550 with modified ID	text/plain	2016-02-23 14:43:38 UTC	26.61 KB	no flags	Details

Attachment #121940
Added debug messages to via_vt1632_probe	patch	2016-02-24 09:30:41 UTC	1.06 KB	no flags	Details

Attachment #121941
Using I2C bus 3 functions that are likely work	patch	2016-02-24 09:48:56 UTC	1.97 KB	no flags	Details

Attachment #121952
DVI on the DVI-D port on HP T5550 with ID, 121940, 121941	text/plain	2016-02-24 20:12:51 UTC	19.36 KB	no flags	Details

Attachment #121957
Altering external DVI transmitter (VT1632A) monitor detection method	patch	2016-02-25 01:53:43 UTC	3.52 KB	no flags	Details

Attachment #121990
DVI on the DVI-D port on HP T5550 with ID, 121940, 121957	text/plain	2016-02-26 21:02:13 UTC	19.89 KB	no flags	Details

Attachment #122261
VGA (crt) connected to DVI-I port of T5550 via DVI-I to VGA adapter (Xorg.0.log)	text/plain	2016-03-13 01:04:36 UTC	49.67 KB	no flags	Details

Attachment #122293
Stock Git at b8eb2ab. VGA plugged into DVI-I via adapter (works)	text/plain	2016-03-14 20:20:11 UTC	26.54 KB	no flags	Details

Attachment #122294
Stock Git at b8eb2ab. DVI plugged into DVI-I (does not work):	text/plain	2016-03-14 20:21:01 UTC	19.08 KB	no flags	Details

Attachment #122295
Git at b8eb2ab with ID patch. VGA plugged into DVI-I via adapter (does not work):	text/plain	2016-03-14 20:21:40 UTC	24.09 KB	no flags	Details

Attachment #122296
Git at b8eb2ab with ID patch. DVI plugged into DVI-I (works)	text/plain	2016-03-14 20:22:18 UTC	23.33 KB	no flags	Details

Attachment #122335
Thin client boards(Wyse C90LE, V90LE, HP T510)	image/jpeg	2016-03-16 08:45:57 UTC	5.64 MB	no flags	Details

Attachment #122336
Thin client boards(Wyse C90LE, V90LE, HP T510)	image/jpeg	2016-03-16 08:47:47 UTC	300.85 KB	no flags	Details

Attachment #122366
DVI-D port output for HP510 platform	text/plain	2016-03-17 09:17:00 UTC	33.55 KB	no flags	Details

Attachment #122367
DVI-I(using DVI) Xorg log for HP T510	text/plain	2016-03-17 09:29:25 UTC	19.13 KB	no flags	Details

Attachment #122490
X log for latest UMS on Wyse V90LE platform DVI port	text/plain	2016-03-23 06:33:49 UTC	57.75 KB	no flags	Details

Attachment #122518
X log for latest UMS on Wyse V90LE platform VGA port	text/plain	2016-03-24 09:29:55 UTC	37.05 KB	no flags	Details

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.