Emmanuel Grumbach
egrumb...@gmail.com
On Sun, Jan 18, 2015 at 9:13 PM, Emmanuel Grumbach wrote:
> On Sun, Jan 18, 2015 at 8:52 PM, Emmanuel Grumbach
> wrote:
>> On Sun, Jan 18, 2015 at 8:40 PM, Linus Torvalds
>> wrote:
>>> On Mon, Jan 19, 2015 at 5:48 AM, Arend van Spriel
>>> wrote:
>>
On Sun, Jan 18, 2015 at 8:52 PM, Emmanuel Grumbach wrote:
> On Sun, Jan 18, 2015 at 8:40 PM, Linus Torvalds
> wrote:
>> On Mon, Jan 19, 2015 at 5:48 AM, Arend van Spriel wrote:
>>>
>>> So as you indicated you were in location where none of your configured
>>> networks were available. Flipping th
On Sun, Jan 18, 2015 at 8:40 PM, Linus Torvalds
wrote:
> On Mon, Jan 19, 2015 at 5:48 AM, Arend van Spriel wrote:
>>
>> So as you indicated you were in location where none of your configured
>> networks were available. Flipping the rfkill switch in that situation is the
>> way to trigger the issu
On Mon, Jan 19, 2015 at 5:48 AM, Arend van Spriel wrote:
>
> So as you indicated you were in location where none of your configured
> networks were available. Flipping the rfkill switch in that situation is the
> way to trigger the issue.
So you certainly seem to be able to explain the behavior I
On 01/18/15 18:48, Arend van Spriel wrote:
On 01/18/15 17:53, Linus Torvalds wrote:
On Sun, Jan 18, 2015 at 11:24 PM, Emmanuel
Grumbach wrote:
we have different scan flows based on the firmware version you have,
so it would help if you could tell me what firmware you have.
Sure. It's the lar
On 01/18/15 17:53, Linus Torvalds wrote:
On Sun, Jan 18, 2015 at 11:24 PM, Emmanuel Grumbach wrote:
we have different scan flows based on the firmware version you have,
so it would help if you could tell me what firmware you have.
Sure. It's the larest one I could find
iwlwifi :01:0
On Sun, Jan 18, 2015 at 11:24 PM, Emmanuel Grumbach wrote:
>
> we have different scan flows based on the firmware version you have,
> so it would help if you could tell me what firmware you have.
Sure. It's the larest one I could find
iwlwifi :01:00.0: loaded firmware version 23.11.10.0 o
Hi Linus,
On Sun, Jan 18, 2015 at 5:25 AM, Linus Torvalds
wrote:
> So there seems to be some issue with unlucky timing when turning off
> wireless while the driver is busy scanning. I can't reproduce this, so
> it's a one-off, but it's not just ugly warnings, the kernel woudln't
> scan any wirele
On 01/18/15 04:25, Linus Torvalds wrote:
So there seems to be some issue with unlucky timing when turning off
wireless while the driver is busy scanning. I can't reproduce this, so
it's a one-off, but it's not just ugly warnings, the kernel woudln't
scan any wireless on that device afterwards and
So there seems to be some issue with unlucky timing when turning off
wireless while the driver is busy scanning. I can't reproduce this, so
it's a one-off, but it's not just ugly warnings, the kernel woudln't
scan any wireless on that device afterwards and I had to reboot to get
networking back, so
10 matches
Mail list logo
