Can someone help with module loading ? I'm lost on this.
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Can someone help with module loading ? I'm lost on this.
I try to ' modprobe vfat ' and I am told " Can't locate module vfat". I do a ' modprobe -c ' to see where modprobe is looking for this module. I see this in the list : ' path[fs]=/lib/modules/fs ' .
So I create the subdirectory ' fs ' and place the file ' vfat.o ' in the directory ' /lib/modles/fs ' .
But I still get the same message.
Also, when I get this ironed out, should I auto load this module from ' rc.modules ' or should I make an entry in ' modules.conf ' to do this ? If this helps, something called " kmod " is loading modules on boot up.
all your modules should be (typically) in
/lib/modules/2.4.20/kernel/drivers
(where 2.4.20 is your kernel version number).
so there should be a /lib/modules/2.4.20/kernel/drivers/fs
and then maybe a vfat/vfat.o file in there somewhere...
if your not sure of your kernel's version number check with 'uname -r'.
rc.modules is the proper place to add the modprobe vfat line. And if after searching through /lib/modules/2.4.20/... and you still don't find the vfat.o check your kernel's config... it might be compiled into the kernel (or not at all).
Thanks for the reply. I'm pulling my hair out on this one. It makes me want to do the easy thing, and like you said compile everything directly into the kernel. But that won't teach me anything. I will need to know how to do this so that I don't have to recompile kernels all of the time just to get one piece of hardware working.
The output of ' insmod vfat ' is this :
/lib/modules/fs/vfat.o: couldn't find the kernel version the module was compiled for
Good information. I needed to know if I was going about this the right way.
But something just occured to me. It looks like I'm the dummy on this one. After looking at my ' .config ' file for the kernel that I built, I see that I compiled vfat into the kernel.
What sent me on this quest was seeing the message on boot that said something about not being able to load vfat for my fat32 partitions ( I have three, refered to in fstab as C,D,E ).
Now I still need to get this straight so that any modules that I may need to load (sound for instance) will work properly. I see that NVIDIA makes an entry in ' module.conf '. Is that a good place to load extra modules ? Or is the best way to use ' rc.modules ' ?
I also need to know why I get the message at boot. Who is asking for the vfat module to load ? (btw: hotplug is disabled in my kernel)
For the kernel question - yes I have compiled a new kernel recently. And from the looks of things, I have screwed something up as far as modules go.
put this in your modules.conf:
path=/lib/modules/`uname -r`
the `uname -r`, when run on the command line will output the running kernel version......so if you are running 2.4.20 this is what modprobe will see when it checks the modules.conf file:
path=/lib/modules/2.4.20
understand? backticks, the ` symbol, drops whatever to a shell to run it. you will see it in perl as well.
I can't thank you enough Terry. Thanks alot for your time. I think I get it now. And I better understand what is in the man pages now.
I don't want to take too much more of your time, but you have been very helpful so I'll ask one more question.
How do you alter disk permissions with mounted FAT32 volumes ? The problem I am having is that I cannot give ' rwx ' permissions to anyone but root. It does this in KDE when I put ticks in the appropriate boxes, and also if I do a ' chmod 777 ' at a prompt. It just ignores my changes, except for of course root.
Another thing is that KDE tells me that I can only share directories that are part of ' /home ' on the network. KDE tells me this even when I try to share folders that ARE in the /home directory. That's really confusing.
In the future you should start a new thread to make it easier for others to find answers.
1) Are you trying to change the permissions as a user other than root? If so, it matters how you mount the volume. You need to mount it as a particular user or particular group (uid,gid) if you want them to be able to modify things. Otherwise, root is the only one who can do so.
2) What version of KDE? What is the name of the tool you are using in KDE?
I hear you on the new post thing. I'm just being greedy I guess because I have your help at the moment.
I am root when I try to make the changes. I notice that root is the owner of the disk, and that UID and GID are not set.
If I set the UID and GID to some number, will I be able to use that in the smb.conf ? In other words, do I specify these numbers for a particular share ?
My KDE version is 3.1 (it's the one that comes with Slackware 9.0), and I am trying to change permissions by right-clicking on the folder that represents the mounted drive, lets say ' /D ' and going to properties.
This will mount the partition so that the users group owns it. You really need to read the mount man page, specifically the options. Check out the 'umask' option for fat. I have not used it but it might be helpful for you. This _might_ let you set a default mask for new files or something like that, similar to samba's 'create mode'.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.