In message <877lglfoal.fsf@redmail.netbsd.org>, Chris G. Demetriou writes:
>right, i had the same problem on my kayaks.  8-)

>it would only let me start reserving space at c8000 (if i recall
>correctly), and it would only let me reserve the first 32KB (or else
>the SCSI bios would fall over).

Well, it turns out that if I reserve space starting at dc000, I can reserve
64k, and I can configure a kernel with this, and ray0 probes.

It doesn't notice returned packets, ever.  If I tcpdump on the laptop, I
see arp requests, and arp responses, on that interface, but the desktop
just thinks the network is dead.

ray0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        nwid NETWORK_NAME
        media: IEEE802.11 FH2 adhoc
        status: active
        inet 192.129.84.130 netmask 0xffffffc0 broadcast 192.129.84.191
        inet6 fe80::200:f1ff:fe11:5d32@ray0 prefixlen 64 scopeid 0x10

Anything look wrong with that?

The other part is
pcic0 at isa0 port 0x3e0-0x3e1 iomem 0xdc000-0xebfff
pcic0: controller 0 (Intel 82365SL Revision 1) has socket A only
pcmcia0 at pcic0 controller 0 socket 0
pcic0: controller 0 detecting irqs with mask 0xdeb8:..9..10
pcic0: using irq 9
[then, later]
ray0 at pcmcia0 function 0: WebGear, PC Card WLAN Adapter, Version 4.88 Jan 1999
ray0: firmware version 85
ray0: supported rates 32:55:55:55:55:55:55:55
ray0: 802.11 address 00:00:f1:11:5d:32
ray0: intr: bad cmd index 255
ray0: intr: bad cmd index 255
ray0: starting DAD for fe80:0010::0200:f1ff:fe11:5d32
ray0: DAD complete for fe80:0010::0200:f1ff:fe11:5d32 - no duplicates found

Dunno what that means.

-s