Arch Linux

cdbfoster

Member

Registered: 2014-01-02

Posts: 12

Can't connect Wi-Fi from installation medium.

Hi,

On a new laptop (Acer Aspire E5-575G-52RJ), I'm having trouble with the Wi-Fi while running off of the installation medium (Release 2016.08.01, SD card).  Upon running

# wifi-menu

I get:

Scanning for networks...
pcieport 0000:00:1d.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ea(Receiver ID)
pcieport 0000:00:1d.2:   device [8086:9d1a] error status/mask=00000081/00002000
pcieport 0000:00:1d.2:    [ 0] Receiver Error
pcieport 0000:00:1d.2:    [ 7] Bad DLLP
pcieport 0000:00:1d.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ea(Receiver ID)
pcieport 0000:00:1d.2:   device [8086:9d1a] error status/mask=00002041/00002000
pcieport 0000:00:1d.2:    [ 0] Receiver Error
pcieport 0000:00:1d.2:    [ 6] Bad TLP
Could not read interface p2p-dev-wlp3s0 flags: No such device

And then the network list pops up like normal, but despite being sure of the correct password, it never succeeds to connect.

Some stuff that might be helpful:

# lspci -v
...
00:1d.2 PCI bridge: Intel Corporation Device 9d1a (rev f1) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 124
        Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
        Memory behind bridge: 94200000-943fffff
        Capabilities: [40] Express Root Port (Slot+), MSI 00
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [90] Subsystem: Acer Incorporated [ALI] Device 1094
        Capabilities: [a0] Power Management version 3
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Access Control Services
        Capabilities: [220] #19
        Kernel driver in use: pcieport
        Kernel modules: shpchp
...
03:00.0 Network controller: Qualcomm Atheros Device 0042 (rev 30)
        Subsystem: Lite-On Communications Inc Device 0806
        Flags: bus master, fast devsel, latency 0, IRQ 133
        Memory at 94200000 (64-bit, non-prefetchable) [size=2M]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable+ Count=8/8 Maskable- 64bit-
        Capabilities: [70] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [148] Virtual Channel
        Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00
        Capabilities: [178] Latency Tolerance Reporting
        Capabilities: [180] L1 PM Substates
        Kernel driver in use: ath10k_pci
        Kernel modules: ath10k_pci
...

# dmesg | grep ath10k
...
[    9.425990] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2
...

Any ideas anyone has are greatly appreciated!  I'd be happy to provide more logs if needed.

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,778

Website

Re: Can't connect Wi-Fi from installation medium.

Could not read interface p2p-dev-wlp3s0 flags: No such device

We have seen this before:
https://bbs.archlinux.org/viewtopic.php?id=196584
https://bbs.archlinux.org/viewtopic.php?id=207816
https://bbs.archlinux.org/viewtopic.php?id=214495

According to @Texbrew, you should use `ip link` to find the name of your wireless interface and then use this to connect:

wifi-menu -o $interface

Replace $interface with the actual name of the interface.

---

Jin, Jîyan, Azadî

cdbfoster

Member

Registered: 2014-01-02

Posts: 12

Re: Can't connect Wi-Fi from installation medium.

That does not solve the issue.

And all of those posts are about Intel wireless; this is Atheros.

Any time I do anything with the wireless card, it gives me those PCIe bus errors.  For instance,

rmmod ath10k_pci && modprobe ath10k_pci

generates the same errors.

Is this a hardware issue?  Bum card or bus connecting the card?  There's also the dmesg output that suggests the firmware didn't load...

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,071

Re: Can't connect Wi-Fi from installation medium.

Is that all the dmesg output for that grep? that the direct firmware load fails is quite normal for this card, because the firmware isn't present on the card and has to be loaded in from the filesystem. do you get any other output in dmesg when the connection fails (not related to the ath10k chip directly?)

Last edited by V1del (2016-08-18 14:41:28)

cdbfoster

Member

Registered: 2014-01-02

Posts: 12

Re: Can't connect Wi-Fi from installation medium.

Apart from the bus errors, I get a number of

ath10k_pci 0000:03:00.0: no channel configured; ignoring frame(s)!

interspersed with a few

wlp3s0: authenticate with <ap mac address>
wlp3s0: send auth to <ap mac address> (try 1/3)
wlp3s0: send auth to <ap mac address> (try 2/3)
wlp3s0: send auth to <ap mac address> (try 3/3)
wlp3s0: authentication with <ap mac address> timed out

Oh, thanks for explaining about the firmware message.  Sorry for the brevity with the grep; I'm copying the logs by hand.
Here's the rest:

# dmesg | grep ath10k
[...] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
[...] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2
[...] ath10k_pci 0000:03:00.0: qca9377 hw1.0 target 0x05020000 chip_id 0x003820ff sub 11ad:0806
[...] ath10k_pci 0000:03:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[...] ath10k_pci 0000:03:00.0: firmware ver WLAN.TF.1.0-00267-1 api 5 features ignore-otp crc32 79cea2c7
[...] ath10k_pci 0000:03:00.0: board_file api 2 bmi_id N/A crc32 93da0176
[...] ath10k_pci 0000:03:00.0: htt-ver 3.1 wmi-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[...] ath10k_pci 0000:03:00.0 wlp3s0: renamed from wlan0

So I guess it is loading the firmware.