public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Mark Watts <m.watts@eris.qinetiq.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Via KT400 agpgart issues
Date: Thu, 14 Aug 2003 19:48:38 +0100	[thread overview]
Message-ID: <20030814184838.GB10901@redhat.com> (raw)
In-Reply-To: <200308141025.12747.m.watts@eris.qinetiq.com>

On Thu, Aug 14, 2003 at 10:25:12AM +0100, Mark Watts wrote:

 > Ok, I _am_ using the nVidia modules (on 2.4.21) but the fact that the agpgart 
 > driver can't sense my agp apature size is concerning... (its set to 256MB in 
 > the bios)
 > 
 > 0: nvidia: loading NVIDIA Linux x86 nvidia.o Kernel Module  1.0-4496  Wed Jul 
 > 16 19:03:09 PDT 2003
 > Linux agpgart interface v0.99 (c) Jeff Hartmann
 > agpgart: Maximum main memory to use for agp memory: 439M
 > agpgart: Detected Via Apollo Pro KT400 chipset
 > agpgart: unable to determine aperture size.
 > 0: NVRM: AGPGART: unable to retrieve symbol table
 > 
 > I'm running a GeForce FX 5600 128Mb with AGP 3.0 support enabled.
 > It seems to run ok, but its slower than the Ti 4200-4x I took out by a larger 
 > margin than it really should be (according to the benchmarks I've seen 
 > scattered through the internet.)
 > I'm also running with the Local APIC turned on (it doesnt seem to break 
 > anything).
 > 
 > Is anything actually broken or is this nothing to worry about?

Caused due to lack of AGP 3.x support in 2.4
See 2.6.0-test

		Dave

-- 
 Dave Jones     http://www.codemonkey.org.uk

  parent reply	other threads:[~2003-08-14 18:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-14  9:25 Via KT400 agpgart issues Mark Watts
2003-08-14 10:50 ` Rahul Karnik
2003-08-14 18:48 ` Dave Jones [this message]
2003-08-15  7:59   ` Mark Watts
2003-08-15 11:07     ` Dave Jones
2003-08-14 18:53 ` dleonard
2003-08-14 18:50   ` 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=20030814184838.GB10901@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.watts@eris.qinetiq.com \
    /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