No xserver after upgrade

To: debian-user@lists.debian.org
Subject: No xserver after upgrade
From: Bill Moseley <moseley@hank.org>
Date: Sat, 28 Feb 2004 11:34:59 -0800
Message-id: <[🔎] 20040228193459.GA7539@hank.org>
I updated my Sid Toshiba laptop yesterday and now X fails to start.
The XFree86.0.log isn't giving me (that I can tell) any clues.  So I'm 
looking for suggestions on how to debug this.  

I'll also append my XFree86-4 config just in case that helps.

The laptop has a Savage/IX-MV dispaly.

ii  xserver-common 4.3.0-2        files and utilities common to all X servers
ii  xserver-xfree8 4.3.0-2        the XFree86 X server

>From the log:

XFree86 Version 4.3.0.1 (Debian 4.3.0-2 20040218145349 root@butters.hq.amellus.com)


[Not sure if this was an existing issue before yesterday]

(II) LoadModule: "GLcore"
(II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a
Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_clip.o":  No symbols found
Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_norm.o":  No symbols found
Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_xform.o":  No symbols found
Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_vertex.o":  No symbols found


[Now, I get hundreds of these:]

(II) SAVAGE(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) SAVAGE(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000

[then it ends with these line -- I'm not requesting these mode, AFAIK:]

(II) SAVAGE(0): Not using default mode "640x350" (vrefresh out of range)
(II) SAVAGE(0): Not using default mode "320x175" (vrefresh out of range)
(II) SAVAGE(0): Not using default mode "640x400" (vrefresh out of range)
(II) SAVAGE(0): Not using default mode "320x200" (vrefresh out of range)
(II) SAVAGE(0): Not using default mode "720x400" (vrefresh out of range)
(II) SAVAGE(0): Not using default mode "360x200" (vrefresh out of range)
(II) SAVAGE(0): Not using default mode "640x480" (vrefresh out of range)
(II) SAVAGE(0): Not using default mode "320x240" (vrefresh out of range)
(II) SAVAGE(0): Not using default mode "800x600" (vrefresh out of range)
(II) SAVAGE(0): Not using default mode "400x300" (vrefresh out of range)
(II) SAVAGE(0): Not using default mode "1024x768" (vrefresh out of range)
(II) SAVAGE(0): Not using default mode "512x384" (vrefresh out of range)
(II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
(II) SAVAGE(0): Not using default mode "512x384" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1152x864" (exceeds panel dimensions)
(II) SAVAGE(0): Not using default mode "576x432" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1280x960" (exceeds panel dimensions)
(II) SAVAGE(0): Not using default mode "1280x960" (exceeds panel dimensions)
(II) SAVAGE(0): Not using default mode "640x480" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1280x1024" (exceeds panel dimensions)
(II) SAVAGE(0): Not using default mode "640x512" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1280x1024" (exceeds panel dimensions)
(II) SAVAGE(0): Not using default mode "640x512" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1280x1024" (exceeds panel dimensions)
(II) SAVAGE(0): Not using default mode "640x512" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1600x1200" (exceeds panel dimensions)
(II) SAVAGE(0): Not using default mode "800x600" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1600x1200" (exceeds panel dimensions)
(II) SAVAGE(0): Not using default mode "800x600" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1600x1200" (exceeds panel dimensions)
(II) SAVAGE(0): Not using default mode "800x600" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1600x1200" (exceeds panel dimensions)
(II) SAVAGE(0): Not using default mode "800x600" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) SAVAGE(0): Not using default mode "800x600" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1792x1344" (insufficient memory for mode)
(II) SAVAGE(0): Not using default mode "896x672" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1792x1344" (insufficient memory for mode)
(II) SAVAGE(0): Not using default mode "896x672" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1856x1392" (insufficient memory for mode)
(II) SAVAGE(0): Not using default mode "928x696" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1856x1392" (insufficient memory for mode)
(II) SAVAGE(0): Not using default mode "928x696" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) SAVAGE(0): Not using default mode "960x720" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) SAVAGE(0): Not using default mode "960x720" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1152x768" (exceeds panel dimensions)
(II) SAVAGE(0): Not using default mode "1400x1050" (exceeds panel dimensions)
(II) SAVAGE(0): Not using default mode "700x525" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1400x1050" (exceeds panel dimensions)
(II) SAVAGE(0): Not using default mode "700x525" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1600x1024" (exceeds panel dimensions)
(II) SAVAGE(0): Not using default mode "800x512" (hsync out of range)
(II) SAVAGE(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) SAVAGE(0): Not using default mode "960x720" (hsync out of range)
(II) SAVAGE(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
(II) SAVAGE(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
(II) SAVAGE(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Fatal server error:
Caught signal 4.  Server aborting

XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 0 requests (0 known processed) with 0 events remaining.


Here's my config:


Section "Files"
	FontPath	"/usr/lib/X11/fonts/misc"
	FontPath	"/usr/lib/X11/fonts/100dpi"
	FontPath	"/usr/lib/X11/fonts/75dpi"
EndSection

Section "Module"
	Load	"GLcore"
	Load	"bitmap"
	Load	"dbe"
	Load	"ddc"
	Load	"dri"
	Load	"extmod"
	Load	"freetype"
	Load	"glx"
	Load	"int10"
	Load	"record"
	Load	"type1"
	Load	"vbe"
EndSection

Section "InputDevice"
	Identifier	"Generic Keyboard"
	Driver		"keyboard"
	Option		"CoreKeyboard"
	Option		"XkbRules"	"xfree86"
	Option		"XkbModel"	"pc104"
	Option		"XkbLayout"	"us"
EndSection

Section "InputDevice"
	Identifier	"Configured Mouse"
	Driver		"mouse"
	Option		"CorePointer"
	Option		"Device"		"/dev/psaux"
	Option		"Protocol"		"ImPS/2"
	Option		"Emulate3Buttons"	"true"
	Option		"ZAxisMapping"		"4 5"
EndSection


Section "Device"
	Identifier	"s3 Savage/IX-MV"
	Driver		"savage"
EndSection

Section "Monitor"
	Identifier	"Generic Monitor"
	HorizSync	30-60
	VertRefresh	50-75
	Option		"DPMS"
EndSection

Section "Screen"
	Identifier	"Default Screen"
	Device		"s3 Savage/IX-MV"
	Monitor		"Generic Monitor"
	DefaultDepth	24
	SubSection "Display"
		Depth		24
		Modes		"1024x768"
	EndSubSection
EndSection

Section "ServerLayout"
	Identifier	"Default Layout"
	Screen		"Default Screen"
	InputDevice	"Generic Keyboard"
	InputDevice	"Configured Mouse"
EndSection

Section "DRI"
	Mode	0666
EndSection




-- 
Bill Moseley
moseley@hank.org
Reply to:
Follow-Ups:
- Re: No xserver after upgrade
  - From: Bill Moseley <moseley@hank.org>
Prev by Date: CUPS+KDE
Next by Date: Re: upgrade to linux 2.6.3 causing strange behaviour
Previous by thread: CUPS+KDE
Next by thread: Re: No xserver after upgrade
Index(es):
- Date
- Thread