Is anyone else having problems running compiz since the updates from yesterday? I am also having problems with the xorg-edgers ppa.
I take it back, just installed the latest and seems to be running just fine
seems like there are packaging/install issues i used your ppa before and got top framerates. then i reinstalled mint 11 with your ppa and it was much slower than before with your ppa. i manually built mesa and copied r600_dri.so. solved all problems.
right now your ppa only produce software rendering in hon for me...
gl info shows galium mesa rendering but hon lags very hard.. can not play with that config..
I'm a Thinkpad X120e (Radeon HD 6310) user working with your packages on Oneiric.
and today, i've updated your latest:
then X120e had failed to kick any 3D desktop... the previous 7.11.0~git1106221745.eb2c9b~gd~n were OK. so I had to rollback them.Code:7.11.0~git1106281542.de33b0~gd~n OpenGL renderer string: Gallium 0.4 on llvmpipe OpenGL version string: 2.1 Mesa 7.11-devel (git-de33b0d natty-oibaf-ppa)
and Xorg.0.log says here when I used your latest:
remember well, the previous said:
do you have any ideas to solve it?Code:OpenGL renderer string: Gallium 0.4 on PALM
You should completely remove it if you want to use open source drivers (dunno how because I never installed it).Code:[ 17040.221] (II) LoadModule: "fglrx" [ 17040.222] (WW) Warning, couldn't open module fglrx [ 17040.222] (II) UnloadModule: "fglrx" [ 17040.222] (II) Unloading fglrx [ 17040.222] (EE) Failed to load module "fglrx" (module does not exist, 0)
Last edited by oibaf; 06-29-2011 at 09:53 AM.
I've checked whether fglrx had been remained anywhere again and again... then almost cleared.
but didn't make any differences.
anyway, today I'm using rollbacked mesa:
and here is the /var/log/Xorg.0.log:Code:7.11.0~git1106221745.eb2c9b~gd~n OpenGL renderer string: Gallium 0.4 on AMD PALM version string: 2.1 Mesa 7.11-devel (git-eb2c9b5 ubuntu-natty-graphics-drivers-ppa)
now it works well with gnome-shell/unity/mutter and any other 3D apps. as far as I know, I might not think the problems were causing fglrx's stuff today...