On 06/13/2016 11:17 PM, Rajkumar Manoharan wrote:
commit b057886524be ("ath10k: do not use coherent memory for allocated
device memory chunks") replaced coherent memory allocation for memory
chunks to fix low memory platforms. Unfortunately this is causing system
freeze on x86 platform while
On Fri, Jul 22, 2016 at 08:51:36AM -0400, Prarit Bhargava wrote:
> On 07/22/2016 08:21 AM, Arend Van Spriel wrote:
> >> Another option to solve to problem would be stop requesting not
> >> available publicly firmware. However, I assume some drivers would
> >> like to preserve that option.
> >
> >
On Fri, Jul 22, 2016 at 12:26:00PM +0200, Stanislaw Gruszka wrote:
> On Fri, Jul 22, 2016 at 10:38:24AM +0200, Arend Van Spriel wrote:
> > + Luis
> >
> > On 21-7-2016 13:51, Stanislaw Gruszka wrote:
> > > (cc: firmware and brcmfmac maintainers)
> > >
> > > On Thu, Jul 21, 2016 at 06:23:11AM
On Fri, Jul 22, 2016 at 10:38:24AM +0200, Arend Van Spriel wrote:
> + Luis
>
> On 21-7-2016 13:51, Stanislaw Gruszka wrote:
> > (cc: firmware and brcmfmac maintainers)
> >
> > On Thu, Jul 21, 2016 at 06:23:11AM -0400, Prarit Bhargava wrote:
> >>
> >>
> >> On 07/21/2016 04:05 AM, Stanislaw
Hi all,
So I decided to have another fiddle with this and managed to get the
WiFi working perfectly first time on an ArchLinux LiveCD so it looks
like this issue is Ubuntu specific.
I’m going to copy the firmware files and check if they’re responsible
and work my way through the various
Hi
On 2016-07-22, Arnd Bergmann wrote:
> On Friday, July 22, 2016 7:55:36 AM CEST Jes Sorensen wrote:
> > Stefan Lippers-Hollmann writes:
> > > On 2016-07-20, Arnd Bergmann wrote:
> > >> On Wednesday, July 20, 2016 11:33:43 AM CEST Jes Sorensen wrote:
> > >> > Arnd Bergmann
On Friday, July 22, 2016 7:55:36 AM CEST Jes Sorensen wrote:
> Stefan Lippers-Hollmann writes:
> > Hi
> >
> > On 2016-07-20, Arnd Bergmann wrote:
> >> On Wednesday, July 20, 2016 11:33:43 AM CEST Jes Sorensen wrote:
> >> > Arnd Bergmann writes:
> >> > > On
I haven’t managed to get connected to a WPA network either so it looks
like open only at the moment but I fear that may just have been a
fluke.
A big problem I’m facing is that editing /etc/default/crda to
REGDOMAIN=GB wasn’t enough to set the wifi regulation mode to GB and I
have to set it
On Fri, Jul 22, 2016 at 03:59:47PM +, Amitkumar Karwar wrote:
> I am trying to understand the problem you mentioned during IGTK rekeying.
> Today I ran tests with two stations connecting an AP. MFP is enabled on all
> of them.
>
> On hostapd side, my observation is add_key() is always
Disregard - I have actually managed to get this to connect to a open network!
# iw reg set GB
# iw reg get
country GB: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 80), (N/A, 20), (N/A)
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
(5490 - 5710 @ 160),
Ok so I created a guest wifi network without any encryption enabled at
all and the client still refuses to connect.
Again, the connection is made perfectly using the USB dongle I have
but not the built in libertas sd8686 chipset.
I do currently use pfSense as a firewall box behind my wireless
Hi Dan,
I will check out the WPA2 vs WPA vs open wireless thing in a few mins.
For now though - the iwlist scan results for both a USB device and the
libertas device:
USB: http://termbin.com/hdwl
Libertas: http://termbin.com/jxh7
Will follow up shortly with WPA and Open network configs.
On Fri, 2016-07-22 at 01:48 -0700, Christopher Williamson wrote:
> Looking through the log lines I see gaps between what WPA is doing
> and what
> dmesg reports and figured this is because of the libertas debugging
> level
> so I’ve set that to 0xfff (for libertas) and created a combined
> log
Hi Jouni,
> From: Jouni Malinen [mailto:j...@w1.fi]
> Sent: Thursday, July 21, 2016 9:22 PM
> To: Amitkumar Karwar
> Cc: Kalle Valo; linux-wireless@vger.kernel.org; Cathy Luo; Nishant
> Sarmukadam
> Subject: Re: [PATCH 5/9] mwifiex: cfg80211 set_default_mgmt_key handler
>
> On Thu, Jul 21, 2016
On Fri, Jul 22, 2016 at 7:02 PM, Ben Greear wrote:
>
>
> On 07/22/2016 05:21 AM, Krishna Chaitanya wrote:
>>
>> On Fri, Jul 22, 2016 at 5:29 PM, Manoharan, Rajkumar
>> wrote:
>>>
>>> [...]
>>
>> Thanks Raj, with this fix the rates are
Hi Dave,
I'm sick so I have to keep this short, but here's the last pull request
to net-next. This time there's a trivial conflict with mtd tree:
http://lkml.kernel.org/g/20160720123133.44dab...@canb.auug.org.au
We concluded with Brian (CCed) that it's best that we ask Linus to fix
this. The
Fixes the following sparse warning:
drivers/net/wireless/ti/wlcore/spi.c:87:34: warning:
symbol 'wilink_data' was not declared. Should it be static?
Signed-off-by: Wei Yongjun
---
drivers/net/wireless/ti/wlcore/spi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On 07/22/2016 05:21 AM, Krishna Chaitanya wrote:
On Fri, Jul 22, 2016 at 5:29 PM, Manoharan, Rajkumar
wrote:
[...]
Thanks Raj, with this fix the rates are 0-7, if i disable then i am
seeing 0-9, so its
working.
But i am seeing a weird issues, the moment i give
On 07/22/2016 08:21 AM, Arend Van Spriel wrote:
> On 22-7-2016 12:26, Stanislaw Gruszka wrote:
>> On Fri, Jul 22, 2016 at 10:38:24AM +0200, Arend Van Spriel wrote:
>>> + Luis
>>>
>>> On 21-7-2016 13:51, Stanislaw Gruszka wrote:
(cc: firmware and brcmfmac maintainers)
On Thu, Jul
On Fri, Jul 22, 2016 at 5:29 PM, Manoharan, Rajkumar
wrote:
> [...]
>> >> Thanks Raj, with this fix the rates are 0-7, if i disable then i am
>> >> seeing 0-9, so its
>> >> working.
>> >>
>> >> But i am seeing a weird issues, the moment i give bitrates command,
>> >>
On 22-7-2016 12:26, Stanislaw Gruszka wrote:
> On Fri, Jul 22, 2016 at 10:38:24AM +0200, Arend Van Spriel wrote:
>> + Luis
>>
>> On 21-7-2016 13:51, Stanislaw Gruszka wrote:
>>> (cc: firmware and brcmfmac maintainers)
>>>
>>> On Thu, Jul 21, 2016 at 06:23:11AM -0400, Prarit Bhargava wrote:
[...]
> >> Thanks Raj, with this fix the rates are 0-7, if i disable then i am
> >> seeing 0-9, so its
> >> working.
> >>
> >> But i am seeing a weird issues, the moment i give bitrates command,
> >> ath10k no longer does encryption, link is a WPA2-PSK: AES. Even after
> >> interface up/down
> >>
Stefan Lippers-Hollmann writes:
> Hi
>
> On 2016-07-20, Arnd Bergmann wrote:
>> On Wednesday, July 20, 2016 11:33:43 AM CEST Jes Sorensen wrote:
>> > Arnd Bergmann writes:
>> > > On Wednesday, July 20, 2016 7:25:19 AM CEST Jes Sorensen wrote:
>> > >> Arnd
Hi Bob,
On Fri, Jul 22, 2016 at 8:38 PM, Bob Copeland wrote:
> On Fri, Jul 22, 2016 at 07:53:35PM +1000, Julian Calaby wrote:
>> Hi Bob,
>
> Hi!
>
>> > --- a/interface.c
>> > +++ b/interface.c
>> > @@ -295,6 +295,10 @@ char *channel_width_name(enum nl80211_chan_width
>> >
Felix Fietkau writes:
> Please let me know if you have any ideas.
Two more things to try:
- Andrew McGregor mentioned that some versions of Iperf on OSX has a
threading bug when running multiple streams against the same server
instance. So try running two separate instances
On Fri, Jul 22, 2016 at 07:53:35PM +1000, Julian Calaby wrote:
> Hi Bob,
Hi!
> > --- a/interface.c
> > +++ b/interface.c
> > @@ -295,6 +295,10 @@ char *channel_width_name(enum nl80211_chan_width width)
> > return "80+80 MHz";
> > case NL80211_CHAN_WIDTH_160:
> >
On Fri, Jul 22, 2016 at 10:38:24AM +0200, Arend Van Spriel wrote:
> + Luis
>
> On 21-7-2016 13:51, Stanislaw Gruszka wrote:
> > (cc: firmware and brcmfmac maintainers)
> >
> > On Thu, Jul 21, 2016 at 06:23:11AM -0400, Prarit Bhargava wrote:
> >>
> >>
> >> On 07/21/2016 04:05 AM, Stanislaw
Hi Bob,
On Fri, Jul 22, 2016 at 1:39 AM, Bob Copeland wrote:
> iw was showing 'width: unknown' for channels on OCB interfaces; teach
> it the values for 5/10 MHz so it will show the configured width.
>
> Signed-off-by: Bob Copeland
> ---
>
Driver may allow support for different beacon interval on virtual interfaces.
Allow if such support is advertised by driver. This adds new ext_feature as
NL80211_EXT_FEATURE_DIFF_BEACON_INTERVAL.
Signed-off-by: Purushottam Kushwaha
---
include/uapi/linux/nl80211.h | 3
Looking through the log lines I see gaps between what WPA is doing and what
dmesg reports and figured this is because of the libertas debugging level
so I’ve set that to 0xfff (for libertas) and created a combined log of
the events from both sources labelled with either [wpa] or [dmesg] and
+ Luis
On 21-7-2016 13:51, Stanislaw Gruszka wrote:
> (cc: firmware and brcmfmac maintainers)
>
> On Thu, Jul 21, 2016 at 06:23:11AM -0400, Prarit Bhargava wrote:
>>
>>
>> On 07/21/2016 04:05 AM, Stanislaw Gruszka wrote:
>>> On Thu, Jul 21, 2016 at 10:36:42AM +0300, Emmanuel Grumbach wrote:
I was thinking about redirecting the wpa logging to syslog but figured
I’d take the lazy way out by abusing curl:
curl -s http://termbin.com/cx0e http://termbin.com/bvdj | sort
Resulting combined log file:
http://termbin.com/909y
Christopher Williamson
On 22 July 2016 at 09:09:59, Arend Van
On 22-7-2016 0:00, Christopher Williamson wrote:
> I’ve created cleaner logs (particularly the dmesg one) and have added
> timestamps line-by-line to both so it should be easier to track
> between the two log files:
>
> wpa_supplicant:
> http://termbin.com/cx0e
>
> dmesg | grep libertas:
>
33 matches
Mail list logo