wireless / wifi cards confirmed to work in puppy - OLD LIST

Message

tempestuous · #101 Post by **tempestuous** » Sun 22 Jun 2008, 15:50

Well I can provide you with a modification which will display the new driver (zd1211b) in the Network Wizard, but it's really not necessary. Instead of following that convoluted rumination process you just described, just run the two simple commands I listed and the new driver will be loaded, ready to configure with the Wizard. Assuming the new driver works, save the configuration and you're done.
Linux sometimes requires some commandline input to troubleshoot problems or, as in this case, achieve non-standard procedures. Linux is not Windows, and it owes no apology for not having a gui for every process.
One big advantage of the commandline is that if there are any errors, you will see them. This is particularly relevant in your case since you are trying a driver which may, or may not, be compatible. If "modprobe zd1211b" reports no errors, you're in good shape. If it does report errors, at least you know that the driver is at fault, and not encryption or DHCP, for example.

Jeffreytooker wrote:When I click the driver in the subfile it just blinks twice. I take it this means that it is installed in the subfile? If this is true then I do not know how to install the driver where it is supposed to go.

Any responsible developer creates dotpets which install to the correct locations. The notion that you would need to shift anything is silly, but if you want to know where the new driver is, it's at /lib/modules/2.6.21.7/net/zd1211b.ko

Jeffreytooker · #102 Post by **Jeffreytooker** » Sun 22 Jun 2008, 18:59

"tempestuous":

I will address the issues in the order you have them listed here.

<<<

tempestuous wrote:Well I can provide you with a modification which will display the new driver (zd1211b) in the Network Wizard, but it's really not necessary. >>>

Agreed

<<<Instead of following that convoluted rumination process you just described, just run the two simple commands I listed and the new driver will be loaded, ready to configure with the Wizard.>>>

The link you gave me yields zd1121%2Bb-2-2.21.0.0-k2.6.21.7pet not zd1211+b-2.21.0.0-k2.6.21.7.pet

<<< Assuming the new driver works, save the configuration and you're done.
Linux sometimes requires some commandline input to troubleshoot problems or, as in this case, achieve non-standard procedures.>>>

More about this later

<<< Linux is not Windows, and it owes no apology for not having a gui for every process.>>>

I agree with the above. I only made the comment about the GUI as an aside. Please notice smiley face. I was only refered to the advanced section of this list by a moderator. This question started out in Beginner list. I am very much a beginner.

<<<One big advantage of the commandline is that if there are any errors, you will see them. This is particularly relevant in your case since you are trying a driver which may, or may not, be compatible. If "modprobe zd1211b" reports no errors, you're in good shape. If it does report errors, at least you know that the driver is at fault, and not encryption or DHCP, for example.>>>

Agreed

Jeffreytooker wrote:When I click the driver in the subfile it just blinks twice. I take it this means that it is installed in the subfile? If this is true then I do not know how to install the driver where it is supposed to go.

Any responsible developer creates dotpets which install to the correct locations. The notion that you would need to shift anything is silly, >>>

I have learned something.

but if want to know where the new driver is it is at: /lib/modules/2.6.21.7/net/zd1211b.ko >>>

I executed your commands. Code: rmmod zd1211rw enter returns to command prompt no errors. Code: modprobe zd1211b enter yields: FATAL module zd1211b not found

Went to /lib/modules/2.6.21.7/net/zd1211b.ko I found no zd modules

Jeffrey

tempestuous · #103 Post by **tempestuous** » Mon 23 Jun 2008, 01:25

Thanks to your accurate reporting I was prompted to investigate further and discover that the forum's server has corrupted the filename of the zd1211b dotpet attachment, and thus the dotpet fails to install, with an error message as the attached image shows.
Problem now fixed -
http://www.murga-linux.com/puppy/viewto ... 745#145745

Jeffreytooker · #104 Post by **Jeffreytooker** » Mon 23 Jun 2008, 03:31

tempestuous wrote:Thanks to your accurate reporting I was prompted to investigate further and discover that the forum's server has corrupted the filename of the zd1211b dotpet attachment, and thus the dotpet fails to install, with an error message as the attached image shows.
Problem now fixed -
http://www.murga-linux.com/puppy/viewto ... 745#145745

"tempestuous":

I have downloaded the new module (thank you) to my desktop and copied it to my USB stick. I have installed in my Puppy computer IAW this procedure: http://tillamookrage.blogspot.com/2008/ ... puppy.html I ended with the paragraph under figure 6. I made a subfolder of My Documents called Belkin 5070 4X Drivers. The new module is in that file now. When I left clicked once on the module it blinked twice and did no more. I executed both commands. code rmmod zd1211rw yielded command prompt. Code modprobe yielded FATAL: module zd1211b not found. Went to /lib/modules/2.6.21.7/net/zd1211b.ko. It is not there. It seems to not be installing. Is my procedure wrong?

Jeffrey

tempestuous · #105 Post by **tempestuous** » Mon 23 Jun 2008, 04:18

I just did a fresh boot to a liveCD and the zd1211b dotpet installs fine.

Jeffreytooker wrote:I made a subfolder of My Documents called Belkin 5070 4X Drivers

There's your problem! Don't use blank spaces in Linux filesystems.
Easier still, you can install the dotpet directly from the USB drive, it's not necessary to copy the dotpet anywhere else ... but of course, the dotpet must not be in a sub-folder on the USB drive with spaces.

ken_cat · #106 Post by **ken_cat** » Tue 24 Jun 2008, 15:53

Works.

D-Link WNA-1330 Wireless G Notebook Adapter, H/W Ver. : A1, F/W Ver. : 1.10.

Tested in a Toshiba Tecra750DVD. Bios setup important.

Puppy version 4.00 on LiveCD.

For trials and tribulations encountered see http://www.murga-linux.com/puppy/viewtopic.php?t=30559

Will automatically load ath_pci on boot.

Network Wizard only seems to work after performing wpa_supplicant.conf modification and commandline setup for WPA/PSK.

Using Motorola WR850G router.

Jeffreytooker · #107 Post by **Jeffreytooker** » Tue 24 Jun 2008, 16:34

tempestuous wrote:I just did a fresh boot to a liveCD and the zd1211b dotpet installs fine.

Jeffreytooker wrote:I made a subfolder of My Documents called Belkin 5070 4X Drivers
There's your problem! Don't use blank spaces in Linux filesystems.
Easier still, you can install the dotpet directly from the USB drive, it's not necessary to copy the dotpet anywhere else ... but of course, the dotpet must not be in a sub-folder on the USB drive with spaces.

tempestuous:

Tested as directed above. Still no joy. I took Puppy 4.0 disk to main computer and ran same stuff, also no joy. The problem is not pressing. The only common item is the live disk. I will send for one by mail that I know is good. Then I will go back to testing. Will research commands and loading of programs. May take a couple of weeks but I will keep you informed. With the fires power and DSL were out for about 24 hrs.

Thank you.

Jeffrey

can8v · #108 Post by **can8v** » Tue 24 Jun 2008, 18:21

tempestuous wrote:The recent official Zydas "vendor" wifi driver from http://zd1211.wiki.sourceforge.net/VendorDriver
apparently supports some newer Zydas-based wifi devices not supported by Puppy 3.00's zd1211rw driver.
I now attach this package. It contains two different modules; zd1211 and zd1211b. If you have a recent Zydas chipset it's more likely to be supported by the zd1211b module.
After installing the dotpet, you will need to unload the standard module, and load the new one, like this -
Code: Select all
rmmod zd1211rw
modprobe zd1211b
Now you can use the Network Wizard to configure your wifi connection.

UPDATE June 23 2008:
Apparently this forum doesn't like attachments with "+" in the filename, and this attachment became renamed to "zd1211%2Bb-2.21.0.0-k2.6.21.7.pet" - which corrupts the installation of the dotpet!
After 350 downloads, why did no one report this problem?
Dotpet has now been repackaged with different filename.

tempestuous,
I have installed this "new" version of the dot pet, but the end result is not a zd1211.k0 and zd1211b.ko, instead I get only a zd1201.ko see the screen shot.

Kind regards,
can8v

Jeffreytooker,
If the dot pet installed you should also have the same file shown in the screen shot and it should appear in the network wizard if you click on load module. You might try loading it just for grins.

Jeffreytooker · #109 Post by **Jeffreytooker** » Tue 24 Jun 2008, 20:16

