zd1211-devs — Developer's Mailing List

Re: [zd1211-devs] Zd1211rw with Sagem

[Hin-Tak L. <ht...@us...>]

The message seems quite clear - missing firmware. Some *cough* zealous *cough* distros ship kernels stripped of binary blobs crucial to the functionality of a device, because it does not fit their ideology of software freedom. Download and install a proper kernel, with all the necessary bits. 


------------------------------
On Sat, Apr 26, 2014 11:39 AM BST jean delamotte wrote:

>Hi
>I've got a Sagem XG 760A key, with USB ID 079b:004a. I work with debian distrib which include dz1211rw firmware.
> 
>dmesg gives :
>[   73.004126] usb 1-1: new full-speed USB device number 2 using uhci_hcd
>[   73.169193] usb 1-1: New USB device found, idVendor=079b, idProduct=004a
>[   73.169215] usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=0
>[   73.169233] usb 1-1: Product: 802.11b/g USB WLAN
>[   73.169248] usb 1-1: Manufacturer: ZyDAS
>[   73.364855] cfg80211: Calling CRDA to update world regulatory domain
>[   73.628133] usb 1-1: reset full-speed USB device number 2 using uhci_hcd
>[   73.826845] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
>[   73.829293] zd1211rw 1-1:1.0: phy0
>[   73.830665] usbcore: registered new interface driver zd1211rw
>[  102.543686] 1-1: Missing Free firmware
>[  102.556812] usb 1-1: Could not load firmware file /*(DEBLOBBED)*/ub. Error number -22
>[  102.557112] zd1211rw 1-1:1.0: couldn't load firmware. Error number -22
>[  126.136188] usb 1-1: USB disconnect, device number 2
>[  166.712126] usb 1-1: new full-speed USB device number 3 using uhci_hcd
>[  166.877141] usb 1-1: New USB device found, idVendor=079b, idProduct=004a
>[  166.877163] usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=0
>[  166.877181] usb 1-1: Product: 802.11b/g USB WLAN
>[  166.877197] usb 1-1: Manufacturer: ZyDAS
>[  166.996132] usb 1-1: reset full-speed USB device number 3 using uhci_hcd
>[  167.147677] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
>[  167.149414] zd1211rw 1-1:1.0: phy1
>[  186.822536] 1-1: Missing Free firmware
>[  186.835359] usb 1-1: Could not load firmware file /*(DEBLOBBED)*/ub. Error number -22
>[  186.835658] zd1211rw 1-1:1.0: couldn't load firmware. Error number -22
>[  231.312413] 1-1: Missing Free firmware
>[  231.325273] usb 1-1: Could not load firmware file /*(DEBLOBBED)*/ub. Error number -22
>[  231.325566] zd1211rw 1-1:1.0: couldn't load firmware. Error number -22
>I don't understand.
> 
>i do that (because file was empty):
># lsusb # modprobe zd1211rw # echo "079b 004a FFFFFFFF FFFFFFFF 0 0 0" > /sys/bus/usb/drivers/zd1211rw/new_id
>i don't see drivers/net/wireless/zd1211rw/zd_usb.c file.
>Any idea? Best regards

Re: [zd1211-devs] Zd1211rw with Sagem

[Jussi K. <jus...@mb...>]

On 26.04.2014 13:39, jean delamotte wrote:
> Hi
> I've got a Sagem XG 760A key, with USB ID 079b:004a. I work with debian distrib which include dz1211rw firmware.
>  
> dmesg gives :
> [ 73.004126] usb 1-1: new full-speed USB device number 2 using uhci_hcd
> [ 73.169193] usb 1-1: New USB device found, idVendor=079b, idProduct=004a
> [ 73.169215] usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=0
> [ 73.169233] usb 1-1: Product: 802.11b/g USB WLAN
> [ 73.169248] usb 1-1: Manufacturer: ZyDAS
> [ 73.364855] cfg80211: Calling CRDA to update world regulatory domain
> [ 73.628133] usb 1-1: reset full-speed USB device number 2 using uhci_hcd
> [ 73.826845] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
> [ 73.829293] zd1211rw 1-1:1.0: phy0
> [ 73.830665] usbcore: registered new interface driver zd1211rw
> [ 102.543686] 1-1: Missing Free firmware
> [ 102.556812] usb 1-1: Could not load firmware file /*(DEBLOBBED)*/ub. Error number -22
> [ 102.557112] zd1211rw 1-1:1.0: couldn't load firmware. Error number -22
> [ 126.136188] usb 1-1: USB disconnect, device number 2
> [ 166.712126] usb 1-1: new full-speed USB device number 3 using uhci_hcd
> [ 166.877141] usb 1-1: New USB device found, idVendor=079b, idProduct=004a
> [ 166.877163] usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=0
> [ 166.877181] usb 1-1: Product: 802.11b/g USB WLAN
> [ 166.877197] usb 1-1: Manufacturer: ZyDAS
> [ 166.996132] usb 1-1: reset full-speed USB device number 3 using uhci_hcd
> [ 167.147677] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
> [ 167.149414] zd1211rw 1-1:1.0: phy1
> [ 186.822536] 1-1: Missing Free firmware
> [ 186.835359] usb 1-1: Could not load firmware file /*(DEBLOBBED)*/ub. Error number -22
> [ 186.835658] zd1211rw 1-1:1.0: couldn't load firmware. Error number -22
> [ 231.312413] 1-1: Missing Free firmware
> [ 231.325273] usb 1-1: Could not load firmware file /*(DEBLOBBED)*/ub. Error number -22
> [ 231.325566] zd1211rw 1-1:1.0: couldn't load firmware. Error number -22
> I don't understand.
>  
> i do that (because file was empty):
> 
> # lsusb
> # modprobe zd1211rw
> # echo "079b 004a FFFFFFFF FFFFFFFF 0 0 0" > /sys/bus/usb/drivers/zd1211rw/new_id
> 
> i don't see drivers/net/wireless/zd1211rw/zd_usb.c file.
> 
> Any idea? Best regards

The "/*(DEBLOBBED)*/" parts in dmesg mean that your kernel has been intentionally broken and
zd1211rw will not work with it. Try again with mainline kernel instead of linux-libre based.

-Jussi

[zd1211-devs] Zd1211rw with Sagem

[jean d. <je...@ya...>]

Hi
I've got a Sagem XG 760A key, with USB ID 079b:004a. I work with debian distrib which include dz1211rw firmware.
 
dmesg gives :
[   73.004126] usb 1-1: new full-speed USB device number 2 using uhci_hcd
[   73.169193] usb 1-1: New USB device found, idVendor=079b, idProduct=004a
[   73.169215] usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=0
[   73.169233] usb 1-1: Product: 802.11b/g USB WLAN
[   73.169248] usb 1-1: Manufacturer: ZyDAS
[   73.364855] cfg80211: Calling CRDA to update world regulatory domain
[   73.628133] usb 1-1: reset full-speed USB device number 2 using uhci_hcd
[   73.826845] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   73.829293] zd1211rw 1-1:1.0: phy0
[   73.830665] usbcore: registered new interface driver zd1211rw
[  102.543686] 1-1: Missing Free firmware
[  102.556812] usb 1-1: Could not load firmware file /*(DEBLOBBED)*/ub. Error number -22
[  102.557112] zd1211rw 1-1:1.0: couldn't load firmware. Error number -22
[  126.136188] usb 1-1: USB disconnect, device number 2
[  166.712126] usb 1-1: new full-speed USB device number 3 using uhci_hcd
[  166.877141] usb 1-1: New USB device found, idVendor=079b, idProduct=004a
[  166.877163] usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=0
[  166.877181] usb 1-1: Product: 802.11b/g USB WLAN
[  166.877197] usb 1-1: Manufacturer: ZyDAS
[  166.996132] usb 1-1: reset full-speed USB device number 3 using uhci_hcd
[  167.147677] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[  167.149414] zd1211rw 1-1:1.0: phy1
[  186.822536] 1-1: Missing Free firmware
[  186.835359] usb 1-1: Could not load firmware file /*(DEBLOBBED)*/ub. Error number -22
[  186.835658] zd1211rw 1-1:1.0: couldn't load firmware. Error number -22
[  231.312413] 1-1: Missing Free firmware
[  231.325273] usb 1-1: Could not load firmware file /*(DEBLOBBED)*/ub. Error number -22
[  231.325566] zd1211rw 1-1:1.0: couldn't load firmware. Error number -22
I don't understand.
 
i do that (because file was empty):
# lsusb # modprobe zd1211rw # echo "079b 004a FFFFFFFF FFFFFFFF 0 0 0" > /sys/bus/usb/drivers/zd1211rw/new_id
i don't see drivers/net/wireless/zd1211rw/zd_usb.c file.
Any idea? Best regards

Re: [zd1211-devs] zd1211rw firmware loading timeout

[Jussi K. <jus...@mb...>]

Quoting Florian Fainelli <fl...@op...>:

> Hello Jussi,
>
> On 02/08/12 14:15, Jussi Kivilinna wrote:
>> Quoting Florian Fainelli <fl...@op...>:
>>
>>>
>>> Hello,
>>>
>>> I am running Debian testing kernel 3.1.0-1-amd64, using a 079b:0062 Sagem
>>> XG-76NA 802.11bg stick.
>>>
>>> Upon zd1211rw interface
>>> bringup (ifconfig wlan0 up) I get the following timeout:
>>>
>>> [  950.330573] zd1211rw 1-3:1.0: phy2
>>> [  955.108510] zd1211rw 1-3:1.0: firmware version 4725
>>> [  955.148532] zd1211rw 1-3:1.0: zd1211b chip 079b:0062 v4810 high 00-19-70
>>> AL2230_RF pa0 g--NS
>>> [snip]
>>> [  955.204072] zd1211rw 1-3:1.0: error ioread32(CR_REG1): -110
>>>
>>> A second ifconfig wlan0 up brings the interface up without problems.
>>>
>>> After a bit more debugging, the call trace is the following:
>>>
>>> [10241.028130] zd1211rw 1-3:1.0: zd_chip_lock_phy_regs: error
>>> ioread32(CR_REG1): -110
>>> [10241.028140] zd1211rw 1-3:1.0: zd_switch_radio_on: failed to  
>>> lock PHY regs
>>> [10241.028148] zd1211rw 1-3:1.0: zd_op_start: failed to set radio on
>>>
>>> The following small modification works around the issue:
>>>
>>> diff --git a/zd_mac.c b/zd_mac.c
>>> index cabfae1..6bfb673 100644
>>> --- a/zd_mac.c
>>> +++ b/zd_mac.c
>>> @@ -306,9 +306,14 @@ int zd_op_start(struct ieee80211_hw *hw)
>>>       r = set_mc_hash(mac);
>>>       if (r)
>>>               goto disable_int;
>>> +
>>> +       msleep(10);
>>> +
>>>       r = zd_chip_switch_radio_on(chip);
>>> -       if (r < 0)
>>> +       if (r < 0) {
>>> +               dev_err(zd_chip_dev(chip), "%s: failed to set radio on\n",
>>> __func__);
>>>               goto disable_int;
>>> +       }
>>>       r = zd_chip_enable_rxtx(chip);
>>>       if (r < 0)
>>>               goto disable_radio;
>>>
>>> Is it possible that some chips require more time between a  
>>> set_mc_hash and a
>>> radio on? Or in general that consequent writes to the PHY regs  
>>> should be timed
>>> appropriately?
>>
>> Yes, it is possible. Vendor driver appears to have quite alot  
>> sleeps spread around in RF-chip handling code. I might have seen  
>> this myself sometimes when zd1211 device has firmware freeze and  
>> has to be reseted. But since freeze is hard to reproduce and reset  
>> didn't fail always, I didn't bother with it.
>>
>> Can you give your "Signed-off-by" line for the patch?
>
> Sure, I will resubmit this patch, do you also want me to keep the  
> line showing the error?
>

