Sponsored Content
Operating Systems Linux SuSE How do I load kernel modules so BestCrypt will work Post 58143 by CTroxtell21 on Sunday 14th of November 2004 07:22:47 PM
Old 11-14-2004
As you can see below I tryed the #insmod but for some reason I don't know how to use it or something but it keeps throwing back an error. With modprobe it don't give an error but it still gives an error on trying to run bctool. Am I using these commands right and do I need to install just the module I need to use like blowfish? I done a #man modprobe and noticed this:

modprobe looks in the module directory /lib/modules/?uname -r? for all the modules and other files, except for the optional /etc/modprobe.conf or /etc/modprobe.d (see modprobe.conf(5)).
I checked but there is no such directory or file in /lib/modules/ there is just the 2.6.8-24-default, precompiled and scripts folder in here.

linux:/etc # modprobe cryptoloop
linux:/home/chris/Desktop # insmod blowfish
insmod: can't read 'blowfish': No such file or directory
linux:/home/chris/Desktop # modprobe blowfish
linux:/home/chris/Desktop # bctool
Kernel modules not loaded

Last edited by CTroxtell21; 11-14-2004 at 08:28 PM..
 

9 More Discussions You Might Find Interesting

1. HP-UX

Information about kernel modules

Hi all, what do kernel modules libaudit, klog and strlog do? Specifically I want to determine if it was possible for us to determine if kernel level auditing is enabled at all? regards (0 Replies)
Discussion started by: slash_blog
0 Replies

2. Programming

HELP!!: CPU resource allocation between kernel modules and user mode process

Hi,all: I run my program which consists of one kernel module and one user mode process on a dual core server. The problem here is the kernel module consumes 100% of one core while the user mode process only consumes 10% of the other core, is there any solution that I can assign some computing... (1 Reply)
Discussion started by: neyshule
1 Replies

3. UNIX for Advanced & Expert Users

Kernel Modules Not geting built

I installed in VM the Mandriva Linux with 2.6.27 kernel. But presently when I fire make the modules .ko does not get built. I get the following output on firing command in the kernel module folder. $ make Building first_driver.c ... make: Entering directory... (1 Reply)
Discussion started by: rupeshkp728
1 Replies

4. Programming

Debugging Linux Kernel Modules

I am aware of debugging linux applications using gdb and ddd. Now I have written a simple kernel module having init_module, exit _module and some functions for tasklets and workqueues. I want to debug these kernel modules like I used to debug applications setting breakpoints etc. How can I debug... (1 Reply)
Discussion started by: rupeshkp728
1 Replies

5. Emergency UNIX and Linux Support

Linux: passing parameters to kernel modules

Hi, I need to set qlogic qla2xxx parameters in /etc/modprobe.conf (Oracle Linux Server release 5.7, almost equal to RedHat 5.7) two questions: how can I pass this parameters to the module while it is loaded (fibre channel luns are in use), if possible at all and how can I check the... (3 Replies)
Discussion started by: funksen
3 Replies

6. UNIX for Dummies Questions & Answers

Linux kernel modules makefiles doubts

This query is regarding the makefiles of linux kernel modules. I saw at some sites on net it is suggesting to include the following path: KERNEL_SOURCE := /usr/src/linux... while at some places it is askibg to include /lib/modules path: KERNEL_SOURCE := /lib/modules/2.6.27-7-generic/build... (0 Replies)
Discussion started by: rupeshkp728
0 Replies

7. Hardware

Linux Kernel Modules

Hey everyone. I have a question, doing an lsmod gives me a list of all the loaded modules for my system. But how did they know to load? my /etc/modules files is empty, so how did these modules know to load themselves on boot time? If I were to take this hard drive to another computer with a... (6 Replies)
Discussion started by: Lost in Cyberia
6 Replies

8. Linux

Disable loading kernel modules

Hi, I am running CentOS 6.5 and I want to remove auto loading 8021q and garp modules, but there are no configure files in /etc/modprobe.d define bot modules. I even added both module names to /etc/modprobe.d/blacklist.conf, both of them are still loaded after the reboot. How can I disable... (2 Replies)
Discussion started by: hce
2 Replies

9. UNIX for Beginners Questions & Answers

Missing Modules After Compiling Kernel

I'm a little embarrassed after all these years I've never really successfully compiled my own kernel. I used this guide to make the following files: linux-headers-5.1.9_5.1.9-1_amd64.deb linux-image-5.1.9_5.1.9-1_amd64.deb linux-libc-dev_5.1.9-1_amd64.deb When I first booted into this... (4 Replies)
Discussion started by: Azrael
4 Replies
modprobe(8)						      System Manager's Manual						       modprobe(8)

