<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#c228">Comment # 228</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 Justin Chevrier from <a href="show_bug.cgi?id=91966#c227">comment #227</a>) Hi Justin, > That is a fair question, but I can confirm that the monitor was set to the > right input type (VGA). The reason I'm 100% confident is that when > transferring the Xorg.0.log file from the thin client to my workstation I > switch to another VT on the thin client (the VGA port comes back when > switching to another VT) and I transfer from the thin client. I do this each > time I get a log. In addition, when testing each patch I ensure only one > cable (DVI or VGA) is connected to the thin client at a time. > > An additional point that may be relevant is that when in this state (EDID is > detected but nothing is displayed on the VGA port) the monitor detects an > input signal (aka it doesn't go into power saving), but it's just a blank > screen. Thank you for answering that question. I just wanted to confirm the problem exactly. I have been working on the DVI related bugs of OpenChrome and preparation for Version 0.3.4 for about 2 weeks straight. I will like to take a few days break on this issue, and work on investigating other bugs for the next few days. I will still monitor the messages posted here everyday.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>