From: "Mark A. Swift" <markaswift@gmail.com>
To: while oneq <while1eq1@gmail.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>, ath10k@lists.infradead.org
Subject: Re: openwrt ath10k / MacBook Pro Retina 802.11ac not connecting
Date: Thu, 15 May 2014 17:26:31 +0100 [thread overview]
Message-ID: <37DFD858-1F18-4A02-B7A8-0D314918189C@gmail.com> (raw)
In-Reply-To: <CAMWKU3eTJ8uPQv9NV_oTD4HVLpyr9_d7U9uc4DgirUk2fB2tNw@mail.gmail.com>
Sadly I resorted back to the TP Link firmware as the lack of 5ghz was a deal breaker for me…
Sorry I cannot be of further help.
On 15 May 2014, at 16:59, while oneq <while1eq1@gmail.com> wrote:
> I would be glad to provide any info that I can to help resolve this
> issue. Itll take me a few days for me to gather it up but when I get
> it I will surely post it here.
>
> Mark did you have anything to add to this?
>
> Thanks
>
> On Wed, May 14, 2014 at 4:39 PM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> Hi again,
>>
>> Kalle Valo <kvalo@qca.qualcomm.com> writes:
>>
>>> while oneq <while1eq1@gmail.com> writes:
>>>
>>>> Im currently using lib/firmware/ath10k/QCA988X/hw2.0/ on a TP-Link
>>>> Archer C7 v2.0 / OpenWRT [BARRIER BREAKER (Bleeding Edge, r40749)]
>>>>
>>>> Package: kmod-ath10k
>>>> Version: 3.10.36+2014-03-31-1
>>>> Depends: kernel (= 3.10.36-1-6548302841f6df0132fbc6960fa209fb), kmod-ath
>>>> Status: install user installed
>>>> Architecture: ar71xx
>>>>
>>>
>>> [...]
>>>
>>>> and am connecting via
>>>>
>>>> a MacBook Pro Retina:
>>>> Model Name: MacBook Pro
>>>> Model Identifier: MacBookPro11,3
>>>
>>>
>>> [...]
>>>
>>>> And am unable to get connected to the access point at all, All
>>>> wireless security settings are disabled at the moment.
>>>>
>>>> Any assistance on this issue would be greatly appreciated.
>>>
>>> With the information you provided it's difficult to say what's the
>>> problem. Here are some tips to get forward:
>>>
>>> * Try disabling all possible features. Setup AP to use simple 11a mode
>>> with 20 MHz channels without aggregation etc and try to narrow down
>>> what is causing the problem.
>>>
>>> * Try with static IPs.
>>>
>>> * Try different channels.
>>>
>>> * If you have a wireless sniffer, take 802.11 airlog with that and post
>>> it somewhere.
>>>
>>> * Provide logs from AP, especially dmesg and hostapd debug logs are
>>> useful.
>>>
>>> Please let me know if you need more help with the above.
>>
>> I just noticed that Mark had also reported problems with the same
>> MacBook. I had even replied to him, but I guess I forgot it entirely due
>> to jetlag :)
>>
>> But anyways, it would awesome if you could provide more info so that we
>> can find the bug causing the problem. And if you have any questions,
>> please ask. We have lots of people here who can help.
>>
>> --
>> Kalle Valo
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2014-05-15 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 2:36 openwrt ath10k / MacBook Pro Retina 802.11ac not connecting while oneq
2014-05-14 20:11 ` Kalle Valo
2014-05-14 20:39 ` Kalle Valo
2014-05-15 15:59 ` while oneq
2014-05-15 16:26 ` Mark A. Swift [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37DFD858-1F18-4A02-B7A8-0D314918189C@gmail.com \
--to=markaswift@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=while1eq1@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox