<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#c147">Comment # 147</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:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"> Kevin Brace</a> <pre>(In reply to Christopher from <a href="show_bug.cgi?id=91966#c144">comment #144</a>) Hi Christopher, > Well, after arguing like **** with the computer (timezone & clock were set > incorrectly), I got it to compile on the WYSE client. Did "make install", > ran xorgwizard then manually edited xorg.conf so it would actually *work* -- > and typed > > # xwin > > pressing ENTER afterwards. > > Cursor blinked for a sec, then a bunch of gobbledegook mess on the top 1/4 > of the screen and a system that was so frozen hard I think it got > freezer-burnt. > > Needless to say there won't be any logs out of *that*. Puppy gets amnesia > when it gets a hard reboot. > > Oh well. One thing I am wondering is, did the crash behavior change between pre-patch version compiled OpenChrome device driver and the patched version? It appears that the crash pattern is different since, if I am correct, you said previously that the display will go blank. I will still need Xorg.0.log to analyze what happened. I hope Xorg.0.log is obtainable, although it is quite possible that if you boot from a USB flash storage stick, it stores the log filed as a RAM disk. I also recommend using a minimalist xorg.conf since OpenChrome does not require the use of it post Ubuntu 10.04 LTS. In my VIA Technologies silicon laptop (C7-M processor and VN896 chipset), I do not use xorg.conf at all. Based on my own testing, the patched device driver works fine. Regards, Kevin Brace</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>