Yes, do that or add URL to original mail. Thanks.

>>
>> -Jussi
>>
>>>
>>> When I googled for this timeout issue, I could see quite some  
>>> reports of other
>>> people having this error while the chip was already operating.
>>>
>>> Thanks
>>> -- 
>>> Florian
>>> -- 
>>> To unsubscribe from this list: send the line "unsubscribe  
>>> linux-wireless" in
>>> the body of a message to maj...@vg...
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>>
>>
>>
>> -- 
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to maj...@vg...
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
>

Re: [zd1211-devs] zd1211rw firmware loading timeout

[Jussi K. <jus...@mb...>]

Quoting Florian Fainelli <fl...@op...>:

>
> Hello,
>
> I am running Debian testing kernel 3.1.0-1-amd64, using a 079b:0062 Sagem
> XG-76NA 802.11bg stick.
>
> Upon zd1211rw interface
> bringup (ifconfig wlan0 up) I get the following timeout:
>
> [  950.330573] zd1211rw 1-3:1.0: phy2
> [  955.108510] zd1211rw 1-3:1.0: firmware version 4725
> [  955.148532] zd1211rw 1-3:1.0: zd1211b chip 079b:0062 v4810 high 00-19-70
> AL2230_RF pa0 g--NS
> [snip]
> [  955.204072] zd1211rw 1-3:1.0: error ioread32(CR_REG1): -110
>
> A second ifconfig wlan0 up brings the interface up without problems.
>
> After a bit more debugging, the call trace is the following:
>
> [10241.028130] zd1211rw 1-3:1.0: zd_chip_lock_phy_regs: error
> ioread32(CR_REG1): -110
> [10241.028140] zd1211rw 1-3:1.0: zd_switch_radio_on: failed to lock PHY regs
> [10241.028148] zd1211rw 1-3:1.0: zd_op_start: failed to set radio on
>
> The following small modification works around the issue:
>
> diff --git a/zd_mac.c b/zd_mac.c
> index cabfae1..6bfb673 100644
> --- a/zd_mac.c
> +++ b/zd_mac.c
> @@ -306,9 +306,14 @@ int zd_op_start(struct ieee80211_hw *hw)
>        r = set_mc_hash(mac);
>        if (r)
>                goto disable_int;
> +
> +       msleep(10);
> +
>        r = zd_chip_switch_radio_on(chip);
> -       if (r < 0)
> +       if (r < 0) {
> +               dev_err(zd_chip_dev(chip), "%s: failed to set radio on\n",
> __func__);
>                goto disable_int;
> +       }
>        r = zd_chip_enable_rxtx(chip);
>        if (r < 0)
>                goto disable_radio;
>
> Is it possible that some chips require more time between a set_mc_hash and a
> radio on? Or in general that consequent writes to the PHY regs  
> should be timed
> appropriately?

Yes, it is possible. Vendor driver appears to have quite alot sleeps  
spread around in RF-chip handling code. I might have seen this myself  
sometimes when zd1211 device has firmware freeze and has to be  
reseted. But since freeze is hard to reproduce and reset didn't fail  
always, I didn't bother with it.

Can you give your "Signed-off-by" line for the patch?

-Jussi

>
> When I googled for this timeout issue, I could see quite some  
> reports of other
> people having this error while the chip was already operating.
>
> Thanks
> --
> Florian
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to maj...@vg...
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>

Re: [zd1211-devs] duration_id field in zd1211rw

[Jussi K. <jus...@mb...>]

Hello again!

I tested the patch with pspoll check and concluded it works as it  
should. I'm planing to post your patch (+ pspoll fix) to upstream, so  
may I add your 'Signed-off-by' to it?

-Jussi

ps. patch attached.

Quoting Jussi Kivilinna <jus...@mb...>:

