From: Jan Mynarik <mynarikj@phoenix.inf.upol.cz>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Cisco Aironet mini-PCI wireless card (MPI-350) [Was: Re: Intel PRO/Wireless 2100 vs. Broadcom BCM9430x]
Date: 13 Jun 2003 12:58:08 +0200 [thread overview]
Message-ID: <1055501888.1452.13.camel@narsil> (raw)
In-Reply-To: <1055439997.10219.54.camel@ixodes.goop.org>
Many thanks,
the patch worked well in the meaning of possible module insertion. But I
wasn't able to configure the card with ACU well.
With older firmware it's possible to insert module and to configure it
with ACU, but I'm not able to configure the card well. The whole
password menu produces segmentation fault :-))
Is there any other way how to configure this card? Unfortunately it
doesn't support wireless extensions.
Jan Mynarik
On Thu, 2003-06-12 at 19:46, Jeremy Fitzhardinge wrote:
> On Thu, 2003-06-12 at 10:20, Jan Mynarik wrote:
> > Cisco's linux support is great until you have IBM's ThinkPad R40. With
> > this notebook, their newest Linux driver (version 2.0, older ones do not
> > support my card) module (mpi350.o) can't be inserted to kernel (oops and
> > module remains 'initializing' forever). Module is compiled successfully
> > against both 2.4.20 and 2.4.21-rc7 kernels.
> >
> > I'm just fighting their bureaucracy (in support) and trying to reach
> > someone who actually wrote the driver (module says Roland Wilcher). I
> > want to help him with testing and provide him with all possible
> > information.
>
> Downgrade your firmware. On the Cisco site, there's a Linux driver
> paired with a particular firmware version. Use it: there's a bug in the
> kernel driver in which it reads stuff out of the card's RIDs into a
> local structure, but using the card's RID size. The newer firmware has
> increased the structure sizes for some RIDs, which overruns the stack
> and crashes.
>
> I have attached a patch for the driver to fix the crash, but I'm not
> confident the card works well without the correct firmware.
>
> J
--
Jan Mynarik <mynarikj@phoenix.inf.upol.cz>
next prev parent reply other threads:[~2003-06-13 10:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 15:15 Intel PRO/Wireless 2100 vs. Broadcom BCM9430x Marc Sowen
2003-06-12 15:16 ` Joel Jaeggli
2003-06-12 17:20 ` Cisco Aironet mini-PCI wireless card (MPI-350) [Was: Re: Intel PRO/Wireless 2100 vs. Broadcom BCM9430x] Jan Mynarik
2003-06-12 17:46 ` Jeremy Fitzhardinge
2003-06-13 10:58 ` Jan Mynarik [this message]
2003-06-13 16:29 ` Jeremy Fitzhardinge
2003-06-12 20:37 ` Intel PRO/Wireless 2100 vs. Broadcom BCM9430x Anders Karlsson
2003-06-12 21:17 ` Jeremy Fitzhardinge
2003-06-12 21:52 ` Anders Karlsson
2003-06-12 21:57 ` Jeremy Fitzhardinge
2003-06-13 3:56 ` Joel Jaeggli
2003-06-12 17:08 ` Davide Libenzi
2003-06-12 17:22 ` Disconnect
2003-06-12 18:07 ` Martin List-Petersen
2003-06-12 20:35 ` Anders Karlsson
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=1055501888.1452.13.camel@narsil \
--to=mynarikj@phoenix.inf.upol.cz \
--cc=jeremy@goop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox