Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(23) |
Jul
(305) |
Aug
(470) |
Sep
(259) |
Oct
(385) |
Nov
(281) |
Dec
(339) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(451) |
Feb
(260) |
Mar
(329) |
Apr
(269) |
May
(357) |
Jun
(444) |
Jul
(309) |
Aug
(327) |
Sep
(345) |
Oct
(239) |
Nov
(345) |
Dec
(357) |
2005 |
Jan
(381) |
Feb
(356) |
Mar
(255) |
Apr
(371) |
May
(370) |
Jun
(295) |
Jul
(280) |
Aug
(280) |
Sep
(313) |
Oct
(395) |
Nov
(457) |
Dec
(346) |
2006 |
Jan
(384) |
Feb
(282) |
Mar
(274) |
Apr
(249) |
May
(195) |
Jun
(259) |
Jul
(153) |
Aug
(183) |
Sep
(119) |
Oct
(155) |
Nov
(159) |
Dec
(125) |
2007 |
Jan
(138) |
Feb
(98) |
Mar
(182) |
Apr
(151) |
May
(129) |
Jun
(93) |
Jul
(155) |
Aug
(133) |
Sep
(90) |
Oct
(123) |
Nov
(74) |
Dec
(93) |
2008 |
Jan
(105) |
Feb
(58) |
Mar
(98) |
Apr
(128) |
May
(68) |
Jun
(118) |
Jul
(150) |
Aug
(80) |
Sep
(84) |
Oct
(58) |
Nov
(78) |
Dec
(51) |
2009 |
Jan
(38) |
Feb
(51) |
Mar
(63) |
Apr
(90) |
May
(41) |
Jun
(39) |
Jul
(79) |
Aug
(10) |
Sep
(25) |
Oct
(36) |
Nov
(66) |
Dec
(20) |
2010 |
Jan
(23) |
Feb
(55) |
Mar
(38) |
Apr
(25) |
May
(18) |
Jun
(29) |
Jul
(19) |
Aug
(16) |
Sep
|
Oct
(16) |
Nov
(11) |
Dec
(15) |
2011 |
Jan
(3) |
Feb
(1) |
Mar
(1) |
Apr
(3) |
May
(12) |
Jun
(15) |
Jul
(18) |
Aug
(6) |
Sep
(8) |
Oct
(12) |
Nov
(6) |
Dec
(1) |
2012 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
(8) |
Jul
(2) |
Aug
(8) |
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(1) |
2013 |
Jan
(17) |
Feb
(6) |
Mar
(10) |
Apr
(2) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(4) |
Oct
|
Nov
(6) |
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2017 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
|
|
|
1
(10) |
2
(18) |
3
(7) |
4
(3) |
5
(22) |
6
(17) |
7
(25) |
8
(11) |
9
(1) |
10
(3) |
11
(25) |
12
(24) |
13
(23) |
14
(22) |
15
(26) |
16
(28) |
17
(13) |
18
(24) |
19
(20) |
20
(24) |
21
(15) |
22
(8) |
23
(6) |
24
|
25
|
26
(14) |
27
(22) |
28
(15) |
29
(1) |
30
(12) |
31
(12) |
From: GolemMTM <golem@mt...> - 2004-01-10 22:20:34
|
Hello madwifi-users! I'm using Linux with kernel 2.4.23, running Atheros card 5ghz My current driver is CVS: wlan: 0.7.2.0 BETA ath_hal: 0.9.6.3 ath_pci: 0.8.4.0 BETA PCI: Found IRQ 12 for device 02:00.0 PCI: Sharing IRQ 12 with 00:1f.3 ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: 802.11 address: 00:05:5d:89:63:2f ath0: Atheros 5211: mem=0xe8000000, irq=12 Why I have ath_hardstart: discard, no xmit buf and while transferring large files transfers is chopping and receiving hardware error resetting... I'm using turbo mode because normal don't seems work (too many packets lost in normal mode) Link Latency is ~1ms on 1km link, Real transfer speed is ~25mbit. Link Quality:24/0 Signal level:-71 dBm Noise level:-95 dBm Rate set to 54M Why big transfers cause hardware error ? Also my other question is about bridge ARP patch, Lastest CVS is bug fixed ? -- Pozdrowienia, GolemMTM |
From: Sam Leffler <sam@er...> - 2004-01-10 21:59:20
|
On Wednesday 07 January 2004 05:10 pm, Greg Chesson wrote: > Goncalo Valverde wrote: > > On Tuesday 06 January 2004 22:49, Greg Chesson wrote: > >>Gon=E7alo Valverde wrote: > >>>power from the battery. Btw, this only happens when using the madwifi > >>>drivers in the desktop machine. When using either driverloader or the > >>>computer in Windows (both in Ad-Hoc > >> > >>The only optimization in the windows drivers on XP is to turn off > >>power-save mode > >>on the wlan driver when AC power is available. The madwifi driver > >>doesn't implement > >>this power-saving mode, so this would not be an issue. > > > > Well,actually this could be an issue because on the laptop i'm running > > windows and not Linux. Linux+madwifi is only running in the desktop (in > > master mode). I'll try instaling linux on the laptop to try the madwifi > > driver > > aha. > I think what might be happening is that the windows laptop in battery mode > operates the driver in power-saving mode. Your madwifi desktop is > acting as an AP, > but it does not (a) generate DTIM signals to the sleeping laptop, or > (b) implement a power save queue and respond to PS-Poll messages from > the laptop. > If the laptop is running on AC power it won't do the power save dance > and should work ok. This reasoning only applies to the case where > madwifi is the AP and is talking to a station that is using the PS > protocol. > A station should never expect PS-Poll support from an AP unless the AP=20 specifies it in the capabilities it broadcasts in each beacon. The current= =20 AP support for madwifi does not support PS-Poll and so does not advertise i= t=20 in beacons. > When the roles are reversed and you see radically different behavior > on a madwifi laptop depending on battery mode or AC power, then > it's much more of a mystery. As I said previously, if the OS's time maintenance is off when operating on= =20 battery power then the ANI support in the HAL could easily get confused and= =20 do something weird. This seems unlikely (that time is not managed correctl= y)=20 but would be something to check. Sam |
From: Goncalo Valverde <goncalo.valverde@ne...> - 2004-01-10 09:04:44
|
Greetings On Thursday 08 January 2004 01:10, Greg Chesson wrote: > Goncalo Valverde wrote: > > On Tuesday 06 January 2004 22:49, Greg Chesson wrote: > >>Gon=E7alo Valverde wrote: > > Well,actually this could be an issue because on the laptop i'm running > > windows and not Linux. Linux+madwifi is only running in the desktop (in > > master mode). I'll try instaling linux on the laptop to try the madwifi > > driver > > aha. > I think what might be happening is that the windows laptop in battery mode > operates the driver in power-saving mode. Your madwifi desktop is > acting as an AP, > but it does not (a) generate DTIM signals to the sleeping laptop, or I've installed linux on the laptop, and the problems i was experiecing wit= h=20 Windows seem to disapear. So this is probably an issue of windows putting t= he=20 card in power-saver mode, and the PCI card acting as an AP not generating t= he=20 DTIM signals you mentioned. Any workaround for this (because i want to use= =20 the laptop both with windows and linux) Best regards |