You probably deleted files from /tmp.
Owing to a Mandrake bug that civilme recently diagnosed based on my
trouble report, this can cause trouble.
The only known fix is to re-install X and the X font server.
On Mon, 20 Mar 2000, you wrote:
| OS: LM 6.1
| Graphics Card: ATI Rage Mach64
| RAM: 128MB
| Processor: 200MHz Intel II
|
| My system was operating just fine until yesterday. I made some changes to a
| couple of directories, which only had data files, not system files in them.
|
| However, upon reboot I got the following: I saw the normal startup (e.g.,
| system info, daemon startup, etc.) - no strange messages, except that the
| "at" daemon failed to start. X was configured to start right away, but this
| time the monitor wouldn't display the GUI (a faint light flickered).
|
| I thought it might have been my XF86Config file, but it wasn't. I ran
| Xconfigurator, too, which gave me a graphical display, so I know it's not
| the monitor. (I have three other machines using the same monitor -- one of
| which is also a LM 6.1 machine.) The following message output makes me
| believe it's font/card related.
|
| I did get the following output when I ran startx:
|
| (--) Mach64: card type: pci
| (--) Mach64: memory type: SGRAM(5)
| (--) Mach64: clock type: internal
| (--) Mach64: maximum allowed dot clock: 230.000 Mhz
| (**) Mach64: mode "1024x768": mode clock = 75.000
| (--) Mach64: virtual resolution: 1024x768
| (--) Mach64: video ram 8192k
| (--) Mach64: using hardware cursor
| (--) Mach64: using 16MB aperture @ 0xfc00000
| (--) Mach64: using 4k register aperture
| (--) Mach64: ramdac is internal
| (--) Mach64: ramdac speed is 230Mhz
| (**) Mach64: color weight: 565
| (--) 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'
| mach64ProgramClkMach64CT: Warning: Q < 10.66666667
|
| X connection to :0.0 broken (explicit kill or server shutdown)
|
|
| Can anyone shed some light on this problem for me? What should I change?
|
| -Lief Erickson
| not a Linux guru, but no dummy either.
--
I am "Brian, the man from babble-on" (Brian T. Schellenberger).
I can be reached at [EMAIL PROTECTED] .
I support http://www.eff.org & http://www.programming-freedom.org .
I boycott amazon.com. See http://www.gnu.org/philosophy/amazon.html .
