On Tue, Oct 17, 2006 at 09:54:45PM +0100, cl@isbd.net wrote:
Well I thought I had modules sussed but apparently not.
A couple of days ago I compiled the module for my RTL8168 Gigabit ethernet interfaces and it worked fine. I did what the README said and it all worked.
Now it doesn't work any more and my system denies all knowledge of the r1000.ko module.
Why are modules so ?^!$%^"$%&^ recalcitrant?
How do I get it to work now? All the 'bits' must be there but none of the module commands give me any help to find them.
Hheellpp!!
Sorry to answer my own question (partly anyway) but I have it working now.
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 -a
Which is a fat lot of good as it doesn't actually make the module do anything.
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.