From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Timothy A. Seufert" <tas@mindspring.com>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: PCMCIA issues
Date: Thu, 13 Sep 2001 14:54:02 +0200 [thread overview]
Message-ID: <20010913125402.29847@smtp.adsl.oleane.com> (raw)
In-Reply-To: <p05100300b7c6188b0203@[10.0.0.42]>
>
>Sep 13 01:08:38 localhost cardmgr[259]: socket 1: Anonymous Memory
>Sep 13 01:08:38 localhost kernel: cs: unable to map card memory!
>Sep 13 01:08:38 localhost kernel: cs: unable to map card memory!
>Sep 13 01:08:39 localhost cardmgr[259]: executing: 'modprobe memory_cs'
>Sep 13 01:08:39 localhost cardmgr[259]: + modprobe: Can't locate
>module memory_cs
>Sep 13 01:08:39 localhost cardmgr[259]: modprobe exited with status 255
>Sep 13 01:08:39 localhost cardmgr[259]: module
>/lib/modules/2.4.10-pre8/pcmcia/memory_cs.o not available
>Sep 13 01:08:40 localhost cardmgr[259]: get dev info on socket 1
>failed: Resource temporarily unavailable
Not sure for the details as I'm not a PCMCIA expert, but I know
paulus fixes some issues with pcmcia resource allocation. His patch
haven't make it upstream yet but is in my tree.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-13 12:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 20:19 Cardbus issues on TiBook Ira Weiny
2001-09-06 21:10 ` Armando Di Cianno
2001-09-07 16:24 ` Ira Weiny
2001-09-07 19:46 ` Armando Di Cianno
2001-09-13 8:19 ` PCMCIA issues Timothy A. Seufert
2001-09-13 12:54 ` Benjamin Herrenschmidt [this message]
2001-09-06 21:10 ` Cardbus issues on TiBook Benjamin Herrenschmidt
2001-09-07 16:36 ` Ira Weiny
2001-09-07 17:06 ` Benjamin Herrenschmidt
2001-09-07 23:47 ` System map in XMON (was: Cardbus issues on TiBook) Ira Weiny
2001-09-08 12:45 ` Benjamin Herrenschmidt
2001-09-06 23:01 ` Cardbus issues on TiBook Marcus O.C. Metzler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010913125402.29847@smtp.adsl.oleane.com \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tas@mindspring.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).