Return to BSD News archive
Xref: sserve comp.windows.x.i386unix:5947 comp.os.386bsd.bugs:1934
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!xlink.net!scsing.switch.ch!swidir.switch.ch!univ-lyon1.fr!ensta!itesec!frmug!renux.frmug.fr.net!keltia.frmug.fr.net!not-for-mail
From: roberto@keltia.frmug.fr.net (Ollivier Robert)
Newsgroups: comp.windows.x.i386unix,comp.os.386bsd.bugs
Subject: [FreeBSD 1.0.2]: Frequent startup lock-up with XFree 2.0
Date: 14 Dec 1993 21:38:56 +0100
Organization: A Private FreeBSD Usenet Site - FRANCE
Lines: 39
Distribution: inet
Message-ID: <2el89e$10g@keltia.frmug.fr.net>
NNTP-Posting-Host: keltia.frmug.fr.net
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Summary: XFree freezes computer upon starting up
Keywords: XFree86 FreeBSD lock-up
Hello FreeBSD and XFree86 folks,
background : 486DX-33, 16 MB, AHA-1542B, 640 MB Micropolis, Fahrenheit VA/VLB
FreeBSD 1.0.2 with 'trap.c' patch, XFree86 2.0/S3
Upon starting up, about 3 times out of 4, when I start XFree86 just after
booting the computer with startx/xinit, the server began displaying
messages about three directories not foudn in my font path (expected), the
computer just freeze. Really out for lunch. No more keyboard, no more disk
activity and a lot of fsck after hitting the big-red-switch...
It seems to be X-related so I post in both groups. I've had a few problem
with Xfree86 at the beginning but my problem was fixed very quickly (thanks
to both David :-)). When it occurs, I started X11 from the second vty
(ttyv1 instead of ttyv0), it seems to solve the problem for a few days.
Then I heard it may be necessary to do a 'man' of something that deals with
the screen, and again my problem was solved for a few days. Now it occurred
4 four times ! The trap.c seems also to have fixed the problem so I was
very happy and it happens again... Since I must switch off my computer
every day (my room is small and I've got to sleep at least a little :-)),
the problem is really bitting at me.
Those days, doing "syscons -m 80x50" followed by "syscons -m 80x25" seems
to "correct" the problem till next time...
Dunno really where to start... Is it XFree86 with my VLB S3 card ? Is it a
problem inside the VM ? An interaction between the two ?
I just got FreeBSD-current but haven't tried it yet...
I can post my various configuration file if it can give a clue...
Thanks again for your great work !
--
Ollivier ROBERT Ollivier.Robert@keltia.frmug.fr.net
A FreeBSD & PERL addict... PGP 2.3a Public Key on request
Herve's keywords: Unix Security Internet Schauer Usenet