Thread: [Madwifi-users] Problems with MadWifi trunk
Status: Beta
Brought to you by:
otaku
From: Віталій Т. <ti...@gm...> - 2009-01-21 18:57:37
|
Hello. I've upgraded to OpenSuse 11.1 and started having problems with my TP-Link card (identified as Atheros AR2414 chip found (MAC 7.9, PHY 2112A 4.5, Radio 5.6)). First, It've tried to use ath5k. The driver does not hang, but gives very low throughput and packet looses. Next I've installed madwifi 0.9.4 from Opensuse 11.1 repository at madwifi site. It've given me good throughput, but my notebook've started to hang (with blinking Caps Lock/Scroll Lock - so it look like kernel trap?) OK, I did download trunk from http://svn.madwifi-project.org/madwifi/trunk/(rev 3913).... and got ath5k throughput and packet looses. Next thing I've tried is to back my kernel to 11.0 one and use 0.9.4 - this combination works OK. No hangs, good throughput. Thunk on old kernel also gives problems. So, I have two problems now that I can't handle: 1) 0.9.4 release hangs on 2.6.27 (may be I should've built it from scratch?) 2) MadWifi Trunk / ath5k works slowly (rates are jumping from 1Mb to 34Mb, a lot of packet lost). The one thing that is strange for me is that trunk dmesg output is much different from 0.9.4 - so that I could think I am building ath5k, but SVN url seems to be correct and I can see 0.9.4 in tags nearby. |
From: Pavel R. <pr...@gn...> - 2009-01-21 19:48:52
|
On Wed, 2009-01-21 at 20:57 +0200, Віталій Тимчишин wrote: > So, I have two problems now that I can't handle: > 1) 0.9.4 release hangs on 2.6.27 (may be I should've built it from > scratch?) Maybe you have this problem? https://madwifi-project.org/ticket/1903 If you are trying to set channel in AP mode, please do so when the interface is down. > 2) MadWifi Trunk / ath5k works slowly (rates are jumping from 1Mb to > 34Mb, a lot of packet lost). > The one thing that is strange for me is that trunk dmesg output is > much different from 0.9.4 - so that I could think I am building ath5k, > but SVN url seems to be correct and I can see 0.9.4 in tags nearby. Please try this command: readlink /sys/class/net/wlan0/device/driver Replace "wlan0" with the name of the interface you are using. That should give you the actual driver name. -- Regards, Pavel Roskin |
From: Віталій Т. <ti...@gm...> - 2009-01-22 07:41:56
|
2009/1/21 Pavel Roskin <pr...@gn...> > On Wed, 2009-01-21 at 20:57 +0200, Віталій Тимчишин wrote: > > > So, I have two problems now that I can't handle: > > 1) 0.9.4 release hangs on 2.6.27 (may be I should've built it from > > scratch?) > > Maybe you have this problem? > https://madwifi-project.org/ticket/1903 > > If you are trying to set channel in AP mode, please do so when the > interface is down. Nope, I am using it in regular mode - connecting to same brand (TP-Link) and features (TurboG) WIFI router. > > 2) MadWifi Trunk / ath5k works slowly (rates are jumping from 1Mb to > > 34Mb, a lot of packet lost). > > The one thing that is strange for me is that trunk dmesg output is > > much different from 0.9.4 - so that I could think I am building ath5k, > > but SVN url seems to be correct and I can see 0.9.4 in tags nearby. > > Please try this command: > > readlink /sys/class/net/wlan0/device/driver > > Replace "wlan0" with the name of the interface you are using. That > should give you the actual driver name. > I am sure it is the driver I've just built. I am checking by module names, using modprobe ath_pci to load. Also they use leds in different way: MadWifi uses both, ath5k uses only one led. For everyone to understand me, here is 0.9.4 output: --- Jan 21 20:34:29 thinkpad kernel: ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) Jan 21 20:34:29 thinkpad kernel: wlan: 0.9.4 Jan 21 20:34:29 thinkpad kernel: ath_pci: 0.9.4 Jan 21 20:34:29 thinkpad kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 Jan 21 20:34:29 thinkpad kernel: ath_rate_sample: 1.2 (0.9.4) Jan 21 20:34:29 thinkpad kernel: wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Jan 21 20:34:29 thinkpad kernel: wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Jan 21 20:34:29 thinkpad kernel: wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Jan 21 20:34:29 thinkpad kernel: wifi0: H/W encryption support: WEP AES AES_CCM TKIP Jan 21 20:34:29 thinkpad kernel: wifi0: mac 7.9 phy 4.5 radio 5.6 Jan 21 20:34:29 thinkpad kernel: wifi0: Use hw queue 1 for WME_AC_BE traffic Jan 21 20:34:29 thinkpad kernel: wifi0: Use hw queue 0 for WME_AC_BK traffic Jan 21 20:34:29 thinkpad kernel: wifi0: Use hw queue 2 for WME_AC_VI traffic Jan 21 20:34:29 thinkpad kernel: wifi0: Use hw queue 3 for WME_AC_VO traffic Jan 21 20:34:29 thinkpad kernel: wifi0: Use hw queue 8 for CAB traffic Jan 21 20:34:29 thinkpad kernel: wifi0: Use hw queue 9 for beacons Jan 21 20:34:29 thinkpad kernel: wifi0: Atheros 5212: mem=0x34000000, irq=11 --- Here is trunk output: --- Jan 21 20:27:38 thinkpad kernel: AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133) Jan 21 20:27:38 thinkpad kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 Jan 21 20:27:39 thinkpad kernel: MadWifi: ath_attach: Switching rfkill capability off. Jan 21 20:27:39 thinkpad kernel: wifi0: Atheros AR2414 chip found (MAC 7.9, PHY 2112A 4.5, Radio 5.6) Jan 21 20:27:39 thinkpad kernel: ath_pci: wifi0: Atheros 5212: mem=0x34000000, irq=11 --- Here is ath5k output: --- Jan 14 20:40:37 thinkpad kernel: ath5k_pci 0000:02:00.0: enabling device (0000 -> 0002) Jan 14 20:40:37 thinkpad kernel: ath5k_pci 0000:02:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11 Jan 14 20:40:37 thinkpad kernel: ath5k_pci 0000:02:00.0: registered as 'phy0' Jan 14 20:40:37 thinkpad kernel: phy0: Selected rate control algorithm 'pid' Jan 14 20:40:37 thinkpad kernel: ath5k phy0: Atheros AR2414 chip found (MAC: 0x79, PHY: 0x45) --- It looks like trunk & ath5k are using same HAL or something like that. |
From: Pavel R. <pr...@gn...> - 2009-01-22 17:52:53
|
On Thu, 2009-01-22 at 09:41 +0200, Віталій Тимчишин wrote: > I am sure it is the driver I've just built. > I am checking by module names, using modprobe ath_pci to load. Also > they use leds in different way: MadWifi uses both, ath5k uses only one > led. > For everyone to understand me, here is 0.9.4 output: > --- > Jan 21 20:34:29 thinkpad kernel: ath_hal: 0.9.18.0 (AR5210, AR5211, > AR5212, RF5111, RF5112, RF2413, RF5413) It looks like you are getting it from the system logs. You may be missing some messages from the kernel that don't have sufficient level to be logged. Use "dmesg" command to see all kernel messages. > It looks like trunk & ath5k are using same HAL or something like that. ath5k doesn't use HAL. -- Regards, Pavel Roskin |
From: Віталій Т. <ti...@gm...> - 2009-01-22 20:59:13
|
2009/1/22 Pavel Roskin <pr...@gn...> > On Thu, 2009-01-22 at 09:41 +0200, Віталій Тимчишин wrote: > > > I am sure it is the driver I've just built. > > I am checking by module names, using modprobe ath_pci to load. Also > > they use leds in different way: MadWifi uses both, ath5k uses only one > > led. > > For everyone to understand me, here is 0.9.4 output: > > --- > > Jan 21 20:34:29 thinkpad kernel: ath_hal: 0.9.18.0 (AR5210, AR5211, > > AR5212, RF5111, RF5112, RF2413, RF5413) > > It looks like you are getting it from the system logs. You may be > missing some messages from the kernel that don't have sufficient level > to be logged. Use "dmesg" command to see all kernel messages. It has the same content. Also at boot I have message that ath_hal taints kernel. Actually it does not matter. What matters for me is that both trunk madwifi and ath5k from OpenSuse 11.1 distribution has same problem with my setup. |
From: Віталій Т. <ti...@gm...> - 2009-01-26 22:43:31
|
OK, I did a search&test on SVN and have found out that rev 3548 makes harm for me (low speed). 3547 is OK. BTW: To perform iterations faster I had to find out how to get results (good/slow speed) very fast. I've found out that while any driver can perform good right after it was loaded, fixing rate for low speed driver to 54M produces low speed. One can later set it to auto again, but speed will still be low. For good driver, it is usually OK while fixed at 54M. At times it is not OK(rarely), one can set to auto to get regular 17-19Mb/s of iperf speed (I've had 3.5MB/s ~= 28Mb/s download speed at OpenSuse 10.3 before the upgrade, but it seems that this would be another reason search). Note: all the tests are done from same place, usual statistics is: Bit Rate=54 Mb/s Tx-Power:18 dBm Sensitivity=1/1 Link Quality=41/70 Signal level=-52 dBm Noise level=-93 dBm |
From: Pavel R. <pr...@gn...> - 2009-04-06 04:42:09
|
On Tue, 2009-01-27 at 00:17 +0200, Віталій Тимчишин wrote: > OK, I did a search&test on SVN and have found out that rev 3548 makes > harm for me (low speed). 3547 is OK. Sorry for the late reply. The 3548 patch is buggy, as documented in https://madwifi-project.org/ticket/1922 The revision 3616 fixes that problem. I don't know if the fix is fully correct. In some cases it's easy to verify, but some calls don't set bf_numdescff to 0, so it's not obvious. Surprisingly, further changes made the calculation introduced in r3616 irrelevant. The "ds" variable in ath_tx_txqaddbuf() is currently write-only and can be removed. Anyway, I suggest that you try revision 3616 and later. We know that the 3548-3616 range is bad. -- Regards, Pavel Roskin |