answers are based on what I remember, they should be fairly accurate.

> of messages.  The last messages were as follows:
>  zd1211: Mixed Mode
>  zd1211: AllowedChannel = 000007ff
>         zd1211: LinkLEDn = 200
>         AllowedChannel = 000107ff
>         Region: 48
>  zd1205: (exit) zd1205_config, /usr/src/zd1211-driver-r71/src/zd1205.c
>   line 2597
>  zd1205: (exit) zd1205_config, /usr/src/zd1211-driver-r71/src/zd1205.c
>   line 8555
> Is mixed mode okay?  
AFAICT it means the stick can connect to either 802.11B or 802.11G networks.
It should be possible to change it with one of the iwpriv commands.

> Are the last two messages in any way problematic? 
No, they show the 'zd1205_config' function has ended.

> Now I entered iwlist wlan0 scan.  The output was:
>  wlan0    Interface doesn't support scanning.
> Why this?  Is this because the interface wasn't brought up yet with
> ifconfig wlan0 up?
Yes, bringing up the interface also "activates" the hardware. In the down 
state some configuration may be possible, but the hardware isn't fully 

> Now I entered exactly this: ifconfig wlan0 up.  The kernel output this:
> ...
>  ADDRCONF(NETDEV_UP): wlan0: link is not ready
> ...
> >  zd1211: STA_ASSOCIATED with 00:01:f4:5b:a6:3b 
>  ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> Why is the link not ready first?  
My guess is because there is no association / connection to an AP, so there's 
not any kind of link either.

> Why are there so many “Mixed Mode” 
> entries? 
Don't know, maybe there's one entry for each channel scanned, see below.

> ...
>   Error for wireless request "Set Frequency" (8B04) : 
>   SET failed on device wlan0 ; Invalid argument. 
> ...
> Is it normal that the ESSID, frequency and access point settings are made
> automatically?  On http://zd1211.ath.cx/ I'm told that I shall set the
> ESSID manually.
> Later I had the situation that iwlist wlan0 scan worked, i.e., showed me
> the correct data about my WLAN.  Surprisingly, I was not able to establish
> a link but the problem of ever-changing frequencies occured.  Is this a bug
> in the driver?  Or a problem with the hardware?
In managed mode the stick seems to do some automatic scanning.
It seems to iterate over the available channels till it finds a network that 
matches the iwconfig settings (mainly the ESSID is my guess) and tries to 
connect to that.
Maybe it's not possible to set the channel/frequency in managed mode because 
the driver/hardware tries to find an appropriate channel by itself.

This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
Zd1211-devs mailing list - http://zd1211.ath.cx/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

Reply via email to