Page 2 of 2

Posted: Wed 10 Oct 2007, 01:13
by CHLee
Thanks tempestuous very much ! I try the zd1211+b-2.21.0.0-k2.6.21.7.pet last night , it work very well with Puppy3.00 . I am very happy .
My WiFi card (USB) was TP-Link TL-WN322G , I bought it last week .
Thanks again !
Best regards,
C.H. Lee

Still not working

Posted: Thu 11 Oct 2007, 08:55
by ecomoney
Hi tempestuous

Sorry for getting back to you late with this, have been busy tidying up the ecopup project for shelving for a while, and getting started on the next ce release (3.3ce).

I am glad this thread is helping so many people get connected, the zydas is a very cheap and common chipset and its unworking state in stock puppy seems to be causing a lot of problems for people. Thanks for your work. Its still not working for me on 2.15ce however.

After installing your .pet I do the "modprobe zydas1211b" and "depmod". I finally figured out how to get the contents of the console back to a text file. "dmesg > dmesg.txt" is attached below, zipped up so the forum will accept it.

Im moving over to 3.00 full time now to prepare for work on the next ce project, perhaps I wil have better luck there.

Version 3 install

Posted: Thu 11 Oct 2007, 12:15
by ecomoney
Hello Again,

Tried the driver you compiled for 3.00 series and got a similar result (error -5) here are the results from dmesg .

Im beginning to think there may be something peculiar about this usb adaptor.

Posted: Fri 12 Oct 2007, 10:34
by tempestuous
ecomoney,
I see one or two reports of the same problem as yours on the web. It appears that no one has come up with a definite solution, but there is a hack mentioned here -
http://sourceforge.net/mailarchive/mess ... nabble.com
I can compile this hacked driver tomorrow, if you're interested to try it.

Posted: Fri 12 Oct 2007, 20:52
by tempestuous
Here is the zd1211b driver, "vendor-based community" version, hacked to avoid this load error

Code: Select all

zd1211: failed intr_urb
zd1211:USB ST Code = -22
zd1211b: probe of 1-1:1.0 failed with error -5

Posted: Sat 13 Oct 2007, 07:44
by ecomoney
Hi tempestuous

Tried the new driver on my 3.00 setup. Do I need to start afresh with a clean pup_save.2fs? I did

Code: Select all

rmmod zd1211rw
rmmod zd1211b
modprobe zd1211b
none of these commands gave any output.

I did a
dmesg > demsg.txt

and then a

zip dmesg.zip dmesg.txt

looking on dmesg Im getting the dreaded error -5 again

Posted: Sat 13 Oct 2007, 15:57
by tempestuous
I did some more reading on the zd1211-devs mailing list. It's looking more and more like a problem with the way that the driver (all versions) passes data to the USB interface ... especially USB1.1 interfaces.

I still think it's worth trying the wifi adaptor on a different computer, preferably one with a USB2.0 interface.
Try the zd1211rw module first, then the zd1211b.
This might not sound like a solution, but it would help isolate the problem.

Posted: Sat 13 Oct 2007, 18:22
by ecomoney
Hi there, tried the "hacked" driver on my Dell c630 laptop, load autousb in the network wizard loaded the zd1211rw but didnt bring up any new interfaces. I then loaded your .pet did

Code: Select all

rmmod zd1211rw
to remove the previous driver, then

Code: Select all

modprobe zd1211b
and got

[/code]FATAL: Module zd1211b not found[/code]

does this driver have a different name?

Posted: Sat 13 Oct 2007, 20:49
by tempestuous
The module is "zd1211b". And the dotpet installer should automatically run "depmod" at the end of the installation, so the new module can be found.
Maybe you're using Puppy 2.17 or 3.00?
zd1211b-hack01-k2.6.18.1.pet is only compatible with Puppy 2.12-2.16

But if you're testing on a different computer, I'm hoping that the hacked version is not necessary.
It would probably be better to try the zd1211+b-v2.21.0.0-k2.6.18.1.pet

Success!!!

Posted: Sun 14 Oct 2007, 06:34
by ecomoney
Success! I now have a working interface using ecopup!!! Thank you for your perseverance in this tempestuous.

Where I live I have no wireless network, although I can usually see two faint locked hotspots. I cant see either of these using the new driver and car, although I suspect that this may be due to the lower sensitivity of the usb adaptor (it was the cheapest on the market). I will take my laptop somewhere I know there is a strong signal and I can do some further testing. I will confirm the results.

While you have the tools at hand, would you go to the trouble of compiling the hacked version for 3.xx series puppy also. No wonder hardware support for puppy is shrinking with all of these kernel changes.

