Date: 2002-01-22 19:42:26 UTC
On Tue, Jan 22, 2002 at 10:59:51AM -0800, Eric Johanson wrote:
> The "Resource in use" makes me think that you have an IRQ conflict.
> I've seen pcmcia try to give out IRQs for existing devices, but you can
> exclude them in /etc/pcmcia.conf (I think...It depends on the distro, some
> are under /etc/pcmcia/*.conf)
Ok, I think I've fixed it, I had excluded irq 3 and it works now without irq 3 excluded. I thought it would use irq 6.
For some reason the range problem with ap mode has gone, and it's as good as adhoc. However it isn't as good as I expected. What range should I expect with wl100s in a house with brick walls?
Is it possible to get signal strength, the bit rate being used etc?
> Otherwise, make sure you don't have any dead pcmcia modules around, that
> could be locking IRQs...
> On Tue, 22 Jan 2002 rob_at_mur.org.uk wrote:
> > Hi
> > I installed hostap on the laptop, but it didn't make any difference. I
> > set the sbc and the laptop to adhoc mode, and the range improved a
> > lot. Something strange is happening with the sbc now though, I don't
> > think I changed anything, appart from pcmcia being loaded in
> > /etc/rc.d. What does the below mean?
> > prism2: prism2.c 0.0.0 2002-01-03 (SSH Communications Security Corp, Jouni Malin
> > en)
> > prism2: (c) SSH Communications Security Corp <jkm_at_ssh.com>
> > prism2: setting Vcc=33 (constant)
> > prism2: CS_EVENT_CARD_INSERTION
> > prism2_config()
> > prism2: setting Vcc=33 (from config)
> > CISTPL_MANFID: 0x0138, 0x0002
> > Checking CFTABLE_ENTRY 0x01 (default 0x01)
> > IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
> > io->flags = 0x0046, io.base=0x0000, len=64
> > prism2: RequestIRQ: Resource in use
> > prism2_release
> > release -> prism2_hw_shutdown
> > prism2: card not configured
> > release <- prism2_hw_shutdown
> > release: CardServices(Release*) done
> > release - done
> > prism2_detach
> > prism2: link->dev == NULL: do not unregister netdevice
> > Cheers
-- Rob Murray