-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Benjamin Herrenschmidt wrote: > On Thu, 2007-04-26 at 15:59 -0400, Andrew J. Barr wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Taylor Oliphant wrote: >>> Anyone have Beryl running? I have a powerbook g4 and >>> would love to get it up and running. >> What graphics card? Compiz runs fine on my ATI RV350 with the free >> radeon driver (well, what else?) and these patches: >> >> http://people.freedesktop.org/~daenzer/aiglx-zero-copy-tfp/ >> >> You _need_ these for AIGLX compositing and a discrete graphics card >> (e.g. it's own memory). You will want to throw your nice shiny Powerbook >> across the room if you don't have them and you try to run Compiz or >> Beryl. Trust me. > > Care to make .debs ? :-)
Been there done that. Add the key this message is signed with to your APT keyring and add the following to /etc/apt/sources.list: deb http://www.oakcourt.dyndns.org/~andrew/linux/powerbook/aiglx-zero-copy-tfp ./ # optionally deb-src http://www.oakcourt.dyndns.org/~andrew/linux/powerbook/aiglx-zero-copy-tfp ./ 512Kbps bandwidth max, however, so if it gets slow someone might have to mirror them. Minor caveat: If you want things WRT to upgrades to work normally, pin that repository somehow. I haven't figured out an easy and sane way to keep packages I've made personal changes to higher up on APT's list than the official repos, and I followed policy with regards to non-maintainer uploads (6.5.2-3 to 6.5.2-3.1) and now aptitude/update-notifier wants to "upgrade" mesa to 6.5.2-4 in unstable. The only thing I have figured is to bump the epoch (2:6.5.2-3) which is a bit messy and won't always yield desired results, especially if I end up distributing the packages. At any rate, enjoy. Andrew > Ben. > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGMXlwhuM+Z62a52oRAlPDAKDMbk270Hk5gSFOYTE01XcDpX9U9wCfcgDT CvlCrtmMoeHAYl4JW0OFDWI= =NFMi -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]