<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#c318">Comment # 318</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>> If compiling OpenChrome is such a problem, please ask the Puppy Linux > developers to do it, and create a new image of with OpenChrome Version > 0.4.0. Often its helpful to file a bug report or feature request asking the updated driver be picked up. Christopher should probably take a proactive role. I've seen a few of them for OpenChrome under Debian, Ubuntu and Fedora. For these distros, the package name is: * Debian - xserver-xorg-video-openchrome * Ubuntu - xserver-xorg-video-openchrome * Fedora - xorg-x11-drv-openchrome Eventually, the current OpenChrome developers (is that just Kevin now?) will get to know the distros and package maintainers, and an offline email will do. Until the relationships are forged, its probably best to stick to bug trackers. 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>