[Madwifi-users] Native Atheros full-duplex support?

[Tom Sharples <tsharples@qo...>]

Hi,

I have an ultra low-latency wireless application that requires full-duplex. There seem to be several ways to do this using a pair of radios at each end of a ptp link, however these methods use e.g. bridging and stp path cost entries to emulate a true full-duplex link, so may not really get us what we need. However, I've seen several references to an "atheros full-duplex" mode and am wondering if that really exists, and if so, whether madwifi supports it. Anyone out here know?

Thanks,

Tom S.

[Madwifi-users] madwifi + minstrel stuck at lowest rate.

[Joe Hershberger <joe.hershberger@gm...>]

Hi,

I'm having an issue with the minstrel rate algorithm in madwifi r4133
and linux 2.6.30 not selecting a rate that is greater than 1 Mbps.  If
I select a fixed rate of 54 Mbps i get much faster throughput.

Looking at the rate_info, it seems that the algorithm is not getting
the feedback it needs.  I'm guessing there is something that is not
plumbed quite right.

Here's that that looks like:

~ # cat /proc/net/madwifi/ath0/rate_info
rate data for node:: 00:25:9c:2a:c8:06
rate     throughput  ewma prob   this prob  this succ/attempt
success    attempts
TtP  1         0.0        0.0        0.0          0(  0)          0           0
     2         0.0        0.0        0.0          0(  0)          0           0
     5.5       0.0        0.0        0.0          0(  0)          0           0
     6         0.0        0.0        0.0          0(  0)          0           0
     9         0.0        0.0        0.0          0(  0)          0           0
    11         0.0        0.0        0.0          0(  0)          0           0
    12         0.0        0.0        0.0          0(  0)          0           0
    18         0.0        0.0        0.0          0(  0)          0           0
    24         0.0        0.0        0.0          0(  0)          0           0
    36         0.0        0.0        0.0          0(  0)          0           0
    48         0.0        0.0        0.0          0(  0)          0           0
    54         0.0        0.0        0.0          0(  0)          0           0

Total packet count::    ideal 31      lookaround 3

The ideal and lookaround packet counts are changing so it is trying.

The machine is a Freescale MPC8313 (powerpc 603e) and the wireless
card is a mini-PCI Silex SX-10WG (AR5005G).

The following in the dmesg traces I get on modprobe:

~ # modprobe ath_pci ratectl=minstrel
wlan: svn r4133 (branch madwifi-0.9.4)
ath_hal: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413,
RF5413, REGOPS_FUNC)
ath_pci: svn r4133 (branch madwifi-0.9.4)
ath_rate_minstrel: Minstrel automatic rate control algorithm 1.2 (svn
r4133 (branch madwifi-0.9.4))
ath_rate_minstrel: Look around rate set to 10%
ath_rate_minstrel: EWMA rolloff level set to 75%
ath_rate_minstrel: Max Segment size in the mrr set to 6000 us
wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps
24Mbps 36Mbps 48Mbps 54Mbps
wifi0: H/W encryption support: WEP AES AES_CCM TKIP
wifi0: mac 7.8 phy 4.5 radio 5.6
wifi0: Use hw queue 1 for WME_AC_BE traffic
wifi0: Use hw queue 0 for WME_AC_BK traffic
wifi0: Use hw queue 2 for WME_AC_VI traffic
wifi0: Use hw queue 3 for WME_AC_VO traffic
wifi0: Use hw queue 8 for CAB traffic
wifi0: Use hw queue 9 for beacons
wifi0: Atheros 5212: mem=0x90000000, irq=48

Thanks for any suggestions,
-Joe

Re: [Madwifi-users] Half and Quarter Channel Support??

[Steve Brown <sbrown@co...>]

  On 07/22/2010 01:35 PM, Shawn wrote:
