public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Jonathan Morton <chromi@chromatix.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: agpgart failure on KT400
Date: Thu, 14 Aug 2003 19:47:41 +0100	[thread overview]
Message-ID: <20030814184741.GA10901@redhat.com> (raw)
In-Reply-To: <779ACC8A-CE86-11D7-A88B-003065664B7C@chromatix.demon.co.uk>

On Thu, Aug 14, 2003 at 07:38:15PM +0100, Jonathan Morton wrote:
 > I recently upgraded to a m/board using the KT400 chipset - specifically 
 > an Abit KD7-G - and now find that I can't load agpgart.  The relevant 
 > kernel messages:
 > 
 > agpgart: Maximum main memory to use for agp memory: 941M
 > agpgart: Detected Via Apollo Pro KT400 chipset
 > agpgart: unable to determine aperture size.
 > 
 > This results in my inability to load XFree86, using the proprietary ATI 
 > drivers, which appear to require AGP support.  Note that the same 
 > problem appears using ATI's "internal agpgart module", just to show I 
 > know the difference.  The regular XFree86 drivers probably work without 
 > AGP - I haven't bothered trying yet.
 > 
 > NB: I tried sending this to Jeff Hartmann, but his address at 
 > precisioninsight.com is dead.  Please CC me, I'm not subscribed to the 
 > list.  Better still, refer me to someone who actually knows what to do 
 > about it.
 > 
 > The BIOS is set up for either a 256MB or 64MB AGP aperture - whichever 
 > of the two settings makes no difference.  The video card is a Radeon 
 > 9700 Pro, 128MB.  The kernel configuration includes ACPI and 
 > HIGHMEM-4GB support, if that is at all relevant.
 > 
 > This problem is identically present in 2.4.21 and 2.4.22-rc2.

For 2.4, you're stuck. It needs AGP3 support. The KT400 stuff in
2.4 only works if you shove an AGP2.x gfx card in the slot.
As soon as you put a 3.x capable card in there the chipset changes
mode, and as there's no AGP3 support in 2.4 yet, you're pooched.

The code in 2.6test should work, but before you (or anyone else) asks,
no, it won't work without a bit of bending in 2.4, and I don't have
a backport, or plans to do so any time soon.

Sorry,

		Dave

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

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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-14 18:38 agpgart failure on KT400 Jonathan Morton
2003-08-14 18:47 ` Dave Jones [this message]
2003-08-14 19:00   ` Jonathan Morton
2003-08-15  0:47   ` Robert Toole
2003-08-15  1:42     ` Jonathan Morton
2003-08-15  4:47       ` Greg KH
2003-08-15  4:55         ` Jonathan Morton
2003-08-18 21:21           ` Greg KH
2003-08-15 10:57       ` Dave Jones
2003-08-15 11:40         ` Christoph Hellwig
2003-08-15 11:59           ` Dave Jones
     [not found] <200308150934.57207.tlee5794@rushmore.com>
2003-08-15 16:02 ` Jonathan Morton

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=20030814184741.GA10901@redhat.com \
    --to=davej@redhat.com \
    --cc=chromi@chromatix.demon.co.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox