Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Sorry Guest, you are banned from posting and sending personal messages on this forum.

This ban is not set to expire.

[123nobody456]

The Atheros QCA9377 is not capturing data packets in monitor mode the table remains empty.

I already installed the new Firmware from GitHub https://github.com/kvalo/ath10k-firmware and try´d this versions:

firmware-5.bin_CNSS.TF.1.0-00267-QCATFSWPZ-1
firmware-sdio-5.bin_WLAN.TF.1.1.1-00061-QCATFSWPZ-1
firmware-5.bin_WLAN.TF.1.0-00002-QCATFSWPZ-5
firmware-6.bin_WLAN.TF.2.1-00014-QCARMSWP-1
firmware-6.bin_WLAN.TF.2.1-00016-QCARMSWP-1
firmware-6.bin_WLAN.TF.2.1-00021-QCARMSWP-1

airodump-ng is still not capturing any data.

Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31)
Operating System: KDE neon 5.15 (Ubuntu 18.04)
Kernel Version: 5.0.0
OS Type: 64-bit
Processors: 8 × AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
Memory: 6.8 GiB of RAM
Aircrack-ng 1.5.2 (installed from source code)

Any solution?

[misterx]

Did you try the firmware that was provided in Ubuntu?

Is there anything in dmesg?

[123nobody456]

Did you try the firmware that was provided in Ubuntu?

Is there anything in dmesg?

Yes
The Wi-Fi connection was slowing down after a few minutes in use. After installing the new Firmware, the Network is working normally.
I had errors in journalctl with the old Ubuntu ath-10k Firmware (firmware-5.bin), since i installed the firmware-6.bin_WLAN.TF.2.1-00021-QCARMSWP-1 i have no issues with the ath10k Firmware.
I still have the AMD-IOMMU Bug.

Old journalctl report:

linux kernel: [Firmware Bug]: AMD-Vi: IOAPIC[4] not in IVRS table
linux kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
linux kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found
linux kernel: AMD-Vi: Disabling interrupt remapping

linux kernel: do_IRQ: 4.55 No irq handler for vector
linux kernel:   #5
linux kernel: do_IRQ: 5.55 No irq handler for vector
linux kernel:   #6
linux kernel: do_IRQ: 6.55 No irq handler for vector
linux kernel:   #7
linux kernel: do_IRQ: 7.55 No irq handler for vector

linux kernel: ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.LPC0.EC0._Q46], AE_ALREADY_EXISTS (20181003/dswload2-316)
linux kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181003/psobject-221)
linux kernel: ACPI Error: Skip parsing opcode Method (20181003/psloop-543)
linux kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.GPP2.BCM5], AE_NOT_FOUND (20181003/dswload2-160)
linux kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181003/psobject-221)
linux kernel: ACPI Error: Ignore error and continue table load (20181003/psobject-604)
linux kernel: ACPI Error: Skip parsing opcode Scope (20181003/psloop-543)

linux kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0x8f7a5000-0x8f7a8fff]

linux kernel: Problem loading in-kernel X.509 certificate (-129)

linux kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
linux kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=00000080/00006000
linux kernel: pcieport 0000:00:01.7:    [ 7] BadDLLP

linux kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
linux kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=00000040/00006000
linux kernel: pcieport 0000:00:01.7:    [ 6] BadTLP

linux kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
linux kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3

-- Unit systemd-backlight@backlight:amdgpu_bl0.service has begun starting up.
linux systemd-backlight[645]: Failed to get backlight or LED device'backlight:acpi_video0': No such device
linux systemd[1]: Mounting /boot/efi...
-- Subject: Unit boot-efi.mount has begun start-up

-- Unit boot-efi.mount has begun starting up.
linux systemd[1]: systemd-backlight@backlight:acpi_video0.service: Main process exited, code=exited, status=1/FAILURE
linux systemd[1]: systemd-backlight@backlight:acpi_video0.service: Failed with result 'exit-code'.
linux systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
-- Subject: Unit systemd-backlight@backlight:acpi_video0.service has failed

