From: Aubin LaBrosse <arl8778@rit.edu>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: DRI and AGP on 2.6.0-test9
Date: Sun, 23 Nov 2003 13:55:55 -0500 [thread overview]
Message-ID: <1069613755.9574.68.camel@rain.rh.rit.edu> (raw)
In-Reply-To: <Pine.LNX.4.53.0311231313110.2498@montezuma.fsmlabs.com>
On Sun, 2003-11-23 at 13:15, Zwane Mwaikambo wrote:
> On Sun, 23 Nov 2003, Aubin LaBrosse wrote:
>
> > Hi all,
> >
> > I'm having a problem with 2.6.0-test9 and DRI. dmesg tells me:
> >
> > [drm] Initialized radeon 1.9.0 20020828 on minor 0
> > [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
> > [drm:radeon_unlock] *ERROR* Process 4113 using kernel context 0
>
> For my curiosity, can you try compiling the Radeom/drm and AGP driver into
> the kernel?
I have done it both ways with the same results, sorry, should have
mentioned that...
>
> > anyway, some more information:
> >
> > this is a 2-cpu machine, AMD MP2000+'s on a Tyan Tiger MPX board
> > (AMD-760MPX chipset ) 4xAGP, Radeon AIW (the original one, so i suspect
> > 7200. certainly r200, which afaik requires no proprietary drivers at all
> > for dri to work. Perhaps it is an smp issue? anyway, here's my kernel
> > config:
>
> I just tried test9-mm5 with a radeon 9000 on an smp machine with the
> desired results.
I will give -mm5 a shot (this was with stock 2.6.0-test9, i haven't
gotten into applying the -bk patches as soon as they hit, yet) Though
I'm not sure -mm5 has any patches specific to DRI or agp, but it's
definitely worth a shot. thanks Zwane.
-Aubin
next prev parent reply other threads:[~2003-11-23 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-23 7:19 DRI and AGP on 2.6.0-test9 Aubin LaBrosse
2003-11-23 18:15 ` Zwane Mwaikambo
2003-11-23 18:55 ` Aubin LaBrosse [this message]
2003-11-23 22:35 ` Zwane Mwaikambo
2003-11-23 19:37 ` Dave Jones
2003-11-23 20:20 ` Aubin LaBrosse
2003-11-29 9:24 ` Tomasz Ciolek
2003-11-29 11:05 ` Dave Jones
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=1069613755.9574.68.camel@rain.rh.rit.edu \
--to=arl8778@rit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).