On 31/05/2019 19:07, senthil kosapeta wrote:
Hi, These are the logs that i got, it says "firmware loading failed" *May 31 12:58:48 debian kernel: [ 0.048770] Spectre V2 : Enabling Restricted Speculation for firmware calls* *May 31 12:58:48 debian kernel: [ 7.671866] i915 0000:00:02.0: Direct firmware load for i915/kbl_dmc_ver1_01.bin failed with error -2May 31 12:58:48 debian kernel: [ 7.671873] i915 0000:00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/intel-linux-graphics-firmwares <https://01.org/linuxgraphics/intel-linux-graphics-firmwares>], disabling runtime power management.May 31 12:58:48 debian kernel: [ 7.677946] [drm] GuC firmware load skippedMay 31 12:58:48 debian kernel: [ 8.226104] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:03:00.0.bin failed with error -2May 31 12:58:48 debian kernel: [ 8.226118] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2May 31 12:58:48 debian kernel: [ 8.226129] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA9377/hw1.0/firmware-5.bin failed with error -2May 31 12:58:48 debian kernel: [ 8.226143] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA9377/hw1.0/firmware-4.bin failed with error -2May 31 12:58:48 debian kernel: [ 8.226156] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA9377/hw1.0/firmware-3.bin failed with error -2May 31 12:58:48 debian kernel: [ 8.226168] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA9377/hw1.0/firmware-2.bin failed with error -2May 31 12:58:50 debian NetworkManager[559]: <info> [1559287730.5479] manager[0x5578b9b35040]: monitoring kernel firmware directory '/lib/firmware'.May 31 12:58:50 debian kernel: [ 16.179299] r8169 0000:02:00.0: Direct firmware load for rtl_nic/rtl8168g-3.fw failed with error -2May 31 12:58:50 debian kernel: [ 16.179307] r8169 0000:02:00.0 enp2s0: unable to load firmware patch rtl_nic/rtl8168g-3.fw (-2)May 31 14:37:49 debian kernel: [ 5323.527328] [drm] GuC firmware load skippedMay 31 18:44:53 debian kernel: [11230.812795] [drm] GuC firmware load skipped* On Fri, May 31, 2019 at 4:46 PM tv.debian@googlemail.com < tv.debian@googlemail.com> wrote:On 31/05/2019 15:46, senthil kosapeta wrote:Dear Debians, I have purchased Lenovo laptop around 6 months back. (Lenovo ideapad) I had installed ubuntu earlier and Wifi used to work fine. Somehow it got crashed a month back. I have decided to switch over to debian 9.9 and installed it. Internet via Ethernet port is working. But wifi is not working and not showing available wireless networks. I searched/googled certain topic related to Debian wifi and tried installing firmware-atheros earlier. It did not work. When i tried restart, shutdown is stuck. If i force shutdown and restart, It will be stuck again. When i tried to do recover mode, msg displays that "ath10k_pci ** failed recieve control reponse completion, polling ...." Please let me know how to proceed. Thanks SenthilHi, can you check for firmware loading information in your logs ? "grep firmware /var/log/messages" or "journalctl -b" and look for info related to the wifi chip. Given the "shutdown stuck" issue I would try disabling interrupts and see if it solves the problem, "modinfo" says ath10k_pci accepts three irq options: "parm: irq_mode:0: auto, 1: legacy, 2: msi" Maybe try "legacy" mode first, that may be what Ubuntu is doing as a default. You will need elevated privileges to run the next commands ("sudo command" or "su -" and then type commands). First two commands unload the driver module: modprobe -r ath10k_pci modprobe -r ath10k_core Then reload it with proper option: modprobe -v ath10k_core modprobe -v ath10k_pci irq_mode=1 If it solves the problem you can make the change permanent. Hope it helps.
The error message is very generic (ignore the message regarding the graphic chip, it's unrelated and mostly harmless).
First look into the firmware directory to make sure you do have the needed firmware binary:
ls -l /lib/firmware/ath10k/QCA9377/hw1.0/ You should see a "firmware-6.bin" file in the output.Then try the commands I suggested before in a terminal window, you need to do this as root, either by using "sudo" in front of the commands or by doing "su -" and ater providing the root password type the actual commands one line at a time:
modprobe -r ath10k_pci modprobe -r ath10k_core modprobe -v ath10k_core modprobe -v ath10k_pci irq_mode=1 and report back to the list the outcome.