On Donnerstag 16 Juli 2009, Keith Dart wrote: > On Thu, 16 Jul 2009 01:56:57 +0200 > > Volker Armin Hemmann <volkerar...@googlemail.com> wrote: > > so very wrong. > > From the AMD driver web site: > > "32-Bit packages must be installed for 64-Bit Linux drivers to install > or work. "
yes, but that does not mean 'strictly 32bit'. In fact, that part of the amd website is wrong, as Bridgeman explained in the phoronix forum. The amd drivers work perfectly fine in a pure 64bit environment. http://www.phoronix.com/forums/showthread.php?t=10868&highlight=32- Bit+packages+installed+64-Bit+Linux+drivers+install > > The ebuild also pulls in the app-emulation/emul-linux-x86-xlibs > package. because the maintainer believes a wrong website and not facts. Also you need the 32bit emul stuff when you try to run 32bit apps - like a lot of people still do or want to do. In a non-multilib environment those are not needed. There is a bug open about this. > > Please explain. > you said 'strictly 32bit' which is absolutely and utterly wrong. > > > The open-source x11-drivers/xf86-video-ati package works much > > > better. If you don't really need the 3D acceleration I'd recommend > > > you switch to that. > > > > except that they don't have working powermanagment, increasing energy > > consumption (a lot) and noise (even more). > > I hadn't noticed that. I did notice a definite speed and > stability improvement after switching to the open-source drivers. The > ati-drivers also crashed my system occasionally. 106W with catalyst. 170W with open source drivers. fan quiet with catalyst (not able to hear it) in KDE and most of the time playing games. fan extremely loud with open source drivers. air warm (2 slot card) with catalyst. air hot with open source drivers. 2d mostly acceptable with catalyst (I can live with the shortcomings since i don't have problems with 'Tearing' or slow window resize with composite turned on). 2d always acceptable with open source drivers. 3d very good with catalyst. 3d not existing with open source drivers. The only crash I can see with 9.6 and 2.6.30: if the monitor was sent into standby/off mode, turns back on and an app uses xv to display video or a 3d game starts there is a high chance that the box might lock up in the next couple of minutes. Since I am at my box either almost all the time or turn it off, this isn't a problem for me - it might be for other people.
