<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#c156">Comment # 156</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>I have been told numerous times that the hardware physically does not have enough wires to support anything higher than 16-bit color. Not an issue for me, and I'm an artist! (Well, we *are* known to be a bit persnickety... ;) ) I seem to recall that GLX-disabling in xorg.conf doesn't always work. I may also have a bad glx.so and not know it, but I find that quite unlikely because I'd have probably heard it mentioned on the Puppy Forum by now. Still, worth checking into. IIRC I have been using the same Pup the whole time. X-Tahr 1b3 is identical to TahrPup 6.0.2, with the sole exceptions that JWM and ROX-Filer have been replaced with XFCE and Thunar. Xorg.0.log and Xerrs.log attachments from previous reportings do exist from the Git build at the time, and are labeled as such. As Xerrs.log is stored in /tmp, it gets deleted at powerdown.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>