Date: Fri, 13 Aug 2004 14:42:11 -0400 From: Jason Andresen <jandrese@mitre.org> To: Mark Murray <markm@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: mem_range_attr_set undefined Message-ID: <411D0B83.5070405@mitre.org> In-Reply-To: <200408131751.i7DHpaBa055244@grimreaper.grondar.org> References: <200408131751.i7DHpaBa055244@grimreaper.grondar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Murray wrote: >Doug White writes: > > >>On Tue, 10 Aug 2004, Jason Andresen wrote: >> >> >> >>>I just upgraded from 5.2-RELEASE to 5.2-CURRENT as of Aug 9 and now the >>>NVidia kernel module doesn't want to load. I recompiled both my X >>>server and the module itself, but every time I try to kldload it I get: >>> >>>link_elf: symbol mem_range_attr_set undefined >>> >>>What did I do wrong? Thanks. >>> >>> >>Make sure you compile in the 'io' and 'mem' devices. >> >> > >Or just kldload the 'mem' device before you kldload the NVidia module. >The 'io' device has hothing to do with this. > > It wasn't good enough to load them as modules at boot time, I had to actually compile the mem device into the kernel to get this to work.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?411D0B83.5070405>