configuration. For instance, the SCSI card drivers require that the kernel be configured with SCSI support,
and the network drivers require a networking kernel. If a kernel lacks a necessary feature, insmod may
report undefined symbols and refuse to load a particular module. Note that insmod error messages do not
distinguish between version mismatch errors and missing symbol errors.
Specifically:
• The serial client driver serial_cs requires the kernel serial driver to be enabled with
CONFIG_SERIAL. This driver may be built as a module.
• Support for multiport serial cards or multifunction cards that include serial or modem devices
requires CONFIG_SERIAL_SHARE_IRQ to be enabled.
• The SCSI client drivers require that CONFIG_SCSI be enabled, along with the appropriate top level
driver options (CONFIG_BLK_DEV_SD, CONFIG_BLK_DEV_SR, etc for 2.1 kernels). These may
be built as modules.
• The network client drivers require that CONFIG_INET is enabled. Kernel networking support cannot
be compiled as a module.
• The token−ring client requires that the kernel be compiled with CONFIG_TR enabled.
There are two ways to proceed:
• Rebuild your kernel with the necessary features enabled.
• If the features have been compiled as modules, then modify /etc/pcmcia/config to preload
these modules.
The /etc/pcmcia/config file can specify that additional modules need to be loaded for a particular
client. For example, for the serial driver, one would use:
device "serial_cs"
class "serial" module "misc/serial", "serial_cs"
Module paths are specified relative to the top−level module directory for the current kernel version; if no
relative path is given, then the path defaults to the pcmcia subdirectory.
3.3 Interrupt scan failures
Symptoms:
• The system locks up when the PCMCIA drivers are loaded, even with no cards present.
• The system log shows a successful host controller probe just before the lock−up, but does not show
interrupt probe results.
After identifying the host controller type, the socket driver probes for free interrupts. The probe involves
programming the controller for each apparently free interrupt, then generating a ``soft'' interrupt, to see if the
interrupt can be detected correctly. In some cases, probing a particular interrupt can interfere with another
system device.
Linux PCMCIA HOWTO
3.3 Interrupt scan failures 15
Comentarios a estos manuales