zd1211rw couldn't load firmware. Error number -145 with Kernel 2.6.30

[Mladen Horvat]

Hello all,

i am running Kernel 2.6.30 on a embedded linux stb and trying with two
different zd1211b usb wlan sticks to get the zd1211rw driver running.

just as a remark:  an rt73usb stick works without problems.

Dont know what you need. so here is some informations:

uname -a
Linux dm7025 2.6.30-dm7025 #1 Tue Jul 28 20:25:28 CEST 2009 mips unknown

lsmod
    Tainted: P
arc4 1536 2 - Live 0xc05c5000
ecb 2880 2 - Live 0xc05bc000
cryptomgr 87872 0 - Live 0xc059d000
crypto_hash 11840 1 cryptomgr, Live 0xc057a000
crypto_blkcipher 13232 2 ecb,cryptomgr, Live 0xc056c000
aead 7168 1 cryptomgr, Live 0xc0560000
pcompress 1952 1 cryptomgr, Live 0xc0558000
crypto_algapi 18176 7
arc4,ecb,cryptomgr,crypto_hash,crypto_blkcipher,aead,pcompress, Live 0xc054a000
zd1211rw 78736 0 - Live 0xc0527000
mac80211 174976 1 zd1211rw, Live 0xc04d6000
crypto 13360 8
ecb,cryptomgr,crypto_hash,crypto_blkcipher,aead,pcompress,crypto_algapi,
mac80211, Live
0xc048c000
cfg80211 79216 2 zd1211rw,mac80211, Live 0xc046e000
rfmod 3808 1 - Live 0xc0448000 (P)
dreambox_keyboard 5248 0 - Live 0xc043d000 (P)
dreambox_rc2 5248 1 dreambox_keyboard, Live 0xc0431000 (P)
xilleon 222592 6 - Live 0xc0185000 (P)
alps_bsbe1_c01a 19568 1 xilleon, Live 0xc0132000 (P)
alps_bsbe1 5264 1 xilleon, Live 0xc0124000 (P)
avs 11168 1 xilleon, Live 0xc0117000 (P)
alps_bsbe2 44480 1 xilleon, Live 0xc0103000 (P)
lnb_ctrl 5664 3 alps_bsbe1_c01a,alps_bsbe1,alps_bsbe2, Live 0xc00f0000 (P)
tu1216 44912 1 xilleon, Live 0xc00de000
cu1216mk3 9504 1 xilleon, Live 0xc00c9000 (P)
stb_core 52704 10
dreambox_keyboard,dreambox_rc2,xilleon,alps_bsbe1_c01a,avs,alps_bsbe2,
lnb_ctrl,cu1216mk3,
Live 0xc00b1000 (P)
pata_xilleon 3888 1 - Live 0xc0095000
lcd 30800 1 - Live 0xc0084000 (P)
fp 21840 4 xilleon,avs,lcd, Live 0xc0072000 (P)

Output from DMESG:
[  279.131000] cfg80211: Calling CRDA to update world regulatory domain
[  279.509000] zd1211rw usb_init()
[  279.520000] usbcore: registered new interface driver zd1211rw
[  279.526000] zd1211rw initialized
[  292.405000] usb 1-1: new full speed USB device using ohci_hcd
 and address 2
