After a few weeks of vacillating I finally decided to join the
wireless set, spurred on by the $150 webgear aviator2.4 2-card kit.

I have it running (limping???) on a Sony 505TX running -current and an
old Intel vs440 motherboard (using one of the isa/pcmcia adaptors).
With the aviator card in the pcmcia slot the Sony complains
continually about a stray irq 7.

    Feb 10 18:52:37 pasillo /netbsd: pcic0 at isa0 port 0x3e0-0x3e1 iomem 0xd0000-0xd3fff
    Feb 10 18:52:37 pasillo /netbsd: pcic0: controller 0 (Intel 82365SL Revision 1) has socket A only
    Feb 10 18:52:37 pasillo /netbsd: pcmcia0 at pcic0 controller 0 socket 0
    Feb 10 18:52:37 pasillo /netbsd: isapnp0: no ISA Plug 'n Play devices found
    Feb 10 18:52:37 pasillo /netbsd: cbb0: interrupting at irq 9
    Feb 10 18:52:37 pasillo /netbsd: cbb0: cacheline 0x0 lattimer 0x20
    Feb 10 18:52:37 pasillo /netbsd: cbb0: bhlc 0x21000 lscp 0x20010100
    Feb 10 18:52:37 pasillo /netbsd: cardslot0 at cbb0 slot 0 flags 1
    Feb 10 18:52:37 pasillo /netbsd: cardbus0 at cardslot0: bus 1 device 0 cacheline 0x0, lattimer 0x20
    Feb 10 18:52:37 pasillo /netbsd: pcmcia1 at cardslot0
    Feb 10 18:52:37 pasillo /netbsd: ray0 at pcmcia1 function 0: WebGear, PC Card WLAN Adapter, Version 4.88 Jan 1999
    Feb 10 18:52:37 pasillo /netbsd: ray0: firmware version 85
    Feb 10 18:52:37 pasillo /netbsd: ray0: 802.11 address 00:00:f1:11:76:4f
    Feb 10 18:52:37 pasillo /netbsd: ray0: supplying EUI64: 00:00:f1:ff:fe:11:76:4f
    Feb 10 18:52:38 pasillo /netbsd: biomask efc5 netmask efc5 ttymask ffc7
    Feb 10 18:52:38 pasillo /netbsd: pcic0: controller 0 detecting irqs with mask 0xdeb8:
    Feb 10 18:52:38 pasillo /netbsd: pcic0: no available irq, will poll for card insertion and removal
    Feb 10 18:52:38 pasillo /netbsd: IPsec: Initialized Security Association Processing.
    Feb 10 18:52:38 pasillo /netbsd: boot device: wd0
    Feb 10 18:52:38 pasillo /netbsd: root on wd0a dumps on wd0b
    Feb 10 18:52:38 pasillo /netbsd: root file system type: ffs
    Feb 10 18:52:38 pasillo /netbsd: ray0: starting DAD for fe80:0001::0200:f1ff:fe11:764f
    Feb 10 18:52:38 pasillo /netbsd: ray0: DAD complete for fe80:0001::0200:f1ff:fe11:764f - no duplicates found
    Feb 10 18:52:38 pasillo /netbsd: stray interrupt 7
    Feb 10 18:52:37 pasillo savecore: no core dump
    Feb 10 18:52:38 pasillo last message repeated 3 times
    Feb 10 18:52:38 pasillo /netbsd: stray interrupt 7; stopped logging

Another problem (most likely related) is the card will wedge up every
5-10 minutes or so, usually under heavy load.  One has to ifconfig it
down and up to get it unstuck.  Running netscape on a desktop machine
and sending the X packets across the airwaves will reliably wedge the
card within seconds.  Ironically http://www.raylink.com/ will kill it
before the first half screen is drawn.

On the netbsd configuration side of things, was the issue of
interfaces coming and going when one plugs/unplugs cards.  Some
programs (like dhclient) get uppity when one gives them a list like
"dhclient ep0 tlp0 ray0" when only one interface will exist at a time.
I ended up putting this crock in my netstart:

     dhclient $(ifconfig -l | tr ' ' '\012' | egrep 'tlp|ep|ray')

That solved the problem at boot-time, but still required that I
restart dhclient whenever I pulled the ray0 interface and stuck in ep0
or tlp0.  (BTW dhclient with no args will attempt to config all the
gif's faiths etc and get horribly confused.  That was a non-starter.)

How are other folks dealing with their mobile -current systems?

-wolfgang
-- 
       Wolfgang Rupprecht <wolfgang+gnus@dailyplanet.wsrcc.com>
		    http://www.wsrcc.com/wolfgang/
DGPS signals via the Internet  http://www.wsrcc.com/wolfgang/gps/dgps-ip.html