2.14: zd1211 wifi driver pet install not working

[Hannge]

I am a linux newbee. I am using puppy 2.14, have USB wireless WLAN with a z1211 chip set, and I can't connect with an open access point. The zd1211xy driver doesn't work as good as the Windows driver, which produces/receives a better signal on the same USB wifi and gives me a good connection.

So, I downloaded the zd1211+b-r85-k2.6.18.1.pet driver, which is supposed to be an update over the puppy 2.14 zd1211xy driver. With no WIFI driver installed, I installed it with the getpet install program. The installation was successful and I could see it in the right column. However puppy didn't recognize the USB wifi when I plugged it in. So, I rebooted puppy hoping it would see it then, it still didn't recognize the usb wifi. I ran the other network wifi software and gave me an error indicating no wireless was recognized. What do I need to do? I must be missing something. I also tried the exact same thing with the zd1211 driver installed with no better luck. I also looked in "ethernetmodels" and it was blank.

I also tried "THe User Guide of ZD1211 USB Linux Driver" manual steps to load the driver that came with the device, and when it came time to build the driver with the "make" command in the instructions, puppy didn't recognize the "make" command. This manual also uses the private command 'iwpriv' which wasn't recognized by puppy.

I am guessing the zd1211xy driver sets the POWER SAVING mode to active by default. If I could turn this off I'm guessing this would help.

Any suggestions? The zd1211xy driver does make a connection sometimes, but is too poor to transfer data so the signal is on the hairy edge.

Thanks ahead of time.

[timhodson]

Once you have installed the zd1211b dotpup, in a terminal window, at the prompt type:

Code: Select all

prompt$ modprobe zd1211b
prompt$ depmod

That should load the driver. (the dotpup has a resource script but you have to run it manualy and it doesn't include the depmod command, which on my computer seems to make a difference.

You then need to set up all the wireless settings. note; I had a problem using an asci string for WEP passkey in the network wizard, but solved this by creating a little script (right click in rox - new>>script) that did the iwconfig setup for me. (the network wizard is a gui interface to iwconfig and ifconfig)

update: forgot to say, I created a symlink to the script from my desktop to make life easy.

I also embellished it with code to show a progress meter, had to add some pauses to the script so that all commands had time to complete.

The finisihed script - replace <thing> with your own router/access point settings.

Code: Select all

#!/bin/sh

TITLE="Configuring network connection"

( 
echo "..........";
  #bring the network card up
  ifconfig eth1 up
  sleep 10

echo "..........";
  # set some settings - if not sure of freq and channel, 
  # scan for a network in the network wizard and then make a note of the settings
  iwconfig eth1 essid <yournetworkname> freq 2.417G channel 2 
  sleep 10
  
echo "..........";
  # found it best to wait before setting the key
  # the s: tells iwconfig it is a string (asci)
  iwconfig eth1 key s:<yourKey>
  sleep 10

echo "..........";
  # remove any dhcp processes
  rm -f /etc/dhcpc/*.pid;
  # get an IP from the router with dhcp
  dhcpcd -t 5 -d eth1;

echo "..........";
  # the rest of this script does the progress bar.
  sleep 1) |
Xdialog --title "$TITLE" --progress "setting up the network" 10 50 100

Xdialog --title "$TITLE" --msgbox "done !" 0 0

# start any other programs you wish
# e.g
# exec gaim

And that works for me. The progress bar is not exactly accurate, but it reminds me that I won't be able to connect until the roughly thirty seconds of setup have passed, and the done ! box is shown.

Then I get Gaim started for me automatically.

Hope this makes some sense.

BTW, I am using a Belkin USB F5D7050 - obviously with the zydas chipset.

Tim

[Hannge]

Thanks for the input. However, after I followed your instructions
prompt$ modprobe zd1211b
prompt$ depmod
The USB wifi was still not recognized. I went into the network wizard and didn't see the new zb1211B driver either, even after rebooting. It seems like I'm still stuck with the zb1211xy.

Any other thoughts?

[timhodson]

The network wizard sometimes shows 'blank space' as being an already loaded driver...

Also, the driver will not appear in the list of drivers (when you click 'load driver'), but if you have a look at the output of these two commands, it should show up and thus is loaded.

Code: Select all

prompt$ modprobe -l -tnet
prompt$ dmesg

The mode probe output lists all modules to do with the network that are loaded in the kernel. the zf1211b driver should be listed.

The dmesg output should show that the Zydas driver has initiated. (big asci text ZYDAS! plus other info)

dmesg will also show up any errors that the driver encountered when trying to startup. - perhaps an idea to copy and paste the output into your next post so we can see?

the modprobe/depmod commands will have to be re-run after every reboot. I modified one of the bootup scripts rc.local0 (search the forums for more info) to do this part of the setup everytime the pc started.

After you have run the modprobe/depmod commands, did you go into the network wizard and find a new eth[n] entry? on my pc there is already a wired network card on eth0, so my usb device showed up as eth1.

If eth[n] shows up, click on it and then in the next window, click 'wireless' to scan/see/set settings for the wireless device. These are then the settings I used in my script.

were you able to check what chipset your usb device was?

[Hannge]

The mod probe command did show the zd1211B driver loaded. I didn't know about the "dmesg" command. After I ran the modprobe depmod command the ethX didn't show up. I expected a eth0, because this is what shows up with the old driver.

I also tried to install a "custom driver" (ZD1211B) in the network wizard. It recognized it after I did the PETGET and installed it. However the driver didn't recognize any hardware. I did save it and rebooted, but that didn't help either. If it did work it would seem that having saved the driver would taken care of the reboot issue and having to run modprobe and depmod at every boot.

I'll try your new suggestions and let you know how it turns out. My chipset is the Zydas chipset also. I won't have time till Tuesday to get to it.

Thanks.

[Hannge]

Here is the output from the DMESG command after I loaded the driver.
It looks like it couldn't talk to the device. I tried it with the device plugged in at power up and after power up. Same results. I tried the zd1211xy driver and it worked albeit very poorly. I wonder if the NDSIWRAPPER would work better?


sh-3.00# dmesg

PCI: Failed to allocate mem resource #6:10000@44000000 for 0000:01:00.0
PCI: Bridge: 0000:00:01.0
IO window: disabled.
MEM window: 40000000-40ffffff
PREFETCH window: 42000000-43ffffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 8192 bind 4096)
TCP reno registered
squashfs: version 3.1 (2006/08/19) Phillip Lougher
NTFS driver 2.1.27 [Flags: R/W].
Initializing Cryptographic API
io scheduler noop registered
io scheduler cfq registered (default)
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:02: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
PCI: setting IRQ 10 as level-triggered
PCI: Found IRQ 10 for device 0000:00:04.0
PCI: Sharing IRQ 10 with 0000:00:14.5
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 13824K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:14.1
VP_IDE: chipset revision 16
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci0000:00:14.1
ide0: BM-DMA at 0x1480-0x1487, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x1488-0x148f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: WDC WD300AA-60BAA0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: LTN403, ATAPI CD/DVD-ROM drive
hdd: Hewlett-Packard CD-Writer Plus 9100, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 58633344 sectors (30020 MB) w/2048KiB Cache, CHS=58168/16/63, UDMA(66)
hda: cache flushes not supported
hda: hda1 hda2 < hda5 >
libata version 2.00 loaded.
PNP: PS/2 Controller [PNP0303,PNP0f0e] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
Time: tsc clocksource has been installed.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 176k freed
usbcore: registered new driver usbfs
usbcore: registered new driver hub
input: ImPS/2 Logitech Wheel Mouse as /class/input/input0
USB Universal Host Controller Interface driver v3.0
PCI: setting IRQ 11 as level-triggered
PCI: Found IRQ 11 for device 0000:00:14.2
PCI: Sharing IRQ 11 with 0000:00:14.3
uhci_hcd 0000:00:14.2: UHCI Host Controller
uhci_hcd 0000:00:14.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:14.2: irq 11, io base 0x00001440
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
PCI: Found IRQ 11 for device 0000:00:14.3
PCI: Sharing IRQ 11 with 0000:00:14.2
uhci_hcd 0000:00:14.3: UHCI Host Controller
uhci_hcd 0000:00:14.3: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:14.3: irq 11, io base 0x00001460
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
hdc: ATAPI 40X CD-ROM drive, 120kB Cache, DMA
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 32X CD-ROM CD-R/RW drive, 4096kB Cache, UDMA(33)
Registering unionfs 20060916-2203
unionfs: debugging is not enabled
fuse init (API version 7.7)
ISO 9660 Extensions: RRIP_1991A
usb 1-2: new full speed USB device using uhci_hcd and address 2
ISO 9660 Extensions: RRIP_1991A
ISO 9660 Extensions: RRIP_1991A
uhci_hcd 0000:00:14.2: Unlink after no-IRQ? Controller is probably using the wr ong IRQ.
usb 1-2: device descriptor read/64, error -110
usb 1-2: device descriptor read/64, error -110
usb 1-2: new full speed USB device using uhci_hcd and address 3
usb 1-2: device descriptor read/64, error -110
usb 1-2: device descriptor read/64, error -110
usb 1-2: new full speed USB device using uhci_hcd and address 4
usb 1-2: device not accepting address 4, error -110
usb 1-2: new full speed USB device using uhci_hcd and address 5
usb 1-2: device not accepting address 5, error -110
usb 2-1: new low speed USB device using uhci_hcd and address 2
usb 2-1: configuration #1 chosen from 1 choice
usb 2-2: new full speed USB device using uhci_hcd and address 3
usb 2-2: configuration #1 chosen from 1 choice
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected VIA Apollo Pro 133 chipset
agpgart: AGP aperture is 64M @ 0x50000000
linmodem(1226): linmodem v0.1 loaded
pctel_hw: module license 'GPL linked with proprietary libraries' taints kernel.
pctel_hw(151): PCTel hardware driver version 0.9.7-9-rht-6 for PCT789

pctel(670): pctel v0.1 loaded
pctel_pci(726): device 134d:7897 is grabbed by driver serial: try to release

PCI: Enabling device 0000:00:04.0 (0000 -> 0001)
PCI: Found IRQ 10 for device 0000:00:04.0
PCI: Sharing IRQ 10 with 0000:00:14.5
pctel_pci(232): PCTel device[0000:00:04.0](0x20) found 134d:7897 (rev 02), iobas e=0x1400, irq=10.
pctel_pci(608): Setup PCI port: port 0x1400, irq 10, type 0, membase 00000000, o ps 00000000
ttyS_PCTEL0 at I/O 0x1400 (irq = 10) is a PCTel
parport_pc: VIA 686A/8231 detected
parport_pc: probing current configuration
parport_pc: Current parallel port base: 0x378
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
parport_pc: VIA parallel port: io=0x378, irq=7
vt596_smbus 0000:00:14.4: SMBUS: Error: Host SMBus controller not enabled! - upg rade BIOS or use force=1
PCI: Found IRQ 10 for device 0000:00:14.5
PCI: Sharing IRQ 10 with 0000:00:04.0
PCI: Setting latency timer of device 0000:00:14.5 to 64
apm: BIOS not found.
apm: BIOS not found.
Adding 102308k swap on /initrd/mnt/dev_save/pupswap.swp. Priority:-1 extents:22 across:402616k
usbcore: registered new driver hiddev
input: Chicony Compaq Internet Keyboard as /class/input/input1
input: USB HID v1.10 Keyboard [Chicony Compaq Internet Keyboard] on usb-0000:00: 14.3-1
input: Chicony Compaq Internet Keyboard as /class/input/input2
input,hiddev96: USB HID v1.10 Device [Chicony Compaq Internet Keyboard] on usb-0 000:00:14.3-1
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
lp0: using parport0 (interrupt-driven).
lp0: console ready
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usb 1-2: new full speed USB device using uhci_hcd and address 6
usb 1-2: configuration #1 chosen from 1 choice
zd1211b: no version for "struct_module" found: kernel tainted.
ZD1211B - http://zd1211.ath.cx/ - r85
Based on www.zydas.com.tw driver version 2.5.0.0
usb 1-2: reset full speed USB device using uhci_hcd and address 6
Release Ver = 4810
zd1211:bulk out: wMaxPacketSize = 40
zd1211:bulk in: wMaxPacketSize = 40
zd1211:interrupt in: wMaxPacketSize = 40
zd1211:interrupt in: int_interval = 1
zd1211:bulk out: wMaxPacketSize = 40
EEPORM Ver = 4810
zd1211:USB Download Boot code success
zd1211: failed intr_urb
zd1211:USB ST Code = -22
zd1211b: probe of 1-2:1.0 failed with error -5
usbcore: registered new driver zd1211b
sh-3.00#

[timhodson]

hmm. I was hoping there would be something obvious there.

It seems like the driver is sort of loading but then having trouble initialising the devise.

Have you tried all the other flavours of the zd1211 driver? i.e. zd1211rw?

Going back to your first post, I have a feeling that the make command is available if you have the Devtools for puppy - I think there is more on that in the forums/wiki.

The only other thing to try is:
With the module loaded, unplug the device and then plug it in again. In theory the led on the device should come on then go off again. Then have a look ini the network wizard to see if it shows up.

I am a newb to this too, and was able to get you as far as my knowledge would take me having wrestled with my own device, but I fear I have run out of ideas.

[Hannge]

Thanks. Perhaps I'll look into using the Ndsiwrapper scheme.

[ecomoney]

Im having the same problem, and with the same output with a Pluscom model number WU-ZD1211B ver 1.0 in 2.15ce. Has there been any movement on getting this driver incorporated into base puppy. It seems it is one of the cheapest chipsets out there so should be perfect for low budget computing, and Im planning to use this model in the forthcoming wireless network around the community centre.

[tempestuous]

Hannge,
It would be helpful if you could tell us the brand/model/revision of your USB wifi device.
There is a critical difference between the zd1211 and zd1211b modules, so it's important to know which one to use.

Under Puppy versions 2.12-2.16 the zd1211/zd1211b modules are reported as more reliable than the zd1211rw module.

Under Puppy 3.00, only the zd1211rw module is available, but apparently this later version is supposed to work well.

[ecomoney]

would there be a way of updating the driver zdrv package from the 3 series, or is it a different kernel version?

[tempestuous]

There's no easy way to get an improved zd1211rw driver for Puppy versions 2.12-2.16 (2.6.18.1 kernel).
The optimal solution is to use the zd1211/zd1211b modules instead, from here -
http://dotpups.de/dotpups/Wifi/drivers- ... 2-to-2.14/

Then the zd1211rw module will need to be blacklisted. This has been discussed on the forum before -
http://www.murga-linux.com/puppy/viewtopic.php?t=16038

[ecomoney]

Hi, thanks for the advice, still no joy. I would like to get this working as it was a donation. I wish to use it for the email system of the head of childrens services on the local council, who currently cant connect the her email and is missing meetings and not getting important reports through. Althoug I have a RT-71 based usb adaptor on its way (which should hopefully work straight away) there is a postal strike in the uk at the moment.

I edited etc/rc.d/rc.modules and edited the "SKIPLIST" variable (I assume its a variable, my bash scripting doesnt amount to much!).

it now reads

Code: Select all

SKIPLIST=" zd1211rw arcfb cirrusfb cyber2000fb ......... etc "

I rebooted with the usb key in and tried the network wizard. Only the wired ethernet showed up (eth0). I opened a terminal window and tried the commands listed above

Code: Select all

modprobe zd1211b
depmod

There was no output recieved from either of these commands

I went back into the network wizard and noted that the following drivers were now loaded - 3c59x zd1211b but still only the wired ethernet card showed up. I tried the following command suggested above.

Code: Select all

modprobe -l -tnet

towards the end of the output I saw

Code: Select all

/lob/modules/2.6.18.1/kernel/drivers/net/zd1211rw/zd1211rw.ko

Can I assume that the faulty zd1211rw is still loaded? I tried

Code: Select all

rmmod zd1211rw

to try and unload the faulty driver manually, but recieved the output

Code: Select all

ERROR: Module zd1211rw does not exist in /proc/modules

Im currently working on ecopup, which is puppy 2.15ce based. I would like to resolve this problem as it would give ecopup user in the planned community wireless network access to some very cheap adaptors. I am familiar with how to edit sfs files using the editor. Could I simple remove the directory in the zdrv_215.ce file containing the faulty driver so it does not cause problems in the future?

Many thanks for your time and expertise tempestuous.

[/code]

[ecomoney]

I rebooted and tried the

Code: Select all

modprobe zd1211b
depmod

commands again, I then tried

Code: Select all

dmesg

I am assuming dmesg is some sort of display of output that doesnt usually show up on the command line. I found some errors towards the end (which is to do with the most recent commands entered on the command line?)

Code: Select all

ZD1211B - http://zd1211.ath.cx/ - r85
Based on www.zydas.com.tw driver version 2.5.0.0
usb 1-1:reset full speed usb device using uhci_hcd and address 2
Release Ver = 4810
zd1211:bulk out: wMaxPacketSize = 40
zd1211:bulk in wMaxPacketSize = 40
zd1211 interrupt in: wMaxPacketSize=40
zd1211 interrupt in:int_interval =1
zd1211:bulk out: wMaxPacketSize = 40
EEPORM Ver = 4810
zd1211:USB Download Boot code success
zd1211: failed intr_urb
zd1211:USB ST Code = -22
zd1211b probe of 1-1:1.0 failed with error -5
usbcore: registered new driver zd1211b

I havnt a clue what this means but it sounds bad!!!! Does it help.

Many thanks again

[tempestuous]

Code: Select all

ERROR: Module zd1211rw does not exist in /proc/modules

Your blacklisting process is fine, the zd1211rw module has clearly not loaded.

After loading the zd1211b module with

Code: Select all

modprobe zd1211b

it's not necessary to run "depmod" because the zd1211+b dotpet already does that during installation.

Confirm that the zd1211b module has loaded successfully with "lsmod".
Now run these 2 commands -

Code: Select all

ifconfig -a

Code: Select all

iwconfig

to see if a wifi interface has been created.
If so, go ahead and use the Network Wizard.
If not, the driver does not recognise your device ... maybe -
i) the zd1211 module is the correct one
ii) your device ID is not properly defined in the zd1211/zd1211b driver code. This would require recompiling.

[ecomoney]

Hi I tried the commands you suggested straight after a reboot, Ive been trying puppy 3.00 to see if the card was supported there and it wasnt). i did

Code: Select all

 modprobe zd1211b

and then dmesg and got with the same eorror as before (-5) I tried

Code: Select all

ifconfig -a

just listed the eth0 (the wired adaptor built into the laptop I am testing with) and lo (loopback) nothing about wlan0 or eth1 showed up, which I believe is what happens when a device is correctly recognised. I tried iwconfig as well but I just got

Code: Select all

lo               no wireless extentions
eth0           no wireless extentions

I tried

Code: Select all

lsmod

and got a list of the loaded drivers( thanks for that tip!) with this at the bottom.

Code: Select all

usbcore                     126116     4  zd1211b, usb_storage, uhci_hcd

I dont know why its coming up with the device as usb storage? Its obviously loaded. I think your right that perhaps my adaptor isnt listed with the correct vendor/product id. This would mean that the driver doesnt recognise the usb device, even though it has the correct chipset? I cant remember where I read it, but I did hear that the device listing for the zydas 1211b in the driver was incomplete (though I didnt know what that meant at the time).

I tried the "USBView USB information" from the main puppy start menu (under system) and read the following information about the adaptor. It came back as

Code: Select all

Vendor ID: 0ace
product ID: 1215

Ive attached a screenshot of the usb information page if its of use.

would you happen to know if this product/vendor id is included with the zydas.pet driver. Will it need to be recompiled. I did have a go at recompiling the driver the other night (my first attempt at compiling, just to show how desperate I am!) and it made a new zd1211b.ko file, which I have seen listed as part of the driver. I wouldnt have a clue what to do with it though.

Many thanks for your patience getting this thorny issues sorted out. If it is the vendor id that is not compatable, I will contact the driver team and make sure it is included. This adaptor has shown up as the cheapest adaptor in the world for usb wireless (£6.49) according to google product search, so I believe its well worth including for a budget computing distribution like puppy!

[tempestuous]

Code: Select all

Vendor ID: 0ace
product ID: 1215

Well that device id is already valid in the zd1211b module.
You can see this by running

Code: Select all

modinfo zd1211b

and here is the relevant line

Code: Select all

usb:v0ACEp1215d*dc*dsc*dp*ic*isc*ip*

zd1211/zd1211b source code development has stalled, so it's not possible to download a more recent version of this driver.

The only thing I can think of is to try swapping the wifi device from USB1 to USB2 port, or vice-versa.
Maybe even try the device in a different computer altogether.

[tempestuous]

At http://zd1211.wiki.sourceforge.net/VendorDriver
I just learned that an updated "Vendor" (official) driver was just released a few days ago, even though the "Vendor-based" driver has stalled.
I now attach this package. As before, there are 2 modules; zd1211 and zd1211b.

[CHLee]

Dear tempestuous ,
zd1211+b-v2.21.0.0-k2.6.18.1.pet work OK for me . I can use it in "puppy-3.00retro-k2.6.18.1" . Thank you very much !
Puppy3.00 build in zd1211rw was not support the new RF chip (UW2453) . I try to compile the v2.21.0.0 driver in Puppy3.00 , but too many error when compiling .
Could you teach us how to compile the driver in Puppy3.00 (kernel: 2.6.21.7) ? Or could you make a zd1211+b-v2.21.0.0-k2.6.21.7.pet please .

Thanks !
C.H.Lee

The below was part of the dmesg :

ZD1211B - version 2.21.0.0
vendor_id = 0ace
product_id = 1215
USB 2.0 Host
Release Ver = 4810
EEPORM Ver = 4810
Finsih download Firmware. Ready to reboot
PA type: 0
UW2453 RF
OverWrite CR157 = 0xF0
zd1205_config: EEP(HWFeature)=0x2000
AllowedChannel = 000107ff
Region:48
usbcore: registered new driver zd1211b
RadioOn
Set to CCK
Set to OFDM

[tempestuous]

OK, zd1211+b-2.21.0.0-k2.6.21.7.pet for Puppy v3.00 available here
http://www.murga-linux.com/puppy/viewto ... 745#145745