Vincent Danen wrote:
>
> I've had a few crashes (power failures, etc.) which I think are really
> screwing up my system. Standard MDK6.0 system, everything but the kernel
> upgraded (using 19mdk... 27mdk is no longer in the updates?). Anyways,
> this is what the X-server gives me when I do a startx or try to load
> gdm/kdm/etc.:
>
> XFree86 Version 3.3.3.1 / X Window System
> (protocol Version 11, revision 0, vendor release 6300)
> Release Date: January 4 1999
> 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: Linux 2.2.9-chmou1 i686 [ELF]
> Configured drivers:
> Mach64: accelerated server for ATI Mach64 graphics adaptors (Patchlevel
> 0)
> (using VT number 7)
>
> XF86Config: /usr/X11R6/lib/X11/XF86Config
> (**) stands for supplied, (--) stands for probed/default values
> (**) XKB: keycodes: "xfree86"
> (**) XKB: types: "default"
> (**) XKB: compat: "default"
> (**) XKB: symbols: "us(pc101)"
> (**) XKB: geometry: "pc"
> (**) XKB: rules: "xfree86"
> (**) XKB: model: "pc101"
> (**) XKB: layout: "us"
> (**) Mouse: type: Microsoft, device: /dev/mouse, baudrate: 1200
> (**) Mouse: buttons: 3, 3 button emulation (timeout: 50ms)
> (**) Mach64: Graphics device ID: "My Video Card"
> (**) Mach64: Monitor ID: "My Monitor"
> (--) Mach64: Mode "800x600" needs hsync freq of 64.02 kHz. Deleted.
> (--) Mach64: Mode "1024x768" needs hsync freq of 62.50 kHz. Deleted.
> (--) Mach64: Mode "1152x864" needs hsync freq of 62.42 kHz. Deleted.
> (--) Mach64: Mode "1280x1024" needs hsync freq of 64.25 kHz. Deleted.
> (--) Mach64: Mode "1024x768" needs hsync freq of 70.24 kHz. Deleted.
> (--) Mach64: Mode "1152x864" needs hsync freq of 70.88 kHz. Deleted.
> (--) Mach64: Mode "1280x1024" needs hsync freq of 74.59 kHz. Deleted.
> (--) Mach64: Mode "1600x1200" needs hsync freq of 75.00 kHz. Deleted.
> (--) Mach64: Mode "1152x864" needs hsync freq of 76.01 kHz. Deleted.
> (--) Mach64: Mode "1280x1024" needs hsync freq of 78.86 kHz. Deleted.
> (--) Mach64: Mode "1024x768" needs hsync freq of 80.21 kHz. Deleted.
> (--) Mach64: Mode "1280x1024" needs hsync freq of 81.13 kHz. Deleted.
> (--) Mach64: Mode "1600x1200" needs hsync freq of 87.50 kHz. Deleted.
> (--) Mach64: Mode "1152x864" needs hsync freq of 89.62 kHz. Deleted.
> (--) Mach64: Mode "1280x1024" needs hsync freq of 91.15 kHz. Deleted.
> (--) Mach64: Mode "1600x1200" needs hsync freq of 93.75 kHz. Deleted.
> (--) Mach64: Mode "1600x1200" needs hsync freq of 105.77 kHz. Deleted.
> (--) Mach64: Mode "1280x1024" needs hsync freq of 107.16 kHz. Deleted.
> (--) Mach64: Mode "1800X1440" needs hsync freq of 96.15 kHz. Deleted.
> (--) Mach64: Mode "1800X1440" needs hsync freq of 104.52 kHz. Deleted.
> (**) FontPath set to "unix/:-1"
> (--) Mach64: PCI: Mach64 RagePro rev 92, Aperture @ 0xe4000000, Registers @
> 0xe6000000, Block I/O @ 0xd000
> (--) Mach64: PCI (92) and CONFIG_CHIP_ID (124) don't agree on ChipRev,
> using PCI value
> (--) Mach64: Card type: AGP
> (--) Mach64: Memory type: SDRAM (4)
> (--) Mach64: Clock type: Internal
> (--) Mach64: Maximum allowed dot-clock: 230.000 MHz
> (**) Mach64: Mode "1152x864": mode clock = 89.900
> (--) Mach64: Virtual resolution: 1152x864
> (--) Mach64: Video RAM: 8192k
> (--) Mach64: Using hardware cursor
> (--) Mach64: Using 16 MB aperture @ 0xe4000000
> (--) Mach64: Using 4 KB register aperture @ 0xe6000000
> (--) Mach64: Ramdac is Internal
> (--) Mach64: Ramdac speed: 230 MHz
> (--) Mach64: Horizontal Sync width (32) in mode "1152x864"
> shortened to 248 pixels
> (--) Mach64: Pixmap cache: 2 256x256 slots, 8 128x128 slots, 32 64x64 slots
> (--) Mach64: Font cache: 16 fonts
> _FontTransSocketUNIXConnect: Can't connect: errno = 111
> failed to set default font path 'unix/:-1'
> Fatal server error:
> could not open default font 'fixed'
>
> When reporting a problem related to a server crash, please send
> the full server output, not just the last messages
>
> mach64ProgramClkMach64CT: Warning: Q < 10.66666667
> X connection to :0.0 broken (explicit kill or server shutdown).
>
> --
> How do I go about fixing this? I can't wait for a reply right now, but
> this has happened to me twice now on this machine (and never once on the
> server machine... mind you, it has a UPS protecting it somewhat). Any
> ideas? Going to do a reinstall right now, but if this happens in the
> future I'd like to know how to fix it.
chkconfig xfs on
/etc/rc.d/init.d/xfs start
startx
You'll notice that the errors are about not being able to set the font
path used by the X font server (xfs). That causes it to fail when it
tries to find the default 'fixed' font. BOOM!
Running xfs should clear up the problem.
--
Steve Philp
Network Administrator
Advance Packaging Corporation
[EMAIL PROTECTED]
