
Arcom Embedded Linux Technical Manual Configuring AEL
Configuring modprobe
The modprobe utility (but not the insmod utility) can be configured to automatically
pass parameters when a module is loaded. This is useful when the kernel calls
modprobe for you but you still want to pass parameters to the module.
The modprobe configuration is stored in files in /etc/modprobe.d/. Each entry has the
following format:
options MODULE PARAMTERS
For example, to pass debug=1 whenever loading the ppp_generic module, you can
create a file named /etc/modprobe.d/ppp containing the line:
options ppp_generic debug=1
In addition, modprobe can alias one module name to another. This is useful because
the kernel often calls modprobe with an abstract service name rather than a specific
module. For example, when an attempt is made to access the first Ethernet device, the
kernel calls modprobe to load eth0 (rather than a specific Ethernet driver module). In
such cases eth0 is configured as an alias for the actual Ethernet module. For example
(if smc91x is the driver for eth0 on your system):
alias eth0 smc91x
The full modprobe configuration format is in the modprobe.conf(5) man page.
Automatically loading modules at boot time
In most cases, the kernel loads the correct modules automatically or they are loaded by
the hotplug daemon. In some circumstances, however, this is not the case and it is
desirable to load the module automatically and unconditionally at boot time. You can do
this by listing the modules you wish to be loaded, one per line, in /etc/modules. Each
line must consist of a module name (or alias). This may be followed by one or more
optional parameters.
Removing kernel modules
A kernel module that is not in use by the system can be removed using the modprobe -
r command.
System recovery and single user mode
If a configuration error has been made that prevents you from logging in, you may be
able to boot into single user mode in order to repair the problem. A target board can be
booted into single user mode by adding the word single to the kernel command line.
This is done using the RedBoot exec command described on page 63
.
If it is not possible to recover the system using this method, you may have to reload the
default Development Kit image, as described in Updating the entire Flash
on page 63.
© 2006 Arcom Issue G 22
Kommentare zu diesen Handbüchern