Project

General

Profile

Bug #3849

Compex WLE200NX wireless card stops responding

Added by Michael von Glasow over 4 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
09/05/2014
Due date:
% Done:

0%

Estimated time:
Affected Version:
Affected Architecture:
amd64

Description

Occasionally, my WiFi adapter will stop working. Clients lose their connection to it, and if I scan nearby WiFis with my cell (using SatStat, https://mvglasow.github.io/satstat) my AP no longer appears in the list.

I have tried disabling and re-enabling the adapter in the Web GUI (applying canges after each step), but to no avail. I need to reboot to get the adapter back to life.

I have been running this setup for a few weeks now. I encountered the issue once in 2.1.4 during setup. I upgraded to 2.1.5 a couple of days ago and noticed yesterday morning that the WiFi was down. I investigated in the evening, eventually rebooting, and got the WiFi back to life. Tonight, as I was working, I noticed that the WiFi once dropped out briefly, then came back. About one or two hours later the WiFi dropped out again, this time for good.

I am seeing the following entry in the log file:

Sep 5 22:15:37 kernel: ath0: stuck beacon; resetting (bmiss count 4)
Sep 5 22:15:37 kernel: ath0: stuck beacon; resetting (bmiss count 4)
Sep 5 22:15:37 kernel: ath0: stuck beacon; resetting (bmiss count 4)
Sep 5 22:15:37 kernel: ath0: stuck beacon; resetting (bmiss count 4)
Sep 5 22:15:38 kernel: ath0: stuck beacon; resetting (bmiss count 4)
Sep 5 22:15:38 kernel: ath0: stuck beacon; resetting (bmiss count 4)
Sep 5 22:15:38 kernel: ath0: stuck beacon; resetting (bmiss count 4)

pfSense version:
2.1.5-RELEASE (amd64)
built on Mon Aug 25 07:44:45 EDT 2014
FreeBSD 8.3-RELEASE-p16

Hardware:
APU 1C4 engine
Compex WLE200NX wireless card (Atheros AR9280 chipset)
pfSense installed on SD card (live image)

Common wireless configuration:
Standard: 802.11g
Other settings were left at their defaults.

Network-specific wireless configuration:
Mode: Access point
Allow intra-BSS communication: Yes
Enable Hide SSID: No
WEP: Disabled
WPA: Enabled
WPA Mode: WPA
WPA Key Management Mode: PSK
Other settings were left at their defaults.

pfsense-system-wireless.txt (4.43 KB) pfsense-system-wireless.txt Wireless log Michael von Glasow, 09/05/2014 05:24 PM

History

#1 Updated by Michael von Glasow over 4 years ago

Just rebooted and WiFi is back again. I still get the stuck beacon message in the system log, but less frequently than while the WiFi was down (at that time I got some 4 messages per second, now the rate of messages varies, 1 message per second on average, with gaps up to 5 seconds).

#2 Updated by Michael von Glasow over 4 years ago

Wifi's gone again, after just 75 minutes of uptime. Wireless log attached.

#3 Updated by Michael von Glasow over 4 years ago

Update: after the last loss of WiFi I just left everything alone and the next morning I noticed the WiFi was back (though later the same on-off game started over again).

Therefore I can't tell for sure if the WiFi is ever gone for good or if all failures are just sporadic in nature and the WiFi eventually recovers by itself.

In any case, this behavior is rendering the WiFi adapter completely unreliable and thus unusable.

#4 Updated by Michael von Glasow over 4 years ago

I have downgraded to 2.1.4 (i.e. reinstalled 2.1.4 from scratch and restored config). I noticed that after the first few reboots the WiFi adapter was not detected at all, after a few reboots it was there again and I could configure it.

I'll watch the setup for a few days and will post if going back to 2.1.4 improves the situation.

#5 Updated by Mischa De Pol over 4 years ago

I had the same issue, with nearly the same setup (APU 1D4 engine).

What really helped me, was to set the Wireless Standard to 802.11b. Unfortunately you're now limited to 11Mbit/s.

The other wireless settings are the same as yours.

#6 Updated by Chris Buechler over 4 years ago

  • Status changed from New to Rejected

driver issue that's outside our control, and is almost certainly fixed in 2.2's base OS.

Also available in: Atom PDF