> Quoting Tomas Vanek <Tom...@fb...>:
>
>> Hello developers,
>>
>> first thank you for the rewrite of zd1211 driver.
>>
>> I use a small x86 server currently with linux 3.2.1 and generic ZyDAS
>> wifi ZD1211B 802.11g (USB ID 0ace:1215), fw 1.4
>> hostapd v0.7.3 is used for AP mode with WPA2 security. 6 wifi clients
>> (ath and prism54 chips) connect without problems.
>>
>> Unfortunately two notebooks with iwl5100 card cannot connect at all.
>> Tested with both linux and Win7 on the notebook.
>> I also tested without security and iwl5100 didn't work again.
>>
>> Hostapd log shows that association worked but EAPOL frame is not replied
>> by iwl:
>> ----------------------------------------------------------------------
>> STA 00:22:fb:xx:xx:xx sent probe request for our SSID
>> mgmt::auth
>> authentication: STA=00:22:fb:xx:xx:xx auth_alg=0 auth_transaction=1
>> status_code=0 wep=0
>>    New STA
>> authentication reply: STA=00:22:fb:xx:xx:xx auth_alg=0
>> auth_transaction=2 resp=0 (IE len=0)
>> mgmt::proberesp cb
>> mgmt::auth cb
>> mgmt::assoc_req
>> association request: STA=00:22:fb:xx:xx:xx capab_info=0x411
>> listen_interval=10
>>    new AID 1
>> nl80211: Set beacon (beacon_set=1)
>> mgmt::assoc_resp cb
>> wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=0xa057900 key_idx=0
>> set_tx=1 seq_len=0 key_len=0
>>     addr=00:22:fb:xx:xx:xx
>> wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=0xa057900 key_idx=0
>> set_tx=1 seq_len=0 key_len=0
>>     addr=00:22:fb:xx:xx:xx
>> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state INITIALIZE
>> wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=0xa057900 key_idx=0
>> set_tx=1 seq_len=0 key_len=0
>>     addr=00:22:fb:xx:xx:xx
>> WPA: 00:22:fb:xx:xx:xx WPA_PTK_GROUP entering state IDLE
>> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state AUTHENTICATION
>> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state AUTHENTICATION2
>> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state INITPSK
>> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state PTKSTART
>> WPA: Send EAPOL(version=2 secure=0 mic=0 ack=1 install=0 pairwise=8
>> kde_len=0 keyidx=0 encr=0)
>> nl80211: Event message available
>> nl80211: Ignored unknown event (cmd=19)
>> IEEE 802.1X: 00:22:fb:xx:xx:xx TX status - version=2 type=3 length=95 -
>> ack=0
>> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state PTKSTART
>> WPA: Send EAPOL(version=2 secure=0 mic=0 ack=1 install=0 pairwise=8
>> kde_len=0 keyidx=0 encr=0)
>> IEEE 802.1X: 00:22:fb:xx:xx:xx TX status - version=2 type=3 length=95 -
>> ack=0
>> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state PTKSTART
>> WPA: Send EAPOL(version=2 secure=0 mic=0 ack=1 install=0 pairwise=8
>> kde_len=0 keyidx=0 encr=0)
>> IEEE 802.1X: 00:22:fb:xx:xx:xx TX status - version=2 type=3 length=95 -
>> ack=0
>> mgmt::deauth
>> deauthentication: STA=00:22:fb:xx:xx:xx reason_code=1
>> AP-STA-DISCONNECTED 00:22:fb:xx:xx:xx
>> wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=0xa057900 key_idx=0
>> set_tx=1 seq_len=0 key_len=0
>>     addr=00:22:fb:xx:xx:xx
>> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state DISCONNECTED
>> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state INITIALIZE
>> ----------------------------------------------------------------------
>>
>> Sniffing wireless packets I found strange values in ieee80211 header of
>> EAPOL and other data packets:
>> duration_id was bigger than 60000, such values should be reserved for PS
>> poll.
>> Sniffer at iwl5100 didn't showed these packets at all. Management
>> packets with duration_id=0 were
>> received ok.
>>
>> After some trials I reset the duration computed by mac80211 to zero:
>> ----------------------------------------------------------------------
>> diff --git a/drivers/net/wireless/zd1211rw/zd_mac.c
>> b/drivers/net/wireless/zd1211rw/zd_mac.c
>> index 0a70149..ffbe208 100644
>> --- a/drivers/net/wireless/zd1211rw/zd_mac.c
>> +++ b/drivers/net/wireless/zd1211rw/zd_mac.c
>> @@ -866,6 +866,9 @@ static int fill_ctrlset(struct zd_mac *mac,
>>
>>          ZD_ASSERT(frag_len <= 0xffff);
>>
>> +       /* firmware computes the duration itself and needs the field set
>> to 0 at input */
>> +       hdr->duration_id= 0;
>> +
>>          txrate = ieee80211_get_tx_rate(mac->hw, info);
>>
>>          cs->modulation = txrate->hw_value;
>> ----------------------------------------------------------------------
>> and surprisingly the ZD1211B firmware computes reasonable values of
>> duration.
>> iwl5100 connects ok with fixed driver.
>>
>> This change probably breaks PS poll packets. They send assoc id in
>> duration_id field.
>
> Looking at vendor's zd1211 driver, it appears that duration_id is kept
> at zero for all packets except PSPoll. So following should work:
>
> +       /* firmware computes the duration itself and needs the field set to 0
> +        * at input for all packet types than PSPoll.
> +        */
> +       if (!ieee80211_is_pspoll(hdr->fc))
> +               hdr->duration_id = 0;
>
>>
>> I don't know if non B version of ZD1211 has the same problem.
>>
>
> Both are handled same for duration_id by vendor driver.
>
>>
>> Best regards
>>      Tomas Vanek
>>
>> ------------------------------------------------------------------------------
>> Try before you buy = See our experts in action!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-dev2
>> _______________________________________________
>> Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
>> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
>>
>>
>
>
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
>
>

Re: [zd1211-devs] duration_id field in zd1211rw

[Jussi K. <jus...@mb...>]

Quoting Tomas Vanek <Tom...@fb...>:

> Hello developers,
>
> first thank you for the rewrite of zd1211 driver.
>
> I use a small x86 server currently with linux 3.2.1 and generic ZyDAS
> wifi ZD1211B 802.11g (USB ID 0ace:1215), fw 1.4
> hostapd v0.7.3 is used for AP mode with WPA2 security. 6 wifi clients
> (ath and prism54 chips) connect without problems.
>
> Unfortunately two notebooks with iwl5100 card cannot connect at all.
> Tested with both linux and Win7 on the notebook.
> I also tested without security and iwl5100 didn't work again.
>
> Hostapd log shows that association worked but EAPOL frame is not replied
> by iwl:
> ----------------------------------------------------------------------
> STA 00:22:fb:xx:xx:xx sent probe request for our SSID
> mgmt::auth
> authentication: STA=00:22:fb:xx:xx:xx auth_alg=0 auth_transaction=1
> status_code=0 wep=0
>    New STA
> authentication reply: STA=00:22:fb:xx:xx:xx auth_alg=0
> auth_transaction=2 resp=0 (IE len=0)
> mgmt::proberesp cb
> mgmt::auth cb
> mgmt::assoc_req
> association request: STA=00:22:fb:xx:xx:xx capab_info=0x411
> listen_interval=10
>    new AID 1
> nl80211: Set beacon (beacon_set=1)
> mgmt::assoc_resp cb
> wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=0xa057900 key_idx=0
> set_tx=1 seq_len=0 key_len=0
>     addr=00:22:fb:xx:xx:xx
> wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=0xa057900 key_idx=0
> set_tx=1 seq_len=0 key_len=0
>     addr=00:22:fb:xx:xx:xx
> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state INITIALIZE
> wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=0xa057900 key_idx=0
> set_tx=1 seq_len=0 key_len=0
>     addr=00:22:fb:xx:xx:xx
> WPA: 00:22:fb:xx:xx:xx WPA_PTK_GROUP entering state IDLE
> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state AUTHENTICATION
> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state AUTHENTICATION2
> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state INITPSK
> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state PTKSTART
> WPA: Send EAPOL(version=2 secure=0 mic=0 ack=1 install=0 pairwise=8
> kde_len=0 keyidx=0 encr=0)
> nl80211: Event message available
> nl80211: Ignored unknown event (cmd=19)
> IEEE 802.1X: 00:22:fb:xx:xx:xx TX status - version=2 type=3 length=95 -
> ack=0
> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state PTKSTART
> WPA: Send EAPOL(version=2 secure=0 mic=0 ack=1 install=0 pairwise=8
> kde_len=0 keyidx=0 encr=0)
> IEEE 802.1X: 00:22:fb:xx:xx:xx TX status - version=2 type=3 length=95 -
> ack=0
> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state PTKSTART
> WPA: Send EAPOL(version=2 secure=0 mic=0 ack=1 install=0 pairwise=8
> kde_len=0 keyidx=0 encr=0)
> IEEE 802.1X: 00:22:fb:xx:xx:xx TX status - version=2 type=3 length=95 -
> ack=0
> mgmt::deauth
> deauthentication: STA=00:22:fb:xx:xx:xx reason_code=1
> AP-STA-DISCONNECTED 00:22:fb:xx:xx:xx
> wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=0xa057900 key_idx=0
> set_tx=1 seq_len=0 key_len=0
>     addr=00:22:fb:xx:xx:xx
> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state DISCONNECTED
> WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state INITIALIZE
> ----------------------------------------------------------------------
>
> Sniffing wireless packets I found strange values in ieee80211 header of
> EAPOL and other data packets:
> duration_id was bigger than 60000, such values should be reserved for PS
> poll.
> Sniffer at iwl5100 didn't showed these packets at all. Management
> packets with duration_id=0 were
> received ok.
>
> After some trials I reset the duration computed by mac80211 to zero:
> ----------------------------------------------------------------------
> diff --git a/drivers/net/wireless/zd1211rw/zd_mac.c
> b/drivers/net/wireless/zd1211rw/zd_mac.c
> index 0a70149..ffbe208 100644
> --- a/drivers/net/wireless/zd1211rw/zd_mac.c
> +++ b/drivers/net/wireless/zd1211rw/zd_mac.c
> @@ -866,6 +866,9 @@ static int fill_ctrlset(struct zd_mac *mac,
>
>          ZD_ASSERT(frag_len <= 0xffff);
>
> +       /* firmware computes the duration itself and needs the field set
> to 0 at input */
> +       hdr->duration_id= 0;
> +
>          txrate = ieee80211_get_tx_rate(mac->hw, info);
>
>          cs->modulation = txrate->hw_value;
> ----------------------------------------------------------------------
> and surprisingly the ZD1211B firmware computes reasonable values of
> duration.
> iwl5100 connects ok with fixed driver.
>
> This change probably breaks PS poll packets. They send assoc id in
> duration_id field.

Looking at vendor's zd1211 driver, it appears that duration_id is kept  
at zero for all packets except PSPoll. So following should work:

+       /* firmware computes the duration itself and needs the field set to 0
+        * at input for all packet types than PSPoll.
+        */
+       if (!ieee80211_is_pspoll(hdr->fc))
+               hdr->duration_id = 0;

>
> I don't know if non B version of ZD1211 has the same problem.
>

Both are handled same for duration_id by vendor driver.

>
> Best regards
>      Tomas Vanek
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
>
>

[zd1211-devs] duration_id field in zd1211rw

[Tomas V. <Tom...@fb...>]

Hello developers,

first thank you for the rewrite of zd1211 driver.

I use a small x86 server currently with linux 3.2.1 and generic ZyDAS 
wifi ZD1211B 802.11g (USB ID 0ace:1215), fw 1.4
hostapd v0.7.3 is used for AP mode with WPA2 security. 6 wifi clients 
(ath and prism54 chips) connect without problems.

Unfortunately two notebooks with iwl5100 card cannot connect at all. 
Tested with both linux and Win7 on the notebook.
I also tested without security and iwl5100 didn't work again.

Hostapd log shows that association worked but EAPOL frame is not replied 
by iwl:
----------------------------------------------------------------------
STA 00:22:fb:xx:xx:xx sent probe request for our SSID
mgmt::auth
authentication: STA=00:22:fb:xx:xx:xx auth_alg=0 auth_transaction=1 
status_code=0 wep=0
   New STA
authentication reply: STA=00:22:fb:xx:xx:xx auth_alg=0 
auth_transaction=2 resp=0 (IE len=0)
mgmt::proberesp cb
mgmt::auth cb
mgmt::assoc_req
association request: STA=00:22:fb:xx:xx:xx capab_info=0x411 
listen_interval=10
   new AID 1
nl80211: Set beacon (beacon_set=1)
mgmt::assoc_resp cb
wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=0xa057900 key_idx=0 
set_tx=1 seq_len=0 key_len=0
    addr=00:22:fb:xx:xx:xx
wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=0xa057900 key_idx=0 
set_tx=1 seq_len=0 key_len=0
    addr=00:22:fb:xx:xx:xx
WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state INITIALIZE
wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=0xa057900 key_idx=0 
set_tx=1 seq_len=0 key_len=0
    addr=00:22:fb:xx:xx:xx
WPA: 00:22:fb:xx:xx:xx WPA_PTK_GROUP entering state IDLE
WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state AUTHENTICATION
WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state AUTHENTICATION2
WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state INITPSK
WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state PTKSTART
WPA: Send EAPOL(version=2 secure=0 mic=0 ack=1 install=0 pairwise=8 
kde_len=0 keyidx=0 encr=0)
nl80211: Event message available
nl80211: Ignored unknown event (cmd=19)
IEEE 802.1X: 00:22:fb:xx:xx:xx TX status - version=2 type=3 length=95 - 
ack=0
WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state PTKSTART
WPA: Send EAPOL(version=2 secure=0 mic=0 ack=1 install=0 pairwise=8 
kde_len=0 keyidx=0 encr=0)
IEEE 802.1X: 00:22:fb:xx:xx:xx TX status - version=2 type=3 length=95 - 
ack=0
WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state PTKSTART
WPA: Send EAPOL(version=2 secure=0 mic=0 ack=1 install=0 pairwise=8 
kde_len=0 keyidx=0 encr=0)
IEEE 802.1X: 00:22:fb:xx:xx:xx TX status - version=2 type=3 length=95 - 
ack=0
mgmt::deauth
deauthentication: STA=00:22:fb:xx:xx:xx reason_code=1
AP-STA-DISCONNECTED 00:22:fb:xx:xx:xx
wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=0xa057900 key_idx=0 
set_tx=1 seq_len=0 key_len=0
    addr=00:22:fb:xx:xx:xx
WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state DISCONNECTED
WPA: 00:22:fb:xx:xx:xx WPA_PTK entering state INITIALIZE
----------------------------------------------------------------------

Sniffing wireless packets I found strange values in ieee80211 header of 
EAPOL and other data packets:
duration_id was bigger than 60000, such values should be reserved for PS 
poll.
Sniffer at iwl5100 didn't showed these packets at all. Management 
packets with duration_id=0 were
received ok.

After some trials I reset the duration computed by mac80211 to zero:
----------------------------------------------------------------------
diff --git a/drivers/net/wireless/zd1211rw/zd_mac.c 
b/drivers/net/wireless/zd1211rw/zd_mac.c
index 0a70149..ffbe208 100644
--- a/drivers/net/wireless/zd1211rw/zd_mac.c
+++ b/drivers/net/wireless/zd1211rw/zd_mac.c
@@ -866,6 +866,9 @@ static int fill_ctrlset(struct zd_mac *mac,

         ZD_ASSERT(frag_len <= 0xffff);

+       /* firmware computes the duration itself and needs the field set 
to 0 at input */
+       hdr->duration_id= 0;
+
         txrate = ieee80211_get_tx_rate(mac->hw, info);

         cs->modulation = txrate->hw_value;
----------------------------------------------------------------------
and surprisingly the ZD1211B firmware computes reasonable values of 
duration.
iwl5100 connects ok with fixed driver.

This change probably breaks PS poll packets. They send assoc id in 
duration_id field.

I don't know if non B version of ZD1211 has the same problem.


Best regards
     Tomas Vanek

Re: [zd1211-devs] Patch for new kernels UP to 2.6.33 and higher

[Jussi K. <jus...@mb...>]

Hello,

Master mode works, but not same way as with zd1211. You need to use 'hostapd':
  http://linuxwireless.org/en/users/Documentation/hostapd

Quick copy-paste from that page: "The mac80211 subsystem moves all  
aspects of master mode into user space. It depends on hostapd to  
handle authenticating clients, setting encryption keys, establishing  
key rotation policy, and other aspects of the wireless infrastructure.  
Due to this, the old method of issuing 'iwconfig <wireless interface>  
mode master' no longer works. Userspace programs like hostapd now use  
netlink (the nl80211 driver) to create a master mode interface for  
your traffic and a monitor mode interface for receiving and  
transmitting management frames. "

-Jussi

Quoting "Michael Y. Gluhovchenko" <glu...@gr...>:

> Hello;
> I  got new kernel 3.0.0-12. Master mode don't work.
> Where can I get zd1211rw driver with support master mode?
> Thanks.
> --
> With best regards,
> Mikler
> --------------------------------------------------
> From: "Jussi Kivilinna" <jus...@mb...>
> Sent: Thursday, November 17, 2011 4:24 PM
> To: "Michael Y. Gluhovchenko" <glu...@gr...>
> Cc: "Michael Tokarev" <mj...@tl...>; <zd1...@li...>
> Subject: Re: [zd1211-devs] Patch for new kernels UP to 2.6.33 and higher
>
>> Hello,
>>
>> zd1211rw gained master mode support in 2.6.39. For older kernels I  
>> recommend you to try compat-wireless (backports of latest wireless  
>> drivers):
>> http://linuxwireless.org/en/users/Download
>>
>> -Jussi
>>
>> Quoting "Michael Y. Gluhovchenko" <glu...@gr...>:
>>
>>> Hi Michael,
>>> Thanks for your reply
>>> Main line driver(zd1211rw) doesn't support master mode. It can't  
>>> use for AP.
>>> I need it to test old chips dongles. And of it possible to improve some
>>> aspect of code.
>>>
>>> --
>>> With best regards,
>>> Mikler
>>>
>>> --------------------------------------------------
>>> From: "Michael Tokarev" <mj...@tl...>
>>> Sent: Thursday, November 17, 2011 3:25 PM
>>> To: "Michael Y. Gluhovchenko" <glu...@gr...>
>>> Cc: <zd1...@li...>
>>> Subject: Re: [zd1211-devs] Patch for new kernels UP to 2.6.33 and higher
>>>
>>>> On 17.11.2011 12:14, Michael Y. Gluhovchenko wrote:
>>>>> Hello all;
>>>>> I've make patch for driver. Now driver compile in new kernels.  But I
>>>>> have
>>>>> some problems. How can I associate the driver and the device? How is it
>>>>> possible to configure.
>>>>> lsusb
>>>>> Bus 001 Device 007: ID 0ace:1215 ZyDAS ZD1211B 802.11g
>>>>> lsmod
>>>>> Module                  Size  Used by
>>>>> zd1211                270616  0
>>>>
>>>> Maybe you should use zd1211rw instead, which is part of the stock
>>>> (mainline) kernel, does not require any patches to compile, and
>>>> also supports this device?
>>>>
>>>> /mjt
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> All the data continuously generated in your IT infrastructure
>>> contains a definitive record of customers, application performance,
>>> security threats, fraudulent activity, and more. Splunk takes this
>>> data and makes sense of it. IT sense. And common sense.
>>> http://p.sf.net/sfu/splunk-novd2d
>>> _______________________________________________
>>> Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
>>> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
>>>
>>>
>>
>>
>>
>
>

Re: [zd1211-devs] Patch for new kernels UP to 2.6.33 and higher

[Michael T. <mj...@tl...>]

On 18.11.2011 07:29, Michael Y. Gluhovchenko wrote:
> Hello;
> I  got new kernel 3.0.0-12. Master mode don't work.

WorksForMe(tm) - I'm sending this email over wifi link
where zd1211rw acts as an access point.

> Where can I get zd1211rw driver with support master mode?

I don't understand this question.

/mjt

Re: [zd1211-devs] Patch for new kernels UP to 2.6.33 and higher

[Michael Y. G. <glu...@gr...>]

Hello;
I  got new kernel 3.0.0-12. Master mode don't work.
Where can I get zd1211rw driver with support master mode?
Thanks.
--
With best regards,
 Mikler
--------------------------------------------------
From: "Jussi Kivilinna" <jus...@mb...>
Sent: Thursday, November 17, 2011 4:24 PM
To: "Michael Y. Gluhovchenko" <glu...@gr...>
Cc: "Michael Tokarev" <mj...@tl...>; <zd1...@li...>
Subject: Re: [zd1211-devs] Patch for new kernels UP to 2.6.33 and higher

> Hello,
>
> zd1211rw gained master mode support in 2.6.39. For older kernels I 
> recommend you to try compat-wireless (backports of latest wireless 
> drivers):
>  http://linuxwireless.org/en/users/Download
>
> -Jussi
>
> Quoting "Michael Y. Gluhovchenko" <glu...@gr...>:
>
>> Hi Michael,
>> Thanks for your reply
>> Main line driver(zd1211rw) doesn't support master mode. It can't use for 
>> AP.
>> I need it to test old chips dongles. And of it possible to improve some
>> aspect of code.
>>
>> --
>>  With best regards,
>>  Mikler
>>
>> --------------------------------------------------
>> From: "Michael Tokarev" <mj...@tl...>
>> Sent: Thursday, November 17, 2011 3:25 PM
>> To: "Michael Y. Gluhovchenko" <glu...@gr...>
>> Cc: <zd1...@li...>
>> Subject: Re: [zd1211-devs] Patch for new kernels UP to 2.6.33 and higher
>>
>>> On 17.11.2011 12:14, Michael Y. Gluhovchenko wrote:
>>>> Hello all;
>>>> I've make patch for driver. Now driver compile in new kernels.  But I
>>>> have
>>>> some problems. How can I associate the driver and the device? How is it
>>>> possible to configure.
>>>> lsusb
>>>> Bus 001 Device 007: ID 0ace:1215 ZyDAS ZD1211B 802.11g
>>>> lsmod
>>>> Module                  Size  Used by
>>>> zd1211                270616  0
>>>
>>> Maybe you should use zd1211rw instead, which is part of the stock
>>> (mainline) kernel, does not require any patches to compile, and
>>> also supports this device?
>>>
>>> /mjt
>>
>>
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure
>> contains a definitive record of customers, application performance,
>> security threats, fraudulent activity, and more. Splunk takes this
>> data and makes sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-novd2d
>> _______________________________________________
>> Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
>> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
>>
>>
>
>
> 

Re: [zd1211-devs] Patch for new kernels UP to 2.6.33 and higher

[Hin-Tak L. <hin...@ya...>]

0x0ACE 0x1215 should bind to the zd1211b kernel module (the vendor driver builds two kernel modules, zd1211 and zd1211b). That said, compat-wireless is probably the way to go...

--- On Thu, 17/11/11, Jussi Kivilinna <jus...@mb...> wrote:

> Hello,
> 
> zd1211rw gained master mode support in 2.6.39. For older
> kernels I  
> recommend you to try compat-wireless (backports of latest
> wireless  
> drivers):
>   http://linuxwireless.org/en/users/Download
> 
> -Jussi
> 
> Quoting "Michael Y. Gluhovchenko" <glu...@gr...>:
> 
> > Hi Michael,
> > Thanks for your reply
> > Main line driver(zd1211rw) doesn't support master
> mode. It can't use for AP.
> > I need it to test old chips dongles. And of it
> possible to improve some
> > aspect of code.
> >
> > --
> >  With best regards,
> >  Mikler
> >
> > --------------------------------------------------
> > From: "Michael Tokarev" <mj...@tl...>
> > Sent: Thursday, November 17, 2011 3:25 PM
> > To: "Michael Y. Gluhovchenko" <glu...@gr...>
> > Cc: <zd1...@li...>
> > Subject: Re: [zd1211-devs] Patch for new kernels UP to
> 2.6.33 and higher
> >
> >> On 17.11.2011 12:14, Michael Y. Gluhovchenko
> wrote:
> >>> Hello all;
> >>> I've make patch for driver. Now driver compile
> in new kernels.  But I
> >>> have
> >>> some problems. How can I associate the driver
> and the device? How is it
> >>> possible to configure.
> >>> lsusb
> >>> Bus 001 Device 007: ID 0ace:1215 ZyDAS ZD1211B
> 802.11g
> >>> lsmod
> >>> Module         
>         Size  Used by
> >>> zd1211         
>       270616  0
> >>
> >> Maybe you should use zd1211rw instead, which is
> part of the stock
> >> (mainline) kernel, does not require any patches to
> compile, and
> >> also supports this device?
> >>
> >> /mjt
> >
> >
> >
> ------------------------------------------------------------------------------
> > All the data continuously generated in your IT
> infrastructure
> > contains a definitive record of customers, application
> performance,
> > security threats, fraudulent activity, and more.
> Splunk takes this
> > data and makes sense of it. IT sense. And common
> sense.
> > http://p.sf.net/sfu/splunk-novd2d
> > _______________________________________________
> > Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
> > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
> >
> >
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT
> infrastructure 
> contains a definitive record of customers, application
> performance, 
> security threats, fraudulent activity, and more. Splunk
> takes this 
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
> 

Re: [zd1211-devs] Patch for new kernels UP to 2.6.33 and higher

[Jussi K. <jus...@mb...>]

Hello,

zd1211rw gained master mode support in 2.6.39. For older kernels I  
recommend you to try compat-wireless (backports of latest wireless  
drivers):
  http://linuxwireless.org/en/users/Download

-Jussi

Quoting "Michael Y. Gluhovchenko" <glu...@gr...>:

> Hi Michael,
> Thanks for your reply
> Main line driver(zd1211rw) doesn't support master mode. It can't use for AP.
> I need it to test old chips dongles. And of it possible to improve some
> aspect of code.
>
> --
>  With best regards,
>  Mikler
>
> --------------------------------------------------
> From: "Michael Tokarev" <mj...@tl...>
> Sent: Thursday, November 17, 2011 3:25 PM
> To: "Michael Y. Gluhovchenko" <glu...@gr...>
> Cc: <zd1...@li...>
> Subject: Re: [zd1211-devs] Patch for new kernels UP to 2.6.33 and higher
>
>> On 17.11.2011 12:14, Michael Y. Gluhovchenko wrote:
>>> Hello all;
>>> I've make patch for driver. Now driver compile in new kernels.  But I
>>> have
>>> some problems. How can I associate the driver and the device? How is it
>>> possible to configure.
>>> lsusb
>>> Bus 001 Device 007: ID 0ace:1215 ZyDAS ZD1211B 802.11g
>>> lsmod
>>> Module                  Size  Used by
>>> zd1211                270616  0
>>
>> Maybe you should use zd1211rw instead, which is part of the stock
>> (mainline) kernel, does not require any patches to compile, and
>> also supports this device?
>>
>> /mjt
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
>
>

Re: [zd1211-devs] Patch for new kernels UP to 2.6.33 and higher

[Michael Y. G. <glu...@gr...>]

Hi Michael,
Thanks for your reply
Main line driver(zd1211rw) doesn't support master mode. It can't use for AP. 
I need it to test old chips dongles. And of it possible to improve some 
aspect of code.

-- 
 With best regards,
 Mikler

--------------------------------------------------
From: "Michael Tokarev" <mj...@tl...>
Sent: Thursday, November 17, 2011 3:25 PM
To: "Michael Y. Gluhovchenko" <glu...@gr...>
Cc: <zd1...@li...>
Subject: Re: [zd1211-devs] Patch for new kernels UP to 2.6.33 and higher

> On 17.11.2011 12:14, Michael Y. Gluhovchenko wrote:
>> Hello all;
>> I've make patch for driver. Now driver compile in new kernels.  But I 
>> have
>> some problems. How can I associate the driver and the device? How is it
>> possible to configure.
>> lsusb
>> Bus 001 Device 007: ID 0ace:1215 ZyDAS ZD1211B 802.11g
>> lsmod
>> Module                  Size  Used by
>> zd1211                270616  0
>
> Maybe you should use zd1211rw instead, which is part of the stock
> (mainline) kernel, does not require any patches to compile, and
> also supports this device?
>
> /mjt 

Re: [zd1211-devs] Patch for new kernels UP to 2.6.33 and higher

[Michael T. <mj...@tl...>]

On 17.11.2011 12:14, Michael Y. Gluhovchenko wrote:
> Hello all;
> I've make patch for driver. Now driver compile in new kernels.  But I have
> some problems. How can I associate the driver and the device? How is it
> possible to configure.
> lsusb
> Bus 001 Device 007: ID 0ace:1215 ZyDAS ZD1211B 802.11g
> lsmod
> Module                  Size  Used by
> zd1211                270616  0

Maybe you should use zd1211rw instead, which is part of the stock
(mainline) kernel, does not require any patches to compile, and
also supports this device?

/mjt

[zd1211-devs] Patch for new kernels UP to 2.6.33 and higher

[Michael Y. G. <glu...@gr...>]

 Hello all;
 I've make patch for driver. Now driver compile in new kernels.  But I have
 some problems. How can I associate the driver and the device? How is it
 possible to configure.
 lsusb
 Bus 001 Device 007: ID 0ace:1215 ZyDAS ZD1211B 802.11g
 lsmod
 Module                  Size  Used by
 zd1211                270616  0

 Linux net-001 2.6.38-12-generic #51-Ubuntu SMP

 -- 
 With best regards,
 Mikler

 

[zd1211-devs] zd1211 in monitor mode only beacon

[吴斌斌 <sq...@gm...>]

Hi all,
my usb wireless card' chip is zd1211, but i can only get beacon and probe
request in monitor mode. Has anyone ever faced such problem?
My PC's system is ubuntu 11.10. These are my commands:

*ifconfig wlan0 down
iwconfig wlan0 mode Monitor(without error output)
ifconfig wlan0 up*

After these, i retype in "iwconfig" to check is the mode was set correctly.
It was in mode Monitor actually.
But in wireshark, it can only capture beacon and probe request/response.

Have i done anything wrong?

Thanks for help.

[zd1211-devs] ZyXEL dongle Connection timed out Ubuntu 10.04

[Fernando J. I. G. <fer...@gm...>]

Hi,

I am facing a trouble trying to use my *ZyXEL* 802.11g Wireless USB Adapter
model *G-202* in my system with Ubuntu 10.04. My hardware system is a
RoBoard100 <http://www.roboard.com/RB-100.htm>, the version 10.04 of Ubuntu
installed just has command-line support. When I installed the operative
system I had to change the kernel in order to work in the RoBoard. The
actual version of it is:

*$ uname -r
2.6.34.10-vortex86-sg
*
The problem is the following. The RoBoard detects the wireless dongle as I
can see in the *dmesg* log, using *lsusb* or simply listing my devices with
wireless extensions with *iwconfig*. As I find it normal, when I plug in the
dongle, the interface is down since I have not yet anything in my
/etc/network/interfaces in order to set it automatically. When I try to set
up the device I obtain the following:

*$ ifconfig wlan1 up
SIOCSIFFLAGS: Connection timed out*

If I insist a couple of times more with the same command, I end up
obtaining:

*usb 2-1: USB control request for firmware upload failed. Error number -110
usb 2-1: Could not upload firmaware code uph. Error number -110
zd1211rq 2-1:1.0: couldn't load firmware. Error number -110
SIOCSIFFLAGS: Connection timed out*

The output of dmesg looks like this after:
*
usb 2-1: firmware: requesting zd1211/zd1211b_ub
usb 2-1: firmware: requesting zd1211/zd1211b_uphr
usb 2-1: USB control request for firmware upload failed. Error number -110**
usb 2-1: Could not upload firmaware code uph. Error number -110
zd1211rq 2-1:1.0: couldn't load firmware. Error number -110*

I am a bit confused with the cause of this problem. Surfing on the web I
have found lot of entrances related to this problem, not with the same
hardware I am using though. I have tried with some of the solutions such as
modifying the permissions of /lib/firmware/zd1211/ and all the files under,
downloading the drivers for this device from linux
wireless<http://linuxwireless.org/en/users/Drivers/zd1211rw>and
copying the files to /lib/firmware/zd1211 and also installing the
package *linux-firmware-nonfree*. I have also tried modifying the speed of
the USB 2.0 from High Speed to Full Speed on the advanced properties of the
BIOS. Unfortunately, none of these strategies have solved my problem.

Does anyone have a clue what can be wrong? How could I know if it is a
problem of hardware incompatibility or if it can be solved via software?

Thank you very much in advanced.

Regards,
Fernando.

[zd1211-devs] monitor mode in Belkin Components F5D7050 Wireless G Adapter v4000

[Christian M. <c...@sp...>]

Hello,

I have a:
Belkin Components F5D7050 Wireless G Adapter v4000

$ dmesg | egrep "zd1211b? chip"
[30382.403185] zd1211rw 1-4.4:1.0: zd1211b chip 050d:705c v4810 high 00-1c-df AL2230_RF pa0 g--NS

if I turn the device in monitor mode there is no signal strength value in the radiotap header.
i have tested this with wireshark and libpcap.

$ uname -a
Linux infrared 2.6.39-02063903-generic #201107091121 SMP Sat Jul 9 11:25:36 UTC 2011 x86_64 GNU/Linux

$ iw dev wlan2 station dump
Station 00:XX:XX:XX:XX:XX (on wlan2)
	inactive time:	21350 ms
	rx bytes:	7703
	rx packets:	268
	tx bytes:	7420
	tx packets:	106
	signal:  	39 dBm
	tx bitrate:	1.0 MBit/s

so the signal should be in [-127 to 0] ?!?
what is iw doing if there is no rssi value given? network manager shows some tiny signal.....

on my other device (ralink based) everything is fine.

thanks, christian

[zd1211-devs] zd1211B for AP mode

[张传德 <zha...@lz...>]

hi, everyone
   Thanks for your help! Use hostapd can make ZD1211B usb wireless card work with master mode.

   In my machine:
#cat hostapd.conf
interface=wlan1
driver=nl80211
ssid=test
channel=1
# hostapd ./hostapd.conf

   In other test machine:
# iwlist wlan0 scan
          Cell 10 - Address: 00:1D:0F:04:81:C6
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=70/70  Signal level=-36 dBm  
                    Encryption key:off
                    ESSID:"test"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
                    Mode:Master
                    Extra:tsf=0000000000000000
                    Extra: Last beacon: 68ms ago
                    IE: Unknown: 000474657374
                    IE: Unknown: 010482840B16
                    IE: Unknown: 030101
# iwconfig wlan0 essid test mode managed channel 1 
# iwconfig wlan0                                  
wlan0     IEEE 802.11bgn  ESSID:"test"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:1D:0F:04:81:C6   
          Bit Rate=1 Mb/s   Tx-Power=14 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=70/70  Signal level=-33 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:3   Missed beacon:0

   Now this card set master mode and another wireless card can access.

Best regards!
zhangchd


> See http://wireless.kernel.org/RTFM-AP
> 
> And in general, mac80211 doesn't really support setting interface
> modes through wext (iwconfig) - use nl80211 (iw) instead. But even
> that won't get you AP mode; see above.
> 

Re: [zd1211-devs] zd1211B for AP mode

[Nerijus B. <ne...@us...>]

On Fri, 17 Jun 2011 20:10:23 +0800 (CST) ÕÅ“«µĀ <zha...@lz...> wrote:

>    I can use this usb wireless card with mode managed and it can access normal wifi.
> If I try to make it work with master mode, I will get error information: 
> # iwconfig wlan1 essid dslab mode master                       
> Error for wireless request "Set Mode" (8B06) :
>     SET failed on device wlan1 ; Invalid argument.

This usually doesn't work. Just setup hostapd and it will setup master mode itself.

Regards,
Nerijus

Re: [zd1211-devs] zd1211B for AP mode

[Gábor S. <net...@gm...>]

See http://wireless.kernel.org/RTFM-AP

And in general, mac80211 doesn't really support setting interface
modes through wext (iwconfig) - use nl80211 (iw) instead. But even
that won't get you AP mode; see above.

On Fri, Jun 17, 2011 at 2:10 PM, 张传德 <zha...@lz...> wrote:
> Hello, everyone
>   I'm a student of Lanzhou university, china.
> I find the message about ZD1211B support master mode with
> Linux kernel 2.6.39 from
> http://linuxwireless.org/en/users/Drivers/zd1211rw
>    My machine information:
> # uname -r
> 2.6.39-gentoo-r1
> # lsusb
> Bus 002 Device 006: ID 0ace:1215 ZyDAS ZD1211B 802.11g
> # dmesg | egrep "zd1211b? chip"
> zd1211rw 2-1.4:1.0: zd1211b chip 0ace:1215 v4810 high 00-1d-0f UW2453_RF pa0 -7---
> # lsmod
> Module                  Size  Used by
> zd1211rw               42496  0
>
>   I can use this usb wireless card with mode managed and it can access normal wifi.
> If I try to make it work with master mode, I will get error information:
> # iwconfig wlan1 essid dslab mode master
> Error for wireless request "Set Mode" (8B06) :
>    SET failed on device wlan1 ; Invalid argument.
>
>   I search from google and find somebody use open1211 driver for mode master.
> I also try this way, but fail. Some website said should use hostapd and iw to
> config and set mode.
>   How can I make this chip work in master mode(AP)?
>   Sorry for my terrible English. Thanks for your patience!
>
> Best regards!
> Zhangchd
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
>



-- 
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)

[zd1211-devs] zd1211B for AP mode

[张传德 <zha...@lz...>]

Hello, everyone
   I'm a student of Lanzhou university, china. 
I find the message about ZD1211B support master mode with 
Linux kernel 2.6.39 from 
http://linuxwireless.org/en/users/Drivers/zd1211rw
    My machine information:
# uname -r
2.6.39-gentoo-r1 
# lsusb 
Bus 002 Device 006: ID 0ace:1215 ZyDAS ZD1211B 802.11g
# dmesg | egrep "zd1211b? chip"
zd1211rw 2-1.4:1.0: zd1211b chip 0ace:1215 v4810 high 00-1d-0f UW2453_RF pa0 -7---
# lsmod 
Module                  Size  Used by
zd1211rw               42496  0 

   I can use this usb wireless card with mode managed and it can access normal wifi.
If I try to make it work with master mode, I will get error information: 
# iwconfig wlan1 essid dslab mode master                       
Error for wireless request "Set Mode" (8B06) :
    SET failed on device wlan1 ; Invalid argument.

   I search from google and find somebody use open1211 driver for mode master.
I also try this way, but fail. Some website said should use hostapd and iw to 
config and set mode.
   How can I make this chip work in master mode(AP)?
   Sorry for my terrible English. Thanks for your patience!

Best regards!
Zhangchd

Re: [zd1211-devs] firmware timeout issues (error -110)

[Roh . <ro...@ho...>]

Hi Jussi,
Thank you for your help :)
I applied the patch to compat-wireless-2011-04-22 and can confirm that everything is working perfectly.
see dmesg (zd1211rw debug on):
[ 6171.801385] zd1211rw usb_init()[ 6171.801595] usb 3-2: print_id() 07b8:6001 v4330 full[ 6171.958038] usb 3-2: reset full speed USB device using ohci_hcd and address 2[ 6172.137333] zd1211rw 3-2:1.0: zd_chip_read_mac_addr_fw() [ 6172.147236] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'[ 6172.149568] zd1211rw 3-2:1.0: probe() successful[ 6172.149578] zd1211rw 3-2:1.0: phy1[ 6172.150844] usbcore: registered new interface driver zd1211rw[ 6172.150979] zd1211rw initialized[ 6172.448820] zd1211rw 3-2:1.0: zd_usb_init_hw() [ 6172.448833] usb 3-2: request_fw_file() fw name zd1211/zd1211_ub[ 6172.455339] usb 3-2: upload_firmware() firmware device id 0x4330 is equal to the actual device id[ 6172.455350] usb 3-2: request_fw_file() fw name zd1211/zd1211_uphr[ 6172.465214] usb 3-2: upload_code() transfer size 4096[ 6172.477253] usb 3-2: upload_code() transfer size 1024[ 6172.485238] usb 3-2: upload_code() firmware confirm return value 0x01[ 6172.488255] zd1211rw 3-2:1.0: zd_usb_enable_int() [ 6172.488270] zd1211rw 3-2:1.0: zd_usb_enable_int() submit urb c6eae000[ 6172.488289] zd1211rw 3-2:1.0: zd_chip_init_hw() [ 6172.492247] zd1211rw 3-2:1.0: dump_cr() CR_AFTER_PNP 0x00000000[ 6172.495246] zd1211rw 3-2:1.0: dump_cr() CR_GPI_EN 0x00000000[ 6172.498246] zd1211rw 3-2:1.0: dump_cr() CR_INTERRUPT 0x00000000[ 6172.504237] zd1211rw 3-2:1.0: read_fw_regs_offset() fw_regs_base: 0xf7d4[ 6172.519235] zd1211rw 3-2:1.0: read_pod() E2P_POD 0x00000104[ 6172.519248] zd1211rw 3-2:1.0: read_pod() RF AL2230_RF 0x4 PA type 0x0 patch CCK 1 patch CR157 0 patch 6M 0 new PHY 0 link LED2 tx led 1[ 6172.519257] zd1211rw 3-2:1.0: hw_init() [ 6172.519262] zd1211rw 3-2:1.0: zd1211_hw_reset_phy() [ 6172.537228] zd1211rw 3-2:1.0: zd1211_hw_init_hmac() [ 6172.558230] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x003f790 bits 24[ 6172.564228] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x0033331 bits 24[ 6172.570227] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x000000d bits 24[ 6172.576226] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x00b3331 bits 24[ 6172.582225] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x003b812 bits 24[ 6172.588224] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x000fff3 bits 24[ 6172.594225] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x00005a4 bits 24[ 6172.600224] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x0000da4 bits 24[ 6172.606222] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x00f4dc5 bits 24[ 6172.612221] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x00805b6 bits 24[ 6172.618221] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x0011687 bits 24[ 6172.624220] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x0000688 bits 24[ 6172.630219] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x00403b9 bits 24[ 6172.636218] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x000dbba bits 24[ 6172.642217] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x000099b bits 24[ 6172.648216] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x00bdffc bits 24[ 6172.654214] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x000000d bits 24[ 6172.660214] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x000500f bits 24[ 6172.669210] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x000d00f bits 24[ 6172.675212] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x0004c0f bits 24[ 6172.681211] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x000540f bits 24[ 6172.687210] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x000700f bits 24[ 6172.693209] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x000500f bits 24[ 6172.709206] zd1211rw 3-2:1.0: firmware version 4605[ 6172.712218] zd1211rw 3-2:1.0: dump_fw_registers() FW_FIRMWARE_VER 0x4605[ 6172.712229] zd1211rw 3-2:1.0: dump_fw_registers() FW_USB_SPEED 0x0000[ 6172.712235] zd1211rw 3-2:1.0: dump_fw_registers() FW_FIX_TX_RATE 0x0000[ 6172.712241] zd1211rw 3-2:1.0: dump_fw_registers() FW_LINK_STATUS 0x0000[ 6172.715216] zd1211rw 3-2:1.0: dump_cr() CR_AFTER_PNP 0x00000001[ 6172.718217] zd1211rw 3-2:1.0: dump_cr() CR_GPI_EN 0x00000000[ 6172.721216] zd1211rw 3-2:1.0: dump_cr() CR_INTERRUPT 0x00000000[ 6172.781206] zd1211rw 3-2:1.0: zd1211 chip 07b8:6001 v4330 full 00-12-0e AL2230_RF pa0 g----[ 6172.784211] zd1211rw 3-2:1.0: zd_read_regdomain() regdomain: 0x30[ 6172.786234] cfg80211: Calling CRDA for country: DE[ 6172.788190] usb 3-2: int_urb_complete() urb c6eae000 error -2[ 6172.788228] zd1211rw 3-2:1.0: zd_usb_disable_int() urb c6eae000 killed[ 6172.788242] zd1211rw 3-2:1.0: zd_usb_enable_int() [ 6172.788253] zd1211rw 3-2:1.0: zd_usb_enable_int() submit urb c6eae000[ 6172.813870] cfg80211: Current regulatory domain intersected:[ 6172.814069] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)[ 6172.814347] cfg80211:     (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)[ 6172.814589] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)[ 6172.814827] cfg80211:     (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)[ 6172.817213] zd1211rw 3-2:1.0: __zd_usb_enable_rx() [ 6172.817300] zd1211rw 3-2:1.0: zd_tx_watchdog_enable() [ 6172.820213] zd1211rw 3-2:1.0: housekeeping_enable() [ 6172.820234] zd1211rw 3-2:1.0: beacon_enable() [ 6172.820251] zd1211rw 3-2:1.0: zd_write_mac_addr_common() mac addr 00:12:0e:xx:xx:xx[ 6172.824195] zd1211rw 3-2:1.0: zd_op_bss_info_changed() changes: e[ 6172.824206] zd1211rw 3-2:1.0: zd_chip_set_rts_cts_rate_locked() preamble=0[ 6172.826226] zd1211rw 3-2:1.0: zd_op_bss_info_changed() changes: 4000[ 6172.830190] zd1211rw 3-2:1.0: zd_rf_set_channel() channel: 1[ 6172.830202] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x003f790 bits 24[ 6172.834189] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x0033331 bits 24[ 6172.838188] zd1211rw 3-2:1.0: zd_usb_rfwrite() value 0x000000d bits 24[ 6172.848192] zd1211rw 3-2:1.0: patch_cck_gain() patching value 20[ 6172.856310] ADDRCONF(NETDEV_UP): wlan0: link is not ready[ 6172.856859] zd1211rw 3-2:1.0: zd_op_prepare_multicast() mc addr 33:33:00:00:00:01[ 6172.856871] zd1211rw 3-2:1.0: zd_op_prepare_multicast() mc addr 01:00:5e:00:00:01

A very interesting bug indeed. The only difference between using the UTP extension cable or not was the device being detected as ehci (2.0) or ohci (1.1), I guess a timing lag would cause the ehci detection to fail and fallback to ohci. Very interesting how the device presents itself differently using the two different protocols (ehci & ohci), from what I can see in your patch one mode is bulk transfer and the other interrupt, kind of a weird way of doing things.
Once again thank you for your very speedy help Jussi.
Kind regards,
Rohan M.


> Date: Sun, 29 May 2011 19:39:22 +0300
> From: jus...@mb...
> To: ro...@ho...; zd1...@li...
> Subject: Re: [zd1211-devs] firmware timeout issues (error -110)
> 
> Hello!
> 
> This is interesting bug. The device actually presents itself  
> differently to host depending if it's running either USB 1.1 or 2.0.  
> As I tested zd1211rw AP-mode only on USB 2.0, result was that zd1211rw  
> expected to always see device as it seen on USB 2.0. On OHCI-host this  
> triggers error in ohci_hcd when driver tries to communicate to device  
> (and correct error message appears only with zd1211rw debugging  
> enabled).
> 
> Patch attached fixes the problem.
> 
> You can get patched compat-wireless tarball from:
>    
> http://koti.mbnet.fi/axh/kernel/zd1211rw/compat-wireless-2011-05-28-zd1211rw_fix.tar.bz2
> 
> -Jussi
> 
> Quoting Jussi Kivilinna <jus...@mb...>:
> 
> > Hi,
> >
> > I have reproduced the bug, happens only on ohci_hci (not ehci or
> > uchi). I'll start working on fix.
> >
> > -Jussi
> >
> > Quoting "Roh ." <ro...@ho...>:
> >
> >>
> >> Hi Devs,
> >> I hope someone can shed some light on why I am seeing these errors.
> >> When using the standard zd1211rw, mac802111 & cfg80211 drivers that
> >> come with fedora 14 (2.6.35.13-91) i am able to run my zd1211-based
> >> device perfectly without a glitch over a 10m UTP usb extension. I
> >> can even run airodump-ng for days on end without a glitch (of course
> >> no packet injection or signal level feedback).
> >> However when I try to use the compat-wireless-2011-05-26 or
> >> compat-wireless-2011-04-22 drivers I receive firmware timeout
> >> errors. Please see /var/log/message output below:
> >> Using stock Fedora 14 2.6.35.13-91 drivers: (works ok)
> >> May 29 17:14:28 rf kernel: [ 7296.240037] usb 2-2: new full speed
> >> USB device using ohci_hcd and address 5May 29 17:14:28 rf kernel: [
> >> 7296.417134] usb 2-2: not running at top speed; connect to a high
> >> speed hubMay 29 17:14:28 rf kernel: [ 7296.432140] usb 2-2: New USB
> >> device found, idVendor=07b8, idProduct=6001May 29 17:14:28 rf
> >> kernel: [ 7296.432213] usb 2-2: New USB device strings: Mfr=16,
> >> Product=32, SerialNumber=0May 29 17:14:28 rf kernel: [ 7296.432322]
> >> usb 2-2: Product: USB2.0 WLANMay 29 17:14:28 rf kernel: [
> >> 7296.432379] usb 2-2: Manufacturer: wug2670May 29 17:14:29 rf
> >> kernel: [ 7296.738492] cfg80211: Calling CRDA to update world
> >> regulatory domainMay 29 17:14:29 rf kernel: [ 7296.995070] usb 2-2:
> >> reset full speed USB device using ohci_hcd and address 5May 29
> >> 17:14:29 rf kernel: [ 7297.010274] cfg80211: World regulatory domain
> >> updated:May 29 17:14:29 rf kernel: [ 7297.010346]     (start_freq -
> >> end_freq @ bandwidth), (max_antenna_gain, max_eirp)May 29 17:14:29
> >> rf kernel: [ 7297.010457]     (2402000 KHz - 2472000 KHz @ 40000
> >> KHz), (300 mBi, 2000 mBm)May 29 17:14:29 rf kernel: [ 7297.010519]
> >>   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)May 29
> >> 17:14:29 rf kernel: [ 7297.010583]     (2474000 KHz - 2494000 KHz @
> >> 20000 KHz), (300 mBi, 2000 mBm)May 29 17:14:29 rf kernel: [
> >> 7297.010646]     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi,
> >> 2000 mBm)May 29 17:14:29 rf kernel: [ 7297.010709]     (5735000 KHz
> >> - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)May 29 17:14:29 rf
> >> kernel: [ 7297.235267] zd1211rw 2-2:1.0: phy0May 29 17:14:29 rf
> >> kernel: [ 7297.235405] usbcore: registered new interface driver
> >> zd1211rwMay 29 17:14:30 rf kernel: [ 7297.977792] cfg80211: Calling
> >> CRDA for country: AUMay 29 17:14:30 rf kernel: [ 7297.999546]
> >> cfg80211: Regulatory domain changed to country: AUMay 29 17:14:30 rf
> >> kernel: [ 7297.999619]     (start_freq - end_freq @ bandwidth),
> >> (max_antenna_gain, max_eirp)May 29 17:14:30 rf kernel: [
> >> 7297.999727]     (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000
> >> mBm)May 29 17:14:30 rf kernel: [ 7297.999789]     (5170000 KHz -
> >> 5250000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)May 29 17:14:30 rf
> >> kernel: [ 7297.999852]     (5250000 KHz - 5330000 KHz @ 40000 KHz),
> >> (300 mBi, 2300 mBm)May 29 17:14:30 rf kernel: [ 7297.999914]
> >> (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)May 29
> >> 17:14:31 rf kernel: [ 7298.945539] zd1211rw 2-2:1.0: firmware
> >> version 4605May 29 17:14:31 rf kernel: [ 7299.005554] zd1211rw
> >> 2-2:1.0: zd1211 chip 07b8:6001 v4330 full 00-12-0e AL2230_RF pa0
> >> g----May 29 17:14:31 rf kernel: [ 7299.010584] cfg80211: Calling
> >> CRDA for country: DEMay 29 17:14:31 rf kernel: [ 7299.026125]
> >> cfg80211: Current regulatory domain intersected:May 29 17:14:31 rf
> >> kernel: [ 7299.026198]     (start_freq - end_freq @ bandwidth),
> >> (max_antenna_gain, max_eirp)May 29 17:14:31 rf kernel: [
> >> 7299.026309]     (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000
> >> mBm)May 29 17:14:31 rf kernel: [ 7299.026371]     (5170000 KHz -
> >> 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)May 29 17:14:31 rf kernel:
> >> [ 7299.026431]     (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A,
> >> 2000 mBm)May 29 17:14:31 rf kernel: [ 7299.071672]
> >> ADDRCONF(NETDEV_UP): wlan0: link is not ready
> >> Using compat-wireless-2011-04-22 (firmware upload fails):
> >> May 29 17:09:47 rf kernel: [ 7015.122044] usb 2-2: new full speed
> >> USB device using ohci_hcd and address 4May 29 17:09:47 rf kernel: [
> >> 7015.299130] usb 2-2: not running at top speed; connect to a high
> >> speed hubMay 29 17:09:47 rf kernel: [ 7015.314138] usb 2-2: New USB
> >> device found, idVendor=07b8, idProduct=6001May 29 17:09:47 rf
> >> kernel: [ 7015.314210] usb 2-2: New USB device strings: Mfr=16,
> >> Product=32, SerialNumber=0May 29 17:09:47 rf kernel: [ 7015.314317]
> >> usb 2-2: Product: USB2.0 WLANMay 29 17:09:47 rf kernel: [
> >> 7015.314374] usb 2-2: Manufacturer: wug2670May 29 17:09:48 rf
> >> kernel: [ 7015.784541] cfg80211: Calling CRDA to update world
> >> regulatory domainMay 29 17:09:48 rf kernel: [ 7016.323803] cfg80211:
> >> World regulatory domain updated:May 29 17:09:48 rf kernel: [
> >> 7016.323875] cfg80211:     (start_freq - end_freq @ bandwidth),
> >> (max_antenna_gain, max_eirp)May 29 17:09:48 rf kernel: [
> >> 7016.323988] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz),
> >> (300 mBi, 2000 mBm)May 29 17:09:48 rf kernel: [ 7016.324155]
> >> cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi,
> >> 2000 mBm)May 29 17:09:48 rf kernel: [ 7016.324269] cfg80211:
> >> (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)May 29
> >> 17:09:48 rf kernel: [ 7016.324378] cfg80211:     (5170000 KHz -
> >> 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)May 29 17:09:48 rf
> >> kernel: [ 7016.324487] cfg80211:     (5735000 KHz - 5835000 KHz @
> >> 40000 KHz), (300 mBi, 2000 mBm)May 29 17:09:48 rf kernel: [
> >> 7016.425051] usb 2-2: reset full speed USB device using ohci_hcd and
> >> address 4May 29 17:09:48 rf kernel: [ 7016.609866] zd1211rw 2-2:1.0:
> >> phy0May 29 17:09:48 rf kernel: [ 7016.612213] usbcore: registered
> >> new interface driver zd1211rwMay 29 17:09:49 rf kernel: [
> >> 7017.026556] udev[8907]: renamed network interface wlan%d to
> >> wlan0May 29 17:09:49 rf kernel: [ 7017.498004] cfg80211: Calling
> >> CRDA for country: AUMay 29 17:09:49 rf kernel: [ 7017.539227]
> >> cfg80211: Regulatory domain changed to country: AUMay 29 17:09:49 rf
> >> kernel: [ 7017.539299] cfg80211:     (start_freq - end_freq @
> >> bandwidth), (max_antenna_gain, max_eirp)May 29 17:09:49 rf kernel: [
> >> 7017.539410] cfg80211:     (2402000 KHz - 2482000 KHz @ 40000 KHz),
> >> (N/A, 2000 mBm)May 29 17:09:49 rf kernel: [ 7017.539519] cfg80211:
> >>   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)May 29
> >> 17:09:49 rf kernel: [ 7017.539627] cfg80211:     (5250000 KHz -
> >> 5330000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)May 29 17:09:49 rf
> >> kernel: [ 7017.539736] cfg80211:     (5735000 KHz - 5835000 KHz @
> >> 40000 KHz), (300 mBi, 3000 mBm)May 29 17:09:50 rf kernel: [
> >> 7018.020584] ohci_hcd 0000:00:03.0: leak ed cb972100 (#04) state
> >> 2May 29 17:09:57 rf kernel: [ 7025.061672] usb 2-2: USB control
> >> request for firmware upload failed. Error number -110May 29 17:09:57
> >> rf kernel: [ 7025.061794] usb 2-2: Could not upload firmware code
> >> uph. Error number -110May 29 17:09:57 rf kernel: [ 7025.061872]
> >> zd1211rw 2-2:1.0: couldn't load firmware. Error number -110
> >>
> >>
> >> There are no other usb device plugged into this pc to cause a
> >> conflict:[root@rf ~]# lsusbBus 004 Device 001: ID 1d6b:0001 Linux
> >> Foundation 1.1 root hubBus 003 Device 001: ID 1d6b:0001 Linux
> >> Foundation 1.1 root hubBus 002 Device 005: ID 07b8:6001 D-Link Corp.
> >> 802.11bgBus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root
> >> hubBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> >> I know I am pushing usb to its limits using a 10 meter UTP cable,
> >> but I'm still curious as to why one driver works fine, and another
> >> driver fails?
> >>
> >> Thanks for any help/tips/ideas etc.
> >> Regards,
> >> Rohan.
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
> >
> > ------------------------------------------------------------------------------
> > vRanger cuts backup time in half-while increasing security.
> > With the market-leading solution for virtual backup and recovery,
> > you get blazing-fast, flexible, and affordable data protection.
> > Download your free trial now.
> > http://p.sf.net/sfu/quest-d2dcopy1
> > _______________________________________________
> > Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
> > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
> >
> >
> 
> 
 		 	   		  

Re: [zd1211-devs] firmware timeout issues (error -110)

[Jussi K. <jus...@mb...>]

Hello!

This is interesting bug. The device actually presents itself  
differently to host depending if it's running either USB 1.1 or 2.0.  
As I tested zd1211rw AP-mode only on USB 2.0, result was that zd1211rw  
expected to always see device as it seen on USB 2.0. On OHCI-host this  
triggers error in ohci_hcd when driver tries to communicate to device  
(and correct error message appears only with zd1211rw debugging  
enabled).

Patch attached fixes the problem.

You can get patched compat-wireless tarball from:
   
http://koti.mbnet.fi/axh/kernel/zd1211rw/compat-wireless-2011-05-28-zd1211rw_fix.tar.bz2

-Jussi

Quoting Jussi Kivilinna <jus...@mb...>:

> Hi,
>
> I have reproduced the bug, happens only on ohci_hci (not ehci or
> uchi). I'll start working on fix.
>
> -Jussi
>
> Quoting "Roh ." <ro...@ho...>:
>
>>
>> Hi Devs,
>> I hope someone can shed some light on why I am seeing these errors.
>> When using the standard zd1211rw, mac802111 & cfg80211 drivers that
>> come with fedora 14 (2.6.35.13-91) i am able to run my zd1211-based
>> device perfectly without a glitch over a 10m UTP usb extension. I
>> can even run airodump-ng for days on end without a glitch (of course
>> no packet injection or signal level feedback).
>> However when I try to use the compat-wireless-2011-05-26 or
>> compat-wireless-2011-04-22 drivers I receive firmware timeout
>> errors. Please see /var/log/message output below:
>> Using stock Fedora 14 2.6.35.13-91 drivers: (works ok)
>> May 29 17:14:28 rf kernel: [ 7296.240037] usb 2-2: new full speed
>> USB device using ohci_hcd and address 5May 29 17:14:28 rf kernel: [
>> 7296.417134] usb 2-2: not running at top speed; connect to a high
>> speed hubMay 29 17:14:28 rf kernel: [ 7296.432140] usb 2-2: New USB
>> device found, idVendor=07b8, idProduct=6001May 29 17:14:28 rf
>> kernel: [ 7296.432213] usb 2-2: New USB device strings: Mfr=16,
>> Product=32, SerialNumber=0May 29 17:14:28 rf kernel: [ 7296.432322]
>> usb 2-2: Product: USB2.0 WLANMay 29 17:14:28 rf kernel: [
>> 7296.432379] usb 2-2: Manufacturer: wug2670May 29 17:14:29 rf
>> kernel: [ 7296.738492] cfg80211: Calling CRDA to update world
>> regulatory domainMay 29 17:14:29 rf kernel: [ 7296.995070] usb 2-2:
>> reset full speed USB device using ohci_hcd and address 5May 29
>> 17:14:29 rf kernel: [ 7297.010274] cfg80211: World regulatory domain
>> updated:May 29 17:14:29 rf kernel: [ 7297.010346]     (start_freq -
>> end_freq @ bandwidth), (max_antenna_gain, max_eirp)May 29 17:14:29
>> rf kernel: [ 7297.010457]     (2402000 KHz - 2472000 KHz @ 40000
>> KHz), (300 mBi, 2000 mBm)May 29 17:14:29 rf kernel: [ 7297.010519]
>>   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)May 29
>> 17:14:29 rf kernel: [ 7297.010583]     (2474000 KHz - 2494000 KHz @
>> 20000 KHz), (300 mBi, 2000 mBm)May 29 17:14:29 rf kernel: [
>> 7297.010646]     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi,
>> 2000 mBm)May 29 17:14:29 rf kernel: [ 7297.010709]     (5735000 KHz
>> - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)May 29 17:14:29 rf
>> kernel: [ 7297.235267] zd1211rw 2-2:1.0: phy0May 29 17:14:29 rf
>> kernel: [ 7297.235405] usbcore: registered new interface driver
>> zd1211rwMay 29 17:14:30 rf kernel: [ 7297.977792] cfg80211: Calling
>> CRDA for country: AUMay 29 17:14:30 rf kernel: [ 7297.999546]
>> cfg80211: Regulatory domain changed to country: AUMay 29 17:14:30 rf
>> kernel: [ 7297.999619]     (start_freq - end_freq @ bandwidth),
>> (max_antenna_gain, max_eirp)May 29 17:14:30 rf kernel: [
>> 7297.999727]     (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000
>> mBm)May 29 17:14:30 rf kernel: [ 7297.999789]     (5170000 KHz -
>> 5250000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)May 29 17:14:30 rf
>> kernel: [ 7297.999852]     (5250000 KHz - 5330000 KHz @ 40000 KHz),
>> (300 mBi, 2300 mBm)May 29 17:14:30 rf kernel: [ 7297.999914]
>> (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)May 29
>> 17:14:31 rf kernel: [ 7298.945539] zd1211rw 2-2:1.0: firmware
>> version 4605May 29 17:14:31 rf kernel: [ 7299.005554] zd1211rw
>> 2-2:1.0: zd1211 chip 07b8:6001 v4330 full 00-12-0e AL2230_RF pa0
>> g----May 29 17:14:31 rf kernel: [ 7299.010584] cfg80211: Calling
>> CRDA for country: DEMay 29 17:14:31 rf kernel: [ 7299.026125]
>> cfg80211: Current regulatory domain intersected:May 29 17:14:31 rf
>> kernel: [ 7299.026198]     (start_freq - end_freq @ bandwidth),
>> (max_antenna_gain, max_eirp)May 29 17:14:31 rf kernel: [
>> 7299.026309]     (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000
>> mBm)May 29 17:14:31 rf kernel: [ 7299.026371]     (5170000 KHz -
>> 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)May 29 17:14:31 rf kernel:
>> [ 7299.026431]     (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A,
>> 2000 mBm)May 29 17:14:31 rf kernel: [ 7299.071672]
>> ADDRCONF(NETDEV_UP): wlan0: link is not ready
>> Using compat-wireless-2011-04-22 (firmware upload fails):
>> May 29 17:09:47 rf kernel: [ 7015.122044] usb 2-2: new full speed
>> USB device using ohci_hcd and address 4May 29 17:09:47 rf kernel: [
>> 7015.299130] usb 2-2: not running at top speed; connect to a high
>> speed hubMay 29 17:09:47 rf kernel: [ 7015.314138] usb 2-2: New USB
>> device found, idVendor=07b8, idProduct=6001May 29 17:09:47 rf
>> kernel: [ 7015.314210] usb 2-2: New USB device strings: Mfr=16,
>> Product=32, SerialNumber=0May 29 17:09:47 rf kernel: [ 7015.314317]
>> usb 2-2: Product: USB2.0 WLANMay 29 17:09:47 rf kernel: [
>> 7015.314374] usb 2-2: Manufacturer: wug2670May 29 17:09:48 rf
>> kernel: [ 7015.784541] cfg80211: Calling CRDA to update world
>> regulatory domainMay 29 17:09:48 rf kernel: [ 7016.323803] cfg80211:
>> World regulatory domain updated:May 29 17:09:48 rf kernel: [
>> 7016.323875] cfg80211:     (start_freq - end_freq @ bandwidth),
>> (max_antenna_gain, max_eirp)May 29 17:09:48 rf kernel: [
>> 7016.323988] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz),
>> (300 mBi, 2000 mBm)May 29 17:09:48 rf kernel: [ 7016.324155]
>> cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi,
>> 2000 mBm)May 29 17:09:48 rf kernel: [ 7016.324269] cfg80211:
>> (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)May 29
>> 17:09:48 rf kernel: [ 7016.324378] cfg80211:     (5170000 KHz -
>> 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)May 29 17:09:48 rf
>> kernel: [ 7016.324487] cfg80211:     (5735000 KHz - 5835000 KHz @
>> 40000 KHz), (300 mBi, 2000 mBm)May 29 17:09:48 rf kernel: [
>> 7016.425051] usb 2-2: reset full speed USB device using ohci_hcd and
>> address 4May 29 17:09:48 rf kernel: [ 7016.609866] zd1211rw 2-2:1.0:
>> phy0May 29 17:09:48 rf kernel: [ 7016.612213] usbcore: registered
>> new interface driver zd1211rwMay 29 17:09:49 rf kernel: [
>> 7017.026556] udev[8907]: renamed network interface wlan%d to
>> wlan0May 29 17:09:49 rf kernel: [ 7017.498004] cfg80211: Calling
>> CRDA for country: AUMay 29 17:09:49 rf kernel: [ 7017.539227]
>> cfg80211: Regulatory domain changed to country: AUMay 29 17:09:49 rf
>> kernel: [ 7017.539299] cfg80211:     (start_freq - end_freq @
>> bandwidth), (max_antenna_gain, max_eirp)May 29 17:09:49 rf kernel: [
>> 7017.539410] cfg80211:     (2402000 KHz - 2482000 KHz @ 40000 KHz),
>> (N/A, 2000 mBm)May 29 17:09:49 rf kernel: [ 7017.539519] cfg80211:
>>   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)May 29
>> 17:09:49 rf kernel: [ 7017.539627] cfg80211:     (5250000 KHz -
>> 5330000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)May 29 17:09:49 rf
>> kernel: [ 7017.539736] cfg80211:     (5735000 KHz - 5835000 KHz @
>> 40000 KHz), (300 mBi, 3000 mBm)May 29 17:09:50 rf kernel: [
>> 7018.020584] ohci_hcd 0000:00:03.0: leak ed cb972100 (#04) state
>> 2May 29 17:09:57 rf kernel: [ 7025.061672] usb 2-2: USB control
>> request for firmware upload failed. Error number -110May 29 17:09:57
>> rf kernel: [ 7025.061794] usb 2-2: Could not upload firmware code
>> uph. Error number -110May 29 17:09:57 rf kernel: [ 7025.061872]
>> zd1211rw 2-2:1.0: couldn't load firmware. Error number -110
>>
>>
>> There are no other usb device plugged into this pc to cause a
>> conflict:[root@rf ~]# lsusbBus 004 Device 001: ID 1d6b:0001 Linux
>> Foundation 1.1 root hubBus 003 Device 001: ID 1d6b:0001 Linux
>> Foundation 1.1 root hubBus 002 Device 005: ID 07b8:6001 D-Link Corp.
>> 802.11bgBus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root
>> hubBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> I know I am pushing usb to its limits using a 10 meter UTP cable,
>> but I'm still curious as to why one driver works fine, and another
>> driver fails?
>>
>> Thanks for any help/tips/ideas etc.
>> Regards,
>> Rohan.
>>
>>
>>
>>
>>
>
>
>
>
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery,
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now.
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
>
>