Mick writes:

> On 25 March 2010 11:50, Helmut Jarausch <jarau...@igpm.rwth-aachen.de>
> wrote:

> > Many thanks, do you have an estimate when 10.4 appears in the tree?
> > Helmut.
> 
> I can't answer that (as far as I know the devs will only say that it
> will appear when it is ready) but I got myself into a pickle with
> trying to switch from radeon to fglrx driver, running xorg-server
> 1.7.6.  

I think you have to wait for ati-drivers-10.4 to work with xorg-1.7.

> It kept going around in circles with blockers and after
> subsequent masking and unmasking I couldn't get it to emerge, so I
> went back to the radeon driver.  Mind you I did not rebuilt the kernel
> at the time and that may be why I was getting 'you can't have these
> packages installed at the same time' type of message.

With the radeon driver, I only got a blank screen, so I am using ati-
drivers. From kernel 2.6.31 on, they are sort of working fine, with GLX 
and all that. Here is what I had to mask to keep the older x.org 1.6:

>=x11-apps/xinput-1.5.0
>=x11-base/xorg-drivers-1.7
>=x11-base/xorg-server-1.7
>=x11-libs/libX11-1.3.2
>=x11-libs/libXScrnSaver-1.2.0
>=x11-libs/libXext-1.1.1
>=x11-libs/libXi-1.3
>=x11-libs/libXinerama-1.1
>=x11-libs/libXtst-1.1.0
>=x11-libs/libXxf86dga-1.1.1
>=x11-libs/libXxf86vm-1.1.0
>=x11-proto/bigreqsproto-1.1.0
>=x11-proto/fixesproto-4.1.1
>=x11-proto/inputproto-2.0
>=x11-proto/recordproto-1.14
>=x11-proto/scrnsaverproto-1.2.0
>=x11-proto/xcmiscproto-1.2.0
>=x11-proto/xextproto-7.1.1
>=x11-proto/xf86bigfontproto-1.2.0
>=x11-proto/xf86dgaproto-2.1
>=x11-proto/xf86driproto-2.1.0
>=x11-proto/xf86vidmodeproto-2.3
>=x11-proto/xineramaproto-1.2
>=media-libs/mesa-7.6


> I only wanted to try fglrx, because someone on the Ubuntu forums said
> that it stopped their laptop fan from running all the time (mine
> starts when the temperature reaches 50C or so and thereafter runs
> continuously).

That's what I heard, too. Still, I have high CPU loads for the X process 
when running KDE4 with my Radeon 4200 GPU.

        Wonko

Reply via email to