kultex: excellent work!!

Edit: I have added some parts.

you should add the intel_agp and agpgart in rcS.conf or you'd need to modprobe every boot.

Great idea! and much needed.

On my setup based on the justx flavor with an intel card the module mesa-dri-intel doesn't exist, even with the package of that name installed.

Modules drm and i810 are loaded, however Xorg looks for the device in /dev/dri/card0 etc. A glance at the log file will show that up. But /dev/dri is not a directory, but a device file!

Other issue, with a VertRefresh 30.0 - 120.0, I could not coerce X into giving me a resolution other than 1280x1024. Putting VertRefresh 75 gives me 1152x864 which is a bit more readable. In the log file there is a line which says Virtual size is 1152x864... It seems to estimate a reasonable virtual size according to what the monitor reports as its physical size, and then it uses a mode that corresponds to that and xrandr will not let me change it. e.g. the command [xrandr --fb 1024x768] responds with "specified screen not large enough for default output (1152x864+0+0)"

Strange! any ideas?
jpeg

@jpeg
Have you ever used puppy linux? I use the same xorg.conf from it in SliTaz. It saved me the time to edit it. That is just an idea if you have it handy.


Rupp

thx jozee - and as I said - it was very quick and dirty, because I did not test all commands - my intel atom board is still running with xorg-xf86-video-vesa and 1600×1200. When I tested the intel driver, there was a bug, but I hope I can do it tonight ....

my atom board is not working - I still get the same error

the Xorg.0.log

drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice:open result is -1, (Not a directory)
drmOpenDevice:Open failed
......continues with the same output with different card-numbers - card1, card2....
(EE) [drm] drmOpenfailed
(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI
(WW) intel(0): drmDropmaster failed: Unknown error 4294967295

here is my lsmod, perhaps somebody find something

tux@slitaz:~$ lsmod
Module                  Size  Used by    Not tainted
i915                  143208  0 
drm                   121736  1 i915
i2c_algo_bit            4724  1 i915
video                  17828  1 i915
backlight               3584  1 video
output                  2260  1 video
i2c_core               17468  3 i915,drm,i2c_algo_bit
intel_agp              23032  1 
agpgart                25980  3 drm,intel_agp
snd_intel8x0           26724  1 
snd_ac97_codec         88736  1 snd_intel8x0
ac97_bus                1308  1 snd_ac97_codec
snd_pcm                51780  2 snd_intel8x0,snd_ac97_codec
snd_timer              16344  1 snd_pcm
snd                    43584  6 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore               5180  1 snd
snd_page_alloc          7256  2 snd_intel8x0,snd_pcm
tux@slitaz:~$ 

@kultex
I've seen the dri open failure on mine as well, but Xorg works. I noticed that /dev/dri is not a directory, that might have something to do with it.

Finally I decided to hop by www.x.org and do a bit of reading. Three very interesting pages...
* http://www.x.org/wiki/FAQVideoModes - on video modes
* http://wiki.debian.org/XStrikeForce/HowToRandR12 - on how to use xrandr, though section [III.5. Forcing a preferred mode] is particularly interesting. I have yet to try it.
* http://www.thinkwiki.org/wiki/Xorg_RandR_1.2

I noticed that /dev/dri is not a directory, that might have something to do with it.

Yes, this exactly is the problem. Try deleting this device file and manually create "mkdir /dev/dri"

with mkdir /dev/dri there is a problem, because I have to delete the file /dev/dri before. But then strange things happen (I just can open xterm, nothing else).

There is something strange now in tazx compared to the old cooking - there is no more /root/xorg.conf.new - its still in xterm-output:
Your xorg.conf is /root/xorg.conf.new
To test the server, run 'X -ocnfig /root/xorg.conf.new' , but there is no file.

Its also written:
patching file /etc/X11/.xorg.conf, but it is the normal slitaz xorg.conf

evrything seems to be ok no - I just have to disable the LVDS Monitor, because this limits the output to 800x600 - I have to find my old xorg.conf - I try this in the night...

first I have to say, that tazx works no like a charme - all depencies are set!! even my svhs-out is working!!!

the only thing that remains is this drm/dri error perhaps as a hint from the dri-wiki: http://dri.freedesktop.org/wiki/DriTroubleshooting

Next, make sure that X works with the DRM correctly. 
Look at the bottom of the X log where it has lines with [dri], [drm], [agp], etc. If there are any (EE) errors in there, look at those.
If you get a message like this:
(EE) [dri] RADEONDRIScreenInit failed because of a version mismatch
(EE) [dri] libdri version is 4.2.0 but version 5.0.0 is needed.
(EE) [dri] Disabling DRI.
then your libdri module is too old. If you installed from a snapshot, be sure to update the common module. 
If the version numbers are the other way around (version is 5.0 but version 4.2 is needed) then you updated your server without updating your 2D driver as well.

but it is no mismatch - for (WW) intel(0): drmDropmaster failed: Unknown error 4294967295 I find nothing relevant

here is my xorg.conf (for Asus EEE-box / Kino Atom), if somebody is interested - some of the options are not working because dri is disabled - and I dont know, what all options are doing, because I adopted one I found on the net, from whom I thought he is competent.

Section "ServerLayout"
	Identifier     "X.org Configured"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
	ModulePath   "/usr/lib/X11/modules"
	FontPath     "/usr/share/fonts/X11/misc/"
	FontPath     "/usr/share/fonts/X11/TTF/"
	FontPath     "/usr/share/fonts/X11/OTF"
	FontPath     "/usr/share/fonts/X11/Type1/"
	FontPath     "/usr/share/fonts/X11/100dpi/"
	FontPath     "/usr/share/fonts/X11/75dpi/"
	FontPath     "/usr/share/fonts/truetype/ttf-dejavu"
EndSection

Section "Module"
	Load  "dri"
	Load  "extmod"
	Load  "dbe"
	Load  "glx"
	Load  "freetype"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option      "XkbLayout" "de"
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "auto"
	Option	    "Device" "/dev/input/mice"
	Option	    "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
	Identifier   "Monitor0"
        Vendorname      "Hewlett-Packard"
        Modelname       "HP LP2065 Flat Panel Monitor"
        Horizsync       30.0-92.0
        Vertrefresh     48.0-85.0
        Modeline "1600x1200" 159.50 1280 1376 1512 1744 1024 1027 1034 1078
        Option "DPMS"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: : integer, : float, : "True"/"False",
        ### : "String", : " Hz/kHz/MHz"
        ### [arg]: arg optional
        #Option     "NoAccel"            	# []
        #Option     "SWcursor"           	# []
        #Option     "ColorKey"           	# 
        #Option     "CacheLines"         	# 
        #Option     "Dac6Bit"            	# []
        #Option     "DRI"                	# []
        #Option     "NoDDC"              	# []
        #Option     "ShowCache"          	# []
        #Option     "XvMCSurfaces"       	# 
        #Option     "PageFlip"           	# []
	Identifier  "Card0"
	Driver      "intel"
	VendorName  "Unknown Vendor"
	BoardName   "Unknown Board"
	Option		"LinearAlloc"		"16384"
	#BusID		"PCI:0:2:0"
#	Option		"NoDDC"				"true"
	Option "XvmcUsesTextures" "true"
	Option "renderAccel" "true"
	Option "NoDDCValue"
	Option "UseEDID" "false"
	Option "ExactModeTimingsDVI" "true"
	Option "NoLogo" "true"
	Option "NoBandWidthTest" "true"
	Option "ModeValidation" "NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes"
	Option "DynamicTwinView" "false"
	Option "UseEvents" "true"
	Option "AllowGLXWithComposite" "true"
	Option "AddARGBGLXVisuals" "true"
	Option "Monitor-LVDS" "Disabled Monitor"
	Option "Monitor-TMDS-1" "Monitor0"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"
	DefaultDepth     24
SubSection "Display"
                Viewport   0 0
                Modes "1600x1200"
        EndSubSection	
	Option "XvmcUsesTextures" "true"
	Option "renderAccel" "true"
	Option "NoDDCValue"
	Option "UseEDID" "false"
	Option "ExactModeTimingsDVI" "true"
	Option "NoLogo" "true"
	Option "NoBandWidthTest" "true"
	Option "ModeValidation" "NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes"
	Option "DynamicTwinView" "false"
	Option "UseEvents" "true"
	Option "AllowGLXWithComposite" "true"
	Option "AddARGBGLXVisuals" "true"
	Option	"TVStandard"	"720p"
EndSection

Section "ServerFlags"
	Option	"AllowMouseOpenFail"	"true"
#	Option	"BlankTime"		"0"
#	Option	"StandbyTime"	"0"
#	Option	"SuspendTime"	"0"
#	Option	"OffTime"		"0"
	Option	"AIGLX"			"Off"
EndSection
Section "Monitor"
	Identifier	"Disabled Monitor"
	Option		"Enable" "false"
	Option		"Ignore" "true"
EndSection
Section "Extensions"
	Option "Composite" "false"
	Option "RENDER" "true"
EndSection 

thanks to KdE_ from the german forum it is solved: the problem was to add tux to the group video

rm /dev/dri
mkdir /dev/dri/
addgroup tux video
modprobe drm

is it please possible to update the xorg-xf86-video-ati-6.9.0 (which was released on 2008-06-26) to xorg-xf86-video-ati-6.13.0 http://cgit.freedesktop.org/xorg/driver/xf86-video-ati

And for the ATI Radeon Mobility M6 LY the ati driver wants to load the Module: "theatre_detect"

(II) RADEON(0): Detected Radeon Mobility M6, disabling multimedia i2c
(II) Loading sub module "theatre_detect"
(II) LoadModule: "theatre_detect"

(WW) Warning, couldn't open module theatre_detect
(II) UnloadModule: "theatre_detect"
(EE) RADEON: Failed to load module "theatre_detect" (module does not exist, 0)
(EE) RADEON(0): Unable to load Rage Theatre detect module

I think it should be included in xf86.video-ati - http://packages.debian.org/de/etch/mipsel/xserver-xorg-video-ati/filelist
http://bbs.archlinux.org/viewtopic.php?id=84071 - in SliTaz there is only ati_drv.so and radeon_drv.so

EDIT: !!! sorry - it is in mesa-dri-ati !!

and I found one more error:

drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(EE) AIGLX error: dlopen of /usr/lib/dri/radeon_dri.so failed (/usr/lib/dri/radeon_dri.so: cannot open shared object file: No such file or directory)
(EE) AIGLX: reverting to software rendering
(EE) AIGLX error: dlopen of /usr/lib/dri/swrast_dri.so failed (/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
(EE) GLX: could not load software renderer

radeon_dri.so and swrast_dri.so should be in the package libgl-dri, which is not present - see http://bbs.archlinux.org/viewtopic.php?id=24216

EDIT: !!! sorry - it is in mesa-dri-ati !!

@jozee - some details on

tazhw setup ati

1) there is missing depency linux-drm - mesa-dri-ati is not working without linux-drm

2) I was trying "tazhw setup ati" from the xvesa.iso and it is not working - I have no Xorg.0.log and the xorg.conf is not changed. If I run afterwards tazx, install the ati driver once again and restart X, I end up with a dark screen

