Date: Fri, 4 Apr 1997 07:28:30 -0800 From: Justin Wolf <jjwolf@bleeding.com> To: Justin Wolf <jjwolf@bleeding.com>, "'Jochim Kuebart'" <joa@delos.lf.net> Cc: "'freebsd-questions@freebsd.org'" <freebsd-questions@freebsd.org> Subject: RE: X-Server hard crashes when started Message-ID: <01BC40C9.CBDB91E0@crimson>
next in thread | raw e-mail | index | archive | help
Ok, here's the result (had to grab it from a telnet session, sine it wasn't flushing the drive and the screen is blank when this happens):
(log below)
This is from startx, although it appears that the output from this, xinit, and X (XF86_VGA16) is the same. Just looking at it makes me think that X is confused and thinks that it can't use any resolution to display with. However, there doesn't appear to be a "debug" mode to go into, so I can't really tell why it stops (no error reported). Could it be that I misconfigured it? If so, what should I change?
-Justin
(log follows)
XFree86 Version 3.2 / X Window System
(protocol Version 11, revision 0, vendor release 6100)
Release Date: Oct 26 1996
If the server is older than 6-12 months, or if your card is newer
than the above date, look for a newer version before reporting
problems. (see http://www.XFree86.Org/FAQ)
Operating System: FreeBSD 2.2.0
Configured drivers:
VGA16: server for 4-bit colour VGA (Patchlevel 0):
et4000, et4000w32, et4000w32i, et4000w32p, et4000w32p, et6000, et3000,
ncr77c22, ncr77c22e, ati, sis86c201, sis86c202, sis86c205, tvga8200lx,
tvga8800cs, tvga8900b, tvga8900c, tvga8900cl, tvga8900d, tvga9000,
tvga9000i, tvga9100b, tvga9200cxr, tgui9320lcd, tgui9400cxi, tgui9420,
tgui9420dgi, tgui9430dgi, tgui9440agi, tgui9660xgi, tgui9680, oti067,
oti077, oti087, oti037c, cl6410, cl6412, cl6420, cl6440, generic
MONO: server for interlaced and banked monochrome graphics adaptors
(Patchlevel 0):
hgc1280, sigmalview, apollo9
Using syscons driver with X support (version 2.0)
(using VT number 4)
XF86Config: /etc/XF86Config
(**) stands for supplied, (--) stands for probed/default values
(**) XKB: keymap: "xfree86(us)" (overrides other XKB settings)
(**) Mouse: type: MouseSystems, device: /dev/cuaa0, baudrate: 1200
(**) VGA16: Graphics device ID: "My Video Card"
(**) VGA16: Monitor ID: "My Monitor"
(--) VGA16: Mode "800x600" needs hsync freq of 35.16 kHz. Deleted.
(--) VGA16: Mode "1024x768" needs hsync freq of 35.52 kHz. Deleted.
(--) VGA16: Mode "640x480" needs hsync freq of 36.46 kHz. Deleted.
(--) VGA16: Mode "800x600" needs hsync freq of 37.88 kHz. Deleted.
(--) VGA16: Mode "800x600" needs hsync freq of 48.08 kHz. Deleted.
(--) VGA16: Mode "1024x768" needs hsync freq of 48.36 kHz. Deleted.
(--) VGA16: Mode "1024x768" needs hsync freq of 56.48 kHz. Deleted.
(--) VGA16: Mode "1280x1024" needs hsync freq of 51.02 kHz. Deleted.
(--) VGA16: Mode "1024x768" needs hsync freq of 62.50 kHz. Deleted.
(--) VGA16: Mode "1280x1024" needs hsync freq of 64.25 kHz. Deleted.
(--) VGA16: Mode "1280x1024" needs hsync freq of 78.86 kHz. Deleted.
(--) VGA16: Mode "1280x1024" needs hsync freq of 81.13 kHz. Deleted.
(--) VGA16: Mode "320x240" needs hsync freq of 39.38 kHz. Deleted.
(--) VGA16: Mode "400x300" needs hsync freq of 35.16 kHz. Deleted.
(--) VGA16: Mode "400x300" needs hsync freq of 37.88 kHz. Deleted.
(--) VGA16: Mode "400x300" needs hsync freq of 48.08 kHz. Deleted.
(--) VGA16: Mode "480x300" needs hsync freq of 35.16 kHz. Deleted.
(--) VGA16: Mode "480x300" needs hsync freq of 37.80 kHz. Deleted.
(--) VGA16: Mode "480x300" needs hsync freq of 39.56 kHz. Deleted.
(--) VGA16: Mode "480x300" needs hsync freq of 48.00 kHz. Deleted.
(**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75
dpi/:unscaled,/usr/X11R6/lib/X11/fonts/75dpi/"
(--) VGA16: oti087: ISA card in a 16-bit AT-BUS slot.
(--) VGA16: oti087: MemBase for Linear Addressing will be
(--) VGA16: oti087: set at 0xE00000 (the 14Mbyte mark).
(--) VGA16: oti087: BT476,SC11487,IMSG174 or equivalent RAMDAC.
(--) VGA16: chipset: oti087
(--) VGA16: videoram: 256k (using 256k)
(--) VGA16: clocks: 25.17 28.32 28.32 28.32 25.17 28.32 28.32 28.32
(--) VGA16: clocks: 25.17 28.32 28.32 28.32 25.17 28.32 28.32 28.32
(--) VGA16: Maximum allowed dot-clock: 80.000 MHz
(**) VGA16: Mode "640x480": mode clock = 25.175, clock used = 25.170
(--) VGA16: There is no mode definition named "800x600"
(--) VGA16: Removing mode "800x600" from list of valid modes.
(**) VGA16: Virtual resolution set to 800x600
(**) VGA16: oti087: FIFO depth: 6.
(**) VGA16: oti087: VLB interface: All wait states.
(**) VGA16: oti087: Chipset speed: 50 Mhz.
(**) VGA16: oti087: BitBlt engine status: Disabled.
(**) VGA16: oti087: Addressing Mode: Segmented.
(**) VGA16: oti087: page size: 64 Kb.
----------
From: Jochim Kuebart[SMTP:joa@delos.lf.net]
Sent: Friday, April 04, 1997 3:49 AM
To: Justin Wolf
Subject: Re: X-Server hard crashes when started
I think what Doug means is you should capture the output of startx or xinit
before your system dies. You could try this by typing "startx > startx.out"
or "xinit > xinit.out" respectively. However, if you cant reboot using the
three finger salute but only via the Reset button, it is likely that the
file system won't get flushed and you never get those files. In this case,
you will have to copy the screen contents by hand and send it to this list
or (preferably) xfree86@xfree86.org so we (or they) know what exactly is
going on.
If you don't see any output, maybe X has already switched your screen to
another console. Try the Alt-F1 etc. combinations to see if you can get
back to the console you started X from...
c u Jo
----------
> Von: Justin Wolf <jjwolf@bleeding.com>
> An: Justin Wolf <jjwolf@bleeding.com>
> Cc: 'freebsd-questions@freebsd.org'
> Betreff: RE: X-Server hard crashes when started
> Datum: Freitag, 4. April 1997 09:41
>
> I'm afraid I'm a bit new to this... which program should I capture? xdm,
xstart, x (and what it links to), xinit, or which? Thanks for the help...
I'd like to get this up and running.
>
> -Justin Wolf
>
> ----------
> From: Doug White[SMTP:dwhite@gdi.uoregon.edu]
> Sent: Thursday, April 03, 1997 3:33 PM
> To: Justin Wolf
> Cc: 'freebsd-questions@freebsd.org'
> Subject: Re: X-Server hard crashes when started
>
>
> On Wed, 2 Apr 1997, Justin Wolf wrote:
>
> > Every time I try to start X-Windows, it hard crashes the system.
> > Meaning, all telnet activity is halted, the console screen goes blank
> > (losses signal), console interactivity is halted. I have to push the
> > reset button in order to get anything back.
>
> The kernel may be panicing.
>
> > I have properly (as far as I can tell), set up the configuration
files
> > via both the shell config program and the X-like interface (making me
> > think that this is not a problem with the video, mouse, keybd, etc).
> > The system is a 486-50 w/ 32MB RAM and plenty of free drive space
> > (over 200MB on the drive with X on it and over a gig elsewhere) with a
> > Diamond Viper VESA SVGA card (which I'm using as a Generic VGA card
> > until I can at least get the thing to start).
> > I'm running 2.2-RELEASE and the latest version of X11 from the ftp
> > site.
> > Any help would be appreciated. Thank you.
>
> Try to capture the X server output and post that.
>
> > (Also, please tell me where to direct X questions in the future...)
>
> You can try xfree86@xfree86.org.
>
>
> Doug White | University of Oregon
> Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant
> http://gladstone.uoregon.edu/~dwhite | Computer Science Major
>
>
>
>
>
-----------------------------------------------------------------------
This is your operator speaking
Joachim Kuebart
<joa@delos.lf.net>
<joa@stuttgart.netsurf.de>
<joki@kuebart.stuttgart.netsurf.de>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01BC40C9.CBDB91E0>