Martins schreef:
> hi,
>
> did a lot of googling, read a lot of howtos, but still strugling to get
> ATI work perfect. could someone send me working conf files for xorg and
> kernel and /etc/modules.autoload.d/kernel-2.6 to row by row check
>
> thanx in advance
>
> Martins
>
> my pci:
> # lspci
> 0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge
> [K8T800/K8T890 South]
> 0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP
> [Radeon 9600]
> 0000:01:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon
> 9600] (Secondary)
>
> # glxinfo | grep -i "direct rendering"
> direct rendering: No
>
> # fglrxinfo
> display: :0.0 screen: 0
> OpenGL vendor string: Mesa project: www.mesa3d.org
> OpenGL renderer string: Mesa GLX Indirect
> OpenGL version string: 1.2 (1.5 Mesa 6.2.1)
>
I have the ATI drivers working on my AIW 9800SE and Direct Rendering
works too:
glxinfo | grep -i "direct rendering"
direct rendering: Yes
So here's the settings you need to get it working for you as well:
The most important setting is in the kernel:
**You must have DRM OFF in the kernel**
You may also need to have agpgart for your motherboard ON.
OK, the actual settings:
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=m
CONFIG_AGP_INTEL_MCH=m
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
CONFIG_AGP_VIA=m
# CONFIG_AGP_EFFICEON is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
CONFIG_HPET_MMAP=y
CONFIG_HANGCHECK_TIMER=y
Because I need kernel support for my motherboard's AGP bus, I cannot use
the driver's internal agpgart.
So here's the relevant settings of my xorg.conf (I don't use composite,
I didn't even install it, as the fglrx drivers don't work with it, even
if it worked, which as I understand it, it doesn't, very well):
# **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access t#
**********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
# Group 100 # users
# Mode 0660
EndSection
# === ATI device section ===
Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
# ### generic DRI settings ###
# === disable PnP Monitor ===
#Option "NoDDC"
# === disable/enable XAA/DRI ===
Option "no_accel" "no"
Option "no_dri" "no"
# === misc DRI settings ===
Option "mtrr" "off" # disable DRI mtrr mapper,
driver has its own code for mtrr
# ### FireGL DDX driver module specific settings ###
# === Screen Management ===
Option "DesktopSetup" "0x00000000"
Option "MonitorLayout" "AUTO, AUTO"
Option "IgnoreEDID" "off"
Option "HSync2" "unspecified"
Option "VRefresh2" "unspecified"
Option "ScreenOverlap" "0"
# === TV-out Management ===
Option "NoTV" "yes"
Option "TVStandard" "NTSC-M"
Option "TVHSizeAdj" "0"
Option "TVVSizeAdj" "0"
Option "TVHPosAdj" "0"
Option "TVVPosAdj" "0"
Option "TVHStartAdj" "0"
Option "TVColorAdj" "0"
Option "GammaCorrectionI" "0x06419064"
Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00008000"
# === Video Overlay for the Xv extension ===
Option "VideoOverlay" "on"
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "on"
# === Center Mode (Laptops only) ===
Option "CenterMode" "off"
# === Pseudo Color Visuals (8-bit visuals) ===
Option "PseudoColorVisuals" "on"
# === QBS Management ===
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
# === FSAA Management ===
Option "FSAAEnable" "yes"
Option "FSAAScale" "1"
Option "FSAADisableGamma" "no"
Option "FSAACustomizeMSPos" "no"
Option "FSAAMSPosX0" "0.000000"
Option "FSAAMSPosY0" "0.000000"
Option "FSAAMSPosX1" "0.000000"
Option "FSAAMSPosY1" "0.000000"
Option "FSAAMSPosX2" "0.000000"
Option "FSAAMSPosY2" "0.000000"
Option "FSAAMSPosX3" "0.000000"
Option "FSAAMSPosY3" "0.000000"
Option "FSAAMSPosX4" "0.000000"
Option "FSAAMSPosY4" "0.000000"
Option "FSAAMSPosX5" "0.000000"
Option "FSAAMSPosY5" "0.000000"
# === Misc Options ===
Option "UseFastTLS" "2"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "no"
Option "ForceGenericCPU" "no"
# Option "KernelModuleParm" "agplock=0"
BusID "PCI:1:0:0" # vendor=1002, device=4148
Screen 0
EndSection
The "KernelModuleParm" option is commented out because that was an
official workaround to prevent the memory leak lockup in NWN, which is
supposed to be fixed in these drivers (8.14.13). But I haven't played
NWN to test it yet. This config was generated by fglrxconfig (because I
don't know all the options) some time ago (8.10.whatever, I think), and
I've been using it since then.
The fglrx drivers seem to like being loaded in
modules.autoload.d/kernel-2.6, so you might consider listing them there.
As for your compile errors... what version of the ati-driver are you
installing? I must say, the 8.14.13 are the first ones that compiled
cleanly without any errors of the kind you describe.
That said, the drivers can often work despite the compile errors, it
really depends very specifically on just what conflicts were
experienced. I've had compiles that were
error
error
error
**DRI did not compile**
in which case the drivers did not work
and also
error
error
error
**driver compiled with DRI support**
in which case the driver did work.
*That* said, errors compiling drivers against the kernel usually
indicate (in my experience) a kernel configuration issue.
# Option "KernelModuleParm" "agplock=0"
It may well be that you have some settings incorrectly set (like DRM
being compiled in the kernel), or that you're using a kernel that the
drivers are not completely compatible with (like 2.6.12).
If one of those is the issue, then at least you know what it is. But
even if the drivers compile with errors after you've fixed the problem
(if it's fixable; you may not want to downgrade your kernel, after all),
they may still work.
Oh, and it's a good idea to not only restart the X server, but really
reboot to load the fglrx drivers if fglrxinfo shows you as using MESA.
Simply restarting the X server never worked for me to unload MESA and
reload fglrx. But then again, under 8.14.13 I haven't had the problem of
Wine or Cedega crashing *and* knocking the fglrx drivers out of the
park.... certainly I've had Wine or Cedega games crash, but unlike past
days, when I kill them and run fglrxinfo, fglrx is still running, and
not all of a sudden MESA. So it's also a good idea to use the most
current drivers; they are actually noticeably improved (not "good", or
even necessarily "better", but literally "noticeably improved").
Hope this helps,
Holly
--
[email protected] mailing list
