ThinkWiki - User contributions [en]

R300

2006-06-04T21:06:19Z

Bgoglin: works on T43p too

== R300 drivers with DRI support ==
In post-2.6.13 development kernels (and also 2.6.13-mm3), DRM support for the [http://r300.sourceforge.net/ R300] chips from ATI has been included. Together with a bleeding-edge version of [http://www.mesa3d.org/ Mesa] (at least 6.3.2), this will allow 3D acceleration support for systems having a chip like this without the need for the ATI binary only driver ([[Fglrx]]). The latest beta releases of [http://www.x.org/ X.Org] for 6.9/7.0 already have Mesa 6.3.2, but building the R300 DRI drivers is disabled by default.

== Kernel configuration ==
You need to build AGP support with
# CONFIG_AGP=y
# CONFIG_AGP_INTEL=y #for a ThinkPad T41p
and the Radeon DRM support with
# CONFIG_DRM=y
# CONFIG_DRM_RADEON=y
Alternatively, can also build modules instead of including the code into the kernel. The modules will then be automatically loaded when X starts up.

If everything works well, the device /dev/dri/card0 should show up.

== Mesa ==
If your distribution does not offer binary packages of the current Mesa development packages, you need to build them yourself. It might also be possible that the DRI driver is included in your X.Org packages, just look out for a file like {{path|/usr/X11R6/lib/modules/dri/r300_dri.so}}.

== X configuration ==
You will need to load the dri and GLcore extensions with
# Section "Module"
# ...
# module "dri"
# module "GLcore"
# ...
# EndSection
Note: In Xorg 7.0 you don't need to load GLCore manually anmore

My radeon configuration looks like this
# Section "Device"
# Identifier "firegl"
# Driver "radeon"
# BusID "PCI:1:0:0"
# ....
# Option "AGPFastWrite" "off" # "on" freezes my laptop
# Option "AGPMode" "4" # this value depends on your hardware, this one is for a T41p
# Option "DynamicClocks" "on"
# Option "ColorTiling" "on"
# EndSection

X will silently ignore if DRI cannot be activated for your card, so you should check yor X logfile. Just search for DRI and/or DRM. Afterwards, you might want to do the usual glxinfo/glxgears magic.

== Packages ==
*{{Debian}} Packages: http://packages.debian.org/libgl1-mesa-dri

== Performance ==
With 2.6.14-rc1 + Mesa 6.3.2, glxgears (the one and only Linux 3D benchmark) gives ~2200 FPS on my ThinkPad T41p with a FireGL Mobility T2 and a 1.7GHz Pentium M, 1GB RAM.

There is to note that the Color-depth has great effect on this value.
on my R50p with 24Bit I get about 2k fps, with 16Bit i get about 1k-1.5k fps

With 2.6.15 + Mesa 6.3.2, glxgears gives ~1480 FPS on a ThinkPad T43 with a Radeon Mobility X300 and a 1.86GHz Pentium M, 512MB RAM, when AGPMode=8, EnablePageFlip=on, AGPFastWrite=on and RenderAccel=on. Adding AccelMethod=EXA reduces to 700 FPS but makes the Composite Extension be usable.

== Troubleshooting ==
* Useful thread about two possible gotchas in Ubuntu Dapper: http://www.ubuntuforums.org/showthread.php?t=110008&page=5 (in short: mv /usr/X11R6/lib/modules/dri /usr/X11R6/lib/modules/dri.old;ln -s /usr/lib/dri /usr/X11R6/lib/modules/dri;apt-get remove --purge xorg-driver-fglrx)

== Useful links ==
* [http://r300.sourceforge.net The original R300 development page]
* [http://www.mesa3d.org Mesa 3D graphics library]
* [http://wiki.x.org/wiki/ChangesSince68 Rough changelog for X.Org 6.9]

== ThinkPads that may be supported ==
Supported chips, as found in select IBM ThinkPads (please add your own ones!):
* [[ATI Mobility FireGL T2]]
** {{R50p}}
** {{T41p}}, {{T42p}}
* [[ATI Mobility Radeon X300]]
** {{R52}}
** {{T43}}
** {{Z60m}}
* [[ATI Mobility FireGL M24 1T]]
** {{T43p}}

Additional options for the radeon driver

2006-01-15T19:33:00Z

Bgoglin: ColorTiling, EnablePageFlip, AccelMethod

Options for the radeon driver are documented on the radeon(4x) man page.

==External Monitors==
You can use '''MergedFB''' to provide dualhead '''Xinerama'''-like setups. MergedFB's pseudo-Xinerama is not Xorg server's Xinerama. You don't have to enable Xorg server's Xinerama to use MergedFB's pseudo-Xinerama. However, applications compiled with Xinerama support (Gentoo users USE="xinerama") can interpret pseudo-Xinerama hints, for example, to maximize to a single monitor instead of spanning two monitors.

The following (partial) '''Xorg''' config will make the Radeon card use '''1024x768''' on the internal lcd display and '''1280x1024''' on the external ('''Note''': only one screen/monitor section is needed (it controls the setup of the internal monitor) even though we have two displays):
'''N.B.:''' Modes used in the ''MetaModes'' also have to be present in the ''screen'' modes section.

Section "Device"
Identifier "ATI"
Driver "radeon"
'''# accelration'''
Option "AGPMode" "4"
Option "EnablePageFlip" "on"
Option "RenderAccel" "on"
'''# enable (partial) PowerPlay features'''
Option "DynamicClocks" "on"
'''# use bios hot keys on thinkpad (aka fn+f7)'''
Option "BIOSHotkeys" "on"
'''# enable radeon specific xinerama'''
Option "MergedFB" "true"
Option "CRT2Position" "RightOf"
Option "CRT2Hsync" "50-75"
Option "CRT2VRefresh" "30-82"
Option "MetaModes" "1024x768-1280x1024"
Option "MergedNonRectangular" "true"
BusID "PCI:1:0:0"
EndSection
Section "Monitor"
Identifier "InternalLCD"
Option "DPMS"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "ATI"
Monitor "InternalLCD"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1024x768"
EndSubSection
EndSection

Note: The '''CRT2''' directives always applies for the external monitore regardless of type (LCD, CRT...). The option '''MergedNonRectangular''' is needed to force the screens into two different sizes.

===External Monitors and Docking Stations/Port Replicators===
I seems that '''Xorg''' incorectly discovers the external displays when connected to a docking station/port replicator - the only solution to this problem (at least that I know of) is to start the laptop (and boot all the way into X) prior to inserting it in the dock.

It also happens that if you are attempting to use the mergedFB trick to
do dual head with out a docking station, you have to start X on the laptop
LCD first, then plug a monitor into the VGA port. If the external monitor
is already plugged in, the internal LCD will be blank.

==AGP speed==

By default, the open source radeon driver forces 1x AGP speed. Quote from the developers:

tuning to the highest speed possible has caused hangs on some boxes, with no
discernable pattern, so we default to 'slow but safe' whilst giving the option
to go fast if the user wants to try it.

Higher speeds can be enabled by adding '''Option "AGPMode" "X"''' (where X is a number) in the '''Device''' section in {{path|/etc/X11/xorg.conf}}.

Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "IBM Thinkpad"
BoardName "ATIdd Mobility FireGL 7800"
'''Option "AGPMode" "4"'''
EndSection

With this option enabled (set to 4x speed), the X11 server should print ({{path|/var/log/Xorg.0.log}}):

(**) RADEON(0): Option "AGPMode" "4"
(**) RADEON(0): Using AGP 4x mode

==AGP Fast Writes==

By default, the open source radeon driver disables AGP Fast Writes. Fast Writes can be enabled by adding '''Option "AGPFastWrite" "yes"''' in the '''Device''' section in {{path|/etc/X11/xorg.conf}}.

Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "IBM Thinkpad"
BoardName "ATI Mobility FireGL 7800"
'''Option "AGPFastWrite" "yes"'''
EndSection

==Dynamic Clock scaling==

Please see:

*[[How to make use of Graphics Chips Power Management features]] <tt>(save even more battery power)</tt>
*[https://bugs.freedesktop.org/show_bug.cgi?id=2187 Xorg bug] <tt>DynamicClocks may hang your machine</tt>

==Color Tiling==

ColorTiling is supposed to be enabled by default. But, it looks like setting it explicitely to "on" increases the FPS in glxgears.

Option "ColorTiling" "on"

==Acceleration Architecture==

By default, the XAA architecture is used. EXA is newer and supposed to have better performance. It looks like it reduces the FPS in glxgears (maybe because it disables Page Flip) but makes the Composite extension be fast.

Option "AccelMethod" "EXA"

==Page Flip==

Page Flip increases performance but is not always supported. It will be disabled if the EXA architecture is used.

Option "EnablePageFlip" "on"

== Related Links ==
*[http://www.x.org/X11R6.8.2/doc/radeon.4.html xorg 6.8.2 Radeon manual page]

R300

2006-01-15T19:16:35Z

Bgoglin: performance on T43

== R300 drivers with DRI support ==
In post-2.6.13 development kernels (and also 2.6.13-mm3), DRM support for the [http://r300.sourceforge.net/ R300] chips from ATI has been included. Together with a bleeding-edge version of [http://www.mesa3d.org/ Mesa] (at least 6.3.2), this will allow 3D acceleration support for systems having a chip like this without the need for the ATI binary only driver ([[Fglrx]]). The latest beta releases of [http://www.x.org/ X.Org] for 6.9/7.0 already have Mesa 6.3.2, but building the R300 DRI drivers is disabled by default.

== Kernel configuration ==
You need to build AGP support with
# CONFIG_AGP=y
# CONFIG_AGP_INTEL=y #for a ThinkPad T41p
and the Radeon DRM support with
# CONFIG_DRM=y
# CONFIG_DRM_RADEON=y
Alternatively, can also build modules instead of including the code into the kernel. The modules will then be automatically loaded when X starts up.

If everything works well, the device /dev/dri/card0 should show up.

== Mesa ==
If your distribution does not offer binary packages of the current Mesa development packages, you need to build them yourself. It might also be possible that the DRI driver is included in your X.Org packages, just look out for a file like {{path|/usr/X11R6/lib/modules/dri/r300_dri.so}}.

== X configuration ==
You will need to load the dri and GLcore extensions with
# Section "Module"
# ...
# module "dri"
# module "GLcore"
# ...
# EndSection

My radeon configuration looks like this
# Section "Device"
# Identifier "firegl"
# Driver "radeon"
# BusID "PCI:1:0:0"
# ....
# Option "AGPFastWrite" "off" # "on" freezes my laptop
# Option "AGPMode" "4" # this value depends on your hardware, this one is for a T41p
# Option "DynamicClocks" "on"
# Option "ColorTiling" "on"
# EndSection

X will silently ignore if DRI cannot be activated for your card, so you should check yor X logfile. Just search for DRI and/or DRM. Afterwards, you might want to do the usual glxinfo/glxgears magic.

== Packages ==
*{{Debian}} Packages: http://packages.debian.org/libgl1-mesa-dri

== Performance ==
With 2.6.14-rc1 + Mesa 6.3.2, glxgears (the one and only Linux 3D benchmark) gives ~2200 FPS on my ThinkPad T41p with a FireGL Mobility T2 and a 1.7GHz Pentium M, 1GB RAM.

There is to note that the Color-depth has great effect on this value.
on my R50p with 24Bit I get about 2k fps, with 16Bit i get about 1k-1.5k fps

With 2.6.15 + Mesa 6.3.2, glxgears gives ~1480 FPS on a ThinkPad T43 with a Radeon Mobility X300 and a 1.86GHz Pentium M, 512MB RAM, when AGPMode=8, EnablePageFlip=on, AGPFastWrite=on and RenderAccel=on. Adding AccelMethod=EXA reduces to 700 FPS but makes the Composite Extension be usable.

== Useful links ==
* [http://r300.sourceforge.net The original R300 development page]
* [http://www.mesa3d.org Mesa 3D graphics library]
* [http://wiki.x.org/wiki/ChangesSince68 Rough changelog for X.Org 6.9]

== ThinkPads that may be supported ==
Supported chips, as found in select IBM ThinkPads (please add your own ones!):
* [[ATI Mobility FireGL T2]]
** {{R50p}}
** {{T41p}}, {{T42p}}
* [[ATI Mobility Radeon X300]]
** {{R52}}
** {{T43}}
** {{Z60m}}

ATI Mobility Radeon X300

2006-01-08T22:10:45Z

Bgoglin: r300 works with xorg 6.9.0

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ATI Mobility Radeon X300 ===
This is an ATI video adapter

=== Features ===
* Chipset: ATI M22
* PCI ID: 1002:5460
* PCI Express x16
* 32 or 64MB GDDR1 on-chip video memory
* "HyperMemory": can use system memory for graphics processing
* "PowerPlay 4.0" technology for dynamic engine clock, memory clock and core voltage, refresh rate reduction and thermal status reporting.
</div>
|style="vertical-align:top" |
|}

See [http://www.ati.com/products/radeonx300/specs.html specifications] from ATI, as well as the [http://www.ati.com/products/embedded/mobilityradeonx300/M22-CSP64_Product_Snapshot.pdf "snapshot" data sheet] (referes to the 32MB on-chip, 128MB "HyperMemory" version).

=== Linux driver ===
Use Driver "radeon" in the xorg.conf file - it works at least for xorg 6.8.2, maybe older versions too. xorg 6.8.2 will only give you 2D-acceleration, though. To enable 3D acceleration as well you need to use xorg 6.9.0 or later. It uses an open source Radeon [http://r300.sf.net/ driver] with 3D acceleration support (merged into [http://dri.freedesktop.org here] recently), but it's still a little bit experimental and may not support all features.

You may also use the binary ATI driver [[fglrx]].

==== ThinkPad LCD ====
Display on the internal LCD works as long as you set the monitor settings correct.

==== External VGA port ====
There are known problems. Both the <tt>radeon</tt> and [[fglrx]] drivers turn off the switching between internal and external port.

=====With the <tt>vesa</tt> driver=====
Using the "vesa" driver built into X.org, mode switching modes. However, this loses acceleration and some capabilities.

=====With the <tt>radeon</tt> driver=====
On-the-fly swiching doesn't work. To activate both ports in clone mode with a reasonable CRT refresh rate, use the following in {{path|/etc/X11/xorg.conf}}:

Section "Device"
Identifier "Videocard0"
VendorName "Videocard vendor"
BoardName "ATI Radeon Mobility X300"

Driver "radeon"
Option "DynamicClocks" "on"

Option "MergedFB" "on"
Option "MonitorLayout" "LVDS, CRT"
Option "CRT2Hsync" "50-75"
Option "CRT2VRefresh" "50-82"
EndSection

Note that without the <tt>MonitorLayout</tt> option, if the external monitor is connected when X starts then the LCD will be deactivated and you will need to restart X.

(Tested wth Fedora Core 4 on ThinkPad {{T43}}).

See also the related discussion about [[Additional options for the radeon driver]].

=====With the [[fglrx]] driver=====
On-the-fly switching doesn't work either. To use both ports, either have the monitor connected during X startup, or force activation of both ports by adding
Option "ForceMonitors" "lvds,crt1"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}}. Powering the CRT port consumes 400-500mW, regardless of whether a CRT is attached.

==== S-Video port (TV-out) ====

Works with the proprietary [[fglrx]] driver (as of version 8.19.10). To activate, add
Option "ForceMonitors" "lvds,tv"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}} and restart X.

==== DVI port ====
??

=== 3D acceleration ===
OpenGL 3D acceleration is provided by the proprietary [[fglrx]] driver (when DRI is enabled). Note that performance is affected by the power saving mode.

=== Linux kernel Framebuffer driver ===

radeonfb might cause problems with hardware acceleration under X on some systems, vesafb and vesafb-tng on the other hand has been reported to work just fine.

=== Clock rates, voltage and power===
{| border="1" cellspacing="0" cellpadding="2"
|+ Clock rates, voltages and power {{footnote|1}}
! Mode !! core freq !! memory freq !! voltage !! idle !! 3DMarks (Windows, 1600x1200, LCD only)
|-
| Performance || 300 || 230 MHz || 1.15V || 2.98 W || 8.28 W
|-
| Balanced || 183 || 210 MHz || 1.00V || 1.71 W || 3.88 W
|-
| Battery || 120 || 105 MHz || 1.00V || 1.61 W || 2.74 W
|}

{| border="1" cellspacing="0" cellpadding="2"
|+ ATI drivers for Windows {{footnote|2}} and [[fglrx]]
! Mode !! core freq !! memory freq
|-
| Performance || 297.00 || 229.50
|-
| Balanced || 209.25 || 182.25
|-
| Battery || 104.63 || 121.50
|}

Experimentally, the difference between the Performance and Battery settings under Linux with the <tt>radeon</tt> driver and <tt>DynamicClocks</tt> enabled is roughly 0.3W and 3-4 degrees in GPU temperature on a ThinkPad {{T43}}. Further frequency reduction leads to display flickering or corruption.

See [[How to make use of Graphics Chips Power Management features]] for details on how to control this using [[Rovclock]], [[How to make use of Graphics Chips Power Management features|<tt>DynamicClocks</tt> option to the <tt>radeon</tt> driver]] and or the [[fglrx]] driver.

Presently the lowest idle-mode power consumption is achieved using the proprietary [[fglrx]] driver and
# aticonfig --set-powerstate=1 --effective=now

=== ThinkPads this chip may be found in ===
* {{R52}}
* {{T43}}
* {{Z60m}}

{{footnotes|
#according to the [http://www.ati.com/products/embedded/mobilityradeonx300/M22-CSP64_Product_Snapshot.pdf "Snapshot" data sheet] (which refers to the 32MB on-chip, 128MB "HyperMemory" version)
#inspected using [http://www.pbus-167.com/chc.htm Notebook Hardware Control]
}}

[[Category:Components]]

R300

2006-01-07T21:06:14Z

Bgoglin: works on T43 too

== R300 drivers with DRI support ==
In post-2.6.13 development kernels (and also 2.6.13-mm3), DRM support for the [http://r300.sourceforge.net/ R300] chips from ATI has been included. Together with a bleeding-edge version of [http://www.mesa3d.org/ Mesa] (at least 6.3.2), this will allow 3D acceleration support for systems having a chip like this without the need for the ATI binary only driver ([[Fglrx]]). The latest beta releases of [http://www.x.org/ X.Org] for 6.9/7.0 already have Mesa 6.3.2, but building the R300 DRI drivers is disabled by default.

== Kernel configuration ==
You need to build AGP support with
# CONFIG_AGP=y
# CONFIG_AGP_INTEL=y #for a ThinkPad T41p
and the Radeon DRM support with
# CONFIG_DRM=y
# CONFIG_DRM_RADEON=y
Alternatively, can also build modules instead of including the code into the kernel. The modules will then be automatically loaded when X starts up.

If everything works well, the device /dev/dri/card0 should show up.

== Mesa ==
If your distribution does not offer binary packages of the current Mesa development packages, you need to build them yourself. It might also be possible that the DRI driver is included in your X.Org packages, just look out for a file like /usr/X11R6/lib/modules/dri/r300_dri.so.

== X configuration ==
You will need to load the dri and GLcore extensions with
# Section "Module"
# ...
# module "dri"
# module "GLcore"
# ...
# EndSection

My radeon configuration looks like this
# Section "Device"
# Identifier "firegl"
# Driver "radeon"
# BusID "PCI:1:0:0"
# ....
# Option "AGPFastWrite" "off" # "on" freezes my laptop
# Option "AGPMode" "4" # this value depends on your hardware, this one is for a T41p
# Option "DynamicClocks" "on"
# Option "ColorTiling" "on"
# EndSection

X will silently ignore if DRI cannot be activated for your card, so you should check yor X logfile. Just search for DRI and/or DRM. Afterwards, you might want to do the usual glxinfo/glxgears magic.

== Packages ==
*{{Debian}} Packages: http://packages.debian.org/libgl1-mesa-dri

== Performance ==
With 2.6.14-rc1 + Mesa 6.3.2, glxgears (the one and only Linux 3D benchmark) gives ~2200 FPS on my ThinkPad T41p with a FireGL Mobility T2 and a 1.7GHz Pentium M, 1GB RAM.

There is to note that the Color-depth has great effect on this value.
on my R50p with 24Bit I get about 2k fps, with 16Bit i get about 1k-1.5k fps

== Useful links ==
* [http://r300.sourceforge.net The original R300 development page]
* [http://www.mesa3d.org Mesa 3D graphics library]
* [http://wiki.x.org/wiki/ChangesSince68 Rough changelog for X.Org 6.9]

== ThinkPads that may be supported ==
Supported chips, as found in select IBM ThinkPads (please add your own ones!):
* [[ATI Mobility FireGL T2]]
** {{T41p}}, {{T42p}}, {{R50p}}
* [[ATI Technologies Inc M22 (Radeon Mobility M300)]]
** {{T43}}