<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><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#c33">Comment # 33</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 <span class="vcard"><a class="email" href="mailto:bensberg@justemail.net" title="Benno Schulenberg <bensberg@justemail.net>"> <span class="fn">Benno Schulenberg</span></a>
</span></b>
<pre>(In reply to Christopher from <a href="show_bug.cgi?id=91966#c0">comment #0</a>)
<span class="quote">> I don't know how relevant this is, but if I use the 'modesetting' or 'vesa'
> drivers, the symptom is the same, except that additionally the system
> freezes upon attempting to return to text mode.</span >
Well, if you can't get an image on your monitor even with the vesa driver, all
bets are off. Vesa should work always.
What does your xorg.conf look like when Puppy has generated it? How do you
modify things to get the vesa driver to be used?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>