ATI radeon Sticky (part 2)

opqdan · Posted: Wed Jan 19, 2005 2:10 pm Post subject:

Thanks to everyone wh has been posting on this tipic. ATI's drivers were one of the last things that kept me dual booting with windows. Now I could switch completely. I've gotten the drivers to work (I get a glxgears fps of 3500) but I was wondering whether there was a control center app for the drivers like there is with the windows ones.

Also, how would I go about enabling Overdrive? I know it doesn't add much, but I have no reason not to turn it on.

Erlend · Guru Joined: 26 Dec 2004 Posts: 493

emerge ati-drivers-extra

Wedge_ · Posted: Wed Jan 19, 2005 2:31 pm Post subject:

The ATI "control panel" in Linux is more of an "information panel" than anything else, it's nothing like what you get in Windows. Last time I checked, all you can change is your gamma / colour correction settings. I doubt you'll be able to get Overdrive working either.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ

Texas · n00b Joined: 24 Aug 2004 Posts: 7 Location: Sweden

Zanfib · Posted: Wed Jan 19, 2005 4:34 pm Post subject: thanks

Thanks corhonio, that's the good option, disable dllloader in the use flags and rebuid xorg !!

My 3d acceleration come back !!! I'm happy

Maybe add this topic in the RADEON-FAQ ?

Zanfib

Wedge_ · Posted: Wed Jan 19, 2005 4:47 pm Post subject: Re: thanks

Mythos · l33t Joined: 02 May 2004 Posts: 953 Location: Portugal

Enemy-Territory doen't work

ben0it · n00b Joined: 14 Jan 2003 Posts: 6 Location: France

Thanks for the "-dlloader" hint: I've rebuilt xorg-x11 and that did the trick, the latest ati-drivers now load correctly

Next and last issue with these ati drivers is getting the OpenGL HW libs from ATI used, because despite the "opengl-update ati" command, glxinfo still says I'm using the software rendering libs:

glxinfo:

Shaman · Posted: Thu Jan 20, 2005 2:22 am Post subject:

I'm having an issue that the FAQ doesn't address. DDC/EDID doesn't pick up a monitor on either channel. Under Windows it does, just fine. In the log, it shows NONE for Primary and Secondary head.

I have a Viewsonic P225fb (whatever that means, there are like 10 different monitors using that product code) and usually it's been fine. With the VESA and Radeon drivers, it works just fine.

I tried turning off EDID, DDC and MonitorLayout. In combinations and all off. Tried doing all that and setting the resolution to 640x480 for safety. VESA works like a charm... the kernel Radeon driver works great for 2D but of course, no 3D acceleration.

The logs look fine to my eye. There are no indications that anything (including DRI, DRM, AGP, MTRR) have failed and it indicates that the screen was opened. PCI device is correct, verified. There are lots of positive reinforcements... but no image on screen.

No good! All I get is a blank screen which the monitor appears to have issues with... the menu won't come up for the monitor itself (press a button on the monitor... works fine in any other sync screen.) The monitor light starts flashing after a few seconds.

Card: Powercolour X800 XT Platinum Edition
Monitor: Viewsonic P225fb (HSync 30-127, VSync 50-160)
System: AMD-64 4000+
Software: Xorg 6.8.912 , gcc 3.4.3 , emerge ati-drivers , fglrxconfig

Three hours I've wrestled with this thing with no luck. Any pointers? Wild-ass guesses? Give-it-ups? At this point I just can't find anything wrong with my setup.

hernejj · n00b Joined: 02 Apr 2003 Posts: 14

I'm trying to use the new ATi drivers and I keep getting the following:
What am I doing wrong????

Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol XAAGetPixmapIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol XAAGetPixmapIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol XAAGetScreenIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol XAAGetScreenIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol XAAGetScreenIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol XAAGetScreenIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol XAAGetScreenIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol noCompositeExtension from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol noCompositeExtension from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!

*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.

Fatal server error:
Caught signal 11. Server aborting

Here is my xorg.conf
---------------------------------
#**********************************************************************
# This is a sample configuration file only, intended to illustrate
# what a config file might look like. Refer to the XF86Config(4/5)
# man page for details about the format of this file. This man page
# is installed as /usr/share/man/man5/xorg.conf.5x
# **********************************************************************

Section "Files"

# 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.

RgbPath "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)

# For XFS, uncomment this and comment the others
# FontPath "unix/:-1"
FontPath "/usr/X11R6/lib/X11/fonts/local/"
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/TTF/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"

# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.

# ModulePath "/usr/X11R6/lib/modules"

EndSection

# **********************************************************************
# 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

# **********************************************************************
# Module section -- this is an optional section which is used to specify
# which run-time loadable modules to load when the X server starts up.
# **********************************************************************

Section "Module"

# This loads the DBE extension module.

Load "dbe"

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.

SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection

# This loads the Type1 and FreeType font modules

Load "type1"
Load "freetype"
Load "glx"
Load "dri"
EndSection

# **********************************************************************
# Server flags section. This contains various server-wide Options.
# **********************************************************************

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><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option "DontVTSwitch"

# 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 "DontZoom"

# 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"

# Set the basic blanking screen saver timeout.

Option "blank time" "10" # 10 minutes

# Set the DPMS timeouts. These are set here because they are global
# rather than screen-specific. These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.

Option "standby time" "20"
Option "suspend time" "30"
Option "off time" "60"

# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.

# Option "EstimateSizesAggresively" "0"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

Identifier "Keyboard1"
Driver "keyboard"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris), comment
# out the above line, and uncomment the following line.

# Option "Protocol" "Xqueue"

# Set the keyboard auto repeat parameters. Not all platforms implement
# this.

Option "AutoRepeat" "240 35"

# Specifiy 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 European
# keyboard, you will probably want to use one of:
#
# Option "XkbModel" "pc102"
# Option "XkbModel" "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
# Option "XkbModel" "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
# Option "XkbModel" "pc104"
#
# 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"

# These are the default XKB settings for xorg
#

# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

EndSection

# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "imps/2"
# Option "Device" "/dev/mouse"
Option "Device" "/dev/input/mouse0"
Option "ZAxisMapping" "4 5"
EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

Section "Monitor"
Identifier "Generic Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

# HorizSync 31.5 # typical for a single frequency fixed-sync monitor
HorizSync 68-93.8 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

# VertRefresh 60 # typical for a single frequency fixed-sync monitor

VertRefresh 70-85 # multisync
# VertRefresh 60, 65 # multiple fixed sync frequencies
# VertRefresh 40-50, 80-100 # multiple ranges of sync frequencies

# Modes can be specified in two formats. A compact one-line format, or
# a multi-line format.

# A generic VGA 640x480 mode (hsync = 31.5kHz, refresh = 60Hz)
# These two are equivalent

# ModeLine "640x480" 25.175 640 664 760 800 480 491 493 525

# Mode "640x480"
# DotClock 25.175
# HTimings 640 664 760 800
# VTimings 480 491 493 525
# EndMode

# These two are equivalent

# ModeLine "1024x768i" 45 1024 1048 1208 1264 768 776 784 817 Interlace

# Mode "1024x768i"
# DotClock 45
# HTimings 1024 1048 1208 1264
# VTimings 768 776 784 817
# Flags "Interlace"
# EndMode

# If a monitor has DPMS support, that can be indicated here. This will
# enable DPMS when the monitor is used with drivers that support it.

# Option "dpms"

# If a monitor requires that the sync signals be superimposed on the
# green signal, the following option will enable this when used with
# drivers that support it. Only a relatively small range of hardware
# (and drivers) actually support this.

# Option "sync on green"

EndSection

# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

Section "Device"
Identifier "Generic VGA"
#Driver "radeon"
Driver "fglrx"
# Chipset "generic"
# VideoRam 256
# Option "hw cursor" "off"

# ### 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

# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "off"

# === Center Mode (Laptops only) ===
Option "CenterMode" "off"

# === Pseudo Color Visuals (8-bit visuals) ===
Option "PseudoColorVisuals" "off"

# === QBS Management ===
Option "Stereo" "off"
Option "StereoSyncEnable" "1"

# === 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" "0x00000000"
Option "GammaCorrectionII" "0x00000000"

# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00000000"

# === Video Overlay for the Xv extension ===
Option "VideoOverlay" "on"

# === FSAA Management ===
Option "FSAAEnable" "no"
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" # was 0, 2 for GL
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "yes" # was yes, no for GL
Option "ForceGenericCPU" "no"
Option "KernelModuleParm" "agplock=0" # AGP locked user pages: di$
BusID "PCI:2:0:0" # vendor=1002, device=4e48
Screen 0

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"

# The Identifier, Device and Monitor lines must be present

Identifier "Screen1"
Device "Generic VGA"
Monitor "Generic Monitor"

# The favoured Depth and/or Bpp may be specified here

DefaultDepth 24

SubSection "Display"
Depth 24
Modes "1280x1024"
EndSubSection

SubSection "Display"
Depth 8
Modes "800x600"
EndSubSection

EndSection

Section "ServerLayout"
Identifier "simple layout"
Screen "Screen1"
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection

hernejj · n00b Joined: 02 Apr 2003 Posts: 14

UPDATE:

