- Wifi no suitable ap
- Re: I have a question about «wifi: Haven’t to connect to a suitable AP now»
- Wifi Hotspot: Access Point Mode Is Not Supported By This Device
- Ji m
- 55 responses to Wifi Hotspot: Access Point Mode Is Not Supported By This Device
- Saved searches
- Use saved searches to filter your results more quickly
- Spamming ‘wifi: Haven’t to connect to a suitable AP now!’ (IDFGH-2731) #4800
- Spamming ‘wifi: Haven’t to connect to a suitable AP now!’ (IDFGH-2731) #4800
- Comments
- Environment
- Problem Description
Wifi no suitable ap
Post by zhejfl » Fri Dec 14, 2018 9:40 am
I call SM_Quit_wifi() to close the wifi task. Then after one minute, I try to init the WIFI resource and task and connect the AP,but the problem occured.
The Debug Info
I (32849) wifi: mode : sta (30:ae:a4:47:27:ac)
[0;32mI (32849) Somnic_WIFICon: received wifi event 2[0m
[0;32mI (32849) Somnic_WIFICon: connected successfully[0m
W (32849) wifi: Haven’t to connect to a suitable AP now!
[0;32mI (32849) WIFICon: current ap ssid:![0m
[0;32mI (122709) event: station ip lost[0m
[0;32mI (122709) WIFICon: received wifi event 8[0m
There are any one know after call esp_wifi_deinit(), how to resolve the problem.
void SM_Quit_wifi(void) < ESP_ERROR_CHECK(esp_wifi_disconnect()); if(esp_wifi_stop()==ESP_ERR_WIFI_NOT_INIT) //停止WIFI < ESP_LOGE(SM_WFC,"Please Init WIFI, then call this function!\r\n"); return; >if(esp_wifi_deinit()==ESP_ERR_WIFI_NOT_INIT) //释放wifi所有资源和WIFI任务 < ESP_LOGE(SM_WFC,"Please Init WIFI, then call this function!\r\n"); >>
Ritesh Posts: 1346 Joined: Tue Sep 06, 2016 9:37 am Location: India Contact:
Re: I have a question about «wifi: Haven’t to connect to a suitable AP now»
Post by Ritesh » Sun Dec 16, 2018 4:56 pm
First of all, is there any requirement or reason to deinit WiFi as you just need to disconnect and stop WiFi if not required.
And then just start it again without WiFi init again.
We have did this way successfully into our project without any issue. So, Just try with below steps
1) WiFi disconnect
2) Stop WiFi
3) Change configuration
4) WiFi Start
5) WiFi connect
Wifi Hotspot: Access Point Mode Is Not Supported By This Device
This tutorial is trying to help those who want to create AP wifi hotspot in Ubuntu Laptop but stuck at “Wifi Hotspot: Access Point Mode Is Not Supported By This Device” error message.
I’ve written three tutorials about how to turn Ubuntu Laptop into a wifi hotspot for Android, and Windows phones. Access Point Mode does not support issue is one of the most asked questions from my readers. Below I will show how to fix it using Broadcom bcm4313 as example.
1. Press Ctrl+Alt+T on keyboard to open terminal. When it opens, run the command below to tell your wireless chip information:
02:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)
The chip id is BCM4313, manufactured by Broadcom.
2. Check the below table. Find out the driver that works for your wireless adapter and support AP mode.
For Broadcom, there are three drivers that support AP mode, but only brcmsmac (check link page for supported chips) support wifi chip BCM4313.
Driver | Manufacturer | Support AP Mode |
adm8211 | ADMtek/Infineon | no |
airo | Aironet/Cisco | ? |
ar5523 | Atheros | no |
at76c50x-usb | Atmel | no |
ath5k | Atheros | yes |
ath6kl | Atheros | no |
ath9k | Atheros | yes |
ath9k_htc | Atheros | yes |
ath10k | Atheros | ? |
atmel | Atmel | ? |
b43 | Broadcom | yes |
b43legacy | Broadcom | yes |
brcmfmac | Broadcom | no |
brcmsmac | Broadcom | yes |
carl9170 | ZyDAS/Atheros | yes |
cw1200 | ST-Ericsson | yes |
hostap | Intersil/Conexant | ? |
ipw2100 | Intel | no |
ipw2200 | Intel | no |
iwlegacy | Intel | no |
iwlwifi | Intel | yes |
libertas | Marvell | no |
libertas_tf | Marvell | yes |
mac80211_hwsim | Jouni | yes |
mwifiex | Marvell | yes |
mwl8k | Marvell | yes |
orinoco | Agere/Intersil/Symbol | no |
p54pci | Intersil/Conexant | yes |
p54spi | Conexant/ST-NXP | yes |
p54usb | Intersil/Conexant | yes |
rndis_wlan | Broadcom | no |
rt61pci | Ralink | yes |
rt73usb | Ralink | yes |
rt2400pci | Ralink | yes |
rt2500pci | Ralink | yes |
rt2500usb | Ralink | yes |
rt2800pci | Ralink | yes |
rt2800usb | Ralink | yes |
vt6656 | VIA | yes |
wil6210 | Atheros | yes |
wl12xx | Texas Instruments | yes |
zd1211rw | ZyDAS/Atheros | yes |
3. Find out current driver running on your wifi adapter by running below command:
ethtool -i wlan0 | grep driver
If need, install ethtool from Ubuntu Software Center. The command outputs something like this:
So in my case I need to switch wireless driver from wl0 to brcmsmac to get AP mode support.
4. Install brcmsmac driver.
sudo apt-get install firmware-b43-installer
5. After installed the new driver, try to enable it from Additional Drivers utility (search & open it from the Unity Dash), and finally restart.
Below section tells you AP mode is support now:
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
For some wireless chips, run below command instead to check out supported interface modes:
sudo iwconfig wlan0 mode master
7 To make this work at next boot, go to /etc/modprobe.d directory in terminal:
Or in your file browser (open as root), find out and remove the line blacklist brcmsmac that blacklist the driver in any file in that directory.
Ji m
I’m a freelance blogger who started using Ubuntu in 2007 and wishes to share my experiences and some useful tips with Ubuntu beginners and lovers. Please comment to remind me outdated tutorial! And, notify me if you find any typo/grammar/language mistakes. English is not my native language. Contact me via [email protected] Buy me a coffee: https://ko-fi.com/ubuntuhandbook1
55 responses to Wifi Hotspot: Access Point Mode Is Not Supported By This Device
I have exactly the same chip. In the end of step 4, when I run lsmod |grep brcmsmac, grep finds nothing. What do you think the problem may be? Thanks a lot.
Do step 5 and then step 3 and see the if the driver has switched to brcmsmac. If not, you may consider remove the previous driver (wl0 as example):
sudo apt-get purge --remove bcmwl-kernel-source
When i try to run this comd
sudo apt-get install firmware-b43-installer
to install the suitable driver it aborts the installation with the output
No chroot environment found. Starting normal installation
Unsupported device(s) found: PCI id 14e4:4727
What do you think the issue is? Could you please get back to me asap.
Thanks
I have an HP2140 Mini and am trying to get it running a wifi hotspot. (In Windows 7 Connectify works just fine) The HP2140 Mini has a Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01) wifi on my system and as far as I can tell, I need to install the b43legacy driver. I tried following the guide above, but the process did not work. I think the problem lies in these steps below. 4. Install brcmsmac driver. (QUESTION: Do i need to use brcmsmac or b43legacy?)
sudo apt-get install firmware-b43-installer 5. Disable the previous driver wl0:
sudo modprobe -r wl Load the new one:
sudo modprobe brcmsmac What code should I use to load the new driver? Thanks for your help in getting this running!
After installed “firmware-b43-installer”, try to enable this driver in the Additional Drivers utility (search and open it from the Unity Dash).
in additional drivers utility i am finding only only Broadcom 802.11 Linux STA wirless driver source from bcmwl-kernel only… and other option is do not use this device. i have installed firmware-b43-installer as per step 4. but its not showing in additional driver utility ….wat to do
thanx in advance
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spamming ‘wifi: Haven’t to connect to a suitable AP now!’ (IDFGH-2731) #4800
Spamming ‘wifi: Haven’t to connect to a suitable AP now!’ (IDFGH-2731) #4800
Comments
Environment
- Development Kit: none
- Module or chip used: ESP32-WROVER-B
- IDF version: v3.3.1
- Build System: Make
- Compiler version: 1.22.0-80-g6c4433a
- Operating System: macOS
- Power Supply: USB
Problem Description
This morning I noticed that one of my boards was spamming the message ‘wifi: Haven’t to connect to a suitable AP now!» on the console. For example:
W (40478) wifi: Haven't to connect to a suitable AP now! W (40598) wifi: Haven't to connect to a suitable AP now! W (40708) wifi: Haven't to connect to a suitable AP now! W (40828) wifi: Haven't to connect to a suitable AP now! W (40948) wifi: Haven't to connect to a suitable AP now! W (41068) wifi: Haven't to connect to a suitable AP now! W (41188) wifi: Haven't to connect to a suitable AP now! W (41298) wifi: Haven't to connect to a suitable AP now! W (41418) wifi: Haven't to connect to a suitable AP now! W (41538) wifi: Haven't to connect to a suitable AP now! W (41648) wifi: Haven't to connect to a suitable AP now! W (41768) wifi: Haven't to connect to a suitable AP now! W (41888) wifi: Haven't to connect to a suitable AP now! W (42008) wifi: Haven't to connect to a suitable AP now! W (42118) wifi: Haven't to connect to a suitable AP now! W (42238) wifi: Haven't to connect to a suitable AP now!
I have power cycled the board and have reflashed it several times and this persists. It started after I purged all connectable wifi networks from the device — thus esp_wifi_connect() is not being called.
This is a situation I test regularly, and have tested as recently as last night.
My WiFi initialization is as follows:
event_group = xEventGroupCreate(); xx_ERROR_CHECK_RET(esp_event_loop_init(event_handler, NULL)); wifi_init_config_t cfg = WIFI_INIT_CONFIG_DEFAULT(); xx_ERROR_CHECK_RET(esp_wifi_init(&cfg)); xx_ERROR_CHECK_RET(esp_wifi_set_storage(WIFI_STORAGE_RAM)); xx_ERROR_CHECK_RET(esp_wifi_set_mode(WIFI_MODE_STA)); xx_ERROR_CHECK_RET(esp_wifi_start()); xx_ERROR_CHECK_RET(esp_wifi_set_ps(WIFI_PS_MIN_MODEM));
After this initialization I start a task which performs site scans and attempt to connect.
I have disabled the task entirely, and commented parts of the initialization. The warning starts as soon as esp_wifi_start() is called, even if I never perform a scan or attempt esp_wifi_connection().
I have searched the ESP-IDF code for this error and not found it, so I assume it is part of the WiFi blob.
Can someone tell me what state causes this warning to appear?
The text was updated successfully, but these errors were encountered: