Hi,
It seems that iwi driver cannot survive more than just a few cycles of
switching down/up.
In a place with a bad wireless connection I needed to do that quite a number of
times
(that was the simplest way to restore connectivity I knew), and after 5-10
cycles I needed
to reboot my notebook to
22:17:48 jhb
Exp $");
It's STABLE, updated couple of days ago.
> cheers
> luigi
>
> On Thu, Feb 15, 2007 at 11:34:48PM +0200, V.Chukharev wrote:
>> Hi,
>>
>> It seems that iwi driver cannot survive more than just a few cycles of
>> switching do
On Fri, 16 Feb 2007 13:15:18 +0200, Luigi Rizzo <[EMAIL PROTECTED]> wrote:
> ok i tried your script to do ifconfig up and down
> and it does not give me the problem you see (at least not until 100).
> Do you see the error always at the same point ? Any other things
> e.g. how is the iwi_bss loaded
On Fri, 16 Feb 2007 19:43:17 +0200, Jeremie Le Hen <[EMAIL PROTECTED]> wrote:
> Hi,
>
> cognet@ has once provided me a tiny hack to the iwi(4) driver and
> I never get such errors. Maybe I'm not suffering enough UP/DOWN
> cycles to trigger it, but it might be worth trying it.
>
> Note that he has
On Fri, 16 Feb 2007 23:10:24 +0200, V.Chukharev <[EMAIL PROTECTED]> wrote:
> On Fri, 16 Feb 2007 19:43:17 +0200, Jeremie Le Hen <[EMAIL PROTECTED]> wrote:
>
>> Hi,
>>
>> cognet@ has once provided me a tiny hack to the iwi(4) driver and
>> I never get su
On Sun, 18 Feb 2007 17:20:18 +0200, Max Laier <[EMAIL PROTECTED]> wrote:
> The linux driver uses one continuous buffer as well. I tried to hand in
> separate buffers, but it failed to initialize the firmware. Attached is
> a diff (for HEAD and RELENG_6) to allocate the DMA buffer once and keep
>
