From: Rodrigo Miranda Terra <rodrigo@isg.com.br>
To: linux-kernel@vger.kernel.org
Subject: patch-2.4.23-pre5 and pcmcia services
Date: Mon, 22 Sep 2003 07:28:24 -0300 [thread overview]
Message-ID: <3F6ECEC8.6040807@isg.com.br> (raw)
Hi all,
I´m wrinting only to report that the new releases that start with
patch-2.4.23-pre1 broken pcmcia support from pcmcia_cs packages. The
error of not compile pcmcia_cs is easy to correct only and #define
CONFIG_NR_CPUS in include/pcmcia/autoconf.h ( pcmcia 2.3.5 ) or
include/pcmcia/config.h ( in pcmcia_cs 2.3.4 ). But the problem is that
result modules cant find devices.
If I repeat exact the same process with 2.4.22 all work fine! The
motherboard that I tested was a A7S333. The device is a SWL-2100 (
Samsung 802.11b - Wireless board ). I was using with hostap driver. The
pcmcia can find device and even locate right module and try load the
module but cant bind. Below a except from /var/log/daemond.log:
Sep 21 12:36:03 eregon cardmgr[201]: watching 4 sockets
Sep 21 12:36:03 eregon cardmgr[201]: starting, version is 3.2.5
Sep 21 12:36:04 eregon cardmgr[201]: socket 0: Samsung SWL2000-N 11Mb/s
WLAN Card
Sep 21 12:36:04 eregon cardmgr[201]: executing: 'modprobe hostap_crypt'
Sep 21 12:36:04 eregon cardmgr[201]: executing: 'modprobe hostap'
Sep 21 12:36:04 eregon cardmgr[201]: executing: 'modprobe hostap_cs'
Sep 21 12:36:04 eregon cardmgr[201]: bind 'hostap_cs' to socket 0
failed: Operation not permitted
If I change ds.c in pcmcia package to ignore bind error i get :
Sep 21 20:46:16 eregon cardmgr[208]: get dev info on socket 0 failed: No
such device
My distribution is debian woody. I´m using now 2.4.22 with some
patchs borrowed from 2.4.23-pre5, like sch_htb.c fix. Any way I would
like report this problem.
Regards Rodrigo.
reply other threads:[~2003-09-22 10:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F6ECEC8.6040807@isg.com.br \
--to=rodrigo@isg.com.br \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.