From: Chris M. <cm...@in...> - 2000-08-22 22:16:22
|
Andy Isaacson wrote: > > On Tue, Aug 22, 2000 at 03:43:49PM -0600, Chris Malley wrote: > > Forgive my ignorance, by I don't know what "module versioning" is. > > My kernel (2.2.16-3) does support kernel modules, but how do I > > determine if it supports module versions? > > 'head /proc/ksyms' is the easiest way I've found. If it looks like > d8023a58 mixer_devs_Rsmp_aa8cbba2 [sound] > ^^^^^^^^ then you've got module versioning. > If it looks like > c888f140 sr_template [sr_mod] > ^^ nothing there! then you've got module > versions turned off. Looks like I have versioning turned on: # head /proc/ksyms d085081c lockd_up_Rf6933c48 [lockd] d0850910 lockd_down_Ra7b91a7b [lockd] ... (If someone has time to send me a reference to 'module versioning' off-list, I'd appreciate it. I'd like to know what it is.) [...] > make -f Makefile.linux CFLAGS="-DKILLFASYNCHASTHREEPARAMETERS" > > except that might not be quite right either -- but it's closer than > the above. You might want to edit Makefile.linux to add this flag > instead of passing it on the command line. Thanks, I modified the Makefile. Then I noticed that the unmodified Makefile handles -DKILLFASYNCHASTHREEPARAMETERS; it's automatically passed to cc if kill_fasync() has 3 args. The prototype for kill_fasync() in my linux/fs.h does indeed have 3 args, so I guess the Makefile is doing the correct thing. In any case: # insmod r128 Using /lib/modules/2.2.16-3/misc/r128.o /lib/modules/2.2.16-3/misc/r128.o: unresolved symbol kill_fasync_Rb2b77a95 Any other ideas? Does everyone have to go through this to get DRI working? -Chris -- Chris Malley Email: cm...@in... Interact-TV Web: http://www.interact-tv.com 2503 Walnut Street Suite 100 Phone: 720-406-9399 Boulder, CO 80302 USA FAX: 720-406-8424 |