Yes, that's strange. The kernel configuration for 2.6.25.16 enables those modules, but it appears that Barry didn't include them in the zdrv driver collection.

Yes, in all puppies from 4.21 back, the Unleashed build script took out some "exotic" modules that I thought would not be needed, to save space.

However, in the new Woof 4-series builds, including the latest "415 alpha", there is virtually no pruning of modules, quite the contrary I have added lots from this thread. So, those nfs modules are retained: I am running 415+ right now, just checked they are there._________________http://bkhome.org/news/

However, in the new Woof 4-series builds, including the latest "415 alpha", there is virtually no pruning of modules, quite the contrary I have added lots from this thread. So, those nfs modules are retained: I am running 415+ right now, just checked they are there.

Well that's good to here. For linux to linux file sharing nfs provides a solid lightweight solution. It seems to me that catering for the variety of wireless adaptors out there is bulking up the kernel modules demand for space.

UPDATE May 26 2009:
The driver was originally located in the wrong directory. Now fixed and re-attached.

Hi;

On the strength of this post I picked up one of these TP-Link WN322G USB modems (incredibly cheap!) and installed the pet, rebooted and ran the Connect program. It recognized the WLAN and went through the whole process fine and what's more, it showed a signal strength of 100%, which had me jumping for joy as the old USB modem I've been using has poor performance, to say the least. Everything goes well...until I open a browser and try to connect, when I get file not found errors from Seamonkey and Opera 9.64 and 10 beta. Although the system says I have a connection (and the little blinky monitors in the bottom right panel are blinking), plainly I don't.

I'm new to Puppy and almost as new to linux itself. I would be happy to run any shell commands and post their output if it would help debug this; I'd love to be able to use this old laptop more than a few feet away from the router.

Here are the Linux drivers for VIA wifi devices:
VIA VT6655 PCI device, the driver is called viawget
VIA VT6656 USB device, the driver is called vntwusb

The source code is from
http://www.viaarena.com/Drivers.aspx
After installing either of these dotpets, reboot.
Both drivers create an interface called eth#. Usually your LAN device takes eth0, so the wifi interface will probably become eth1.

For WPA-encrypted connections, both package include a modified version of wpa_supplicant compatible with the new driver.
I have included the necessary configuration file (/usr/sbin/wag-profiles.sh) so that Puppy's Network Wizard should be able to configure the connection.
But if you want to configure a WPA connection via the commandline, be aware that the wpa_supplicant "-D" parameter for the new drivers are the same name as the driver itself (which is quite unconventional).

As an example, with the viawget driver and a WPA2 connection, your command would be -

I picked up an older 2WIRE and Qwest branded USB wireless adapter. Through research and the use of a screwdriver I have this information.
FCC ID: M4Y-XG702B
Manufacturer: ZCOM (ZCOMAX)
Chipset: Intersil, Controller NET2280, Wireless ISL3886 (PRISM Duette)
Vendor ID: 1630
Device ID: 0005
(1630:0005)
I think it's part of the existing p54 driver (p54usb, p54pci p54common) http://lekernel.net/prism54/snapshots/ . The chipset would make it a direct match to Linksys WUSB54G 5041:2234, and a host of others http://lekernel.net/prism54/newdrivers.html . It appears that driver development is dead so even though support might be as simple as adding the vendor and device id's to the source I don't know who to forward the information to.

I don't expect anyone on the forum to edit the source and recompile the driver since ndiswrapper works. I did think it would be useful to post this information somewhere although this isn't the best place. I would guess the amount of these USB adapters still in use is trivial.Edited_time_total

If, indeed, your device has a Prism54-softmac chipset then it should be supported by the p54usb driver ...
but the p54usb driver in Puppy 4.1/4.2 does not recognise your USB device number.
It's quite easy to hack the kernel source file (p54usb.c) to add your device number, but the driver is supposed to probe the device to determine the exact firmware file necessary to load (which for your ISL3886 + net2280 chipset will be isl3890usb) and I can't guarantee that this process will be successful for you.
Give it a try.
After installing this dotpet, reboot.
When you plug in your USB device, Puppy should automatically load the p54usb driver, but if not you can load it manually from the Network Wizard.

Thank you so much Tempestuous for building p54usb-ZCOM-k2.6.25.16.pet . It definitely initialized the usb adapter and gave me a wlan0 interface. Unfortunately it had problems with the host usb controller on my test machines whenever I tried to scan for wireless networks. I will derive lsusb -vvv and post that along with the other information to linuxwireless.org in the hopes that native support may be available in the future based on that information.

Unfortunately it had problems with the host usb controller on my test machines whenever I tried to scan for wireless networks.

I vaguely remember reading a similar problem such as this, where a workaround was to force the USB interface to USB1.1 instead of USB2.0.
I think (??) this was simply a matter of unloading the USB2 kernel module (ehci-hcd), at which point the underlying USB1.1 module (ohci-hcd) should become active.
Worth a try?

July 18 2009
The acpid dotpets for hotkey wifi on/off for ASUS Eee have just been fixed in the earlier post.
http://www.murga-linux.com/puppy/viewtopic.php?p=237744#237744
It's sad that after almost 2000 downloads of these packages since October 2008, only one forum member (jakfish) was sensible enough to identify and report this problem.

Hey tempestuous, I got my ZCOM 1630:0005 wireless adapter working in Ubuntu Jaunty with your help (see http://ubuntuforums.org/showthread.php?t=707972 ).
Eventually I setup Puppy 4.2.1 with the development environment on a bootable USB stick. This way I could compile the kernel drivers using a faster computer and test it on a slower computer. To date I have tested this NET2280+ISL3886 adapter on Intel 440BX chipset, Nvidia Nforce2 chipset, and ATI 780G chipset on PII-300, Athlon XP 2800+ and Athlon X2 3000+. The 440BX is USB1.1 where the others are 2.0.

I found that the USB bus seems to hang on the 440BX when using the network wizard to "scan" for networks. The driver seems to force USB 1.1 on the Nforce2 which stops my Puppy USB stick from being able to write changes (must have had both devices on the same host controller). There were no ill effects on the 780G but the USB stick and wireless device were probably on different host controllers.

After messing with this more dmesg provided the following information:

Oddly if I run "ifconfig wlan1 up" then "iwlist wlan1 scan" I see networks but if I scan using the network manager dmesg shows pages of unknown frames:

phy1: unknown frame RXed (0x20) (also 30 31 37 54 6d 6f 72 73 77 78 )

The unknown frames are consistent regardless of computer.

I edited this post to let tempestuous know that I did try quite a few things (compiled from source, tried multiple firmwares, tested on multiple machines) and did not rely entirely on his efforts but had no better luck myself. I'm not sure if this will affect other NET2280+ISL3886 adapters in Puppy or if it's just this one. It may be somewhat chipset specific as far as the USB bus problems. I use wpa_supplicant but don't think it's affecting the connection, it seems to be a driver issue.