From owner-freebsd-questions Mon Apr 15 18:31:27 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA24050 for questions-outgoing; Mon, 15 Apr 1996 18:31:27 -0700 (PDT) Received: from eduserv.its.unimelb.EDU.AU (s_koyin@eduserv.its.unimelb.EDU.AU [128.250.6.4]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA24040 for ; Mon, 15 Apr 1996 18:31:24 -0700 (PDT) Received: (from s_koyin@localhost) by eduserv.its.unimelb.EDU.AU (8.7.4/8.7.3) id LAA27351; Tue, 16 Apr 1996 11:29:06 +1000 (EST) Date: Tue, 16 Apr 1996 11:29:05 +1000 (EST) From: HMG coA reductase To: tony@odin.sunquest.com cc: questions@FreeBSD.org Subject: Re: screen lock up problem (2.1-stable) In-Reply-To: <199604152222.PAA03136@ermintrude.sunquest.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk G'day. Yes, i have an S3-805 and got the same thing before. happened when i tried a Ctrl-Alt-F1 to get to the vty. blank screen, beep at every keystroke. Sometimes the blank screen doesn't apear, but i remain in X. Pressing Ctrl-R to kill X didn't bring up the vty either. what i did was, go through the X startup messages and find out which of the displays (whatever you call it, those lines full of hsync and vsync numbers) were NOT being used, and commented them out, leaving only those three resolutions that i work with. Solved it! On Mon, 15 Apr 1996, Tony Jones wrote: > > I came into work this morning and the display on my FreeBSD system [S3-801/805, > DEC 486/66] was totally locked up. > > Blank screen, switching to a virtual console just caused the system to 'beep'. > > I was able to get in via telnet, killing xdm/X didn't fix the problem. > > No indication of a problem in any log files, the only processes running on > the vty's were getty's which respawned fine when killed. xdm/X respawned fine > also. In the end I had to reboot. >