2.6.28-rc4: iwlagn / 5100 state

2.6.28-rc4: iwlagn / 5100 state

[Nico -telmich- Schottelius]

[-- Attachment #1: Type: text/plain, Size: 983 bytes --]

Hello!

Using that kernel I see the following features / bugs:

   - loading the firmware "freezes" the system for a few seconds
   - setting the link up of wlan0 "freezes" the system for a few seconds
   - connecting to 802.11b/g works (802.11a is untested)
   - roaming does *NOT* work -> just looses the AP, does not connect
     to other AP with same essid
   - connecting to a ap sometimes does not work, though essid is set
      -> sometimes it helps to specify "ap <addr>"
      -> sometimes setting down and up the link helps
      -> with earlier kernels one sometimes needed to rmmod and insmod
         the module again, so there is some progress :-)

So far it is somehow usable, though the connection problems and missing
roaming is a bit painful.

Sincerly,

Nico


-- 
Think about Free and Open Source Software (FOSS).
http://nico.schottelius.org/documentations/foss/the-term-foss/

PGP: BFE4 C736 ABE5 406F 8F42  F7CF B8BE F92A 9885 188C

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: 2.6.28-rc4: iwlagn / 5100 state

[Rafael J. Wysocki]

(Cc to linux-wireless@vger.kernel.org)

On Friday, 14 of November 2008, Nico -telmich- Schottelius wrote:
> Hello!
> 
> Using that kernel I see the following features / bugs:
> 
>    - loading the firmware "freezes" the system for a few seconds
>    - setting the link up of wlan0 "freezes" the system for a few seconds
>    - connecting to 802.11b/g works (802.11a is untested)
>    - roaming does *NOT* work -> just looses the AP, does not connect
>      to other AP with same essid
>    - connecting to a ap sometimes does not work, though essid is set
>       -> sometimes it helps to specify "ap <addr>"
>       -> sometimes setting down and up the link helps
>       -> with earlier kernels one sometimes needed to rmmod and insmod
>          the module again, so there is some progress :-)
> 
> So far it is somehow usable, though the connection problems and missing
> roaming is a bit painful.

Re: 2.6.28-rc4: iwlagn / 5100 state

[Zhu Yi]

On Fri, 2008-11-14 at 23:05 +0800, Nico -telmich- Schottelius wrote:
>    - loading the firmware "freezes" the system for a few seconds
>    - setting the link up of wlan0 "freezes" the system for a few
> seconds

We use a wait_event_interruptible_timeout in mac80211 start callback to
make sure firmware is loading OK before 'ifconfig wlan0 up' returns.
This prevents the EREADY error some wireless configuration commands
immediately followed by link up (usually in some scripts). The timeout
is 4 seconds, but usually firmware responses in less than 500ms. Did you
see the "freeze" in a failure case?

>    - connecting to 802.11b/g works (802.11a is untested)
>    - roaming does *NOT* work -> just looses the AP, does not connect
>      to other AP with same essid

This needs to be addressed in user level (i.e. NM).

>    - connecting to a ap sometimes does not work, though essid is set
>       -> sometimes it helps to specify "ap <addr>"

This is not required with recent mac80211.

>       -> sometimes setting down and up the link helps
>       -> with earlier kernels one sometimes needed to rmmod and insmod
>          the module again, so there is some progress :-)

These are unexpected behaviours. Please report bugs to
http://bughost.org.

Thanks,
-yi