public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: detlef.grittner@t-online.de (Detlef Grittner)
To: linux-kernel@vger.kernel.org
Subject: kernel-2.6.1-rc1-bk6: too many northbridges for AGP
Date: Mon, 05 Jan 2004 15:45:05 +0100	[thread overview]
Message-ID: <1073313905.6180.10.camel@linux.local> (raw)

Hi all,

I have compiled and installed the kernel-2.6.1-rc1-bk6 on a x32_64
architecture, i.e. an AMD Athlon64 3200+ processor.
In the dmesg I can see the following messages:

agpgart: Detected AGP bridge 0
agpgart: Too many northbridges for AGP

And AGP doesn't work after this. The northbridge chipset is a VIA K8T800
(southbridge is VT8237). The video card is an NVidia 5900 with AGP8x.

I think I've read in the NVidia newsgroup that this is a known bug and
would be fixed in 2.6.0, but now I'm not sure: Is this a known bug or is
it a new bug?

Detlef




             reply	other threads:[~2004-01-05 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-05 14:45 Detlef Grittner [this message]
2004-01-05 18:01 ` kernel-2.6.1-rc1-bk6: too many northbridges for AGP 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=1073313905.6180.10.camel@linux.local \
    --to=detlef.grittner@t-online.de \
    --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