UPDATE June 23 2008:
Apparently this forum doesn't like attachments with "+" in the filename, and this attachment became renamed to "zd1211%2Bb-2.21.0.0-k2.6.21.7.pet" - which corrupts the installation of the dotpet!
After 350 downloads, why did no one report this problem?
Dotpet has now been repackaged with different filename.[/quote]
tempestuous,
I have installed this "new" version of the dot pet, but the end result is not a zd1211.k0 and zd1211b.ko, instead I get only a zd1201.ko see the screen shot.

Kind regards,
can8v

can8v:

In a previous post "tempestuous" stated path to file as: /lib/modules/2.6.21.7/net/zd1211b.ko. You screenshot states: /lib/modules/2.6.21.7/kernel/drivers/net/wireless(allthumbs) Why the different paths to the module? I will try loading this evening, but I am not hopeful. Will keep all informed.

Jeffrey

Jeffreytooker,
If the dot pet installed you should also have the same file shown in the screen shot and it should appear in the network wizard if you click on load module. You might try loading it just for grins.[/quote]

can8v · #110 Post by **can8v** » Tue 24 Jun 2008, 21:43

@Jeffreytooker
I cannot say with absolute certainty why tempestuous gave you a different path than I did for the location of the driver; my best guess is that he was typing the path from memory and forgot to include part of the directory tree in the path. While tempestuous is the foremost Puppy WiFi expert, he is human. I have never to my knowlege had my WiFi drivers in the directory that he mentions, in fact I don't even recall seeing that directory before, though the path is very similar to the path for the directory that stores my WiFi drivers.
In my mind the bigger concern is that I ended up with a zd2101.ko driver rather than a zd1211b.ko driver. At any rate it is possible that this could work for you. When I installed the pet package it installed the zd1201.ko just as I described and from then on I could see it in the load module section of the network wizard.

Jeffreytooker · #111 Post by **Jeffreytooker** » Tue 24 Jun 2008, 22:10

Jeffreytooker,
If the dot pet installed you should also have the same file shown in the screen shot and it should appear in the network wizard if you click on load module. You might try loading it just for grins.[/quote][/quote]

can8v & tempestuous:

The files in the same location as can8s's screenshot are: airo.ko, at76_usb.ko, atmel.ko, atmel_pci.ko, zd1201.ko and a folder named zd1211rw. In that folder exists a file named zd1211rw.ko

I believe (and I do not know how to prove) that "zd1201.ko" came original with the Puppy 4.0 disk. Code "rmmod zd1211rw" returns command prompt. Code "modprobe zd1211b" returns "Fatal: module zd1211b not found". Module exists in "mydocuments" by name as a .pet file (module) and is a 198K zipped file. The problem seems to be that "modprobe" can not find the zd1211b module in folder "mydocuments". Is "mydocuments" not a searchable folder for "modprobe'?

Jeffrey

tempestuous · #112 Post by **tempestuous** » Wed 25 Jun 2008, 01:13

The location of the module in /lib/modules/2.6.21.7/net is where the compiler script (from Zydas) installs the module. Third party modules often install to unconventional locations. Modules can go anywhere in /lib/modules/<kernelversion> ... provided the "depmod" command is run after installation to "register" the location of the new module(s). My dotpet package has a post-installation script to run "depmod".

I just booted to the Puppy3.02alpha CD, which has the same kernel as Puppy4.0.
I downloaded zd1211b-2.21.0.0-k2.6.21.7.pet from the forum into /root/my-documents
I clicked on the file, and got the install prompt, refer image1.
After the installation I am greeted with the "SUCCESS" prompt, refer image2.
If I use ROX to browse to /lib/modules/2.6.21.7/net I can see the two new modules - refer image3. But more importantly, if I run "modinfo zd1211b" in a console I see this -

Code: Select all

# modinfo zd1211b
filename:       /lib/modules/2.6.21.7/net/zd1211b.ko
license:        GPL
description:    ZyDAS 802.11b/g USB Wireless LAN adapter
author:         Yarco Yang
alias:          usb:v1582p6003d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1233p0471d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0F88p3014d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DF6p9075d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0CDEp001Ad*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0BAFp0121d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v083ApE501d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v083Ap4505d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v079Bp0062d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0586p340Fd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v050Dp705Cd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v050Dp4050d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v2019p5303d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0053p5302d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0053p5301d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0ACEpA215d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0ACEp1215d*dc*dsc*dp*ic*isc*ip*
depends:        usbcore

If the dotpet is failing to install by clicking on it in ROX, try the commandline equivalent -

Code: Select all

