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: Mon, 10 Oct 2005 11:22:34 -0500	[thread overview]
Message-ID: <434A954A.5010803@comcast.net> (raw)
In-Reply-To: <a3c2e88b0510091344n7fd93d8fod7c6384097fcf23f@mail.gmail.com>

Fernando Meira wrote:

> Hi,
> I know this is a well discussed topic.. but I can't find answer to my 
> problem.. and I'm completely lost in all mails/forums..
>
> I have a ATI Technologies Inc Radeon Mobility M6 LY and I been using 
> "radeon" driver from kernel.
> In order to enable rendering, I been looking around and after no 
> success I was told that I should use fglrx driver from proprietary 
> ATI-drivers! Tried it, but no deal! Then I was again told that these 
> drivers were not to my card, and that radeon should made it.
> So, I'm back to radeon but still no rendering. However, there's noting 
> saying the opposite unless:
> # glxinfo | grep -i rendering
> direct rendering: No
>
I am following this thread w/ interest as I am having similar problems.  
Although I am seeing errors in my syslog file that indicate I'm not even 
able to get agp going.  Anyone seen something similar? 

[drm] Initialized radeon 1.16.0 20050311 on minor 0: ATI Technologies 
Inc M9+ 5C61 [Radeon Mobility 9200 (AGP)]
[drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
[drm:drm_unlock] *ERROR* Process 9513 using kernel context 0


I've got a radeon mobility 9200 in my laptop and have compiled 
CONFIG_AGP=m, CONFIG_AGP_INTEL=m, CONFIG_DRM=m, and CONFIG_DRM_RADEON=m. 

Interestingly enough, agpgart module loads at boot but intel_agp 
doesn't.  Modprobe of intel_agp produces no errors, but lsmod shows it's 
not loaded.  Nothing in log files either.  When X is started, drm and 
radeon modules load up, but dri still doesn't work, probably because agp 
isn't working.

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



  parent reply	other threads:[~2005-10-10 16:26 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 [this message]
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
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=434A954A.5010803@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