These are dedicated drivers for specific wireless chipsets, as a (better) alternative to ndiswrapper.
They were compiled with the 2.4.29 kernel, so are good for Puppy 1.0.4 - 1.0.9.

UPDATE August 2006: These files are no longer at http://mymirrors.homelinux.org/puppy/wireless/
They're now here http://dotpups.de/dotpups/Wifi/drivers-for-Puppy-1/

See http://www.murga.org/~puppy/viewtopic.php?t=8488
for wifi drivers compatible with Puppy 2.0/2.01.

There are 12 different driver packages plus a separate application for those brave people who want to use WPA encryption.
"_Puppy_wireless_README" contains overall information, particularly help with identifying the chipset in your wireless device ... achieved mainly by going to the Wireless Adapter Chipset Directory at http://linux-wless.passys.nl/

I have packaged these drivers as gzipped tarballs, designed to be uncompressed from the uppermost directory.
Some of these drivers involve multiple modules, and the only easy way for one module to call other modules is if they are located in /lib/modules/2.4.29/ (and "depmod" run).
This directory is not retained in the persistent pupfile. Similarly, certain modules expect to find their support files in specific locations, and some of these locations are not persistent either. So the value of using the DotPup format was negated.

These drivers can be made "permanent" by following the instructions in the README file(s).
Here is what's available -

NOTE: There is no dedicated driver for Broadcom-based devices. ndiswrapper should be used.

At this stage, the linux-wlan-ng and ipw2200 drivers have been tested and are known-good.

All drivers except linux-wlan-ng support the wireless extensions interface, so I think (?) they will work with keenerd's Wireless Access Gadget http://www.murga.org/%7Epuppy/viewtopic.php?p=10027#10027

Craig SLast edited by tempestuous on Tue 15 Aug 2006, 20:51; edited 4 times in total

Happy to report that the Texas Instruments ACX100/ACX111 package works well with the D-Link DWL-650+ and Puppy 1.0.4.

Then I wandered over to my neighbour's place and tried out the Ralink rt2400/2500/2570 package with an MSI PC54G2 (rt2500 chipset) and Puppy 1.0.4. It worked well too. When depmod is run it complains about unresolved symbols in rt2570, but I have no way of knowing if this might be serious or not.

When you compiled the Realtek module you you even get it to load with out any complaints, if you used the one from Realtek, as this is tried in very closely with particular RedHat Kernels which are anything but a vanilla kernel.

Yes, as I mentioned in the relevant README's, there are "*** Unresolved symbols" errors with the Ralink rt2570, Realtek rtl8180_24x, and all 13 atmelwlan modules.
In the case of atmelwlandriver, these errors are well known, and should not affect the modules' success.
And I would be cautiously optimistic that the rt2570 (USB) should be OK.

Regarding the rtl8180, this is the original version from Realtek, and as bladehunter has indicated does not have a good reputation.
I have just discovered a more "developed" version from http://rtl8180-sa2400.sourceforge.net/
I will upload this version soon. I'm not sure whether to keep the old version there as well?

NOTE: There is no dedicated driver for Broadcom-based devices. ndiswrapper should be used.

We need a clear, illustrated, step-by-step howto for getting Puppy 1.0.5 wireless up and running on laptops similar to http://www.novell.com/coolsolutions/feature/15484.html . We discovered we did need to download the perl PupGet but upon entering "ndiswrapper -i bcmwl5.inf" in the /tmp directory on our HP ZE2113US laptop we got the following:

I got equally funky error messages the first time I tried to make an ndiswrapper driver. My mistake was attempting to use ndiswrapper with only the inf. Turns out you need all the files from the drivers.

Ndiswrapper can convert the drivers without the hardware installed. It should work regardless, as long as all the files are in place.

We copied the entire WLAN folder from the Windows XP disk into Puppy 1.0.5 and it appears to be up and running (although we still got the Forcing parameter messages). Apparently in Puppy you don't want to put the files in /tmp because they will disappear when you exit the program.

To summarize, we downloaded the Perl PupGet, copied the Windows WLAN folder from the Windows CD to root in Puppy. Then installed the wireless driver with "ndiswrapper -i /root/WLAN/bcmwl.inf". Then checked the install with "ndiswrapper -l". Then entered "modprobe ndiswrapper". Then entered "iwconfig". Then ran the Wireless Wizard in Puppy. We successfully connected to a wireless network to test the system so this problem is solved.

I had posted in another thread that I was able to set up a wireless connection with the intel pro 2200 drivers but unable to connect to the network. It was my WPA encryption that was causing the failure. When I turned off the encryption, I was able to connect.

I decided to try the WPA helper utility, wpa supplicant. I was uable to uncompress the files of wpa_supplicant-0.3.9.tar.gz in a terminal window in the "base" directory. I used cd / tar -zxvf wpa_supplicant-0.3.9.tar.gz. If I opened the file in a compression utility, I was able to uncompress. Therefore I was never able to successfully connect using these helper files.

I copied the wpa supplicant file to the uppermost directory from my mounted NTFS HDD. I opened an RXVT window there. ( I am very new to puppy linux and am not clear on the commands.) What is the path of the uppermost directory?

I use the term "uppermost directory" to describe the root directory of the running filesystem (/).
I think the correct term is "root directory" but I find this term confusing since I think of it as "/root" ... even though "/root" is probably accurately referred to as "root home directory".

If you have copied the wpa_supplicant-0.3.9.tar.gz file to / then all you need to do is change directory here "cd /" then run "tar -zxvf wpa_supplicant-0.3.9.tar.gz".
In this situation, there's no need to specify the path to the file, since you are running the command from the same location as the file itself.
No matter where you locate the tarball, the tar command MUST be run from / because the files will uncompress relative to this location.

Some commandline tips -
"pwd" will display your current location
"ls" will list files and directories in your current location

I had little trouble running Puppy 1.05 and using the Wifi-Beta2 and WAG to connect to my wireless network. I have a Toshiba laptop with an Atheros wifi card and a Linksys WRT54G Router. Excellent job guys...it was "fairly" simple and works perfectly. I still need to figure out how to get it to set itself up each time I boot up Puppy so I don't have to set it up each time though. Puppy is really starting to mature.

Ralink 2500 on a foxconn WLL-3350 works fine. Saved the tarball to /root, used guiTar to extract it it, checked that it was there in modules, opened a terminal, depmod, then modprobe rt2500 and I'm up. I have been using this card under ndiswrapper for the last 3 or 4 Pup versions but the native driver seems as stable, the setup is MUCH cleaner, and will stay in as I switch to 1.05/1.06.

Thanks tempestuous _________________Pups currently in kennel LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64, and LxPupBB for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS. Now tazpup for puzzles

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum