You are not logged in.
Note: I was following the Arch Wiki Guide but I ran into an error that is not stated on the wiki explicitly and I'm stuck.
I created a bootable usb using balenaetcher of arch linux. I booted from it and the first command I typed was "ping archlinux.org". It returned the error "ping: archlinux.org: Temporary failure in name resolution". This meant I wasn't connected to wifi so I followed the arch wiki on connecting to wifi. I typed "ip link" as stated and then proceeded to go to a different page about Network Connections. I checked my driver status with "lspci -k" and everything was normal. This is the driver in use:
"Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter
Kernel driver in use: ath10k_pci,
Kernel modules: ath10k_pci, wl"
I then typed in "ip link set wlan0 up". This worked as intended and I then checked if the firmware was loaded by typing "dmesg | grep firmware". It should show loaded firmware next to ath10k_pci but it instead shows this:
ath10k_pci 0000:02:00:0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8cal
To find further issues I typed "dmesg | grep ath10k_pci" and this was the output:
My wireless drivers are supported so I went to "Troubleshooting drivers and firmware". Upon reaching Atheros, ath10kit was not available and the page said to "See Linux Wireless Documentation for details". From there I didn't know what to do.
wifi-menu will fail to connect to wifi
I tried adding an ip address and using "iwctl" but it got stuck on "Waiting for IWD to appear...".
Please help me connect to the wifi so I can actually install arch.
Last edited by JohnstonLiu (2020-04-02 09:05:07)
Offline
Upon reaching antegros...
Antegros is not supported here, please ask them for help. https://wiki.archlinux.org/index.php/Co … pport_ONLY
Offline
No I'm not using antegros. That was a typo I meant Atheros.
Offline
JohnstonLiu wrote:Upon reaching antegros...
Antegros is not supported here, please ask them for help. https://wiki.archlinux.org/index.php/Co … pport_ONLY
No I'm not using antegros. That was a typo I meant Atheros.
Offline
Welcome to the forums - other than the typo which led to some confusion, that was a very good first post with good details about all the steps you had taken. At least right up to this point:
wifi-menu will fail to connect to wifi
From the information available, I do not see reason to suspect an issue with the driver. But we'll need more information on this last step. How did it fail? Were there error messages? Personally I don't much like wifi-menu ... at all really, but definitely not for debuging. It's automation hides the relevant information.
Use wpa_supplicant or iwd to attempt to connect. At least the former gives good error output if something goes wrong.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Welcome to the forums - other than the typo which led to some confusion, that was a very good first post with good details about all the steps you had taken. At least right up to this point:
JohnstonLiu wrote:wifi-menu will fail to connect to wifi
From the information available, I do not see reason to suspect an issue with the driver. But we'll need more information on this last step. How did it fail? Were there error messages? Personally I don't much like wifi-menu ... at all really, but definitely not for debuging. It's automation hides the relevant information.
Use wpa_supplicant or iwd to attempt to connect. At least the former gives good error output if something goes wrong.
Iwd does not work. If I try to use iwd, the console will get stuck on "Waiting for IWD to appear...".
I will try wpa_supplicant.
This is what happens when I try to join a network with wifi-menu:
https://imgur.com/a/MvG4oO2
Last edited by JohnstonLiu (2020-04-02 05:16:18)
Offline
Trilby wrote:Welcome to the forums - other than the typo which led to some confusion, that was a very good first post with good details about all the steps you had taken. At least right up to this point:
JohnstonLiu wrote:wifi-menu will fail to connect to wifi
From the information available, I do not see reason to suspect an issue with the driver. But we'll need more information on this last step. How did it fail? Were there error messages? Personally I don't much like wifi-menu ... at all really, but definitely not for debuging. It's automation hides the relevant information.
Use wpa_supplicant or iwd to attempt to connect. At least the former gives good error output if something goes wrong.
Iwd does not work. If I try to use iwd, the console will get stuck on "Waiting for IWD to appear...".
I will try wpa_supplicant.This is what happens when I try to join a network with wifi-menu:
https://imgur.com/a/MvG4oO2
This is what happened when I tried to use wpa_supplicant:
> scan
OK
> scan_results
bssid / frequency / signal level / flags / ssid
The results are empty?
*EDIT:
I forgot to enable iwd.service before typing "iwctl" which explains why the console got stuck. After enabling it, everything worked and I connected to my wifi. However, when I tried to ping archlinux.org I received this error:
ping: archlinux.org: Temporary failure in name resolution
Last edited by JohnstonLiu (2020-04-02 05:48:30)
Offline
iwd connects, but doesn't get you a lease or configures your DNS (by default)
https://wiki.archlinux.org/index.php/Iw … figuration
Also check the journal after the failed wifi-menu approach (apparently you can find an SSID there, so the NIC works, but the association or further steps fail)
NOTICE: use *one* approach at a time! Do not start the wpa_supplicant and iwd dameons in parallel and don't start them before using wifi-menu or anything like that. The different tools will trip over each other.
Offline
iwd connects, but doesn't get you a lease or configures your DNS (by default)
https://wiki.archlinux.org/index.php/Iw … figurationAlso check the journal after the failed wifi-menu approach (apparently you can find an SSID there, so the NIC works, but the association or further steps fail)
NOTICE: use *one* approach at a time! Do not start the wpa_supplicant and iwd dameons in parallel and don't start them before using wifi-menu or anything like that. The different tools will trip over each other.
Thanks for all the help guys I actually figured all of this out a few hours ago. I was too excited and was setting up my system. Yeah I didn’t have a dns so I setup one and everything worked. I connected to wifi with IWD. Once again thanks everyone!
Offline
Just as an FYI, wpa_supplicant didn't return any results as you ran the "scan_results" command before the "scan" command completed. wpa_cli is a bit unintuitive as it runs many commands asynchronously. When you entered "scan", you got the result "OK" which only meant the scan started. There'd be another output shortly after that (if you had waited) saying results were ready.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline