From: <jrf...@us...> - 2004-02-19 12:08:02
|
diff -urN /tmp/wiki.qjQHTM/wiki/text/CvsBranches /home/groups/d/dr/dri/wiki/text/CvsBranches --- /tmp/wiki.qjQHTM/wiki/text/CvsBranches 2004-01-01 16:07:49.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/CvsBranches 2004-02-18 11:42:32.000000000 -0800 @@ -1,4 +1,4 @@ -= DRI CVS Branches = +STUPID STUPID STUPID STUPID STUPID We're using CVS quite heavily and have a fairly structured layout of the repository. This document should explain how we're using CVS and what material is stored where. diff -urN /tmp/wiki.qjQHTM/wiki/text/DriTroubleshooting /home/groups/d/dr/dri/wiki/text/DriTroubleshooting --- /tmp/wiki.qjQHTM/wiki/text/DriTroubleshooting 2004-01-14 06:53:39.000000000 -0800 +++ /home/groups/d/dr/dri/wiki/text/DriTroubleshooting 2004-02-18 05:29:02.000000000 -0800 @@ -2,8 +2,6 @@ This process assumes you have XFree86 4.3.0 or newer installed. If not, update to XFree86 4.3.0 first. -'''Note, that as of 2003-09-21, the binary packages being distributed from dri.sourceforge.net are broken. If you want current DRI, use CVS for now.''' - Check that the DRM (Direct Rendering Module, the kernel module) is loaded and found your card. Do dmesg | grep drm. You should have several lines of info, with samples below: FreeBSD: @@ -139,7 +137,7 @@ (libexpat.so.1 : cannot open shared object file: No such file or directory) libGL error: unable to find driver: r200_dri.so }}} -then make sure that you have libexpat.so.1 installed. Unfortunately the file has slightly different names on different systems. If you're installing a binary snapshot and get this error message even with libexpat installed then check if you really have a libexpat.so.1 in /usr/lib. If not then make a symlink to the existing library with ln -s libexpat.so.<yourversion> /usr/lib/libexpat.so.1. +then make sure that you have libexpat.so.1 installed. Binary snapshots now come with a statically linked libexpat, so this should no longer be a problem. If you have a 3dfx card and it's complaining about libglide3, or there are glide errors, you need to install correct glide for your card as provided by your distribution. @@ -154,3 +152,6 @@ FreeBSD: Linux compatibility has its own set of issues. To debug linux DRI compatibility (i.e. quake3/UT), use {{{/compat/linux/usr/X11R6/bin/glxinfo}}} with {{{LIBGL_DEBUG=verbose}}} set. You should be using -current as of April 25, 2003 or -stable as of May 2nd, 2003. Your linux_dri version should exactly match the X you have installed. If not you'll probably get segfaults. If your XFree86 segfaults, make sure you don't have the linux_glx port installed. If you get coredumps on your system with SSE support (Pentium 3 and up, Athlon XP and up), you may need to set the environment variable MESA_FORCE_SSE to 1 due to what appears to be a bug with our linux compat's signal handling. On Mandrake 9.2 : big troubles I will try to recover. + +---- +CategoryTroubleshooting diff -urN /tmp/wiki.qjQHTM/wiki/text/Troubleshooting /home/groups/d/dr/dri/wiki/text/Troubleshooting --- /tmp/wiki.qjQHTM/wiki/text/Troubleshooting 2003-10-01 11:14:08.000000000 -0700 +++ /home/groups/d/dr/dri/wiki/text/Troubleshooting 2004-02-18 18:54:27.000000000 -0800 @@ -1,10 +1,11 @@ -= Troubleshooting = +Problem: -This is a list of problems users may run into and potential solutions. +After install last dri cvs, key '/' stop working. -[[FullSearch('CategoryTroubleshooting')]] + Option "XkbRules" "xfree86" + Option "XkbModel" "abnt2" + Option "XkbLayout" "br" -== Adding new troubleshooting items == +I had XFree 4.3.1. -To add new troubleshooting items choose the TroubleshootingTemplate when -creating a new page. +Installed last cvs version then the key stop working |