Date: Tue, 17 Aug 2004 02:02:52 +0200 From: Cedric Tabary <tabary@efrei.fr> To: Mark Murray <markm@FreeBSD.ORG> Cc: freebsd-current@FreeBSD.ORG Subject: Re: mem_range_attr_set undefined Message-ID: <20040817000252.GE37300@efrei.fr> In-Reply-To: <200408161822.i7GIM5aa040437@grimreaper.grondar.org> References: <4120BE98.1030301@mitre.org> <200408161822.i7GIM5aa040437@grimreaper.grondar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040817000252.GE37300>