Re: mem_range_attr_set undefined
From: Jason Andresen (jandrese_at_mitre.org)
Date: 08/17/04
- Previous message: Daniel Eriksson: "/var/run/dmesg.boot not complete"
- In reply to: Robert Watson: "Re: mem_range_attr_set undefined"
- Next in thread: Robert Watson: "Re: mem_range_attr_set undefined"
- Reply: Robert Watson: "Re: mem_range_attr_set undefined"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 17 Aug 2004 10:13:52 -0400 To: Robert Watson <rwatson@freebsd.org>
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?
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Daniel Eriksson: "/var/run/dmesg.boot not complete"
- In reply to: Robert Watson: "Re: mem_range_attr_set undefined"
- Next in thread: Robert Watson: "Re: mem_range_attr_set undefined"
- Reply: Robert Watson: "Re: mem_range_attr_set undefined"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|