Re: DStumbler / BSD-AirTools Error with new Wi code?
* Bruce M Simpson [Fr, 21 Nov 2003 at 20:36 GMT]: > On Wed, Nov 19, 2003 at 05:32:37PM -0800, Sean Chittenden wrote: >> I don't know if Lucent cards are supported or not. How old is your >> kernel, btw? You should update to -CURRENT as there have been many >> wlan fixes since 5.1-RELEASE. -sc > > To the best of my knowledge, only PRISM2 has ever been supported by the > dstumbler port we have. Lucent cards worked fine with dstumbler and 4.x. I haven't tried the new version with CURRENT yet. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DStumbler / BSD-AirTools Error with new Wi code?
On Wed, Nov 19, 2003 at 05:32:37PM -0800, Sean Chittenden wrote: > I don't know if Lucent cards are supported or not. How old is your > kernel, btw? You should update to -CURRENT as there have been many > wlan fixes since 5.1-RELEASE. -sc To the best of my knowledge, only PRISM2 has ever been supported by the dstumbler port we have. BMS ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DStumbler / BSD-AirTools Error with new Wi code?
> I have been getting the following error when attempting to use dstumbler > with 5.1-RELEASE-p10: > > error: unable to ioctl device socket: Invalid argument > > After much searching around newsgroups/mailing lists it looks like the > Wi(4) code was changed and dstumbler never got updated. I found one patch > that supposedly fixed support on some cards, however, it didn't seem to > work on mine. Has anyone worked on this in -current? Or does anyone know of > patches that aren't in CVS yet that might work? > > Here is my info: > lilshadow# dmesg |grep wi0 > wi0: at port 0x100-0x13f irq 11 > function 0 config 1 on pccard2 > wi0: 802.11 address: 00:02:2d:84:22:18 > wi0: using Lucent Embedded WaveLAN/IEEE > wi0: Lucent Firmware: Station (8.10.1) > wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > > Wireless card works fine otherwise. Have you tried just `dstumbler wi0` ? I need the -o with my Netgear card. $ dmesg | grep wi0 wi0: at port 0x100-0x13f irq 11 function 0 config 1 on pccard0 wi0: 802.11 address: 00:30:ab:11:f6:88 wi0: using RF:PRISM2 MAC:HFA3841 CARD:HWB3163 rev.A wi0: Intersil Firmware: Primary (0.3.0), Station (0.8.3) wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps $ sudo dstumbler wi0 -o [fires up] I don't know if Lucent cards are supported or not. How old is your kernel, btw? You should update to -CURRENT as there have been many wlan fixes since 5.1-RELEASE. -sc -- Sean Chittenden ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DStumbler / BSD-AirTools Error with new Wi code?
I upgraded to 0.3 and installed. However, I'm still getting errors no matter how I run it: dstumbler wi0 -o error: cannot use monitor mode on non-prism2 cards dstumbler wi0 -s error: unable to ioctl device socket: Invalid argument same for just running dstumbler wi0. Any ideas? Sean Chittenden writes: I have been getting the following error when attempting to use dstumbler with 5.1-RELEASE-p10: error: unable to ioctl device socket: Invalid argument After much searching around newsgroups/mailing lists it looks like the Wi(4) code was changed and dstumbler never got updated. I found one patch that supposedly fixed support on some cards, however, it didn't seem to work on mine. Has anyone worked on this in -current? Or does anyone know of patches that aren't in CVS yet that might work? I just updated it yesterday. Update to 0.3 and things should work: dstumbler wi0 -o -sc -- Sean Chittenden -- Ryan "leadZERO" Sommers Gamer's Impact President [EMAIL PROTECTED] ICQ: 1019590 AIM/MSN: leadZERO -= http://www.gamersimpact.com =- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DStumbler / BSD-AirTools Error with new Wi code?
> I have been getting the following error when attempting to use dstumbler > with 5.1-RELEASE-p10: > > error: unable to ioctl device socket: Invalid argument > > After much searching around newsgroups/mailing lists it looks like the > Wi(4) code was changed and dstumbler never got updated. I found one patch > that supposedly fixed support on some cards, however, it didn't seem to > work on mine. Has anyone worked on this in -current? Or does anyone know of > patches that aren't in CVS yet that might work? I just updated it yesterday. Update to 0.3 and things should work: dstumbler wi0 -o -sc -- Sean Chittenden ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
DStumbler / BSD-AirTools Error with new Wi code?
I have been getting the following error when attempting to use dstumbler with 5.1-RELEASE-p10: error: unable to ioctl device socket: Invalid argument After much searching around newsgroups/mailing lists it looks like the Wi(4) code was changed and dstumbler never got updated. I found one patch that supposedly fixed support on some cards, however, it didn't seem to work on mine. Has anyone worked on this in -current? Or does anyone know of patches that aren't in CVS yet that might work? Here is my info: lilshadow# dmesg |grep wi0 wi0: at port 0x100-0x13f irq 11 function 0 config 1 on pccard2 wi0: 802.11 address: 00:02:2d:84:22:18 wi0: using Lucent Embedded WaveLAN/IEEE wi0: Lucent Firmware: Station (8.10.1) wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Wireless card works fine otherwise. Thanks for the help in advance. -- Ryan "leadZERO" Sommers Gamer's Impact President [EMAIL PROTECTED] ICQ: 1019590 AIM/MSN: leadZERO -= http://www.gamersimpact.com =- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
