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.
I added these modules to /etc/modprobe.d and upon reboot, got a massive amount of errors. When I use to load the modules manually, there was no issue. So it tells me that I have misconfigured when I need to insert the module to be loaded as part of the kernel.
Anyone knows what I 'should' be configuring to get this to work?
I'm using Ubuntu and on my system /etc/modprobe.d is a directory. I usually put modules that need to be loaded in /etc/modules with just the module name.
On your system is modprobe.d a file? What system do you use?
I'm using Ubuntu and on my system /etc/modprobe.d is a directory. I usually put modules that need to be loaded in /etc/modules with just the module name.
On your system is modprobe.d a file? What system do you use?
I use centos 5.2
And yes you are right, modprobe.d is a directory, i also have a file in etc called modprobe.conf
Are you able to tell me how you store these modules in modprobe.d directory?
Are you able to tell me how you store these modules in modprobe.d directory?
No, I don't know centos. If there is a file /etc/modules, then you can put the module name in that file. But I don't know how centos works; so they may not use that file for loading modules.
You don't store modules there. You create a file with the same entry that would go in modprobe.conf. It doesn't really matter which you do.
e.g.: cat /etc/modprobe.d/nvidia
options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0660
Debian is probably different. Do you have a file that lists the modules to load at boot time? On SuSE, there is /etc/sysconfig/kernel where you can add the kernel modules to load in a variable. I think that debian may have a similar file.
Manually load the modules and look at them with lsmod and modinfo to see which are prerequisites of the others. I wonder if the order you are loading them is important or if your modprobe.conf entries need to indicate that. Also try running "sudo /sbin/depmod -a" in case that needs updating.
Sorry, I misread. I don't know where I got the idea that you are using debian.
If you look in /lib/modules/$(uname -r)/modules.dep you may see a line such as:
/lib/modules/2.6.27.5-117.fc10.x86_64/kernel/net/netfilter/nf_conntrack_pptp.ko: /lib/modules/2.6.27.5-117.fc10.x86_64/kernel/net/netfilter/nf_conntrack_proto_gre.ko
The dependencies are loaded right to left. If modules.dep isn't up to date it may not have the dependency info and cause errors if modules are loaded in the wrong order. What were the errors you were seeing? Another possibility is if you are missing a needed parameter in the modprobe.conf entry. However, I didn't find any parameters when I used modinfo.
You could try running modprobe with the -nv option. -n (dry run) -v (verbose) to load the modules. Also, what are the error messages you were seeing?
Sorry, I misread. I don't know where I got the idea that you are using debian.
If you look in /lib/modules/$(uname -r)/modules.dep you may see a line such as:
/lib/modules/2.6.27.5-117.fc10.x86_64/kernel/net/netfilter/nf_conntrack_pptp.ko: /lib/modules/2.6.27.5-117.fc10.x86_64/kernel/net/netfilter/nf_conntrack_proto_gre.ko
The dependencies are loaded right to left. If modules.dep isn't up to date it may not have the dependency info and cause errors if modules are loaded in the wrong order. What were the errors you were seeing? Another possibility is if you are missing a needed parameter in the modprobe.conf entry. However, I didn't find any parameters when I used modinfo.
You could try running modprobe with the -nv option. -n (dry run) -v (verbose) to load the modules. Also, what are the error messages you were seeing?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.