3) If I first run tazx on the xvesa.iso and install the ati driver, xorg is changed to the radeon driver, but there are missing depencies. If I run now tazhw setup ati, the rest of the missing depencies are installed. So I think it would be good to synchronize tazx and hwsetup
!!EDIT: sorry thats wrong - it only works on xvesa.iso, when I install the ati driver before X is started (when you are asked to set the resolution, there is the possibility to install the driver)!!!

4) is there any possibility that tazhw is detecting AGP? perhaps, when lspci finds AGP in the output, that tazhw is installing linux-agp and loads the modules (the modul intel-agp must be loaded, when you have a intel cpu, even you have a ati card)? - and the the module agpgart must be loaded before the module radeon, otherwhise dri is not working

5) as a summit from above: the ati driver should be updated to xorg-xf86-video-ati-6.13.0 including the module "theatre_detect"

I have Asus EEE PC 1000H...I installed the drivers and fix drm dri error. Is there a way to activate OpenGL? Still i cant use OpenGL Support.

can you post the output of:

glxinfo | grep render

and the contents of /var/log/Xorg.0.log

http://en.wikipedia.org/wiki/Direct_Rendering_Infrastructure

@kultex

there is missing depency linux-drm - mesa-dri-ati

fixed http://hg.slitaz.org/wok-stable/rev/d4f3fe7e0dc0

