2010-07-16

Slitaz -- glx / ati

X600/M24

X700 / X1300 / X1400 / X1600

root@slitaz:~# glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: Mesa DRI R300 20060815 x86/MMX/SSE2 TCL

root@slitaz:~# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
8811 frames in 5.0 seconds = 1762.070 FPS
9123 frames in 5.0 seconds = 1824.461 FPS
9058 frames in 5.0 seconds = 1811.539 FPS
9169 frames in 5.0 seconds = 1833.587 FPS
root@slitaz:~#

Summary - System information
-Computer-
Processor : Intel(R) Pentium(R) M processor 1.73GHz
Memory : 2074MB (60MB used)
Operating System : Slitaz GNU/Linux 3.0
User Name : root (Root Administrator)
Date/Time : Fri 16 Jul 2010 09:05:44 PM UTC
-Display-
Resolution : 1280x768 pixels
OpenGL Renderer : Mesa DRI R300 20060815 x86/MMX/SSE2 TCL
X11 Vendor : (null)
-Multimedia-
Audio Adapter : HDA-Intel - HDA Intel
-Input Devices-
PC Speaker
BTC USB Multimedia Cordless Keyboard
SynPS/2 Synaptics TouchPad
BTC USB Multimedia Cordless Keyboard
AT Translated Set 2 keyboard
-Printers-
CUPS libraries cannot be found
-IDE Disks-
-SCSI Disks-
ATA IC25N060ATMR04-0
TSSTcorp CD/DVDW TS-L532A

root@slitaz:~# lsmod | head -7
Module Size Used by Not tainted
lib80211_crypt_wep 3172 1
radeon 341348 2
drm 121736 3 radeon
i2c_core 17468 1 drm
intel_agp 23032 0
agpgart 25980 2 drm,intel_agp

root@slitaz:~#


* ASUS W3V ATI X600/M24

----
20110227

Extract from

KernelModeSetting (KMS)

https://wiki.ubuntu.com/X/KernelModeSetting

[..]

KMS with a Radeon card

Note that radeon KMS is work in progress, so installing the newest possible kernel is recommended. If you use Karmic, you may want to install the Lucid kernel.

Add radeon.modeset=1 to your BootOptions to enable KMS (and DRI2) with the ati/radeon driver.

For Grub2 on Ubuntu 9.10 and later:

* sudo nano /etc/default/grub.
* Add radeon.modeset=1 to the end of the line GRUB_CMDLINE_LINUX_DEFAULT=.
* Then sudo update-grub

You can also try out KMS without rebooting, by logging out, switching to a virtual console, then

sudo stop gdm
sudo modprobe -r radeon drm
sudo modprobe radeon modeset=1
sudo start gdm

With the module loading issues (see below), this method is actually safer.

If needed, also remove the splash option from your boot options since usplash can cause some issues.

Module loading issues on ATI

If you get "RADEONDRIGetVersion failed" in Xorg.0.log it is because of a race issue. The radeon module is not initialized in time before X is starting, and X will falsely believe that there is no KMS support and do its own modesetting...

To make sure the radeon modules is initialized before gdm (and X) is starting, insert "modprobe radeon" into your /etc/init/gdm.conf just before the gdm-binary is executed:

...
initctl emit starting-dm DM=gdm

modprobe radeon
exec gdm-binary $CONFIG_FILE
end script

Missing firmware issue on ATI

If your /var/log/syslog has the line Cannot find firmware file 'radeon/R600_rlc.bin' you should download it.

sudo wget -O /var/lib/firmware/`uname -r`/radeon/R600_rlc.bin http://people.freedesktop.org/~agd5f/radeon_ucode/R600_rlc.bin

ATI KMS Results

Some benchmarking KMS/DRI2 versus non-KMS/DRI


Does DRI2 suck? No! According to the developers, DRI2 makes simple operations less efficient, like these "benchmarks" below. On the other hand, more complex operations (which will be used in a 3D-intensive application like games) should be more efficient with DRI2.

[..]