From owner-freebsd-current@FreeBSD.ORG  Fri Aug 29 06:48:41 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B9A0216A4BF
	for <current@freebsd.org>; Fri, 29 Aug 2003 06:48:41 -0700 (PDT)
Received: from tao.xtaz.co.uk (82-32-29-13.cable.ubr04.azte.blueyonder.co.uk
	[82.32.29.13])	by mx1.FreeBSD.org (Postfix) with ESMTP id 7B69243F85
	for <current@freebsd.org>; Fri, 29 Aug 2003 06:48:40 -0700 (PDT)
	(envelope-from matt@xtaz.co.uk)
Received: from webmail.xtaz.co.uk (localhost [127.0.0.1])
	by tao.xtaz.co.uk (Postfix) with SMTP
	id 122EC900B5; Fri, 29 Aug 2003 14:48:39 +0100 (BST)
MIME-Version: 1.0
X-Mailer: V-webmail 1.5.0 ( http://www.v-webmail.co.uk/ )
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-ID: <hkdvp3.a4ect5@webmail.xtaz.co.uk>
In-Reply-To: <3F4F57FA.4030605@techfak.uni-bielefeld.de>
References: <200308281540.h7SFeUV22668@accms33.physik.rwth-aachen.de>
	<20030828201301.GA14685@gattaca.yadt.co.uk>
	<3F4F57FA.4030605@techfak.uni-bielefeld.de>
Date: Fri, 29 Aug 2003 14:48:39 +0100
From: "Matt" <matt@xtaz.co.uk>
To: Hendrik Hasenbein <hhasenbe@techfak.uni-bielefeld.de>
cc: current@freebsd.org
Subject: Re: nvidia.ko freezes system in -current
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Aug 2003 13:48:41 -0000

Hendrik Hasenbein <hhasenbe@techfak.uni-bielefeld.de> wrote:

> 
> Does somebody use the nvidia driver together with a nforce2 chipset?
> The driver won't enable the agp port:
> 
> nvidia0: <Unknown> at device 0.1 on pci0
> nvidia0: Unable to enable PCI busmastering.
> device_probe_and_attach: nvidia0 attach returned 6
> 
> Any ideas?
> 
> Hendrik

Yes I have an nforce2 motherboard and use it. I get the same messages but mine
does detect it and work fine after all the messages as you can see below.
These messages never used to be printed on the older nvidia port but since it
was updated I see this every time I kldload it. Though as it eventually
attaches and works I have never really cared much about it.

Aug 25 09:54:01 neo kernel: nvidia0: <Unknown> at device 0.1 on pci0
Aug 25 09:54:01 neo kernel: nvidia0: Unable to enable PCI busmastering.
Aug 25 09:54:01 neo kernel: device_probe_and_attach: nvidia0 attach returned 6
Aug 25 09:54:01 neo kernel: nvidia0: <Unknown> at device 0.2 on pci0
Aug 25 09:54:01 neo kernel: nvidia0: Unable to enable PCI busmastering.
Aug 25 09:54:01 neo kernel: device_probe_and_attach: nvidia0 attach returned 6
Aug 25 09:54:01 neo kernel: nvidia0: <Unknown> at device 0.3 on pci0
Aug 25 09:54:01 neo kernel: nvidia0: Unable to enable PCI busmastering.
Aug 25 09:54:01 neo kernel: device_probe_and_attach: nvidia0 attach returned 6
Aug 25 09:54:01 neo kernel: nvidia0: <Unknown> port
0x2480-0x249f,0x24b0-0x24bf,0x24a0-0x24af irq 11 at device 1.1 on pci0
Aug 25 09:54:01 neo kernel: nvidia0: Unable to enable PCI busmastering.
Aug 25 09:54:01 neo kernel: device_probe_and_attach: nvidia0 attach returned 6
Aug 25 09:54:01 neo kernel: nvidia0: <GeForce4 MX 420> mem
0xfc200000-0xfc27ffff,0xf8000000-0xfbffffff,0xfd000000-0xfdffffff irq 5 at
device 0.0 on pci1

--
email: matt@xtaz.co.uk - web: http://xtaz.co.uk/
Hardware, n.: The parts of a computer system that can be kicked.