Since Cyanogen ported over the WPA Enterprise support from the donut branch, I have been eagerly wanting to get onto my corporate network.
With 3.9.5 running on my phone now, I can see the SSID of my network
show up in the list of available APs. It is listed as secured with WPA-EAP.
When I click the AP, I can set the EAP method (PEAP), the Phase 2 authentication (MSCHAP2),etc...
When I try to connect, it fails and gives a Disconnected status. When I
enter the following in Terminal:
Code:
su
cat /data/misc/wifi/wpa_supplicant.conf
I can scroll to the bottom and see the following:
network={
ssid="____"
key_mgmt=WPA-EAP
group=CCMP TKIP
priority=23
}
It does not appear to keep the settings for PEAP or MSCHAP2...
I manually edit the entry to the following:
network={
ssid="___"
key_mgmt=WPA-EAP
group=CCMP TKIP
eap=PEAP
identity="xxxxx"
password="xxxxx"
phase2="AUTH=MSCHAPV2"
priority=19
}
When I push the changes back into the /data/misc/wifi directory and restart,
it now tries to obtain an address... unsuccessfully... lol...
Here is the output from wpa_cli:
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>Trying to associate with 00:13:60:d4:e5:70 (SSID='___' freq=2462 MHz)
<2>CTRL-EVENT-STATE-CHANGE id=4 state=3
<2>CTRL-EVENT-STATE-CHANGE id=4 state=4
<2>Associated with 00:13:60:d4:e5:70
<2>CTRL-EVENT-EAP-STARTED EAP authentication started
<2>CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
<2>CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
<2>CTRL-EVENT-STATE-CHANGE id=4 state=5
<2>CTRL-EVENT-STATE-CHANGE id=4 state=5
<2>CTRL-EVENT-STATE-CHANGE id=4 state=6
<2>CTRL-EVENT-STATE-CHANGE id=4 state=6
<2>WPA: Key negotiation completed with 00:13:60:d4:e5:70 [PTK=TKIP GTK=TKIP]
<2>CTRL-EVENT-STATE-CHANGE id=4 state=7
<2>CTRL-EVENT-CONNECTED - Connection to 00:13:60:d4:e5:70 completed (auth) [id=4
id_str=]
<2>CTRL-EVENT-STATE-CHANGE id=4 state=8
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>CTRL-EVENT-STATE-CHANGE id=-1 state=8
<2>CTRL-EVENT-STATE-CHANGE id=-1 state=2
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>CTRL-EVENT-SCAN-RESULTS Ready
.
.
.
I am still reading up on all of this and will post anything I find, but I wanted to throw it out there for others too...
Any help would be greatly appreciated...
L8r,
Vermithrax
Solved
K.. Apparently all I needed to do was reboot after I made the changes above... Came into work this morning and I can now connect to my company network...
Go figure...
L8r,
Vermithrax
Try setting up to connect to my openvpn server on GDX v.19 with the built-in tun interface. Got thru all the initiation but something happens that the connection was dropped. Here's the releveant part of the logcat:
I/openvpn ( 4537): [serverkey] Peer Connection Initiated with *.*.*.*:1194
D/Tethering( 1720): tun0 is not a tetherable iface, ignoring
I/System.out( 4537): THREAD Thread[Thread-13,5,main] TERMINATED
W/Tethering( 1720): attempting to remove unknown iface (tun0), ignoring
I/mtpd ( 4814): Received signal 17
I/mtpd ( 4814): Pppd is terminated (status = 1)
I/mtpd ( 4814): Mtpd is terminated (status = 33)
Anyone knows what's the deal with that TUN module?
I have since installed openvpn-installer and openvpn settings and it works
The same debug output exists as well for tun. The problem is not with that module per se since I have not changed it anyway. It seems that the openvpn binary that comes with GDX is not the same binary that I have gotten from openvpn-installer.
It is probably a bug inherited from CM anyway
Touchpad just trying to turn wifi on without any success. I have no idea what happened. touchpad worked well for months and just lost wifi. when I boot to WebOs - wifi is working well. I tried to clean up cm9 and flash cm10 - same result.
output from catlog:
02-18 11:35:07.449 E/WifiStateMachine(350): Failed to reload STA firmware java.lang.IllegalStateException: command '40 softap fwreload wlan0 STA' failed with '400 40 Softap operation failed (No such device)'
02-18 11:35:07.459 E/WifiStateMachine(350): Unable to change interface settings: java.lang.IllegalStateException: command '42 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 42 Failed to set address (No such device)'
02-18 11:35:18.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:19.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:20.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:21.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:22.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:22.479 E/WifiStateMachine(350): Failed to setup control channel, restart supplicant
02-18 11:35:27.499 E/WifiStateMachine(350): Failed to reload STA firmware java.lang.IllegalStateException: command '43 softap fwreload wlan0 STA' failed with '400 43 Softap operation failed (No such device)'
02-18 11:35:27.509 E/WifiStateMachine(350): Unable to change interface settings: java.lang.IllegalStateException: command '45 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 45 Failed to set address (No such device)'
02-18 11:35:27.509 E/WifiHW (350): Unable to open connection to supplicant on "wlan0": No such file or directory
02-18 11:35:28.509 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:29.519 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:30.519 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:31.519 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:32.519 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:32.519 E/WifiStateMachine(350): Failed to setup control channel, restart supplicant
netcfg shows all interfaces down except lo.
wifi country is eu (never checked it before) and I can't change it.
You could try this; maybe it's something similar?
bananagranola said:
You could try this; maybe it's something similar?
Click to expand...
Click to collapse
no link?
Well, that's my first brain fart today. Won't be the last. http://forum.xda-developers.com/showthread.php?t=1813200
Thanks, but not. my wifi just stopped working without any updates etc.
My goodness - wrong device, wrong thread. Like I said, not the last. http://forum.xda-developers.com/showthread.php?t=1937109
No, didn't helped. wifi in webos works without any problems too.
I'm looking at dmesg and found:
board sdio wifi disable
mmc1: card 0001 removed
is it wifi card?
Sorry, then that was the limit of what I can help with. Other than a full wipe and reflash I don't know what else to try. Hopefully someone with more knowledge will show up.
More info from dmesg:
<6>[ 443.108696] CMTP-ATH6KL v4.4
<3>[ 443.108715] board_sdio_wifi_enable
<6>[ 443.114565] wifi_power(1) 1.8V sdio: set load
<6>[ 443.119068] tenderloin_wifi_power: New regulator mode for 8058_s3: 1
<6>[ 443.126264] wifi_power(1) 3.3V
<6>[ 443.126583] wifi_power(1) 8901_l1 3.3V
<6>[ 443.134761] wifi_power(1) 8058_l19 1.8V
<4>[ 443.135074] wifi_power(1) CHIP_PWD
<4>[ 443.498377] mmc1: queuing unknown CIS tuple 0x01 (3 bytes)
<4>[ 443.507770] mmc1: queuing unknown CIS tuple 0x1a (5 bytes)
<4>[ 443.511869] mmc1: queuing unknown CIS tuple 0x1b (8 bytes)
<4>[ 443.518944] mmc1: queuing unknown CIS tuple 0x14 (0 bytes)
<4>[ 443.529203] mmc1: queuing unknown CIS tuple 0x80 (1 bytes)
<4>[ 443.529474] mmc1: queuing unknown CIS tuple 0x81 (1 bytes)
<4>[ 443.541910] mmc1: queuing unknown CIS tuple 0x82 (1 bytes)
<6>[ 443.541961] mmc1: new high speed SDIO card at address 0001
<3>[ 443.598711] ath6kl: bef2fd6c
<3>[ 446.099490] ath6kl: bef2fcfc
<4>[ 446.099507] ath6kl: bef2fcdc
<6>[ 446.114969] ath6kl: bef2fbc4
<6>[ 446.114985] ath6kl: bef2fbc4
<6>[ 446.116982] ath6kl: bef2fbc4
<6>[ 446.119846] ath6kl: bef2fbc4
<6>[ 446.122747] ath6kl: bef2fbc4
<6>[ 446.125644] ath6kl: bef2fbc4
<6>[ 446.128447] ath6kl: bef2fbc4
<6>[ 446.131304] ath6kl: bef2fbc4
<6>[ 446.134207] ath6kl: bef2fbc4
<6>[ 446.137091] ath6kl: bef2fbc4
<6>[ 446.139949] ath6kl: bef2fbc4
<6>[ 446.142802] ath6kl: bef2fbc4
<6>[ 446.145628] ath6kl: bef2fbc4
<6>[ 446.148491] ath6kl: bef2fbc4
<6>[ 446.151356] ath6kl: bef2fbc4
<6>[ 446.154317] ath6kl: bef2fbc4
<6>[ 446.157094] ath6kl: bef2fbc4
<4>[ 446.160235] ath6kl: bef2fc94
<3>[ 446.163154] ath6kl: bef2fe14
<3>[ 446.166015] ath6kl: bef2fe44
<4>[ 446.168669] ath6kl_sdio: probe of mmc1:0001:1 failed with error -5
<6>[ 462.282740] adm_close port_id=0 index 0
<6>[ 478.764935] adm_close port_id=0 index 0
<3>[ 498.557702] board_sdio_wifi_disable
<6>[ 498.564551] tenderloin_wifi_power: New regulator mode for 8058_s3: 1
<6>[ 498.685586] mmc1: card 0001 removed
i dont know what cleanup cm9 + 10 means.. delete things?
uninstall?
nandroid restore and still no-go?
maybe rootzwixi knows..
goodluck
amkaos said:
i dont know what cleanup cm9 + 10 means.. delete things?
uninstall?
nandroid restore and still no-go?
maybe rootzwixi knows..
goodluck
Click to expand...
Click to collapse
format cache, sdcard, config and data from clockworkmod and then acmeuninstall. tried 3 times. Now trying to flash cm9.
this sounds impossible maybe ::
sometimes my router will not broadcast wifi but all things connected thru ethernet work fine.. or one wireless device cannot connect but others do or other connex issues..etc..
if i restart modem + router, everything connex just fine..
you didnt really give any detes about if hptp only fails on your network etc..
if you do uninstall then acme3 correctly, there is no way that HPTP wont connect to your network... unless you share some obscure hardware fubar that i never heard of..
GL
i hope you post what the outcome is and how you resolved prob.
your experience will help out someone in future time
btw, i dont wanna rub it in but when you get things going, make a nandroid backup .. make more as you tweak out your tab and safely delete prior backups... saved me many headaches..
GL
EDIT:: i see that you do connect w/ webos.. still its easy to restart router + modem..
So, new wifi driver in the new cm10 build - still no success. It's only internet browser with webos ;(
Epic 4g same thing
crea7or said:
So, new wifi driver in the new cm10 build - still no success. It's only internet browser with webos ;(
Click to expand...
Click to collapse
CM10 for 4 months no wifi issues. Suddenly the other morning wifi won't turn on. Boot to a stock image it is fine. Did you ever find a solution?
RichMichPA said:
CM10 for 4 months no wifi issues. Suddenly the other morning wifi won't turn on. Boot to a stock image it is fine. Did you ever find a solution?
Click to expand...
Click to collapse
stock image?
Multiboot utility
crea7or said:
stock image?
Click to expand...
Click to collapse
I use multi boot which lets you reboot into fc09 to add MSL etc. I just tried 9.1 ics and wifi is working.
Exactly the same problem
As yet, no fix in sight.
Wifi in WebOS is solid. I have managed to spontaneously connect a couple of times after several hours, sometimes days. I've tried reflashing several roms/updates, reformating, clearing cache and dalvik, resetting permissions. Nothing.
As long as I do not reboot, once connected the wifi is solid. My catlog shows exactly the same problems as OPs.
It may be a coincidence, but my problems seemed to begin after switching to airplane mode on a recent trip. Since then I've only managed to get the wifi up 3 times.
In settings under wifi it just says "connecting to wifi" regardless of whether the wifi button is set to "ON" or "OFF"
What bothers me, is the "not found" errors in logcat.
I'm out of ideas. If anyone can suggest a way to nail down the issue, I'm all ears. Thanks in advance!
Code:
07-24 11:37:27.209 E/WifiStateMachine(242): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
07-24 11:37:27.209 W/CommandListener(156): Failed to retrieve HW addr for wlan0 (No such device)
07-24 11:37:27.209 D/CommandListener(156): Setting iface cfg
07-24 11:37:27.209 D/NetworkManagementService(242): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
07-24 11:37:27.209 D/NetworkManagementService(242): flags <[down]>
07-24 11:37:27.219 E/WifiStateMachine(242): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
07-24 11:37:27.389 I/wpa_supplicant(6737): rfkill: Cannot open RFKILL control device
07-24 11:37:27.389 E/wpa_supplicant(6737): Could not read interface wlan0 flags: No such device
I'm having the same issue. WiFi works solid on webOs just when I boot into android and try to turn WiFi on, it stays stuck saying “turning on wifi" on cm9 any build and cm10 any build. I uninstalled everything at least 20 times wiped my TP clean on android and webOs(basically factory reset) wiped the cache wiped the delvik cache turned off turn on reinstall android also downloaded WiFi fixer apk and that doesn't help at all either. Everything on webOs works WiFi internet works great. Just when I go into android it stays stuck at turning on WiFi and when I reinstall cm9 or cm10 open up settings this is the only time I can switch the setting to turning on WiFi but everything is in gray with no luck just stuck saying turning on WiFi. Any help would be much appreciated! I hate webOs android is way better!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
[email protected] said:
I'm having the same issue. WiFi works solid on webOs just when I boot into android and try to turn WiFi on, it stays stuck saying “turning on wifi" on cm9 any build and cm10 any build. I uninstalled everything at least 20 times wiped my TP clean on android and webOs(basically factory reset) wiped the cache wiped the delvik cache turned off turn on reinstall android also downloaded WiFi fixer apk and that doesn't help at all either. Everything on webOs works WiFi internet works great. Just when I go into android it stays stuck at turning on WiFi and when I reinstall cm9 or cm10 open up settings this is the only time I can switch the setting to turning on WiFi but everything is in gray with no luck just stuck saying turning on WiFi. Any help would be much appreciated! I hate webOs android is way better!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
[email protected] said:
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
did u try doctore your TP?
Until I had this problem my wifi worked great. The issue seemed to be related to (but may have nothing to do with) switching on airplane mode, while on a flight. Since then I've been unable to get wifi to enable without doing the following:
Emailing myself a logcat (I guess it could be anything in an email, this is just to alert me of a state change).
Setting the tablet in clock mode (so that it does not sleep).
Waiting.
Eventually (I assume after a reboot). The email gets sent and then I know wifi is back up. This is less than ideal as it used to take several hours, now it takes several days.
I have this problem regardless of whether I'm using a new ROM or a backup with a previously working wifi.
Sometimes you can change the button from "Off" to "On" in settings. It remains grey, the status remains "connecting to wifi" and then after a couple of minutes the button changes back to "Off"
Code:
09-11 08:51:46.489 I/SystemServer(239): NetworkStats Service
09-11 08:51:46.489 I/SystemServer(239): NetworkPolicy Service
09-11 08:51:46.499 I/SystemServer(239): Wi-Fi P2pService
09-11 08:51:46.499 I/SystemServer(239): Wi-Fi Service
09-11 08:51:46.519 I/SystemServer(239): Connectivity Service
09-11 08:51:46.519 D/ConnectivityService(239): ConnectivityService starting up
09-11 08:51:46.519 E/ConnectivityService(239): Ignoring protectedNetwork 10
09-11 08:51:46.519 E/ConnectivityService(239): Ignoring protectedNetwork 11
09-11 08:51:46.519 E/ConnectivityService(239): Ignoring protectedNetwork 12
09-11 08:51:46.529 D/NetworkManagementService(239): Registering observer
09-11 08:51:46.529 D/NetworkManagementService(239): Registering observer
09-11 08:51:46.529 I/WifiService(239): WifiService starting up with Wi-Fi enabled
09-11 08:51:46.539 I/SystemServer(239): Throttle Service
09-11 08:51:46.539 I/SystemServer(239): Mount Service
09-11 08:51:48.579 D/NetworkManagementService(239): Registering observer
09-11 08:51:49.549 D/NetworkManagementService(239): Registering observer
09-11 08:51:49.609 I/ActivityManager(239): Start proc android.process.media for broadcast
09-11 08:51:50.319 D/WifiService(239): New client listening to asynchronous messages
09-11 08:51:50.609 W/ThrottleService(239): unable to find stats for iface rmnet0
09-11 08:51:50.919 I/ActivityManager(239): Start proc com.google.process.gapps for service com.google.android.location/.NetworkLocationService: pid=503 uid=10043 gids={3003, 1015, 1007, 1006, 2001, 3006}
09-11 08:51:51.029 I/ActivityManager(239): Start proc com.android.settings for broadcast
09-11 08:52:01.849 D/NetworkManagementService(239): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
09-11 08:52:01.849 D/NetworkManagementService(239): flags <[down]>
09-11 08:52:58.119 E/WifiHW (239): Supplicant not running, cannot connect
09-11 08:53:02.119 E/WifiStateMachine(239): Failed to setup control channel, restart supplicant
09-11 08:53:02.129 E/WifiStateMachine(239): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
09-11 08:53:02.129 W/CommandListener(155): Failed to retrieve HW addr for wlan0 (No such device)
09-11 08:53:02.129 D/CommandListener(155): Setting iface cfg
09-11 08:53:02.129 D/NetworkManagementService(239): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
09-11 08:53:02.129 D/NetworkManagementService(239): flags <[down]>
09-11 08:53:02.139 E/WifiStateMachine(239): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
09-11 08:53:02.259 I/wpa_supplicant(2313): rfkill: Cannot open RFKILL control device
09-11 08:53:02.259 E/wpa_supplicant(2313): Could not read interface wlan0 flags: No such device
09-11 08:53:03.299 E/wpa_supplicant(2313): nl80211: Could not set interface 'wlan0' UP
09-11 08:53:03.299 E/wpa_supplicant(2313): wlan0: Failed to initialize driver interface
09-11 08:53:17.149 E/WifiStateMachine(239): Failed 6 times to start supplicant, unload driver
09-11 08:53:17.149 E/WifiStateMachine(239): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
09-11 08:53:17.159 D/CommandListener(155): Setting iface cfg
09-11 08:53:17.159 E/WifiStateMachine(239): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
09-11 08:53:17.159 D/NetworkManagementService(239): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
09-11 08:53:17.159 D/NetworkManagementService(239): flags <[down]>
09-11 08:53:17.259 I/wpa_supplicant(2353): rfkill: Cannot open RFKILL control device
09-11 08:53:18.289 E/wpa_supplicant(2353): nl80211: Could not set interface 'wlan0' UP
Things I've tried (that I can remember, I may have forgotten some!):
Changing the wifi channel on the router.
Cycling to router
Logging into WebOS - toggling the wifi (Wifi works fine in WebOS)
What I don't get is why even a fresh ROM does not work and yet, WebOS is still working fine.
(Are there some conf files I can check? Is it likely they got changed somehow?).
I am currently running jcsullins cm-10-20130418-EXPERIMENTAL
Thanks in advance.
OK, after scouring dmesg it appears there is a conflict between the ath6kl driver and sdio. (I think I have a couple of jcsullins test drivers on my sd card, so I will try those next).
I'll include a dmesg tomorrow, but the gist of it is as follows:
Code:
ath6kl: temporary war to avoid sdio crc error
ath6kl: firmware crashed
ath6kl: crash dump:
ath6kl: hw 0x30000582 fw
ath6kl: invalid address for debug_hdr_addr
ath6kl: Failed to start hardware: -5
ath6kl: Failed to init ath6kl core
ath6kl_sdio: probe of mmcl:0001:1 failed with error -5 board_sdio_wifi_disable
tenderloin_wifi_power: New regulator mode for 8058_s3:1
mmcl: card 00001 removed
Can anyone please offer a suggestion?
Is there another kernel I can try?
Is there a wifi fix now for the ath6kl driver?
Hi everyone! I'm new to custom roms and got thrilled with how CM's pervormance is better that LG's original rom, but since I flashed it I can´t use wifi :crying:
I ain´t even able to turn wifi on or of... As I work developing andoid apps, I've noticed the error log below at logcat... seems like the wifi drivers are missing... is it correct? how am I supposed to fix that?
Thanks you all in andvance for any help/suggestions!
Code:
10-30 09:31:30.726: ERROR/WifiStateMachine(477): Failed 6 times to start supplicant, unload driver
10-30 09:31:30.756: ERROR/WifiStateMachine(477): Unable to change interface settings: java.lang.IllegalStateException: command '5479 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 5479 Failed to set address (No such device)'
10-30 09:31:30.786: ERROR/wpa_supplicant(4967): nl80211: Could not configure driver to use managed mode
10-30 09:31:30.796: ERROR/wpa_supplicant(4967): Could not read interface wlan0 flags: No such device
10-30 09:31:30.796: ERROR/wpa_supplicant(4967): wlan0: Failed to initialize driver interface
10-30 09:31:39.336: ERROR/gralloc(146): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
10-30 09:31:41.796: ERROR/WifiHW(477): Supplicant not running, cannot connect
10-30 09:31:42.806: ERROR/WifiHW(477): Supplicant not running, cannot connect
10-30 09:31:43.806: ERROR/WifiHW(477): Supplicant not running, cannot connect
10-30 09:31:44.806: ERROR/WifiHW(477): Supplicant not running, cannot connect
10-30 09:31:45.806: ERROR/WifiHW(477): Supplicant not running, cannot connect
10-30 09:31:45.826: ERROR/WifiStateMachine(477): Failed to setup control channel, restart supplicant
10-30 09:31:45.876: ERROR/WifiStateMachine(477): Unable to change interface settings: java.lang.IllegalStateException: command '5482 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 5482 Failed to set address (No such device)'
10-30 09:31:45.906: ERROR/wpa_supplicant(5004): nl80211: Could not configure driver to use managed mode
10-30 09:31:45.906: ERROR/wpa_supplicant(5004): Could not read interface wlan0 flags: No such device
10-30 09:31:45.906: ERROR/wpa_supplicant(5004): wlan0: Failed to initialize driver interface
bonus:
Code:
10-31 14:47:38.139: ERROR/(25264): file /data/data/com.nvidia.NvCPLSvc/files/driverlist.txt: not found!
Check 'netcfg' output and also kmesg at boot. CM has the Wi-Fi driver built into the kernel and it's loaded when the system starts.