Release Candidates :: DSL v4.0rc4

I just booted up rc4 and noticed the torsmo display is missing. I copied the two torsmo files from /etc/skel and restarted just to be sure, but still no torsmo...

I have the same problem in dsl-3.4.3 also. I guess this is something to do with the move to torsmo-0.18?

I did some testing on the auto-library finder for uci extensions in rc4. If we assume that Curaga's Glxgears extension has no idea where to find the libs in Mikshaw's mesa3d extension, then it seems to work well:

Code Sample

$ mydsl-load /mnt/sdb1/mydsl/mesa3d.uci
/mnt/sdb1/mydsl/mesa3d.uci sucessfully loaded!
$ mydsl-load /mnt/sdb1/mydsl/Glxprogs.tar.gz
$ glxgears
3618 frames in 5.0 seconds = 723.600 FPS
3641 frames in 5.0 seconds = 728.200 FPS
3674 frames in 5.0 seconds = 734.800 FPS
3674 frames in 5.0 seconds = 734.800 FPS
3635 frames in 5.0 seconds = 727.000 FPS

$ glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: No
server glx vendor string: Brian Paul
server glx version string: 1.4 Mesa 6.5.2

..note no drm as there's no i915 module.

Interestingly, this was significantly faster than XFree86 with drm on the same machine, albeit dsl-3.4.3:

Code Sample

$ glxgears
2748 frames in 5.0 seconds = 549.600 FPS
3115 frames in 5.0 seconds = 623.000 FPS
3123 frames in 5.0 seconds = 624.600 FPS
3121 frames in 5.0 seconds = 624.200 FPS

$ glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2

Well, openGL/mesa updates can also bring speed

And remember that glxgears is not a benchmark.
It's just for verifying that your system's DRI is working properly.

But back on topic: did the loading of the extension take longer?

Quote (Juanito @ Sep. 19 2007,03:43)

Anyone else experiencing this?
Any errors displayed when starting from an xterm?
Anything special about your hardware, i.e., multiple processors?

It worked fine on my 4 test machines.

Would like more feedback.

Next Page...
original here.