On Fri, 2003-06-13 at 03:58, Jan Mynarik wrote:
> 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.
I used ACU/bcard, but it was fairly fiddly. I kept finding that
changing a setting would make the card go into a strange state which was
unrecoverable, even by unloading/reloading the module. Only rebooting
would fix it. Eventually I managed to get everything configured, and I
just get modprobe to run bcard after loading the module to configure the
card. This seems to work reliably so long as I avoid doing any other
settings with acu (
I've been doing some work to extend airo.c to support the 350, based on
Ben Reed's start. Unfortunately the card gets into state just keeps
misbehaving and reports errors, but without any documentation its hard
to work out what's going wrong. I'm hoping Cisco will see fit to
release some documentation (or at least a new driver) - particularly
since it seems the number of mpi350 Linux users is increasing, driven
into Cisco's arm by Intel and Broadcom's complete documentation void.
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jun 15 2003 - 22:00:37 EST