From: John L. C. <jl...@cf...> - 2000-09-26 15:34:18
|
On Tue, Sep 26, 2000 at 12:12:29AM -0700, David Paschal wrote: <snip><snip><snip> > That part is left over from the previous maintainers. The new > "make install" I added to the top-level directory doesn't even invoke > makefiles in subdirectories. By default, it installs the modules under > /usr/local/lib, which doesn't help make it accessible to modprobe. > Based on John Chmielewski's message from September 13, it sounds like it > could be moved to (or possibly symlinked in) /lib/modules/misc, but there's > still the problem that modprobe doesn't detect that ieee12844pp.o depends > on parport_probe, not just parport and parport_pc. My idea was to add a > dummy function in ieee12844pp.c which never got called but which made a > reference to a function in parport_probe (for example, parport_probe()). > Since you're working on this code at the moment could you try this out and > let me know if it fixes the problem (or I can try it myself later). If you do a modprobe -c, you will see the directories that are searched for modules. Besides directories under specific kernel versions, modprobe will also search specific directories under /lib/modules, if they exist. So I created /lib/modules/misc and moved the ieee12844 modules there. I would like to see the modules installed there instead of /usr/local/lib. Burkhard Kohl sent a message to this list explaining how to set up conf.modules, as a workaround, so the modules load. I modified it into two lines: above parport parport_pc below ieee12844 parport_probe John Chmielewski |