From owner-freebsd-current@FreeBSD.ORG  Tue Aug 17 00:02:58 2004
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 804AA16A4D1; Tue, 17 Aug 2004 00:02:58 +0000 (GMT)
Received: from angel.grumly.eu.org (angel.grumly.eu.org [193.138.90.69])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0B6AE43D1D; Tue, 17 Aug 2004 00:02:58 +0000 (GMT)
	(envelope-from ced@grumly.eu.org)
Received: by angel.grumly.eu.org (Postfix, from userid 1001)
	id 4BE4AFF5E; Tue, 17 Aug 2004 02:02:52 +0200 (CEST)
Date: Tue, 17 Aug 2004 02:02:52 +0200
From: Cedric Tabary <tabary@efrei.fr>
To: Mark Murray <markm@FreeBSD.ORG>
Message-ID: <20040817000252.GE37300@efrei.fr>
References: <4120BE98.1030301@mitre.org>
	<200408161822.i7GIM5aa040437@grimreaper.grondar.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <200408161822.i7GIM5aa040437@grimreaper.grondar.org>
X-Mailman-Approved-At: Tue, 17 Aug 2004 11:55:45 +0000
cc: freebsd-current@FreeBSD.ORG
Subject: Re: mem_range_attr_set undefined
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: Tue, 17 Aug 2004 00:02:58 -0000

On 16/08/2004 19:22, Mark Murray wrote:
> Jason Andresen writes:
> > Mark Murray wrote:
> > >Jason Andresen writes:
> > >
> > >>>Make sure you compile in the 'io' and 'mem' devices.
> > >>>
> > >>Oh, I was loading them as modules.  That's probably it.
> > >>
> > >
> > >That's crazy. Loading as modules or building them in would have
> > >had the same result here. Did you cvsup between builds or anything?
> > >
> > 
> > Nope.  Was the fact that I was loading them as modules fairly late in 
> > the boot cycle (right before the Nvidia driver module was loaded) 
> > instead of in the boot loader itself perhaps the problem?
> 
> If it is, its a bug. Loading is loading.
> 
> Can you please try this really pedantically and report back?

I had exactly the same problem with nvidia driver compiled from ports
with default options except -DWITHOUT_LINUX.

kldload mem
kldload io (needed by xorg)
kldload nvidia -> failed (mem_range_attr_set undefined)

I had to compile 'device mem' into kernel

note 1: I did not try loading mem at the boot loader stage
note 2: I did not try the new release of nvidia driver

Hope this helps ...

Cédric Tabary