cardmgr(8) [redhat man page]

CARDMGR(8)						      System Manager's Manual							CARDMGR(8)

NAME

       cardmgr - PCMCIA device manager

SYNOPSIS

       cardmgr [-V] [-q] [-d] [-o] [-f] [-v] [-c configpath] [-m modpath] [-p pidfile] [-s stabfile]

DESCRIPTION

       Cardmgr monitors PCMCIA sockets for card insertion and removal events.  When a card is inserted, cardmgr looks up the card in a database of
       known cards.  If the card can be identified, appropriate device drivers will be loaded and bound to the card.  When a card is ejected, that
       card's  drivers	will  be shut down and unloaded if possible.  Based on the contents of the PCMCIA card configuration database, cardmgr may
       also execute arbitrary commands when appropriate cards are either inserted or removed.

       All insertion and removal events, device driver loads and unloads, and startup and shutdown commands are reported in the system	log  file.
       Warnings and errors will also be logged.  Current card and device information for each socket is recorded in /var/lib/pcmcia/stab.

       Normally, when a card is identified, cardmgr will send a beep to the console.  A beep is also generated when a card is successfully config-
       ured.  A beep of lower pitch is generated if either of these steps fails.  Ejecting a card produces a single beep.

       When cardmgr receives a SIGHUP signal, it will reload its configuration file.  When cardmgr receives a SIGTERM signal, it  will	shut  down
       all sockets that are not busy and then exit, but drivers for busy sockets will stay loaded.

       If the PCMCIA_OPTS environment variable is set, its contents will be parsed after the main card configuration file is read.

       At startup, cardmgr requires that /tmp reside on a filesystem that permits special device files (i.e., a real linux filesystem, that is not
       mounted "nodev").

OPTIONS

       -V     Show version information and exit.

       -q     Quiet mode: don't beep when cards are inserted.

       -v     Verbose mode: generates more informational messages during normal operation.  Configuration scripts are executed with VERBOSE=y.

       -d     Follow module dependencies when loading driver modules, by defaulting to use modprobe instead of insmod.	Normally, cardmgr will try
	      using modprobe only after an unsuccessful attempt with insmod.

       -f     Foreground: do not fork and run as a daemon until after configuring any cards that are already present.

       -o     One pass: configure cards that are present, then exit.  This flag also forces cardmgr to run in the foreground.

       -c configpath
	      Look for the card configuration database and card configuration scripts in the specified directory, instead of /etc/pcmcia.

       -m modpath
	      Look for loadable kernel modules in the specified directory, instead of /lib/modules/`uname -r`.

       -p pidfile
	      Write the PID of the cardmgr process to the specified file, instead of /var/run/cardmgr.pid.

       -s stabfile
	      Write current socket information to the specified file, instead of /var/lib/pcmcia/stab.

FILES

       /etc/pcmcia/config	 Card configuration database
       /etc/pcmcia/config.opts	 Local resource settings for PCMCIA devices
       /var/run/cardmgr.pid	 PID of active cardmgr process
       /var/lib/pcmcia/stab	 Current card and device information for each socket.

AUTHOR

       David Hinds - dahinds@users.sourceforge.net
SEE ALSO

       pcmcia(5), stab(5), cardctl(8), cardinfo(1).

pcmcia-cs							2001/07/19 23:41:34							CARDMGR(8)

Check Out this Related Man Page

3C589_CS(4)						     Kernel Interfaces Manual						       3C589_CS(4)

NAME

       3c589_cs - 3Com 3c589 Etherlink III device driver

SYNOPSIS

       insmod 3c589_cs.o [pc_debug=n] [if_port=n] [irq_list=i,j,...]

DESCRIPTION

       3c589_cs  is  the  low-level  Card  Services driver for the 3Com 3c589 PCMCIA ethernet adapter and 3Com 3c562/3c563 combo cards.  When this
       driver is attached to a card, it allocates the next available ethernet device (eth0..eth#).  This device name will be reported in the  ker-
       nel log file, and passed on to cardmgr(8).

       With  the default transceiver setting, the driver will attempt to continuously autodetect the transceiver type (10base2 or 10baseT).  There
       should normally only be a one or two second lag before the correct transceiver is selected.  On particularly noisy or busy networks, it	is
       possible  for the detection logic to incorrectly toggle the transceiver type.  If this becomes a problem, it may be necessary to explicitly
       select the interface type when the module is loaded or with the ifport command.

PARAMETERS

       pc_debug=n
	      Selects the PCMCIA debugging level.  This parameter is only available if the module is compiled with debugging enabled.  A  non-zero
	      value enables debugging.

       if_port=n
	      Selects  the  transceiver type.  0 is autodetect (10baseT or 10base2), 1 is 10baseT (twisted pair), 2 is 10base2 (BNC, or thin net).
	      and 3 is AUI (thick ethernet).  The default is 0 (autodetect).

       irq_list=i,j,...
	      Specifies the set of interrupts that may be allocated by this driver.

DIAGNOSTICS

       eth#: interrupt(s) dropped!
	      Indicates that the driver did not receive an interrupt notification for some reason.  The driver will poll the card (with a signifi-
	      cant  performance penalty) if the problem persists.  The most likely cause is an interrupt conflict and/or host bridge configuration
	      problem.

AUTHOR

       David Hinds - dahinds@users.sourceforge.net

SEE ALSO

       cardmgr(8), pcmcia(5), ifport(8).

pcmcia-cs							2000/06/12 21:24:48						       3C589_CS(4)

Linux and UNIX Man Pages

cardmgr(8) [redhat man page]

Check Out this Related Man Page