Linux lspcmcia: Show Information about PCMCIA sockets and Devices

in Categories last updated August 17, 2012

How do I see information about PC Card (pcmcia) under Linux operating systems?

You can use the following command:

  1. pccardctl – PCMCIA card control utility
  2. lspcmcia – display extended PCMCIA debugging information

Type the following command:
# pccardctl ls
# lspcmcia
Sample outputs:

Socket 0 Bridge:   	[yenta_cardbus] 	(bus ID: 0000:03:01.0)

To see current status for socket 0, enter:
# pccardctl status 0
Sample outputs:

  no card

To get more info about socket # 0:
# pccardctl info 0
The syntax is as follows:

pccardctl command socket

Where, command can be any one of the following:

           Display the current socket status flags.

           Display the socket configuration, including power settings, interrupt and  I/O  window
           settings, and configuration registers.  --not yet implemented

           Display  card  identification  information,  including product identification strings,
           manufacturer ID codes, and function ID codes.  Not yet implemented for cardbus  cards.
           Use lspci instead.

           Much  like  the ident command, but its output is formatted as a series of Bourne-stype
           shell variable definitions for use in scripts.  Not yet implemented for cardbus cards.

       ls  Display extended debugging information about the PCMCIA sockets and devices present in
           the system.

           Shut down and then disable power for a socket.

           Restore power to a socket, and re-configure for use.

           Notify all client drivers that this card will be ejected, then cut power to the

           Notify all client drivers that this card has just been inserted.

Posted by: Vivek Gite

The author is the creator of nixCraft and a seasoned sysadmin, DevOps engineer, and a trainer for the Linux operating system/Unix shell scripting. Get the latest tutorials on SysAdmin, Linux/Unix and open source topics via RSS/XML feed or weekly email newsletter.

Share this on (or read 0 comments/add one below):