From: "Peter Gaži" <petergazi@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ati-drivers and gentoo-dev-sources-2.6.9 hate each other?
Date: Sun, 5 Dec 2004 22:24:43 +0100 [thread overview]
Message-ID: <cce1d1460412051324716c7372@mail.gmail.com> (raw)
In-Reply-To: <41B3798E.8030605@planet.nl>
>
> What driver were you actually using when you re-emerged ati-drivers? I
> have a Radeon 9800 SE and use a 2.6.10 kernel, but of late I've noticed
> that this combo fares badly if I don't actually start up with the vesa
> drivers before re-emerging the ati-drivers (as opposed to starting up
> with the old version of fglrx, which won't load from modules.autoload.d,
> but will kinda half run in some weird fashion using MESA if I start X).
>
> Of course, all is normal after (yet another) reboot, as long as there
> were no "DRM driver not built" errors during the ati-drivers compile
> (lately there have in fact been other warning errors, but the module is
> in fact built and works fairly well).
>
> Also, what version of the ati-drivers are you using? Most of them are
> flakey, but some versions are flakier than others.
>
I use media-video/ati-drivers-3.14.1, the last 'stable' ones in x86
portage tree. So what is your procedure after upgrading a kernel? I
only do
emerge ati-drivers && opengl-update ati
am I missing something? Also I am quite confused of the
UseInternalAGPGart option which is so often mentioned in all the
howtos, how do i determine if i shoud check it?
Thanks for any ideas.
Peter
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2004-12-05 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 19:20 [gentoo-user] ati-drivers and gentoo-dev-sources-2.6.9 hate each other? Peter Gaži
2004-12-05 21:11 ` Holly Bostick
2004-12-05 21:24 ` Peter Gaži [this message]
2004-12-06 2:21 ` Adrien Tougas
2004-12-06 3:36 ` cs_snx
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=cce1d1460412051324716c7372@mail.gmail.com \
--to=petergazi@gmail.com \
--cc=gentoo-user@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