[sisela] problem with two PCMCIA cards
Thu, 20 May 1999 18:39:07 -0400 (EDT)
I had a very similar problem with an old laptop. The problem turned out
to be that Sisela was trying to assign irq=5 which didn't work.
I corresponded with the PCMCIA guru who suggested I add a line in
pcmcia.conf (or whatever it's called) to "exclude" that irq. As I recall
the real pcmcia.conf is in a strange place (not the pcmcia directory) when
you build sisela.
After that two PCMCIA cards (one wireless, one ethernet) worked fine.
I have not tried that machine as a wireless bridge, mostly because I
never got around to it.
Sisela 0.2 DOES work fine as an "inverse" access point with a Prism2
card and an ethernet card. You have to set ipv4_forward by writing a 1 to
the correct place in the /proc filesystem.
I am not currently using that inverse access point since I have run out
of prism2 cards :(. I am not sure whether they are still being made? and
if so by whom?
On Thu, 20 May 2004, Martin Ling wrote:
> On Wed, May 19, 2004 at 09:29:55PM -0500, S. R. Voloch wrote:
> > Hi,
> > I have an old laptop (Soyo PW980) that I want to use as a wireless bridge.
> > It doesn't have an ethernet port but it has two PCMCIA slots. My plan was
> > to plug a ethernet card in one of the slots and the wireless card on the
> > other. Now, if I plug either of these cards by itself, then sisela recognizes
> > the card and everything works. However if I plug in both cards then only
> > one gets recognized. Is there a workaround this problem?
> I'd need to see some more information to figure out what's going on. If
> you're able to get the system connected to the net in each case (card A,
> card B, cards A+B) could you send a feedback report from each using
> 'ytheleus feedback'?
> Otherwise if you could give the output of:
> cardctl status
> cardctl config
> cardctl ident
> that'd be a useful start.
> Sisela mailing list