Qualcomm Atheros QCA61x4 issues with Linux Topic is solved
Moderator: jkerr82508
Re: Qualcomm Atheros QCA61x4 issues with Linux
Strange. That seems like the password to use.
Manjaro 64bit on the main box -Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz and nVidia Corporation GT200b [GeForce GTX 275] (rev a1. + Centos on the server - Arch on the laptop.
"There are no stupid questions - Only stupid answers!"
"There are no stupid questions - Only stupid answers!"
- dedanna1029
- Sound-Berserk
- Posts: 8780
- Joined: 14 Mar 2010, 20:29
- Contact:
Re: Qualcomm Atheros QCA61x4 issues with Linux
Aye, it does seem so to me too.
There's been a new commit from kvalo, and Thomas has built a new kernel and kernel-firmware-nonfree for this thing, to go with the new board.bin and firmware-5.bin.
I've installed the new kernel and kernel-firmware-nonfree, but ran out of energy for the day to plop in the board.bin and firmware-5.bin to their respective folder (/lib/firmware/ath10k/QCA6174/hw2.1). I'll do it tomorrow; let's hope it works. There's new information on the bug without the new things. The new commit from kvalo is only a very few days old.
There's been a new commit from kvalo, and Thomas has built a new kernel and kernel-firmware-nonfree for this thing, to go with the new board.bin and firmware-5.bin.
I've installed the new kernel and kernel-firmware-nonfree, but ran out of energy for the day to plop in the board.bin and firmware-5.bin to their respective folder (/lib/firmware/ath10k/QCA6174/hw2.1). I'll do it tomorrow; let's hope it works. There's new information on the bug without the new things. The new commit from kvalo is only a very few days old.
I'd rather be a free person who fears terrorists, than be a "safe" person who fears the government.
No gods, no masters.
"A druid is by nature anarchistic, that is, submits to no one."
http://uk.druidcollege.org/faqs.html
No gods, no masters.
"A druid is by nature anarchistic, that is, submits to no one."
http://uk.druidcollege.org/faqs.html
- dedanna1029
- Sound-Berserk
- Posts: 8780
- Joined: 14 Mar 2010, 20:29
- Contact:
Re: Qualcomm Atheros QCA61x4 issues with Linux
OK, I've got to be doing something wrong. Mageia is now seeing the wireless connections around me, including mine. Network Manager is running, and I can set up the connection. My options for encryption are:
None
Open WEP
Restricted WEP
WPA/WPA2 Enterprise
WPA/WPA2 Pre-shared Key
Network Manager is finding my connection as being Pre-shared Key, which I believe is correct. However, I put in my password, and the connection fails on test.
I've tried it on all the other settings, including None (wide open), but the connection fails on test every time.
I'm so close I can taste it. I don't get this.
None
Open WEP
Restricted WEP
WPA/WPA2 Enterprise
WPA/WPA2 Pre-shared Key
Network Manager is finding my connection as being Pre-shared Key, which I believe is correct. However, I put in my password, and the connection fails on test.
I've tried it on all the other settings, including None (wide open), but the connection fails on test every time.
I'm so close I can taste it. I don't get this.
I'd rather be a free person who fears terrorists, than be a "safe" person who fears the government.
No gods, no masters.
"A druid is by nature anarchistic, that is, submits to no one."
http://uk.druidcollege.org/faqs.html
No gods, no masters.
"A druid is by nature anarchistic, that is, submits to no one."
http://uk.druidcollege.org/faqs.html
Re: Qualcomm Atheros QCA61x4 issues with Linux
WPA/WPA2 Pre-shared Key or PSK seems to be OK(but you need to use the correct one).
You entered those data like SSID and password key in the IPv4 settings:
Things to check:
Check out the part that starts with "Ethernet controller" it will show the driver you are using (should be ath10k).
Check that ath10k is loaded with:
....
Or better yet; just post the output of
Check the name of your wireless (often wlan0) with:
This should be reported by:
as root
So if your Network Interface is wlan0 then you can start it with
and stop it with
To check that your connection is up:
If it is good it will show a BROADCAST message.
Now how Mageia gets the IP address is not clear to me (cause I don't use it anymore) but it is probably done by systemd-networkd
So check the output of:
(as root)
If it is not up try to start it with
For this to run you need a working wpa-supplicant... there is a lot more to check but I guess this is a start....
You are not supposed to edit that directly: Mageias wizards should set it up for you.
You entered those data like SSID and password key in the IPv4 settings:
Things to check:
Code: Select all
lspci -v
Check out the part that starts with "Ethernet controller" it will show the driver you are using (should be ath10k).
Check that ath10k is loaded with:
Code: Select all
dmesg |grep ath10k
....
Or better yet; just post the output of
Code: Select all
inxi -n
Check the name of your wireless (often wlan0) with:
Code: Select all
ls /sys/class/net
This should be reported by:
as root
Code: Select all
ip link
So if your Network Interface is wlan0 then you can start it with
Code: Select all
ip link set wlan0 up
and stop it with
Code: Select all
ip link set wlan0 down
To check that your connection is up:
Code: Select all
sudo ip link show dev wlan0
If it is good it will show a BROADCAST message.
Now how Mageia gets the IP address is not clear to me (cause I don't use it anymore) but it is probably done by systemd-networkd
So check the output of:
(as root)
Code: Select all
sudo systemctl status network systemd-netorkd.service
If it is not up try to start it with
Code: Select all
sudo systemctl start network systemd-netorkd.service
For this to run you need a working wpa-supplicant... there is a lot more to check but I guess this is a start....
Code: Select all
cat /etc/resolv,conf
You are not supposed to edit that directly: Mageias wizards should set it up for you.
Manjaro 64bit on the main box -Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz and nVidia Corporation GT200b [GeForce GTX 275] (rev a1. + Centos on the server - Arch on the laptop.
"There are no stupid questions - Only stupid answers!"
"There are no stupid questions - Only stupid answers!"
- dedanna1029
- Sound-Berserk
- Posts: 8780
- Joined: 14 Mar 2010, 20:29
- Contact:
Re: Qualcomm Atheros QCA61x4 issues with Linux
Thanks, viking. Here's the rub:
In the process of things at Bug #16915, Thomas had me go in and enable NetworkManager and NetworkManager-wait-online, and disable network. Nonetheless, here are the outputs (it's too much to quote you on these in order and break the quotes, but you'll find the outputs right down the line). I have also reported these results to the bug:
Even if repetitive, here's the inxi -n:
I then ran "ip link set wlp3s0 up" again before I moved on. I was already in root (well, almost anyway; just su, not su -), and I don't use sudo, so kept it where I was at:
Edit for code correction:
/edit
I've split up each command for easier reading. I'm beginning to see what's going on. It seems the firmware isn't loading, but if it isn't loading, then how is Network Manager seeing wireless connections? Also, how am I getting a "Wireless connections are available" popup in the lower right of the screen upon login?
In the process of things at Bug #16915, Thomas had me go in and enable NetworkManager and NetworkManager-wait-online, and disable network. Nonetheless, here are the outputs (it's too much to quote you on these in order and break the quotes, but you'll find the outputs right down the line). I have also reported these results to the bug:
Code: Select all
[root@localhost dedanna]# lspci -v
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
Subsystem: Lenovo Device 3987
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0c <?>
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device 381c
Flags: bus master, fast devsel, latency 0, IRQ 47
Memory at c2000000 (64-bit, non-prefetchable) [size=16M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 5000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
Subsystem: Lenovo Device 3987
Flags: bus master, fast devsel, latency 0, IRQ 58
Memory at c4310000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03) (prog-if 30 [XHCI])
Subsystem: Lenovo Device 3987
Flags: bus master, medium devsel, latency 0, IRQ 48
Memory at c4300000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [70] Power Management version 2
Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
Subsystem: Lenovo Device 3987
Flags: bus master, fast devsel, latency 0, IRQ 59
Memory at c431a000 (64-bit, non-prefetchable) [size=32]
Capabilities: [50] Power Management version 3
Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: mei_me
Kernel modules: mei_me
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
Subsystem: Lenovo Device 3987
Flags: bus master, fast devsel, latency 64, IRQ 49
Memory at c4314000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 3
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00002000-00002fff
Memory behind bridge: a0100000-a02fffff
Prefetchable memory behind bridge: 00000000a0300000-00000000a04fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Lenovo Device 3987
Capabilities: [a0] Power Management version 3
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 00004000-00004fff
Memory behind bridge: c4200000-c42fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Lenovo Device 3987
Capabilities: [a0] Power Management version 3
Capabilities: [100] #00
Capabilities: [200] L1 PM Substates
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
Memory behind bridge: c4000000-c41fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Lenovo Device 3987
Capabilities: [a0] Power Management version 3
Capabilities: [100] #00
Capabilities: [200] L1 PM Substates
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 (rev e3) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 00003000-00003fff
Memory behind bridge: c3000000-c3ffffff
Prefetchable memory behind bridge: 00000000b0000000-00000000c1ffffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Lenovo Device 3987
Capabilities: [a0] Power Management version 3
Capabilities: [100] #00
Capabilities: [200] L1 PM Substates
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
Subsystem: Lenovo Device 3987
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0c <?>
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03) (prog-if 01 [AHCI 1.0])
Subsystem: Lenovo Device 3987
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 46
I/O ports at 5088 [size=8]
I/O ports at 5094 [size=4]
I/O ports at 5080 [size=8]
I/O ports at 5090 [size=4]
I/O ports at 5060 [size=32]
Memory at c4318000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [70] Power Management version 3
Capabilities: [a8] SATA HBA v1.0
Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
Subsystem: Lenovo Device 3987
Flags: medium devsel, IRQ 18
Memory at c4319000 (64-bit, non-prefetchable) [size=256]
I/O ports at 5040 [size=32]
Kernel modules: i2c_i801
-->02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
Subsystem: Lenovo Device 3819
Flags: bus master, fast devsel, latency 0, IRQ 60
I/O ports at 4000 [size=256]
Memory at c4204000 (64-bit, non-prefetchable) [size=4K]
Memory at c4200000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
Capabilities: [d0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
Capabilities: [170] Latency Tolerance Reporting
Capabilities: [178] L1 PM Substates
Kernel driver in use: r8169
Kernel modules: r8169
-->03:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 20)
Subsystem: Lenovo Device 3044
Flags: bus master, fast devsel, latency 0, IRQ 50
Memory at c4000000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=8/8 Maskable+ 64bit-
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Virtual Channel
Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [178] Latency Tolerance Reporting
Capabilities: [180] L1 PM Substates
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
04:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 840M] (rev a2)
Subsystem: Lenovo Device 381c
Flags: fast devsel, IRQ 16
Memory at c3000000 (32-bit, non-prefetchable) [size=16M]
Memory at b0000000 (64-bit, prefetchable) [size=256M]
Memory at c0000000 (64-bit, prefetchable) [size=32M]
I/O ports at 3000 [size=128]
Expansion ROM at <ignored> [disabled]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [250] Latency Tolerance Reporting
Capabilities: [258] L1 PM Substates
Capabilities: [128] Power Budgeting <?>
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
Capabilities: [900] #19
Kernel modules: nvidiafb, nouveau
[root@localhost dedanna]#
Code: Select all
[root@localhost dedanna]# dmesg | grep ath10k
[ 10.725675] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
-->[ 11.150508] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2
[ 12.895424] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000, 0x003405ff) fw WLAN.RM.1.1-00141 api 5 htt 3.1 wmi 4 cal otp max_sta 32
[ 12.895427] ath10k_pci 0000:03:00.0: debug 1 debugfs 0 tracing 0 dfs 0 testmode 0
-->[ 17.551211] ath10k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
[root@localhost dedanna]#
Even if repetitive, here's the inxi -n:
Code: Select all
[root@localhost dedanna]# inxi -n
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169
IF: enp2s0 state: down mac: 68:f7:28:d0:14:46
Card-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
driver: ath10k_pci
IF: wlp3s0 state: down mac: b8:86:87:47:28:81
Card-3: Atheros
IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A
[root@localhost dedanna]#
Code: Select all
[root@localhost dedanna]# ls /sys/class/net
enp2s0@ lo@ wlp3s0@
[root@localhost dedanna]#
Code: Select all
[root@localhost dedanna]# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether 68:f7:28:d0:14:46 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
link/ether b8:86:87:47:28:81 brd ff:ff:ff:ff:ff:ff
[root@localhost dedanna]#
Code: Select all
[root@localhost dedanna]# ip link set wlp3s0 up
[root@localhost dedanna]#
Code: Select all
[root@localhost dedanna]# ip link set wlp3s0 down
[root@localhost dedanna]#
I then ran "ip link set wlp3s0 up" again before I moved on. I was already in root (well, almost anyway; just su, not su -), and I don't use sudo, so kept it where I was at:
Code: Select all
[root@localhost dedanna]# ip link show dev wlp3s0
3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
link/ether b8:86:87:47:28:81 brd ff:ff:ff:ff:ff:ff
[root@localhost dedanna]#
Edit for code correction:
Code: Select all
[root@localhost dedanna]# systemctl status network systemd-networkd.service
â— network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network)
Active: inactive (dead)
â— systemd-networkd.service - Network Service
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled)
Active: active (running) since Tue 2015-10-27 10:51:36 MDT; 4min 18s ago
Docs: man:systemd-networkd.service(8)
Main PID: 1060 (systemd-network)
Status: "Processing requests..."
CGroup: /system.slice/systemd-networkd.service
└─1060 /usr/lib/systemd/systemd-networkd
[root@localhost dedanna]#
I've split up each command for easier reading. I'm beginning to see what's going on. It seems the firmware isn't loading, but if it isn't loading, then how is Network Manager seeing wireless connections? Also, how am I getting a "Wireless connections are available" popup in the lower right of the screen upon login?
I'd rather be a free person who fears terrorists, than be a "safe" person who fears the government.
No gods, no masters.
"A druid is by nature anarchistic, that is, submits to no one."
http://uk.druidcollege.org/faqs.html
No gods, no masters.
"A druid is by nature anarchistic, that is, submits to no one."
http://uk.druidcollege.org/faqs.html
Re: Qualcomm Atheros QCA61x4 issues with Linux
Well it looks like it is working. If Mageia can see the wireless networks then it should be possible to hook them up too.
From there on it is a matter of configuring correctly.
Those data are on your (the routers) end so I can only guess
From there on it is a matter of configuring correctly.
Those data are on your (the routers) end so I can only guess
Manjaro 64bit on the main box -Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz and nVidia Corporation GT200b [GeForce GTX 275] (rev a1. + Centos on the server - Arch on the laptop.
"There are no stupid questions - Only stupid answers!"
"There are no stupid questions - Only stupid answers!"
- dedanna1029
- Sound-Berserk
- Posts: 8780
- Joined: 14 Mar 2010, 20:29
- Contact:
Re: Qualcomm Atheros QCA61x4 issues with Linux
Aye which is what I'm using. I'm not getting why it's not working. The password for the wireless is even what's on the router. There's no encryption key on it.
I'd rather be a free person who fears terrorists, than be a "safe" person who fears the government.
No gods, no masters.
"A druid is by nature anarchistic, that is, submits to no one."
http://uk.druidcollege.org/faqs.html
No gods, no masters.
"A druid is by nature anarchistic, that is, submits to no one."
http://uk.druidcollege.org/faqs.html
Re: Qualcomm Atheros QCA61x4 issues with Linux
I think checkin like Thomas described in that bug is where you are at now.
Manjaro 64bit on the main box -Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz and nVidia Corporation GT200b [GeForce GTX 275] (rev a1. + Centos on the server - Arch on the laptop.
"There are no stupid questions - Only stupid answers!"
"There are no stupid questions - Only stupid answers!"
- dedanna1029
- Sound-Berserk
- Posts: 8780
- Joined: 14 Mar 2010, 20:29
- Contact:
Re: Qualcomm Atheros QCA61x4 issues with Linux
Probably.
I used for this in Mageia is what I use for Windows, so...
I've tried on everything.
I used for this in Mageia is what I use for Windows, so...
I've tried on everything.
I'd rather be a free person who fears terrorists, than be a "safe" person who fears the government.
No gods, no masters.
"A druid is by nature anarchistic, that is, submits to no one."
http://uk.druidcollege.org/faqs.html
No gods, no masters.
"A druid is by nature anarchistic, that is, submits to no one."
http://uk.druidcollege.org/faqs.html
- dedanna1029
- Sound-Berserk
- Posts: 8780
- Joined: 14 Mar 2010, 20:29
- Contact:
Re: Qualcomm Atheros QCA61x4 issues with Linux
The connection is WPA/WPA2 PSK (PreShared Key) (AES). The passphrase I'm using for that should be working and connecting me. The connection is seen, but isn't connecting properly.
I don't know where that issue is, it's somewhere between the Qualcomm Atheros and my ISP I'm assuming, either that or between the kernel, board.bin, firmware-5.bin, and Qualcomm Atheros.
That's all I can think.
EXCEPT... isn't eth0 supposed to stay up to create and maintain the bridge for the wireless connection? During the process of testing the wireless connection when I try to set it up, the RealTek goes down.
I don't know where that issue is, it's somewhere between the Qualcomm Atheros and my ISP I'm assuming, either that or between the kernel, board.bin, firmware-5.bin, and Qualcomm Atheros.
That's all I can think.
EXCEPT... isn't eth0 supposed to stay up to create and maintain the bridge for the wireless connection? During the process of testing the wireless connection when I try to set it up, the RealTek goes down.
I'd rather be a free person who fears terrorists, than be a "safe" person who fears the government.
No gods, no masters.
"A druid is by nature anarchistic, that is, submits to no one."
http://uk.druidcollege.org/faqs.html
No gods, no masters.
"A druid is by nature anarchistic, that is, submits to no one."
http://uk.druidcollege.org/faqs.html
Re: Qualcomm Atheros QCA61x4 issues with Linux
You don't have eth0 you have enp2s0.
Manjaro 64bit on the main box -Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz and nVidia Corporation GT200b [GeForce GTX 275] (rev a1. + Centos on the server - Arch on the laptop.
"There are no stupid questions - Only stupid answers!"
"There are no stupid questions - Only stupid answers!"
- dedanna1029
- Sound-Berserk
- Posts: 8780
- Joined: 14 Mar 2010, 20:29
- Contact:
Re: Qualcomm Atheros QCA61x4 issues with Linux
Yeah, I know, but that is a renaming of eth0 that it does, so for simplicity's sake and for a general naming, I put eth0. If you look above, the wireless is renamed too - it mentions it in the outputs. So in my case, we have enp2s0 and wlp3s0.
The question is, it's supposed to stay up... I found a link on it that said to bring up eth0 first, then the wlan0 (so mine with their names would be coming up). for a bridge. The thing is, my "eth0" comes up, but then when the wireless tries to connect, it goes right back down.
The question is, it's supposed to stay up... I found a link on it that said to bring up eth0 first, then the wlan0 (so mine with their names would be coming up). for a bridge. The thing is, my "eth0" comes up, but then when the wireless tries to connect, it goes right back down.
I'd rather be a free person who fears terrorists, than be a "safe" person who fears the government.
No gods, no masters.
"A druid is by nature anarchistic, that is, submits to no one."
http://uk.druidcollege.org/faqs.html
No gods, no masters.
"A druid is by nature anarchistic, that is, submits to no one."
http://uk.druidcollege.org/faqs.html