NAME
modprobe -- program to add and remove modules from the Linux Kernel SYNOPSIS
modprobe [-v] [-V] [-C config-file] [-n] [-i] [-q] [-b] [modulename] [module parameters ...] modprobe [-r] [-v] [-n] [-i] [modulename ...] modprobe [-l] [-t dirname] [wildcard] modprobe [-c] modprobe [--dump-modversions] [filename] Description modprobe intelligently adds or removes a module from the Linux kernel: note that for convenience, there is no difference between _ and - in module names (automatic underscore conversion is performed). modprobe looks in the module directory /lib/modules/`uname -r` for all the modules and other files, except for the optional /etc/modprobe.conf configuration file and /etc/modprobe.d directory (see mod- probe.conf(5)). modprobe will also use module options specified on the kernel command line in the form of <module>.<option>. Note that unlike in 2.4 series Linux kernels (which are not supported by this tool) this version of modprobe does not do anything to the module itself: the work of resolving symbols and understanding parameters is done inside the kernel. So module failure is sometimes accom- panied by a kernel message: see dmesg(8). modprobe expects an up-to-date modules.dep.bin file (or fallback human readable modules.dep file), as generated by the corresponding depmod utility shipped along with modprobe (see depmod(8)). This file lists what other modules each module needs (if any), and modprobe uses this to add or remove these dependencies automatically. If any arguments are given after the modulename, they are passed to the kernel (in addition to any options listed in the configuration file). OPTIONS
-a --all Insert all module names on the command line. -b --use-blacklist This option causes modprobe to apply the blacklist commands in the configuration files (if any) to module names as well. It is usually used by udev(7). -C --config This option overrides the default configuration directory/file (/etc/modprobe.d or /etc/modprobe.conf). This option is passed through install or remove commands to other modprobe commands in the MODPROBE_OPTIONS environment variable. -c --showconfig Dump out the effective configuration from the config directory and exit. --dump-modversions Print out a list of module versioning information required by a module. This option is commonly used by distributions in order to package up a Linux kernel module using module versioning deps. -d --dirname Directory where modules can be found, /lib/modules/RELEASE by default. --first-time Normally, modprobe will succeed (and do nothing) if told to insert a module which is already present or to remove a module which isn't present. This is ideal for simple scripts; however, more complicated scripts often want to know whether modprobe really did something: this option makes modprobe fail in the case that it actually didn't do anything. --force-vermagic Every module contains a small string containing important information, such as the kernel and compiler versions. If a module fails to load and the kernel complains that the "version magic" doesn't match, you can use this option to remove it. Naturally, this check is there for your protection, so this using option is dangerous unless you know what you're doing. This applies to any modules inserted: both the module (or alias) on the command line and any modules on which it depends. --force-modversion When modules are compiled with CONFIG_MODVERSIONS set, a section detailing the versions of every interfaced used by (or supplied by) the module is created. If a module fails to load and the kernel complains that the module disagrees about a version of some interface, you can use "--force-modversion" to remove the version information altogether. Naturally, this check is there for your protection, so using this option is dangerous unless you know what you're doing. This applies any modules inserted: both the module (or alias) on the command line and any modules on which it depends. -f --force Try to strip any versioning information from the module which might otherwise stop it from loading: this is the same as using both --force-vermagic and --force-modversion. Naturally, these checks are there for your protection, so using this option is dangerous unless you know what you are doing. This applies to any modules inserted: both the module (or alias) on the command line and any modules it on which it depends. -i --ignore-install --ignore-remove This option causes modprobe to ignore install and remove commands in the configuration file (if any) for the module specified on the command line (any dependent modules are still subject to commands set for them in the configuration file). Both install and remove commands will currently be ignored when this option is used regardless of whether the request was more specifi- cally made with only one or other (and not both) of --ignore-install or --ignore-remove. See modprobe.conf(5). -l --list List all modules matching the given wildcard (or "*" if no wildcard is given). This option is provided for backwards compatibil- ity and may go away in future: see find(1) and basename(1) for a more flexible alternative. -n --dry-run --show This option does everything but actually insert or delete the modules (or run the install or remove commands). Combined with -v, it is useful for debugging problems. For historical reasons both --dry-run and --show actually mean the same thing and are interchangeable. -q --quiet With this flag, modprobe won't print an error message if you try to remove or insert a module it can't find (and isn't an alias or install/remove command). However, it will still return with a non-zero exit status. The kernel uses this to opportunistically probe for modules which might exist using request_module. -R --resolve-alias Print all module names matching an alias. This can be useful for debugging module alias problems. -r --remove This option causes modprobe to remove rather than insert a module. If the modules it depends on are also unused, modprobe will try to remove them too. Unlike insertion, more than one module can be specified on the command line (it does not make sense to specify module parameters when removing modules). There is usually no reason to remove modules, but some buggy modules require it. Your distribution kernel may not have been built to support removal of modules at all. -S --set-version Set the kernel version, rather than using uname(2) to decide on the kernel version (which dictates where to find the modules). --show-depends List the dependencies of a module (or alias), including the module itself. This produces a (possibly empty) set of module file- names, one per line, each starting with "insmod" and is typically used by distributions to determine which modules to include when generating initrd/initramfs images. Install commands which apply are shown prefixed by "install". It does not run any of the install commands. Note that modinfo(8) can be used to extract dependencies of a module from the module itself, but knows nothing of aliases or install commands. -s --syslog This option causes any error messages to go through the syslog mechanism (as LOG_DAEMON with level LOG_NOTICE) rather than to standard error. This is also automatically enabled when stderr is unavailable. This option is passed through install or remove commands to other modprobe commands in the MODPROBE_OPTIONS environment variable. -t --type Restrict -l to modules in directories matching the dirname given. This option is provided for backwards compatibility and may go away in future: see find(1) and basename(1) for a more flexible alternative. -V --version Show version of program and exit. -v --verbose Print messages about what the program is doing. Usually modprobe only prints messages if something goes wrong. This option is passed through install or remove commands to other modprobe commands in the MODPROBE_OPTIONS environment variable. ENVIRONMENT
The MODPROBE_OPTIONS environment variable can also be used to pass arguments to modprobe. COPYRIGHT
This manual page originally Copyright 2002, Rusty Russell, IBM Corporation. Maintained by Jon Masters and others. SEE ALSO
modprobe.conf(5), modprobe.d(5), insmod(8), rmmod(8), lsmod(8), modinfo(8) modprobe(8)
All times are GMT -4. The time now is 11:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy