PCMCIA not detected

aepic · 05-21-2005, 06:26 PM

I have searched for over a month and have not found a solution for my probelm. The problem is with my PCMCIA card not being detected. Checking the HCL lists 4 versions of WPC54G and is supposedly compatible. However, linux is not discovering it when inserted into the cardbus.

I also verified that worked on w2k on the same machine to eliminate any potential thoughts of an hardware issue. Everything works great, except under linux.

Some specs on the hardware:

PCMCIA: Linksys WPC54Gv4

Code:

00:02:0 CardBus bridge: Texas Instruments PCI1250 (rev 02)
00:02:1 CardBus bridge: Texas Instruments PCI1250 (rev 02)

Code:

00:2.0 Class 0607: 104c:ac16 (rev 02)
00:2.1 Class 0607: 104c:ac16 (rev 02)

Code:

cardctl config output:   
Socket 0:    
  Vcc 3.3V    Vpp1 3.3V    Vpp2 3.3V    
  Interface type is "cardbus"   
  irq 11 [exclusive] [level]    
  function 0:  
Socket 1:     
  not configured    

cardctl status output:  
Socket 0:    
  3.3V CardBus card    
  function 0: [ready]  
Socket 1:     
  no card

Please help.

musicman_ace · 05-22-2005, 04:18 AM

Is PCMCIA built into the kernel, or are they modules?
Are the modules loaded? {if modules}
Are the drivers built into the kernel, or are they modules?
Are the driver modules loaded? {if modules}
Are you using ndis wrappers?
After booting, plug the card in and post the output of dmesg

From the looks of it, yenta has detected the card since your lspci shows it and cardctl verifies that socket0 has a card in it. Does iwconfig show anything? Can you bring up eth1/wlan0 up manually?

aepic · 05-22-2005, 04:53 AM

Quote:

Originally posted by musicman_ace
[B]Is PCMCIA built into the kernel, or are they modules?
Are the modules loaded? {if modules}
Are the drivers built into the kernel, or are they modules?

not sure what you mean by this... just a beginner in linux. However, I have installed ndiswrapper with no problems, but can never get this card up as linux shows no connection. The hardware is never detected under lspci (texas instruments is my cardbus not the pcmcia), I had the impression that when you insert a pcmcia card into the cardbus, lspci will output what chipset was installed into the socket.

this is what I am lead to believe.. with any distro, respectively. if I call lspci with the card withdrawn it should read:

Code:

00:02:0 CardBus bridge: Texas Instruments PCI1250 (rev 02)
00:02:1 CardBus bridge: Texas Instruments PCI1250 (rev 02)

with the pcmcia card inserted lspci should read: (exagerated details)

Code:

00:02:0 PCMCIA: Aironet 3341 PCI2823 (rev 01)
00:02:1 CardBus bridge: Texas Instruments PCI1250 (rev 02)

lspci -n should read

Code:

00:2.0 Class 0607: 1344c:bd23 (rev 02)  <- Aironet card
00:2.1 Class 0607: 104c:ac16 (rev 02) <- Cardbus bridge Texas Instruments

As you said yenta does discover that the socket is in use and advertises that, init.d/pcmcia restart, but fails to restart as yenta is using the socket.

Code:

Shutting down PCMCIA services: ERROR: Module pcmcia_core is in use by yenta_socket done. 
Starting PCMCIA services: cardmgr[pid#]: open_socket(socket 2) failed: Bad file descriptor cardmgr[pid#]: watching 2 sockets done.

I will get the output of dmesg and post it here soon.

musicman_ace · 05-22-2005, 06:20 AM

For those 3 questions, you have to enter the kernel configuration utility and search around. If you haven't compiled a kernel before, don't mess with the one currently on your system. We'd rather leave it alone since it works.

Download a full kernel source from kernel.org
unpack it to /usr/src/linux-version
cd /usr/src/linux-version
make menuconfig

Do some editing and adding/subtracting to the kernel. This is where you'd check to see if your drivers are built in or modules.

Save the kernel and exit
make && make modules && make modules_install <- this will do all the compiling.
cp arch/i386/boot/bzImage /boot/bzImage-version

Add the new kernel to your bootloader. Reboot and choose the new one.

aepic · 05-23-2005, 12:48 AM

I am missing the point of downloading and recompiling a new kernel. When in fact the kernel should detect a hardware change regardless if it's a built in module, it should state "unknown" in lspci.

Whats so difficult to get more one then opinion on this matter? I see many thread views but no responses, are you all soo godly not to answer?

musicman_ace · 05-23-2005, 01:14 AM

Quote:

Originally posted by aepic
I see many thread views but no responses, are you all soo godly not to answer?

There are questions that will go unanswered. Everyone on these boards has a life beyond them. Most us try to help as much as we can, but that comment might turn away people who would be willing to help. My advice is to bump this question once a day or so if no one else answers. Do some more searches and see what comes up.

hlenderk · 04-08-2006, 11:02 AM

Hello, this is a little bit late (like a year?) I show the same card bus but I have a slightly different situation. There is a newer thread over in slackware but I thought "linux hardware" sounded more apropo so I'm posting this here I hope it gets seen. Sorry about the length.

I'm trying to get my pcmcia modem to be recognized by a 2.6.12-5 kernel that is running on a lfs livecd! My "other" install is a RedHat9 (2.4.20 kernel) which has never had a problem with it (win '98 either)
I too have been reading up on this transition phase of the 2.6 kernel and it appears that the real break is, as xenon2000, is saying at the 2.6.13 where it now uses the "udev" device system instead of devfs. While there is some helpful info out there for stuff that works, I'm not finding anything on like a step by step how to find out what you need present on the system for a card to be properly id'd ....with troubleshooting!
In my situation I don't think it is practical (or doable) to install the new pcmciautils on every boot. Or to have it installed on hda to be used in the ramfs... I have this to work with while booted to the lfs livecd:
-----
lsmod
Module Size Used by
usb_storage 30980 1
ext3 98180 1
jbd 55576 1 ext3
nls_iso8859_1 4864 2
nls_cp437 6528 2
vfat 11520 2
fat 46876 1 vfat
yenta_socket 20360 1
rsrc_nonstatic 11648 1 yenta_socket
pcmcia_core 43908 2 yenta_socket,rsrc_nonstatic
---------------------------------
lspci
00:00.0 Host bridge: Intel Corporation 430TX - 82439TX MTXC (rev 01)
00:01.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01)
00:01.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:01.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 01)
00:02.0 VGA compatible controller: S3 Inc. ViRGE/MX+MV (rev 03)
00:03.0 CardBus bridge: Texas Instruments PCI1250 (rev 02)
00:03.1 CardBus bridge: Texas Instruments PCI1250 (rev 02)
-----
Those last 2 are the pcmcia slots.
In redhat9 modem is 00:03.1 on ttyS1. The 00:03:1 is the same BUT where the heck does udev put it?
I don't think it's connected to ttyS1 (or maybe anything!)
When I learned a little more I found I could look more at the /sys files for clues.
Here is what's shown for 00:03:1 using `udevinfo` which sorts through the /sys area to report:
( check the inserted ##comment## )

udevinfo -a -p /sys/class/pcmcia_socket/pcmcia_socket1 | less
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.

looking at class device '/sys/class/pcmcia_socket/pcmcia_socket1':
KERNEL=="pcmcia_socket1"
SUBSYSTEM=="pcmcia_socket"
SYSFS{available_resources_io}==""
SYSFS{available_resources_mem}==""
SYSFS{available_resources_setup_done}=="no"
SYSFS{card_irq_mask}=="0x06b8"
##These next 4 lines are not present when card is removed, everything else remains the same##
SYSFS{card_type}=="16-bit"
SYSFS{card_vcc}=="5.0V"
SYSFS{card_voltage}=="5.0V"
SYSFS{card_vpp}=="5.0V"

follow the "device"-link to the physical device:
looking at the device chain at '/sys/devices/pci0000:00/0000:00:03.1':
BUS=="pci"
ID=="0000:00:03.1"
DRIVER=="yenta_cardbus"
SYSFS{class}=="0x060700"
SYSFS{device}=="0xac16"
SYSFS{irq}=="11"
SYSFS{local_cpus}=="01"
SYSFS{modalias}=="pci:v0000104Cd0000AC16sv00000000sd00000000bc06sc07i00"
SYSFS{subsystem_device}=="0x0000"
SYSFS{subsystem_vendor}=="0x0000"
SYSFS{vendor}=="0x104c"

looking at the device chain at '/sys/devices/pci0000:00':
BUS==""
ID=="pci0000:00"
DRIVER=="unknown"
(END)
-----------
So I think it knows "something is there" but it doesn't know what to do with it.
My chores would then be:
- To make a "udev rule" or something to get this information to it?
What info and where do I put it
- Get it plugged into ttyS1 or wherever it's supposed to be nowadays so's I can point to it with pppd.
???could it be that I just need to make a node to 00:03:01 ?????
setserial is not in the livecd fs. mknod?
Thanks, Howard

hlenderk · 04-10-2006, 01:53 PM

After some more research, I'm finding that I have these other pcmcia kernel modules that may be helpful.
So on boot I get:
-----
# lsmod
Module Size Used by
ext3 98180 1
jbd 55576 1 ext3
nls_iso8859_1 4864 1
nls_cp437 6528 1
vfat 11520 1
fat 46876 1 vfat
usb_storage 30980 0
yenta_socket 20360 1
rsrc_nonstatic 11648 1 yenta_socket
pcmcia_core 43908 2 yenta_socket,rsrc_nonstatic
-----
And then I see these additional available: (I think)
/lib/modules/2.6.12.5/kernel/drivers/scsi/pcmcia/sym53c500_cs.ko
/lib/modules/2.6.12.5/kernel/drivers/scsi/pcmcia/qlogic_cs.ko
/lib/modules/2.6.12.5/kernel/drivers/scsi/pcmcia/nsp_cs.ko
/lib/modules/2.6.12.5/kernel/drivers/scsi/pcmcia/fdomain_cs.ko
/lib/modules/2.6.12.5/kernel/drivers/scsi/pcmcia/aha152x_cs.ko
/lib/modules/2.6.12.5/kernel/drivers/pcmcia/yenta_socket.ko
/lib/modules/2.6.12.5/kernel/drivers/pcmcia/tcic.ko
/lib/modules/2.6.12.5/kernel/drivers/pcmcia/rsrc_nonstatic.ko
/lib/modules/2.6.12.5/kernel/drivers/pcmcia/pd6729.ko
/lib/modules/2.6.12.5/kernel/drivers/pcmcia/pcmcia_core.ko
/lib/modules/2.6.12.5/kernel/drivers/pcmcia/pcmcia.ko
/lib/modules/2.6.12.5/kernel/drivers/pcmcia/i82365.ko
/lib/modules/2.6.12.5/kernel/drivers/pcmcia/i82092.ko
/lib/modules/2.6.12.5/kernel/drivers/net/pcmcia/xirc2ps_cs.ko
/lib/modules/2.6.12.5/kernel/drivers/net/pcmcia/smc91c92_cs.ko
/lib/modules/2.6.12.5/kernel/drivers/net/pcmcia/pcnet_cs.ko
/lib/modules/2.6.12.5/kernel/drivers/net/pcmcia/nmclan_cs.ko
/lib/modules/2.6.12.5/kernel/drivers/net/pcmcia/fmvj18x_cs.ko
/lib/modules/2.6.12.5/kernel/drivers/net/pcmcia/axnet_cs.ko
/lib/modules/2.6.12.5/kernel/drivers/net/pcmcia/3c589_cs.ko
/lib/modules/2.6.12.5/kernel/drivers/net/pcmcia/3c574_cs.ko
-----
But I'm not sure which one(s) are needed.
There is a full kernel source on the cd and my thinking is that I could:
- build what I might need and store in over in vfat and load it after booting to cd;
- or worse-case: install the utility, track where eveything is put , copy them to vfat for later insertion;
- or: worse-worse-case rebuild utility each time I want to dial out!!! (I don't think so)
Any ideas? Thanks, Howard