DWL-G520 rev B3 not working under ath driver (was Re: ndis0: link down after idle time)
I've tracked this down to an error in src/share/misc/pci_vendors.h,v 1.30.2.2; and from browsing in cvsweb it appears that no current version of this file has the correct data: 168CAtheros Communications Inc. 0007AR5000 802.11a Wireless Adapter 0011AR5210 802.11a Wireless Adapter 0012AR5211 802.11a/b/g Mini-PCI Wireless Adapter 0013AR5213 802.11a/b/g Wireless Adapter but the current output of http://www.pcidatabase.com/reports.php?type=tab-delimeted is this: 168CAtheros Communications Inc. 0007AR5000 802.11a Wireless Adapter 0011AR5210 802.11a Wireless Adapter 0012AR5211 802.11a/b/g Mini-PCI Wireless Adapter 0013AR5212, AR5213 802.11a/b/g Wireless Adapter In the current pci vendors list, 168C 0013 should indicate both AR5212 and AR5213. The 5213 is apparently an a/b/g chip used in the DWL-G530, and since I have the DWL-G520 that uses the AR5212 I do have a supported card under the ath driver.. but the driver failed to load, so something is wrong. I will try the ath driver again soon and post results for it. On 1/24/2005, Hendrik Spiegel [EMAIL PROTECTED] wrote: Hi, I use the same D_Link card as you do, although I use it successfully with the native ath driver. On Sun, 2005-01-23 at 22:23 -0600, [EMAIL PROTECTED] wrote: I am running FreeBSD 5.3-stable and have had limited success with a d-link DWL-G520 card, rev B3 (atheros ar5213 chipset). I had hoped that I would have purchased a card with a supported native driver (ath), You probably did ;) The card works well, albeit only in 802.11b 11mb/s adhoc mode, I can reproduce this with the native driver. 11g is sometimes down to a few kBit and 500-1000ms when I switch to 11b speed is ok and times are 25-40ms. that I can't figure out. After about an hour or so of idle time on the link, the interface brings itself down and cannot be resurrected unless I issue a command through ifconfig to bring the interface up again. Does anyone else experience this problem and/or have a solution? I will watch this - I do not remember exactly if there were such problems. FreeBSD mars.local 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #0: Mon Jan 10 23:27:32 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BTKERNEL i386 [EMAIL PROTECTED]:9:0: class=0x02 card=0x3a131186 chip=0x0013168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5213 802.11a/b/g Wireless Adapter' class= network subclass = ethernet ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 ether 00:0f:3d:ab:9a:b6 media: IEEE 802.11 Wireless Ethernet autoselect mode 11b (DS/11Mbps) status: associated ssid LokalHorst 1:LokalHorst channel 4 authmode OPEN powersavemode OFF powersavesleep 100 rtsthreshold 2312 protmode CTS wepmode MIXED weptxkey 1 wepkey 1:104-bit ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ndis0: link down after idle time
Hendrik - are you certain it is a rev. B3 with the ar5213 chipset? The ath driver on my box attempts to hook, but fails. I get these kernel messages: ath0: Atheros 5212 mem 0xd680-0xd68 0 irq 5 at device 10.0 on pci0 ath0: unable to attach hardware; HAL status 13 kernel: device_attach: ath0 attach returned 6 On 1/24/2005, Hendrik Spiegel [EMAIL PROTECTED] wrote: Hi, I use the same D_Link card as you do, although I use it successfully with the native ath driver. On Sun, 2005-01-23 at 22:23 -0600, [EMAIL PROTECTED] wrote: I am running FreeBSD 5.3-stable and have had limited success with a d-link DWL-G520 card, rev B3 (atheros ar5213 chipset). I had hoped that I would have purchased a card with a supported native driver (ath), You probably did ;) The card works well, albeit only in 802.11b 11mb/s adhoc mode, I can reproduce this with the native driver. 11g is sometimes down to a few kBit and 500-1000ms when I switch to 11b speed is ok and times are 25-40ms. that I can't figure out. After about an hour or so of idle time on the link, the interface brings itself down and cannot be resurrected unless I issue a command through ifconfig to bring the interface up again. Does anyone else experience this problem and/or have a solution? I will watch this - I do not remember exactly if there were such problems. FreeBSD mars.local 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #0: Mon Jan 10 23:27:32 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BTKERNEL i386 [EMAIL PROTECTED]:9:0: class=0x02 card=0x3a131186 chip=0x0013168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5213 802.11a/b/g Wireless Adapter' class= network subclass = ethernet ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 ether 00:0f:3d:ab:9a:b6 media: IEEE 802.11 Wireless Ethernet autoselect mode 11b (DS/11Mbps) status: associated ssid LokalHorst 1:LokalHorst channel 4 authmode OPEN powersavemode OFF powersavesleep 100 rtsthreshold 2312 protmode CTS wepmode MIXED weptxkey 1 wepkey 1:104-bit ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ndis0: link down after idle time
That's what the kernel tells me during boot: ath0: Atheros 5212 mem 0xde10-0xde10 irq 5 at device 9.0 on pci0 ath0: mac 5.9 phy 4.3 5ghz radio 4.6 ath0: Ethernet address: 00:0f:3d:ab:9a:b6 ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Mine is also identified as the 5212. But I saw that my hardware version is B2 and the firmware versionn is 3.1.6. You do not seem to be the only one with your problem: This guy gets the same message as you did, but it is supposed to be fixed: http://lists.freebsd.org/pipermail/freebsd-current/2003-November/014227.html According to this link an European B3 does not work with linux either: http://madwifiwiki.thewebhost.de/wiki/DLinkDWLG520 sysctl dev.ath dev.ath.0.%desc: Atheros 5212 dev.ath.0.%driver: ath dev.ath.0.%location: slot=9 function=0 dev.ath.0.%pnpinfo: vendor=0x168c device=0x0013 subvendor=0x1186 subdevice=0x3a13 class=0x02 dev.ath.0.%parent: pci0 BTW: Are you German? I just wondered because your SSID was deutschland in your initial posting. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ndis0: link down after idle time
Sorry, I should read first and post afterwards :) According to the drivers source HAL_STATUS 13 means Hardware revision not supported. Am Montag, den 24.01.2005, 09:02 -0600 schrieb [EMAIL PROTECTED]: Hendrik - are you certain it is a rev. B3 with the ar5213 chipset? The ath driver on my box attempts to hook, but fails. I get these kernel messages: ath0: Atheros 5212 mem 0xd680-0xd68 0 irq 5 at device 10.0 on pci0 ath0: unable to attach hardware; HAL status 13 kernel: device_attach: ath0 attach returned 6 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ndis0: link down after idle time
I am running FreeBSD 5.3-stable and have had limited success with a d-link DWL-G520 card, rev B3 (atheros ar5213 chipset). I had hoped that I would have purchased a card with a supported native driver (ath), but alas! The card was supposed to have used the 5212 chipset, which is supported by the ath driver. The ndis driver will only bring the link up if the media is forced to adhoc mode, which seems to be common from my limited viewing of reports in the mailing lists. The card works well, albeit only in 802.11b 11mb/s adhoc mode, but there is a major problem that I can't figure out. After about an hour or so of idle time on the link, the interface brings itself down and cannot be resurrected unless I issue a command through ifconfig to bring the interface up again. Does anyone else experience this problem and/or have a solution? Attached below is all pertinent information I can think of: uname -a output: FreeBSD [hidden] 5.3-STABLE FreeBSD 5.3-STABLE #7: Tue Jan 18 21:47:38 CST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/HAUTLOS i386 pciconf -lv output for the device: [EMAIL PROTECTED]:10:0:class=0x02 card=0x3a131186 chip=0x0013168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5213 802.11a/b/g Wireless Adapter' class= network subclass = ethernet ifconfig ndis0: ndis0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.2.1 netmask 0xff00 broadcast 192.168.2.255 inet6 fe80::211:95ff:fe8d:1379%ndis0 prefixlen 64 scopeid 0x1 ether 00:11:95:8d:13:79 media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps adhoc) status: associated ssid deutschland 1:deutschland channel 6 authmode OPEN powersavemode OFF powersavesleep 100 rtsthreshold 2312 protmode CTS wepmode OFF weptxkey 1 available sysctls for dev.ndis.0: dev.ndis.0.%desc: D-Link AirPlus DWL-G520 Wireless PCI Adapter(rev.B) dev.ndis.0.%driver: ndis dev.ndis.0.%location: slot=10 function=0 dev.ndis.0.%pnpinfo: vendor=0x168c device=0x0013 subvendor=0x1186 subdevice=0x3a13 class=0x02 dev.ndis.0.%parent: pci0 dev.ndis.0.InitFile: A3AB.ini dev.ndis.0.aifs: 2 dev.ndis.0.cwmin: 15 dev.ndis.0.MapRegisters: 256 dev.ndis.0.NetworkAddress: dev.ndis.0.sleepMode: 0 dev.ndis.0.tpc: 0 dev.ndis.0.shortPreamble: 1 dev.ndis.0.radioEnable: 1 dev.ndis.0.BusType: 5 dev.ndis.0.AdHocChannel: 2437 dev.ndis.0.AwakeTimePerf: 200 dev.ndis.0.beaconInterval: 100 dev.ndis.0.bkScanEnable: 1 dev.ndis.0.bssType: 1 dev.ndis.0.ccode: US dev.ndis.0.clist: dev.ndis.0.defaultKey: 0 dev.ndis.0.EncryptionAlg: 2 dev.ndis.0.FragThreshold: 2346 dev.ndis.0.HwTxRetries: 4 dev.ndis.0.privacyInvoked: 0 dev.ndis.0.QoS: 0 dev.ndis.0.rateCtrlEnable: 1 dev.ndis.0.RTSThreshold: 2346 dev.ndis.0.scanType: 2 dev.ndis.0.SwTxRetryScale: 6 dev.ndis.0.SSID: default dev.ndis.0.NetBand: 28 dev.ndis.0.AdHocBand: 0 dev.ndis.0.NicType: 0 dev.ndis.0.p24GAG: 2 dev.ndis.0.p5GAG: 4 dev.ndis.0.abolt: 255 dev.ndis.0.Environment: 1 dev.ndis.0.NdisVersion: 0x00050001 dev.ndis.0.InterruptNumber: 5 dev.ndis.0.DriverDesc: UNSET dev.ndis.0.BusConfig: UNSET dev.ndis.0.TriggerAdj: UNSET dev.ndis.0.CalibrationTime: UNSET dev.ndis.0.gpioPinFunc0: UNSET dev.ndis.0.gpioPinFunc1: UNSET dev.ndis.0.TransmitRate11a: UNSET dev.ndis.0.TransmitRate11b: UNSET dev.ndis.0.TransmitRate11g: UNSET dev.ndis.0.TransmitRate108g: UNSET dev.ndis.0.TransmitRateTurbo: UNSET dev.ndis.0.TransmitRate11Xr: UNSET dev.ndis.0.antennaSwitch: UNSET dev.ndis.0.writeBlockSize: UNSET dev.ndis.0.MinimumRate11a: UNSET dev.ndis.0.MinimumRate11b: UNSET dev.ndis.0.MinimumRate11g: UNSET dev.ndis.0.MinimumRate108g: UNSET dev.ndis.0.MinimumRateTurbo: UNSET dev.ndis.0.MinimumRate11Xr: UNSET dev.ndis.0.iqOverride: UNSET dev.ndis.0.iqLogCountMax: UNSET dev.ndis.0.iCoff: UNSET dev.ndis.0.qCoff: UNSET dev.ndis.0.modeCTS: UNSET dev.ndis.0.rateCTS: UNSET dev.ndis.0.shortSlotTime: UNSET dev.ndis.0.gdraft5: UNSET dev.ndis.0.protectionType: UNSET dev.ndis.0.Ssid2: UNSET dev.ndis.0.Ssid3: UNSET dev.ndis.0.XrFragThreshold: UNSET dev.ndis.0.atimWindow: UNSET dev.ndis.0.cfpDuration: UNSET dev.ndis.0.RD: UNSET dev.ndis.0.ignore11dBeacon: UNSET dev.ndis.0.quietDuration: UNSET dev.ndis.0.quietOffset: UNSET dev.ndis.0.quietAckCtsAllow: UNSET dev.ndis.0.extendedChanMode: UNSET dev.ndis.0.overRideTxPower: UNSET dev.ndis.0.enableFCC3: UNSET dev.ndis.0.capLinkSp: UNSET dev.ndis.0.keyLength0: UNSET dev.ndis.0.key0: UNSET dev.ndis.0.keyLength1: UNSET dev.ndis.0.key1: UNSET dev.ndis.0.keyLength2: UNSET dev.ndis.0.key2: UNSET dev.ndis.0.keyLength3: UNSET dev.ndis.0.key3: UNSET dev.ndis.0.uniqKeyLength: UNSET dev.ndis.0.uniqKey: UNSET dev.ndis.0.leapEnabled: UNSET dev.ndis.0.leapUserName: UNSET dev.ndis.0.leapUserPasswdLen: UNSET dev.ndis.0.leapUserPasswd: UNSET dev.ndis.0.leapTimeout: UNSET dev.ndis.0.CardCfgId: UNSET dev.ndis.0.authType: UNSET dev.ndis.0.authTypeUseOnly: UNSET dev.ndis.0.wpaEnabled: UNSET
Re: ndis0: link down after idle time
Hi, I use the same D_Link card as you do, although I use it successfully with the native ath driver. On Sun, 2005-01-23 at 22:23 -0600, [EMAIL PROTECTED] wrote: I am running FreeBSD 5.3-stable and have had limited success with a d-link DWL-G520 card, rev B3 (atheros ar5213 chipset). I had hoped that I would have purchased a card with a supported native driver (ath), You probably did ;) The card works well, albeit only in 802.11b 11mb/s adhoc mode, I can reproduce this with the native driver. 11g is sometimes down to a few kBit and 500-1000ms when I switch to 11b speed is ok and times are 25-40ms. that I can't figure out. After about an hour or so of idle time on the link, the interface brings itself down and cannot be resurrected unless I issue a command through ifconfig to bring the interface up again. Does anyone else experience this problem and/or have a solution? I will watch this - I do not remember exactly if there were such problems. FreeBSD mars.local 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #0: Mon Jan 10 23:27:32 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BTKERNEL i386 [EMAIL PROTECTED]:9:0: class=0x02 card=0x3a131186 chip=0x0013168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5213 802.11a/b/g Wireless Adapter' class= network subclass = ethernet ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 ether 00:0f:3d:ab:9a:b6 media: IEEE 802.11 Wireless Ethernet autoselect mode 11b (DS/11Mbps) status: associated ssid LokalHorst 1:LokalHorst channel 4 authmode OPEN powersavemode OFF powersavesleep 100 rtsthreshold 2312 protmode CTS wepmode MIXED weptxkey 1 wepkey 1:104-bit ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
