public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Aune <faune@stud.ntnu.no>
To: linux-kernel@vger.kernel.org
Subject: nvidia nforce3 support
Date: Tue, 27 Jan 2004 15:56:39 +0100	[thread overview]
Message-ID: <200401271556.40135.faune@stud.ntnu.no> (raw)

Hello,

What is the status for nforce3 support in 2.4 and 2.6? Ive found a patch from 
google dating all the way back in nov 2003, but it doesnt seem like its been 
applied. FYR here is the google search link:

http://groups.google.com/groups?q=nforce3
+linux&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=JSef.Wi.19%40gated-at.bofh.it&rnum=1

When trying the agpgart and nvidia_agp module on my nforce3 system, I get this 
message in dmesg:

agpgart: Detected an NVIDIA nForce/nForce2 chipset, but could not find the 
secondary devices.

Right now Im using 2.6.2-rc2-mm2, but 2.4.24 also give the same message. What 
is this "secondary devices" it cant find? Is this related to an unsupported 
AGP card? (Im using an Creative ATI Radeon 9200SE, and I cant enable direct 
rendering - only been able to use X version 4.3.99.902 and its built-in 
driver.)

I'll be happy to provide DeviceIDs and test patches, if someone needs it.

Thank you.


                 reply	other threads:[~2004-01-27 15:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200401271556.40135.faune@stud.ntnu.no \
    --to=faune@stud.ntnu.no \
    --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