x_vid_problems

This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.



Subject: RE: Opinions
From: Bill Carlson <wcarlson@vh.org>
Date: Wed, 12 Jan 2000 13:43:17 -0600 (CST)


On Wed, 12 Jan 2000, Bernhard Rosenkraenzer wrote:

> On Wed, 12 Jan 2000, Bill Carlson wrote:
> 
> > 1. XFree86 - Nothing kills a machine faster than buggy video drivers.
> > Sometimes only the display gets wacked and one can telnet in and reboot
> > the machine, sometimes not.
> 
> There's no needs to reboot in this case. You can just kill the X server
> and everything will be back to normal.
> X can't mess up kernel space, so once you killed the process it's gone.
> 

I can see you haven't had this happen to you. The keyboard is gone, the
mouse is gone, the display is toast. Trust me, I fiddled with this for
quite a while, upgrading to a new release of XFree86 made the problem go
away. You can kill the X server all you want, the trick is to get
something to tell the card to do back to text mode! I never had any luck
doing that, better to clean shutdown/boot.

I've also had X completely kill a machine, no network no nothing.

C'est la kernel software.

===

Subject: RE: Opinions
From: Bernhard Rosenkraenzer <bero@redhat.de>
Date: Wed, 12 Jan 2000 20:46:18 +0100 (CET)


On Wed, 12 Jan 2000, Bill Carlson wrote:

> I can see you haven't had this happen to you. The keyboard is gone, the
> mouse is gone, the display is toast. Trust me, I fiddled with this for
> quite a while, upgrading to a new release of XFree86 made the problem go
> away. You can kill the X server all you want, the trick is to get
> something to tell the card to do back to text mode!

Using SVGATextMode to switch to graphics mode and back should do the
trick.

===




the rest of The Pile (a partial mailing list archive)

doom@kzsu.stanford.edu