-- The start-up result is RESULT.
linux kernel: hid-generic 0003:1241:1503.0004: input,hidraw3: USB HID v1.10 Keyboard [  USB Keyboard] on usb-0000:03:00.4-2/input0
linux kernel: Bluetooth: hci0: using NVM file: qca/nvm_usb_00000302.bin
linux kernel: input:   USB Keyboard System Control as /devices/pci0000:00/0000:00:08.1/0000:03:00.4/usb3/3-2/3-2:1.1/0003:1241:1503.0005/input/input20
linux kernel: input:   USB Keyboard Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:03:00.4/usb3/3-2/3-2:1.1/0003:1241:1503.0005/input/input21
linux kernel: hid-generic 0003:1241:1503.0005: input,hidraw4: USB HID v1.10 Device [  USB Keyboard] on usb-0000:03:00.4-2/input1
linux kernel: usbcore: registered new interface driver usbhid
linux kernel: usbhid: USB HID core driver
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc514ec flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc515a8 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc51490 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc5149c flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc515e8 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc514b0 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc514c0 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc514e8 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc51514 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc51540 flags=0x0020]
linux kernel: amd_iommu_report_page_fault: 11 callbacks suppressed
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc4ebc0 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc4ec68 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc4eb50 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc4eb5c flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc4eca8 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc4eb70 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc4eb80 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc4eba8 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc4ebd4 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc4ec00 flags=0x0020]
linux kernel: amd_iommu_report_page_fault: 42 callbacks suppressed
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc48fec flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc49000 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc48f9c flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc490a8 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc490c0 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc48f90 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc490e8 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc49140 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc491c0 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc49100 flags=0x0020]
linux kernel: amd_iommu_report_page_fault: 29 callbacks suppressed
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc49180 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc491e8 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc49240 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc48fec flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc49000 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc48f9c flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc490a8 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc490c0 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc48f90 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc490e8 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc49140 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc491c0 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc49100 flags=0x0020]
linux kernel: amd_iommu_report_page_fault: 29 callbacks suppressed
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc49180 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc491e8 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc49240 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc492c0 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc49200 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc49280 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc492e8 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc49340 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc493c0 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc49300 flags=0x0020]
linux kernel: acpi AMDI0010:01: Already enumerated
linux kernel: amd_iommu_report_page_fault: 96 callbacks suppressed
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc3f26c flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc3f328 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc3f210 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc3f21c flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc3f368 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc3f230 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc3f240 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc3f268 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc3f294 flags=0x0020]
linux kernel: ath10k_pci 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000ffc3f2c0 flags=0x0020]
linux kernel: amd_iommu_report_page_fault: 86 callbacks suppressed
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc3f208 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc3f204 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc3f280 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc3c940 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc3c9e8 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc3c8d0 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc3c8dc flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc3ca28 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc3c8f0 flags=0x0020]
linux kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x00000000ffc3c900 flags=0x0020]

linux wpa_supplicant[827]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
linux wpa_supplicant[827]: dbus: Failed to construct signal

linux spice-vdagent[1258]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

linux pulseaudio[1244]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono

[123nobody456]

Some additional informations

ethtool -i wlp2s0

driver: ath10k_pci
Linux kernel-version: 5.0.0
firmware-version: WLAN.TF.2.1-00021-QCARMSWP-1
expansion-rom-version:
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

New journalctl report:

linux kernel: AMD-Vi: [Firmware Bug]: : IOAPIC[4] not in IVRS table
 linux kernel: AMD-Vi: [Firmware Bug]: : IOAPIC[5] not in IVRS table
 linux kernel: AMD-Vi: [Firmware Bug]: : No southbridge IOAPIC found
 linux kernel: AMD-Vi: Disabling interrupt remapping

 linux kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
 linux kernel: ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.LPC0.EC0._Q46], AE_ALREADY_EXISTS (20181213/dswload2-324)
 linux kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221)
 linux kernel: ACPI: Skipping parse of AML opcode: Method (0x0014)
 linux kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.GPP2.BCM5], AE_NOT_FOUND (20181213/dswload2-160)
 linux kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221)
 linux kernel: ACPI: Skipping parse of AML opcode: Scope (0x0010)

 linux kernel: AMD-Vi: Unable to write to IOMMU perf counter.

 linux kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0x8f7a5000-0x8f7a8fff]

 linux kernel: zswap: default zpool zbud not available
 linux kernel: zswap: pool creation failed

 linux kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
 linux kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3

-- Unit systemd-rfkill.service has begun starting up.
 linux kernel: acer_wmi: Acer Laptop ACPI-WMI Extras
 linux kernel: acer_wmi: Function bitmap for Communication Button: 0x801
 linux kernel: pcieport 0000:00:01.7: AER: Multiple Corrected error received: 0000:00:01.0
 linux kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
 linux kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=00000040/00006000
 linux kernel: pcieport 0000:00:01.7:    [ 6] BadTLP               
 linux systemd[1]: Started Load/Save RF Kill Switch Status.
-- Subject: Unit systemd-rfkill.service has finished start-up
-- Defined-By: systemd

-- The start-up result is RESULT.
 linux sddm[931]: Logind interface found
 linux sddm[931]: Starting...
 linux sddm[931]: Adding new display on vt 1 ...
 linux sddm[931]: Loading theme configuration from ""
 linux sddm[931]: Display server starting...
 linux sddm[931]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} -background none -noreset -displayfd 17 -seat seat0 vt1
 linux kernel: r8169 0000:01:00.1 enp1s0f1: Link is Down
 linux NetworkManager[823]: <info>  [1551820719.4752] wifi-nl80211: (wlp2s0): using nl80211 for WiFi device control
 linux NetworkManager[823]: <info>  [1551820719.4756] device (wlp2s0): driver supports Access Point (AP) mode
 linux NetworkManager[823]: <info>  [1551820719.4769] manager: (wlp2s0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/3)
 linux NetworkManager[823]: <info>  [1551820719.4781] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
 linux NetworkManager[823]: <warn>  [1551820719.4782] platform-linux: do-change-link[3]: failure changing link: failure 97 (Address family not supported by protocol)
 linux NetworkManager[823]: <warn>  [1551820719.4783] device (wlp2s0): failed to enable userspace IPv6LL address handling (unspecified)
 linux kernel: pcieport 0000:00:01.7: AER: Corrected error received: 0000:00:01.0
 linux kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
 linux kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=00000040/00006000
 linux kernel: pcieport 0000:00:01.7:    [ 6] BadTLP               
 linux kf5_snap.rb[921]: /usr/lib/neon_update/kf5_snap.rb:80:in `fetch': key not found: "slots" (KeyError)
 linux kf5_snap.rb[921]:         from /usr/lib/neon_update/kf5_snap.rb:80:in `block in <main>'
 linux kf5_snap.rb[921]:         from /usr/lib/neon_update/kf5_snap.rb:60:in `get'
 linux kf5_snap.rb[921]:         from /usr/lib/neon_update/kf5_snap.rb:76:in `<main>'
 linux systemd[1]: neon-update-kf5-snap.service: Main process exited, code=exited, status=1/FAILURE
 linux systemd[1]: neon-update-kf5-snap.service: Failed with result 'exit-code'.
 linux systemd[1]: Failed to start Remove kde-frameworks-5 snap if it is unused.
-- Subject: Unit neon-update-kf5-snap.service has failed
-- Defined-By: systemd

-- Userspace start-up required 1999852 microseconds.
 linux set-cpufreq[828]: Setting ondemand scheduler for all CPUs
 linux kernel: ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536
 linux NetworkManager[823]: <warn>  [1551820719.7409] Error: failed to open /run/network/ifstate
 linux NetworkManager[823]: <info>  [1551820719.7465] bluez: use BlueZ version 5
 linux NetworkManager[823]: <info>  [1551820719.7467] modem-manager: ModemManager available
 linux NetworkManager[823]: <info>  [1551820719.7476] supplicant: wpa_supplicant running
 linux NetworkManager[823]: <info>  [1551820719.7477] device (wlp2s0): supplicant interface state: init -> starting
 linux NetworkManager[823]: <info>  [1551820719.7490] bluez5: NAP: added interface xx:xx:xx:xx:xx:xx
 linux kernel: NET: Registered protocol family 17
 linux wpa_supplicant[837]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
 linux wpa_supplicant[837]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
 linux wpa_supplicant[837]: dbus: Failed to construct signal
 linux wpa_supplicant[837]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
 linux NetworkManager[823]: <info>  [1551820719.8010] device (wlp2s0): supplicant interface state: starting -> ready
 linux NetworkManager[823]: <info>  [1551820719.8011] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
 linux NetworkManager[823]: <warn>  [1551820719.8012] platform-linux: do-change-link[3]: failure changing link: failure 97 (Address family not supported by protocol)
 linux NetworkManager[823]: <warn>  [1551820719.8013] device (wlp2s0): failed to enable userspace IPv6LL address handling (unspecified)
 linux sddm[931]: Setting default cursor
 linux sddm[931]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
 linux sddm[931]: Display server started.
 linux sddm[931]: Socket server starting...
 linux sddm[931]: Socket server started.
 linux sddm[931]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
 linux sddm[931]: Greeter starting...
 linux sddm[931]: Adding cookie to "/var/run/sddm/{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}"
 linux sddm-helper[976]: [PAM] Starting...
 linux sddm-helper[976]: [PAM] Authenticating...
 linux sddm-helper[976]: [PAM] returning.
 linux sddm-helper[976]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
 linux systemd[1]: Created slice User Slice of sddm.
-- Subject: Unit user-116.slice has finished start-up
-- Defined-By: systemd

 linux spice-vdagent[1237]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

 linux pulseaudio[1218]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono

[misterx]

Did you kill network managers with airmon-ng check kill BEFORE putting it in monitor mode?

[123nobody456]

Did you kill network managers with airmon-ng check kill BEFORE putting it in monitor mode?

of course i killed the NetworkManager and wap-supplicant with

airmon-ng check kill
airmon-ng start wlp2s0
airodump-ng wlp2s0mon

[123nobody456]

I also downloaded Kali-Linux and Ubuntu 18.10 and try´d Aircrack-ng on the Live version, same problem. Musst be a hardware issue, i hopped a ath-10k-firmware update would fix it.

[madafakaz]

here's how it works and why:

when you start mon interface with airmon-ng and have sta interface disconnected airodump will not find any AP
if you have sta interface connected to an AP and run airodump on mon interface it will find AP
or if you put sta interface down e.g. ifconfig wlanX down and leave only mon interface active airodump will find AP

this is at least how it works with qca9880 and it's probably the same with qca6174

i just check this with qca9377, it works only if connected to an AP at the same time, and that is on clean 16.04.6 ubuntu system while my qca9880 runs on patched 10.04 ubuntu. if patched all drivers settings on 16.04.6 behaviour would most likely be identical

[Buddhika Nawod]

Does qca9377 support monitor mode?

[Kirk Shrewsbury]

From Qualcomm developer network forum:  " Regarding your prior query on Monitor Mode (you need this feature to run an injector), sorry QCA9377 doesn't support it."

[madder]

I've posted a fix here check it out
https://forum.aircrack-ng.org/index.php?topic=2545.0