[ath10k_pci] Not able to see visible devices when wifi is turned on please verify.

[Shivam Tiwari]

Not able to see available devices in wifi panel.
---
ProblemType: Bug
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: fyriousfighter 3764 F.... wireplumber
 /dev/snd/seq: fyriousfighter 3754 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.04
InstallationDate: Installed on 2021-02-13 (927 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
MachineType: Dell Inc. Inspiron 5567
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=eb0f7397-d28a-4d11-ac7b-51001c65f6d3 ro quiet splash i8042.nomux i8024.noloop vt.handoff=7
ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-32-generic N/A
 linux-backports-modules-6.2.0-32-generic N/A
 linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.6
Tags: lunar wayland-session
Uname: Linux 6.2.0-32-generic x86_64
UpgradeStatus: Upgraded to lunar on 2023-08-26 (2 days ago)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/14/2018
dmi.bios.release: 1.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.5
dmi.board.name: 0DG5G3
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd05/14/2018:br1.2:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn0DG5G3:rvrA03:cvnDellInc.:ct10:cvr:sku0767:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5567
dmi.product.sku: 0767
dmi.sys.vendor: Dell Inc.

[Daniel van Vugt (vanvugt)]

Please run:

  apport-collect 2033260
  rfkill > rfkill.txt
  lspci > lspci.txt
  lsusb > lsusb.txt
  journalctl -b0 > journal.txt

and attach the resulting text files here.

[Shivam Tiwari (st123)]

rfkill.txt

[Shivam Tiwari (st123)]

lspci.txt

[Shivam Tiwari (st123)]

lsusb.txt

[Shivam Tiwari (st123)]

journal.txt

[Shivam Tiwari (st123)]

journalctl b0

[Daniel van Vugt (vanvugt)]

Your logs are full of errors from the ath10k_pci and r8169 kernel drivers, so this is a kernel bug (or a hardware fault).

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 2033260

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Shivam Tiwari (st123)]

apport information

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1875756, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.