pccardctl
Control and monitor PCMCIA (PC Card) devices
SYNOPSIS
pccardctl [options] [command] [arguments]
Commonly: pccardctl command [socket]
Example: pccardctl status
Example: pccardctl suspend 0
PARAMETERS
status [socket]
Displays the status of all or a specified PCMCIA socket.
ident [socket]
Shows detailed identification information about the card in a socket.
config [socket]
Presents configuration details for the card in a given socket.
suspend [socket]
Suspends power to the card in the specified socket, typically for power saving.
resume [socket]
Resumes power to a suspended card, bringing it back online.
eject [socket]
Initiates the physical ejection of a card from its socket.
insert [socket]
Notifies the PCMCIA subsystem of a card insertion (less common with auto-detect).
reset [socket]
Performs a hardware reset on the card in the chosen socket.
power [socket]
Controls the power state (on/off) of a specific socket.
bind [socket]
Associates a kernel driver with the detected card.
unbind [socket]
Detaches a kernel driver from the card.
-V, --version
Displays the pccardctl utility version.
-h, --help
Shows a help message with command usage.
DESCRIPTION
pccardctl is a utility used to control and query the status of PCMCIA (Personal Computer Memory Card International Association) and CardBus sockets. These sockets were commonly found on older laptop computers, allowing the use of various expansion cards such as modems, network adapters, storage, and more.
The command provides functionalities to enable/disable sockets, power on/off cards, reset cards, examine card information, and manage the PCMCIA subsystem's operation. It's part of the pcmciautils package and works in conjunction with cardmgr (or cardd on older systems) to manage card insertions, removals, and configuration. While less prevalent on modern hardware, it was an essential tool for configuring and troubleshooting expansion cards in the era when PCMCIA slots were standard.
CAVEATS
pccardctl is primarily relevant for systems with physical PCMCIA/CardBus slots. Modern laptops rarely include these, making the command largely obsolete for new hardware. Its functionality relies on the pcmciautils package and a running cardmgr (or cardd) daemon, which may not be installed or enabled by default on contemporary Linux distributions. Usage often requires root privileges.
SOCKET NUMBERING
PCMCIA sockets are typically referred to by a zero-based index (e.g., 0, 1). If no socket number is specified for commands that require it, pccardctl often defaults to socket 0 or operates on all available sockets depending on the command.
DAEMON REQUIREMENT
For most pccardctl commands to function correctly, the cardmgr (or cardd) daemon must be running. This daemon manages the detection, configuration, and hot-plugging of PCMCIA cards.
HISTORY
The pccardctl command emerged as part of the Linux PCMCIA subsystem development, which began in the mid-1990s. This subsystem was crucial for enabling Linux to run effectively on laptops, which heavily relied on PCMCIA slots for networking, modems, and other peripherals. It was initially part of the PCMCIA-CS (Card Services) package, later evolving into pcmciautils. Its peak usage coincided with the prevalence of PCMCIA and CardBus slots on laptops, roughly from the late 1990s to the mid-2000s, before USB and integrated hardware largely superseded these expansion slots. While the underlying standards are still supported by the kernel, the command-line utility is less frequently used today due to the declining availability of PCMCIA hardware.