Nabble - ZyDAS ZD1211 Linux Driver

Re: zd1211 and 802.11a for kernel 2.6.24 or newer

2008-08-13T07:58:44Z

On Wednesday 13 August 2008 16:10:14 Hin-Tak Leung wrote:

> > ZD1211LnxDrv_2_22_0_0.working-on-2.6.25.1-but-ugly.diff
> > patch and
> > it works as well as my modified driver, it load the driver,
> > but mac is same
> > 00:00:00:00:00:00 :).
>
> I have recently upgraded to 2.6.26.2 and the same patch works fine.
>
> Maybe you have a zd1211 chip (rather than the b chip)? 802.11a is a bit
> old. and what vid/pid do you have, exactly?

I have two different wlan sticks, one regular A-Link 802.11b/g (vid/pid
0ace:1215) and the second one is 802.11a/b/g stick from a small company.
Both are with ZD1211B chip (I open these and check it) and these also works
fine on 2.6.18 kernel.

I add mac address by modifying zd1205.c (line 6293...) and after that I can
set ethX up, also "iwconfig ethX" display settings and I can change SSID and
so on, but "iwlist ethX scanning" doesn't do anything except this appear to
the dmesg:

[30535.380635] jiffies = 8769102, lastSetBusy = 8764972, HZ=250
[30535.473084] ZD1211_TX_BUSY is locked over 5 seconds
[30535.473093] jiffies = 8769127, lastSetBusy = 8764972, HZ=250
[30535.569815] ZD1211_TX_BUSY is locked over 5 seconds
[30535.569825] jiffies = 8769152, lastSetBusy = 8764972, HZ=250
[30535.662237] ZD1211_TX_BUSY is locked over 5 seconds
[30535.662248] jiffies = 8769177, lastSetBusy = 8764972, HZ=250
[30535.764299] Wait too long to start Scanning

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

From forum: zd1211-devs

Re: zd1211 and 802.11a for kernel 2.6.24 or newer

2008-08-13T06:10:14Z

--- On Wed, 13/8/08, Kari Kallio <kari.markos@...> wrote:
<snipped>
> I also try
> ZD1211LnxDrv_2_22_0_0.working-on-2.6.25.1-but-ugly.diff
> patch and
> it works as well as my modified driver, it load the driver,
> but mac is same
> 00:00:00:00:00:00 :).

I have recently upgraded to 2.6.26.2 and the same patch works fine.

Maybe you have a zd1211 chip (rather than the b chip)? 802.11a is a bit old.
and what vid/pid do you have, exactly?

Send instant messages to your online friends http://uk.messenger.yahoo.com

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

From forum: zd1211-devs

zd1211 and 802.11a for kernel 2.6.24 or newer

2008-08-13T01:37:51Z

Hello

Is there any workable patch for vendor 2.22 driver and kernel 2.6.24 or newer?
I try driver ZD1211LnxDrv_2_22_0_0__2_6_24.tar.gz first, but it doesn't work.

<dmesg>
zd1211: failed intr_urb
Calling zd1211_InitSetup fails
zd1211: probe of 5-5:1.0 failed with error -5
</dmesg>

So I try to fix it by changing usb_fill_bulk_urb functions to usb_fill_int_urb
and so on, and now it register driver, but ethernet hwaddress is
00:00:00:00:00:00. And now I have no idea what to do :)

I also try ZD1211LnxDrv_2_22_0_0.working-on-2.6.25.1-but-ugly.diff patch and
it works as well as my modified driver, it load the driver, but mac is same
00:00:00:00:00:00 :).

I know there is zd1211rw driver and it works fine, but I really need 802.11a
and kernel 2.6.24 or newer.

--
kari.markos@...

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

From forum: zd1211-devs

Development effort

2008-08-12T23:35:57Z

AoA,
Can any one give me a rough estimate that how much
effort is involved in developing a USB driver for this
1211 chip for an embedded host? Ofcourse the USB
host/802.11 stacks and HW drivers are already
availble.
If someone claims that it would take him/her just 3/4
months to write a complete driver for this chip then
would it be really possible?

Regards
Waqar

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

From forum: zd1211-devs

How to Disable and enable all the interrupts in Linux 2.4

2008-08-06T04:41:30Z

Hi all,

Can anybody provide me some functions to disable all interrupts before critical section and to enable all interrupts after critical section..

I have used cli(); and Sti() functions ..but when i tried to insert the kernel module got the output as shown below...

#insmod ./a.o
insmod: unresolved symbol __sti
insmod: unresolved symbol unregister_chrdev
insmod: unresolved symbol register_chrdev
insmod: unresolved symbol printk
insmod: unresolved symbol __cli

I know that loacl_irq_save(); and local_irq_restore() are for linux 2.6....

Any help could be appreciated...

Thanks,

reddy

Re: Problem when trying ad-hoc patch for zd1211rw

2008-07-15T09:50:47Z

(Sigh...) You are posting to the zd1211-devs list and did not bother
to look around the project's web site for information first?
http://zd1211.wiki.sourceforge.net/
http://zd1211.wiki.sourceforge.net/VendorDriver

--- On Tue, 15/7/08, Mark Ryden <markryde@...> wrote:

> From: Mark Ryden <markryde@...>
> Subject: Re: [zd1211-devs] Problem when trying ad-hoc patch for zd1211rw
> To: "Hin-Tak Leung" <hintak_leung@...>
> Cc: dsd@..., zd1211-devs@..., kune@...
> Date: Tuesday, 15 July, 2008, 5:24 PM
> I have FC9 , x86_64.
>
> ls
> /lib/modules/2.6.25-14.fc9.x86_64/kernel/drivers/net/wireless/zd*
> gives:
>
> /lib/modules/2.6.25-14.fc9.x86_64/kernel/drivers/net/wireless/zd1201.ko
>
> /lib/modules/2.6.25-14.fc9.x86_64/kernel/drivers/net/wireless/zd1211rw:
> zd1211rw.ko
>
> So no zd1211.ko !
>
> I checked also on a 32 bit machine running FC8.
> There I have:
>
> under
> /lib/modules/2.6.23.1-42.fc8/kernel/drivers/net/wireless:
> I have only these two:
> zd1201.ko and
> zd1211rw-mac80211/zd1211rw-mac80211.ko
>
>
> So also no zd1211.ko on 32 bit!
>
> I also checked on FC7 (x86_64) and there I have only:
> zd1201.ko
>
> So where is this zd1211 ? should I download it from
> somewhere ?
> Thanks in advance !
>
> Regards,
> Mark
>
>
>
> On Tue, Jul 15, 2008 at 6:52 PM, Hin-Tak Leung
> <hintak_leung@...> wrote:
> > Mark Ryden wrote:
> >>
> >> Hello,
> >>
> >> Thanks.
> >>
> >> In sys log I see:
> >> usbcore: registered new interface driver zd1201
> >>
> >> I tried "modprobe zd1201".
> >> I see no wireles card with iwconfig or ifconfig
> -a;
> >>
> >> running "iwconfig" gives:
> >>
> >> lo no wireless extensions.
> >>
> >> eth0 no wireless extensions.
> >>
> >> I will try later on 32 bit machine and see.
> >
> > *which* vendor driver are you using? The kernel
> modules
> > are called zd1211 and zd1211b. (and you obviously has
> a
> > device with id 0x1211, not 0x1201.
> >
> >

__________________________________________________________
Not happy with your email address?.
Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

From forum: zd1211-devs

Re: Problem when trying ad-hoc patch for zd1211rw

2008-07-15T09:24:31Z

I have FC9 , x86_64.

ls /lib/modules/2.6.25-14.fc9.x86_64/kernel/drivers/net/wireless/zd*
gives:

/lib/modules/2.6.25-14.fc9.x86_64/kernel/drivers/net/wireless/zd1201.ko

/lib/modules/2.6.25-14.fc9.x86_64/kernel/drivers/net/wireless/zd1211rw:
zd1211rw.ko

So no zd1211.ko !

I checked also on a 32 bit machine running FC8.
There I have:

under /lib/modules/2.6.23.1-42.fc8/kernel/drivers/net/wireless:
I have only these two:
zd1201.ko and
zd1211rw-mac80211/zd1211rw-mac80211.ko

So also no zd1211.ko on 32 bit!

I also checked on FC7 (x86_64) and there I have only:
zd1201.ko

So where is this zd1211 ? should I download it from somewhere ?
Thanks in advance !

Regards,
Mark

On Tue, Jul 15, 2008 at 6:52 PM, Hin-Tak Leung <hintak_leung@...> wrote:

> Mark Ryden wrote:
>>
>> Hello,
>>
>> Thanks.
>>
>> In sys log I see:
>> usbcore: registered new interface driver zd1201
>>
>> I tried "modprobe zd1201".
>> I see no wireles card with iwconfig or ifconfig -a;
>>
>> running "iwconfig" gives:
>>
>> lo no wireless extensions.
>>
>> eth0 no wireless extensions.
>>
>> I will try later on 32 bit machine and see.
>
> *which* vendor driver are you using? The kernel modules
> are called zd1211 and zd1211b. (and you obviously has a
> device with id 0x1211, not 0x1201.
>
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

From forum: zd1211-devs

Re: Problem when trying ad-hoc patch for zd1211rw

2008-07-15T08:52:47Z

Mark Ryden wrote:

> Hello,
>
> Thanks.
>
> In sys log I see:
> usbcore: registered new interface driver zd1201
>
> I tried "modprobe zd1201".
> I see no wireles card with iwconfig or ifconfig -a;
>
> running "iwconfig" gives:
>
> lo no wireless extensions.
>
> eth0 no wireless extensions.
>
> I will try later on 32 bit machine and see.

*which* vendor driver are you using? The kernel modules
are called zd1211 and zd1211b. (and you obviously has a
device with id 0x1211, not 0x1201.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

From forum: zd1211-devs

Re: Problem when trying ad-hoc patch for zd1211rw

2008-07-15T08:39:54Z

Hello,

Thanks.

In sys log I see:
usbcore: registered new interface driver zd1201

I tried "modprobe zd1201".
I see no wireles card with iwconfig or ifconfig -a;

running "iwconfig" gives:

lo no wireless extensions.

eth0 no wireless extensions.

I will try later on 32 bit machine and see.

Regards,
Mark

On Tue, Jul 15, 2008 at 5:57 PM, Hin-Tak Leung <hintak_leung@...> wrote:

> Mark Ryden wrote:
>>
>> Hello,
>> I added:
>> blacklist zd1211rw
>> to /etc/modprobe.d/blacklist
>> and , when there zd1201rw and zd1201 modules are not loaded,
>> I tried plugging the zd1211 USB nic.
>> None of the two drivers were insmoded.
>>
>> lsmod | grep zd
>> gives nothing.
>>
>> I wonder: which kernel are you using ?
>> "uname -r" gives "2.6.25-14.fc9.x86_64" on my machine.
>
> Argh, the whole point of the blacklist file is that it
> stops udevd from loading specific kernel modules for you.
> So udevd doesn't do it for you and you have to modprobe
> yourself, manually.
>
> Hmm, and you did not mention that you are using x86_64 - that's a lot of
> difference, since x86 32-bit is still mainstream, and you may be between
> a rock and a hard place because I know the vendor driver
> has some 64-bit portability issues. On the machine
> where I use the vendor driver it is stock 2.6.25.1 on slackware, 32-bit.
> On the other machine where I have dual drivers for another wireless
> chip, it is 2.6.25.10-91.fc9.x86_64, I believe.
>
>

From forum: zd1211-devs

Re: Problem when trying ad-hoc patch for zd1211rw

2008-07-15T07:54:18Z

Mark Ryden wrote:

> Hello,
> I added:
> blacklist zd1211rw
> to /etc/modprobe.d/blacklist
> and , when there zd1201rw and zd1201 modules are not loaded,
> I tried plugging the zd1211 USB nic.
> None of the two drivers were insmoded.
>
> lsmod | grep zd
> gives nothing.
>
> I wonder: which kernel are you using ?
> "uname -r" gives "2.6.25-14.fc9.x86_64" on my machine.

Argh, the whole point of the blacklist file is that it
stops udevd from loading specific kernel modules for you.
So udevd doesn't do it for you and you have to modprobe
yourself, manually.

Hmm, and you did not mention that you are using x86_64 - that's a lot of
difference, since x86 32-bit is still mainstream, and you may be between
a rock and a hard place because I know the vendor driver
has some 64-bit portability issues. On the machine
where I use the vendor driver it is stock 2.6.25.1 on slackware, 32-bit.
On the other machine where I have dual drivers for another wireless
chip, it is 2.6.25.10-91.fc9.x86_64, I believe.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

From forum: zd1211-devs

Re: Problem when trying ad-hoc patch for zd1211rw

2008-07-15T07:33:35Z

Hello,
I added:
blacklist zd1211rw
to /etc/modprobe.d/blacklist
and , when there zd1201rw and zd1201 modules are not loaded,
I tried plugging the zd1211 USB nic.
None of the two drivers were insmoded.

lsmod | grep zd
gives nothing.

I wonder: which kernel are you using ?
"uname -r" gives "2.6.25-14.fc9.x86_64" on my machine.

When plugging the usb nic I see this in the syslog:

kernel: usb 1-4: new high speed USB device using ehci_hcd and address 5
kernel: usb 1-4: configuration #1 chosen from 1 choice
kernel: usb 1-4: New USB device found, idVendor=0ace, idProduct=1211
kernel: usb 1-4: New USB device strings: Mfr=16, Product=32, SerialNumber=0
kernel: usb 1-4: Product: USB2.0 WLAN
kernel: usb 1-4: Manufacturer: ZyDAS

but that's all I get.

Any idea? I am bewildered.

Regards,
Mark

On Tue, Jul 15, 2008 at 4:43 PM, Hin-Tak Leung <hintak_leung@...> wrote:

> Mark Ryden wrote:
>>
>> Hi,
>>>
>>> use the vendor driver.
>>
>> In fact it seems to me that it is impossible.
>>
>> I have 0ace:1211 as vendor id/product id.
>> The zd1201.c seems *not* to support it.
>> In the usb device id table, we have only
>>
>> {USB_DEVICE(0x0ace, 0x1201)}, /* ZyDAS ZD1201 Wireless USB Adapter */
>>
>> (see zd1201.c).
>>
>> When I try to plug in the USB zd1211 nic, the zd1211rw driver is the
>> one that is loaded.
>>
>> (the zd1211rw driver has this vendor id/product id
>> combination; see
>> { USB_DEVICE(0x0ace, 0x1211), .driver_info = DEVICE_ZD1211 },
>> in zd_usb.c.
>>
>> So I cannot even use the vendor driver, and I am totally stuck.
>
> You can tell udevd not to autoload kernel modules by putting
> them in the blacklist file. It is /etc/modprobe.d/blacklist on my system
> but maybe somewhere else under /etc/modprobe* . This is the standard
> way of trying alternative kernel-module drivers - put all of them
> in blacklist, and do modprobe explicitly to load each of them.
>
> I have both the vendor driver and the rw driver for this,
> and another alternative pairs of drivers for a different wireless chip
> on another machine.
>
>
>

From forum: zd1211-devs

Re: Problem when trying ad-hoc patch for zd1211rw

2008-07-15T06:49:09Z

Mark Ryden wrote:
> Hello,
> I must say that I am a bit disappointed about that my problem is
> still unresolved ; I assume probably I am not the only one who
> encountered
> it. Though I googled for solution, I could not find some appropriate
> solution. Could anybody help in this point ?
>

I am surprised you feel *entitled* to be disappointed. You have the source code
of two drivers and you have the hardware, which is exactly the same situation
as me. Feel free to look inside.

I am not involved with either driver but just happened to have spent some time
with the vendor driver because I needed master mode, which the rw driver does
not provide - and I posted the patch a few weeks ago. I have spent a little time
tracing the code path in the rw driver for you - which you could have done
yourself.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

From forum: zd1211-devs

Re: Problem when trying ad-hoc patch for zd1211rw

2008-07-15T06:36:56Z

Mark Ryden wrote:

> Hi,
>> use the vendor driver.
> In fact it seems to me that it is impossible.
>
> I have 0ace:1211 as vendor id/product id.
> The zd1201.c seems *not* to support it.
> In the usb device id table, we have only
>
> {USB_DEVICE(0x0ace, 0x1201)}, /* ZyDAS ZD1201 Wireless USB Adapter */
>
> (see zd1201.c).
>
> When I try to plug in the USB zd1211 nic, the zd1211rw driver is the
> one that is loaded.
>
> (the zd1211rw driver has this vendor id/product id
> combination; see
> { USB_DEVICE(0x0ace, 0x1211), .driver_info = DEVICE_ZD1211 },
> in zd_usb.c.
>
> So I cannot even use the vendor driver, and I am totally stuck.

You can tell udevd not to autoload kernel modules by putting
them in the blacklist file. It is /etc/modprobe.d/blacklist on my system
but maybe somewhere else under /etc/modprobe* . This is the standard
way of trying alternative kernel-module drivers - put all of them
in blacklist, and do modprobe explicitly to load each of them.

I have both the vendor driver and the rw driver for this,
and another alternative pairs of drivers for a different wireless chip
on another machine.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

From forum: zd1211-devs

Re: Problem when trying ad-hoc patch for zd1211rw

2008-07-15T02:38:29Z

Hi,
> use the vendor driver.
In fact it seems to me that it is impossible.

I have 0ace:1211 as vendor id/product id.
The zd1201.c seems *not* to support it.
In the usb device id table, we have only

{USB_DEVICE(0x0ace, 0x1201)}, /* ZyDAS ZD1201 Wireless USB Adapter */

(see zd1201.c).

When I try to plug in the USB zd1211 nic, the zd1211rw driver is the
one that is loaded.

(the zd1211rw driver has this vendor id/product id
combination; see
{ USB_DEVICE(0x0ace, 0x1211), .driver_info = DEVICE_ZD1211 },
in zd_usb.c.

So I cannot even use the vendor driver, and I am totally stuck.

Is there a way out ?
Regards,
Mark

On Fri, Jul 11, 2008 at 9:34 PM, Hin-Tak Leung <hintak_leung@...> wrote:

> I am going to make myself very unpopular to suggest this: use the vendor
> driver.
> Here is a passage from around line 236 of zd_mac.c:
>
> /* At this point, the vendor driver downloads the whole firmware
> * image, hacks around with version IDs, and uploads it again,
> * completely overwriting the boot code. We do not do this here as
> * it is not required on any tested devices, and it is suspected to
> * cause problems. */
>
> So the zd1211rw code doesn't cope with your situation, and it is a known
> problem. I don't think you will get better answers at linux-wireless mailing
> list. The manufacturer is being a bit funny in mislabelling the devices.
> (And, really, you should have approached your distro's bug tracking system
> first).
>
> Mark Ryden wrote:
>>
>> Thanks!
>>
>> I am looking for a more accurate answer. What should I do with this
>> firmware problem ? I do not want to delve into the zd1211rw code trying to
>> solve it.
>> Didn't other people encounter this problem ? Maybe the zd1211rw
>> developers can
>> try to hint as to what the problem is ?
>>
>> Or maybe should I forward this message to the linux wireless mailing list
>> ?
>>
>> I am quite stuck with this problem,as you can see.
>>
>> Regards,
>> Mark Ryden
>>
>> On Fri, Jul 11, 2008 at 12:31 PM, Hin-Tak Leung
>> <htl10@...> wrote:
>>>
>>> Hmm, a quick look around the net says your message possibly comes from
>>> a 1211 lying about being a 1211b or vice versa.
>>>
>>> --- On Fri, 11/7/08, Mark Ryden <markryde@...> wrote:
>>>
>>>> From: Mark Ryden <markryde@...>
>>>> Subject: Re: [zd1211-devs] Problem when trying ad-hoc patch for zd1211rw
>>>> To: "Hin-Tak Leung" <hintak_leung@...>
>>>> Cc: zd1211-devs@..., dsd@...,
>>>> kune@...
>>>> Date: Friday, 11 July, 2008, 6:48 AM
>>>> Hello,
>>>> Thanks!
>>>>
>>>> Could it be a probelem of firmware version ?
>>>> How can I know what is the zd1211 firmware version I have ?
>>>>
>>>> I have these files under /lib/firmware/zd1211/:
>>>>
>>>> ls -al /lib/firmware/zd1211/
>>>> total 72
>>>> drwxr-xr-x 2 root root 4096 2008-05-14 19:48 .
>>>> drwxr-xr-x 3 root root 4096 2008-05-06 13:35 ..
>>>> -rw-r--r-- 1 root root 4018 2007-10-12 14:44 zd1211b_ub
>>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211b_uph
>>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211b_uphm
>>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211b_uphr
>>>> -rw-r--r-- 1 root root 3584 2007-10-12 14:44 zd1211b_ur
>>>> -rw-r--r-- 1 root root 4018 2007-10-12 14:44 zd1211_ub
>>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211_uph
>>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211_uphm
>>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211_uphr
>>>> -rw-r--r-- 1 root root 3584 2007-10-12 14:44 zd1211_ur
>>>>
>>>> Regards,
>>>> Mark
>>>>
>>>> On Thu, Jul 10, 2008 at 6:41 PM, Hin-Tak Leung
>>>> <hintak_leung@...> wrote:
>>>>>
>>>>> It is as it says, can't load firmware. If you had
>>>>
>>>> not used this USB nic
>>>>>
>>>>> on a machine before, it is likely you did not have
>>>>
>>>> them installed.
>>>>>
>>>>> They should be under /lib/firmware/zd1211 . In
>>>>
>>>> whatever mode,
>>>>>
>>>>> the driver still needs the firmware.
>>>>>
>>>>> Mark Ryden wrote:
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I have build and booted the last linux
>>>>
>>>> wireless-netx-2.6 tree:
>>>>>>
>>>>>> (
>>>>>>
>>>>
>>>> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next-2.6.git)
>>>>>>
>>>>>> This tree includes the ad-hoc patch for zd1211rw.
>>>>>>
>>>>>> See:
>>>>>>
>>>> http://marc.info/?l=linux-wireless&m=121514338914960&w=2
>>>>>>
>>>>>> I tried to run these two actions:
>>>>>> (I must say that I did not tried this USB nic with
>>>>
>>>> other modes before on
>>>>>>
>>>>>> this
>>>>>> machine):
>>>>>>
>>>>>> iwconfig wlan0 mode ad-hoc
>>>>>> ifconfig wlan0 up
>>>>>>
>>>>>> I get:
>>>>>> SIOCSIFFLAGS: Connection timed out
>>>>>>
>>>>>> in in the kernel log I get:
>>>>>> Jul 10 15:40:53 kernel: usb 1-4: firmware version
>>>>
>>>> 0x4330 and device
>>>>>>
>>>>>> bootcode version 0x4810 differ
>>>>>> Jul 10 15:40:54 kernel: usb 1-4: USB control
>>>>
>>>> request for firmware
>>>>>>
>>>>>> upload failed. Error number -110
>>>>>> Jul 10 15:40:54 kernel: zd1211rw 1-4:1.0:
>>>>
>>>> couldn't load firmware.
>>>>>>
>>>>>> Error number -110
>>>>>>
>>>>>> What should I do ? is it has to do with some
>>>>
>>>> firmware mismatch ?
>>>>>>
>>>>>> Any ideas?
>>>>>>
>>>>>> lsusb -v shows:
>>>>>> Bus 001 Device 003: ID 0ace:1211 ZyDAS 802.11b/g
>>>>
>>>> USB2 WiFi
>>>>>>
>>>>>> Device Descriptor:
>>>>>> bLength 18
>>>>>> bDescriptorType 1
>>>>>> bcdUSB 2.00
>>>>>> bDeviceClass 255 Vendor Specific Class
>>>>>> bDeviceSubClass 255 Vendor Specific
>>>>
>>>> Subclass
>>>>>>
>>>>>> bDeviceProtocol 255 Vendor Specific
>>>>
>>>> Protocol
>>>>>>
>>>>>> bMaxPacketSize0 64
>>>>>> idVendor 0x0ace ZyDAS
>>>>>> idProduct 0x1211 802.11b/g USB2 WiFi
>>>>>> bcdDevice 48.10
>>>>>> iManufacturer 16
>>>>>> iProduct 32
>>>>>> iSerial 0
>>>>>> bNumConfigurations 1
>>>>>> Configuration Descriptor:
>>>>>> bLength 9
>>>>>> bDescriptorType 2
>>>>>> wTotalLength 46
>>>>>> bNumInterfaces 1
>>>>>> bConfigurationValue 1
>>>>>> iConfiguration 0
>>>>>> bmAttributes 0x80
>>>>>> (Bus Powered)
>>>>>> MaxPower 500mA
>>>>>> Interface Descriptor:
>>>>>> bLength 9
>>>>>> ...
>>>>>>
>>>>>> Regards,
>>>>>> Mark Ryden
>>>>>>
>>>>>>
>>>>
>>>> -------------------------------------------------------------------------
>>>>>>
>>>>>> Sponsored by: SourceForge.net Community Choice
>>>>
>>>> Awards: VOTE NOW!
>>>>>>
>>>>>> Studies have shown that voting for your favorite
>>>>
>>>> open source project,
>>>>>>
>>>>>> along with a healthy diet, reduces your potential
>>>>
>>>> for chronic lameness
>>>>>>
>>>>>> and boredom. Vote Now at
>>>>
>>>> http://www.sourceforge.net/community/cca08
>>>>>>
>>>>>> _______________________________________________
>>>>>> Zd1211-devs mailing list -
>>>>
>>>> http://zd1211.wiki.sourceforge.net/
>>>>>>
>>>>>> Unsubscribe:
>>>>
>>>> https://lists.sourceforge.net/lists/listinfo/zd1211-devs
>>>>>
>>>
>>> __________________________________________________________
>>> Not happy with your email address?.
>>> Get the one you really want - millions of new email addresses available
>>> now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html
>>>
>>>
>>
>
>

From forum: zd1211-devs

Re: Problem when trying ad-hoc patch for zd1211rw

2008-07-14T22:19:10Z

Hello,
I must say that I am a bit disappointed about that my problem is
still unresolved ; I assume probably I am not the only one who
encountered
it. Though I googled for solution, I could not find some appropriate
solution. Could anybody help in this point ?

Regards,
Mark

On Sun, Jul 13, 2008 at 7:17 PM, Hin-Tak Leung <hintak_leung@...> wrote:

> Daniel Drake wrote:
>>
>> Hin-Tak Leung wrote:
>>>
>>> "Because it doesn't work for your device"? That paragraph seems
>>> to suggest that a solution to your problem is in the vendor driver
>>> but is considered to ugly to copy. There is a clean
>>> driver which does not work for your device, or an ugly driver
>>> which does, but not one that is both clean and work for your device
>>> (at the moment).
>>
>> Let's not jump to conclusions here.. nobody said the vendor driver works.
>>
>> I personally think it is unlikely that the code in question has anything
>> to do with this problem. You seem to have only reached that conclusion based
>> on the presence of the "mismatch" message, which harmlessly appears for the
>> majority of zd1211 devices. Also, in theory, what the vendor driver is doing
>> that we don't is completely irrelevant since we don't do any version
>> checking beyond that point.
>
> I did not reach that conclusion based on the mismatch message alone, but
> by looking at what is supposed to happen *after* that mismatch message, and
> that's when I saw that comment in the code. That comment is in the part
> of the zd1211rw driver for handling or not-handling mismatches. It seems
> that *some* mismatches are handled, but *some* mismatches are intentionally
> not handled because they are considered too ugly.
>
> Maybe the person who wrote that comment should come forward and explain what
> he
> meant when he wrote it (assuming that person is still on the list), and
> clarify
> that comment.
>
>
>
>
>
>
>

From forum: zd1211-devs

Re: Problem when trying ad-hoc patch for zd1211rw

2008-07-13T09:10:02Z

Daniel Drake wrote:

> Hin-Tak Leung wrote:
>> "Because it doesn't work for your device"? That paragraph seems
>> to suggest that a solution to your problem is in the vendor driver
>> but is considered to ugly to copy. There is a clean
>> driver which does not work for your device, or an ugly driver
>> which does, but not one that is both clean and work for your device
>> (at the moment).
>
> Let's not jump to conclusions here.. nobody said the vendor driver works.
>
> I personally think it is unlikely that the code in question has anything
> to do with this problem. You seem to have only reached that conclusion
> based on the presence of the "mismatch" message, which harmlessly
> appears for the majority of zd1211 devices. Also, in theory, what the
> vendor driver is doing that we don't is completely irrelevant since we
> don't do any version checking beyond that point.

I did not reach that conclusion based on the mismatch message alone, but
by looking at what is supposed to happen *after* that mismatch message, and
that's when I saw that comment in the code. That comment is in the part
of the zd1211rw driver for handling or not-handling mismatches. It seems
that *some* mismatches are handled, but *some* mismatches are intentionally
not handled because they are considered too ugly.

Maybe the person who wrote that comment should come forward and explain what he
meant when he wrote it (assuming that person is still on the list), and clarify
that comment.

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

From forum: zd1211-devs

Re: Problem when trying ad-hoc patch for zd1211rw

2008-07-13T08:49:25Z

Hi,
Thanks for your response.

I have a question, regarding the bottom line:
Should I understand from what was said here that I should simply
ignore this message ?

Regardsm
Mark

On Sun, Jul 13, 2008 at 6:42 PM, Daniel Drake <dsd@...> wrote:

> Hin-Tak Leung wrote:
>>
>> "Because it doesn't work for your device"? That paragraph seems
>> to suggest that a solution to your problem is in the vendor driver
>> but is considered to ugly to copy. There is a clean
>> driver which does not work for your device, or an ugly driver
>> which does, but not one that is both clean and work for your device
>> (at the moment).
>
> Let's not jump to conclusions here.. nobody said the vendor driver works.
>
> I personally think it is unlikely that the code in question has anything to
> do with this problem. You seem to have only reached that conclusion based on
> the presence of the "mismatch" message, which harmlessly appears for the
> majority of zd1211 devices. Also, in theory, what the vendor driver is doing
> that we don't is completely irrelevant since we don't do any version
> checking beyond that point.
>
> Daniel
>

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

From forum: zd1211-devs

Re: Problem when trying ad-hoc patch for zd1211rw

2008-07-13T07:43:45Z

Hin-Tak Leung wrote:
> "Because it doesn't work for your device"? That paragraph seems
> to suggest that a solution to your problem is in the vendor driver
> but is considered to ugly to copy. There is a clean
> driver which does not work for your device, or an ugly driver
> which does, but not one that is both clean and work for your device
> (at the moment).

Let's not jump to conclusions here.. nobody said the vendor driver works.

I personally think it is unlikely that the code in question has anything
to do with this problem. You seem to have only reached that conclusion
based on the presence of the "mismatch" message, which harmlessly
appears for the majority of zd1211 devices. Also, in theory, what the
vendor driver is doing that we don't is completely irrelevant since we
don't do any version checking beyond that point.

Daniel

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

From forum: zd1211-devs

Re: Problem when trying ad-hoc patch for zd1211rw

2008-07-13T07:34:22Z

Mark Ryden wrote:
> Hello,
>> Here is a passage from around line 236 of zd_mac.c:
>
> 1) At which tree are you you looking ?
> I have the wireless-next-2.6 .git tree (updated as true for today).
> There is no such comment in this file

Sorry, quoted the wrong file - it is zd_usb.c -
I had wireless-testing, but that paragraph is in wireless-next-2.6
too:
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-2.6.git;a=blob_plain;f=drivers/net/wireless/zd1211rw/zd_usb.c;hb=HEAD
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=blob_plain;f=drivers/net/wireless/zd1211rw/zd_usb.c;hb=HEAD

>
> 2)
>> I am going to make myself very unpopular
> This is indeed so. Why should I not use the new driver ?
> this firmware question should be solved; it has nothing to do with
> the new AD-HOC feature, which was added recently.

"Because it doesn't work for your device"? That paragraph seems
to suggest that a solution to your problem is in the vendor driver
but is considered to ugly to copy. There is a clean
driver which does not work for your device, or an ugly driver
which does, but not one that is both clean and work for your device
(at the moment).

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

From forum: zd1211-devs

Re: Problem when trying ad-hoc patch for zd1211rw

2008-07-13T03:44:39Z

Hello,
> Here is a passage from around line 236 of zd_mac.c:

1) At which tree are you you looking ?
I have the wireless-next-2.6 .git tree (updated as true for today).
There is no such comment in this file

2)
> I am going to make myself very unpopular
This is indeed so. Why should I not use the new driver ?
this firmware question should be solved; it has nothing to do with
the new AD-HOC feature, which was added recently.

(Namely, the addition of the AD-HOC feadture has nothing to do with
this firmware question.)

Regards,
Mark R.

On Fri, Jul 11, 2008 at 9:34 PM, Hin-Tak Leung <hintak_leung@...> wrote:

From forum: zd1211-devs

Re: Problem when trying ad-hoc patch for zd1211rw

2008-07-11T11:27:19Z

I am going to make myself very unpopular to suggest this: use the vendor driver.
Here is a passage from around line 236 of zd_mac.c:

/* At this point, the vendor driver downloads the whole firmware

* image, hacks around with version IDs, and uploads it again,

* completely overwriting the boot code. We do not do this here as

* it is not required on any tested devices, and it is suspected to

* cause problems. */

So the zd1211rw code doesn't cope with your situation, and it is a known
problem. I don't think you will get better answers at linux-wireless mailing
list. The manufacturer is being a bit funny in mislabelling the devices.
(And, really, you should have approached your distro's bug tracking system first).

Mark Ryden wrote:

> Thanks!
>
> I am looking for a more accurate answer. What should I do with this
> firmware problem ? I do not want to delve into the zd1211rw code trying to
> solve it.
> Didn't other people encounter this problem ? Maybe the zd1211rw developers can
> try to hint as to what the problem is ?
>
> Or maybe should I forward this message to the linux wireless mailing list ?
>
> I am quite stuck with this problem,as you can see.
>
> Regards,
> Mark Ryden
>
> On Fri, Jul 11, 2008 at 12:31 PM, Hin-Tak Leung
> <htl10@...> wrote:
>> Hmm, a quick look around the net says your message possibly comes from
>> a 1211 lying about being a 1211b or vice versa.
>>
>> --- On Fri, 11/7/08, Mark Ryden <markryde@...> wrote:
>>
>>> From: Mark Ryden <markryde@...>
>>> Subject: Re: [zd1211-devs] Problem when trying ad-hoc patch for zd1211rw
>>> To: "Hin-Tak Leung" <hintak_leung@...>
>>> Cc: zd1211-devs@..., dsd@..., kune@...
>>> Date: Friday, 11 July, 2008, 6:48 AM
>>> Hello,
>>> Thanks!
>>>
>>> Could it be a probelem of firmware version ?
>>> How can I know what is the zd1211 firmware version I have ?
>>>
>>> I have these files under /lib/firmware/zd1211/:
>>>
>>> ls -al /lib/firmware/zd1211/
>>> total 72
>>> drwxr-xr-x 2 root root 4096 2008-05-14 19:48 .
>>> drwxr-xr-x 3 root root 4096 2008-05-06 13:35 ..
>>> -rw-r--r-- 1 root root 4018 2007-10-12 14:44 zd1211b_ub
>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211b_uph
>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211b_uphm
>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211b_uphr
>>> -rw-r--r-- 1 root root 3584 2007-10-12 14:44 zd1211b_ur
>>> -rw-r--r-- 1 root root 4018 2007-10-12 14:44 zd1211_ub
>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211_uph
>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211_uphm
>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211_uphr
>>> -rw-r--r-- 1 root root 3584 2007-10-12 14:44 zd1211_ur
>>>
>>> Regards,
>>> Mark
>>>
>>> On Thu, Jul 10, 2008 at 6:41 PM, Hin-Tak Leung
>>> <hintak_leung@...> wrote:
>>>> It is as it says, can't load firmware. If you had
>>> not used this USB nic
>>>> on a machine before, it is likely you did not have
>>> them installed.
>>>> They should be under /lib/firmware/zd1211 . In
>>> whatever mode,
>>>> the driver still needs the firmware.
>>>>
>>>> Mark Ryden wrote:
>>>>> Hello,
>>>>>
>>>>> I have build and booted the last linux
>>> wireless-netx-2.6 tree:
>>>>>
>>>>> (
>>>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next-2.6.git)
>>>>> This tree includes the ad-hoc patch for zd1211rw.
>>>>>
>>>>> See:
>>>>>
>>> http://marc.info/?l=linux-wireless&m=121514338914960&w=2
>>>>> I tried to run these two actions:
>>>>> (I must say that I did not tried this USB nic with
>>> other modes before on
>>>>> this
>>>>> machine):
>>>>>
>>>>> iwconfig wlan0 mode ad-hoc
>>>>> ifconfig wlan0 up
>>>>>
>>>>> I get:
>>>>> SIOCSIFFLAGS: Connection timed out
>>>>>
>>>>> in in the kernel log I get:
>>>>> Jul 10 15:40:53 kernel: usb 1-4: firmware version
>>> 0x4330 and device
>>>>> bootcode version 0x4810 differ
>>>>> Jul 10 15:40:54 kernel: usb 1-4: USB control
>>> request for firmware
>>>>> upload failed. Error number -110
>>>>> Jul 10 15:40:54 kernel: zd1211rw 1-4:1.0:
>>> couldn't load firmware.
>>>>> Error number -110
>>>>>
>>>>> What should I do ? is it has to do with some
>>> firmware mismatch ?
>>>>> Any ideas?
>>>>>
>>>>> lsusb -v shows:
>>>>> Bus 001 Device 003: ID 0ace:1211 ZyDAS 802.11b/g
>>> USB2 WiFi
>>>>> Device Descriptor:
>>>>> bLength 18
>>>>> bDescriptorType 1
>>>>> bcdUSB 2.00
>>>>> bDeviceClass 255 Vendor Specific Class
>>>>> bDeviceSubClass 255 Vendor Specific
>>> Subclass
>>>>> bDeviceProtocol 255 Vendor Specific
>>> Protocol
>>>>> bMaxPacketSize0 64
>>>>> idVendor 0x0ace ZyDAS
>>>>> idProduct 0x1211 802.11b/g USB2 WiFi
>>>>> bcdDevice 48.10
>>>>> iManufacturer 16
>>>>> iProduct 32
>>>>> iSerial 0
>>>>> bNumConfigurations 1
>>>>> Configuration Descriptor:
>>>>> bLength 9
>>>>> bDescriptorType 2
>>>>> wTotalLength 46
>>>>> bNumInterfaces 1
>>>>> bConfigurationValue 1
>>>>> iConfiguration 0
>>>>> bmAttributes 0x80
>>>>> (Bus Powered)
>>>>> MaxPower 500mA
>>>>> Interface Descriptor:
>>>>> bLength 9
>>>>> ...
>>>>>
>>>>> Regards,
>>>>> Mark Ryden
>>>>>
>>>>>
>>> -------------------------------------------------------------------------
>>>>> Sponsored by: SourceForge.net Community Choice
>>> Awards: VOTE NOW!
>>>>> Studies have shown that voting for your favorite
>>> open source project,
>>>>> along with a healthy diet, reduces your potential
>>> for chronic lameness
>>>>> and boredom. Vote Now at
>>> http://www.sourceforge.net/community/cca08
>>>>> _______________________________________________
>>>>> Zd1211-devs mailing list -
>>> http://zd1211.wiki.sourceforge.net/
>>>>> Unsubscribe:
>>> https://lists.sourceforge.net/lists/listinfo/zd1211-devs
>>>>
>>
>> __________________________________________________________
>> Not happy with your email address?.
>> Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html
>>
>>
>

From forum: zd1211-devs