[  292.557000] usb 1-1: configuration #1 chosen from 1 choice
[  292.573000] usb 1-1: print_id() 050d:705c v4810 full
[  292.686000] usb 1-1: reset full speed USB device using ohci_hcd
and address 2
[  292.829000] zd1211rw 1-1:1.0: zd_chip_read_mac_addr_fw()
[  293.308000] phy0: Selected rate control algorithm 'pid'
[  293.309000] zd1211rw 1-1:1.0: probe() successful
[  293.309000] zd1211rw 1-1:1.0: phy0
[  359.661000] warning: `vsftpd' uses 32-bit capabilities (legacy support in use)
[  408.957000] zd1211rw 1-1:1.0: zd_usb_init_hw()
[  408.957000] usb 1-1: request_fw_file() fw name zd1211/zd1211b_ub
[  408.957000] usb 1-1: firmware: requesting zd1211/zd1211b_ub
[  409.022000] usb 1-1: upload_firmware() firmware device id 0x4810 is equal
to
the actual device id
[  409.022000] usb 1-1: request_fw_file() fw name zd1211/zd1211b_uphr
[  409.022000] usb 1-1: firmware: requesting zd1211/zd1211b_uphr
[  409.079000] usb 1-1: upload_code() transfer size 4018
[  409.094000] usb 1-1: upload_code() firmware confirm return value 0x01
[  414.094000] zd1211rw 1-1:1.0: zd_usb_init_hw()
couldn't reset configuration. Error number -145
[  415.226000] zd1211rw 1-1:1.0: zd_usb_init_hw()
[  415.226000] usb 1-1: request_fw_file() fw name zd1211/zd1211b_ub
[  415.226000] usb 1-1: firmware: requesting zd1211/zd1211b_ub
[  415.271000] usb 1-1: upload_firmware()
firmware device id 0x4810 is equal to the actual device id
[  415.271000] usb 1-1: request_fw_file() fw name zd1211/zd1211b_uphr
[  415.271000] usb 1-1: firmware: requesting zd1211/zd1211b_uphr
[  415.350000] usb 1-1: upload_code() transfer size 4018
[  416.350000] usb 1-1: USB control request for firmware upload failed.
Error number -145
[  416.358000] usb 1-1: Could not upload firmware code uph. Error number -145
[  416.365000] zd1211rw 1-1:1.0: couldn't load firmware. Error number -145
[  432.484000] zd1211rw 1-1:1.0: zd_usb_init_hw()
[  432.484000] usb 1-1: request_fw_file() fw name zd1211/zd1211b_ub
[  432.484000] usb 1-1: firmware: requesting zd1211/zd1211b_ub
[  432.529000] usb 1-1: upload_firmware()
firmware device id 0x4810 is equal to the actual device id
[  432.529000] usb 1-1: request_fw_file() fw name zd1211/zd1211b_uphr
[  432.529000] usb 1-1: firmware: requesting zd1211/zd1211b_uphr
[  432.608000] usb 1-1: upload_code() transfer size 4018
[  433.608000] usb 1-1: USB control request for firmware upload failed.
Error number -145
[  433.616000] usb 1-1: Could not upload firmware code uph. Error number -145
[  433.623000] zd1211rw 1-1:1.0: couldn't load firmware. Error number -145
[  434.827000] eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1

output from lsusb
Bus 001 Device 002: ID 050d:705c Belkin Components

the Firmware Files are located with correct right under /lib/firmware/zd1211
any idea on this ?

Regards

Mladen



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

[Hin-Tak Leung]

-145 is time out ('Use the source, Luke!'). mips is a bit exotic, not many people have that, and probably not very well-tested; could try compat-wireless to see if there is any endian fixes. The other thing is, ohci is a bit slow, and the ZyDAS chip draws a fair amount of power and doesn't really work on bus-powered usb 1.1 host, if that's what you have. I don't know if you would get a 'not enough power' message - I seem to recall I did.

--- On Wed, 29/7/09, Mladen Horvat <acid-burn@...> wrote:

> From: Mladen Horvat <acid-burn@...>
> Subject: [zd1211-devs] zd1211rw couldn't load firmware. Error number -145 with Kernel 2.6.30
> To: zd1211-devs@...
> Date: Wednesday, 29 July, 2009, 12:32 PM
> Hello all,
>
> i am running Kernel 2.6.30 on a embedded linux stb and
> trying with two
> different zd1211b usb wlan sticks to get the zd1211rw
> driver running.
>
> just as a remark:  an rt73usb stick works without
> problems.
>
> Dont know what you need. so here is some informations:
>
> uname -a
> Linux dm7025 2.6.30-dm7025 #1 Tue Jul 28 20:25:28 CEST 2009
> mips unknown
>
> lsmod
>     Tainted: P
> arc4 1536 2 - Live 0xc05c5000
> ecb 2880 2 - Live 0xc05bc000
> cryptomgr 87872 0 - Live 0xc059d000
> crypto_hash 11840 1 cryptomgr, Live 0xc057a000
> crypto_blkcipher 13232 2 ecb,cryptomgr, Live 0xc056c000
> aead 7168 1 cryptomgr, Live 0xc0560000
> pcompress 1952 1 cryptomgr, Live 0xc0558000
> crypto_algapi 18176 7
> arc4,ecb,cryptomgr,crypto_hash,crypto_blkcipher,aead,pcompress,
> Live 0xc054a000
> zd1211rw 78736 0 - Live 0xc0527000
> mac80211 174976 1 zd1211rw, Live 0xc04d6000
> crypto 13360 8
> ecb,cryptomgr,crypto_hash,crypto_blkcipher,aead,pcompress,crypto_algapi,
> mac80211, Live
> 0xc048c000
> cfg80211 79216 2 zd1211rw,mac80211, Live 0xc046e000
> rfmod 3808 1 - Live 0xc0448000 (P)
> dreambox_keyboard 5248 0 - Live 0xc043d000 (P)
> dreambox_rc2 5248 1 dreambox_keyboard, Live 0xc0431000 (P)
> xilleon 222592 6 - Live 0xc0185000 (P)
> alps_bsbe1_c01a 19568 1 xilleon, Live 0xc0132000 (P)
> alps_bsbe1 5264 1 xilleon, Live 0xc0124000 (P)
> avs 11168 1 xilleon, Live 0xc0117000 (P)
> alps_bsbe2 44480 1 xilleon, Live 0xc0103000 (P)
> lnb_ctrl 5664 3 alps_bsbe1_c01a,alps_bsbe1,alps_bsbe2, Live
> 0xc00f0000 (P)
> tu1216 44912 1 xilleon, Live 0xc00de000
> cu1216mk3 9504 1 xilleon, Live 0xc00c9000 (P)
> stb_core 52704 10
> dreambox_keyboard,dreambox_rc2,xilleon,alps_bsbe1_c01a,avs,alps_bsbe2,
> lnb_ctrl,cu1216mk3,
> Live 0xc00b1000 (P)
> pata_xilleon 3888 1 - Live 0xc0095000
> lcd 30800 1 - Live 0xc0084000 (P)
> fp 21840 4 xilleon,avs,lcd, Live 0xc0072000 (P)
>
> Output from DMESG:
> [  279.131000] cfg80211: Calling CRDA to update world
> regulatory domain
> [  279.509000] zd1211rw usb_init()
> [  279.520000] usbcore: registered new interface
> driver zd1211rw
> [  279.526000] zd1211rw initialized
> [  292.405000] usb 1-1: new full speed USB device
> using ohci_hcd
>  and address 2
> [  292.557000] usb 1-1: configuration #1 chosen from 1
> choice
> [  292.573000] usb 1-1: print_id() 050d:705c v4810
> full
> [  292.686000] usb 1-1: reset full speed USB device
> using ohci_hcd
> and address 2
> [  292.829000] zd1211rw 1-1:1.0:
> zd_chip_read_mac_addr_fw()
> [  293.308000] phy0: Selected rate control algorithm
> 'pid'
> [  293.309000] zd1211rw 1-1:1.0: probe() successful
> [  293.309000] zd1211rw 1-1:1.0: phy0
> [  359.661000] warning: `vsftpd' uses 32-bit
> capabilities (legacy support in use)
> [  408.957000] zd1211rw 1-1:1.0: zd_usb_init_hw()
> [  408.957000] usb 1-1: request_fw_file() fw name
> zd1211/zd1211b_ub
> [  408.957000] usb 1-1: firmware: requesting
> zd1211/zd1211b_ub
> [  409.022000] usb 1-1: upload_firmware() firmware
> device id 0x4810 is equal
> to
> the actual device id
> [  409.022000] usb 1-1: request_fw_file() fw name
> zd1211/zd1211b_uphr
> [  409.022000] usb 1-1: firmware: requesting
> zd1211/zd1211b_uphr
> [  409.079000] usb 1-1: upload_code() transfer size
> 4018
> [  409.094000] usb 1-1: upload_code() firmware confirm
> return value 0x01
> [  414.094000] zd1211rw 1-1:1.0: zd_usb_init_hw()
> couldn't reset configuration. Error number -145
> [  415.226000] zd1211rw 1-1:1.0: zd_usb_init_hw()
> [  415.226000] usb 1-1: request_fw_file() fw name
> zd1211/zd1211b_ub
> [  415.226000] usb 1-1: firmware: requesting
> zd1211/zd1211b_ub
> [  415.271000] usb 1-1: upload_firmware()
> firmware device id 0x4810 is equal to the actual device id
> [  415.271000] usb 1-1: request_fw_file() fw name
> zd1211/zd1211b_uphr
> [  415.271000] usb 1-1: firmware: requesting
> zd1211/zd1211b_uphr
> [  415.350000] usb 1-1: upload_code() transfer size
> 4018
> [  416.350000] usb 1-1: USB control request for
> firmware upload failed.
> Error number -145
> [  416.358000] usb 1-1: Could not upload firmware code
> uph. Error number -145
> [  416.365000] zd1211rw 1-1:1.0: couldn't load
> firmware. Error number -145
> [  432.484000] zd1211rw 1-1:1.0: zd_usb_init_hw()
> [  432.484000] usb 1-1: request_fw_file() fw name
> zd1211/zd1211b_ub
> [  432.484000] usb 1-1: firmware: requesting
> zd1211/zd1211b_ub
> [  432.529000] usb 1-1: upload_firmware()
> firmware device id 0x4810 is equal to the actual device id
> [  432.529000] usb 1-1: request_fw_file() fw name
> zd1211/zd1211b_uphr
> [  432.529000] usb 1-1: firmware: requesting
> zd1211/zd1211b_uphr
> [  432.608000] usb 1-1: upload_code() transfer size
> 4018
> [  433.608000] usb 1-1: USB control request for
> firmware upload failed.
> Error number -145
> [  433.616000] usb 1-1: Could not upload firmware code
> uph. Error number -145
> [  433.623000] zd1211rw 1-1:1.0: couldn't load
> firmware. Error number -145
> [  434.827000] eth0: link up, 100Mbps, full-duplex,
> lpa 0xC5E1
>
> output from lsusb
> Bus 001 Device 002: ID 050d:705c Belkin Components
>
> the Firmware Files are located with correct right under
> /lib/firmware/zd1211
> any idea on this ?
>
> Regards
>
> Mladen
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal
> Reports 2008 30-Day
> trial. Simplify your report design, integration and
> deployment - and focus on
> what you do best, core application coding. Discover what's
> new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
>

     


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

