public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff Nguyen" <jeff@aslab.com>
To: "Carl D. Blake" <carl@boeckeler.com>, <linux-kernel@vger.kernel.org>
Subject: Re: nforce2 and agpgart
Date: Mon, 23 Dec 2002 15:59:12 -0800	[thread overview]
Message-ID: <037301c2aadf$4aea4050$6502a8c0@jeff> (raw)
In-Reply-To: 1040683214.4447.7.camel@vulcan

Carl,

Are you using the onboard IDE controller for your hard disk?
If so, please check to see if DMA is enabled or not.

Jeff

----- Original Message -----
From: "Carl D. Blake" <carl@boeckeler.com>
To: <linux-kernel@vger.kernel.org>
Sent: Monday, December 23, 2002 2:40 PM
Subject: Re: nforce2 and agpgart


> On Mon, 2002-12-23 at 14:16, Bongani Hlope wrote:
> > On Mon, 2002-12-23 at 20:50, Carl D. Blake wrote:
> > > I'm having trouble getting agpgart support to work with an nforce2
> > > chipset.  Is this supported on any kernels?  I'm running a Redhat 7.1
> > > system with Redhat's 2.4.9-21 kernel.
> >
> > Try to use a newer kernel from Redhat, because that kernel was around
> > looong before nforce was released. IIRC support for nforce2 was added
> > around 2.4.19
> >
>
> I just upgraded to the 2.4.18 kernel provided by Redhat and it didn't
> make any difference.  The message I get in dmesg is:
>
> Linux agpgart interface v0.99 (c) Jeff Hartmann
> agpgart: Maximum main memory to use for agp memory: 439M
> agpgart: unsupported bridge
> agpgart: no supported devices found.
>
> You suggested trying 2.4.19, so I downloaded kernel 2.4.20 from
> kernel.org and compared its agp code (drivers/char/agp) with the code in
> 2.4.18.  There are a few differences - such as supporting AMD 8151 - but
> nothing that indicates improved support for agpgart on the nforce2
> chipset.  The changelog for 2.4.20 indicated some added support for the
> nforce2 chipset, but that seems to be support for the audio and network
> portions of the chipset, not agp.  I was able to incorporate the audio
> changes manually for kernel 2.4.18 by using Nvidia's patches, but I
> can't get agp to work.
>
> Any other suggestions?  Thanks for your help.
> > --
> > For future reference - don't anybody else try to send patches as vi
> > scripts, please. Yes, it's manly, but let's face it, so is
> > bungee-jumping with the cord tied to your testicles.
> >
> >                 -- Linus
> --
> Carl D. Blake
> Director of Engineering
> Boeckeler Instruments, Inc.
> 4650 S. Butterfield Dr.
> Tucson, AZ  85714
>
> Phone: 520-745-0001
> FAX: 520-745-0004
> email: carl@boeckeler.com
>
> .com
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>


  parent reply	other threads:[~2002-12-23 23:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-23 18:50 nforce2 and agpgart Carl D. Blake
2002-12-23 21:16 ` Bongani Hlope
2002-12-23 22:40   ` Carl D. Blake
2002-12-23 23:19     ` Bongani Hlope
2002-12-26 18:55       ` Carl D. Blake
2002-12-23 23:59     ` Jeff Nguyen [this message]
2002-12-26 18:55       ` Carl D. Blake
     [not found]       ` <1040928705.6372.27.camel@vulcan>
     [not found]         ` <086101c2ad18$46fea8b0$6502a8c0@jeff>
2002-12-26 20:09           ` Carl D. Blake

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='037301c2aadf$4aea4050$6502a8c0@jeff' \
    --to=jeff@aslab.com \
    --cc=carl@boeckeler.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox