All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Markus Hästbacka" <midian@ihme.org>
To: Alistair J Strachan <alistair@devzero.co.uk>
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Nforce2
Date: Tue, 09 Sep 2003 22:40:26 +0300	[thread overview]
Message-ID: <1063136426.3406.7.camel@midux> (raw)
In-Reply-To: <200309091801.17024.alistair@devzero.co.uk>

[-- Attachment #1: Type: text/plain, Size: 2396 bytes --]

Hello Alistair,

I've tested everything, I think. It just can't use AGP 4x. I tryed with
NvAGP 1 and 3. Here's the output in /var/log/XFree86.0.log:
[...snip...]
(**) NVIDIA(0): Option "NvAGP" "3"
(**) NVIDIA(0): Use of any AGP requested (try AGPGART, then try NVIDIA's
AGP)
[...snip...]
(WW) NVIDIA(0): Failed to verify AGP usage
[...snip...]
And I just noticed that 2.4 is not telling me the truth. The agp isn't
enbaled there either. I don't know anything to do anymore.
Looks like linux totally lacks support for my Mobo. *sigh*.

midian@midux:~$ uname -r
2.6.0-test5-mm1

NVRM version: NVIDIA Linux x86 nvidia.o Kernel Module  1.0-4496  Wed Jul
16 19:03:09 PDT 2003
GCC version:  gcc version 3.3.2 20030831 (Debian prerelease)

midian@midux:~$ cat /proc/driver/nvidia/agp/status
Status:          Disabled

midian@midux:~$ lspci
00:00.0 Host bridge: nVidia Corporation: Unknown device 01e0 (rev c1)
00:00.1 RAM memory: nVidia Corporation: Unknown device 01eb (rev c1)
00:00.2 RAM memory: nVidia Corporation: Unknown device 01ee (rev c1)
00:00.3 RAM memory: nVidia Corporation: Unknown device 01ed (rev c1)
00:00.4 RAM memory: nVidia Corporation: Unknown device 01ec (rev c1)
00:00.5 RAM memory: nVidia Corporation: Unknown device 01ef (rev c1)
00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev
a4)
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev
a4)
00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev
a4)
00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet
Controller (rev a1)
00:08.0 PCI bridge: nVidia Corporation: Unknown device 006c (rev a3)
00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
01:06.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev
07)
01:06.1 Input device controller: Creative Labs SB Live! MIDI/Game Port
(rev 07)
01:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
01:0d.0 FireWire (IEEE 1394): Lucent Microelectronics FW323 (rev 61)
02:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX
440] (rev a3)

Thanks.
-- 
----
Markus Hästbacka <midian@ihme.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-09-09 19:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09 13:34 Nforce2 Markus Hästbacka
2003-09-09 17:01 ` Nforce2 Alistair J Strachan
2003-09-09 19:40   ` Markus Hästbacka [this message]
2003-09-09 17:10 ` Nforce2 Rahul Karnik
2003-09-09 18:50   ` Nforce2 Markus Hästbacka
  -- strict thread matches above, loose matches on Subject: below --
2003-09-09 13:46 Nforce2 Jose Luis Alarcon Sanchez
2005-05-19  6:24 nForce2 Andrew Munday
2005-05-19  6:24 ` nForce2 Jean Delvare
2005-05-19  6:24 ` nForce2 Andrew Munday
2005-05-19  6:24 ` nForce2 Jean Delvare

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=1063136426.3406.7.camel@midux \
    --to=midian@ihme.org \
    --cc=alistair@devzero.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.