So I think it would be good to synchronize tazx and hwsetup

Yes, its on our to-do list

the module agpgart must be loaded before the module radeon

Theoretically, it should be automatically loaded by "tazhw detect-pci" . It worked on my computer with nvidia. If its not happening oon your computer, we need to retest and troubleshoot on finding the lingering bug.

My output for
glxinfo | grep render
is
sh: glxinfo: not found

@ozgur

so I think you did not follow the howto ..... did you tazhw detect-pci and modprobe drm? did you load all modules at startup?

@ jozee the problem is that tazhw setup ati does not install linux-agp - it is also in the manual installation section of the howto - tazhw setup nv installs linux-agp tazhw setup ati not - I have no idea if linux-agp is needed by all ati cards?

when I install linux-agp before running tazhw setup ati, everything is ok.

And I think tazhw setup nv should also download linux-drm

@kultex
Do i have to load all those modules over again in each start up or is there a way to start them automatically?

@ozgur

see section: Load modules persistently of the howto

@jozee the trident driver has troubles to get dri working - until now, I dont know, if it is a bug in xorg or in Slitaz

glxinfo is

tux@slitaz:~$ glxinfo
-sh: glxinfo: not found

but should be:

tom@ubuntu-studio:~$ glxinfo | grep render
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
OpenGL renderer string: Mesa GLX Indirect

the missing line in Xorg.0.log is

(II) AIGLX: Screen 0 is not DRI capable
(II) Loading sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/lib/xorg/modules/extensions//libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
	compiled for 1.4.0.90, module version = 1.0.0
	ABI class: X.Org Server Extension, version 0.3
(II) GLX: Initialized MESA-PROXY GL provider for screen 0
Atom 4, CARD32 4, unsigned long 4

and it would be good to have glxgears available - normally I think, it should be included in mesa http://www.x.org/wiki/ModuleComponentList?highlight=(glxgears)

EDIT: I found glxgears and glxinfo: both are in mesa demos and also trident is ok - they use a different renderer now

tux@slitaz:~$ glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: Software Rasterizer

when I install linux-agp before running tazhw setup ati, everything is ok.

I purposely didn't add linux-agp to tazhw setup for ati. I thought I will update mesa-dri receipt in repos and then, I totally forgot about that. Now fixed. Thanks for reminding. http://hg.slitaz.org/wok-stable/rev/972f227eb745

Other thing if you have "sh: not found" error, please see which package is the file in and install that pkg. Search with :

 tazpkg search-pkgname glxinfo

I did everything written in "howto", but still i have no 3d support

first have a look into the howto again ( I was changing it quite a lot yesterday) , then install mesa demos

tazpkg get-install mesa-demos

and then give the output of

glxinfo | grep render

and

glxgears

After installing mesa-demos, i have no wallpaper and i can not run desktop wallpaper changer. and still slitaz can not recognize glxinfo command.
It says "glxinf?" instead of "glxinfo".

Ozgur,

You might have a bug reported a year ago on the old forum-

http://forum.slitaz.org/index.php/discussion/1162/solved-main-menu-preferences-desktop-wallpaper-broken

Slicel,
Ok this fixes desktop issue but system can not recognize glxinfo command and it says:
sh: glxinf?: not found
and why it is written as "glxinf?"

@ozgur

so lets start from the beginning: output of: " lspci"

and which iso are you using

@jozee

checking glxgears on different computers, I recognized, that SliTaz has very poor output. What I have recognized is, that SliTaz is using all the time the OpenGL renderer string: Software Rasterizer and the glxgears output is on all machines the same !! a bit strange !!

============= Thinkpad X31 ==============

on Slitaz

tux@slitaz:~$ glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: Software Rasterizer

tux@slitaz:~$ glxgears
937 frames in 5.0 seconds = 187.236 FPS

on Crunchbang Linux with xorg-server 1.7.5

