Author: branden
Date: 2003-10-22 15:24:48 -0500 (Wed, 22 Oct 2003)
New Revision: 697
Modified:
trunk/debian/changelog
trunk/debian/local/FAQ
Log:
Add several new entries to the FAQ:
+ The X server log says there was an error and it's disabling DRI. Is
that why the X server won't start?
+ The X server log says there was an error opening my "core pointer" or
the file /dev/input/mice. Is that why the X server won't start?
+ The X server log says it's skipping modules due to "No symbols found"
errors. Is that why the X server won't start?
+ The X server log says "AddScreen/ScreenInit failed for driver 0". Is
that why the X server won't start?
+ How can I tell if it's the X server crashing, or my X session exiting
abnormally?
- debian/local/FAQ
Modified: trunk/debian/changelog
===================================================================
--- trunk/debian/changelog 2003-10-22 17:53:46 UTC (rev 696)
+++ trunk/debian/changelog 2003-10-22 20:24:48 UTC (rev 697)
@@ -140,8 +140,21 @@
output is sure to be generated.
- debian/xserver-xfree86.config.in
- -- Branden Robinson <[EMAIL PROTECTED]> Tue, 21 Oct 2003 23:47:15 -0500
+ * Add several new entries to the FAQ:
+ + The X server log says there was an error and it's disabling DRI. Is
+ that why the X server won't start?
+ + The X server log says there was an error opening my "core pointer" or
+ the file /dev/input/mice. Is that why the X server won't start?
+ + The X server log says it's skipping modules due to "No symbols found"
+ errors. Is that why the X server won't start?
+ + The X server log says "AddScreen/ScreenInit failed for driver 0". Is
+ that why the X server won't start?
+ + How can I tell if it's the X server crashing, or my X session exiting
+ abnormally?
+ - debian/local/FAQ
+ -- Branden Robinson <[EMAIL PROTECTED]> Wed, 22 Oct 2003 15:21:34 -0500
+
xfree86 (4.2.1-12.1) unstable; urgency=low
* Fix typo in xlibs preinst. Closes: #213774, #213776
Modified: trunk/debian/local/FAQ
===================================================================
--- trunk/debian/local/FAQ 2003-10-22 17:53:46 UTC (rev 696)
+++ trunk/debian/local/FAQ 2003-10-22 20:24:48 UTC (rev 697)
@@ -107,6 +107,16 @@
achieve that?
*) How do I add custom sections to a dexconf-generated XF86Config or
XF86Config-4 file?
+*) The X server log says there was an error and it's disabling DRI. Is that
+ why the X server won't start?
+*) The X server log says there was an error opening my "core pointer" or
+ the file /dev/input/mice. Is that why the X server won't start?
+*) The X server log says it's skipping modules due to "No symbols found"
+ errors. Is that why the X server won't start?
+*) The X server log says "AddScreen/ScreenInit failed for driver 0". Is that
+ why the X server won't start?
+*) How can I tell if it's the X server crashing, or my X session exiting
+ abnormally?
GENERAL QUESTIONS
@@ -1615,4 +1625,117 @@
server configuration, and XF86Config-4(5x) for more information on XFree86 4.x
X server configuration.
+*) The X server log says there was an error and it's disabling DRI. Is that
+ why the X server won't start?
+
+No. If DRI (Direct Rendering Infrastructure) is disabled, then 3D-accelerated
+applications such as games may not run satisfactorily or at full speed, but
+this doesn't prevent the X server from working. A disabled DRI doesn't
+prevent your desktop from coming up, or programs like XTerm or Mozilla from
+running.
+
+If your X server is failing to start and you think this error message is the
+problem, look elsewhere; the problem is something else.
+
+*) The X server log says there was an error opening my "core pointer" or
+ the file /dev/input/mice. Is that why the X server won't start?
+
+Errors about "failure to initialize core devices" are usually fatal. Errors
+about failing to open "/dev/input/mice" usually aren't if they're not
+accompanied by a "failure to initialize core devices" message.
+
+If you have non-USB mouse configured, the Debian default XFree86 X server
+configuration sets up an extra input device so that you can just plug a USB
+mouse in and use it as well.
+
+It's easy enough to determine whether errors opening /dev/input/mice are
+really the cause of a failing X server. As root, run the following command:
+
+# X -allowMouseOpenFail
+
+(If you get a message like "Server already active for display 0", then you're
+probably already running X somewhere. Try specifying a display for the X
+server to run on:
+
+# X :50 -allowMouseOpenFail
+
+See the Xserver(1x) and XFree86(1x) manual pages for more information.)
+
+If the X server does not start, then the mouse device is not your problem.
+Search the X server's log (in the above examples, /var/log/XFree86.0.log or
+/var/log/XFree86.50.log) for other errors.
+
+If the X server *does* start, then you *do* have a mouse problem. Use
+"dpkg-reconfigure xserver-xfree86" to correct the configuration of your mouse.
+The "mdetect" package and utility of the same name may help you to determine
+how the XFree86 X server should be configured in this regard. Install the
+package and run the following command:
+
+# mdetect -x
+
+Note that the X server will usually succeed in opening the /dev/input/mice
+device (if it exists), even if there is no mouse actually plugged into the
+port. That's because the Linux kernel's "mousedev" driver (which handles
+/dev/input/mice) serves as a go-between for userspace processes like the X
+server and your actual mouse hardware.
+
+*) The X server log says it's skipping modules due to "No symbols found"
+ errors. Is that why the X server won't start?
+
+Generally, no.
+
+(II) Loading /usr/X11R6/lib/modules/fonts/libspeedo.a
+Skipping "/usr/X11R6/lib/modules/fonts/libspeedo.a:spencode.o": No symbols found
+
+Messages like the above are not fatal. If your X server refuses to start,
+it's most likely for some other reason.
+
+*) The X server log says "AddScreen/ScreenInit failed for driver 0". Is that
+ why the X server won't start?
+
+Usually, yes. Look for lines before that in the X server log that start with
+"(EE)". For instance, users of Intel i810-family chipsets often have this
+problem if they're running a Linux kernel that doesn't support GART access to
+the AGP port. (This facility is provided by a kernel module called
+"agpgart".)
+
+If you're an i810 user and you see the following in the log:
+
+(EE) Unable to open /dev/agpgart (No such device)
+
+Then that is the exact problem you have. You need to install a Debian
+kernel-image package that contains support for AGP GART. Official Debian
+kernel-image packages for the x86 and compatible processors typically do.
+
+*) How can I tell if it's the X server crashing, or my X session exiting
+ abnormally?
+
+Generally, when the X server has no more clients to manage, it will exit
+immediately. This can look a lot like a "crash" to the uninitiated, especially
+when the clients themselves crash.
+
+It's easy to determine whether the X server itself works. As root, simply run
+the command "X". If that brings up the little root window weave and the X
+cursor, then *you do not have a fatal X server configuration problem*. The X
+server is working. Use CTRL-ALT-BACKSPACE to kill it.
+
+Alternatively, if you're using a display manager and you can see the greeter
+(login screen), then the X server is running: *you do not have a fatal X server
+configuration problem*. Most failures after that point are client-side
+problems. (Yes, there are bugs in the X server that can cause it spontaneously
+crash, but if the X server "crashes" immediately upon logging in to your X
+session, it's probably a client side problem.)
+
+If the X server doesn't start with the command "X", but you get a message like
+"Server already active for display 0", then you're probably already running X
+somewhere. See the "The X server log says there was an error opening my 'core
+pointer'..." question above for more information on how to deal with this.
+
+Alternatively, if you're using a display manager and you can see the
+greeter (login screen), then the X server is running: *you do not have a
+fatal X server configuration problem*. Most failures after that point
+are client-side problems. (Yes, there are bugs in the X server that can
+cause it spontaneously crash, but if the X server "crashes" immediately
+upon logging in to your X session, it's probably a client side problem.)
+
vim:set ai et sts=2 sw=2 tw=78:
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