petget /root/my-documents/zd1211b-2.21.0.0-k2.6.21.7.pet

If it fails, at least you should get some clue why.

Jeffreytooker · #113 Post by **Jeffreytooker** » Wed 25 Jun 2008, 03:06

I just booted to the Puppy3.02alpha CD, which has the same kernel as Puppy4.0.
I downloaded zd1211b-2.21.0.0-k2.6.21.7.pet from the forum into /root/my-documents
I clicked on the file, and got the install prompt, refer image1.
After the installation I am greeted with the "SUCCESS" prompt, refer image2.
If I use ROX to browse to /lib/modules/2.6.21.7/net I can see the two new modules - refer image3. But more importantly, if I run "modinfo zd1211b" in a console I see this -

Code: Select all

# modinfo zd1211b
filename:       /lib/modules/2.6.21.7/net/zd1211b.ko
license:        GPL
description:    ZyDAS 802.11b/g USB Wireless LAN adapter
author:         Yarco Yang
alias:          usb:v1582p6003d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1233p0471d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0F88p3014d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DF6p9075d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0CDEp001Ad*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0BAFp0121d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v083ApE501d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v083Ap4505d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v079Bp0062d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0586p340Fd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v050Dp705Cd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v050Dp4050d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v2019p5303d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0053p5302d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0053p5301d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0ACEpA215d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0ACEp1215d*dc*dsc*dp*ic*isc*ip*
depends:        usbcore

If the dotpet is failing to install by clicking on it in ROX, try the commandline equivalent -

Code: Select all

petget /root/my-documents/zd1211b-2.21.0.0-k2.6.21.7.pet

If it fails, at least you should get some clue why.[/quote]

Tempesteous:

When I click on the .pet file icon I get two blinks and no install prompt. In console I entered required code. Yields: bash: petget /root/my-documents/zd1211b-2.21.0.0-k2.6.21.7.pet: No such file or directory. I placed the .pet file in /. I entered: petget /zd1211b-2.21.0.0-k2.6.21.7.pet. Yielded petget /zd1211b-2.21.0.0-k2.6.21.7.pet: No such file or directory.

I may be mistaken but it appears that can8v in his post of 2:21 today says he installs and gets zd1201. I believe he was not successful in his install and believes zd1201 to be the result of his install. I believe zd1201 was original with the Puppy 4.0 disk. My reason for this is that zd1201 is with zd1211rw in a different path and file from the one where you told me the zd1211b file will go. If can8v and I both have the same problem, then there may be a problem somewhere else.

can8v:

look in this location and see what you have. /lib/modules/2.6.21.7/net/zd1211b.ko.

Jeffrey

tempestuous · #114 Post by **tempestuous** » Wed 25 Jun 2008, 08:48

Jeffreytooker wrote:In console I entered required code. Yields: bash: petget /root/my-documents/zd1211b-2.21.0.0-k2.6.21.7.pet: No such file or directory

Well the error seems quite clear, you should be able to diagnose it yourself; zd1211b-2.21.0.0-k2.6.21.7.pet does not exist in /root/my-documents
Maybe you have inadvertently copied over the old corrupt version of the dotpet?

"zd1211%2Bb-2.21.0.0-k2.6.21.7.pet" = corrupt version

"zd1211b-2.21.0.0-k2.6.21.7.pet" = fixed version

Jeffreytooker · #115 Post by **Jeffreytooker** » Wed 25 Jun 2008, 15:07

tempestuous wrote:
Jeffreytooker wrote:In console I entered required code. Yields: bash: petget /root/my-documents/zd1211b-2.21.0.0-k2.6.21.7.pet: No such file or directory
Well the error seems quite clear, you should be able to diagnose it yourself; zd1211b-2.21.0.0-k2.6.21.7.pet does not exist in /root/my-documents
Maybe you have inadvertently copied over the old corrupt version of the dotpet?

"zd1211%2Bb-2.21.0.0-k2.6.21.7.pet" = corrupt version

"zd1211b-2.21.0.0-k2.6.21.7.pet" = fixed version

"tempestuous":

I agree. I believe the problem is the loading, not the module. Working with Muggins. Thread: http://www.murga-linux.com/puppy/viewto ... 683#209683

Thank you for all of your help. I will keep you informed.

Jeffrey

can8v · #116 Post by **can8v** » Wed 25 Jun 2008, 19:30

tempestuous,
I am quite certain I have the most recent pet package and I have no directory despite having installed the pet package and getting the same success message you did. The screen shot is below.
can8v
*edit*
I tried to uninstall the package and it does not show up in the package manager. I deleted the zd1201.ko driver from the system then redownloaded the pet package and tried to run it again. When I clicked on it I got a warning that the package had already been installed. I then clicked install anyway and the installation completed successfully per the success message at the end. I however, still do not have the two driver files or the /lib/modules/2.6.21.7/net/ directory.

can8v · #117 Post by **can8v** » Wed 25 Jun 2008, 20:15

Partial success!
I decided to change the file extention of the pet package to .tar.gz instead of .pet. I then opened the archive using pupzip and extracted the two driver files to the /lib/modules/2.6.21.7/net directory, which I had to create of course.
I did this using a 400 live cd with puppy pfix=ram boot parameter. Now I merely need to get back to my house, so I can test the drivers with the WiFi adapter. I still cannot figure out why the pet package will not install by clicking on it. The package looks to be in order other than the fact that I can't install it by clicking on it.
can8v

tempestuous · #118 Post by **tempestuous** » Thu 26 Jun 2008, 02:00

can8v, if you manually copy the modules into place, don't forget to run "depmod" afterwards. Otherwise your system will not recognise the new modules.

I'm now wondering if the dotpet installer is failing to create a new directory? It would be worth manually creating the necessary directory, then see if the dotpet will successfully install. So try this -

Code: Select all

mkdir /lib/modules/2.6.21.7/net

then run the dotpet and see if it installs now.

Jeffreytooker · #119 Post by **Jeffreytooker** » Thu 26 Jun 2008, 16:55

tempestuous wrote:
Jeffreytooker wrote:In console I entered required code. Yields: bash: petget /root/my-documents/zd1211b-2.21.0.0-k2.6.21.7.pet: No such file or directory
Well the error seems quite clear, you should be able to diagnose it yourself; zd1211b-2.21.0.0-k2.6.21.7.pet does not exist in /root/my-documents
Maybe you have inadvertently copied over the old corrupt version of the dotpet?

"zd1211%2Bb-2.21.0.0-k2.6.21.7.pet" = corrupt version

"zd1211b-2.21.0.0-k2.6.21.7.pet" = fixed version

tempestuous:

Sorry to intrude. I am sending this post FYI. In my researching my problem I find that there are several people with the same problem. The modprobe can not find the module. I started a thread: ROX Not Installing Modules. Link: http://www.murga-linux.com/puppy/viewto ... 611#209611

This should get you up to speed on where I am. I have found further information which I have not put on the above link. I do not wish to question your expertise but all that I have found leads me to believe there is a difference between the Puppy kernel that you are using and the 4.0 kernel that others of us are using. I would like to try the Puppy 3.01 CD in my system to see if I can get the zd1211b module to install. My Puppy 4.0 has installed files to my HDD. Can I just load a 3.01 disk in and have the system come up OK?

Jeffrey

ken_cat · #120 Post by **ken_cat** » Thu 26 Jun 2008, 20:22

Hello folks,

I've been finding the last topic interesting and thought I could maybe help by trying out the zd1211b-2.21.0.0-k2.6.21.7.pet in question for another look at it's behavior.

I have Puppy 4.00 loaded on my desktop in 256 MB of ram. I don't have the USB wireless card being considered here, so can't follow through with seeing if it will work as a connection.

I downloaded the .pet into the my-documents folder and opened Rox. Clicked on the .pet file and the Pet Manager opened and the installation went perfect.

I then did "modprobe zd1211b and that went ok, no error messages and # sign came up. I then did a search for zd1211b and you can see the results below.

I then looked into the Puppy Package Manager and the .pet file shows up in the bottom pane.

From PPG, I uninstalled the .pet with no issues.

I then did "rmmod zd1211b" in console. No problems. Then redid the search in pfind and there were enties gone with some left behind.
See image

On my system, the zd1211b-2.21.0.0-k2.6.21.7.pet file installs from Rox ok, and modprobe works ok on zd1211b, but the file locations are different from what has been discussed. The PPG manager functions as it should for uninstall of the .pet , as does rmmod.

Sorry for the images, I couldn't get them to go in the right locations

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

wireless / wifi cards confirmed to work in puppy - OLD LIST