> > > I'm bailing here. I don't remember 3.4 well enough.
> >
> > I was afraid of that. I've been meaning to upgrade to 3.7 for
> > a while -- is it
> > likely to make that big of a difference if I upgrade? If I
> > were to still
> > experience this problem with 3.7, might you be able to offer
On Tue, 20 Sep 2005 12:49:16 +0100, Stuart Henderson wrote:
>--On 19 September 2005 20:24 -0400, Alex Kirk wrote:
>
>>> > wi0 at pci0 dev 12 function 0 "National Datacomm Corp NCP130 Rev
>>> > A2" rev 0x01: irq 9 wi0: PRISM2 HWB3163 rev.B, Firmware 0.3.0
>>> > (primary), 1.7.1 (station), address 0
--On 19 September 2005 20:24 -0400, Alex Kirk wrote:
> wi0 at pci0 dev 12 function 0 "National Datacomm Corp NCP130 Rev
> A2" rev 0x01: irq 9 wi0: PRISM2 HWB3163 rev.B, Firmware 0.3.0
> (primary), 1.7.1 (station), address 00:80:c6:e3:72:2c
It's ancient but it should work.
It was the most curr
From: Alex Kirk [mailto:[EMAIL PROTECTED]
> > I'm bailing here. I don't remember 3.4 well enough.
>
> I was afraid of that. I've been meaning to upgrade to 3.7 for
> a while -- is it
> likely to make that big of a difference if I upgrade? If I
> were to still
> experience this problem with 3.7,
> > shorty.kirknet.net:~$ dmesg
> > OpenBSD 3.4-stable (GENERIC) #0: Sun Sep 18 18:29:41 EDT 2005
>
> I'm bailing here. I don't remember 3.4 well enough.
I was afraid of that. I've been meaning to upgrade to 3.7 for a while -- is it
likely to make that big of a difference if I upgrade? If I were
> It was the most current I could find for this particular chipset
The chipset is ancient.
> shorty.kirknet.net:~$ dmesg
> OpenBSD 3.4-stable (GENERIC) #0: Sun Sep 18 18:29:41 EDT 2005
I'm bailing here. I don't remember 3.4 well enough.
First, I apologize for the delay -- I had a very long, hectic day at work.
Meanwhile, thank you for replying.
> > wi0 at pci0 dev 12 function 0 "National Datacomm Corp NCP130 Rev A2" rev
> > 0x01: irq 9 wi0: PRISM2 HWB3163 rev.B, Firmware 0.3.0 (primary), 1.7.1
> > (station), address 00:80:c6:e3:
> Restart the machine and if your clients still can't connect put the
> wireless
> interface into debug mode:
Is there a recommended way to do this without a reboot?
> wi0 at pci0 dev 12 function 0 "National Datacomm Corp NCP130 Rev A2" rev
> 0x01: irq 9 wi0: PRISM2 HWB3163 rev.B, Firmware 0.3.0 (primary), 1.7.1
> (station), address 00:80:c6:e3:72:2c
It's ancient but it should work.
> ...my wireless configuration:
No obvious problem there.
> Meanwhile, runn
On Sun, 18 Sep 2005 19:22:32 -0400, Alex Kirk <[EMAIL PROTECTED]>
wrote:
>...my wireless configuration:
>
>shorty.kirknet.net:~$ wicontrol
...
>Promiscuous mode: [ Off ]
...
>wi0: flags=8943 mtu 1500
I'm not sure if it's actually relevant to your connect problems but I
notic
10 matches
Mail list logo