Article View: comp.os.linux.x
Article #56Fatal (X-) server error: Hung on ApmSync()
From: Gerd Roethig
Date: Tue, 09 Feb 1999 00:00
Date: Tue, 09 Feb 1999 00:00
116 lines
5931 bytes
5931 bytes
Hello all,
after some trouble with the X-server that came with my graphics card
(Yakumo Voodoo Rush 3D with Alliance Promotion AT25 chip) I upgraded
to the latest version 3.3.3.1 of Xfree86 X Window System. In contrast
to that server provided by my graphics card vendor the new XF86_SVGA
server detects the chipset and my font path and tries to start, but it
never gets past this:
XFree86 Version 3.3.3.1 / X Window System
(protocol Version 11, revision 0, vendor release 6300)
Release Date: December 29 1998
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.0.35 i686 [ELF]
Configured drivers:
SVGA: server for SVGA graphics adaptors (Patchlevel 0):
NV1, STG2000, RIVA128, RIVATNT, ET4000, ET4000W32, ET4000W32i,
ET4000W32i_rev_b, ET4000W32i_rev_c, ET4000W32p,
ET4000W32p_rev_a,
ET4000W32p_rev_b, ET4000W32p_rev_c, ET4000W32p_rev_d, ET6000,
ET6100,
et3000, pvga1, wd90c00, wd90c10, wd90c30, wd90c24, wd90c31,
wd90c33,
gvga, ati, sis86c201, sis86c202, sis86c205, sis86c215,
sis86c225,
sis5597, sis5598, sis6326, tvga8200lx, tvga8800cs, tvga8900b,
tvga8900c, tvga8900cl, tvga8900d, tvga9000, tvga9000i,
tvga9100b,
tvga9200cxr, tgui9400cxi, tgui9420, tgui9420dgi, tgui9430dgi,
tgui9440agi, cyber9320, tgui9660, tgui9680, tgui9682, tgui9685,
cyber9382, cyber9385, cyber9388, cyber9397, cyber9520,
3dimage975,
3dimage985, clgd5420, clgd5422, clgd5424, clgd5426, clgd5428,
clgd5429, clgd5430, clgd5434, clgd5436, clgd5446, clgd5480,
clgd5462,
clgd5464, clgd5465, clgd6205, clgd6215, clgd6225, clgd6235,
clgd7541,
clgd7542, clgd7543, clgd7548, clgd7555, clgd7556, ncr77c22,
ncr77c22e,
cpq_avga, mga2064w, mga1064sg, mga2164w, mga2164w AGP, mgag200,
mgag100, oti067, oti077, oti087, oti037c, al2101, ali2228,
ali2301,
ali2302, ali2308, ali2401, cl6410, cl6412, cl6420, cl6440,
video7,
ark1000vl, ark1000pv, ark2000pv, ark2000mt, mx, realtek,
s3_virge,
AP6422, AT24, AT3D, s3_svga, NM2070, NM2090, NM2093, NM2097,
NM2160,
NM2200, ct65520, ct65525, ct65530, ct65535, ct65540, ct65545,
ct65546,
ct65548, ct65550, ct65554, ct65555, ct68554, ct69000, ct64200,
ct64300, mediagx, V1000, V2x00, p9100, spc8110, generic
(using VT number 7)
XF86Config: /etc/XF86Config
(**) stands for supplied, (--) stands for probed/default values
(**) Mouse: type: Microsoft, device: /dev/mouse, baudrate: 1200
(**) Mouse: buttons: 3, Chorded middle button
(**) SVGA: Graphics device ID: "Yakumo"
(**) SVGA: Monitor ID: "Visa"
(--) SVGA: Mode "1600x1200" needs hsync freq of 105.77 kHz. Deleted.
(--) SVGA: Mode "1800X1440" needs hsync freq of 104.52 kHz. Deleted.
(**) FontPath set to
"/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"
(--) SVGA: PCI: Alliance Semiconductor Unknown chipset (0x643d) rev 2,
Memory @ 0xfe000000, I/O @ 0xffa0
(--) SVGA: chipset: AT3D
(**) SVGA: videoram: 6110k
(**) SVGA: Using 8 bpp, Depth 8, Color weight: 666
(--) SVGA: Maximum allowed dot-clock: 175.500 MHz
(**) SVGA: Mode "640x480": mode clock = 45.800
(**) SVGA: Mode "800x600": mode clock = 69.650
(**) SVGA: Mode "1024x768": mode clock = 115.500
(--) SVGA: There is no mode definition named "1280x1024"
(--) SVGA: Removing mode "1280x1024" from list of valid modes.
(--) SVGA: Virtual resolution set to 1024x768
(--) SVGA: Generic SpeedUps selected (Flags=0x30)
(--) SVGA: AT3D: Using linear framebuffer at 0xFE000000 (PCI bus)
(--) SVGA: AT3D: Using hardware cursor
(--) SVGA: Using XAA (XFree86 Acceleration Architecture)
(--) SVGA: XAA: Solid filled rectangles
(--) SVGA: XAA: Screen-to-screen copy
(--) SVGA: XAA: CPU to screen color expansion (bitmap, stipple,
TE/NonTE imagetext, TE/NonTE polytext)
(--) SVGA: XAA: Using 8 128x128 areas for pixmap caching
(--) SVGA: XAA: Caching tiles and non-transparent stipples
(--) SVGA: XAA: General lines and segments
Fatal server error:
Hung in ApmSync()
When reporting a problem related to a server crash, please send
the full server output, not just the last messages
_X11TransSocketUNIXConnect: Can't connect: errno = 111
giving up.
xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error.
My question: What does this Hung in ApmSync() mean? And how can this
problem be solved?
Thank you very much for any hint in advance!
Cheers
Gerd
Gerd
P.S.: System: 486DX4/100 mit 32 MB, 10 GB Festplatte und Linux
Slackware 3.1 mit Kernel 2.0.36
Technical Details
Message-ID:
<36c37c53.39116343@news.uni-leipzig.de>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: faa64,ea04d5eb813aeb99,start X-Google-Attributes: gidfaa64,public X-Google-Thread: 10a997,ea04d5eb813aeb99,start X-Google-Attributes: gid10a997,public X-Google-Thread: 102983,ea04d5eb813aeb99,start X-Google-Attributes: gid102983,public X-Google-Thread: f4bda,ea04d5eb813aeb99,start X-Google-Attributes: gidf4bda,public X-Google-Thread: f9b51,ea04d5eb813aeb99,start X-Google-Attributes: gidf9b51,public X-Google-Thread: 1103af,ea04d5eb813aeb99,start X-Google-Attributes: gid1103af,public X-Google-Thread: 100b1f,ea04d5eb813aeb99,start X-Google-Attributes: gid100b1f,public From: roetg@server3.medizin.uni-leipzig.de (Gerd Roethig) Subject: Fatal (X-) server error: Hung on ApmSync() Date: 1999/02/09 Message-ID: <36c37c53.39116343@news.uni-leipzig.de> X-Deja-AN: 442496211 Content-Transfer-Encoding: 7bit Followup-To: comp.os.linux.x Content-Type: text/plain; charset=us-ascii Organization: Uni Leipzig Mime-Version: 1.0 Newsgroups: comp.os.linux.x,comp.os.linux.misc,comp.os.linux.help,comp.os.linux.setup,aus.computers.linux,alt.os.linux,alt.uu.comp.os.linux.questions