On Tue, Nov 20, 2001 at 02:24:37PM -0800, Peter Jay Salzman wrote: > begin: Micah Cowan <[EMAIL PROTECTED]> quote > > or in the kernel docs (admittedly outdated; the kernel docs still talk > > about kerneld, with a simple note at the top saying that kerneld is no > > longer supported). > > modprobe, insmod rmmod and family have nothing to do with the kernel. they > are user space programs provided to the distibution for use with the linux > kernel. usually in a package called "modutils".
Right. But the design of modutils obviously coincided with the design of the modular kernel - at least the concepts. Anyway, the document I was talking about is modules.txt in the kernel docs directory. At any rate, it probably isn't an issue with the modutils, but more likely (to me) a kernel or kmod issue, since it doesn't appear that the kernel detects that it *needs* a module at all. I'm currently suspicious that the new event-driven input interface must do some "special" stuff behind the scenes, that ends up affecting whether the kernel realizes you've just tried to read from a device file. <snip> > your previous email got snipped -- it sounds like a bad modules.conf > configuration. can you modprobe the driver in successfully? Yes, I can. And, even when I remove the relevant entries from modules.conf, I still don't get a "couldn't find module char-major-13" style message anywhere. At this point, I suspect I'll be doing some kernel-source reading if I still want to know why. It could even be some sort of bug they've fixed by now (my home machine's currently 2.4.8). Thanks for your time, Pete Micah
