On Donnerstag 03 November 2005 22:28, Josh Babcock wrote:
> Mathias Fröhlich wrote:
> > Now using fglrx with a newer radeon on that machine. Since that it works
> > fine ...
>
> Hmm, after much pain and suffering I have installed fglrx on my machine.
> Good news: all my OpenGL apps work fine. Bad news: except FlightGear.
>
> It just falls back to software rendering. What X system are you using?
> Xorg of XF86? can you send me your xorg.conf or XF86Config-4 file? I
> want to see if it's a configuration option that's causing the problem.
Hmm,
OpenGL on Linux is fun ...
:-/
I use a recent update of xorg from Fedora core 4 without local modifications,
that is at the moment xorg-x11-6.8.2-37.FC4.49.2. I also use the fglrx from
the livna yum repository. They often fix some bugs in the official ati fglrx
code in their rpms. This version is currently ati-fglrx-8.18.6.1-0.lvn.1.4.
For such fixes, look into their src rpms.
Attached is my xorg.conf from that machine.
But at the current state flightgear crashes on exit somewhere in GL, but only
on the fglrx machine ...
At work, I work (at least partly) in a team doing OpenGL based 3D
visualization of fluid dynamics. Some of the most strange problem reports
originate from machines with ATI cards. All our development machines (except
some machines used for testing and reproducing that strange problems) are
equipped with NVidia cards.
I personally like the ATI cards much more since ATI ever released some specs
about their cards to the open source community, so there was some hope that
well doing drivers will appear.
But looking at those problems with ATIs closed source drivers, I must say that
NVidia seems to work better.
On the other hand, many people see massive performance hits with current
NVidia drivers in presence of OpenGL points (all our lights are such
points ...). The NVidia card at work does not show any problem with FG at
night, but that one is a extremely expensive Quadro card certified for
professional CAD use (often many points/lines).
Since the performance hit with points seemed to have begun at a specific
driver version, it comes in mind that NVidia might want people drawing lines
and points not needed for most 3D games pay much for their professional
cards?
You remember the driver limitation in the windows nvidia drivers not enabling
sli with non nvidia mainboard chipsets, even when old drivers showed
promising results with all chipsets ...
All together no 'better choice' ...
Greetings
Mathias
--
Mathias Fröhlich, email: [EMAIL PROTECTED]
# 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"
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA
extension
EndSubSection
# 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 "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
Option "XkbVariant" "nodeadkeys"
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 "NEC MultiSync LCD2080UX"
HorizSync 20.0 - 75
VertRefresh 43.0 - 72.0
# Option "dpms"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "Videocard vendor"
BoardName "ATI Radeon"
Option "MonitorLayout" "TMDS, NONE"
# Option "AGPMode" "4"
# Option "DDCMode" "on"
# BusID "PCI:3:0:0"
EndSection
Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
Option "no_accel" "no"
Option "no_dri" "no"
Option "MonitorLayout" "AUTO, NONE"
Option "NoTV" "yes"
Option "FSAAEnable" "yes"
Option "FSAAScale" "2"
Option "UseInternalAGPGART" "yes"
Option "UseFastTLS" "2"
BusID "PCI:3:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
# Device "Videocard0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1600x1200"
EndSubSection
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
