[BAT] wi0: init failed -- bad or normal?
david
Mon, 15 Apr 2002 22:21:56 +0100
On 13 Apr 2002, at 10:36, Jerry Francus wrote:
here is a plug for my website: www.darkminds.net/wlan
I came across most of the issues possible under freebsd when I
was setting up my box and that website details how I fixed them. I
think the wi0 init failure error is in the hardware configuration page.
Along with numerous other problems. Give it a look and see if it
helps fix your problem.
reagrds,
Dragon - Kin
(david)
> I am having the same problem with the D-Link DWL-650 under FreeBSD 4.4. The
> message is more than an annoyance as it hangs my laptop and I am forced to
> do a hardware reset and reboot. Is there a resolution?
>
> Thanks
> - Jerry
>
> -------------
>
> when I insert my card, the following is what is written to the messages
> file:
> Prism II HWB3163 SST-flash, firmware 0.8 variant 2
>
> Mike Scott, NADA
> Security Systems Engineer
> SAIC Corp. IT Security
>
>
> PGP fingerprint:
> A98A D4D2 43B2 4F37 B086 49A1 6ECE 4B22 F0B4 F44B
>
>
> -----Original Message-----
> From: Mike Shaw [mailto:]
> Sent: Thursday, March 14, 2002 12:56 PM
> To: ; ''
> Subject: RE: [BAT] wi0: init failed -- bad or normal?
>
>
> What's your chipset and firmware on the Dlink? I'm beginning to think my
> card is too 'new'...
>
> I've noticed some other problems, including the anything that makes the
> card go into monitor mode. First, when I use prism2ctl to tell it to go to
> monitor mode, it doesn't have any effect. The promisc. mode programs give
> pcap errors. However, when I run tcpdump and leave it running the programs
> seem to run (although the output is highly suspect.)
>
> In all, it seems to me like the source-mods aren't working, since the
> functionality they enable seems broken. Reasons? As I said, the 2.5
> chipset and/or 1.3 firmware might not 'jive' with the drivers. That's my
> theory anyway. Unfortunately I don't have an older card to try out. I
> also could be doing something boneheaded somewhere, so I'll probably try
> manually applying the mods to watch what's going on.
>
> -Mike
>
> At 11:50 AM 3/14/2002 -0800, Scott, Michael R. wrote:
> >I am running 3.0 -current (as of yesterday) on a Compaq Armada M700, and
> >after manually patching the if_wivar.h, if_wi.c, and wicontrol.c everything
> >is working perfectly for both my Dlink DWL-650 and a Lucent card. I too
> >have a personalized kernel. Ron and I are putting together the patches to
> >send to h1kari for review (since the -current source has changed a _lot_).
> >Hopefully we can get the updated source-mods in cvs shortly.
> >
> >Mike Scott, NADA
> >Security Systems Engineer
> >SAIC Corp. IT Security
> >
> >
> >PGP fingerprint:
> >A98A D4D2 43B2 4F37 B086 49A1 6ECE 4B22 F0B4 F44B
> >
> >
> >-----Original Message-----
> >From: Mike Shaw [mailto:]
> >Sent: Thursday, March 14, 2002 7:26 AM
> >To:
> >Subject: [BAT] wi0: init failed -- bad or normal?
> >
> >
> >I'm using OpenBSD 3.0 - stable on a Compaq Presario laptop. I'm using a
> >DLink DWL-650:
> >
> >wi0 at pcmcia0 function 0 "D, Link DWL-650 11Mbps WLAN Card, Version 01.02"
> >wi0: PRISM 2.5 ISL3873, Firmware 1.3 variant 4, address 00:05<snip>
> >I can forward the whole dmesg if needed, but it's kind of isolated from my
> >other pc's right now.
> >
> >I CVS'd the latest stable/patch source code and applied the source
> >mods. Everything compiled smoothly, but I get
> >
> >wi0: init failed
> >
> >over and over when running dstumbler. Is this an indication of a true
> >failure, or is this something that's a byproduct of scanning?
> >
> >wicontrol seems to work fine.
> >ifconfing-ing the interface up and down has no effect.
> >
> >I did strip down the kernel config a bit, so I'm wondering if I might have
> >hinked something up. Any ideas?
> >
> >Thanks
> >-Mike
> >
> >_______________________________________________
> >Bat mailing list
> >
> >http://lists.dachb0den.com/mailman/listinfo/bat
> >_______________________________________________
>
>
> _______________________________________________
> Bat mailing list
>
> http://lists.dachb0den.com/mailman/listinfo/bat
>