public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kevin Hanson <tuxpert@comcast.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] struggling with dri
Date: Wed, 12 Oct 2005 16:28:39 -0500	[thread overview]
Message-ID: <434D8007.3060809@comcast.net> (raw)
In-Reply-To: <434CB665.2050302@tiscali.it>


><*> /dev/agpgart (AGP Support)
>< >   ALI chipset support
>< >   ATI chipset support
>< >   AMD Irongate, 761, and 762 chipset support
>< >   AMD Opteron/Athlon64 on-CPU GART support
><*>   Intel 440LX/BX/GX, I8xx and E7x05 chipset support
>< >   NVIDIA nForce/nForce2 chipset support
>< >   SiS chipset support
>< >   Serverworks LE/HE chipset support
>< >   VIA chipset support
>< >   Transmeta Efficeon support
>< > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
>< >   3dfx Banshee/Voodoo3+ (NEW)
>< >   ATI Rage 128 (NEW)
>< >   ATI Radeon
>< >   Intel I810 (NEW)
>< >   Intel 830M, 845G, 852GM, 855GM, 865G
>< >   Matrox g200/g400 (NEW)
>< >   SiS video cards (NEW)
>
>and all was fine... Direct Rendering up and running!
>
>  
>
This is what finally worked for me.  I am on a 2.6.13 kernel and until I 
built *BOTH* agpgart and intel-agp into the kernel instead of as 
modules, I was unable to get dri working.

I emerged x11-drm with VIDEO_CARDS="radeon".  The radeon driver and drm 
get loaded automatically when I start X.

I think this is an issue with the 2.6.13 kernel not liking agp compiled 
as a module.

Cheers,
Kevin
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2005-10-12 21:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-09 20:44 [gentoo-user] struggling with dri Fernando Meira
2005-10-10  1:50 ` Ow Mun Heng
2005-10-10  8:13   ` Fernando Meira
2005-10-10  8:26     ` Frank Schafer
2005-10-10 10:39     ` Jason Cooper
2005-10-10 14:03       ` Fernando Meira
2005-10-10 14:10         ` Michael Taylor
2005-10-10 14:48           ` Richard Fish
2005-10-10 15:43             ` Fernando Meira
2005-10-10 16:22 ` Kevin Hanson
2005-10-10 16:41   ` Jason Cooper
2005-10-10 17:37     ` Fernando Meira
2005-10-10 19:34       ` Jason Cooper
2005-10-11 15:42         ` Fernando Meira
2005-10-11 16:34           ` Fernando Meira
2005-10-11 16:38           ` Holly Bostick
2005-10-11 22:32             ` Fernando Meira
2005-10-12  7:08             ` gentoo_falstaff
2005-10-12 17:37               ` Douglas James Dunn
2005-10-12 21:28               ` Kevin Hanson [this message]
2005-10-10 17:47     ` Kevin Hanson
2005-10-11  2:26       ` W.Kenworthy
2005-10-11  9:17         ` gentoo_falstaff
2005-10-11  9:34           ` Fernando Meira
2005-10-12 15:31 ` Robert Svoboda
2005-10-12 20:02   ` Fernando Meira
2005-10-13  7:02   ` Fernando Meira

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=434D8007.3060809@comcast.net \
    --to=tuxpert@comcast.net \
    --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