Wireless issue with WCA6174

Issues related to configuring your network
Post Reply
pegruder
Posts: 3
Joined: 2017/11/14 14:47:36

Wireless issue with WCA6174

Post by pegruder » 2017/11/14 14:52:23

Hey folks, running CentOS 7.4 on a new Lenovo Yoga 920 with the QCA6174 wifi adapter and am having issues. When I toggle the wifi to on nothing seems to happen. I've tried recommendations from various posts including trying the elrepo with no luck. Any ideas?

lspci -nn | grep -i Net
6b:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)

User avatar
TrevorH
Site Admin
Posts: 33216
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Wireless issue with WCA6174

Post by TrevorH » 2017/11/14 16:10:19

Code: Select all

# grep -i 168c /lib/modules/3.10.0-693.5.2.el7.x86_64/modules.* | grep -i 003e
/lib/modules/3.10.0-693.5.2.el7.x86_64/modules.alias:alias pci:v0000168Cd0000003Esv*sd*bc*sc*i* ath10k_pci
modprobe ath10k_pci and see if your interface then appears in the output of `ifconfig -a` or `ip link show`
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

pegruder
Posts: 3
Joined: 2017/11/14 14:47:36

Re: Wireless issue with WCA6174

Post by pegruder » 2017/11/14 16:26:40

TrevorH wrote:

Code: Select all

# grep -i 168c /lib/modules/3.10.0-693.5.2.el7.x86_64/modules.* | grep -i 003e
/lib/modules/3.10.0-693.5.2.el7.x86_64/modules.alias:alias pci:v0000168Cd0000003Esv*sd*bc*sc*i* ath10k_pci
modprobe ath10k_pci and see if your interface then appears in the output of `ifconfig -a` or `ip link show`
Here is the output:

Code: Select all

 grep -i 168c /lib/modules/3.10.0-693.5.2.el7.x86_64/modules.* | grep -i 003e
/lib/modules/3.10.0-693.5.2.el7.x86_64/modules.alias:alias pci:v0000168Cd0000003Esv*sd*bc*sc*i* ath10k_pci
[cchris@localhost Downloads]$ sudo modprobe ath10k_pci

Downloads]$ ifconfig -a
enp0s20f0u1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.128.112.82  netmask 255.255.255.0  broadcast 10.128.112.255
        inet6 fe80::3d67:c8c4:56fa:a196  prefixlen 64  scopeid 0x20<link>
        ether a0:ce:c8:03:84:02  txqueuelen 1000  (Ethernet)
        RX packets 78523  bytes 22621535 (21.5 MiB)
        RX errors 0  dropped 27  overruns 0  frame 0
        TX packets 19683  bytes 2343507 (2.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 692  bytes 38706 (37.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 692  bytes 38706 (37.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:56:03:ac  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0-nic: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 52:54:00:56:03:ac  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp107s0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether ce:7b:9e:71:1f:ad  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Downloads]$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s20f0u1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
    link/ether a0:ce:c8:03:84:02 brd ff:ff:ff:ff:ff:ff
3: wlp107s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether ce:7b:9e:71:1f:ad brd ff:ff:ff:ff:ff:ff
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT qlen 1000
    link/ether 52:54:00:56:03:ac brd ff:ff:ff:ff:ff:ff
5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN mode DEFAULT qlen 1000
    link/ether 52:54:00:56:03:ac brd ff:ff:ff:ff:ff:ff

User avatar
TrevorH
Site Admin
Posts: 33216
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Wireless issue with WCA6174

Post by TrevorH » 2017/11/14 16:43:02

Well I'm not sure how you've managed to get an enp0s20f0u1 (looks like wired) and an wlp107s0 interface but the wl one is a wireless one. Now you need to configure it using nmcli/nmtui or manually using an ifcfg file.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

pegruder
Posts: 3
Joined: 2017/11/14 14:47:36

Re: Wireless issue with WCA6174

Post by pegruder » 2017/11/14 16:48:19

TrevorH wrote:Well I'm not sure how you've managed to get an enp0s20f0u1 (looks like wired) and an wlp107s0 interface but the wl one is a wireless one. Now you need to configure it using nmcli/nmtui or manually using an ifcfg file.
I do have a USB wired adapter connected at the moment which should be why thats showing up. I'll try and configure it but it tells me unavailable:

Code: Select all

wnmcli
virbr0: connected to virbr0
	"virbr0"
	bridge, 52:54:00:56:03:AC, sw, mtu 1500
	inet4 192.168.122.1/24


wlp107s0: unavailable
	"Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter"
	wifi (ath10k_pci), CE:7B:9E:71:1F:AD, hw, mtu 1500

lo: unmanaged
	"lo"
	loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536



Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(5) manual pages for complete usage details.


Post Reply