<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=91966#c258">Comment # 258</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=91966">bug 91966</a> from <a class="email" href="mailto:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"> Kevin Brace</a> <pre>(In reply to John Friend from <a href="show_bug.cgi?id=91966#c248">comment #248</a>) Hi John, > Hi Kevin > > First, thanks for reassuming the development of this project. > > I have an HP-T5550 and I wonder if VGA connected to DVI-I port of T5550 > supposed to work at current master (commit b8eb2ab)? I have built current > master and tested it but result is same as original openchrome 0.3.3. I am > attaching the log file. I donot know if they will be helpfull, but I have > enabled some register dump and I2C scanning options in xorg.conf. (Pls. see > head of the log file.) My SW platfom is a custom Linux mostly based on a > previous snapshot of Thinstation 5.2. > > I have performed tests with two different CRT monitors, two different DVI-I > to VGA adaptors and with a Y-cable (DVI-I to DVI and VGA). All have same > logs (except few bencmark differences). > > Both monitors work OK with recent via (semi ?) opensource KMS driver. You > can check it at > <a href="http://manu.agat.net/5.76.52.92-opensource-009-005f78-20150730.tar.gz">http://manu.agat.net/5.76.52.92-opensource-009-005f78-20150730.tar.gz</a> Is it possible you can upload an unmodified Xorg.0.log? For some reason, it appears that the DDX (i.e., OpenChrome) is not seeing the monitor via I2C bus. Furthermore, if you are using those DVI-Y-cable, you may want to connect only one device at a time (i.e., VGA only or DVI only) for now. Regarding HP T5550's DVI, it is coming from VX900 chipset's integrated TMDS transmitter, so Justin's modification to the code is the only way to get it working for now. I am in the process of trying to figure out how to get OpenChrome to perform automatic detection of DVI / LVDS interface, but it may take a week or so since I did encounter several problems in the past few days (I am working on the fix.). I do not want to start blaming the previous developers, but I did not write the code, so I am still in the process of figuring out what they are doing (I would not have written such code if I were doing the development.). Regarding the VIA Technologies developed 2D graphics device driver, I have not taken a look at it, so I do not have too many things to say. In general, OpenChrome developers have not relied on VIA Technologies historically, and VIA Technologies has not had a good track record of working with open source development community (This was written extensively over at Phoronix. Do a search about VIA Technologies over at Phoronix, and you can probably find several articles about what happened.). I am not personally against them, so if they wanted to reach out to OpenChrome developers (There are current 2 people working on OpenChrome and obviously I am one of them. The other person is trying to develop DRM / KMS module so that it can be incorporated in the Linux kernel sometime in the future.) I am okay with that.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>