Oops, this popped out of moderation a bit late because I sent it from the wrong address.
On Fri, Oct 20, 2006 at 09:19:16AM +0100, Brett Parker wrote:
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
I *think* this was probably my problem, I think using the /test kernel meant that my 'make install' didn;t put it in the right place. A later 'make install' put it in the right place though and I'm not quite sure what changed in the interim.
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.
But this *isn't* necessary when I reboot, the kernel somehow automagically finds that it needs the r1000 module and loads it. It's this that I find a bit disconcerting.
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.
It would appear that this is what happens by default with any distro, just do the required make and depmod and then "it just works", assuming that one's system is set up correctly for the given kernel (which mine wasn't quite).