All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrew S. Johnson" <andy@asjohnson.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DRM, radeon, and X 4.3
Date: Thu, 17 Jul 2003 21:36:56 -0500	[thread overview]
Message-ID: <200307172136.56019.andy@asjohnson.com> (raw)
In-Reply-To: <20030717172625.GA16502@suse.de>

On Thursday 17 July 2003 12:26 pm, Dave Jones wrote:
> On Thu, Jul 17, 2003 at 05:39:25AM -0500, Andrew S. Johnson wrote:
>  > I start X but it says DRM is disabled, even though the
>  > radeon and agpgart modules are loaded.  Here is the dmesg tail:
>  > 
>  > Linux agpgart interface v0.100 (c) Dave Jones
>  > [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 1929 using kernel context 0
>  > 
>  > There is something X doesn't like.  How do I fix this?
> 
> Looks like there isn't an agp chipset module also loaded
> (via-agp.o, intel-agp.o etc...)
> 
> You should have additional text after the first AGP line.
> 
> 		Dave

In the 2.4 kernels, the chipset was compiled in with the agpgart
module.  Now they are separate.  So, yes, modprobe via-agp
did the trick.

How can get the modprobe.conf file to load this module after
agpgart and not crash the system?  My attempts to make this
work using the install command example from the manpage
have been generally disasterous.

Thanks,

Andy Johnson



  reply	other threads:[~2003-07-18  2:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17 10:39 DRM, radeon, and X 4.3 Andrew S. Johnson
2003-07-17 13:20 ` Damian Kolkowski
2003-07-17 17:26 ` Dave Jones
2003-07-18  2:36   ` Andrew S. Johnson [this message]
2003-07-18 12:55   ` Alan Cox
2003-07-18 14:08     ` Rahul Karnik
2003-07-19 14:48       ` Andrew S. Johnson

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=200307172136.56019.andy@asjohnson.com \
    --to=andy@asjohnson.com \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.