Novell LINUX ENTERPRISE DESKTOP 10 SP2 - DEPLOYMENT GUIDE 08-05-2008 Deployment Manual page 534

a. The pcmcia_socket events trigger udev to call /sbin/hwup and load the
b. All I/O and memory ranges specified in /etc/pcmcia/config.opts are
c. The card services in the kernel check these ranges. If the memory ranges in
After these steps have been successfully completed, the bridge is fully initialized. After
this, the card itself is initialized as described in the following section.
26.2.2 Card Initialization
The events caused by plugging in a PCMCIA card can be summarized as follows:
1. A hotplug event occurs. For PC cards, this is a pcmcia event. For CardBus cards,
this is a pci event.
2. For any events, udev calls /sbin/hwup to load a driver module. The module
name is either specified in a hwcfg* file under /etc/sysconfig/hardware
or via modprobe modalias.
3. If needed, device initialization triggers a firmware hotplug event. This searches
for firmware and loads it.
4. The device driver registers the interfaces.
After these steps have been completed, the system proceeds with interface setup as de-
scribed in the next section.
If your card is a PC card, you might need some of the following parameters in /etc/
sysconfig/pcmcia to get it fully supported and working flawlessly:
PCMCIA_LOAD_CIS
A PC card's firmware is referred to as CIS (Card Information Structure). It provides
additional implementation details of the card. hwup checks the integrity of the
card's built-in CIS and tries to load another CIS from disk if the card's CIS proves
518 Deployment Guide
pcmcia kernel module.
added to the socket.
/etc/pcmcia/config.opts are wrong, this step may crash your machine.
See Section 26.3.1, "Machine Crashes on PCMCIA"
about how to debug and fix this issue.
(page 520) for information