I know that I'm not suposed to compile Xorg with "static", "dlloader", and "hardened". I did not Smile Here are my use flags. Do I need to specifically set -dlloader ???

USE="alsa oss 3dnow X aim avi cdr crypt cups divx4linux dvd dvdr encode esd ethereal evo exif flac ftp gif gnome gtk2 gtkhtml
imlib java joystick jpeg mcal mikod mmx mozilla mpeg ncurses offensive oggvorbis opengl pam pcmcia pdflib png pnp quicktime readline samba sockets
spell sse ssl svg svga tiff truetype usb videos xine xmms xv xvid"

hernejj · n00b Joined: 02 Apr 2003 Posts: 14

Ok, so I recompiled xorg-x11 with the following added to my USE flags.:

-dlloader -static -hardened

It seems as though atleast ONE of these needs to be explicitly disabled with the'-' in order for the new radeon driver to work.

This took can of the unresolves symbols error:

dustfinger · Guru Joined: 15 Aug 2004 Posts: 449

Under Device Drivers > Graphics support:
Is it advisable for an ati radeon M9 user to Enable Tile Blitting Support?

I have 2.6.10-gentoo-r4

dustfinger.
_________________
Unanswered Post Initiative:
https://forums.gentoo.org/viewtopic.php?t=119906

Wedge_ · Posted: Thu Jan 20, 2005 3:39 pm Post subject:

dustfinger · Guru Joined: 15 Aug 2004 Posts: 449

Wedge_

I had enabled the Tile Blitting Support the moment the option was implemented. I just dissabled it and I found that by dissabling it I was given another option called
[*] Support for the framebuffer splash (NEW)
By enabling that I now solved my problem where the gensplash emergence theme was not being displayed while my system boots.

I am still having the problem where my system fails to load into the fvwm windows manager. I am forced to log in at the consil and type startx to load fvwm2. I noticed that there is some text that is written to the screen when I do this. Where would that output be logged? Also are there any other logs that I may want to look at? So far I have only been looking through dmesg.

dustfinger.
_________________
Unanswered Post Initiative:
https://forums.gentoo.org/viewtopic.php?t=119906

Wedge_ · Posted: Thu Jan 20, 2005 5:11 pm Post subject:

dustfinger · Guru Joined: 15 Aug 2004 Posts: 449

Thanks again Wedge_

Here are some noteable snippets that I pulled from my Xorg.0.log

Wedge_ · Posted: Thu Jan 20, 2005 5:28 pm Post subject:

The APM warning is normal and can be ignored. The drmOpenDevice/Busid messages seem to be new with the 8.8.25 driver but don't seem to cause problems. As I said, it sounds like you have the driver and X setup properly, but there's something wrong with the way you're launching fvwm. How have you got that setup?
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ

fuSEboX · n00b Joined: 20 Jan 2005 Posts: 59

Hi.
I'm new to gentoo and new to this forum...but I think that this is the right place to post my problem.... I'll do it quickly and simple:

When I tried to install ati drivers, I run into problems.
On 'setup' everything went smooth... I did 'fglrxconfig' and renamed new cfg to 'xorg.cfg'... I tried to start X and I got message like 'can't load or find module fglrx'...
Then I decided to try using command 'modprobe fglrx' and surprise surprise... the output for that was:

Sith_Happens · Posted: Thu Jan 20, 2005 7:35 pm Post subject:

I'm having some trouble with XFCE's compositors and the new ATI drivers. I'll put a link to the post here in case somebody has the same problem or some information.

https://forums.gentoo.org/viewtopic.php?p=1994197#1994197
_________________
"That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall

Wedge_ · Posted: Thu Jan 20, 2005 8:14 pm Post subject:

blistovrev

Arg, I have a satellite a75, P4, 512 Mb, ati mobility radeon 9100 IGP. I tried the old ati-drivers-3.whatever, got everything installed, load Xorg-6.8.0-any, everything works fine, untill i run a GL app. Just now installed the new 8.8.25 drivers, all reinstalled, X again, starts just fine, and once again, any GL apps lock the system entirely. Everything dies. I can't even get the problem logged, as even that locks.
I run say, glxgears, the glxgears window pops up, and is black, thats all there is.
The install went fine, no errors, switched to ati gl extentions, i'm using the kernel agp drivers, as the internals don't recognize my pci-agp bus. glxinfo reports everything a-ok, what am i missing?
If anyone has had a simalar problem, and found a solution, i can post all relevent logs.
Sweet JESUS someone help me!!
_________________
Blah

Wedge_ · Posted: Thu Jan 20, 2005 11:38 pm Post subject:

Have you had this system working with the ati-drivers before? Can you post your Xorg log?
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