<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#c148">Comment # 148</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>Behavior is indeed different. Before it would either fail with a nonblinking cursor, fail with a blinking cursor, or not last long enough to get out of text mode. I will try and boot it again (I rebooted to save the driver progress, so that I wouldn't have to compile it *again* and the image is what I got upon it coming back up and trying to GUI) and see if it can be caught and CTRL+ALT+BKSP'd before everything packs up and goes away. If I can't do that, I will have to reinstall a different way, compile the driver all over again, and get the files that way... the way it's installed now it runs in RAM which is bad for crash reports but better for the drive I'm using in it -- an SD card in an IDE adapter. (Hey, it fits in the housing! A 2.5" drive would not, and the system does not have enough oomph to spin up a mechanical hard drive of any kind.) We'll see what happens. I'll keep you posted :)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>