[Mladen Horvat]

Hin-Tak Leung <hintak_leung <at> yahoo.co.uk> writes:

>
> -145 is time out ('Use the source, Luke!'). mips is a bit exotic, not many
people have that, and probably not
> very well-tested; could try compat-wireless to see if there is any endian
fixes. The other thing is, ohci
> is a bit slow, and the ZyDAS chip draws a fair amount of power and doesn't
really work on bus-powered usb 1.1
> host, if that's what you have. I don't know if you would get a 'not enough
power' message - I seem to recall I
> did.
>


Hi Hin-Tak

thanks for your fast answer.

The same stb only booted with a rt73usb wlan stick attached has no
problems with the firmware upload and also wpa-supplicant connection and
everything works on wlan0.  only problem are these two zd1211b usb sticks in the
zd1211rw driver i have here.

the same stb running a kernel 2.6.12 and the original vendor driver 2.22.00
works without problems..

i will take a look what happens with an externally powered usb hub.

Hope this helps.
If any other logs are needed i will provide them.

Regards

Mladen




------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

[Mladen Horvat]

Hin-Tak Leung <hintak_leung <at> yahoo.co.uk> writes:

>
> -145 is time out ('Use the source, Luke!'). mips is a bit exotic, not many
people have that, and probably not
> very well-tested; could try compat-wireless to see if there is any endian
fixes. The other thing is, ohci
> is a bit slow, and the ZyDAS chip draws a fair amount of power and doesn't
really work on bus-powered usb 1.1
> host, if that's what you have. I don't know if you would get a 'not enough
power' message - I seem to recall I
> did.
>

