Etch continue loading old network card driver after new driver installation
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Etch continue loading old network card driver after new driver installation
Hi, I downloaded a new version (3.5.17) for my network card (the file is called e100), I compiled the module and added using modprobe e100 and still, everytime the PC starts Debian loads the old driver version (3.5.10), I see that doing a dmesg.
And if I do a lsmod cuz the size of the modules are different, the new version is bigger
If a remove that module (the old version) with modprobe -r e100 and load the newone (with modprobe e100) the new module is loaded, but when I restart the PC, Debian loads the old driver version again.
I even deleted the old e100.ko file from /lib/modules/2.6.18-custom/kernel/drivers/net cuz the new e100.ko file got installed at /lib/modules/2.6.18-custom/kernel/drivers/net/e100
modprobe only loads and unloads modules from the currently running kernel, it does not make any changes to the actual system configuration.
To replace the old module with the new one, you first need to delete the old module from the proper directory under /lib/modules. Use uname -r to determine the kernel release you are running and therefore figure out which directory you need to go into. After you have deleted the proper .ko, replace it with the new .ko, and run "depmod -a". This will cause the system to rebuild it's database of kernel modules, which should then cause it to load the new module properly.
modprobe -r e100
insmod /lib/modules/2.6.18-custom/kernel/drivers/net/e100.ko (not sure of the format, could be without the .ko)
dpkg-reconfigure linux-image-`uname -r`
Probably that your initramfs still contains the old driver, so it needs to be regenerated.
When reconfiguring the linux kernel, I expect that it will call mkinitramfs which should copy your running configuration to the udev one.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.