> I am trying to use a Ubiquity XR9 in Half and Quarter channel modes, but I
> cannot get it to work.
>
> The managed stations sees the access point in half and quarter channel mode
> but they cannot associate to the AP. Works properly in full (20MHz) BW mode.
>
> I've done a ton of reading on here and the web, but I can't seem to get a
> straight answer: Is Half and Quarter channel operation supported by Madwifi? I
> guess particularly with the Ubiquity XR9 card. I spoke with the Ubiquity tech
> support guy and he tells me that Madwifi does NOT support 10MHz and 5MHz
> channels. Yet, I can get the Wiligear 2.4 cards to work in half bandwidth
> modes with Madwifi.... so confused now.
>
> If so, any ideas what could be wrong?
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Madwifi-users mailing list
> Madwifi-users@...
> https://lists.sourceforge.net/lists/listinfo/madwifi-users
Setting the country to 5001 gives channel mappings for all 5, 10 and 20 
MHz channel widths.

The problem I had is that the scanner only used the first channel/width 
combo on each frequency. So, it only scanned 4 instead of the 10 
possible combinations.

Steve

[Madwifi-users] Half and Quarter Channel Support??

[Shawn <shawn.lightfoot@gm...>]

I am trying to use a Ubiquity XR9 in Half and Quarter channel modes, but I 
cannot get it to work.

The managed stations sees the access point in half and quarter channel mode 
but they cannot associate to the AP. Works properly in full (20MHz) BW mode.

I've done a ton of reading on here and the web, but I can't seem to get a 
straight answer: Is Half and Quarter channel operation supported by Madwifi? I 
guess particularly with the Ubiquity XR9 card. I spoke with the Ubiquity tech 
support guy and he tells me that Madwifi does NOT support 10MHz and 5MHz 
channels. Yet, I can get the Wiligear 2.4 cards to work in half bandwidth 
modes with Madwifi.... so confused now.

If so, any ideas what could be wrong? 

Re: [Madwifi-users] MadWifi driver fails to recognize Ubiquity card

[Pavel Roskin <proski@gn...>]

On Wed, 2010-07-14 at 17:52 -0400, Aditya Bhave wrote: 
> Even with the trunk version, the same problem occurs. No wifi0 appears

I guess lshw is wrong and you actually have an AR9220 card.  Please keep
in mind that the output of "lspci -nn" is more useful.

AR9220 is not currently supported, but I made a patch for it.  I'm not
ready to commit it now because it seems somewhat inelegant and most
importantly because I didn't test it on any PCI Express devices yet.

Please test and report results.

Add AR9220 support

From: Pavel Roskin <proski@...>


---
 ath/if_ath_pci.c               |    4 +---
 ath_hal/ah.c                   |   19 +++++++++++++++++++
 ath_hal/ah_eeprom.h            |    1 +
 ath_hal/ah_eeprom_v14.c        |    3 +++
 ath_hal/ah_internal.h          |    3 +++
 ath_hal/ar5416/ar5416.h        |    1 +
 ath_hal/ar5416/ar5416_reset.c  |    5 ++---
 ath_hal/ar5416/ar9280_attach.c |   18 ++++++++++++++----
 8 files changed, 44 insertions(+), 10 deletions(-)

diff --git a/ath/if_ath_pci.c b/ath/if_ath_pci.c
index 71e0fe7..ff41070 100644
--- a/ath/if_ath_pci.c
+++ b/ath/if_ath_pci.c
@@ -114,9 +114,7 @@ static struct pci_device_id ath_pci_id_table[] __devinitdata = {
 	{ 0x168c, 0x0023, PCI_ANY_ID, PCI_ANY_ID },
 	{ 0x168c, 0x0024, PCI_ANY_ID, PCI_ANY_ID },
 	{ 0x168c, 0x0027, PCI_ANY_ID, PCI_ANY_ID },
-#if 0 /* PCI based AR9280 doesn't work yet */
-	{ 0x168c, 0x0029, PCI_ANY_ID, PCI_ANY_ID }, /* AR9280 PCI */
-#endif
+	{ 0x168c, 0x0029, PCI_ANY_ID, PCI_ANY_ID }, /* AR9220 PCI */
 	{ 0x168c, 0x002a, PCI_ANY_ID, PCI_ANY_ID }, /* AR9280 PCI Express */
 	{ 0x168c, 0x9013, PCI_ANY_ID, PCI_ANY_ID }, /* sonicwall */
 	{ 0 }
diff --git a/ath_hal/ah.c b/ath_hal/ah.c
index 668ace7..2cecf93 100644
--- a/ath_hal/ah.c
+++ b/ath_hal/ah.c
@@ -862,6 +862,25 @@ ath_hal_ini_write(struct ath_hal *ah, const HAL_INI_ARRAY *ia,
 	return regWr;
 }
 
+int
+ath_hal_ini_write_masked(struct ath_hal *ah, const HAL_INI_ARRAY *ia,
+	int col, int regWr, uint32_t maskreg, uint32_t mask)
+{
+	int r;
+	uint32_t reg, val;
+
+	for (r = 0; r < ia->rows; r++) {
+		reg = HAL_INI_VAL(ia, r, 0);
+		val = HAL_INI_VAL(ia, r, col);
+		if (reg == maskreg)
+			val &= ~mask;
+
+		OS_REG_WRITE(ah, reg, val);
+		DMA_YIELD(regWr);
+	}
+	return regWr;
+}
+
 void
 ath_hal_ini_bank_setup(uint32_t data[], const HAL_INI_ARRAY *ia, int col)
 {
diff --git a/ath_hal/ah_eeprom.h b/ath_hal/ah_eeprom.h
index 0adfcd1..f308912 100644
--- a/ath_hal/ah_eeprom.h
+++ b/ath_hal/ah_eeprom.h
@@ -99,6 +99,7 @@ enum {
 	AR_EEP_ANTGAINMAX_5,	/* int8_t* */
 	AR_EEP_ANTGAINMAX_2,	/* int8_t* */
 	AR_EEP_WRITEPROTECT,	/* use ath_hal_eepromGetFlag */
+	AR_EEP_PWDCLKIND,	/* int8_t* */
 };
 
 typedef struct {
diff --git a/ath_hal/ah_eeprom_v14.c b/ath_hal/ah_eeprom_v14.c
index 8793d3b..412cf21 100644
--- a/ath_hal/ah_eeprom_v14.c
+++ b/ath_hal/ah_eeprom_v14.c
@@ -120,6 +120,9 @@ v14EepromGet(struct ath_hal *ah, int param, void *val)
 	case AR_EEP_ANTGAINMAX_5:
 		*(int8_t *) val = ee->ee_antennaGainMax[0];
 		return HAL_OK;
+	case AR_EEP_PWDCLKIND:
+		*(int8_t *) val = pBase->pwdclkind;
+		return HAL_OK;
         default:
 		HALASSERT(0);
 		return HAL_EINVAL;
diff --git a/ath_hal/ah_internal.h b/ath_hal/ah_internal.h
index eb452fa..1d8cfd8 100644
--- a/ath_hal/ah_internal.h
+++ b/ath_hal/ah_internal.h
@@ -796,6 +796,9 @@ typedef struct {
 
 extern	int ath_hal_ini_write(struct ath_hal *ah, const HAL_INI_ARRAY *ia,
 		int col, int regWr);
+extern	int ath_hal_ini_write_masked(struct ath_hal *ah,
+		const HAL_INI_ARRAY *ia, int col, int regWr, uint32_t maskreg,
+		uint32_t mask);
 extern	void ath_hal_ini_bank_setup(uint32_t data[], const HAL_INI_ARRAY *ia,
 		int col);
 extern	int ath_hal_ini_bank_write(struct ath_hal *ah, const HAL_INI_ARRAY *ia,
diff --git a/ath_hal/ar5416/ar5416.h b/ath_hal/ar5416/ar5416.h
index d92641a..2c825d4 100644
--- a/ath_hal/ar5416/ar5416.h
+++ b/ath_hal/ar5416/ar5416.h
@@ -77,6 +77,7 @@ struct ath_hal_5416 {
 	uint32_t	ah_extBusy;
 	uint32_t	ah_rx_chainmask;
 	uint32_t	ah_tx_chainmask;
+	uint32_t	ah_pwdclkmask;
 
 	struct ar5416PerCal ah_cal;		/* periodic calibration state */
 };
diff --git a/ath_hal/ar5416/ar5416_reset.c b/ath_hal/ar5416/ar5416_reset.c
index 43013f4..4984c20 100644
--- a/ath_hal/ar5416/ar5416_reset.c
+++ b/ath_hal/ar5416/ar5416_reset.c
@@ -270,10 +270,9 @@ ar5416Reset(struct ath_hal *ah, HAL_OPMODE opmode,
 	    regWrites);
 	OS_REG_WRITE(ah, AR_PHY_ADC_SERIAL_CTL, AR_PHY_SEL_INTERNAL_ADDAC);
 
-	/* XXX Merlin ini fixups */
 	/* XXX Merlin 100us delay for shift registers */
-	regWrites = ath_hal_ini_write(ah, &ahp->ah_ini_modes, modesIndex,
-	    regWrites);
+	regWrites = ath_hal_ini_write_masked(ah, &ahp->ah_ini_modes, modesIndex,
+	    regWrites, AR_AN_TOP2, AH5416(ah)->ah_pwdclkmask);
 #ifdef AH_SUPPORT_AR9280
 	if (AR_SREV_MERLIN_20_OR_LATER(ah)) {
 		regWrites = ath_hal_ini_write(ah, &AH9280(ah)->ah_ini_rxgain,
diff --git a/ath_hal/ar5416/ar9280_attach.c b/ath_hal/ar5416/ar9280_attach.c
index 5281add..b684aa5 100644
--- a/ath_hal/ar5416/ar9280_attach.c
+++ b/ath_hal/ar5416/ar9280_attach.c
@@ -87,6 +87,7 @@ ar9280Attach(uint16_t devid, HAL_SOFTC sc,
 	uint32_t val;
 	HAL_STATUS ecode;
 	HAL_BOOL rfStatus;
+	uint8_t pwdclkind;
 
 	HALDEBUG(AH_NULL, HAL_DEBUG_ATTACH, "%s: sc %p st %p sh %p\n",
 	    __func__, sc, (void*) st, (void*) sh);
@@ -166,6 +167,11 @@ ar9280Attach(uint16_t devid, HAL_SOFTC sc,
 	if (ecode != HAL_OK)
 		goto bad;
 
+	if (!AH_PRIVATE(ah)->ah_ispcie &&
+	    (ath_hal_eepromGet(ah, AR_EEP_PWDCLKIND,
+		&pwdclkind) == HAL_OK) && !pwdclkind)
+		AH5416(ah)->ah_pwdclkmask = AR_AN_TOP2_PWDCLKIND;
+
 	if (!ar5416ChipReset(ah, AH_NULL)) {	/* reset chip */
 		HALDEBUG(ah, HAL_DEBUG_ANY, "%s: chip reset failed\n", __func__);
 		ecode = HAL_EIO;
@@ -334,16 +340,20 @@ ar9280WriteIni(struct ath_hal *ah, const HAL_CHANNEL *chan)
 	OS_REG_WRITE(ah, AR_PHY(0), 0x00000007);
 	OS_REG_WRITE(ah, AR_PHY_ADC_SERIAL_CTL, AR_PHY_SEL_INTERNAL_ADDAC);
 
-	/* XXX Merlin ini fixups */
 	/* XXX Merlin 100us delay for shift registers */
-	regWrites = ath_hal_ini_write(ah, &AH5212(ah)->ah_ini_modes,
-	    modesIndex, regWrites);
 	if (AR_SREV_MERLIN_20_OR_LATER(ah)) {
 		regWrites = ath_hal_ini_write(ah, &AH9280(ah)->ah_ini_rxgain,
 		    modesIndex, regWrites);
 		regWrites = ath_hal_ini_write(ah, &AH9280(ah)->ah_ini_txgain,
 		    modesIndex, regWrites);
-	}
+		regWrites = ath_hal_ini_write_masked(ah,
+		    &AH5212(ah)->ah_ini_modes, modesIndex, regWrites,
+		    AR_AN_TOP2, AH5416(ah)->ah_pwdclkmask);
+
+	} else
+		regWrites = ath_hal_ini_write(ah, &AH5212(ah)->ah_ini_modes,
+		    modesIndex, regWrites);
+
 	/* XXX Merlin 100us delay for shift registers */
 	regWrites = ath_hal_ini_write(ah, &AH5212(ah)->ah_ini_common,
 	    1, regWrites);


-- 
Regards,
Pavel Roskin

Re: [Madwifi-users] unable to put wireless card in monitor mode

[yuva raj <ubuntuv@gm...>]

Hi,

I am very much glad to see the replies.  Thanks a lot for the effort.  The
commands mentioned by Mohammad worked.  The onboard card somehow didnot
work.  I changed new Atheros card and it started working. these were the
commands:

- sudo ifconfig wlan0 down
- sudo iwconfig wlan0 mode monitor
- sudo iwconfig wlan0 channel x
- sudo iwconfig wlan0 essid ......
- sudo ifconfig wlan0 up

--uv

-- 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+  REGISTERED LINUX USER: 406811  +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Re: [Madwifi-users] unable to put wireless card in monitor mode

[Pavel Roskin <proski@gn...>]

On Fri, 2010-07-16 at 13:53 +0530, yuva raj wrote:
> hi,
> 
> I am running Ubuntu 9.10. on Acer Aspire One with following card:
> 
> Ethernet controller: Atheros Communications Inc. AR5001 Wireless
> Network Adapter (rev 01)
> 
> I have madwifi installed. I am trying to put the wlan0 interface to
> monitor mode. For that I wanted to issue the following commands:
> 
> sudo wlanconfig wlan0 destroy
> sudo wlanconfig create wlan1 wlandev wifi0 wlanmode monitor
> sudo wlan<x> up
> 
> But, my first try resulted in
> 
> laptop:~$ sudo wlanconfig wlan0 destroy
> wlanconfig: ioctl: Operation not supported
> 
> Please suggest me necessary steps to put card in monitor mode.

I believe wlan0 was created by some other driver.  If you only have one
wireless device in the system, it must be ath5k.  If you insist on using
MadWifi, you should unload both drivers and then load MadWifi (the
module is called ath_pci).  You can use an option to create a monitor
mode interface on startup:

sudo rmmod ath5k
sudo rmmod ath_pci
sudo modprobe ath_pci autocreate=monitor

Now you can run iwconfig to make sure that the new interface is in
monitor mode.

-- 
Regards,
Pavel Roskin

Re: [Madwifi-users] unable to put wireless card in monitor mode

[Mohammad Abdelhadi <moh.jaser@ie...>]

On Fri, Jul 16, 2010 at 1:00 PM, yuva raj <ubuntuv@...> wrote:

> Hi Mohammad,
>
> Thanks for replying.   But I am still having some trouble.
>
> I did 'iwconfig' and got the wireless interface showing as 'wlan0'  I issue
> the commands
>
> - sudo service network-manager stop
> - sudo wlanconfig ath0 destroy
>
> And for the following :
>
> >sudo wlanconfig ath0 create wlandev wlan0 wlanmode monitor
> wlanconfig: ioctl: Operation not supported
>
> Please help me solve it.
>
> Thanks
> uv
>
>
Hi,

First, make sure that the wireless tools is installed on your system (sudo
apt-get install wireless-tools), then if you have the interface wlan0, you
could try the following:

- sudo ifconfig wlan0 down
- sudo iwconfig wlan0 mode monitor
- sudo iwconfig wlan0 channel x
- sudo iwconfig wlan0 essid ......
- sudo ifconfig wlan0 up

If you have the interface ath, you could try the steps mentioned in my
previous e-mail.

Hope this helps...


Regards
-- 
Mohammad

Re: [Madwifi-users] unable to put wireless card in monitor mode

[Mohammad Abdelhadi <moh.jaser@ie...>]

On Fri, Jul 16, 2010 at 11:23 AM, yuva raj <ubuntuv@...> wrote:

> hi,
>
> I am running Ubuntu 9.10. on Acer Aspire One with following card:
>
> Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network
> Adapter (rev 01)
>
> I have madwifi installed. I am trying to put the wlan0 interface to monitor
> mode. For that I wanted to issue the following commands:
>
> sudo wlanconfig wlan0 destroy
> sudo wlanconfig create wlan1 wlandev wifi0 wlanmode monitor
> sudo wlan<x> up
>
> But, my first try resulted in
>
> laptop:~$ sudo wlanconfig wlan0 destroy
> wlanconfig: ioctl: Operation not supported
>
> Please suggest me necessary steps to put card in monitor mode.
>
> Thanks in advance
> uv.
> --
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> +  REGISTERED LINUX USER: 406811  +
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Madwifi-users mailing list
> Madwifi-users@...
> https://lists.sourceforge.net/lists/listinfo/madwifi-users
>
>
Hi,

You could try the following steps:

- sudo service network-manager stop
- sudo wlanconfig ath0 destroy
- sudo wlanconfig create ath0 wlandev wifi0 wlanmode monitor
- sudo iwconfig ath0 channel x   # the channel that you want to monitor
- sudo iwconfig ath0 essid "...."  # the name of the network that you want
to monitor
- sudo ifconfig ath0 up

Now your card should work in monitor mode..

Hope this helps.

Regards,
-- 
Mohammad

[Madwifi-users] unable to put wireless card in monitor mode

[yuva raj <ubuntuv@gm...>]

hi,

I am running Ubuntu 9.10. on Acer Aspire One with following card:

Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network
Adapter (rev 01)

I have madwifi installed. I am trying to put the wlan0 interface to monitor
mode. For that I wanted to issue the following commands:

sudo wlanconfig wlan0 destroy
sudo wlanconfig create wlan1 wlandev wifi0 wlanmode monitor
sudo wlan<x> up

But, my first try resulted in

laptop:~$ sudo wlanconfig wlan0 destroy
wlanconfig: ioctl: Operation not supported

Please suggest me necessary steps to put card in monitor mode.

Thanks in advance
uv.
-- 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+  REGISTERED LINUX USER: 406811  +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Re: [Madwifi-users] [Madwifi-devel] Sample Rate Implementation

[Derek Smithies <derek@in...>]

On Wed, 14 Jul 2010, Bishal Thapa wrote:

> Hello,  I have a small question regarding the implementation of Sample 
> Rate in "madwifi version 0.9.4" concerning Sample Rate adaptation 
> algorithm's coupling with MRR (Multi Rate Retry). My question is, if we 
> leave MRR enabled (by default) and Sample Rate chosen as the rate 
> adaptation algorithm (by default), and lets say all transmissions at 
> 54Mbps fails, then MRR retries at rate 1Mbps and is successful, does the 
> transmission_time calculation for 54Mbps bit rate now include the time 
> it took to retransmit using 1Mbps? I would really appreciate if someone 
> could answer this question for me. 

Hi, Some years ago I tried the different rate algorithms on offer then.
Sample, amrr and onoe.

They all performed badly. Take the following simple test.

Two nodes running madwifi+some_rate_algorithm.

put two nodes 30cm apart, measure bandwidth.

the measured datarate is good - real good

Insert barrier between minders - the panel of a computer is ideal.
measure throughput. The datarate is bad - as expected.

30 seconds later, remove that barrier.
With all the rate algorithms, the response time is incredibly slow. It may 
take a minute to get back to where it was.

=====>
So I wrote Minstrel, based on an idea from Andrew McGregor.

The basis for the minstrel code was the sample code. I injested much 
coffee, and had many discussions with Andrew, but could not work out the 
reasons for the accounting in sample.

When Minstrel is put to the above test - measured throuhput is back to 
perfect in under 5 seconds - every time.

let me be more definate.
Abandon Sample. The idea behind sample (to use ewma) is good.
The implementation in sample is poor.

The evidence on the net is conclusive. Use Minstrel.

Cheers,
  Derek.

-- 
Derek Smithies Ph.D.
IndraNet Technologies Ltd.
ph +64 3 365 6485
Web: http://www.indranet-technologies.com/

"How did you make it work??"
       "Oh, the usual, get everything right".

Re: [Madwifi-users] MadWifi driver fails to recognize Ubiquity card

[Aditya Bhave <ayb@an...>]

Even with the trunk version, the same problem occurs. No wifi0 appears

--Aditya Bhave

On 07/14/2010 05:39 PM, Aditya Bhave wrote:
> what is relatively new code and not tested? The 0.9.4 branch or the
> trunk (SVN ??) version?
> I need to use Master mode and need access to OPenHal to enable 5/10 MHz
> channels. Are these facilities available in ath5k/9k?
>
> Thanks
> regards,
> Aditya Bhave
>
>
>
> On 07/14/2010 05:15 PM, Pavel Roskin wrote:
>    
>> On Wed, 2010-07-14 at 16:55 -0400, Aditya Bhave wrote:
>>
>>
>>      
>>> I compiled and installed the latest MadWifi code in the following way
>>>
>>> ayb@...:~/Desktop/madwifi-0.9.4-r4133-20100621$ cd scripts
>>>
>>>        
>> ...
>>
>>
>>      
>>>           product: AR928X Wireless Network Adapter (PCI-Express)
>>>
>>>        
>> Support for AR9280 only exists in the trunk, not in the 0.9.4 branch.
>> It's relatively new code that received very little testing.  Besides,
>> 802.11n is not supported by MadWifi.  I suggest that you use ath9k if
>> you can.
>>
>>
>>      
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Madwifi-users mailing list
> Madwifi-users@...
> https://lists.sourceforge.net/lists/listinfo/madwifi-users
>
>    

Re: [Madwifi-users] MadWifi driver fails to recognize Ubiquity card

[Aditya Bhave <ayb@an...>]

what is relatively new code and not tested? The 0.9.4 branch or the 
trunk (SVN ??) version?
I need to use Master mode and need access to OPenHal to enable 5/10 MHz 
channels. Are these facilities available in ath5k/9k?

Thanks
regards,
Aditya Bhave



On 07/14/2010 05:15 PM, Pavel Roskin wrote:
> On Wed, 2010-07-14 at 16:55 -0400, Aditya Bhave wrote:
>
>    
>> I compiled and installed the latest MadWifi code in the following way
>>
>> ayb@...:~/Desktop/madwifi-0.9.4-r4133-20100621$ cd scripts
>>      
> ...
>
>    
>>          product: AR928X Wireless Network Adapter (PCI-Express)
>>      
> Support for AR9280 only exists in the trunk, not in the 0.9.4 branch.
> It's relatively new code that received very little testing.  Besides,
> 802.11n is not supported by MadWifi.  I suggest that you use ath9k if
> you can.
>
>    

Re: [Madwifi-users] MadWifi driver fails to recognize Ubiquity card

[Pavel Roskin <proski@gn...>]

On Wed, 2010-07-14 at 16:55 -0400, Aditya Bhave wrote:

> I compiled and installed the latest MadWifi code in the following way
> 
> ayb@...:~/Desktop/madwifi-0.9.4-r4133-20100621$ cd scripts
...

>         product: AR928X Wireless Network Adapter (PCI-Express)

Support for AR9280 only exists in the trunk, not in the 0.9.4 branch.
It's relatively new code that received very little testing.  Besides,
802.11n is not supported by MadWifi.  I suggest that you use ath9k if
you can.

-- 
Regards,
Pavel Roskin

[Madwifi-users] MadWifi driver fails to recognize Ubiquity card

[Aditya Bhave <ayb@an...>]

Hi,

I compiled and installed the latest MadWifi code in the following way

ayb@...:~/Desktop/madwifi-0.9.4-r4133-20100621$ cd scripts
sudo ./madwifi-unload
sudo ./find-madwifi-modules.sh -r $(uname -r)
cd ../
make clean
make
sudo make install


Im using Ubiquity SR71X miniPCI card (the one that plugs into the 
external mini slot of a laptop). Inspite of all the above steps 
completing successfully, the driver does not recognize the card. Here 
are some outputs

ayb@...:~/Desktop/madwifi-0.9.4-r4133-20100621$ lsmod | grep ath_pci
ath_pci                86603  0
wlan                  193535  1 ath_pci
ath_hal               190909  1 ath_pci

ayb@...:~/Desktop/madwifi-0.9.4-r4133-20100621$ lshw -C network
WARNING: you should run this program as super-user.
   *-network
        description: Wireless interface
        product: BCM4311 802.11b/g WLAN
        vendor: Broadcom Corporation
        physical id: 0
        bus info: pci@...:0b:00.0
        logical name: eth2
        version: 01
        serial: 00:16:cf:0c:0a:78
        width: 32 bits
        clock: 33MHz
        capabilities: bus_master cap_list ethernet physical wireless
        configuration: broadcast=yes driver=wl0 driverversion=5.60.48.36 
ip=192.168.0.7 latency=0 multicast=yes wireless=IEEE 802.11
        resources: irq:16 memory:dfdfc000-dfdfffff
   *-network UNCLAIMED
        description: Network controller
        product: AR928X Wireless Network Adapter (PCI-Express)
        vendor: Atheros Communications Inc.
        physical id: 0
        bus info: pci@...:0c:00.0
        version: 01
        width: 64 bits
        clock: 33MHz
        capabilities: cap_list
        configuration: latency=0
        resources: memory:dfcf0000-dfcfffff
   *-network
        description: Ethernet interface
        product: BCM4401-B0 100Base-TX
        vendor: Broadcom Corporation
        physical id: 0
        bus info: pci@...:03:00.0
        logical name: eth0
        version: 02
        serial: 00:15:c5:22:ed:a3
        width: 32 bits
        clock: 33MHz
        capabilities: bus_master cap_list ethernet physical
        configuration: broadcast=yes driver=b44 driverversion=2.0 
latency=64 multicast=yes
        resources: irq:17 memory:dfafe000-dfafffff

ayb@...:~/Desktop/madwifi-0.9.4-r4133-20100621$ iwconfig
lo        no wireless extensions.

eth2      IEEE 802.11  Access Point: Not-Associated
           Link Quality:5  Signal level:215  Noise level:199
           Rx invalid nwid:0  invalid crypt:551  invalid misc:0

eth0      no wireless extensions.

ayb@...:~/Desktop/madwifi-0.9.4-r4133-20100621$


As you can see, even though the driver module is loaded, no wifi0 
appears in iwconfig and the card remains unclaimed. Any idea why this 
could be happening?

Thanks
regards,
Aditya Bhave

[Madwifi-users] Sample Rate Implementation

[Bishal Thapa <bdarealthug@gm...>]

Hello,
  I have a small question regarding the implementation of Sample Rate in
"madwifi version 0.9.4" concerning Sample Rate adaptation algorithm's
coupling with MRR (Multi Rate Retry). My question is, if we leave MRR
enabled (by default) and Sample Rate chosen as the rate adaptation algorithm
(by default), and lets say all transmissions at 54Mbps fails, then MRR
retries at rate 1Mbps and is successful, does the transmission_time
calculation for 54Mbps bit rate now include the time it took to retransmit
using 1Mbps? I would really appreciate if someone could answer this question
for me.

Thank you very much,
Sincerely,

Re: [Madwifi-users] Unable to unload MadWifi module

[Markus Koßmann <mkossmann_ml1@gm...>]

Am Dienstag, 13. Juli 2010 schrieb Aditya Bhave:
> Hi,
> 
> For some reason, Im not able to run the script madwifi-unload inspite of
> sudoing.
> 
> ayb@...:$ sudo ./madwifi-unload
> [sudo] password for ayb:
> sudo: unable to execute ./madwifi-unload: Permission denied
> 
> Any reason why this should happen?
From where do you try to run madwifi-unload ? Might it be that this filesystem 
is mounted with noexec permissions ?  

Re: [Madwifi-users] Unable to unload MadWifi module

[Pavel Roskin <proski@gn...>]

On Tue, 2010-07-13 at 16:13 -0400, Aditya Bhave wrote:
> Hi,
> 
> For some reason, Im not able to run the script madwifi-unload inspite of 
> sudoing.
> 
> ayb@...:$ sudo ./madwifi-unload
> [sudo] password for ayb:
> sudo: unable to execute ./madwifi-unload: Permission denied
> 
> Any reason why this should happen?

The message comes from sudo, not from anything inside madwifi-unload.
Perhaps madwifi-unload doesn't have executable permissions.  Or maybe
there are some other restrictions in the sudo policy.

You could try running shell explicitly:

sudo /bin/sh ./madwifi-unload

-- 
Regards,
Pavel Roskin

[Madwifi-users] Unable to unload MadWifi module

[Aditya Bhave <ayb@an...>]

Hi,

For some reason, Im not able to run the script madwifi-unload inspite of 
sudoing.

ayb@...:$ sudo ./madwifi-unload
[sudo] password for ayb:
sudo: unable to execute ./madwifi-unload: Permission denied

Any reason why this should happen?

Thanks
regards,
Aditya Bhave