From owner-freebsd-current@FreeBSD.ORG Mon Aug 16 18:26:30 2004 Return-Path: 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 85AB716A4CE for ; Mon, 16 Aug 2004 18:26:30 +0000 (GMT) Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.157.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0882A43D2F for ; Mon, 16 Aug 2004 18:26:30 +0000 (GMT) (envelope-from mark@grondar.org) Received: from storm.FreeBSD.org.uk (Ugrondar@localhost [127.0.0.1]) i7GIPEEr033964; Mon, 16 Aug 2004 19:25:14 +0100 (BST) (envelope-from mark@grondar.org) Received: (from Ugrondar@localhost)i7GIPER5033963; Mon, 16 Aug 2004 19:25:14 +0100 (BST) (envelope-from mark@grondar.org) X-Authentication-Warning: storm.FreeBSD.org.uk: Ugrondar set sender to mark@grondar.org using -f Received: from grondar.org (localhost [127.0.0.1])i7GIM5aa040437; Mon, 16 Aug 2004 19:22:05 +0100 (BST) (envelope-from mark@grondar.org) Message-Id: <200408161822.i7GIM5aa040437@grimreaper.grondar.org> To: Jason Andresen From: Mark Murray In-Reply-To: Your message of "Mon, 16 Aug 2004 10:03:04 EDT." <4120BE98.1030301@mitre.org> Date: Mon, 16 Aug 2004 19:22:04 +0100 Sender: mark@grondar.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Aug 2004 18:26:30 -0000 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? M -- Mark Murray iumop ap!sdn w,I idlaH