New to the open source drivers - please help

[gloscherrybomb]

I tried xmoto and it seemed to run fine, and no errors from the terminal.

So what seems to be the problem?

I tried xmoto and it seemed to run fine, and no errors from the terminal.

So what seems to be the problem?

Is it linked to my glxinfo wher eit says None or Slow like this:?

16 GLXFBConfigs:
   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------
0x5c  0 tc  0 32  0 r  .  .  8  8  8  8  0 24  0  0  0  0  0  0 0 None
0x5d  0 tc  0 32  0 r  .  .  8  8  8  8  0 24  0 16 16 16 16  0 0 Slow
0x5e  0 tc  0 32  0 r  y  .  8  8  8  8  0 24  0  0  0  0  0  0 0 None
0x5f  0 tc  0 32  0 r  y  .  8  8  8  8  0 24  0 16 16 16 16  0 0 Slow
0x60  0 tc  0 32  0 r  .  .  8  8  8  8  0 24  8  0  0  0  0  0 0 None
0x61  0 tc  0 32  0 r  .  .  8  8  8  8  0 24  8 16 16 16 16  0 0 Slow
0x62  0 tc  0 32  0 r  y  .  8  8  8  8  0 24  8  0  0  0  0  0 0 None
0x63  0 tc  0 32  0 r  y  .  8  8  8  8  0 24  8 16 16 16 16  0 0 Slow
0x64  0 dc  0 32  0 r  .  .  8  8  8  8  0 24  0  0  0  0  0  0 0 None
0x65  0 dc  0 32  0 r  .  .  8  8  8  8  0 24  0 16 16 16 16  0 0 Slow
0x66  0 dc  0 32  0 r  y  .  8  8  8  8  0 24  0  0  0  0  0  0 0 None
0x67  0 dc  0 32  0 r  y  .  8  8  8  8  0 24  0 16 16 16 16  0 0 Slow
0x68  0 dc  0 32  0 r  .  .  8  8  8  8  0 24  8  0  0  0  0  0 0 None
0x69  0 dc  0 32  0 r  .  .  8  8  8  8  0 24  8 16 16 16 16  0 0 Slow
0x6a  0 dc  0 32  0 r  y  .  8  8  8  8  0 24  8  0  0  0  0  0 0 None
0x6b  0 dc  0 32  0 r  y  .  8  8  8  8  0 24  8 16 16 16 16  0 0 Slow

[gloscherrybomb]

Been playing with this for hours now and still no fix.

Can desktop effects definitely be enabled on x1650 pro jaunty?

[agd5f]

yes, it should work fine.

[Pitabred]

Been playing with this for hours now and still no fix.

Can desktop effects definitely be enabled on x1650 pro jaunty?

Gnome desktop effects work great for me (even the full uber-mode) on my integrated x1250 and Jaunty, so I can't imagine it'd be any worse on an x1650.

[gloscherrybomb]

I cant work it out. I tried totally removing (including config files) compiz and reinstalling, made no difference. Is there a command which checks which version of the opensource driver is being used and that it is working properly?

[suokko]

I cant work it out. I tried totally removing (including config files) compiz and reinstalling, made no difference. Is there a command which checks which version of the opensource driver is being used and that it is working properly?

glxinfo It reports your opengl version + mesa version. It also tells all 3D related options that are enabled in your driver.

One possibility is that compiz is causing software fallback for some reason. You can try to run compiz with debuging "RADEON_DEBUG=verbose compiz --replace 2> compiz.log". After moment of extreme slowness you can go back using metacity/kwin and pastebin that logfile in case there is some useful info.

Also you could try if metacity can handle basic composite. Easiest way to test that is to install screenlets and start composite toggler. If you use KDE kwin also has very good composite support that rivals what compiz can do.

3D driver is part of mesa. If you want to try cutting edge version of driver (that might be unstable) you can follow https://wiki.ubuntu.com/XorgOnTheEdge but be very careful as break stuff with them is very easy. The best way to first test is to use Jaunty livecd and install driver there and then if everything works you can do same in your real environment.

[bridgman]

I cant work it out. I tried totally removing (including config files) compiz and reinstalling, made no difference. Is there a command which checks which version of the opensource driver is being used and that it is working properly?

Did you ever install fglrx on this copy of Jaunty, or are you still basically running the open source drivers which were installed by default ? The reason I'm asking is that fglrx over-writes some files on installation, and I believe those over-written files will cause problems with the open source drivers. Pretty sure that uninstalling fglrx with the package manager restores the previous files, but not 100% sure.

[gloscherrybomb]

I havent touched fglrx, and I've double checked and nothing to do with fglrx is installed. I have kept the same home folder, so there could be some old config files somewhere?

Suokko, just trying your bits now, I'll report back.

[gloscherrybomb]

james@james-desktop:~$ RADEON_DEBUG=verbose compiz --replace 2> compiz.log
Checking for Xgl: not present. 
xset q doesn't reveal the location of the log file. Using fallback /var/log/Xorg.0.log 
Detected PCI ID for VGA: 
Checking for texture_from_pixmap: not present. 
Trying again with indirect rendering:
Checking for texture_from_pixmap: present. 
Checking for non power of two support: present. 
Checking for Composite extension: present. 
Checking screen 1Comparing resolution (1440x900) to maximum 3D texture size (4096): Passed.
Checking for Software Rasterizer: Not present. 
Checking for nVidia: not present. 
Checking for FBConfig: present. 
Checking for Xgl: not present. 
james@james-desktop:~$

compiz.log (dont think this has any important info):

/home/james/.themes/Dust/gtk-2.0/gtkrc:80: Murrine configuration option "highlight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
/home/james/.themes/Dust/gtk-2.0/gtkrc:81: Murrine configuration option "lightborder_ratio" will be deprecated in future releases. Please use "lightborder_shade" instead.
/home/james/.themes/Dust/gtk-2.0/gtkrc:96: Murrine configuration option "style" is not supported and will be ignored.
/home/james/.themes/Dust/gtk-2.0/gtkrc:228: Murrine configuration option "style" is not supported and will be ignored.
/home/james/.themes/Dust/gtk-2.0/gtkrc:337: Murrine configuration option "style" is not supported and will be ignored.
/home/james/.themes/Dust/gtk-2.0/gtkrc:371: Murrine configuration option "style" is not supported and will be ignored.
/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format

[gloscherrybomb]

This may help: When I click normal desktop effects in jaunty, it searches for a driver before starting the slow desktop effects?

I have started metacity composite using the toggler, and all seems to work well. The only way I can tell is because using a transparent terminal I see my desktop items, i.e. true transparency, so it must be working. I can move windows around quickly with no slowdown, but then there arent any effects.