Re: [ipw3945-devel] [BUG] iwlwifi 3945 works only with disable_hw_scan=1

["Tomas Winkler" <tomasw@gmail.com>]

On Sun, Jun 15, 2008 at 4:42 PM, Maxim Levitsky <maximlevitsky@gmail.co=
m> wrote:
> Tomas Winkler wrote:
>>
>> On Fri, Jun 13, 2008 at 6:06 PM, Maxim Levitsky <maximlevitsky@gmail=
=2Ecom>
>> wrote:
>>>
>>> Tor H=E5kon Haugen wrote:
>>>>
>>>> John W. Linville wrote:
>>>>>
>>>>> On Fri, Jun 13, 2008 at 03:35:23PM +0800, Zhu Yi wrote:
>>>>>>
>>>>>> On Thu, 2008-06-12 at 09:59 -0400, John W. Linville wrote:
>>>>>>>
>>>>>>> Honestly I'm tempted to change it to "enable_hw_scan" instead..=
=2E
>>>>>>
>>>>>> Give the advantages, I'd like to use it if we can fix the bug (I
>>>>>> haven't
>>>>>> seen what the bug is myself). But you are free to change the def=
ault
>>>>>> value until it is fixed. There is no such problem for 4965, righ=
t?
>>>>>
>>>>> AFAICT only the 3945 seems to need it.
>>>>>
>>>> I can confirm that this also applies to 4965 as a friend of mine h=
as
>>>> this card. According to him the card works a lot better with the
>>>> parameters "swcrypto=3D1" and "disable_hw_scan=3D1".
>>>
>>> Just to make it clear,
>>> iwl3945 doesn't work at all without disable_hw_scan=3D1 here.
>>> The driver just shuts down thee card since it detects microcode err=
or.
>>>
>>
>> It looks like this is all caused by the big rate, band patch. Looks
>> like A band scan channels are not configured correctly for the
>> scanning. This crashes the firmware.
>>
>> Tomas
>
> Probably, I see that eeprom according to dmesg contains no info about=
 A
> channels, so maybe this crashes the firmware.
>

Can you please send your dmesg.

> I have few questions:
>
> * Is there a software workaround without the need to update the firmw=
are?

Yes

> * Is the firmware error so harmful, so driver can't continue?

This is firmware misconfiguration.  Driver should be friendly to
firmware and use correctly API.

> * Can I expect updated version of the firmware with  fix?

No need so far.

> Sadly this confirms that firmware is worse that I thought, it is clos=
er to
> closed drivers.

The firmware API is open, it just wasn't used correctly.

> (Although intel isn't guilty in this case due to regulations.)

Thanks
Tomas
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html