Date: Tue, 17 Aug 2004 10:13:52 -0400 From: Jason Andresen <jandrese@mitre.org> To: Robert Watson <rwatson@freebsd.org> Cc: Cedric Tabary <tabary@efrei.fr> Subject: Re: mem_range_attr_set undefined Message-ID: <412212A0.2040502@mitre.org> In-Reply-To: <Pine.NEB.3.96L.1040817095051.13561A-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1040817095051.13561A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote: >On Tue, 17 Aug 2004, Cedric Tabary wrote: > > > >>>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 ... >> >> > >The mem kld will need to explicitly symbols required by other modules >using the EXPORT_SYMS line in its Makefile. So try adding: > > EXPORT_SYMS= mem_range_attr_set > >to the module Makefile for mem, rebuilding, reloading, and adding >additional symbols until it works? > > Sure, I can try this. Where is the Makefile for the mem device?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?412212A0.2040502>