module strangeness with 2.4 kernels
This is odd. I've compiled a selection of the latest 2.4 kernels
(including ben's) but the kernel is not looking for modules in the
correct place.
For example, when I run with ben's kernel I can't load dmasound and
doing modprobe -c produces output something like this:
path[sound] = /lib/modules/2.4.18-benh/sound
.
.
.
Clearly that's why modprobe can't find anything! Because the modules
the directory referred to doesn't exist, instead the tree looks like
this:
/lib/modules/2.4.18-benh/
kernel/
drivers/
sound/
So, have I configured something wrong? Or is there a step I missed
out? or what?
Nic Ferrier
Reply to: