*BSD News Article 43362


Return to BSD News archive

Xref: sserve comp.unix.bsd.freebsd.misc:52 comp.windows.x.i386unix:15745
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!news.hawaii.edu!ames!elroy.jpl.nasa.gov!decwrl!purdue!mozo.cc.purdue.edu!not-for-mail
From: lzt@mace.cc.purdue.edu (Robert Yoder)
Newsgroups: comp.unix.bsd.freebsd.misc,comp.windows.x.i386unix
Subject: FreeBSD 2.0 & XFree86 3.x problem (Linux & NetBSD OK)
Date: 4 Mar 1995 09:43:07 -0500
Organization: Purdue University
Lines: 41
Message-ID: <3j9u9r$if8@mace.cc.purdue.edu>
NNTP-Posting-Host: mace.cc.purdue.edu
Summary: XFree86 problem with FreeBSD, but not with Linux or NetBSD
Keywords: FreeBSD,XFree86


I have a problem with XFree86, (3.1 & 3.1.1), and FreeBSD, (2.0 & 950210-SNAP).
Using exactly the same hardware, I do NOT have the problem with NetBSD and
Linux.

X starts up and runs with no problems;  The problem occurs when I shut it down.
The console is reduced to narrow purple, horizontal streaks on a black
background.  Nothing I do to the keyboard makes any difference.  The only
thing I can do is push the "big red button".  I can't tell if the machine has
actually crashed, or whether it is only the console that is hosed.

I have tried shutting down X by using the twm menu 'exit'.
I have tried ctrl-alt-bksp.
I have tried shutdown -h now.
All give the same results.

Linux, (Slackware 2.1 & kernel 1.1.94), and NetBSD 1.0 both run XFree86 3.1 on
the SAME MACHINE with no such problems.  I would prefer to run FreeBSD, but
being forced to end each session with a hardware reset, leaves a lot to be
desired.

My system is:

486DX2/66 (Overdrive chip in a 33Mhz socket)
Intel EISA motherboard w/ Phoenix BIOS
16M RAM
Orchid Prodesigner II EISA video card (et4000)
AHA-1740 SCSI host adapter
all HD's are SCSI
Toshiba 3201-B SCSI CDROM
PAS 16 Basic soundcard

Monitor is a Zenith ZCM-1492 (VGA-only - 640x480)

Please reply via email;  My newsfeed is sporadic, and frequently non-existent.

Robert Yoder
cry005@comm.mot.com

"NO!  You can't have one PHONE CALL!!!"
(A law-enforcement official responding to Kevin Mitnick's first request.)