Posted: Sun 14 Oct 2007, 08:14
by tempestuous
OK, so let's just clarify, using Pluscom WU-ZD1211B ver 1.0,
device id 0ace 1215
in Puppy v2.15ce (or remaster thereof);

- zd1211rw driver definitely fails.
- zd1211+b-v2.21.0.0-k2.6.18.1.pet (latest Vendor driver) fails?
- zd1211b "hacked" Vendor-based community driver works.

... and changing computer/USB interface made no difference?

Progress

Posted: Mon 15 Oct 2007, 07:18
by ecomoney
Yes, sorry about my exuberence at getting this working at last (it was a donation and I didnt want to see it go to waste).

Ive tested on my laptop (usb2.0)and my desktop (usb1.1)

- The stock zd1211rw supplied with puppy 2.15 and 3.00 doesnt work on either machine
- The zd1211+b-v2.21.0.0-k2.6.18.1.pet (latest Vendor driver) also doesnt work on either machine in puppy 2.15ce or 3.00
- The zd1211b "hacked" Vendor-based community driver works on both machines (usb1.1 and 2.0)in 2.15ce :D as in I can see a new interface (wlan0).

However, I cant seem to find any wireless networks, Im currently at home and I have no wireless network here, however there is an encrypted network from one of my neighbours which is visible using my linksys hp200 pcmcia card and ndiswrapper. It may be that the pluscom zd1211b usb model has less sensitivity. Under the pcmcia card Im getting a signal strength in rutlit of -91, but I dont know if this is good or bad, I know its only available near my window so I wuold assume its weak). My wireless router has been held up by the postal strike here.

Hope this is of use, many thanks again for your help.

Posted: Mon 15 Oct 2007, 09:21
by tempestuous
Thanks for confirming your results.
I don't think you can make too many assumptions about the device's performance until you connect to a wifi access point within reasonable proximity.
But don't be too upset if the device has limited range. I know that there are other cheap wifi devices which are infamous for having limited range. A classic example is Marvell chipset-based devices.

Sometimes you can "tweak" the device's settings to improve performance. Run this command to determine what unique iwpriv settings are available with your device -

Code: Select all

iwpriv wlan0
One possibility is to force the device into pure B mode or pure G mode, which might help performance -

Code: Select all

iwpriv wlan0 set_mac_mode <MAC mode>
1: Mixed Mode
2: Pure G Mode
3: Pure B Mode

I have now added the "hacked" version of the zd1211b driver for Puppy v3.00 to the earlier post.

Posted: Mon 15 Oct 2007, 12:22
by ecomoney
Very many thanks for that, I will try it when I get home to try and see those weak networks and test the driver on puppy 3.00. I will be able to give you a better result when the wireless router arrives. (I think I already mentioned) were planning a community wireless network based on the mesh principle arounf the community centre where I work. Range and penetration are going to play a big role. Were starting off the network using 2.15ce based ecopup 7.2, but will be rolling out the future ecopup 0.8 based on puppy 3.02ce when that arrives. Im hoping to buy a few of these wireless access keys if the reception turns out to be good, as they are the cheapest I have seen. If the range isnt that great and were going to need more wireless routers it may turn out to be false economy. The tips you provided on how to make the key use the g or b bands exclusively will no doubt turn out to be very useful in a tricky situation. Are the rumours correct that the older "B" standard has greater range and penetration? If you have any more tips you can think of please let me know. Thanks for all of your hard work, research and perseverance in getting this finally work.

Posted: Wed 02 Apr 2008, 13:57
by tinyos
i got the same problem.
i will test the pet
thanks

Posted: Wed 30 Apr 2008, 16:14
by GrinningLeopard
Installed the hacked .pet on 3.01. Now have new 'wlan0' interface which the network wizard recognises, but reports 'no networks detected' even when I sit on my router. Not literally :wink: My network is WEP, g, maybe that's part of the problem. I'll take it for a wander and see if I can find some random unsecured one... ah yes USB is 1.1 - don't know if that is relevent.

Posted: Sat 03 May 2008, 22:06
by GrinningLeopard
okay
Have been playing around with this and had no luck. I've tried both drivers on two different laptops (1.1 and 2.0 usb) I've also tried blacklisting the module zd1211rw and used the rmmod command to remove it but that isn't the problem - the interface simply doesn't seem to 'see' my network. Am going to try to re-compile the source drivers from the mini CD the stick came with as soon as I've made some really strong coffee - if it works I'll post it.

zd1211b on 3.01 0ace 1215 branded as 'pluscom'