A few suggestions: 1) Please send non-Debian-specific X questions to newbie@xfree86.org until there are official Debian XFree86 4.x packages, at which time you should use debian-user@lists.debian.org. Unless you subscribe to those lists, please be sure to request private replies. 2) Please avoid asking sundry unrelated questions in one huge paragraph; it makes it difficult to reply. 3) Make sure you've set up the "Modules" section of your XF86Config to get the proper extensions loaded. It looks like you're only loading a very few. You've got a subsection for "extmod" but you never ask it to be loaded. I think the SHAPE extension is in the extmod module. 4) The libGLU problem is being worked out. At first XFree86 didn't build it in their version of Mesa, now it looks like they might start. Please be patient and keep in mind that these .debs are unstable and unofficial. 5) The tdfx driver problems were fixed in phase2v5; please test the latest versions of these packages BEFORE reporting problems. I do actually fix bugs. 6) Please, please, please send Debian-specific questions about the unofficial X .debs to debian-x@lists.debian.org. The other caveats above about mailing lists apply here. That way more than one person can help you out, since many more people know the answers to your questions. When XFree86 4.x .debs become official, use debian-user. 7) Please review the language at the X Strike Force regarding these .debs. "they are for testing, not general-purpose use". The content and style of your mail indicates to me that you are approach these packages as an end-user, not a fellow developer who is experienced with the X Window System and who knows how to help people fix bugs as well as find them. 8) I appreciate your patience as I (and the helpful people on debian-x) move toward official XFree86 4.x .debs that WILL be for general-purpose use. Having to offer private tutorials to people who send me mail directly does not hasten this process, so please consider other avenues for assistance before mailing me directly in the future. On Tue, Sep 12, 2000 at 03:18:43PM -0400, Travis Whitton wrote: > Branden, > I installed XFree86 4.0.1 from your apt repository yesterday. I'm using > Debian Woody w/ the Linux 2.4.0-test7 kernel w/ DRI Rage 128 support and > agpgart support compiled as modules. When I did the update yesterday, I > also installed xlibgl1. I tried tuxracer (a GL game included w/ Debian) > as a test and the 3d acceleration worked great. After doing an apt-get > dist-upgrade this morning, all of my GL applications(including the > xscreensaver hacks) blink constantly and when I play Tuxracer, portions of > the screen flicker constantly. Did something get changed after the > upgrade? I have 2 other computers in my office with identical > configurations(both hardware and software), and they're having the same > problems. Also, until the initial upgrade to 4.0.1, I was using helix > gnome as my desktop environment. Now when I run helix code all of the > icons have a 1 inch grey border around them and all of the window > borders are either half grey or non-existent. When I try and start > enlightenment(and several other apps like licq), I get the error message > that the current xserver does not support the shape extension. Is this > also the root of the helix problem? Is the shape extension not being > present directly related to the r128 module I'm using, or is it more > generally related to the entire X server? Since xlibgl-dev does not > include the GLU libraries, I've manually extracted them from mesag3 and > copied them into /usr/local/lib so that I can compile Mesa based apps. I > see that xlibgl1 conflicts with mesag3(which provides GLU) and that > xlibgl1 does not provide the GLU libraries. Is this going to be fixed in > future updates? How will GLU be provided? I also have a Voodoo 3 card > which I tried with yesterday's packages from your repository. > /var/log/XFree86.0.log had a bunch of messages about tdfx_drv.o having > functions that were unresolved, and I could never get it to startx > successfully. Have you had any other reports of this problem? I'm going > to try it again with the newer packages, so I apologize if that problem > has been fixed. I'm attaching a copy of my XF86Config file in case > you're curious as to what my configuration is. > > Thanks, > Travis Whitton <whitton@atlantic.net> > # File generated by xf86config. > > # > # Copyright (c) 1999 by The XFree86 Project, Inc. > # > # Permission is hereby granted, free of charge, to any person obtaining a > # copy of this software and associated documentation files (the "Software"), > # to deal in the Software without restriction, including without limitation > # the rights to use, copy, modify, merge, publish, distribute, sublicense, > # and/or sell copies of the Software, and to permit persons to whom the > # Software is furnished to do so, subject to the following conditions: > # > # The above copyright notice and this permission notice shall be included in > # all copies or substantial portions of the Software. > # > # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR > # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, > # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL > # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, > # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF > # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE > # SOFTWARE. > # > # Except as contained in this notice, the name of the XFree86 Project shall > # not be used in advertising or otherwise to promote the sale, use or other > # dealings in this Software without prior written authorization from the > # XFree86 Project. > # > > # ********************************************************************** > # Refer to the XF86Config(4/5) man page for details about the format of > # this file. > # ********************************************************************** > > # ********************************************************************** > # Module section -- this section is used to specify > # which dynamically loadable modules to load. > # ********************************************************************** > # > Section "Module" > > > Load "dbe" # Double buffer extension > Load "glx" > Load "dri" > > # This loads the miscellaneous extensions module, and disables > # initialisation of the XFree86-DGA extension within that module. > # SubSection "extmod" > # Option "omit xfree86-dga" # don't initialise the DGA extension > # EndSubSection > > # This loads the Type1 and FreeType font modules > Load "type1" > Load "freetype" > > # This loads the GLX module > # Load "glx" > > EndSection > > # ********************************************************************** > # Files section. This allows default font and rgb paths to be set > # ********************************************************************** > > Section "Files" > > RgbPath "/usr/X11R6/lib/X11/rgb" > FontPath "/usr/X11R6/lib/X11/fonts/misc/" > FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" > FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" > FontPath "/usr/X11R6/lib/X11/fonts/Type1/" > FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" > FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" > FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" > > # The module search path. The default path is shown here. > > ModulePath "/usr/X11R6/lib/modules" > > EndSection > > # ********************************************************************** > # Server flags section. > # ********************************************************************** > > Section "ServerFlags" > > # Uncomment this to cause a core dump at the spot where a signal is > # received. This may leave the console in an unusable state, but may > # provide a better stack trace in the core dump to aid in debugging > > # Option "NoTrapSignals" > > # Uncomment this to disable the <Crtl><Alt><BS> server abort sequence > # This allows clients to receive this key event. > > # Option "DontZap" > > # Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching > # sequences. This allows clients to receive these key events. > > # Option "Dont Zoom" > > # Uncomment this to disable tuning with the xvidtune client. With > # it the client can still run and fetch card and monitor attributes, > # but it will not be allowed to change them. If it tries it will > # receive a protocol error. > > # Option "DisableVidModeExtension" > > # Uncomment this to enable the use of a non-local xvidtune client. > > # Option "AllowNonLocalXvidtune" > > # Uncomment this to disable dynamically modifying the input device > # (mouse and keyboard) settings. > > # Option "DisableModInDev" > > # Uncomment this to enable the use of a non-local client to > # change the keyboard or mouse settings (currently only xset). > > # Option "AllowNonLocalModInDev" > > EndSection > > Section "InputDevice" > > Identifier "Keyboard1" > Driver "Keyboard" > Option "AutoRepeat" "500 30" > Option "XkbRules" "xfree86" > Option "XkbModel" "pc104" > Option "XkbLayout" "us" > > EndSection > > Section "InputDevice" > > Identifier "Mouse1" > Driver "mouse" > Option "Protocol" "Intellimouse" > Option "Device" "/dev/mouse" > > EndSection > > Section "Monitor" > > Identifier "Sony" > HorizSync 31.5 - 79.0 > VertRefresh 50-100 > > EndSection > > > # ********************************************************************** > # Graphics device section > # ********************************************************************** > > # Any number of graphics device sections may be present > > # Standard VGA Device: > > Section "Device" > Identifier "Standard VGA" > VendorName "Unknown" > BoardName "Unknown" > Driver "vga" > > # The BusID line is used to specify which of possibly multiple devices > # this section is intended for. When this line isn't present, a device > # section can only match up with the primary video device. For PCI > # devices a line like the following could be used. This line should not > # normally be included unless there is more than one video device > # intalled. > > # BusID "PCI:0:10:0" > > # VideoRam 256 > > # Clocks 25.2 28.3 > > EndSection > > # Device configured by xf86config: > > Section "Device" > Identifier "Rage 128" > Driver "r128" > #VideoRam 16384 > EndSection > > > # ********************************************************************** > # Screen sections > # ********************************************************************** > > # Any number of screen sections may be present. Each describes > # the configuration of a single screen. A single specific screen section > # may be specified from the X server command line with the "-screen" > # option. > Section "Screen" > Identifier "Screen 1" > Device "Rage 128" > Monitor "Sony" > DefaultDepth 24 > > Subsection "Display" > Depth 8 > Modes "640x480" "800x600" "1024x768" "1280x1024" > ViewPort 0 0 > EndSubsection > Subsection "Display" > Depth 16 > Modes "640x480" "800x600" "1024x768" "1280x1024" > ViewPort 0 0 > EndSubsection > Subsection "Display" > Depth 24 > Modes "1280x1024" "1024x768" "800x600" "640x480" > ViewPort 0 0 > EndSubsection > EndSection > > # ********************************************************************** > # ServerLayout sections. > # ********************************************************************** > > # Any number of ServerLayout sections may be present. Each describes > # the way multiple screens are organised. A specific ServerLayout > # section may be specified from the X server command line with the > # "-layout" option. In the absence of this, the first section is used. > # When now ServerLayout section is present, the first Screen section > # is used alone. > > Section "ServerLayout" > > # The Identifier line must be present > Identifier "Simple Layout" > > # Each Screen line specifies a Screen section name, and optionally > # the relative position of other screens. The four names after > # primary screen name are the screens to the top, bottom, left and right > # of the primary screen. In this example, screen 2 is located to the > # right of screen 1. > > Screen "Screen 1" > > # Each InputDevice line specifies an InputDevice section name and > # optionally some options to specify the way the device is to be > # used. Those options include "CorePointer", "CoreKeyboard" and > # "SendCoreEvents". > > InputDevice "Mouse1" "CorePointer" > InputDevice "Keyboard1" "CoreKeyboard" > > EndSection > > Section "DRI" > Mode 0666 > EndSection -- G. Branden Robinson | If you wish to strive for peace of soul, Debian GNU/Linux | then believe; if you wish to be a branden@deadbeast.net | devotee of truth, then inquire. http://deadbeast.net/~branden/ | -- Friedrich Nietzsche
Attachment:
pgprk3FHLMQe_.pgp
Description: PGP signature