[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: blaster xscreensaver crashes computer?



>>>>> "Adam" == Adam Lackorzynski <al10@inf.tu-dresden.de> writes:

    Adam> On Wed Jun 27, 2001 at 10:32:33 +1000, Brian May wrote:
    >> 1. running the blaster screen saver crashes almost immediately
    >> after I run it (just after the first screen refresh I
    >> think). This is very reproducible.

    Adam> Same here :( I never tried this one before and ran right
    Adam> into the crash.  Machine locks up hard (no ping) with XFree
    Adam> 4 (this box has a chip without the scrolling bug). With
    Adam> XFree 3.3.6 (potota version) only the X server goes nuts
    Adam> (and is killable)..  Only known solution so far: Don't use
    Adam> blaster.

Interesting... At least, now I know I am not the only one... I have
gone into xscreensaver-demo and manually disabled "blaster", so my
computer wont automatically "lock" while I leave it on random ;-)
(this did happen at least once now).

However, the exact same thing happened to me with potato versions of
everything, too.

    >> 2. switching to a text mode console produces a black screen,
    >> and I can't see any text, so I switch back to X and fortunately
    >> X still works.

    Adam> Hmm, I'm not seeing this here but I use FB for the console
    Adam> with "vga=0x318, video=vesa:mtrr", maybe this makes the
    Adam> difference?

As I have said before, I can't get framebuffer :-(. I haven't tried
0x318 yet (I saw 0x33b somewhere, so tried that), but I am
skeptical. In fact, the symptoms are exactly the same. Coincidence?

    >> Maybe I need to wait for 4.1.0?

    Adam> I don't belief it makes things better right now. I'll
    Adam> contact Tim...

Thanks.

Do you think the blaster crash is a display driver problem?
-- 
Brian May <bam@debian.org>



Reply to: