-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
open8021s support for ATH10k QCA6174 chipsets? #80
Comments
Try changing the MAC address so it doesn't duplicate another interface?
…On Sat, Dec 8, 2018, 9:25 PM ngiftsun ***@***.*** wrote:
I would like to know if open80211s is supported for ath10k based QCA6174
devices. I could see a firmware patch for QCA98XX
<https://github.com/o11s/open80211s/wiki/ath10k-(802.11ac)-for-Mesh-Support>
devices but I'm not sure about QCA6174 . I don't know what's the problem
with my driver. I use Compex WLT674
<https://wikidevi.com/wiki/Compex_WLT674> card on Ubuntu 16.04 with a
kernel version 4.4.x. I have verified that the card supports both mesh
point & IBSS mode using *iw* but I get an error SIOCSIFFLAGS: Invalid
argument when I try to bring up the mesh interface.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#80>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAaW2OKd5u8WxcP2jUPC9q8mozfakBgsks5u3J7EgaJpZM4ZJ9l7>
.
|
@twpedersen Thanks for your response. No, it doesn't work. |
Please share your bring up steps, and give the latest backports a try. The
ath10k firmware should also be up to date.
…On Sat, Dec 8, 2018, 10:18 PM ngiftsun ***@***.*** wrote:
@twpedersen <https://github.com/twpedersen> Thanks for your response. No,
it doesn't work.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#80 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAaW2AG2PwrQApwWffTcrCwN2wMOTd5vks5u3KtSgaJpZM4ZJ9l7>
.
|
@twpedersen sorry for my late response. I gave up on using this chipset. I used Ralink RT5572 based dongle to create a mesh and it works fine at the moment. |
Make sure that you try to unmanage your wireless device in Network Manager
in Ubuntu.
…On Tue, Mar 19, 2019 at 3:33 AM ngiftsun ***@***.***> wrote:
@twpedersen <https://github.com/twpedersen> sorry for my late response. I
gave up on using this chipset. I used Ralink RT5572 based dongle to create
a mesh.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#80 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABBewvmFGflYUfOuFEtG_rygwYbSSgqpks5vX-oZgaJpZM4ZJ9l7>
.
|
Script used to automate the mesh |
You need to check whether the loaded ath10k firmware support raw mode or
not.
…On Tue, Mar 19, 2019, 6:32 PM ngiftsun ***@***.***> wrote:
*Script used to automate the mesh*
sudo systemctl stop network-manager >/dev/null 2>/dev/null || :
sudo ifconfig $MESH_IF down
sudo iw $MESH_IF set type mp
sudo ifconfig $MESH_IF up
sudo ifconfig $MESH_IF $MESH_IP
sudo iw dev $MESH_IF mesh join $MESH_NAME freq $FREQ HT40+
sudo iw dev $MESH_IF set mesh_param mesh_rssi_threshold -65
sudo ip route add default via $MESH_GW
I could still get the same error SIOCSIFFLAGS: Invalid argument for
QCA6174 card. I'm using Ubuntu 4.16 kernel.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#80 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABBewoO3A_0X8myxvSi_-G2-LGJvkpH-ks5vYLzKgaJpZM4ZJ9l7>
.
|
Here you go. According to what I understand the firmware doesn't support raw_mode if you see my very first message. The module cannot be loaded with raw_mode enabled. I could clearly see errors in dmesg complaining about the raw_mode. This is really strange to me. I think raw_mode is only supported in QCA988x but not in QCA6174 as I went through several posts. https://github.com/kvalo/ath10k-firmware/tree/master/QCA988X/hw2.0/10.2.4.70. |
I guess the problem is you need a 10.4 firmware and QCA6174 doesn't seem to support that? |
You may try your luck on the following firmware:
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1.c3
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1.c2
raw mode seems to be there.
…On Wed, Mar 20, 2019 at 3:01 AM Thomas Pedersen ***@***.***> wrote:
I guess the problem is you need a 10.4 firmware and QCA6174 doesn't seem
to support that?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#80 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABBewqrO5DTgniZYyQoEbdvmRElmyNVyks5vYTPugaJpZM4ZJ9l7>
.
|
Thanks @chunyeow ! I'm having technical difficulty to choose the firmware that you suggest. I don't understand board.bin and all the firmware apis 1-6. My drivers automatically choose WLAN.RM.4.4.1-00079-QCARMSWPZ-1 and I don't know a way to control it. |
@chunyeow I was able to load the right firmware with rawmode flag enabled while loading the ath10k_core module. The good news is that I'm able to bring up the mesh interface. But sudo iw dev $MESH_IF mesh join $MESH_NAME freezes my computer |
Check the dmesg and see what the problem. If it is firmware related, then
probably need to wait for new release.
…On Thu, Mar 28, 2019 at 10:24 PM ngiftsun ***@***.***> wrote:
@chunyeow <https://github.com/chunyeow> I was able to load the right
firmware with rawmode flag while loading the ath10k_core module.
The good news is that I'm able to bring up the mesh interface. But *sudo
iw dev $MESH_IF mesh join $MESH_NAME* freezes my computer
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#80 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABBewhCyny2S8Ry5goOABpWwe3mT-8lSks5vbKmkgaJpZM4ZJ9l7>
.
|
@twpedersen <https://github.com/twpedersen> where can we post questions
related to ath10k firmware issue?
On Fri, Mar 29, 2019 at 12:04 AM Chun-Yeow Yeoh <yeohchunyeow@gmail.com>
wrote:
… Check the dmesg and see what the problem. If it is firmware related, then
probably need to wait for new release.
On Thu, Mar 28, 2019 at 10:24 PM ngiftsun ***@***.***>
wrote:
> @chunyeow <https://github.com/chunyeow> I was able to load the right
> firmware with rawmode flag while loading the ath10k_core module.
> The good news is that I'm able to bring up the mesh interface. But *sudo
> iw dev $MESH_IF mesh join $MESH_NAME* freezes my computer
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#80 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABBewhCyny2S8Ry5goOABpWwe3mT-8lSks5vbKmkgaJpZM4ZJ9l7>
> .
>
|
I think ath10k@lists.infradead.org is the best place to ask firmware questions. |
I would like to know if open80211s is supported for ath10k based QCA6174 devices. I could see a firmware patch for QCA98XX devices but I'm not sure about QCA6174 . I don't know what's the problem with my driver. I use Compex WLT674 card on Ubuntu 16.04 with a kernel version 4.4.x. I have verified that the card supports both mesh point & IBSS mode using iw but I get an error
SIOCSIFFLAGS: Invalid argument
when I try to bring up the mesh interface. I tried to load ath10k_core module with rawmode=1 but the kernel fails to load the module complaining about the fact the firmware doesn't support it. I even tried the latest firmware but did not really succeed.Thanks in advance.
The text was updated successfully, but these errors were encountered: