<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#c51">Comment # 51</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:laserhawk64@gmail.com" title="Christopher <laserhawk64@gmail.com>"> Christopher</a> <pre>Got the thing to compile, with the arbiter patch included. Was unable to bypass mir requirement, but was able to institute a workaround that didn't involve patching Puppy itself. Per request I will not go into detail about /how/ I did the workaround. Have not actually /tested/ the newly-built driver yet, as I would like you folks' help on adjusting xorg.conf this time. Next message will be me attaching it from a 'pristine install' (having booted Puppy with instructions to ignore persistence). Commands were -- ./autogen.sh --prefix=/usr --enable-debug --enable-xv-debug --enable-viaregtool make make install</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>