On Tue, Oct 17, 2006 at 10:07:40PM +0100, chris@isbd.co.uk wrote:
However I'm still unclear how it's *supposed* to work.
I have compiled the new module and have produced a new driver called r1000.ko.
The instructions say just:-
make clean modules (as root or with sudo) make install depmod -aWhich is a fat lot of good as it doesn't actually make the module do anything.
The make install should have copied it in the /lib/modules/<kernel-version>/someplace, try doing: find /lib/modules -name r1000.ko
And see where it put it. You should also be able to just use modprobe r1000 To load the module, assuming that it has actually put it in the right place in the make install.
If I do:- insmod ./src/r1000.ko
then the module works, but of course it only works if I happen to be in the directory where I unpacked and built the module.
The "make install" doesn't appear to have put the module anywhere sensible so that I can 'run' it at startup.
How do I find out how to actually get the module to be part of my installation and run when I start the system up? I can muddle my way there no doubt but surely there should be a relatively easy way to find out.
Sorry about the rant but every time I [re]-install Linux I have this stupid game with modules.
This is where debian's module-assisstant is really nice. You end up with a packaged version of the module for the current kernel, you install the package and it just works.