crunchbang@crunchbang:~$ glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: Mesa DRI R100 (RV100 4C59) 20090101 AGP 1x x86/MMX/SSE2 NO-TCL
crunchbang@crunchbang:~$ glxgears
2470 frames in 5.0 seconds = 493.880 FPS

=============Portege R100 ===============

SliTaz

tux@slitaz:~$ glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: Software Rasterizer

tux@slitaz:~$ glxgears
560 frames in 5.0 seconds = 111.956 FPS

on Ubuntustudio 8.4 (xorg 7.3, xorg-server 1.4.1)

tom@ubuntu-studio:~$ glxinfo | grep render
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
OpenGL renderer string: Mesa GLX Indirect

tom@ubuntu-studio:~$ glxgears
1038 frames in 5.1 seconds = 204.261 FPS

I dont get running crunchbang on the portege

===============Asus EEE/Box =============

Slitaz

tux@slitaz:~$ glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: Software Rasterizer
tux@slitaz:~$ glxgears
619 frames in 5.0 seconds = 123.699 FPS

Crunchbang

crunchbang@crunchbang:~$ glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: Mesa DRI Intel(R) 945GME GEM 20091221 2009Q4 x86/MMX/SSE2
crunchbang@crunchbang:~$ glxgears
2066 frames in 5.0 seconds = 413.184 FPS

Good report. Need to debug which pkg is a culprit : xorg, xorg-xf86-video-ati, mesa , mesa-dri, meda-dri-ati or something else like the intel card. Maybe the latest update in xorg-server in coooking wok already addresses this issue. May like to file this on labs.

I think the integration of the different renderers does not work - like it does not make any difference, if I install mesa-dri-ati or mesa-dri-intel or mesa-dri-trident or not - this does not effect nither glxinfo nore glxgears, OpenGL renderer string is always Software Rasterizer, which I think is included as a basic in mesa-dri.

"May like to file this on labs. " sorry, I do not understand, if I should do this or you - I prefer you, because I think it is more efficiant.

@kultex : Its either the problem with mesa 7.4 or Xorg. I think these two bug reports are relevant :
1) Mesa problem and
2) Xorg path problem : looking for drivers in /usr/lib/xorg/modules/dri instead of /usr/lib/dri/

In cooking, mesa is already > 7.8 and linux kernel =33.2, so mesa problem should be resolved. Can you check Xorg logs and also check the output of:

 LIBGL_DEBUG="verbose" glxinfo 

both not - there should be errors, either in Xorg.=.log or in glxgears. But there are no errors.

I am replacing my Ubuntustudio on the R100 by puredyne - Ardour is working much better than in Ubuntustudio (no crashes). In purednye I was struggling quite a lot with xorg, because without the correct modline I just had 800x600. I took the xorg.conf from SliTaz - no chance. And it is also using the xorg 7.4 with xorg-server 1.6.4. And also there is only Rasterizer available - I have to check this on the other machines. Perhaps its just a bug in xorg 7.4

tux@slitaz:~$ LIBGL_DEBUG="verbose" glxinfo
name of display: :0.0
libGL: OpenDriver: trying /usr/lib/dri/swrast_dri.so
display: :0  screen: 0
direct rendering: Yes
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.4.4
OpenGL shading language version string: 1.20

I have seen similar differences with frame rates as reported by glxgears using xorg and nvidia -96xx...on slitaz 3.0 and another small linuz distro also using xorg and nvidia-96xx. The slitaz reported frame rates are substantialy lower. Can it be due to mesa-dri?

@greg : Nvidia is fixed now : http://hg.slitaz.org/wok/rev/96f8f0d779a5 .
Here is mine:

glxgears                   
Running synchronized to the vertical refresh.  The framerate should be
approximately 1/2 the monitor refresh rate.
44135 frames in 5.0 seconds = 8826.935 FPS
44310 frames in 5.0 seconds = 8861.892 FPS

I will update nvidia-96xx package tomorrow. Meanwhile, you can just do this and test (ONLY FOR NVIDIA non-free) :

cd /usr/lib/X11/modules/extensions
mv libglx.so libglx.so.xorg.bak
ln -s libglx.so.* libglx.so

Then, just rename xorg.conf to xorg.conf.bak and reboot.

