Red Hat Bugzilla – Bug 122875
cardmgr not finding sockets
Last modified: 2007-11-30 17:10:42 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Description of problem:
On a thinkpad A31p when starting most of the time the boot.log shows
May 9 20:59:12 laptop pcmcia: Starting PCMCIA services:
May 9 20:59:12 laptop pcmcia: cardmgr: no sockets found!
May 9 20:59:12 laptop pcmcia: done.
Worked fine under core 1.
Occasionally cardmgr will report it's watching 2 sockets.
using an orinoco wireless card and an IBM bluetooth card
Version-Release number of selected component (if applicable):
core2-test3 yum update as of 9th May 7pm GMT
Steps to Reproduce:
1. start laptop
2. insert pcmcia card
3. look a boot log
Actual Results: card did nothing, no beeps, no lights etc
Expected Results: beeps and lights
Same behavior on my Dell Inspiron 7500 PIII-700, 512MB RAM, Sony
PCWA-C150S 802.11b card and Xircom CBE2-100 10/100 Ethernet.
This is with a fresh install of FC2T3 from DVD.
What happens if you execute /sbin/modprobe yenta_socket before
inserting PCMCIA card?
I have the same problem with Cisco 350. If I modprobe yenta_socket
and restart pcmcia service I can get the card to work. I have a
Winbook X4 with a P4 1.8 and 256mb ram.
/sbin/modprobe yenta_socket then
service pcmcia restart
reports cardmgr: watching 2 sockets
inserting either card and I get lights and functioning cards.
Had the problem with an orinoco card in a Dell 4150.
and cardmgr seems to work..
Setup: Linksys card in a Toshiba Tecra 8100.
The "modprobe yenta_socket; service pcmcia restart" steps work for me
To make this permanent, I followed the instructions to reorder
I have that problem with Fedora 2 on a Dell Laptop, with or
without a single ELSA ISDN card. Actually, the ELSA used to
work!! (But see bug 125135 for erratic behaviour of that card
Yesterday Fedora decided to no longer find any sockets.
Mystifying. Things work well under Windows. Tried to load/unload
the kernel modules (elsa, ds, pcmcia) to no avail. cardmgr -v does
not give any additional information.
Will try the yenta_socket (what the heck is THAT?) thing and report
Yup, works. The question is: what makes Linux load (or not?)
yenta_socket? And would it change?
*** This bug has been marked as a duplicate of 121742 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.