The wi driver did not see my card at first. Thus I fixed that problem. Now I have a new problem. Every time the wi driver is loaded I get this message:
wi0: <D-Link DWL-650 Wireless PC Card RevP> at port 0x280-0x2ff irq 11 function 0 config 1 on pccard0 wi0: timeout in wi_cmd 0x0000; event status 0x0000 wi0: wi_cmd: busy bit won't clear. : intit failed device_attached: wi0 attach returned 6
LinuxFreak wrote:> The wi driver did not see my card at first. Thus I fixed that problem.> Now I have a new problem. Every time the wi driver is loaded I get this> message:>
wi0: <D-Link DWL-650 Wireless PC Card RevP> at port 0x280-0x2ff irq 11> function 0 config 1 on pccard0> wi0: timeout in wi_cmd 0x0000; event status 0x0000> wi0: wi_cmd: busy bit won't clear.> : intit failed> device_attached: wi0 attach returned 6 >
I am using FreeBSD 5.3.>
what revision is the card? if it's not a Prism chip then "fixing" it won't help. i know that many of these used TI instead.
Mike Gleason Jr Couturier 4 February 2005 01:42:31 [ permanent link ]
"LinuxFreak" <aunixaddict@gmail.com> wrote in message news:1107460999.663820.25210@f14g2000cwb.googlegroups.com...> The wi driver did not see my card at first. Thus I fixed that problem.> Now I have a new problem. Every time the wi driver is loaded I get this> message:>
wi0: <D-Link DWL-650 Wireless PC Card RevP> at port 0x280-0x2ff irq 11> function 0 config 1 on pccard0> wi0: timeout in wi_cmd 0x0000; event status 0x0000> wi0: wi_cmd: busy bit won't clear.> : intit failed> device_attached: wi0 attach returned 6>
I am using FreeBSD 5.3.>
I had those with WEP enabled... Consider maybe OpenVPN (which I use and I think is great)
It's frustrating using wireless devices (wi) with FreeBSD because 1-WEP is broken, 2- you're stuck in 2mbit in AP mode.
"LinuxFreak" <aunixaddict@gmail.com> wrote in message> I had those with WEP enabled...> Consider maybe OpenVPN (which I use> and I think is great)>
It's frustrating using wireless devices> (wi) with FreeBSD because 1-WEP is> broken, 2- you're stuck in 2mbit in AP> mode.>
Mike
I'm using a Cisco Aironet 650 card and it appears to work fine. I had a little trouble with it at first, but eventually I got the 128Bit WEP working. Is this problem only with the prism cards? -- Enjoying Freedom Every Day...
The revision is V.P1. I believe it has the Prism3 chipset; though I could be wrong. I have the card working under Linux fine. With FreeBSD I am having this strange problem. Also, notice that the
Begin <1107540264.760608.268390@f14g2000cwb.googlegroups.com> On 2005-02-04, aunixaddict@gmail.com <aunixaddict@gmail.com> wrote:> The revision is V.P1. I believe it has the Prism3 chipset; though I> could be wrong. I have the card working under Linux fine.
Soooo.... do the obvious and fire up linux. Either you can pry enough information out of _its_ dmesg and sundry means of enquiring the hardware to be sure, or you are left with an OS with a working card.
-- j p d (at) d s b (dot) t u d e l f t (dot) n l .
aunixaddict@gmail.com wrote:> The revision is V.P1. I believe it has the Prism3 chipset; though I> could be wrong. I have the card working under Linux fine. With FreeBSD> I am having this strange problem. Also, notice that the>
: intit failed >
line does not say:>
wi0: init failed>
how did you "fix" the problem with it not being found by the wi driver? what driver are you using under linux? output of lsmod would help. if you're using the orinoco driver under linux then it's most likely a prism and FreeBSD just doesn't like it, but i doubt that's the case. if all else fails then you can always try "Project Evil" (ndis wrapper)
