Ah! There is one thing I've noticed:
only works with modules sited in /lib/modules/$YOUR KERNEL VERSION/modules.dep
. Even if you're right there inside the directory where realtek.ko is situated.
1. Without going too deep into these details, you may try this version of your command:
using in this case full path to the directory, where the module , and not the link, really is.
2. There's one more thing to mention dealing with custom modules in "unusual situations": instead of `modprobe
` command you can try `insmod
As I understand it, the `modprobe` command is a "more safe" one in that it WON'T load the module if it is doubtful about its source. But if YOU are not doubtful about your module and want to load it right here right now "at your own risk" (from the viewpoint of the system, which in this case doesn't recognize your module for its own), then the `insmod` command will do the thing. At least, you will see if it works.
Insmod doesn't give feedback, whether it was successful or not. So you'll need to do use `dmesg` command to see, if your networking card appeared on the system after loading the module.
3. Then again, does this module depend on other ones? You must see the source code for this module to see the dependencies (you need not be a code guru to see this either). Or, if the old kernel modules directory is still there, see the modules.dep file found therein for the dependencies.
For example, some Realtek NIC drivers depend on mii.ko
to load properly (meaning this one must be loaded first). So perhaps you must first do
as this one must be well known to the system and usually exists in default kernel configurations, since RealTek chip based NICs are widely used.
Then after loading this one you can try again with your custom driver.
Here is how it looks with my two RealTek based NICs (part of my lsmod output):
8139too 25075 0
r8169 31809 0
mii 3578 2 8139too,r8169
So you see, there are two versions of RealTek cards, both need the mii.ko driver to load. Perhaps yours need this one, too?
And in ANY CASE,reading of manual pages for modprobe
is a MUST. That sure will help to get you out of the pit of ignorance regarding this process
Things described here are a "dirty fix" and can be tolerated only in case you're absolutely sure about the source of your "vendor driver".