zd1211-devs Mailing List for ZD1211 USB WLAN Linux Driver (Page 2)
Status: Beta
Brought to you by:
mayne
You can subscribe to this list here.
2005 |
Jan
(1) |
Feb
(36) |
Mar
(237) |
Apr
(45) |
May
(97) |
Jun
(60) |
Jul
(66) |
Aug
(149) |
Sep
(75) |
Oct
(55) |
Nov
(43) |
Dec
(111) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(104) |
Feb
(102) |
Mar
(102) |
Apr
(137) |
May
(113) |
Jun
(100) |
Jul
(77) |
Aug
(72) |
Sep
(77) |
Oct
(101) |
Nov
(98) |
Dec
(141) |
2007 |
Jan
(105) |
Feb
(86) |
Mar
(47) |
Apr
(54) |
May
(90) |
Jun
(54) |
Jul
(47) |
Aug
(52) |
Sep
(24) |
Oct
(23) |
Nov
(25) |
Dec
(27) |
2008 |
Jan
(8) |
Feb
(9) |
Mar
(13) |
Apr
(4) |
May
(12) |
Jun
(5) |
Jul
(21) |
Aug
(4) |
Sep
(3) |
Oct
(11) |
Nov
(6) |
Dec
(17) |
2009 |
Jan
(17) |
Feb
(23) |
Mar
(6) |
Apr
(6) |
May
(1) |
Jun
(7) |
Jul
(12) |
Aug
(8) |
Sep
|
Oct
(5) |
Nov
(15) |
Dec
(21) |
2010 |
Jan
(27) |
Feb
(33) |
Mar
(6) |
Apr
(7) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(9) |
Nov
|
Dec
|
2011 |
Jan
(1) |
Feb
(1) |
Mar
(4) |
Apr
|
May
(15) |
Jun
(4) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
(9) |
Dec
|
2012 |
Jan
(2) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Jussi K. <jus...@mb...> - 2011-05-29 10:09:25
|
Hello, Have you tried without the cable? Can you compile compat-wireless with CONFIG_ZD1211RW_DEBUG=y enabled, for more output from driver? (edit compat-wireless-[version]/config.mk, take out "# " from line with "CONFIG_ZD1211RW_DEBUG=y" and recompile) -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 5 > May 29 17:14:28 rf kernel: [ 7296.417134] usb 2-2: not running at > top speed; connect to a high speed hub > May 29 17:14:28 rf kernel: [ 7296.432140] usb 2-2: New USB device > found, idVendor=07b8, idProduct=6001 > May 29 17:14:28 rf kernel: [ 7296.432213] usb 2-2: New USB device > strings: Mfr=16, Product=32, SerialNumber=0 > May 29 17:14:28 rf kernel: [ 7296.432322] usb 2-2: Product: USB2.0 WLAN > May 29 17:14:28 rf kernel: [ 7296.432379] usb 2-2: Manufacturer: wug2670 > May 29 17:14:29 rf kernel: [ 7296.738492] cfg80211: Calling CRDA to > update world regulatory domain > May 29 17:14:29 rf kernel: [ 7296.995070] usb 2-2: reset full speed > USB device using ohci_hcd and address 5 > May 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: phy0 > May 29 17:14:29 rf kernel: [ 7297.235405] usbcore: registered new > interface driver zd1211rw > May 29 17:14:30 rf kernel: [ 7297.977792] cfg80211: Calling CRDA for > country: AU > May 29 17:14:30 rf kernel: [ 7297.999546] cfg80211: Regulatory > domain changed to country: AU > May 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 4605 > May 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: DE > May 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 4 > May 29 17:09:47 rf kernel: [ 7015.299130] usb 2-2: not running at > top speed; connect to a high speed hub > May 29 17:09:47 rf kernel: [ 7015.314138] usb 2-2: New USB device > found, idVendor=07b8, idProduct=6001 > May 29 17:09:47 rf kernel: [ 7015.314210] usb 2-2: New USB device > strings: Mfr=16, Product=32, SerialNumber=0 > May 29 17:09:47 rf kernel: [ 7015.314317] usb 2-2: Product: USB2.0 WLAN > May 29 17:09:47 rf kernel: [ 7015.314374] usb 2-2: Manufacturer: wug2670 > May 29 17:09:48 rf kernel: [ 7015.784541] cfg80211: Calling CRDA to > update world regulatory domain > May 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 4 > May 29 17:09:48 rf kernel: [ 7016.609866] zd1211rw 2-2:1.0: phy0 > May 29 17:09:48 rf kernel: [ 7016.612213] usbcore: registered new > interface driver zd1211rw > May 29 17:09:49 rf kernel: [ 7017.026556] udev[8907]: renamed > network interface wlan%d to wlan0 > May 29 17:09:49 rf kernel: [ 7017.498004] cfg80211: Calling CRDA for > country: AU > May 29 17:09:49 rf kernel: [ 7017.539227] cfg80211: Regulatory > domain changed to country: AU > May 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 2 > May 29 17:09:57 rf kernel: [ 7025.061672] usb 2-2: USB control > request for firmware upload failed. Error number -110 > May 29 17:09:57 rf kernel: [ 7025.061794] usb 2-2: Could not upload > firmware code uph. Error number -110 > May 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 ~]# lsusb > > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 002 Device 005: ID 07b8:6001 D-Link Corp. 802.11bg > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 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. |
From: Jussi K. <jus...@mb...> - 2011-05-29 10:06:38
|
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. > > > > > |
From: Roh . <ro...@ho...> - 2011-05-29 08:27:47
|
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. |
From: Hin-Tak L. <hin...@ya...> - 2011-05-13 17:42:31
|
Michael Tokarev wrote: > 13.05.2011 14:22, Hin-Tak Leung wrote: >> ownership of the firmware files (and the containing directories)? > > The firmware loading is done from a root process, so permissions > are largely irrelevant. Especially with this error number > (-2 = ENOENT No such file or directory). That does not appear the case, as I seem to recall (I could be wrong)? i.e. The files could be readable by root but not by the firmware-loading process/thread. >> Krzysztof Stankiewicz wrote: >>> Im developing on LPC3250 NPX Embedded system, Ive placed the firmawere >>> where instructed, >>> and I keep getting this error no matter what I do? >>> Ive gone as far ast tracing the kernel stack but makes no sense to me.. >>> can anyone help? >>> >>> usb 1-1: Could not load firmware file zd1211/zd1211b_ub. Error number -2 >>> zd1211rw 1-1:1.0: couldn't load firmware. Error number -2 > > This looks like the system can't run the firmware loader, > ie, it can't start /sbin/hotplug or whatever is configured > in /proc/sys/kernel/hotplug. You need udev or hotplug package > or a simple script for /sbin/hotplug. > > The file should be in /lib/firmware/zd1211/zd1211b_ub. > > /mjt > |
From: <zd1...@ku...> - 2011-05-13 11:15:49
|
if you do an strace on ifconfig as it is bringing the interface up you will see the device that the driver is looking for to load the firmware and not finding. i am not that expert to know what it is , but i have found a way around the problem for all drivers that have this firmware loading problem, and that is to use the facility available to compile the firmware "blob" directly into the kernel. put the firmware in the subdirectory of the kernel tree named firmware and then go into the kernel configuration(Device drivers/Generic Driver Options/Include in-kernel firmware blobs in kernel binary) and list their names there. it seems customary to put them in a subdir in exactly the same way as in the /lib/firmware dir and then list the path/name (eg zd1211/zd1211b_ub) in the config option. recompile the kernel. no more firmware problems. fractoid On Fri, May 13, 2011 at 06:28:42PM +1000, Krzysztof Stankiewicz wrote: > > Im developing on LPC3250 NPX Embedded system, Ive placed the firmawere where instructed, > and I keep getting this error no matter what I do? > Ive gone as far ast tracing the kernel stack but makes no sense to me.. can anyone help? > > > usb 1-1: Could not load firmware file zd1211/zd1211b_ub. Error number -2 > zd1211rw 1-1:1.0: couldn't load firmware. Error number -2 > ifconfig: SIOCSIFFLAGS: No such file or directory > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/ > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs |
From: <zd1...@ku...> - 2011-05-13 10:58:36
|
if you do an strace on ifconfig as it is bringing the interface up you will see the device that the driver is looking for to load the firmware and not finding. i am not that expert to know what it is , but i have found a way around the problem for all drivers that have this firmware loading problem, and that is to use the facility available to compile the firmware "blob" directly into the kernel. put the firmware in the subdirectory of the kernel tree named firmware and then go into the kernel configuration(Device drivers/Generic Driver Options/Include in-kernel firmware blobs in kernel binary) and list their names there. it seems customary to put them in a subdir in exactly the same way as in the /lib/firmware dir and then list the path/name (eg zd1211/zd1211b_ub) in the config option. recompile the kernel. no more firmware problems. fractoid On Fri, May 13, 2011 at 06:28:42PM +1000, Krzysztof Stankiewicz wrote: > > Im developing on LPC3250 NPX Embedded system, Ive placed the firmawere where instructed, > and I keep getting this error no matter what I do? > Ive gone as far ast tracing the kernel stack but makes no sense to me.. can anyone help? > > > usb 1-1: Could not load firmware file zd1211/zd1211b_ub. Error number -2 > zd1211rw 1-1:1.0: couldn't load firmware. Error number -2 > ifconfig: SIOCSIFFLAGS: No such file or directory > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/ > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs |
From: Michael T. <mj...@tl...> - 2011-05-13 10:37:49
|
13.05.2011 14:22, Hin-Tak Leung wrote: > ownership of the firmware files (and the containing directories)? The firmware loading is done from a root process, so permissions are largely irrelevant. Especially with this error number (-2 = ENOENT No such file or directory). > Krzysztof Stankiewicz wrote: >> Im developing on LPC3250 NPX Embedded system, Ive placed the firmawere >> where instructed, >> and I keep getting this error no matter what I do? >> Ive gone as far ast tracing the kernel stack but makes no sense to me.. >> can anyone help? >> >> usb 1-1: Could not load firmware file zd1211/zd1211b_ub. Error number -2 >> zd1211rw 1-1:1.0: couldn't load firmware. Error number -2 This looks like the system can't run the firmware loader, ie, it can't start /sbin/hotplug or whatever is configured in /proc/sys/kernel/hotplug. You need udev or hotplug package or a simple script for /sbin/hotplug. The file should be in /lib/firmware/zd1211/zd1211b_ub. /mjt |
From: Hin-Tak L. <hin...@ya...> - 2011-05-13 10:22:32
|
ownership of the firmware files (and the containing directories)? Krzysztof Stankiewicz wrote: > Im developing on LPC3250 NPX Embedded system, Ive placed the firmawere > where instructed, > and I keep getting this error no matter what I do? > Ive gone as far ast tracing the kernel stack but makes no sense to me.. > can anyone help? > > > usb 1-1: Could not load firmware file zd1211/zd1211b_ub. Error number -2 > zd1211rw 1-1:1.0: couldn't load firmware. Error number -2 > ifconfig: SIOCSIFFLAGS: No such file or directory |
From: Krzysztof S. <krz...@ho...> - 2011-05-13 08:28:48
|
Im developing on LPC3250 NPX Embedded system, Ive placed the firmawere where instructed, and I keep getting this error no matter what I do? Ive gone as far ast tracing the kernel stack but makes no sense to me.. can anyone help? usb 1-1: Could not load firmware file zd1211/zd1211b_ub. Error number -2 zd1211rw 1-1:1.0: couldn't load firmware. Error number -2 ifconfig: SIOCSIFFLAGS: No such file or directory |
From: Hin-Tak L. <hin...@ya...> - 2011-05-12 16:10:10
|
Nerijus Baliunas wrote: > What are standard instructions? It works with hostapd here... Perhaps I should say the patch looks incomplete, because I have seen the "official" change I mentioned below, and it is more than just two lines. >> in any case, the "official" change has >> already happened - once something is in the wireless-testing branch of the >> kernel, it is just a matter of time before it reaches Linus himself. The process >> usually takes a few months between a change appearing in wireless testing to it >> appearing in the official release. > > Great. You wrote the patch was for 2.6.35.10, and my old message was about it entering the wireless-testing branch after 2.6.38 (and before the 2.6.39 merge windows, I think). I just checked that 2.6.39 is in rc7 now, so you probably just need to wait a week or two - and to be sure about it, read the changelog on www.kernel.org. |
From: Nerijus B. <ne...@us...> - 2011-05-12 12:30:15
|
On Thu, 12 May 2011 08:58:31 +0100 Hin-Tak Leung <hin...@ya...> wrote: > > There is a patch at http://ankalagon.ru/notes/patch-na-zd1211rw which adds AP > > mode in a very simple way, and it actually works! I had to modify the first > > hunk slightly for kernel 2.6.38, modified patch below: > > It looks like a non-standard(ugly?) hack though, and not likely to work with > standard linux AP-setup instruction... What are standard instructions? It works with hostapd here... > in any case, the "official" change has > already happened - once something is in the wireless-testing branch of the > kernel, it is just a matter of time before it reaches Linus himself. The process > usually takes a few months between a change appearing in wireless testing to it > appearing in the official release. Great. Regards, Nerijus |
From: Hin-Tak L. <hin...@ya...> - 2011-05-12 07:58:44
|
Nerijus Baliunas wrote: > On Wed, 16 Feb 2011 01:28:19 +0000 (GMT) Hin-Tak Leung > <ht...@us...> wrote: > >> I use it mainly for the AP mode, on an old machine that has just been >> resurrected after over a year, so the last it worked was on 2.6.31.x . >> There are a couple of old and new quirks: a dozen of 'We are trapped in >> zd_SigProcess, Going to release all,id=3,block=1' is new to 2.6.35.x, but >> the driver has always needed if down/up and or iwlist scan before a client >> station can connect, and that's still the case; and under extended use (a >> few days, and/or a few GB traffic) it can still bring the AP machine down. >> >> I see some great person has just had a whole bunch of patches committed to >> wireless-testing in the last few months for enabling AP mode for the >> in-kernel zd1211rw driver... so 2.6.39(?) or thereabout it would be >> generally available...so the use of the vendor driver for AP mode would >> soon not be needed any more. I'd probably give the compat-wireless a try >> soon enough. > > There is a patch at http://ankalagon.ru/notes/patch-na-zd1211rw which adds AP > mode in a very simple way, and it actually works! I had to modify the first > hunk slightly for kernel 2.6.38, modified patch below: It looks like a non-standard(ugly?) hack though, and not likely to work with standard linux AP-setup instruction... in any case, the "official" change has already happened - once something is in the wireless-testing branch of the kernel, it is just a matter of time before it reaches Linus himself. The process usually takes a few months between a change appearing in wireless testing to it appearing in the official release. |
From: Nerijus B. <ne...@us...> - 2011-05-11 19:01:32
|
On Wed, 16 Feb 2011 01:28:19 +0000 (GMT) Hin-Tak Leung <ht...@us...> wrote: > I use it mainly for the AP mode, on an old machine that has just been resurrected after over a year, so the last it worked was on 2.6.31.x . There are a couple of old and new quirks: a dozen of 'We are trapped in zd_SigProcess, Going to release all,id=3,block=1' is new to 2.6.35.x, but the driver has always needed if down/up and or iwlist scan before a client station can connect, and that's still the case; and under extended use (a few days, and/or a few GB traffic) it can still bring the AP machine down. > > I see some great person has just had a whole bunch of patches committed to wireless-testing in the last few months for enabling AP mode for the in-kernel zd1211rw driver... so 2.6.39(?) or thereabout it would be generally available...so the use of the vendor driver for AP mode would soon not be needed any more. I'd probably give the compat-wireless a try soon enough. There is a patch at http://ankalagon.ru/notes/patch-na-zd1211rw which adds AP mode in a very simple way, and it actually works! I had to modify the first hunk slightly for kernel 2.6.38, modified patch below: --- a/drivers/net/wireless/zd1211rw/zd_mac.c 2009-08-17 01:19:38.000000000 +0400 +++ b/drivers/net/wireless/zd1211rw/zd_mac.c 2009-08-22 21:05:06.268498867 +0400 @@ -882,6 +882,7 @@ case NL80211_IFTYPE_MESH_POINT: case NL80211_IFTYPE_STATION: case NL80211_IFTYPE_ADHOC: + case NL80211_IFTYPE_AP: mac->type = vif->type; break; default: @@ -1046,6 +1047,7 @@ dev_dbg_f(zd_mac_dev(mac), "changes: %x\n", changes); if (mac->type == NL80211_IFTYPE_MESH_POINT || + mac->type == NL80211_IFTYPE_AP || mac->type == NL80211_IFTYPE_ADHOC) { associated = true; if (changes & BSS_CHANGED_BEACON) { @@ -1143,6 +1145,7 @@ hw->wiphy->interface_modes = BIT(NL80211_IFTYPE_MESH_POINT) | BIT(NL80211_IFTYPE_STATION) | + BIT(NL80211_IFTYPE_AP) | BIT(NL80211_IFTYPE_ADHOC); hw->max_signal = 100; Regards, Nerijus |
From: yacc <fea...@ya...> - 2011-03-31 16:04:13
|
It seems your receving stops after first strike. Maybe you can print message in any error codition in zd1211_submit_rx_urb() Also, you can check the fileds used in usb_fill_bulk_urb() to see if any abnormal value. If you want to check the rx function, you can just print something and call zd1211_submit_rx_urb(macp) at very begining of zd1211_rx_comp_cb(). Dear Nazim and experts, I have updated the patches #2, #5, #6, #7, #8, #9, #12, #13 found in http://www.reactivated.net/software/zd1211-vendor/. But ZyDas 1211b still doesn't work for me. Following is the dmesg output. (I didn't update patch #1, #3, #4, #10, #11, #14 because the version of my linux kernel is 2.6.14. Updating these patch will result in compile errors.) |__ / _| _ \ / \ / ___| / / | | | | | |/ _ \ \___ \ / /| |_| | |_| / ___ \ ___) | /____\__, |____/_/ \_\____/ |___/ ZD1211B - version 3.0.0.56 vendor_id = 0ace product_id = 1215 USB 2.0 Host Release Ver = 4810 EEPORM Ver = 4810 Finsih download Firmware. Ready to reboot PA type: 0 AR2124 RF [zd1205_set_zd_cbs, 11919] pObj->bChScanning is 0 AllowedChannel = 00011fff Region:48 usbcore: registered new driver zd1211b / # cp /mnt/nfs/wireless_tools.29/target/* / -rf / # cd /mnt/nfs /mnt/nfs # ifconfig ath0 up [zd1205_open, 4911] calling zd1211_submit_rx_urb() [zd1211_submit_rx_urb, 2766] started [zd1211_submit_rx_urb, 2791] calling usb_fill_bulk_urb() [zd1211_submit_rx_urb, 2809] ended [zd1211_rx_comp_cb, 2370] started [zd1211_rx_comp_cb, 2483] calling zd1211_rx_isr() [zd1211_rx_isr, 2213] started [zd1211_rx_isr, 2314] calling zd1211_submit_rx_urb() [zd1211_submit_rx_urb, 2766] started [zd1211_submit_rx_urb, 2791] calling usb_fill_bulk_urb() [zd1211_submit_rx_urb, 2809] ended [zd1211_rx_isr, 2331] calling zd1205_rx_isr() [zd1205_rx_isr, 3821] started [zd1205_rx_isr, 4575] ended [zd1211_rx_isr, 2348] ended [zd1211_rx_comp_cb, 2489] ended [zd_ConnectMon, 2817] [zd_CmdProbeReq, 961] pdot11Obj->bChScanning is 1 [zd_CmdProbeReq, 976] mMacMode: 1, CurrScanCH: 1 [zd_CmdProbeReq, 977] HZ: 1000, region: 48 /mnt/nfs [zdcb_start_timer, 11653] scan expire time: -194315 # header part data [24]: 40 20 60 27 ff ff ff ff ff ff 00 12 cf f4 11 38 ff ff ff ff ff ff 10 07 data part data [14]: -- View this message in context: http://old.nabble.com/No-packet-received-by-ZyDas-1211B-tp31253914p31287088.html Sent from the zd1211-devs mailing list archive at Nabble.com. |
From: 李文星 <wen...@gm...> - 2011-03-31 07:52:52
|
Dear Nazim and experts, I have updated the patches #2, #5, #6, #7, #8, #9, #12, #13 found in http://www.reactivated.net/software/zd1211-vendor/. But ZyDas 1211b still doesn't work for me. Following is the dmesg output. (I didn't update patch #1, #3, #4, #10, #11, #14 because the version of my linux kernel is 2.6.14. Updating these patch will result in compile errors.) |__ / _| _ \ / \ / ___| / / | | | | | |/ _ \ \___ \ / /| |_| | |_| / ___ \ ___) | /____\__, |____/_/ \_\____/ |___/ ZD1211B - version 3.0.0.56 vendor_id = 0ace product_id = 1215 USB 2.0 Host Release Ver = 4810 EEPORM Ver = 4810 Finsih download Firmware. Ready to reboot PA type: 0 AR2124 RF [zd1205_set_zd_cbs, 11919] pObj->bChScanning is 0 AllowedChannel = 00011fff Region:48 usbcore: registered new driver zd1211b / # cp /mnt/nfs/wireless_tools.29/target/* / -rf / # cd /mnt/nfs /mnt/nfs # ifconfig ath0 up [zd1205_open, 4911] calling zd1211_submit_rx_urb() [zd1211_submit_rx_urb, 2766] started [zd1211_submit_rx_urb, 2791] calling usb_fill_bulk_urb() [zd1211_submit_rx_urb, 2809] ended [zd1211_rx_comp_cb, 2370] started [zd1211_rx_comp_cb, 2483] calling zd1211_rx_isr() [zd1211_rx_isr, 2213] started [zd1211_rx_isr, 2314] calling zd1211_submit_rx_urb() [zd1211_submit_rx_urb, 2766] started [zd1211_submit_rx_urb, 2791] calling usb_fill_bulk_urb() [zd1211_submit_rx_urb, 2809] ended [zd1211_rx_isr, 2331] calling zd1205_rx_isr() [zd1205_rx_isr, 3821] started [zd1205_rx_isr, 4575] ended [zd1211_rx_isr, 2348] ended [zd1211_rx_comp_cb, 2489] ended [zd_ConnectMon, 2817] [zd_CmdProbeReq, 961] pdot11Obj->bChScanning is 1 [zd_CmdProbeReq, 976] mMacMode: 1, CurrScanCH: 1 [zd_CmdProbeReq, 977] HZ: 1000, region: 48 /mnt/nfs [zdcb_start_timer, 11653] scan expire time: -194315 # header part data [24]: 40 20 60 27 ff ff ff ff ff ff 00 12 cf f4 11 38 ff ff ff ff ff ff 10 07 data part data [14]: 00 00 01 04 82 84 8b 96 32 08 0c 12 18 60 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [zd_CmdProbeReq, 991] zd_ProbeReq() result is 1 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 1 --> 2 [zdcb_start_timer, 11653] scan expire time: -194180 header part data [24]: 40 20 00 00 ff ff ff ff ff ff 00 12 cf f4 11 38 ff ff ff ff ff ff 10 07 data part data [14]: 00 00 01 04 82 84 8b 96 32 08 0c 12 18 60 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 2 --> 3 [zdcb_start_timer, 11653] scan expire time: -194044 header part data [24]: 40 20 00 00 ff ff ff ff ff ff 00 12 cf f4 11 38 ff ff ff ff ff ff 10 07 data part data [14]: 00 00 01 04 82 84 8b 96 32 08 0c 12 18 60 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 3 --> 4 [zdcb_start_timer, 11653] scan expire time: -193908 header part data [24]: 40 20 00 00 ff ff ff ff ff ff 00 12 cf f4 11 38 ff ff ff ff ff ff 10 07 data part data [14]: 00 00 01 04 82 84 8b 96 32 08 0c 12 18 60 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 4 --> 5 [zdcb_start_timer, 11653] scan expire time: -193772 header part data [24]: 40 20 00 00 ff ff ff ff ff ff 00 12 cf f4 11 38 ff ff ff ff ff ff 10 07 data part data [14]: 00 00 01 04 82 84 8b 96 32 08 0c 12 18 60 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 5 --> 6 [zdcb_start_timer, 11653] scan expire time: -193635 header part data [24]: 40 20 00 00 ff ff ff ff ff ff 00 12 cf f4 11 38 ff ff ff ff ff ff 10 07 data part data [14]: 00 00 01 04 82 84 8b 96 32 08 0c 12 18 60 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 6 --> 7 [zdcb_start_timer, 11653] scan expire time: -193499 header part data [24]: 40 20 00 00 ff ff ff ff ff ff 00 12 cf f4 11 38 ff ff ff ff ff ff 10 07 data part data [14]: 00 00 01 04 82 84 8b 96 32 08 0c 12 18 60 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 7 --> 8 [zdcb_start_timer, 11653] scan expire time: -193363 header part data [24]: 40 20 00 00 ff ff ff ff ff ff 00 12 cf f4 11 38 ff ff ff ff ff ff 10 07 data part data [14]: 00 00 01 04 82 84 8b 96 32 08 0c 12 18 60 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 8 --> 9 [zdcb_start_timer, 11653] scan expire time: -193227 header part data [24]: 40 20 00 00 ff ff ff ff ff ff 00 12 cf f4 11 38 ff ff ff ff ff ff 10 07 data part data [14]: 00 00 01 04 82 84 8b 96 32 08 0c 12 18 60 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 9 --> 10 [zdcb_start_timer, 11653] scan expire time: -193089 header part data [24]: 40 20 00 00 ff ff ff ff ff ff 00 12 cf f4 11 38 ff ff ff ff ff ff 10 07 data part data [14]: 00 00 01 04 82 84 8b 96 32 08 0c 12 18 60 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 10 --> 11 [zdcb_start_timer, 11653] scan expire time: -192951 header part data [24]: 40 20 00 00 ff ff ff ff ff ff 00 12 cf f4 11 38 ff ff ff ff ff ff 10 07 data part data [14]: 00 00 01 04 82 84 8b 96 32 08 0c 12 18 60 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 11 --> 12 [zdcb_start_timer, 11653] scan expire time: -192813 header part data [24]: 40 20 00 00 ff ff ff ff ff ff 00 12 cf f4 11 38 ff ff ff ff ff ff 10 07 data part data [14]: 00 00 01 04 82 84 8b 96 32 08 0c 12 18 60 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 12 --> 13 [zdcb_start_timer, 11653] scan expire time: -192675 header part data [24]: 40 20 00 00 ff ff ff ff ff ff 00 12 cf f4 11 38 ff ff ff ff ff ff 10 07 data part data [14]: 00 00 01 04 82 84 8b 96 32 08 0c 12 18 60 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 13 --> 14 [zdcb_start_timer, 11653] scan expire time: -192551 header part data [24]: 40 20 00 00 ff ff ff ff ff ff 00 12 cf f4 11 38 ff ff ff ff ff ff 10 07 data part data [14]: 00 00 01 04 82 84 8b 96 32 08 0c 12 18 60 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1875] last channel: 14 [zd_SwitchNextCH, 1878] pdot11Obj->bChScanning is 0 SSID BSSID CH Signal Mode Basic-Rates Ext-Rates b/g AP<7>zd1205: (enter) defer_kevent, /home/louis/dmr400_new/LinuxUSB/ar2524drv/src/zd1211.c line 3778 ------------------------------------------------------------------------------------ ****** Scan Finished ****** iwlist ath0 s[zd_Roaming, 2792] [zd_CmdProbeReq, 961] pdot11Obj->bChScanning is 1 [zd_CmdProbeReq, 976] mMacMode: 1, CurrScanCH: 1 [zd_CmdProbeReq, 977] HZ: 1000, region: 48 [zdcb_start_timer, 11653] scan expire time: -188485 header part data [24]: 2011/3/28 Nazim Khan <naz...@gm...> > There are some patches available for zd1211b vendor driver. > I don't have the link available but if you google, you should be able to > find it. > Browse through the history of this mailing list starting from mid 2007. > > Nazim > > 2011/3/28 李文星 <wen...@gm...> > >> Dear guys, >> I have used ZyDas on ARM platform with Linux kernel 2.6.14. The >> compilation of the source code (downloaded from >> http://www.filewatcher.com/m/LinuxUSB_AR2524-3.0.0.56.tgz.5578938.0.0.html) >> is OK. So does the insert module (by executing "insmod zd1211b.ko"). But >> after that, no packet is notified even for beacon. I think the hardware >> is ok becasue I have tried the same HW on a desktop PC with Fedora 5 >> installed (the kernel verson is 2.6.15) and it works pretty fine. >> I have tried to add some debug message for checking the data path. On >> my desktop PC, zd1211_rx_comp_cb() is called repeatly when a packet is >> received. But when using embedded environment (ARM with Linux 2.6.14), that >> function never been called. Following is the dmesg after ZyDas 1211B is >> installed. >> I have working on this for 2~3 weeks and can not find a solution >> for it. It will be great for anybody who can give me a hint or, even >> better, a solution. I really appreciat for you help. >> >> >> usb 1-1: new high speed USB device using FOTG2XX_DRV and address 5 >> hub 1-1:1.0: USB hub found >> hub 1-1:1.0: 4 ports detected >> usb 1-1.2: new high speed USB device using FOTG2XX_DRV and address 6 >> usb 1-1.1: new high speed USB device using FOTG2XX_DRV and address 7 >> >> / # i insmod /mnt/nfs/LinuxUSB/ar2524drv/zd1211b.ko >> >> _____ ____ _ ____ >> |__ / _| _ \ / \ / ___| >> / / | | | | | |/ _ \ \___ \ >> / /| |_| | |_| / ___ \ ___) | >> /____\__, |____/_/ \_\____/ >> |___/ >> ZD1211B - version 3.0.0.56 >> vendor_id = 0ace >> product_id = 1215 >> USB 2.0 Host >> Release Ver = 4810 >> EEPORM Ver = 4810 >> Finsih download Firmware. Ready to reboot >> PA type: 0 >> AR2124 RF >> [zd1205_set_zd_cbs, 11887] pObj->bChScanning is 0 >> AllowedChannel = 00011fff >> Region:48 >> usbcore: registered new driver zd1211b >> / # ifconfig ath0 up[zd1205_open, 4901] calling zd1211_submit_rx_urb() >> >> [zd1211_submit_rx_urb, 2766] started >> [zd1211_submit_rx_urb, 2791] calling usb_fill_bulk_urb() >> [zd1211_submit_rx_urb, 2809] ended >> [zd1211_rx_comp_cb, 2370] started >> [zd1211_rx_comp_cb, 2483] calling zd1211_rx_isr() >> [zd1211_rx_isr, 2213] started >> [zd1211_rx_isr, 2314] calling zd1211_submit_rx_urb() >> [zd1211_submit_rx_urb, 2766] started >> [zd1211_submit_rx_urb, 2791] calling usb_fill_bulk_urb() >> [zd1211_submit_rx_urb, 2809] ended >> [zd1211_rx_isr, 2331] calling zd1205_rx_isr() >> [zd1205_rx_isr, 3814] started >> [zd1205_rx_isr, 4567] ended >> [zd1211_rx_isr, 2348] ended >> [zd1211_rx_comp_cb, 2489] ended >> [zd_ConnectMon, 2816] >> [zd_CmdProbeReq, 961] pdot11Obj->bChScanning is 1 >> [zd_CmdProbeReq, 976] mMacMode: 1, CurrScanCH: 1 >> [zd_CmdProbeReq, 977] HZ: 1000, region: 48 >> [zdcb_start_timer, 11621] scan expire time: -116372 >> / [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 >> # [zd_CmdProbeReq, 991] zd_ProbeReq() result is 1 >> [kevent, 3963] scan time out >> [zd_SwitchNextCH, 1989] start next channel: 1 --> 2 >> [zdcb_start_timer, 11621] scan expire time: -116237 >> [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 >> [kevent, 3963] scan time out >> [zd_SwitchNextCH, 1989] start next channel: 2 --> 3 >> [zdcb_start_timer, 11621] scan expire time: -116102 >> [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 >> [kevent, 3963] scan time out >> [zd_SwitchNextCH, 1989] start next channel: 3 --> 4 >> [zdcb_start_timer, 11621] scan expire time: -115967 >> [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 >> [kevent, 3963] scan time out >> [zd_SwitchNextCH, 1989] start next channel: 4 --> 5 >> [zdcb_start_timer, 11621] scan expire time: -115831 >> [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 >> [kevent, 3963] scan time out >> [zd_SwitchNextCH, 1989] start next channel: 5 --> 6 >> [zdcb_start_timer, 11621] scan expire time: -115696 >> [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 >> [kevent, 3963] scan time out >> [zd_SwitchNextCH, 1989] start next channel: 6 --> 7 >> [zdcb_start_timer, 11621] scan expire time: -115560 >> [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 >> [kevent, 3963] scan time out >> [zd_SwitchNextCH, 1989] start next channel: 7 --> 8 >> [zdcb_start_timer, 11621] scan expire time: -115424 >> [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 >> [kevent, 3963] scan time out >> [zd_SwitchNextCH, 1989] start next channel: 8 --> 9 >> [zdcb_start_timer, 11621] scan expire time: -115289 >> [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 >> [kevent, 3963] scan time out >> [zd_SwitchNextCH, 1989] start next channel: 9 --> 10 >> [zdcb_start_timer, 11621] scan expire time: -115153 >> [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 >> [kevent, 3963] scan time out >> [zd_SwitchNextCH, 1989] start next channel: 10 --> 11 >> [zdcb_start_timer, 11621] scan expire time: -115016 >> [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 >> d[kevent, 3963] scan time out >> [zd_SwitchNextCH, 1989] start next channel: 11 --> 12 >> [zdcb_start_timer, 11621] scan expire time: -114878 >> [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 >> [kevent, 3963] scan time out >> [zd_SwitchNextCH, 1989] start next channel: 12 --> 13 >> [zdcb_start_timer, 11621] scan expire time: -114741 >> [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 >> [kevent, 3963] scan time out >> [zd_SwitchNextCH, 1989] start next channel: 13 --> 14 >> [zdcb_start_timer, 11621] scan expire time: -114619 >> [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 >> [kevent, 3963] scan time out >> [zd_SwitchNextCH, 1875] last channel: 14 >> [zd_SwitchNextCH, 1878] pdot11Obj->bChScanning is 0 >> >> SSID BSSID CH Signal Mode Basic-Rates >> Ext-Rates b/g AP >> >> ------------------------------------------------------------------------------------ >> ****** Scan Finished ****** >> mesg > 2.[zd_Roaming, 2791] >> [zd_CmdProbeReq, 961] pdot11Obj->bChScanning is 1 >> [zd_CmdProbeReq, 976] mMacMode: 1, CurrScanCH: 1 >> [zd_CmdProbeReq, 977] HZ: 1000, region: 48 >> [zdcb_start_timer, 11621] scan expire time: -110541 >> >> >> BRs, >> WengSing >> >> >> >> ------------------------------------------------------------------------------ >> Enable your software for Intel(R) Active Management Technology to meet the >> growing manageability and security demands of your customers. Businesses >> are taking advantage of Intel(R) vPro (TM) technology - will your software >> be a part of the solution? Download the Intel(R) Manageability Checker >> today! http://p.sf.net/sfu/intel-dev2devmar >> _______________________________________________ >> Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/ >> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs >> > > |
From: Nazim K. <naz...@gm...> - 2011-03-28 07:22:49
|
There are some patches available for zd1211b vendor driver. I don't have the link available but if you google, you should be able to find it. Browse through the history of this mailing list starting from mid 2007. Nazim 2011/3/28 李文星 <wen...@gm...> > Dear guys, > I have used ZyDas on ARM platform with Linux kernel 2.6.14. The > compilation of the source code (downloaded from > http://www.filewatcher.com/m/LinuxUSB_AR2524-3.0.0.56.tgz.5578938.0.0.html) > is OK. So does the insert module (by executing "insmod zd1211b.ko"). But > after that, no packet is notified even for beacon. I think the hardware > is ok becasue I have tried the same HW on a desktop PC with Fedora 5 > installed (the kernel verson is 2.6.15) and it works pretty fine. > I have tried to add some debug message for checking the data path. On > my desktop PC, zd1211_rx_comp_cb() is called repeatly when a packet is > received. But when using embedded environment (ARM with Linux 2.6.14), that > function never been called. Following is the dmesg after ZyDas 1211B is > installed. > I have working on this for 2~3 weeks and can not find a solution > for it. It will be great for anybody who can give me a hint or, even > better, a solution. I really appreciat for you help. > > > usb 1-1: new high speed USB device using FOTG2XX_DRV and address 5 > hub 1-1:1.0: USB hub found > hub 1-1:1.0: 4 ports detected > usb 1-1.2: new high speed USB device using FOTG2XX_DRV and address 6 > usb 1-1.1: new high speed USB device using FOTG2XX_DRV and address 7 > > / # i insmod /mnt/nfs/LinuxUSB/ar2524drv/zd1211b.ko > > _____ ____ _ ____ > |__ / _| _ \ / \ / ___| > / / | | | | | |/ _ \ \___ \ > / /| |_| | |_| / ___ \ ___) | > /____\__, |____/_/ \_\____/ > |___/ > ZD1211B - version 3.0.0.56 > vendor_id = 0ace > product_id = 1215 > USB 2.0 Host > Release Ver = 4810 > EEPORM Ver = 4810 > Finsih download Firmware. Ready to reboot > PA type: 0 > AR2124 RF > [zd1205_set_zd_cbs, 11887] pObj->bChScanning is 0 > AllowedChannel = 00011fff > Region:48 > usbcore: registered new driver zd1211b > / # ifconfig ath0 up[zd1205_open, 4901] calling zd1211_submit_rx_urb() > > [zd1211_submit_rx_urb, 2766] started > [zd1211_submit_rx_urb, 2791] calling usb_fill_bulk_urb() > [zd1211_submit_rx_urb, 2809] ended > [zd1211_rx_comp_cb, 2370] started > [zd1211_rx_comp_cb, 2483] calling zd1211_rx_isr() > [zd1211_rx_isr, 2213] started > [zd1211_rx_isr, 2314] calling zd1211_submit_rx_urb() > [zd1211_submit_rx_urb, 2766] started > [zd1211_submit_rx_urb, 2791] calling usb_fill_bulk_urb() > [zd1211_submit_rx_urb, 2809] ended > [zd1211_rx_isr, 2331] calling zd1205_rx_isr() > [zd1205_rx_isr, 3814] started > [zd1205_rx_isr, 4567] ended > [zd1211_rx_isr, 2348] ended > [zd1211_rx_comp_cb, 2489] ended > [zd_ConnectMon, 2816] > [zd_CmdProbeReq, 961] pdot11Obj->bChScanning is 1 > [zd_CmdProbeReq, 976] mMacMode: 1, CurrScanCH: 1 > [zd_CmdProbeReq, 977] HZ: 1000, region: 48 > [zdcb_start_timer, 11621] scan expire time: -116372 > / [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 > # [zd_CmdProbeReq, 991] zd_ProbeReq() result is 1 > [kevent, 3963] scan time out > [zd_SwitchNextCH, 1989] start next channel: 1 --> 2 > [zdcb_start_timer, 11621] scan expire time: -116237 > [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 > [kevent, 3963] scan time out > [zd_SwitchNextCH, 1989] start next channel: 2 --> 3 > [zdcb_start_timer, 11621] scan expire time: -116102 > [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 > [kevent, 3963] scan time out > [zd_SwitchNextCH, 1989] start next channel: 3 --> 4 > [zdcb_start_timer, 11621] scan expire time: -115967 > [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 > [kevent, 3963] scan time out > [zd_SwitchNextCH, 1989] start next channel: 4 --> 5 > [zdcb_start_timer, 11621] scan expire time: -115831 > [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 > [kevent, 3963] scan time out > [zd_SwitchNextCH, 1989] start next channel: 5 --> 6 > [zdcb_start_timer, 11621] scan expire time: -115696 > [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 > [kevent, 3963] scan time out > [zd_SwitchNextCH, 1989] start next channel: 6 --> 7 > [zdcb_start_timer, 11621] scan expire time: -115560 > [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 > [kevent, 3963] scan time out > [zd_SwitchNextCH, 1989] start next channel: 7 --> 8 > [zdcb_start_timer, 11621] scan expire time: -115424 > [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 > [kevent, 3963] scan time out > [zd_SwitchNextCH, 1989] start next channel: 8 --> 9 > [zdcb_start_timer, 11621] scan expire time: -115289 > [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 > [kevent, 3963] scan time out > [zd_SwitchNextCH, 1989] start next channel: 9 --> 10 > [zdcb_start_timer, 11621] scan expire time: -115153 > [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 > [kevent, 3963] scan time out > [zd_SwitchNextCH, 1989] start next channel: 10 --> 11 > [zdcb_start_timer, 11621] scan expire time: -115016 > [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 > d[kevent, 3963] scan time out > [zd_SwitchNextCH, 1989] start next channel: 11 --> 12 > [zdcb_start_timer, 11621] scan expire time: -114878 > [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 > [kevent, 3963] scan time out > [zd_SwitchNextCH, 1989] start next channel: 12 --> 13 > [zdcb_start_timer, 11621] scan expire time: -114741 > [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 > [kevent, 3963] scan time out > [zd_SwitchNextCH, 1989] start next channel: 13 --> 14 > [zdcb_start_timer, 11621] scan expire time: -114619 > [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 > [kevent, 3963] scan time out > [zd_SwitchNextCH, 1875] last channel: 14 > [zd_SwitchNextCH, 1878] pdot11Obj->bChScanning is 0 > > SSID BSSID CH Signal Mode Basic-Rates > Ext-Rates b/g AP > > ------------------------------------------------------------------------------------ > ****** Scan Finished ****** > mesg > 2.[zd_Roaming, 2791] > [zd_CmdProbeReq, 961] pdot11Obj->bChScanning is 1 > [zd_CmdProbeReq, 976] mMacMode: 1, CurrScanCH: 1 > [zd_CmdProbeReq, 977] HZ: 1000, region: 48 > [zdcb_start_timer, 11621] scan expire time: -110541 > > > BRs, > WengSing > > > > ------------------------------------------------------------------------------ > Enable your software for Intel(R) Active Management Technology to meet the > growing manageability and security demands of your customers. Businesses > are taking advantage of Intel(R) vPro (TM) technology - will your software > be a part of the solution? Download the Intel(R) Manageability Checker > today! http://p.sf.net/sfu/intel-dev2devmar > _______________________________________________ > Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/ > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs > |
From: 李文星 <wen...@gm...> - 2011-03-28 05:51:07
|
Dear guys, I have used ZyDas on ARM platform with Linux kernel 2.6.14. The compilation of the source code (downloaded from http://www.filewatcher.com/m/LinuxUSB_AR2524-3.0.0.56.tgz.5578938.0.0.html) is OK. So does the insert module (by executing "insmod zd1211b.ko"). But after that, no packet is notified even for beacon. I think the hardware is ok becasue I have tried the same HW on a desktop PC with Fedora 5 installed (the kernel verson is 2.6.15) and it works pretty fine. I have tried to add some debug message for checking the data path. On my desktop PC, zd1211_rx_comp_cb() is called repeatly when a packet is received. But when using embedded environment (ARM with Linux 2.6.14), that function never been called. Following is the dmesg after ZyDas 1211B is installed. I have working on this for 2~3 weeks and can not find a solution for it. It will be great for anybody who can give me a hint or, even better, a solution. I really appreciat for you help. usb 1-1: new high speed USB device using FOTG2XX_DRV and address 5 hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected usb 1-1.2: new high speed USB device using FOTG2XX_DRV and address 6 usb 1-1.1: new high speed USB device using FOTG2XX_DRV and address 7 / # i insmod /mnt/nfs/LinuxUSB/ar2524drv/zd1211b.ko _____ ____ _ ____ |__ / _| _ \ / \ / ___| / / | | | | | |/ _ \ \___ \ / /| |_| | |_| / ___ \ ___) | /____\__, |____/_/ \_\____/ |___/ ZD1211B - version 3.0.0.56 vendor_id = 0ace product_id = 1215 USB 2.0 Host Release Ver = 4810 EEPORM Ver = 4810 Finsih download Firmware. Ready to reboot PA type: 0 AR2124 RF [zd1205_set_zd_cbs, 11887] pObj->bChScanning is 0 AllowedChannel = 00011fff Region:48 usbcore: registered new driver zd1211b / # ifconfig ath0 up[zd1205_open, 4901] calling zd1211_submit_rx_urb() [zd1211_submit_rx_urb, 2766] started [zd1211_submit_rx_urb, 2791] calling usb_fill_bulk_urb() [zd1211_submit_rx_urb, 2809] ended [zd1211_rx_comp_cb, 2370] started [zd1211_rx_comp_cb, 2483] calling zd1211_rx_isr() [zd1211_rx_isr, 2213] started [zd1211_rx_isr, 2314] calling zd1211_submit_rx_urb() [zd1211_submit_rx_urb, 2766] started [zd1211_submit_rx_urb, 2791] calling usb_fill_bulk_urb() [zd1211_submit_rx_urb, 2809] ended [zd1211_rx_isr, 2331] calling zd1205_rx_isr() [zd1205_rx_isr, 3814] started [zd1205_rx_isr, 4567] ended [zd1211_rx_isr, 2348] ended [zd1211_rx_comp_cb, 2489] ended [zd_ConnectMon, 2816] [zd_CmdProbeReq, 961] pdot11Obj->bChScanning is 1 [zd_CmdProbeReq, 976] mMacMode: 1, CurrScanCH: 1 [zd_CmdProbeReq, 977] HZ: 1000, region: 48 [zdcb_start_timer, 11621] scan expire time: -116372 / [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 # [zd_CmdProbeReq, 991] zd_ProbeReq() result is 1 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 1 --> 2 [zdcb_start_timer, 11621] scan expire time: -116237 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 2 --> 3 [zdcb_start_timer, 11621] scan expire time: -116102 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 3 --> 4 [zdcb_start_timer, 11621] scan expire time: -115967 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 4 --> 5 [zdcb_start_timer, 11621] scan expire time: -115831 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 5 --> 6 [zdcb_start_timer, 11621] scan expire time: -115696 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 6 --> 7 [zdcb_start_timer, 11621] scan expire time: -115560 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 7 --> 8 [zdcb_start_timer, 11621] scan expire time: -115424 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 8 --> 9 [zdcb_start_timer, 11621] scan expire time: -115289 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 9 --> 10 [zdcb_start_timer, 11621] scan expire time: -115153 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 10 --> 11 [zdcb_start_timer, 11621] scan expire time: -115016 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 d[kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 11 --> 12 [zdcb_start_timer, 11621] scan expire time: -114878 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 12 --> 13 [zdcb_start_timer, 11621] scan expire time: -114741 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1989] start next channel: 13 --> 14 [zdcb_start_timer, 11621] scan expire time: -114619 [SynchEntry, 505] SIG_PROBE_REQ, ProbeReq(): 0 [kevent, 3963] scan time out [zd_SwitchNextCH, 1875] last channel: 14 [zd_SwitchNextCH, 1878] pdot11Obj->bChScanning is 0 SSID BSSID CH Signal Mode Basic-Rates Ext-Rates b/g AP ------------------------------------------------------------------------------------ ****** Scan Finished ****** mesg > 2.[zd_Roaming, 2791] [zd_CmdProbeReq, 961] pdot11Obj->bChScanning is 1 [zd_CmdProbeReq, 976] mMacMode: 1, CurrScanCH: 1 [zd_CmdProbeReq, 977] HZ: 1000, region: 48 [zdcb_start_timer, 11621] scan expire time: -110541 BRs, WengSing |
From: Hin-Tak L. <ht...@us...> - 2011-02-16 01:28:27
|
Hi, I added patch 13 and 14 to http://htl10.users.sourceforge.net/patchsets/LinuxUSB_AR2524-3.0.0.56/ which allows the zd1211 vendor driver to build against recent kernel - in my case, 2.6.35.10 . I use it mainly for the AP mode, on an old machine that has just been resurrected after over a year, so the last it worked was on 2.6.31.x . There are a couple of old and new quirks: a dozen of 'We are trapped in zd_SigProcess, Going to release all,id=3,block=1' is new to 2.6.35.x, but the driver has always needed if down/up and or iwlist scan before a client station can connect, and that's still the case; and under extended use (a few days, and/or a few GB traffic) it can still bring the AP machine down. I see some great person has just had a whole bunch of patches committed to wireless-testing in the last few months for enabling AP mode for the in-kernel zd1211rw driver... so 2.6.39(?) or thereabout it would be generally available...so the use of the vendor driver for AP mode would soon not be needed any more. I'd probably give the compat-wireless a try soon enough. |
From: nadia h. <hao...@ya...> - 2011-01-21 21:10:08
|
http://polepositionmodellismo.it/index-sl122.php |
From: julien c. <j.c...@fr...> - 2010-10-30 08:23:41
|
Le samedi 30 octobre 2010 à 06:22 +0100, Hin-Tak Leung a écrit : > That's not what I said - I said there is some evidence that the *new* minstrel > rate control algorithm doesn't work, so older kernel kernel releases work better > for some people. That's not what I experience : * with minstrel, there is some rate control going on since the rate isn't stuck at 1Mb * with pid (stock driver from kernel 2.6.32 and 2.6.35 when I set it at build time), there wasn't any rate control : rate stayed at 1Mb/s if I didn't set it otherwise. However, with minstrel (stock driver from 2.6.35) I get these disconnections during upload. I also get them with pid when I set it at build time so maybe the two issues (rate control and disconnections) aren't related. |
From: Hin-Tak L. <hin...@ya...> - 2010-10-30 05:22:30
|
julien cubizolles wrote: > Le vendredi 29 octobre 2010 à 00:38 +0100, Hin-Tak Leung a écrit : >> julien cubizolles wrote: >>> By default, the bitrate is set to 1Mb/s. I usually set it to 48Mb/s or >>> upload is ridiculously slow. That's what I've been doing with kernel >>> 2.6.32 for a year or so. >> By default, the bitrate is set to 1Mb/s *when you are not using your >> connection*. It should shift up when you start using it, otherwise the rate >> control algorithm is not working. That's what "rate control algorithm" means. > > Tha'ts what i had understood : the previous rate control algorithm (pid > from what you said) doesn't work. That's not what I said - I said there is some evidence that the *new* minstrel rate control algorithm doesn't work, so older kernel kernel releases work better for some people. |
From: julien c. <j.c...@fr...> - 2010-10-29 07:05:52
|
Le vendredi 29 octobre 2010 à 00:38 +0100, Hin-Tak Leung a écrit : > julien cubizolles wrote: > > By default, the bitrate is set to 1Mb/s. I usually set it to 48Mb/s or > > upload is ridiculously slow. That's what I've been doing with kernel > > 2.6.32 for a year or so. > > By default, the bitrate is set to 1Mb/s *when you are not using your > connection*. It should shift up when you start using it, otherwise the rate > control algorithm is not working. That's what "rate control algorithm" means. Tha'ts what i had understood : the previous rate control algorithm (pid from what you said) doesn't work. |
From: Hin-Tak L. <hin...@ya...> - 2010-10-28 23:38:09
|
julien cubizolles wrote: > By default, the bitrate is set to 1Mb/s. I usually set it to 48Mb/s or > upload is ridiculously slow. That's what I've been doing with kernel > 2.6.32 for a year or so. By default, the bitrate is set to 1Mb/s *when you are not using your connection*. It should shift up when you start using it, otherwise the rate control algorithm is not working. That's what "rate control algorithm" means. >>> For the first occurence of the bug : >>> >>> master-tag : master-2009-11-02 >>> git-describe : v2.6.32-rc5-40735-g8573aa6 >>> compat-release : master-2009-10-30-1-g357b74e >>> >>> Is this the information you need ? >> And the corresponding "last working" version of these. > > master-tag : master-2009-10-16 > git-describe : v2.6.32-rc5-40584-g9b469da > compat-release : master-2009-10-16 that's it. Now everybody can have a look at the diff. (I am not promising to look at it any time soon...) |
From: julien c. <j.c...@fr...> - 2010-10-28 13:21:33
|
Le jeudi 28 octobre 2010 à 13:31 +0100, Hin-Tak Leung a écrit : > --- On Thu, 28/10/10, julien cubizolles <j.c...@fr...> wrote: > > > First : I have to manually set the bitrate like it was > > before. > > > > But the bug remains : I get deconnected after a few Mo > > uploaded. > > Overriding bitrate is probably not advisable - why do you do that. By default, the bitrate is set to 1Mb/s. I usually set it to 48Mb/s or upload is ridiculously slow. That's what I've been doing with kernel 2.6.32 for a year or so. > > For the first occurence of the bug : > > > > master-tag : master-2009-11-02 > > git-describe : v2.6.32-rc5-40735-g8573aa6 > > compat-release : master-2009-10-30-1-g357b74e > > > > Is this the information you need ? > > And the corresponding "last working" version of these. master-tag : master-2009-10-16 git-describe : v2.6.32-rc5-40584-g9b469da compat-release : master-2009-10-16 |
From: Hin-Tak L. <hin...@ya...> - 2010-10-28 12:31:57
|
--- On Thu, 28/10/10, julien cubizolles <j.c...@fr...> wrote: > First : I have to manually set the bitrate like it was > before. > > But the bug remains : I get deconnected after a few Mo > uploaded. Overriding bitrate is probably not advisable - why do you do that. (also, please keep the cc to the list - this is not a private consultancy). > > > 2) It is not very useful posting > compat-wireless-2009-10-28 vs > > compat-wireless-2009-11-03 - it is more useful posting > the content of > > "master-tag", "git-describe", and "compat-release" > (and maybe other small files) > > at the top of the tarball which contains the git tags > or sha1 sum of where they > > derives (this may it easier to pin point what it was > made of and the difference > > between it and the other). > > For the first occurence of the bug : > > master-tag : master-2009-11-02 > git-describe : v2.6.32-rc5-40735-g8573aa6 > compat-release : master-2009-10-30-1-g357b74e > > Is this the information you need ? And the corresponding "last working" version of these. |