<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#c157">Comment # 157</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>Did some more testing work on this. A bit of background. May have explained this before. If so, I apologize. There are two ways of installing Puppy Linux. One is a "frugal" install and the other is a "full" install, in the lingo we use. A "full" install is a traditional Linux unpack-n-set-up-all-over-a-partition install. (Windows does it the same way, of course.) A "frugal" install mimics a LiveCD -- the SquashFS file containing the primary filesystem is copied over (sometimes there's an extra one for drivers) along with the initrd.gz (init f/s) and vmlinuz (kernel) files, and a bootloader is applied (GRUB if you're smart, grub4dos if you're me) -- and that's it. When Puppy boots from a "frugal" install, it unpacks the SFS file(s) into RAM and runs from there, saving changes to a separate changelog sort of file (or, more recently, folder) that we call a "savefile" (or "savefolder"). I've been using a "frugal" install of Puppy, which is actually the preferred and suggested method, for all of the testing so far, and involving persistence by way of a savefolder. I decided to plow that under today and go for a "full" install, to see if it behaved differently enough that it would perhaps aid in debugging. It did -- although, not in the way I'd hoped -- I didn't get /tmp/Xerrs.log. That said, one new Xorg.0.log coming up! I think it got farther this time, too... log looks longer. It also didn't futz the screen. I got a blinking cursor, then a smaller nonblinking cursor at which it hung. Dunno.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>