Ok. Just added a external usb hub but now there are even more errors ;-)
http://pastebin.com/m37023ceb
perhaps it helps.

regards

Mladen


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

[Hin-Tak Leung]

--- On Wed, 29/7/09, Mladen Horvat <acid-burn@...> wrote:

> Hi Hin-Tak
>
> thanks for your fast answer.
>
> The same stb only booted with a rt73usb wlan stick attached
> has no
> problems with the firmware upload and also wpa-supplicant
> connection and
> everything works on wlan0.  only problem are these two
> zd1211b usb sticks in the
> zd1211rw driver i have here.
>
> the same stb running a kernel 2.6.12 and the original
> vendor driver 2.22.00
> works without problems..
>
> i will take a look what happens with an externally powered
> usb hub.
>
> Hope this helps.
> If any other logs are needed i will provide them.

Well, if the vendor driver 2.22.00 works with 2.6.12, you can grab my patch set (sorry it is 'pathset' in the web location - I made a mistake in May and haven't fixed it yet): http://htl10.users.sourceforge.net/ZD1211LnxDrv_2_22_0_0_2009May_pathset/ 

which would take you up to 2.6.29. I haven't tried 2.6.30 as I already moved to the vendor driver 3.0 by then. You need the other patch set

http://htl10.users.sourceforge.net/LinuxUSB_AR2524-3.0.0.56_2009May_pathset/
to take you up to 2.6.29, and the last one (attached) to take you to 2.6.30.. It may also work for the 2.22 driver but I haven't tried, but it will at least give you some ideas if you like to make the vendor 2.22 driver work on 2.6.30.

The 3.0 vendor driver is at:
http://www.kernel.org/pub/linux/kernel/people/mcgrof/zd1211/LinuxUSB_AR2524-3.0.0.56.tgz

Hmm, the firmware upload problem seems to have come up from time to time...

if either versions of the vendor drivers work (but the rw driver does not) I like to know. You will need to set up the blacklist to stop udev from autoloading kernel modules, but presumably you already know that.


   
[0001-2.6.30-irqreturn_t-breakage.patch]

---

From 470a784d9ba4db962fb66080bdf2ca0d1d2edc9e Mon Sep 17 00:00:00 2001
From: Hin-Tak Leung <HinTak.Leung@...>
Date: Thu, 25 Jun 2009 00:09:08 +0100
Subject: [PATCH] 2.6.30-irqreturn_t-breakage

Change to deal with this change:

commit bedd30d986a05e32dc3eab874e4b9ed8a38058bb
Author: Thomas Gleixner <tglx@...>
Date:   Tue Sep 30 23:14:27 2008 +0200

    genirq: make irqreturn_t an enum

    Impact: cleanup

    Remove the 2.4 compabiliy cruft

    Signed-off-by: Thomas Gleixner <tglx@...>
    Reviewed-by: Peter Zijlstra <peterz@...>
---
 ar2524drv/src/zdcompat.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/ar2524drv/src/zdcompat.h b/ar2524drv/src/zdcompat.h
index 3d352e7..45008ba 100644
--- a/ar2524drv/src/zdcompat.h
+++ b/ar2524drv/src/zdcompat.h
@@ -65,7 +65,7 @@ struct iw_request_info
 #endif
 
 /* linux < 2.5.69 */
-#ifndef IRQ_NONE
+#ifndef _LINUX_IRQRETURN_H
 typedef void irqreturn_t;
 #define IRQ_NONE
 #define IRQ_HANDLED
--
1.6.2.5

---

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

[Mladen Horvat]

Hin-Tak Leung <hintak_leung <at> yahoo.co.uk> writes:

>
> --- On Wed, 29/7/09, Mladen Horvat <acid-burn <at> opendreambox.org> wrote:
>
> > Hi Hin-Tak
> >
> > thanks for your fast answer.
> >
> > The same stb only booted with a rt73usb wlan stick attached
> > has no
> > problems with the firmware upload and also wpa-supplicant
> > connection and
> > everything works on wlan0.  only problem are these two
> > zd1211b usb sticks in the
> > zd1211rw driver i have here.
> >
> > the same stb running a kernel 2.6.12 and the original
> > vendor driver 2.22.00
> > works without problems..
> >
> > i will take a look what happens with an externally powered
> > usb hub.
> >
> > Hope this helps.
> > If any other logs are needed i will provide them.
>
> Well, if the vendor driver 2.22.00 works with 2.6.12, you can grab my patch

set (sorry it is 'pathset' in the
> web location - I made a mistake in May and haven't fixed it yet):
> http://htl10.users.sourceforge.net/ZD1211LnxDrv_2_22_0_0_2009May_pathset/ 
>
> which would take you up to 2.6.29. I haven't tried 2.6.30 as I already moved
to the vendor driver 3.0 by then.
> You need the other patch set
>
> http://htl10.users.sourceforge.net/LinuxUSB_AR2524-3.0.0.56_2009May_pathset/
> to take you up to 2.6.29, and the last one (attached) to take you to 2.6.30..
It may also work for the 2.22
> driver but I haven't tried, but it will at least give you some ideas if you
like to make the vendor 2.22 driver
> work on 2.6.30.
>
> The 3.0 vendor driver is at:
>
http://www.kernel.org/pub/linux/kernel/people/mcgrof/zd1211/LinuxUSB_AR2524-3.0.0.56.tgz
>
> Hmm, the firmware upload problem seems to have come up from time to time...
>
> if either versions of the vendor drivers work (but the rw driver does not) I
like to know. You will need to set
> up the blacklist to stop udev from autoloading kernel modules, but presumably
you already know that.
>
>      
> Attachment (0001-2.6.30-irqreturn_t-breakage.patch): text/x-patch, 1020 bytes
>

Hi again,

perhaps this is an idea to try the vendor 3.0 driver with the new kernel.

Just a question. Is the driver using the new mac80211 wireless interface so i
can use it over wpa supllicant 0.6.9 and the build-in wext interface ?

Just saw sth about wpa-s 0.4.8 and was wondering if this will work ?

regards

Mladen


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

[Hin-Tak Leung]

--- On Wed, 29/7/09, Mladen Horvat <acid-burn@...> wrote:

> Hi again,
>
> perhaps this is an idea to try the vendor 3.0 driver with
> the new kernel.
>
> Just a question. Is the driver using the new mac80211
> wireless interface so i
> can use it over wpa supllicant 0.6.9 and the build-in wext
> interface ?
>
> Just saw sth about wpa-s 0.4.8 and was wondering if this
> will work ?

old stack, but it does wext and should just work regardless of wpa supplicant version.
(I don't use that - I run it in AP mode). Basically whatever you did with 2..22 should just work with 3.0 - only better and less buggy :-).


     


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

[Hin-Tak Leung]

Do not write directly - all traffic should go into the mailing list archive.. That's very selfish behavior. I do not work for you and I'll have to charge you on private consultancy rate for that.

Your kernel headers do not match your kernel. (supposedly 2.6.30), nothing to do with
compiler version.

--- On Thu, 30/7/09, acid-burn <acid-burn@...> wrote:

> Hello,
>
> thought i write you directlyand not bother the list with
> compile problems..
>
> i am currently trying to compile the 3.0 src with your
> patches.
>
> I get a bunch of warnings about undefined things and
> errors.
>
> Could this be related on the used gcc compiler ?
>
> I have to use gcc-4.4.0
>
>
> Perhaps you have an idea ?
>
> Regards
>
> Mladen

     


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

[Mladen Horvat]

Hin-Tak Leung <hintak_leung <at> yahoo.co.uk> writes:

> Well, if the vendor driver 2.22.00 works with 2.6.12, you can grab my patch
set (sorry it is 'pathset' in the
> web location - I made a mistake in May and haven't fixed it yet):
> http://htl10.users.sourceforge.net/ZD1211LnxDrv_2_22_0_0_2009May_pathset/ 
>
> which would take you up to 2.6.29. I haven't tried 2.6.30 as I already moved
to the vendor driver 3.0 by then.
> You need the other patch set
>
> http://htl10.users.sourceforge.net/LinuxUSB_AR2524-3.0.0.56_2009May_pathset/
> to take you up to 2.6.29, and the last one (attached) to take you to 2.6.30..
It may also work for the 2.22
> driver but I haven't tried, but it will at least give you some ideas if you
like to make the vendor 2.22 driver
> work on 2.6.30.
>
> The 3.0 vendor driver is at:
>
http://www.kernel.org/pub/linux/kernel/people/mcgrof/zd1211/LinuxUSB_AR2524-3.0.0.56.tgz
>
> Hmm, the firmware upload problem seems to have come up from time to time...
>
> if either versions of the vendor drivers work (but the rw driver does not) I
like to know. You will need to set
> up the blacklist to stop udev from autoloading kernel modules, but presumably
you already know that.
>

Ok, finally managed with the help of a friend to compile the vender driver
3.0.0.56 with the mips 2.6.30 kernel i use here.
Here is a patch that was needed to get it finally compiled under 2.6.30.
http://pastebin.com/m17687d4e

Firmware Upload works !!!  and interface comes up as ath0.

But: looks like the driver doesnt work or like my WPA-Supplicant 0.6.9

Here is a Bootlog and outputs that come:  http://pastebin.com/m232e0dfa

Network Configuration:
cat /etc/network/interfaces
auto ath0
iface ath0 inet dhcp
        wpa-driver wext
        wpa-debug-level 3
        wpa-conf /etc/wpa_supplicant.conf

auto eth0
iface eth0 inet dhcp

cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
fast_reauth=1
ap_scan=1
network={
        ssid="MyNetwork"
        scan_ssid=1
        key_mgmt=WPA-PSK
        proto=WPA RSN
        pairwise=CCMP TKIP
        group=CCMP TKIP
        psk="MyPassword"
}

This configuration works flawless with an other machine and a ath5k mini-pci
card or on the same machine with an rt73usb stick running wpa-supplicant 0.6.9
and the wext driver.

Any Idea ?

regards

Mladen







------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

[Hin-Tak Leung]

--- On Thu, 30/7/09, Mladen Horvat <acid-burn@...> wrote:

> Ok, finally managed with the help of a friend to compile
> the vender driver
> 3.0.0.56 with the mips 2.6.30 kernel i use here.
> Here is a patch that was needed to get it finally compiled
> under 2.6.30.
> http://pastebin.com/m17687d4e

Hmm, the net_ops is new and should only generates a warning with vanilla 2.6.30 . Your kernel source tree is not vanilla 2.6.30, is it? If you need the net_ops change, your tree is probably closer to 2.6.31 rcX . (since it generates a warning on ifconfig up, I know about it and it is just not urgent/immediate yet in 2.6.30)

> Firmware Upload works !!!  and interface comes up as
> ath0.

Yes, the renaming is a visible change.

>
> But: looks like the driver doesnt work or like my
> WPA-Supplicant 0.6.9
>
> Here is a Bootlog and outputs that come:  http://pastebin.com/m232e0dfa

The log looks okay to me... sorry I only use it in AP mode & with WEP, can't help you there.

I did find the driver in AP mode has a curious behavior: it won't talk to a client after loading until I do something like 'iwlist scan' or 'iwpriv card_reset' first. (the latter hangs the machine 1/2 of the time, but iwlist scan is quite reliable and I only need to do it once per reboot of the AP which isn't bad). May be you can try iwlist scan as a client also.


     


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

[Mladen Horvat]

Hin-Tak Leung <hintak_leung <at> yahoo.co.uk> writes:

>
> Hmm, the net_ops is new and should only generates a warning with vanilla
2.6.30 . Your kernel source tree is
> not vanilla 2.6.30, is it? If you need the net_ops change, your tree is
probably closer to 2.6.31 rcX .
> (since it generates a warning on ifconfig up, I know about it and it is just
not urgent/immediate yet in 2.6.30)

Using the offical 2.6.30 kernel from kernel.org:
www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.30.tar.bz2

> > But: looks like the driver doesnt work or like my
> > WPA-Supplicant 0.6.9
> >
> > Here is a Bootlog and outputs that come:  http://pastebin.com/m232e0dfa
>
> The log looks okay to me... sorry I only use it in AP mode & with WEP,can't
help you there.

what does not look great is this stuff:

[ 6133.287000] wrq->u.param.value = 00000000
[ 6133.301000] Temp Solution here. Need to look detail
[ 6133.525000] 1211_readl failed for 5 attempts...Very Serious<3>1211_readl
failed for 5 attempts...Very Serious<3>1211_readl failed for 5 attempts...Very
Serious<3>1211_readl failed for 5 attempts...Very Serious<3>1211_readl failed
for 5 attempts...Very Serious<3>1211_readl failed for 5 attempts...Very
Serious<3>1211_readl failed for 5 attempts...Very Serious<3>1211_readl failed
for 5 attempts...Very Serious<3>1211_readl failed for 5 attempts...Very
Serious<3>1211_readl failed for 5 attempts...Very SeriousgetService failed!
getService failed!



>
> I did find the driver in AP mode has a curious behavior: it won't talk to a
client after loading until I do
> something like 'iwlist scan' or 'iwpriv card_reset' first. (the latter hangs
the machine 1/2 of the time,
> but iwlist scan is quite reliable and I only need to do it once per reboot of
the AP which isn't bad). May be you
> can try iwlist scan as a client also.
>

Scanning works here but no connect to my hidden Network with wpa2.
perhaps there is only a patch missing on the ssid stuff i saw somewhere for
zd1211rw

here some output:
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=8):
     53 70 61 63 65 4e 65 74    MyNet
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
0: 00:15:0c:85:06:66 ssid='' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
skip - SSID mismatch
^^  this is my AP with hidden ssid   but even with non hidden there is no
connection possible.


So i probably think it would be best to somehow fix the firmwareloading in
zd1211rw probaly.

regards








------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

[Hin-Tak Leung]

--- On Thu, 30/7/09, Mladen Horvat <acid-burn@...> wrote:

> Using the offical 2.6.30 kernel from kernel.org:
> www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.30.tar.bz2

Hmm, I have that as well, and the patches I used are those I mentioned... Hmm, did you copy over any compat-wireless headers? Those are beyond 2.6.31.

> what does not look great is this stuff:
>
> [ 6133.287000] wrq->u.param.value = 00000000
> [ 6133.301000] Temp Solution here. Need to look detail
> [ 6133.525000] 1211_readl failed for 5 attempts...Very
> Serious<3>1211_readl
> failed for 5 attempts...Very Serious<3>1211_readl
> failed for 5 attempts...Very
> Serious<3>1211_readl failed for 5 attempts...Very
> Serious<3>1211_readl failed
> for 5 attempts...Very Serious<3>1211_readl failed for
> 5 attempts...Very
> Serious<3>1211_readl failed for 5 attempts...Very
> Serious<3>1211_readl failed
> for 5 attempts...Very Serious<3>1211_readl failed for
> 5 attempts...Very
> Serious<3>1211_readl failed for 5 attempts...Very
> SeriousgetService failed!
> getService failed!

This comes from one of my patches to cope with slow CPUs. I haven't seen them with 3.0 (used to see them in 2.22) - so 3.0 had coped some other way. They are fairly harmless actually, you could increase the 5 if your board is really slow.

> Scanning works here but no connect to my hidden Network
> with wpa2.
> perhaps there is only a patch missing on the ssid stuff i
> saw somewhere for
> zd1211rw

Well, nobody has done anything significant for the rw driver for a year or two now. (other than just adding ids and the odd change to cope with changes elsewhere in the kernel). good luck fixing that or the firmware load problem. If you manage anything, please write back.


     


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs