[PyMOL] enable direct rendering DRI on fedora core 2
Hi everyone! how can I enable direct rendering DRI on fedora core 2? I have an ATI radeon 8500 LE, Should I use the redeon driver, or the r200 driver? I edited my xorg.conf file is as below, but VMD and pymol tells me I am still using indirect mesa rendering, and it is SLOW. the ATI closed source driver doesn't work on the fedora 2.6 kernel so I cant use that. cheers Dan # XFree86 4 configuration created by pyxf86config Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Files" # RgbPath is the location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. # Multiple FontPath entries are allowed (they are concatenated together) # By default, Red Hat 6.0 and later now use a font server independent of # the X server to render fonts. RgbPath "/usr/X11R6/lib/X11/rgb" FontPath "unix/:7100" EndSection Section "Module" Load "dbe" Load "extmod" Load "fbdevhw" Load "glx" Load "record" Load "freetype" Load "type1" Load "dri" EndSection Section "InputDevice" # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) # Option "Xleds" "1 2 3" # To disable the XKEYBOARD extension, uncomment XkbDisable. # Option "XkbDisable" # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # Option "XkbModel" "pc102" # If you have a US Microsoft Natural keyboard, you can use: # Option "XkbModel" "microsoft" # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # Option "XkbLayout" "de" # or: # Option "XkbLayout" "de" # Option "XkbVariant""nodeadkeys" # # If you'd like to switch the positions of your capslock and # control keys, use: # Option "XkbOptions""ctrl:swapcaps" # Or if you just want both to be control, use: # Option "XkbOptions""ctrl:nocaps" # Identifier "Keyboard0" Driver "keyboard" Option "XkbModel" "pc105" Option "XkbLayout" "fi" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "yes" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"CPD-G520" DisplaySize 400300 HorizSync30.0 - 130.0 VertRefresh 48.0 - 170.0 Option "dpms" EndSection Section "Device" Identifier "Videocard0" Driver "radeon" VendorName "Videocard vendor" BoardName "ATI Radeon 8500LE" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor"Monitor0" DefaultDepth 24 DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes"1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "DRI" Group0 Mode 0666 EndSection Dr. Daniel James White BSc. (Hons.) PhD Cell Biology Department of biological and environmental science PO Box 35 University of Jyväskylä Jyväskylä FIN 40014 Finland +358 14 260 4183 (work) +358 468102840 (new mobile) NEW PHONE NUMBER!!! http://www.chalkie.org.uk d...@chalkie.org.uk wh...@cc.jyu.fi
[PyMOL] Re: [o-info] enable direct rendering DRI on fedora core 2
Dr. Daniel James White PhD wrote: > how can I enable direct rendering DRI on fedora core 2? I have an ATI radeon 8500 LE, Should I use the redeon driver, or the r200 driver? You want the 'r200' driver. See: http://dri.sourceforge.net/doc/dri_driver_features.phtml There are actually two drivers at the X level, called 'r200' and 'radeon'. 'r200' is for Radeon 8500 and up, 'radeon' is for older Radeons. Confusingly, they both use the same kernel level driver which is *also* named 'radeon'. But the driver you specify in the xorg.conf is the X level one. Also, if your card is PCI rather than AGP, there may be some extra work you may have to do... -- Matt Matthew Zimmerman Interdisciplinary Biophysics, University of Virginia http://www.people.virginia.edu/~mdz4c/ Lab: 4-223 Jordan Hall, 1300 Jefferson Park Avenue, Charlottesville, VA 22908 (434)924-2948 Home: 2655-C Barracks Road Charlottesville, VA 22901 (434)244-7989
Re: [PyMOL] enable direct rendering DRI on fedora core 2
Daniel, Did you use the 'glxinfo' command in an xterminal under FC2 to check if 'direct rendering: Yes' is reported. Assuming you have your board in an AGP slot and used the System Settings-> Display control panel to enable the radeon driver, the resulting xorg.conf should be preconfigured to enable DRI. If you are interested in using the ATI closed source fglrx driver instead I posted a set of instructions for FC2 at... http://www.redhat.com/archives/fedora-list/2004-June/msg01514.html Jack
RE: [PyMOL] CGO raytracing problem
Gareth, Yes...triangles needs normals in order to compute lighting. You can compute a single normal using cross products between any two sides of the triangle, but you do have to be concerned about handedness, both in terms of the normal direction, and in the ordering of vertices. If I recall correctly, OpenGL triangles should be right handed: so if you're facing the front of the triangle with the normal pointed at you, then the vertices should be drawn with counter-clockwise ordering. In other words, with vertices: p1, p2, p3, the cross product (p2 - p1) X (p3 - p1) should point in the same direction as the triangle normal. If it doesn't, then swap the ordering of any two points. Cheers, Warren -- mailto:war...@delsci.com Warren L. DeLano, Ph.D. Principal Scientist DeLano Scientific LLC Voice (650)-346-1154 Fax (650)-593-4020 > -Original Message- > From: pymol-users-ad...@lists.sourceforge.net > [mailto:pymol-users-ad...@lists.sourceforge.net] On Behalf Of > Gareth Stockwell > Sent: Wednesday, June 09, 2004 8:33 AM > To: pymol-users > Subject: [PyMOL] CGO raytracing problem > > > Hello, > > I have a problem ray-tracing some CGO objects. Basically I > have a script which produces a surface, in the form of a load > of CGO triangles. This is done using a command which looks like: > > my_cgo = [ BEGIN, TRIANGLES, > > COLOR, r, g, b, > VERTEX x1, y1, z1, > VERTEX x2, y2, z2, > VERTEX x3, y3, z3, > > ... > > END > ] > > (See attached script cgo.py for an example) > > This works fine, until I try to ray-trace it. What I see is > that, from some angles, it ray-traces OK, but then if I > rotate by 45 or 90 degrees, the ray-traced image gets darker > until it disappears. > > I suspect that surface normals are the problem - do I need to > compute and then explictly state a normal for each vertex? > > Gareth > > > -- > Gareth Stockwell > European Bioinformatics Institute >
