Thread: Re: [zd1211-devs] zd1211rw couldn't load firmware. Error number -145 with Kernel 2.6.30
Status: Beta
Brought to you by:
mayne
From: Hin-Tak L. <hin...@ya...> - 2009-07-29 14:30:16
Attachments:
0001-2.6.30-irqreturn_t-breakage.patch
|
--- On Wed, 29/7/09, Mladen Horvat <aci...@op...> 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. |
From: Mladen H. <aci...@op...> - 2009-07-29 14:59:50
|
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 |
From: Hin-Tak L. <hin...@ya...> - 2009-07-29 15:28:02
|
--- On Wed, 29/7/09, Mladen Horvat <aci...@op...> 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 :-). |
From: Mladen H. <aci...@op...> - 2009-07-30 13:05:17
|
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 |
From: Hin-Tak L. <hin...@ya...> - 2009-07-30 13:27:50
|
--- On Thu, 30/7/09, Mladen Horvat <aci...@op...> 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. |
From: Mladen H. <aci...@op...> - 2009-07-30 14:05:05
|
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 |
From: Hin-Tak L. <hin...@ya...> - 2009-07-30 14:19:53
|
--- On Thu, 30/7/09, Mladen Horvat <aci...@op...> 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. |