Wireless not working after updating kernel-firmware

Hi everybody,
I’m using a Lenovo laptop, Ideapad 500; as soon as I apply the latest patches and reboot, I completely lost wireless connection. Kernel logs show:

Jan 15 21:18:09 portatile kernel: ath10k_pci 0000:03:00.0: unable to read from the deviceJan 15 21:18:09 portatile kernel: ath10k_pci 0000:03:00.0: could not execute otp for board id check: -110
Jan 15 21:18:09 portatile kernel: ath10k_pci 0000:03:00.0: failed to get board id from otp: -110
Jan 15 21:18:09 portatile kernel: ath10k_pci 0000:03:00.0: could not probe fw (-110)

As you see kernel module is ath10k_pci. The actual wireless hardware is

22: PCI 300.0: 0282 WLAN controller  [Created at pci.378]
  Unique ID: y9sn.QC79k097vy2
  Parent ID: HnsE.JEvSNgJfDgD
  SysFS ID: /devices/pci0000:00/0000:00:1c.5/0000:03:00.0
  SysFS BusID: 0000:03:00.0
  Hardware Class: network
  Model: "Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter"
  Vendor: pci 0x168c "Qualcomm Atheros"
  Device: pci 0x0042 "QCA9377 802.11ac Wireless Network Adapter"
  SubVendor: pci 0x17aa "Lenovo"
  SubDevice: pci 0x4035 
  Revision: 0x30
  Driver: "ath10k_pci"
  Driver Modules: "ath10k_pci"
  Device File: wlan0
  Features: WLAN
  Memory Range: 0xa2000000-0xa21fffff (rw,non-prefetchable)
  IRQ: 128 (48417 events)
  HW Address: c8:ff:28:50:bf:7d
  Permanent HW Address: c8:ff:28:50:bf:7d
  Link detected: yes
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 5.64 5.66 5.68 5.7
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Module Alias: "pci:v0000168Cd00000042sv000017AAsd00004035bc02sc80i00"
  Driver Info #0:
    Driver Status: ath10k_pci is active
    Driver Activation Cmd: "modprobe ath10k_pci"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #26 (PCI bridge)

I can restore connectivity only by reverting from latest btrfs snapshot, which not include the latest updates:


# zypper lu
Loading repository data...
Reading installed packages...
S | Repository                | Name                   | Current Version       | Available Version     | Arch  
--+---------------------------+------------------------+-----------------------+-----------------------+-------
v | openSUSE-Leap-15.0-Update | acl                    | 2.2.52-lp150.2.46     | 2.2.52-lp150.3.3.1    | x86_64
v | openSUSE-Leap-15.0-Update | apparmor-abstractions  | 2.12-lp150.6.3.1      | 2.12-lp150.6.6.1      | noarch
v | openSUSE-Leap-15.0-Update | apparmor-docs          | 2.12-lp150.6.3.1      | 2.12-lp150.6.6.1      | noarch
v | openSUSE-Leap-15.0-Update | apparmor-parser        | 2.12-lp150.6.3.1      | 2.12-lp150.6.6.1      | x86_64
v | openSUSE-Leap-15.0-Update | apparmor-parser-lang   | 2.12-lp150.6.3.1      | 2.12-lp150.6.6.1      | noarch
v | openSUSE-Leap-15.0-Update | apparmor-profiles      | 2.12-lp150.6.3.1      | 2.12-lp150.6.6.1      | noarch
v | openSUSE-Leap-15.0-Update | apparmor-utils         | 2.12-lp150.6.3.1      | 2.12-lp150.6.6.1      | noarch
v | openSUSE-Leap-15.0-Update | apparmor-utils-lang    | 2.12-lp150.6.3.1      | 2.12-lp150.6.6.1      | noarch
v | Visual Studio Code        | code                   | 1.28.2-1539736121.el7 | 1.30.2-1546901769.el7 | x86_64
v | openSUSE-Leap-15.0-Update | gdm                    | 3.26.2.1-lp150.11.3.1 | 3.26.2.1-lp150.11.6.1 | x86_64
v | openSUSE-Leap-15.0-Update | gdm-lang               | 3.26.2.1-lp150.11.3.1 | 3.26.2.1-lp150.11.6.1 | noarch
v | openSUSE-Leap-15.0-Update | gdmflexiserver         | 3.26.2.1-lp150.11.3.1 | 3.26.2.1-lp150.11.6.1 | noarch
v | openSUSE-Leap-15.0-Update | gpg2                   | 2.2.5-lp150.3.3.1     | 2.2.5-lp150.3.6.1     | x86_64
v | openSUSE-Leap-15.0-Update | gpg2-lang              | 2.2.5-lp150.3.3.1     | 2.2.5-lp150.3.6.1     | noarch
v | openSUSE-Leap-15.0-Update | kernel-firmware        | 20180525-lp150.2.3.1  | 20181026-lp150.2.6.1  | noarch
v | openSUSE-Leap-15.0-Update | libacl1                | 2.2.52-lp150.2.46     | 2.2.52-lp150.3.3.1    | x86_64
v | openSUSE-Leap-15.0-Update | libacl1-32bit          | 2.2.52-lp150.2.46     | 2.2.52-lp150.3.3.1    | x86_64
v | openSUSE-Leap-15.0-Update | libapparmor-devel      | 2.12-lp150.6.3.1      | 2.12-lp150.6.6.1      | x86_64
v | openSUSE-Leap-15.0-Update | libapparmor1           | 2.12-lp150.6.3.1      | 2.12-lp150.6.6.1      | x86_64
v | openSUSE-Leap-15.0-Update | libgdm1                | 3.26.2.1-lp150.11.3.1 | 3.26.2.1-lp150.11.6.1 | x86_64
v | openSUSE-Leap-15.0-Update | libpolkit0             | 0.114-lp150.2.3.1     | 0.114-lp150.2.6.1     | x86_64
v | openSUSE-Leap-15.0-Update | osinfo-db              | 20180720-lp150.2.6.1  | 20181116-lp150.2.9.1  | noarch
v | openSUSE-Leap-15.0-Update | perl-apparmor          | 2.12-lp150.6.3.1      | 2.12-lp150.6.6.1      | x86_64
v | openSUSE-Leap-15.0-Update | polkit                 | 0.114-lp150.2.3.1     | 0.114-lp150.2.6.1     | x86_64
v | openSUSE-Leap-15.0-Update | python3-apparmor       | 2.12-lp150.6.3.1      | 2.12-lp150.6.6.1      | x86_64
v | TeamViewer - x86_64       | teamviewer-suse        | 13.2.13582-0          | 14.1.3399-0           | x86_64
v | openSUSE-Leap-15.0-Update | typelib-1_0-Gdm-1_0    | 3.26.2.1-lp150.11.3.1 | 3.26.2.1-lp150.11.6.1 | x86_64
v | openSUSE-Leap-15.0-Update | typelib-1_0-Polkit-1_0 | 0.114-lp150.2.3.1     | 0.114-lp150.2.6.1     | x86_64
v | openSUSE-Leap-15.0-Update | ucode-amd              | 20180525-lp150.2.3.1  | 20181026-lp150.2.6.1  | noarch
v | openSUSE-Leap-15.0-Update | xfsprogs               | 4.15.0-lp150.3.4.1    | 4.15.0-lp150.3.7.1    | x86_64
v | openSUSE-Leap-15.0-Update | yast2-storage-ng       | 4.0.215-lp150.2.18.1  | 4.0.216-lp150.2.21.1  | x86_64



I suspect the fault is of kernel-firmware update.

Any help will be greatly appreciated

Roberto

https://forums.opensuse.org/showthread.php/534542-Kernel-firmware-update-20181026-lp150-2-6-1-locks-up-system

Many thanks
Roberto