X-Windows does'nt start anymore

X-Windows does'nt start anymore

Post by Geert Van Lo » Wed, 12 May 1999 04:00:00



Hi,

Recently my linux crashed (yes, this is sometimes possible :-)). I was
running X-windows at that time.  Ctrl+Alt+Back didn't help so I had to use
the reset button.

After rebooting my X-window doesn't start anymore.  I get an error with a
font that can't be found.  However these X-fonts were loaded fine when
booting.

And when I shut down my system now, it fails to shut down these X-fonts.

Can anyone help me with this problem?

Thx anyway

Geert

 
 
 

X-Windows does'nt start anymore

Post by Geert Van Lo » Thu, 13 May 1999 04:00:00


This is me again.

I had forgotten to include my X.out file
So here it is

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.1-ac1 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: "be"
(**) Mouse: type: IntelliMouse, device: /dev/mouse, baudrate: 1200
(**) Mouse: buttons: 5
(**) Mouse: zaxismapping: (-)4 (+)5
(**) Mach64: Graphics device ID: "215CT222"
(**) Mach64: Monitor ID: "AOC 4N Series"
(--) Mach64: Mode "640x480" needs hsync freq of 53.01 kHz. Deleted.
(--) Mach64: Mode "1152x864" needs hsync freq of 53.51 kHz. Deleted.
(--) Mach64: Mode "800x600" needs hsync freq of 55.84 kHz. Deleted.
(--) Mach64: Mode "1024x768" needs hsync freq of 56.48 kHz. Deleted.
(--) Mach64: Mode "1280x1024" needs hsync freq of 51.02 kHz. Deleted.
(--) 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: Card type: PCI
(--) Mach64: Memory type: DRAM (1)
(--) Mach64: Clock type: Internal
(--) Mach64: Maximum allowed dot-clock: 80.000 MHz
(**) Mach64: Mode "800x600": mode clock =  50.000
(--) Mach64: Virtual resolution: 800x600
(--) Mach64: Video RAM: 1024k
(--) Mach64: Using hardware cursor

(--) Mach64: Ramdac is Internal
(--) Mach64: Ramdac speed: 80 MHz
(**) Mach64: Color weight: 565
(--) Mach64: Pixmap cache: 0 256x256 slots, 0 128x128 slots, 0 64x64 slots
(--) Mach64: Font cache: 0 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


Quote:>Hi,

>Recently my linux crashed (yes, this is sometimes possible :-)). I was
>running X-windows at that time.  Ctrl+Alt+Back didn't help so I had to use
>the reset button.

>After rebooting my X-window doesn't start anymore.  I get an error with a
>font that can't be found.  However these X-fonts were loaded fine when
>booting.

>And when I shut down my system now, it fails to shut down these X-fonts.

>Can anyone help me with this problem?

>Thx anyway

>Geert


 
 
 

X-Windows does'nt start anymore

Post by Christopher Brow » Fri, 14 May 1999 04:00:00




Quote:>I had forgotten to include my X.out file
>So here it is

>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.1-ac1 i686 [ELF]
>Configured drivers:
>  Mach64: accelerated server for ATI Mach64 graphics adaptors (Patchlevel 0)
>(using VT number 7)

... material elided ...
[critical material...]

Quote:>failed to set default font path 'unix/:-1'
>Fatal server error:
>could not open default font 'fixed'

There should be a section in the XFree86 config file (usually in
/etc/X11) that deals with where fonts may be located.

The problem you're having definitely has to do with a lack of font
location information.  I suggest you post the lines that contain the
word font; might do this thus:

% grep -i font /etc/X11/XF*

and then paste in the results of that.

Make sure that the paths that are indicated exist, and have fonts in
them.  You may perhaps have had fonts upgraded to be in a new location
that the configuration is not aware of.
--
"On the Internet, no one knows you're using Windows NT"


 
 
 

X-Windows does'nt start anymore

Post by Anthony J. Gabrielso » Fri, 14 May 1999 04:00:00


try reinstalling the fonts.

Anthony


> This is me again.

> I had forgotten to include my X.out file
> So here it is

> 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.1-ac1 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: "be"
> (**) Mouse: type: IntelliMouse, device: /dev/mouse, baudrate: 1200
> (**) Mouse: buttons: 5
> (**) Mouse: zaxismapping: (-)4 (+)5
> (**) Mach64: Graphics device ID: "215CT222"
> (**) Mach64: Monitor ID: "AOC 4N Series"
> (--) Mach64: Mode "640x480" needs hsync freq of 53.01 kHz. Deleted.
> (--) Mach64: Mode "1152x864" needs hsync freq of 53.51 kHz. Deleted.
> (--) Mach64: Mode "800x600" needs hsync freq of 55.84 kHz. Deleted.
> (--) Mach64: Mode "1024x768" needs hsync freq of 56.48 kHz. Deleted.
> (--) Mach64: Mode "1280x1024" needs hsync freq of 51.02 kHz. Deleted.
> (--) 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: Card type: PCI
> (--) Mach64: Memory type: DRAM (1)
> (--) Mach64: Clock type: Internal
> (--) Mach64: Maximum allowed dot-clock: 80.000 MHz
> (**) Mach64: Mode "800x600": mode clock =  50.000
> (--) Mach64: Virtual resolution: 800x600
> (--) Mach64: Video RAM: 1024k
> (--) Mach64: Using hardware cursor

> (--) Mach64: Ramdac is Internal
> (--) Mach64: Ramdac speed: 80 MHz
> (**) Mach64: Color weight: 565
> (--) Mach64: Pixmap cache: 0 256x256 slots, 0 128x128 slots, 0 64x64 slots
> (--) Mach64: Font cache: 0 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


> >Hi,

> >Recently my linux crashed (yes, this is sometimes possible :-)). I was
> >running X-windows at that time.  Ctrl+Alt+Back didn't help so I had to use
> >the reset button.

> >After rebooting my X-window doesn't start anymore.  I get an error with a
> >font that can't be found.  However these X-fonts were loaded fine when
> >booting.

> >And when I shut down my system now, it fails to shut down these X-fonts.

> >Can anyone help me with this problem?

> >Thx anyway

> >Geert

 
 
 

X-Windows does'nt start anymore

Post by Steffen Klu » Fri, 14 May 1999 04:00:00




Quote:>_FontTransSocketUNIXConnect: Can't connect: errno = 111
>failed to set default font path 'unix/:-1'
>Fatal server error:
>could not open default font 'fixed'

Could it be that you installed some font server (like xfs or
xfstt) lately? Check your XF86Config for a line similar to to
  FontPath "unix/:7100"

If it is there make sure there is a font server actually
listening on port 7100 (or whatever you find). Otherwise comment
out this line.

I had similar problems with earlier versions of xfstt when
running multiple X servers on the same machine. Only the first
server could connect to xfstt, the others failed.

Hope this helps
Steffen.

--

Fujitsu Australia Ltd
Keywords: photography, Mozart, UNIX, Islay Malt, dark skies
--

 
 
 

X-Windows does'nt start anymore

Post by Jeff Hayni » Fri, 04 Jun 1999 04:00:00


Well unfortunately booting a system like that can cause problems with files.
I think one question I have for you and one I haven't seen asked yet is --
"Have you run 'fsck' on your drive(s) yet?"  Often times 'fsck'  will detect
and correct the errors.  Failing that you may have to reinstall your fonts.

Let me know if this helps.

Jeff Haynie, Integration Specialist


> Hi,

> Recently my linux crashed (yes, this is sometimes possible :-)). I was
> running X-windows at that time.  Ctrl+Alt+Back didn't help so I had to use
> the reset button.

> After rebooting my X-window doesn't start anymore.  I get an error with a
> font that can't be found.  However these X-fonts were loaded fine when
> booting.

> And when I shut down my system now, it fails to shut down these X-fonts.

> Can anyone help me with this problem?

> Thx anyway

> Geert

 
 
 

1. Can't start X windows anymore (X Font Server problem)

I really hope someone can help me with this one...

Yesterday I had a Linux-capable laptop that happily booted up and entered X
Windows and KDE and worked wonderfully.

This morning I fired up the laptop to check a demo that I was due to give
later in the day and Linux won't get into  X Windows becuase of the
following message:

FontTransSocketUNIXConnect: Can't connect: errno=111
failed to set default font path 'unix/:-1'
Fatal server error
could not open default font 'fixed'

I've no idea what this means or indeed how to fix it! Does anyone know what
I need to do?

The last thing I was doing when the machine was OK was working with GIMP on
some logo graphics. This wouldn't allow me to save anything and I later
discovered that my disk usage was up to 100%! (I'm not sure how the disk has
filled up - is there a temporary GIMP file hanging around somewhere? If so,
where?) Whether this has contributed to the current problem I don't know.

I hope someone knows how to get my box running again.

Thanks,

Mark

2. Changing passwords for 600 users

3. X-windows in Windows 95 and type writers in X-windows

4. Support for ANVIL STALLION 8port cards?

5. X-windows can't start up

6. Trouble compiling atk-1.0.3 on Solaris 8

7. Can't start Control-panel via X-windows (Red Hat 3.2)

8. Switch GRUB to LILO

9. Can't start X-Windows. Aaarrgghh!

10. X-windows won't start

11. Oops...X-windows won't start :(

12. X-Windows won't start: /dev/console missing

13. Can't start X-windows