pcmcia - what is first place to look for bug?

[Jerry Walden]

Thanks -

Okay - I rebuilt the kernel and made the modules pcmcia_core,
yenta_socket, ds, ide_cs 
Below is the output from dmesg.  Output from /var/log/messages only
happens after I run the cardmgr

insmod pcmcia_core:
Linux Kernel Card Services 3.1.22
  options:  [pci] [cardbus]

insmod yenta_socket:
yenta 00:0c.1: Preassigned resource 0 busy, reconfiguring...
yenta 00:0c.1: Preassigned resource 2 busy, reconfiguring...
Yenta ISA IRQ mask 0x0000, PCI irq 1
Socket status: 30000006
Yenta ISA IRQ mask 0x0000, PCI irq 1
Socket status: 30000006

ismod ds:
(no output from dmesg)

insmod ide-cs:
(no output)


/etc/rc.d/rc.pcmcia start:

aStarting PCMCIA services: 
cardmgr opts
cardmgr[113]: watching 2 sockets
cardmgr[113]: could not adjust resource: IO ports 0x1100-0x17ff: Invalid
argument
cardmgr[113]: could not adjust resource: IO ports 0x110-0x4ff: Invalid
argument
cardmgr[113]: could not adjust resource: memory 0xc8000-0xcffff: Invalid
argument
cardmgr[113]: could not adjust resource: memory 0xa0000000-0xa0ffffff:
Invalid argument
cardmgr[113]: could not adjust resource: IO ports 0xa00-0xaff: Invalid
argument
cardmgr[113]: could not adjust resource: irq 4: Invalid argument
cardmgr[114]: starting, version is 3.2.7

-bash-2.05b#

I looked at /proc/iomem and /proc/ioports

-bash-2.05b# cat /proc/iomem
-bash-2.05b# cat /proc/ioports
02a41000-02a41007 : ide0
02a41206-02a41206 : ide0
ad000000-ad003fff : ltxser
b0400000-b0400fff : frontpanel
b1100000-b1100007 : serial(auto)
b1400000-b1400007 : serial(auto)
b1500000-b150ffff : Au1x00 ENET
b1510000-b151ffff : Au1x00 ENET

-bash-2.05b# cat /proc/interrupts
           CPU0
  1:          0    Au1000 Level  PCI device 104c:ac55, PCI device
104c:ac55
  3:      95873    Au1000 Level  serial
 28:      21150    Au1000 Level  eth0
 32:          1    Au1000 Level  ltxser
 35:         12    Au1000 Level  ide0

I'm not certain - given the output above - how to begin to guess an
address for the port/mem.  Which one of the above modules would normally
identify a card in the slot and return some form of ID - it seems that
is the first thing that is not showing up



----Original Message-----
From: Pavel Roskin [mailto:proski at gnu.org] 
Sent: Friday, March 12, 2004 4:06 PM
To: Jerry Walden
Cc: linux-pcmcia at lists.infradead.org
Subject: Re: pcmcia - what is first place to look for bug?


On Fri, 12 Mar 2004, Jerry Walden wrote:

>  I have a certain level of experience with Linux kernel hacking and 
> with drivers etc...  Not much with PCMCIA.  So - I just went ahead and

> built the kernel with PCMCIA support and cross-compiled the utilities.

> Problem is - I'm trying to figure out where to start debugging.  I 
> have configured many other boards for PCMCIA support from the 
> standpoint of modifying scripts etc. Problem is - I know what I have 
> does not work - I just cannot tell where the first sign of a problem 
> is.

dmesg and /var/log/messages are your best friends.  Try doing everything
by hand (modprobe ds; modprobe yenta_socket; cardmgr) - what you
attached looks like an output from a script.

> Below is the output while my kernel is loading, and also the output 
> from running cardmgr.  We have a TI-PCI1520 cardbus controller with an

> alchemy 1500.  I built the kernel with i82092 support.

You need Yenta support, not i82092.

> I have PCCARD (a CompactFlash adapter) in slot 0.  It is obviously not

> being recognized.  I cannot tell if my problem starts with the cardbus

> driver in the kernel (yenta_socket right?) or if it is a simpler 
> config problem.  What should I be seeing?  Where should I start 
> debugging?

See kernel messages.  To make cardmgr run, edit /etc/pcmcia/config.opts
and set memory and address range appropriate for your platform.  See
/proc/iomem and /proc/ioports for ideas.  Try unused areas near used
areas.

-- 
Regards,
Pavel Roskin