@kultex :
can you also rename xorg.conf to xorg.conf.bak and reboot. It would generate a new Xorg.conf. Then test again and see your xorg.0.log. Please check the module loading path. It may again be just a linking problem to libglx.so .

I removed libglx.so and made new symbolic link to libglx.so.96.43.16. Could not reboot as I am running from live cd (my-flavor), and would have lost changes...so I downloaded packages and ran .....ldconfig.....logged out of xsession and restarted x

NOW I GET GREAT FRAME RATES...equal to that other distros Yes it is a linking problem...await the new nividix-96xx...thanks

@jozee

I dont know, I have no problems with libglx.so - the module loading path is all the time correct in Xorg.0.log

if I do cd /usr/lib/X11/modules/extensions
rm libglx.so
ln -s libglx.so.* libglx.so

it creates a xorg.conf with errors - when I correct them, I get

(II) LoadModule: "glx"
(II) Loading /usr/lib/X11/modules/extensions//libglx.so
dlopen: /usr/lib/X11/modules/extensions//libglx.so: cannot open shared object file: No such file or directory
(EE) Failed to load /usr/lib/X11/modules/extensions//libglx.so
(II) UnloadModule: "glx"
(EE) Failed to load module "glx" (loader failed, 7)

@kultex: Really sorry! I was not clear in my instructions. Those instructions were only for nvidia (non-free). I have edited of my post now.

For free version, one needs to use xorg-server libglx.so . Either just reinstall xorg-server or extract libglx.so from xorg-server.tazpkg and copy it to /usr/lib/X11/modules/extensions/

Can you check if xorg is loading drivers from /usr/lib/dri as all the dri drivers are in this path. In my xorg.conf, Module Path is set to /usr/lib/X11/modules/ path. I suspect in case of ati and intel, it may this path problem. Could you post some relevant parts (loading of glx, dri and ati driver) of your xorg.conf .

as I told you, the pathes are fine, but there is a problem in splitting mesa-dri e.g integration of mesa-dri-ati

ok - I did manual install without mesa-dri-ati

Output of Xorg.0.log:

