<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#c303">Comment # 303</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:noloader@gmail.com" title="Jeffrey Walton <noloader@gmail.com>"> Jeffrey Walton</a> <pre>> Anyway, after researching what to do with the LVDS flat panel automatic > detection issue, I believe I came up with a good enough solution. > Apparently, VIA uses scratch pad registers in their CRT register section to > pass the presence of a flat panel and what native resolution the panel > supports Forgive my ignorance Kevin... I picked up a couple of additional thin clients for testing. I'm trying to determine what needs to be done for them. That leads to the question (I think someone else brought it up).... Is this 100+ thread all related to OpenChrome and VX855 chipset? It seems to be all over the place, and I am having trouble determining what applies and what I need to do. If the thread is drifting, could you help keep folks focused on the problem at hand to help ensure problems and solutions can be located without much fuss? My apologies for speaking out of turn. Jeff</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>