Re: ath0, Driver support?
Hi! On Tue, 16 Sep 2003 11:21:01 +1200 Marcos Biscaysaqu [EMAIL PROTECTED] wrote: Hi There . I have in comming a couple a Proxim 8480- pcmcia , with Atheros Chipset and 8482- pci . someone knows if this card work on Freebsd? 'man ath' has a list of supported cards. There may be more devices listed in the driver itself. 54Mbit equipment using PCMCIA would be useless since PCMCIA basicly is just ISA and only can transfer ~16Mbit/s. The manpage shows cardbus (= PCI speed) cards which work but (see BUGS) do not support any powersaving modes. Hendrik -- Hendrik Scholz - [EMAIL PROTECTED] - http://raisdorf.net/ drag me, drop me - treat me like an object ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 driver
On Wed, 6 Aug 2003, Sam Leffler wrote: Shouldn't that be 0.9.5.2? I run the latest current, and hw.ath.hal.version is 0.9.5.2. You're right; I committed a slightly older version to FreeBSD than to Linux. Any chance that you could commit the newer version? Or are the differences too marginal? There are no substantive differences. The later version was created to identify some fixes specific to Linux. Sam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 driver
Ive got a Dlink DWL-G520 that Ive installed into a Freebsd system. Ive set up the card with the following ifconfig_ath0=inet 10.0.0.1 netmask 255.255.255.0 ssid daves channel 10 media DS11 mediaopt hostap This system was cvsuped and buildworld about 3 days ago. The card appears to be working because when I try to connect with my PDA it shows full Link and quality, and when I ifconfig ath0 down , the link and quality go down to nothing. However it doesn't give out dhcp addresses over this interface. Im sure my dhcpd.conf is fine because I've used a similar one on a laptop = aka wireless access point that worked very well. So I tried to use dstumbler to see if it could detect the PDA, however it gives me the following error error: unable to ioctl device socket: Operation now in progress and it stays that way. Has anyone had this issue as well or now what it means? Verify you have the latest HAL using sysctl hw.ath The version should be 0.9.5.3 or better (can't remember if I committed .4 or .3). If you have an old version update. Otherwise you might try tapping 802.11 frames with tcpdump on the AP to see what's going on: tcpdump -i ath0 -y IEEE802_11 As to dstumbler, it is intimately tied to the wi driver at the moment. I have a version that works w/ wi and ath drivers but it's a major rewrite and incomplete. If someone wants to pick it up I'd be happy to pass the (incomplete) work on... Sam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 driver
M == M Warner Losh [EMAIL PROTECTED] writes: M The ath driver doesn't work with broadcom hardware. You will need M to write your own driver, or find someone else that can write a M broadcom one for you. OK ... so slap me down... Geez. It certainly has been discussed that the PCI vendor doesn't necessarily have anything to do with the chipset. Simple question ... so many snarky answers. Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 driver
Sam == Sam Leffler [EMAIL PROTECTED] writes: On Wed, 6 Aug 2003, Sam Leffler wrote: Shouldn't that be 0.9.5.2? I run the latest current, and hw.ath.hal.version is 0.9.5.2. You're right; I committed a slightly older version to FreeBSD than to Linux. Any chance that you could commit the newer version? Or are the differences too marginal? Sam There are no substantive differences. The later version was Sam created to identify some fixes specific to Linux. I just have to ask: is this in any way related to the a/b/g network card in my laptop that shows up as: [EMAIL PROTECTED]:3:0: class=0x028000 card=0x00011028 chip=0x432414e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' class= network Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 driver
I just have to ask: is this in any way related to the a/b/g network card in my laptop that shows up as: [EMAIL PROTECTED]:3:0: class=0x028000 card=0x00011028 chip=0x432414e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' class= network if (broadcom == atheros) use ath driver; else ask broadcom for specs on their hardware. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 driver
Sam == Sam Leffler [EMAIL PROTECTED] writes: I just have to ask: is this in any way related to the a/b/g network card in my laptop that shows up as: [EMAIL PROTECTED]:3:0: class=0x028000 card=0x00011028 chip=0x432414e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' class = network Sam if (broadcom == atheros) use ath driver; else ask broadcom Sam for specs on their hardware. I was hoping for some more contructive help on that... like how I might figure this out. Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 driver
In message: [EMAIL PROTECTED] David Gilbert [EMAIL PROTECTED] writes: : M == M Warner Losh [EMAIL PROTECTED] writes: : : M The ath driver doesn't work with broadcom hardware. You will need : M to write your own driver, or find someone else that can write a : M broadcom one for you. : : OK ... so slap me down... Geez. It certainly has been discussed that : the PCI vendor doesn't necessarily have anything to do with the : chipset. Simple question ... so many snarky answers. It is a frequently asked question, so maybe I've gotten a little snarky about it. Please accept my appoligies. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 driver
In message: [EMAIL PROTECTED] David Gilbert [EMAIL PROTECTED] writes: : Sam == Sam Leffler [EMAIL PROTECTED] writes: : : I just have to ask: is this in any way related to the a/b/g network : card in my laptop that shows up as: : : [EMAIL PROTECTED]:3:0: class=0x028000 card=0x00011028 chip=0x432414e4 : rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' class = network : : Sam if (broadcom == atheros) use ath driver; else ask broadcom : Sam for specs on their hardware. : : I was hoping for some more contructive help on that... like how I : might figure this out. The ath driver doesn't work with broadcom hardware. You will need to write your own driver, or find someone else that can write a broadcom one for you. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 driver
Hi, The version should be 0.9.5.3 or better (can't remember if I committed .4 or .3). Shouldn't that be 0.9.5.2? I run the latest current, and hw.ath.hal.version is 0.9.5.2. You're right; I committed a slightly older version to FreeBSD than to Linux. The version The version I have is 0.9.5.2. As to the tcpdump, I get er# tcpdump -i ath0 -y IEEE802_11 tcpdump: data link type DLT_IEEE802_11 tcpdump: listening on ath0 00:18:02.152294 10.0.0.1.netbios-dgm 10.0.0.255.netbios-dgm: NBT UDP PACKET(138) 00:18:02.152502 10.0.0.1.netbios-dgm 10.0.0.255.netbios-dgm: NBT UDP PACKET(138) and thats all that comes up. Does this driver support being set up as an access point yet? I figured it did because ifconfig ath0 mediaopt hostap didnt return any errors. Please let me know if Im doing something wrong. Im sure ive got my *.conf files set up right as I have used them before, however I could be wrong. Thanks for the help David Ive got a Dlink DWL-G520 that Ive installed into a Freebsd system. Ive set up the card with the following00:18:02.152294 10.0.0.1.netbios-dgm 10.0.0.255.netbios-dgm: NBT UDP PACKET(138) 00:18:02.152502 10.0.0.1.netbios-dgm 10.0.0.255.netbios-dgm: NBT UDP PACKET(138) ifconfig_ath0=inet 10.0.0.1 netmask 255.255.255.0 ssid daves channel 10 media DS11 mediaopt hostap This system was cvsuped and buildworld about 3 days ago. The card appears to be working because when I try to connect with my PDA it shows full Link and quality, and when I ifconfig ath0 down , the link and quality go down to nothing. However it doesn't give out dhcp addresses over this interface. Im sure my dhcpd.conf is fine because I've used a similar one on a laptop = aka wireless access point that worked very well. So I tried to use dstumbler to see if it could detect the PDA, however it gives me the following error error: unable to ioctl device socket: Operation now in progress and it stays that way. Has anyone had this issue as well or now what it means? Verify you have the latest HAL using sysctl hw.ath The version should be 0.9.5.3 or better (can't remember if I committed .4 or .3). If you have an old version update. Otherwise you might try tapping 802.11 frames with tcpdump on the AP to see what's going on: tcpdump -i ath0 -y IEEE802_11 As to dstumbler, it is intimately tied to the wi driver at the moment. I have a version that works w/ wi and ath drivers but it's a major rewrite and incomplete. If someone wants to pick it up I'd be happy to pass the (incomplete) work on... Sam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 driver
Verify you have the latest HAL using sysctl hw.ath The version should be 0.9.5.3 or better (can't remember if I committed .4 or .3). Shouldn't that be 0.9.5.2? I run the latest current, and hw.ath.hal.version is 0.9.5.2. You're right; I committed a slightly older version to FreeBSD than to Linux. Sam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 driver
On Wed, 6 Aug 2003, Sam Leffler wrote: Verify you have the latest HAL using sysctl hw.ath The version should be 0.9.5.3 or better (can't remember if I committed .4 or .3). Shouldn't that be 0.9.5.2? I run the latest current, and hw.ath.hal.version is 0.9.5.2. regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
