Just a comment, I too am seeing the htc 1536 error following something along the lines of pdev 0 cannot be set, I believe the 1536 is actually the length of the previous kernel msg

[    5.979641] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[    6.263245] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[    6.263252] ath10k_pci 0000:01:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0
[    6.263598] ath10k_pci 0000:01:00.0: firmware ver 10.2.4-1.0-00041 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 f43fa422
[    6.301982] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[    7.566975] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
[    7.588108] ath10k_pci 0000:01:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1
[    7.712550] ath10k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
[    9.265597] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
[    9.286847] ath10k_pci 0000:01:00.0: pdev param 0 not supported by firmware
[   10.801252] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
[   10.822294] ath10k_pci 0000:01:00.0: pdev param 0 not supported by firmware
[   19.533916] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
[   19.555015] ath10k_pci 0000:01:00.0: pdev param 0 not supported by firmware
[   73.793452] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
[   73.814662] ath10k_pci 0000:01:00.0: pdev param 0 not supported by firmware
[   82.302021] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
[   82.323382] ath10k_pci 0000:01:00.0: pdev param 0 not supported by firmware

linux-firmware-20181218.0f22c85 has same outputs to dmesg, but hostapd seems to work with that version, whereas the more recent firmware packages it ends up disabling the interfaces / "doesn't"

So in my case, the latest from the official unofficial upstream https://github.com/kvalo/ath10k-firmware/ is working. I assume it'll make it into linux-firmware soon. I also encountered a recently addressed bug in mac80211 (see: https://patchwork.kernel.org/patch/10814377/ ) where beacon_interval was set to zero during the failure of the configuration of the virtual interfaces/dev parameters, which made it impossible to create additional virtual interface/ap afterward.

(In reply to William McLean from comment #0)
> User-Agent:       Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:65.0)
> Gecko/20100101 Firefox/65.0
> Build Identifier: 
> 
> I have a Lenovo Miix 510.  Doing 'lspci -k' produces
> 
> 1:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless
> Network Adapter (rev 31)
> 	Subsystem: Lenovo Device 0901
> 	Kernel driver in use: ath10k_pci
> 	Kernel modules: ath10k_pci
> 
> Looking at the output from dmesg I notice
> 
> [    6.587462] ath10k_pci 0000:01:00.0: qca9377 hw1.1 target 0x05020001
> chip_id 0x003821ff sub 17aa:0901
> [    6.587464] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0
> dfs 0 testmode 0
> [    6.587898] ath10k_pci 0000:01:00.0: firmware ver
> WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877
> [    6.657137] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id N/A crc32
> 8aedfa4a
> [    6.733584] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
> [    6.749116] ath10k_pci 0000:01:00.0: Unknown eventid: 118809
> [    6.752057] ath10k_pci 0000:01:00.0: Unknown eventid: 90118
> [    6.752841] ath10k_pci 0000:01:00.0: htt-ver 3.56 wmi-op 4 htt-op 3 cal
> otp max-sta 32 raw 0 hwcrypto 1
> [    6.756009] ath: EEPROM regdomain: 0x6c
> [    6.756012] ath: EEPROM indicates we should expect a direct regpair map
> [    6.756043] ath: Country alpha2 being used: 00
> [    6.756045] ath: Regpair used: 0x6c
> [    6.759431] EXT4-fs (sda3): mounted filesystem with ordered data mode.
> Opts: (null)
> [    6.805835] ath10k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
> 
> However, Gnome settings reports 'No WiFi Adapter Found'.  If I run
> 'journalctl -f' and attempt turn on WiFi in Gnome settings, I see
> 
> Feb 02 16:10:37 localhost.localdomain NetworkManager[841]: <info> 
> [1549084237.4025] audit: op="radio-control" arg="wireless-enabled" pid=2806
> uid=1000 result="success"
> 
> but still get 'No WiFi Adapter Found'.
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1. Start laptop
> 2. Log in
> 3. No WiFi
> Actual Results:  
> No WiFi adapter found.
> 
> Expected Results:  
> WiFi adaptor detected.
> 
> Running kernel 4.20.4-200.fc29.x86_64

Just curious, what is your output from "iw phy"

Created attachment 1538291 [details]
Output of 'iw phy'

I have uploaded the output of 'iw phy' as an attachment.

(In reply to William McLean from comment #6)
> I have uploaded the output of 'iw phy' as an attachment.

In your case your wireless card is there, it just might not have a virtual interface? "iw dev" to see-- but if thats the case try adding one:

iw phy0 interface add wlan0 type managed

gnome also makes use of NetworkManager so make sure that service is started, check "rfkill list" as well, and possibly "rfkill unblock all" to re-enable cards that are switched off.

Not sure what may have changed in your case/env, would be interested to know if you're able to add the interface, and if there are any errors in "dmesg | grep ath"

Justin,

Thanks for your suggestions. Here is the output you wanted to see.

$ iw dev
phy#0
	Interface wlp1s0
		ifindex 3
		wdev 0x1
		addr 46:60:db:46:39:08
		type managed
		txpower 0.00 dBm

$ systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-03-12 15:32:22 AEDT; 17min ago
     Docs: man:NetworkManager(8)
 Main PID: 861 (NetworkManager)
    Tasks: 4 (limit: 4915)
   Memory: 17.5M
   CGroup: /system.slice/NetworkManager.service
           ├─ 861 /usr/sbin/NetworkManager --no-daemon
           └─2843 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-enp0s20f0u2.pid -lf /var/lib/Netw>

Mar 12 15:36:38 tempt030.maths.unsw.edu.au NetworkManager[861]: <info>  [1552365398.0964] dhcp4 (enp0s20f0u2):   gateway 129.9>
Mar 12 15:36:38 tempt030.maths.unsw.edu.au NetworkManager[861]: <info>  [1552365398.0965] dhcp4 (enp0s20f0u2):   lease time 28>
Mar 12 15:36:38 tempt030.maths.unsw.edu.au NetworkManager[861]: <info>  [1552365398.0965] dhcp4 (enp0s20f0u2):   nameserver '1>
Mar 12 15:36:38 tempt030.maths.unsw.edu.au NetworkManager[861]: <info>  [1552365398.0965] dhcp4 (enp0s20f0u2):   nameserver '1>
Mar 12 15:36:38 tempt030.maths.unsw.edu.au NetworkManager[861]: <info>  [1552365398.0966] dhcp4 (enp0s20f0u2):   domain name '>
Mar 12 15:36:38 tempt030.maths.unsw.edu.au NetworkManager[861]: <info>  [1552365398.0966] dhcp4 (enp0s20f0u2): state changed u>
Mar 12 15:36:38 tempt030.maths.unsw.edu.au dhclient[2843]: bound to 129.94.176.190 -- renewal in 13763 seconds.
Mar 12 15:39:32 tempt030.maths.unsw.edu.au NetworkManager[861]: <info>  [1552365572.5399] audit: op="radio-control" arg="wirel>
Mar 12 15:39:41 tempt030.maths.unsw.edu.au NetworkManager[861]: <info>  [1552365581.6848] audit: op="radio-control" arg="wirel>
Mar 12 15:39:52 tempt030.maths.unsw.edu.au NetworkManager[861]: <info>  [1552365592.5018] audit: op="radio-control" arg="wirel>

$ rfkill unblock all
$ rfkill list
0: ideapad_wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: yes
1: ideapad_bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: yes
2: ideapad_3g: Wireless WAN
	Soft blocked: no
	Hard blocked: yes
3: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
4: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

$ dmesg | grep ath
[    8.855357] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[    9.106992] ath10k_pci 0000:01:00.0: qca9377 hw1.1 target 0x05020001 chip_id 0x003821ff sub 17aa:0901
[    9.106998] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[    9.108520] ath10k_pci 0000:01:00.0: firmware ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877
[    9.177650] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id N/A crc32 8aedfa4a
[    9.254154] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
[    9.269374] ath10k_pci 0000:01:00.0: Unknown eventid: 118809
[    9.272295] ath10k_pci 0000:01:00.0: Unknown eventid: 90118
[    9.273363] ath10k_pci 0000:01:00.0: htt-ver 3.56 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[    9.277387] ath: EEPROM regdomain: 0x6c
[    9.277390] ath: EEPROM indicates we should expect a direct regpair map
[    9.277396] ath: Country alpha2 being used: 00
[    9.277398] ath: Regpair used: 0x6c
[    9.343109] ath10k_pci 0000:01:00.0 wlp1s0: renamed from wlan0

Gnome settings still shows 'No Wi-Fi Adapter Found'.

The wireless/bluetooth adapters seem to indicate hard blocked, which would usually be a switch or perhaps a keyboard FN combination

Bluetooth works, and I have no problems using WiFi under Windows.  There is no physical WiFi switch (although the F7 key toggles airplane mode).  The WiFi setting in the Bios is enabled.

Ok, and just so you know I'm not affiliated with Redhat in any way-- don't want you to get the wrong idea!

Looking over your dmesg again, I'm thinking perhaps it has something to do with CRDA / the regdomain. It looks like it is not correctly setting your regulatory domain. The interface is clearly there though, I'm not sure what Gnome is actually checking before showing the adapters. You might try using the Network Manager command line tool, just as a test.

To list existing profiles:
nmcli connection

To tell it to activate/connect to profile named "Wireless 1" (can use guid from above):
nmcli connection "Wireless 1" up

This of course assumes you have a profile created... If this works I would be inclined to call this a Gnome bug.

Perhaps take a look at this: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-setting_wireless_regulatory_domain

Anyways, good luck. I'll leave it up to the Redhat folks to take it from here

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

FTR, modprobe -r ideapad_laptop helped me (IdeaPad S145-15IWL (81MV011ACK)),
running epel8 box though:
kernel-4.18.0-80.11.2.el8_0.x86_64
linux-firmware-20190111-92.gitd9fb2ee6.el8.noarch

Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.