-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
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
WiFi adapter not found when scanning for network in Ubuntu #1107
Comments
can you paste the output from |
This may or may not be the same as #961. |
Could also be Wifi card FW issue: https://kb.protectli.com/kb/wifi-on-the-vault/#articleTOC_5 |
Yep, it was a card marked as 2145 so it probably was caused by wrong FW. Unfortunately, from the OS both revisions look identical, so it isn't possible to differentiate between them remotely, other than by trial and error. |
Dmesg would tell us what went wrong. But it isn't probably Dasharo's fault. Just software/driver/card FW fault that the card is not operable in OS. |
Issue no longer present on Ubuntu when testing rc4, however scans on Windows yield no device |
Component
Dasharo firmware
Device
Protectli VP3230
Dasharo version
v0.9.0-rc2
Dasharo Tools Suite version
develop
Test case ID
WLE002.001 Wi-Fi scanning (Ubuntu)
Brief summary
WiFi adapter not found when scanning for network in Ubuntu
How reproducible
100%
How to reproduce
Boot machine to Ubuntu
Login as root
Execute:
lspci | grep "Network controller:"
to verify if the network controller exists in the platform. you should receive:3:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev ff)
nmcli radio wifi on
nmcli device wifi rescan
you will recieve:
Error: No Wi-Fi device found.
Expected behavior
after waiting for a few seconds and executing:
nmcli device wifi list
a list of networks should be displaeydActual behavior
Error: No Wi-Fi device found.
Screenshots
log - WLE.zip
Additional context
Under windows there is no problem with detecting the adapter and scanning for networks.
Solutions you've tried
No response
The text was updated successfully, but these errors were encountered: