From: Holly Bostick <motub@planet.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: vlc dies on GL
Date: Thu, 10 Nov 2005 23:59:05 +0100 [thread overview]
Message-ID: <4373D0B9.4060003@planet.nl> (raw)
In-Reply-To: <7573e9640511101212v22954c4cwcb6756a487247a46@mail.gmail.com>
Richard Fish schreef:
> If you want to try the ati-drivers, generally you just need to merge
> the package and change the "Driver" setting in xorg.conf from radeon
> to fglrx.
>
Not completely true; the ati-driver module (fglrx) will not work if the
kernel DRM is compiled (either as a module or statically). Further, the
driver has an included agpgart, but this does not cover all mobo agp
chipsets (no idea which ones it does cover, but not mine apparently)--
so while the kernel agpgart must be available (preferably as a module,
since the fglrx install script checks this before it will compile),
depending on whether you need to use the internal (fglrx) agpgart, or an
external one (from the kernel; I use via-agp), one may need to do some
kernel voodoo (compiling the correct agpgart for your mobo) or some
xorg.conf voodoo (turning on "UseInternalAGPGART" yes or no), some
/etc/modules.autoload.d/kernel-2.6 voodoo (to load your agpgart before
the driver agpgart), or possibly even some /etc/hotplug/blacklist voodoo
(to prevent the kernel DRM from loading, because if the kernel loads its
own DRM, the ATI DRM won't load, and the driver does not work with the
kernel DRM). It's quite likely that several forms of voodoo will be
necessary.
Apparently the fglrx module does not work in combination with the
radeonfb driver, either, so if one used that, and the driver did not
work, one might not know why.
In any case, the fglrx requires a specific kernel configuration in order
to work even as well as it does (which may, or may not, be that well,
depending on what you want to do with it), and switching to it is not
necessarily a matter of simply changing the setting in xorg.conf.
Holly
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-10 23:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 19:52 [gentoo-user] vlc dies on GL James
2005-11-09 20:55 ` abhay
2005-11-09 21:08 ` [gentoo-user] " James
2005-11-10 7:14 ` abhay
2005-11-10 14:47 ` James
2005-11-10 16:28 ` Holly Bostick
2005-11-10 18:52 ` James
2005-11-10 19:18 ` abhay
2005-11-12 3:27 ` James
2005-11-10 20:12 ` Richard Fish
2005-11-10 22:59 ` Holly Bostick [this message]
2005-11-10 23:31 ` Richard Fish
2005-11-11 16:07 ` James
2005-11-12 3:24 ` James
2005-11-10 2:01 ` James
2005-11-10 7:16 ` abhay
2005-11-10 15:30 ` James
2005-11-10 16:02 ` ellotheth rimmwen
2005-11-10 18:43 ` James
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=4373D0B9.4060003@planet.nl \
--to=motub@planet.nl \
--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