From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?
Date: Fri, 22 Sep 2006 17:08:37 -0700 [thread overview]
Message-ID: <5bdc1c8b0609221708t53c0557bw30a746f548acffb5@mail.gmail.com> (raw)
In-Reply-To: <ef1sda$jgt$2@sea.gmane.org>
On 9/22/06, Duncan <1i5t5.duncan@cox.net> wrote:
> "Mark Knecht" <markknecht@gmail.com> posted
> 5bdc1c8b0609221235i2270bbenf016d5fa7a1998ec@mail.gmail.com, excerpted
> below, on Fri, 22 Sep 2006 12:35:47 -0700:
>
> > It turns out that for me the problem was the ati-drivers package.
> > Switching to the radeon driver today lowered the CPU usage back to the 9%
> > range that I was used to:
>
> Thanks! Always nice to see freedomware win. =8^)
>
I agree Duncan.
Now, the one issue left for complete world domination would be to
better understand how to get DRI working with this video adapter. Am I
correct that DRI==3D? Or does DRI go further than just basic 3D and
help other things like MythTV or something else I'm not thinking of at
all?
I do see these messages in xorg.0.log:
(**) RADEON(0): RADEONSaveMode returns 0x709390
(WW) RADEON(0): Enabling DRM support
*** Direct rendering support is highly experimental for Radeon 9500
*** and newer cards. The 3d mesa driver is not provided in this tree.
*** A very experimental (and incomplete) version is available
from Mesa CVS.
*** Additional information can be found on http://r300.sourceforge.net
*** This message has been last modified on 2005-08-07.
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
I do NOT do ANY Linux-based 3D stuff today. My workload is Mainly
music applications - Ardour, etc., which do not care about 3D, web
browsing, MythTV and Xine to watch movies. Do I / should I care about
DRI?
I do occasionally play Windows games under Cedega. Would DRI ever help
that sort of application?
Anyway, things seem to be in pretty good shape. Maybe I should just
leave good enough alone. ;-)
Cheers,
Mark
P.S. - I'm still curious about trying your compiler flags but now
there is no pressing timeframe to do it in on this machine. - MWK
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-23 0:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 19:35 [gentoo-amd64] SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone? Mark Knecht
2006-09-22 23:42 ` [gentoo-amd64] " Duncan
2006-09-23 0:08 ` Mark Knecht [this message]
2006-09-23 8:28 ` Christoph Mende
2006-09-23 9:55 ` Greg Bur
2006-09-23 10:03 ` Mark Knecht
2006-09-23 10:16 ` Greg Bur
2006-09-23 10:49 ` Peter Humphrey
2006-09-23 17:40 ` Mark Knecht
2006-09-23 21:00 ` Duncan
2006-09-25 20:25 ` Sergio Polini
2006-09-25 20:55 ` Piotr Pruszczak
2006-10-08 18:44 ` Sergio Polini
2006-10-08 18:47 ` Peter Davoust
2006-09-26 1:09 ` Mark Knecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5bdc1c8b0609221708t53c0557bw30a746f548acffb5@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox