WLAN / WIFI Card Issues

That does suck fdisker, but I can't resist this question..

Why would you use the wlan to copy a 3Gb file?

Personally, any file that big, I hook up the usb drive, move it that way.. transfer rate is much better.

Doesn't solve the problem, though.. just works around it.. good luck working it out.

 

The 3304 bios fixed the Wifi issue for me on all OSs except for Vista. XP and Linpus had been having issues, but now they're super stable. So for now, I'm sticking with XP. The bios fixed other problems I was having including the black screen boot error so, I'm not willing to downgrade. I haven't tried 3305 yet though so...

 

I'm only copying the file as a test. If I wanted to move it quickly I'd copy it from one of the many USB keys or external hard drives I have laying around. The point of the test is that I can reproduce the network drops at will as opposed to most others having this problem randomly.

 

I have been using 3305 for the past few days. I've used 3304 too and that took away my problems with the slow downs coming back from standby. But that's when the drop offs started occurring. I'm going to try different BIOS today to see how they go.

A somewhat good news for me though, I've found that after disabling QoS on the wifi adapter (using the toshiba atheros utility), the drop offs don't occur anymore. No matter if it's on AC power or on battery. But now after standby, my slow downs are back again. Damn it. I can't get both of them to work without having one or the other having problems.
Will try different BIOS's today and report back soon. EDIT: nevermind, the disabling QoS thing is not working now. Damn it. Still dropping connections

EDIT: and by the way, I have been in talk with a technician at ACER Australia and I might have to send my machine in for service. Update you guys later on.

 

Would you or anyone have that bios version file? Can you upload it somewhere so I can give it a try?
I can't seem to find it anyway on the Acer site or their FTP site.

Thanks a bunch!

EDIT: nevermind. Just tried it and it didn't change anything for me either.
sigh. Hopefully the acer technician's turn out helpful.

 

Just got my Acer 3 days ago and I am too experiencing this issue... Just updated to BIOS 3304 and Atheros/Acer driver 7.60.224 with no change. Whether I reboot, resume from standby, or come back from hibernate, I notice sluggish wifi on battery mode with the power save features enabled. Have tried various settings only to end up going back to "Power save off."

All this at the expense of battery life
I hope its not a hardware issue, but a faulty driver... aargh.

Did the following simple test to show that AC vs. Battery does indeed affect it.

POWER SAVE MAXIMUM

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\100988>ping 192.168.1.1 -n 100

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=32ms TTL=64
Reply from 192.168.1.1: bytes=32 time=54ms TTL=64
Reply from 192.168.1.1: bytes=32 time=76ms TTL=64
Reply from 192.168.1.1: bytes=32 time=98ms TTL=64
Reply from 192.168.1.1: bytes=32 time=18ms TTL=64
Reply from 192.168.1.1: bytes=32 time=40ms TTL=64
Reply from 192.168.1.1: bytes=32 time=62ms TTL=64

POWER SAVE MAXIMUM - ON AC
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=47ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

BACK TO BATTERY POWER
Reply from 192.168.1.1: bytes=32 time=77ms TTL=64
Reply from 192.168.1.1: bytes=32 time=99ms TTL=64
Reply from 192.168.1.1: bytes=32 time=18ms TTL=64
Reply from 192.168.1.1: bytes=32 time=39ms TTL=64
Reply from 192.168.1.1: bytes=32 time=60ms TTL=64
Reply from 192.168.1.1: bytes=32 time=184ms TTL=64
Reply from 192.168.1.1: bytes=32 time=104ms TTL=64
Reply from 192.168.1.1: bytes=32 time=23ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 28, Received = 28, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 184ms, Average = 36ms
Control-C
^C
C:\Documents and Settings\100988>ping 192.168.1.1 -n 1000

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=73ms TTL=64
Reply from 192.168.1.1: bytes=32 time=94ms TTL=64
Reply from 192.168.1.1: bytes=32 time=14ms TTL=64
Reply from 192.168.1.1: bytes=32 time=37ms TTL=64
Reply from 192.168.1.1: bytes=32 time=59ms TTL=64
Reply from 192.168.1.1: bytes=32 time=81ms TTL=64
Reply from 192.168.1.1: bytes=32 time=102ms TTL=64
Reply from 192.168.1.1: bytes=32 time=22ms TTL=64
Reply from 192.168.1.1: bytes=32 time=44ms TTL=64
Reply from 192.168.1.1: bytes=32 time=67ms TTL=64
Reply from 192.168.1.1: bytes=32 time=89ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=31ms TTL=64
Reply from 192.168.1.1: bytes=32 time=53ms TTL=64
Reply from 192.168.1.1: bytes=32 time=76ms TTL=64
Reply from 192.168.1.1: bytes=32 time=97ms TTL=64
Reply from 192.168.1.1: bytes=32 time=17ms TTL=64
Reply from 192.168.1.1: bytes=32 time=40ms TTL=64
Reply from 192.168.1.1: bytes=32 time=62ms TTL=64
Reply from 192.168.1.1: bytes=32 time=186ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=25ms TTL=64
Reply from 192.168.1.1: bytes=32 time=47ms TTL=64
Reply from 192.168.1.1: bytes=32 time=70ms TTL=64
Reply from 192.168.1.1: bytes=32 time=92ms TTL=64
Reply from 192.168.1.1: bytes=32 time=12ms TTL=64
Reply from 192.168.1.1: bytes=32 time=34ms TTL=64
Reply from 192.168.1.1: bytes=32 time=55ms TTL=64
Reply from 192.168.1.1: bytes=32 time=77ms TTL=64
Reply from 192.168.1.1: bytes=32 time=99ms TTL=64
Reply from 192.168.1.1: bytes=32 time=19ms TTL=64
Reply from 192.168.1.1: bytes=32 time=41ms TTL=64
Reply from 192.168.1.1: bytes=32 time=62ms TTL=64
Reply from 192.168.1.1: bytes=32 time=84ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

SWITCHING TO POWER SAVE NORMAL
Reply from 192.168.1.1: bytes=32 time=143ms TTL=64
Reply from 192.168.1.1: bytes=32 time=60ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=19ms TTL=64
Reply from 192.168.1.1: bytes=32 time=191ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=30ms TTL=64
Reply from 192.168.1.1: bytes=32 time=52ms TTL=64
Reply from 192.168.1.1: bytes=32 time=74ms TTL=64
Reply from 192.168.1.1: bytes=32 time=96ms TTL=64
Reply from 192.168.1.1: bytes=32 time=15ms TTL=64
Reply from 192.168.1.1: bytes=32 time=37ms TTL=64
Reply from 192.168.1.1: bytes=32 time=59ms TTL=64
Reply from 192.168.1.1: bytes=32 time=81ms TTL=64
Reply from 192.168.1.1: bytes=32 time=103ms TTL=64
Reply from 192.168.1.1: bytes=32 time=22ms TTL=64
Reply from 192.168.1.1: bytes=32 time=44ms TTL=64
Reply from 192.168.1.1: bytes=32 time=66ms TTL=64
Reply from 192.168.1.1: bytes=32 time=88ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=29ms TTL=64
Reply from 192.168.1.1: bytes=32 time=51ms TTL=64
Reply from 192.168.1.1: bytes=32 time=74ms TTL=64
Reply from 192.168.1.1: bytes=32 time=95ms TTL=64
Reply from 192.168.1.1: bytes=32 time=15ms TTL=64
Reply from 192.168.1.1: bytes=32 time=37ms TTL=64
Reply from 192.168.1.1: bytes=32 time=58ms TTL=64
Reply from 192.168.1.1: bytes=32 time=80ms TTL=64
Reply from 192.168.1.1: bytes=32 time=101ms TTL=64
Reply from 192.168.1.1: bytes=32 time=21ms TTL=64
Reply from 192.168.1.1: bytes=32 time=43ms TTL=64
Reply from 192.168.1.1: bytes=32 time=66ms TTL=64
Reply from 192.168.1.1: bytes=32 time=87ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=30ms TTL=64
Reply from 192.168.1.1: bytes=32 time=52ms TTL=64
Reply from 192.168.1.1: bytes=32 time=74ms TTL=64

SWITCHING TO POWER SAVE OFF
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=54ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 117, Received = 99, Lost = 18 (15% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 191ms, Average = 41ms
Control-C
^C

AFTER STANDBY - POWER SAVE OFF
C:\Documents and Settings\100988>ping 192.168.1.1 -n 1000

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
Control-C
^C
C:\Documents and Settings\100988>

 

Some new drivers are floating around for both XP and Vista. I just installed it on Vista. I'll be sure to report back once I test it a bit. The drivers are being discussed over here:

viewtopic.php?f=11&t=5317&st=0&sk=t&sd=a

New version is 7.6.1.149 (though someone also said they had gotten their hands on a more stable version, 7.6.1.140).

 

I just installed 7.6.1.149 on XP. Put it in standby, and checked again -- NO ISSUES so far...
All on maximum power save mode.

 

I've been testing it off and on since last night. So far I *think* that it's working well. At the very least I have had zero issues that required me to restart the laptop. I've tested it plugged in, coming up from standby, coming up from hibernate, on a/c power, on battery only.... the signal is still there. I've been streaming music via Pandora to test it. By this point, I would have lost the device at least once.

I did just have something funny happen, but I can't be sure that it wasn't the wireless connection here at work that caused the hiccup. For a few seconds, Pandora stopped playing and gmail gave a connection error. Everything was back quickly though. Either way, this is WAY better than having to shutdown just to get the device back. I'll continue testing and report back.

 

After resuming a couple of times from standby, everything still seems to be okay:
Note: settings are on POWER SAVE MAXIMUM.

BATTERY

Code:

Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

ON AC

Code:

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

BACK TO BATTERY

Code:

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 37, Received = 37, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 4ms, Average = 0ms
Control-C
^C

I also noticed this new option which I didnt have on my previous 7.6.0.224 driver.
[attachment=0:24b50915]untitled.JPG[/attachment:24b50915]

I also found this, which seems to be an interesting read: http://blogs.techrepublic.com.com/networking/?p=533
Basically, I think the new driver just shuts off the battery saving mode by default (the Pollling is Off by default). I guess when you put the computer on standby or hibernate, it doesn't tell the AP that you've shut down the system. Thus, the AP goes nuts and your connection gets dropped, if you have the polling on.

 

Edit: False hope at fixing it, nevermind :lol:

 

my aao 150 xpsp3 home edition 120gb works perfectly well after flashing the bios to v.3305 and upgraded to atheros latest driver v7.6.1.149. i have so far not experiencing any drop in wi-fi connection, did tried to hibernate, switch on and off the wi-fi button - no problem encountered

 

Same here and crossing my fingers. Upgraded to driver 7.1.6.149 and flashed the bios to 3305. Been on all morning with no dropouts so far.
Acer support was totally unhelpful, by the way. "This is not a documented issue." Offered an rma. Useless.

 

I agree acer do suck here's there response to me asking about wifi dropping out and network manager disappearing

not really that useful and doesn't help with the wifi dropping out but at least they know theres a problem, i think the more of us that complain the faster it might get sorted. We shouldn't have to find a solution ourselves, Here's hoping they get it sorted.

 

Can someone post or e-mail me the BIOS version 3109?
I see that many people seem to have solved this issue with that BIOS rollback.
Much thanx.

 

If you're on Windows; no more issues with wlan driver v. 7.6.1.149.
See: viewtopic.php?f=34&t=1477&st=0&sk=t&sd=a&start=120#p37246

 

I tried 3114, downgraded the bios from 3305 and 3304. The wifi problems and occasionally crash have dissipated. I've been running the machine overnight, coming out of stand by / AC or DC power.

If anyone has tried this, let me know if we got the same result.. I cannot find the 3109 BIOS anymore. I just tried my luck with 3114.

Addendum: just minutes after posting the wifi died and I have to completely shutdown because restart does not turn back wifi . I guess the problem does not lay on the BIOS alone. I also upgraded by Linpus OS to 1.0.15E and there was an update for the wireless driver just a few weeks ago. My guess would be that drivers updated by Linpus was not compatible as XP drivers including the kernel on 1.0.15E, causing the system to halt/crash in a few hours.

 

Aspire One -- XP, 120gig HD, 1 gig ram. WIFI dropouts stopped after updating the BIOS to ver 3305, and installed the new driver from the Microsoft Update Site--

Hope this helps-

 

Thanks boatman. I'm have the AAO 110 with 8gb SSD, I'm already having second thoughts about Linpus Linux lite. It seems the problem has already been resolved to people who purchased with a XP environment. I'll try to be patient and probably switch to XP if this is not resolved by Linpus by next week.

 

I'm using XP, 1gig ram, 160gig HD. 3305 BIOS and have tried basically every iteration of the drivers so far, right up to the latest ones (7.6.1.160) and nothing works. Also tried the drivers from the Windows Update site, no luck there either.

After updating the BIOS my wireless worked perfectly until a reboot and since then it's worked exactly once. Otherwise it can't find the router.

No idea what to try now. Already tried Atheros client, bios 3304, and all iterations of the wireless driver except possibly 7.6.1.149, which I'm about to try for what will probably be no f----g reason whatsoever.