(EE) AIGLX error: dlopen of /usr/lib/dri/radeon_dri.so failed (/usr/lib/dri/radeon_dri.so: cannot open shared object file: No such file or directory)
(EE) AIGLX: reverting to software rendering
(II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0

tux@slitaz:~$ glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: Software Rasterizer
tux@slitaz:~$ glxgears
963 frames in 5.0 seconds = 192.476 FPS
I install mesa-dri-ati

output of Xorg.0.log

(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
(II) AIGLX: enabled GLX_texture_from_pixmap with driver support
(II) AIGLX: Loaded and initialized /usr/lib/dri/radeon_dri.so
(II) GLX: Initialized DRI GL provider for screen 0

still:

tux@slitaz:~$ glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: Software Rasterizer
tux@slitaz:~$ glxgears
963 frames in 5.0 seconds = 192.476 FPS

I rename /usr/lib/dri/swast_dri.so to swast_dri.so.back

the same output of Xorg.0.log but:

tux@slitaz:~$ glxinfo | grep render
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
OpenGL renderer string: Mesa DRI Radeon 20061018 AGP 4x x86/MMX/SSE2 NO-TCL
tux@slitaz:~$ glxgears
1303 frames in 5.5 seconds = 237.682 FPS
1260 frames in 5.6 seconds = 226.145 FPS

slightly better results, but direct rendering: No should be yes

and as I checked in crunchbang both swast_dri.so and radeon_dri.so are present

@kultex : swast_dri.so (in mesa-dri) is what mesa relies on if it does not find the correct drivers that we package in mesa-dri-* (e.g., mesa-dri-ati provides radeon_dri.so) . "OpenGL renderer string: Software Rasterizer" means "swast_dri.so" is providing direct rendering, and therefore you have low framerates.

This may mean that that radeon_dri.so is either faulty or its not the right opengl driver(maybe r600.so). Can you check chrunchbang and see which is the right driver that's getting loaded?

I am now on crunchbang

(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
(II) AIGLX: enabled GLX_SGI_make_current_read !! this line is different to SliTaz !!
(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
(II) AIGLX: enabled GLX_texture_from_pixmap with driver support
(II) AIGLX: Loaded and initialized /usr/lib/dri/radeon_dri.so
(II) GLX: Initialized DRI GL provider for screen 0

and here I deleted radeo_dri.so

(EE) AIGLX error: dlopen of /usr/lib/dri/radeon_dri.so failed (/usr/lib/dri/radeon_dri.so: cannot open shared object file: No such file or directory)
(EE) AIGLX: reverting to software rendering
(II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0

crunchbang@crunchbang:~$ glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: Software Rasterizer
crunchbang@crunchbang:~$ glxgears
416 frames in 5.0 seconds = 83.092 FPS

I deleted swrast_dri.so in crunchbang and everything is still working fine - so its clear, that radeon_dri.so and all the other sub dri.so are faulty

@kultex : Surprising!!. Lets just do a small recap:

1) ATI 2D driver is provided by xorg-xf86-video-ati package (radeon_drv.so file). It works

2) ATI 3D driver is provided by mesa-dri-ati (radeon_dri.so in your case). Xorg loads the module without any errors. But, for some unknown reason, OpenGL direct rendering does not work. Instead swrast.so, the default fallback driver from mesa-dri, is used and that results in low framerate.

3) linux-drm package provides drm.ko and radeon.ko modules. I think these need to be loaded for ati dri to work. Can you check the "dmesg | tail" to see if there are any modprobe errors? Similarly for intel, there is i915 module.

If everything is fine, this is really strange. I have checked the mesa* receipts. Everything looks ok. You said this happens with your intel computer too? But we don't have any logs to suggest any type of error. Surprising!!

yep - exactly . The box with the intel grafic I have to check later, because I am not home, but maybe I forgot something, because I just checked quick before leaving, but for the Thinkpad X31 with the radeon grafic and the Portege R100 with the trident, yes. Just to verify:

tux@slitaz:~$ glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: Software Rasterizer
tux@slitaz:~$ lsmod
Module                  Size  Used by    Not tainted
radeon                341348  2 
intel_agp              23032  1 
drm                   121736  3 radeon
agpgart                25980  2 intel_agp,drm
i2c_core               17468  1 drm

just to compare with crunchbang - there are 2 more: ttm and drm_kms_helper

crunchbang@crunchbang:~$ lsmod
Module                  Size  Used by
radeon                397947  2 
ttm                    24317  1 radeon
drm_kms_helper         17211  1 radeon
drm                   106483  5 radeon,ttm,drm_kms_helper
i2c_algo_bit            3489  1 radeon
intel_agp              20067  1 
agpgart                19100  3 ttm,drm,intel_agp

here is the output of dmesg | tail

tux@slitaz:~$ dmesg | tail
pci 0000:01:00.0: power state changed by ACPI to D0
pci 0000:01:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
[drm] Initialized radeon 1.30.0 20080528 for 0000:01:00.0 on minor 0
mtrr: no MTRR for e0000000,ff0000 found
agpgart-intel 0000:00:00.0: AGP 2.0 bridge
agpgart-intel 0000:00:00.0: putting AGP V2 device into 4x mode
pci 0000:01:00.0: putting AGP V2 device into 4x mode
[drm] Setting GART location based on new memory map
[drm] Loading R100 Microcode
[drm] writeback test succeeded in 2 usecs

and there is an error after tazhw setup ati

================================
your config is backed up at /etc/X11/xorg.conf.backup
if ati fails; please use your backed up xorg.conf

Replace vesa driver with radeon in /etc/X11/xorg.conf
Checking if ati radeon is working ...
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual or fbconfig
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
================================

and in Xorg.0.log there is the module "theatre_detect" missing, but I think that this has no influence

(II) Loading sub module "theatre_detect"
(II) LoadModule: "theatre_detect"
(WW) Warning, couldn't open module theatre_detect
(II) UnloadModule: "theatre_detect"
(EE) RADEON: Failed to load module "theatre_detect" (module does not exist, 0)
(EE) RADEON(0): Unable to load Rage Theatre detect module

jozee, I think, it is not worth to continue here. I thought it is stupid to compare apples with grapes, so I tried to find a Live distro with full xorg support with xorg-server 1.5.2. Still available, I only found crunchbang 8.2, which does not even start on the X31.
Most of the distros either stayed on 7.3 with 1.4.6 or jumped directly to 1.7.5, which seem to work very good and I think is not without reason. At least in Slitaz 3.0 evrything is working - not that fast, but working.

I prefer to continue with the new cooking as soon as something is availaible and I hope, Slitaz is jumping to 1.7.5

Could anyone post using an older laptop that uses the following hardware please post their xorg.conf. I am using a Slitaz on an ancient Compaq Armada E500 (installed to the hard drive). Stuck with a reduced 800x600 screen. Followed all the various howto's and guides and gone round in circles including editing xorg.conf manually to set the modes and change the "Device" but no different.

/etc/slim.conf:

# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path ./:/bin:/usr/bin:/usr/local/bin
default_xserver /usr/bin/Xorg
#xserver_arguments -ac -shadow dpms +extension Composite -screen 1024x768x24

lspci -v

01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64) (prog-if 00 [VGA controller])
Subsystem: Compaq Computer Corporation Armada E500
Flags: bus master, stepping, medium devsel, latency 66, IRQ 11
Memory at 40000000 (32-bit, non-prefetchable) [size=16M]
I/O ports at 2000 [size=256]
Memory at 41000000 (32-bit, non-prefetchable) [size=4K]
[virtual] Expansion ROM at 30000000 [disabled] [size=128K]
Capabilities: [50] AGP version 1.0
Capabilities: [5c] Power Management version 1

root@slitaz:/home/paul# lspci -v
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
Subsystem: Compaq Computer Corporation Armada M700/E500
Flags: bus master, medium devsel, latency 64
Memory at 50000000 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 1.0
Kernel driver in use: agpgart-intel
Kernel modules: intel-agp

root@slitaz:/home/paul# lsmod
Module Size Used by Not tainted
aes_generic 26844 1
intel_agp 23032 1
agpgart 25980 1 intel_agp
rt73usb 22372 0
crc_itu_t 1568 1 rt73usb
rt2x00usb 8532 1 rt73usb
rt2x00lib 23700 2 rt73usb,rt2x00usb
led_class 3436 1 rt2x00lib
input_polldev 3008 1 rt2x00lib
mac80211 138268 2 rt2x00usb,rt2x00lib
cfg80211 52872 2 rt2x00lib,mac80211
snd_es1968 21380 1
gameport 9348 1 snd_es1968
snd_ac97_codec 88736 1 snd_es1968
ac97_bus 1308 1 snd_ac97_codec
snd_pcm 51780 2 snd_es1968,snd_ac97_codec
snd_timer 16344 1 snd_pcm
snd_page_alloc 7256 2 snd_es1968,snd_pcm
snd_mpu401_uart 5612 1 snd_es1968
snd_rawmidi 16920 1 snd_mpu401_uart
snd_seq_device 5544 1 snd_rawmidi
snd 43584 9 snd_es1968,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore 5180 1 snd
yenta_socket 20988 1
rsrc_nonstatic 9136 1 yenta_socket
pcmcia_core 27628 2 yenta_socket,rsrc_nonstatic

Apart from the display niggles, SliTaz works great, and made old hardware very usuable!

Paul

tazhw setup ati --non-free

==========================================================
Due to a lack of compatible hardware for troubleshooting,
this ati device has not been properly tested. Please
report any success, failure, bug to SliTaz Labs or Forums.
==========================================================

Detected PCI devices Kernel modules
================================================================================
> Module in use: intel_agp
> Module in use: yenta_socket
> Module in use: yenta_socket
! Missing module: radio_maestro,
> Module in use: snd_es1968
================================================================================


Detected USB devices Kernel modules
================================================================================
802.11 bg WLAN
* Use --get-firmware option to install missing files.
> Module in use: rt73usb
================================================================================

Do you want to configure X using non-free catalyst ati(radeon) driver (y/N) ? y

your config is backed up at /etc/X11/xorg.conf.backup
if ati fails; please use your backed up xorg.conf
aticonfig: No supported adapters detected
Checking if ati catalyst is working ...
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbo