I'm using the latest ati-drivers and the latest xorg - everyone knows, they don't work well. But, I think portage should "think" better and not do things like this: Mon Sep 20 23:03:05 2004 >>> x11-base/xorg-x11-6.8.0-r1 Fri Sep 24 23:50:46 2004 >>> x11-base/xorg-x11-6.7.0-r2 Mon Sep 27 23:11:48 2004 >>> x11-base/xorg-x11-6.8.0-r1 Sun Oct 3 17:48:15 2004 >>> x11-base/xorg-x11-6.7.0-r2 Tue Oct 5 22:05:39 2004 >>> x11-base/xorg-x11-6.8.0-r1 Thu Oct 7 22:28:01 2004 >>> x11-base/xorg-x11-6.7.0-r2 Fri Oct 8 15:46:12 2004 >>> x11-base/xorg-x11-6.8.0-r1 As you can notice, every once and a while I have to downgrade to xorg-x11-6.7.0 and then I get back to 6.8.0. Everything works fine :) Thank God, I have ccache ;] Reproducible: Always Steps to Reproduce: 1. 2. 3.
The problem here is that 6.8.0 is newer than 6.7.0, so it wants to replace it, and does. But then ati-drivers don't want anything later than 6.7.99, so they switch it back. You should be seeing the flip-flop on every emerge -uDp world or similar. I have observed that the 6.8.0 driver-r1 driver *DOES* seem to work, in fact works better, with the latest ati-drivers, so I have been using a locally-patched ebuild that specifies >=6.8.0 instead of <6.7.99.
Should be fixed now.
