<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#c63">Comment # 63</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#c58">comment #58</a>)
<span class="quote">> FYI -- I got a Puppy developer [...] to bodge together a version of TahrPup
> 6.0.2 [...] with the kernel and Xorg stuff from Precise Puppy 5.7.1 Retro,
> and lo and behold I get working video.</span >
Great! Which kernel version is that? Please attach a Xorg.0.log.
<span class="quote">> I'm very much still interested in trying to work out what the issue is
> that's breaking the driver on this hardware in later revisions...</span >
Yes, but most likely it's not a driver issue, but a kernel issue... You see, I
woke up my old KM400 machine, booted it from a USB stick with Linux Lite 2.6...
and see... I don't get any video either! (When I boot it in safe mode, it
forces the use of the vesa driver and I get a visible and usable desktop.)
What I then noticed in the log is a line that I'll post in a minute.</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>