<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#c233">Comment # 233</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>That's not the problem. The problem is that there is a kernel module (correction, not the kernel itself, but rather the driver for the CS5536 "companion chip"*) that needs modifications compiled into it in order to (re)activate the IDE header after the BIOS cuts it off. The necessary alterations are on this page, in the last section at the very bottom -- <a href="http://www.parkytowers.me.uk/thin/wyse/s10/Linux.shtml">http://www.parkytowers.me.uk/thin/wyse/s10/Linux.shtml</a> -- however, manual patching is still, quite honestly, well beyond my abilities. I don't code ;) On top of that, I'm not 100% sure where in Puppy I would put the patched driver. I would assume that I'd have to modify initrd.gz which would be kind of a pain, as it's actually a CPIO archive, rather than the GZIP archive it claims to be by way of extension. (It might actually be both, a CPIO nested inside of a GZIP. I'm not actually sure.) Even then, there's a pretty sizable chance that I won't be able to do what I need to do... I seem to recall having some significant issues getting that particular system to boot in the first place.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>