[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

BUG?! no pcmcia ethernet on battery power



This has gotta be a bug, but I want to ask about it here before I finally
submit it as a formal bug.

If I run my laptop (Toshiba 490CDT) on battery power, then when I insert my ethernet card
(Xircom REM56G Ethernet/modem combo, I'm not using the modem at the moment), it is
routinely misrecognised as a memory card, and insertion consequently fails.
The entry in /var/log/daemon.log looks like:

Feb  2 13:52:46 strider cardmgr[1429]: initializing socket 0
Feb  2 13:52:46 strider cardmgr[1429]: socket 0: Anonymous Memory
Feb  2 13:52:46 strider cardmgr[1429]: executing: 'insmod
/lib/modules/2.2.14/pcmcia/memory_cs.o'
Feb  2 13:52:46 strider cardmgr[1429]: executing: './memory start mem0'

The only way I can get my card to work under battery power is to remove the
card and restart /etc/init.d/pcmcia, and I have to do this every time I want
to start using the card, after every suspend/resume cycle, say.  After
restarting pcmcia (with the card removed), the card is recognised properly:

Feb  2 13:57:29 strider cardmgr[1566]: initializing socket 0
Feb  2 13:57:29 strider cardmgr[1566]: socket 0: Xircom CEM56 Ethernet/Modem
Feb  2 13:57:29 strider cardmgr[1566]: executing: 'insmod
/lib/modules/2.2.14/pcmcia/xirc2ps_cs.o'
Feb  2 13:57:29 strider cardmgr[1566]: executing: 'insmod
/lib/modules/2.2.14/pcmcia/serial_cs.o'
Feb  2 13:57:32 strider cardmgr[1566]: executing: './network start eth0'
Feb  2 13:57:34 strider cardmgr[1566]: executing: './serial start ttyS3'

and everything works OK.

I only have this problem with "anonymous memory" consistently when I run on
battery power.  Under AC power the card can be removed and inserted at will
perfectly fine.  

But under slink I'm pretty sure the card worked fine under battery power.  I
now have potato, though I don't remember precisely when the problem first
came up.  Maybe with pcmcia-cs v3.1?  (I have 3.1.8-4, but it seems
unlikely it was fixed in the latest 3.1.8-5)

Does this problem make sense to anyone, or is it worth filing as a bug?

Drew Parsons

Attachment: pgpK2uGe3p0Um.pgp
Description: PGP signature


Reply to: