From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-user+bounces-97579-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1MMnx0-0007bR-W7
for garchives@archives.gentoo.org; Fri, 03 Jul 2009 18:57:35 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 115DAE0457;
Fri, 3 Jul 2009 18:57:34 +0000 (UTC)
Received: from IMPaqm4.telefonica.net (impaqm4.telefonica.net [213.4.129.19])
by pigeon.gentoo.org (Postfix) with ESMTP id 46222E0457
for <gentoo-user@lists.gentoo.org>; Fri, 3 Jul 2009 18:57:33 +0000 (UTC)
Received: from IMPmailhost4.adm.correo ([10.20.102.125])
by IMPaqm4.telefonica.net with bizsmtp
id BWJi1c02A2iL0W23QWxYgy; Fri, 03 Jul 2009 20:57:32 +0200
Received: from jesgue.homelinux.org ([78.136.66.163])
by IMPmailhost4.adm.correo with BIZ IMP
id BWxP1c0023XLmEe1kWxPNU; Fri, 03 Jul 2009 20:57:28 +0200
X-TE-authinfo: authemail="i92guboj.terra.es" |auth_email="i92guboj@terra.es"
X-TE-AcuTerraCos: auth_cuTerraCos="cosuitera01"
Received: from 192.168.0.10
(SquirrelMail authenticated user i92guboj)
by jesgue.homelinux.org with HTTP;
Fri, 3 Jul 2009 20:57:27 +0200
Message-ID: <e592a4c4d29838d10312fd142c31b80a.squirrel@jesgue.homelinux.org>
In-Reply-To: <200907032030.37646.volkerarmin@googlemail.com>
References:
<5602B0BD6D59AE4791BE83104940118DC338017F@excprdmbxw002.optus.com.au>
<200907031717.34010.volkerarmin@googlemail.com>
<d07a70780907030922p1856e9a1mc26902031dd3909f@mail.gmail.com>
<200907032030.37646.volkerarmin@googlemail.com>
Date: Fri, 3 Jul 2009 20:57:27 +0200
Subject: Re: [gentoo-user] ATI-Driver 9.6 support?
From: =?iso-8859-1?Q?Jes=FAs_Guerrero?= <i92guboj@terra.es>
To: gentoo-user@lists.gentoo.org
User-Agent: SquirrelMail/1.5.2 [SVN]
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: 3c99de91-40b0-45ee-9a23-84e3451eae3d
X-Archives-Hash: 6d8ad84a8c119d5fc3ef0ff3f6965cd4
On Fri, July 3, 2009 20:30, Volker Armin Hemmann wrote:
> Well, AMD uses a fixed cycle - one release a month. They also have a
> fixed development cycle that takes roughly 3 month (all explained on
> phoronix a long time ago). So supporting the latest kernels is not easy=
or
> even possible.
Very well for them, I don't know how that is relevant, since 2.6.29 was
released 23-Mar-2009 23:30. So, by now, both the 1 month and the 3 month
cycles have passed. Still no support. Or maybe my maths are not correct.
> They also only support a few distros. If you insist on using a
> non-supported kernel, you are on your own.
Crap. All the distros use the same kernel. If it compiles against a vanil=
la
kernel, it will compile against a vanilla kernel on *every* distro under
the sun. There can be problems with the location of the libraries, versio=
ns
of xorg and mesa and the like, that that's out of the scope of this threa=
d,
which is basically that we will get a working driver for 2.6.30 6 months
after the kernel is released. By then we will have .35, which won't work
with fglrx either. That the distro is listed as supported or not doesn't
change the scenery if you want to use a current kernel for some reason.
> That said - Nvidia might be 'better' when it comes to binary drivers, b=
ut
> they suck when it comes to open source drivers.
Agreed. But at least, you have *one* driver that works. With my hd2600,
fglrx sucks big time, and neither radeon nor radeonhd works (unless I
disable dri, and then vesa performs better).
If I have to choose between one closed driver that works perfectly and
one close driver that works bad+2 open ones that simply don't work, I
choose the closed driver that works.
> AMD is working on free
> drivers for all cards - that is something you have to recognize.
As far as I know (I might be wrong) amd isn't working in anything. They
just released the specifications and some technical sheets. The community
is doing all the work.
> Besides - if you use the ebuild, even 2.6.30 works. Yes, dmesg is spamm=
ed
> with ugly messages. But who cares? Do you really monitor dmesg non stop=
?
Who cares?!? mmmm, my /var partition gets filled with +1gb logs everyday,
I have to delete the logs (yes, losing everything in them) and then
restart
the sys logger because while the files are open the space won't be freed.
The driver does that, and the rest of my programs fail. But, who cares...
The cpu usage is insane when using fglrx on .30, 60-100% on X when I play
something in mplayer, so while watching a movie I can't do anything else,
with the same fglrx version on linux 2.6.28 it takes around 10%.
Who cares? I do. The driver just doesn't work, these are not minor
annoyances, as you paint them, these are big problems. And the ebuild
should be eliminated, and the old one depending on <2.6.29 should be
restored.
I really advice to stay in .28 if you are going to use fglrx.
--=20
Jes=FAs Guerrero