Skip to content
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

Open
JanPrusinowski opened this issue Oct 24, 2024 · 5 comments
Open

WiFi adapter not found when scanning for network in Ubuntu #1107

JanPrusinowski opened this issue Oct 24, 2024 · 5 comments

Comments

@JanPrusinowski
Copy link

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 displaeyd

Actual behavior

Error: No Wi-Fi device found.

Screenshots

image
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

@mkopec
Copy link
Member

mkopec commented Oct 24, 2024

can you paste the output from dmesg here? That would probably help a lot

@krystian-hebel
Copy link

This may or may not be the same as #961.

@miczyg1
Copy link
Contributor

miczyg1 commented Oct 30, 2024

Could also be Wifi card FW issue: https://kb.protectli.com/kb/wifi-on-the-vault/#articleTOC_5

@krystian-hebel
Copy link

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.

@miczyg1
Copy link
Contributor

miczyg1 commented Nov 7, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants