Wireless driver packages for Puppy2
Need wireless driver
Running 2.02. I need a wireless driver for ZD1211, which is shown at bottom of list of drivers for 2.01.
I found linux driver tar file on Zydas site, but not sure what to do next.
http://www.zydas.com.tw/downloads/download-1211.asp
Can someone help?
Don
I found linux driver tar file on Zydas site, but not sure what to do next.
http://www.zydas.com.tw/downloads/download-1211.asp
Can someone help?
Don
I compiled the zd1211 in 202. A script to load and unload the module is included, but I'm not sure about the interface name, so these scripts might not work. Anyway the module is there along with the user guide.
- Attachments
-
- zd1211.tar.gz
- (157.31 KiB) Downloaded 401 times
- Waikiki Websurfer
- Posts: 36
- Joined: Sat 19 Nov 2005, 22:39
- Location: Waikiki Beach
2.02 compiling
tempestuous,
Thanks for the great job with the drivers. It is unfortunate that they won't work with 2.02. In anticipation of future Kernel, module, etc. upgrades which will make recompiling drivers necessary, it might be best if everyone simply compiled whatever driver they need. However, since I don't have any experience in compiling drivers, could you point out the basic requirements to do the job? Basically, a quick pointer about how you did it with the linux-wlan-ng for example to make it work with the updated Puppy versions... this of course assuming that the whole process is relatively straightforward and quick.
Aloha,
W.W.
Thanks for the great job with the drivers. It is unfortunate that they won't work with 2.02. In anticipation of future Kernel, module, etc. upgrades which will make recompiling drivers necessary, it might be best if everyone simply compiled whatever driver they need. However, since I don't have any experience in compiling drivers, could you point out the basic requirements to do the job? Basically, a quick pointer about how you did it with the linux-wlan-ng for example to make it work with the updated Puppy versions... this of course assuming that the whole process is relatively straightforward and quick.
Aloha,
W.W.
__O__ \/\/ \/\/
__/\___
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
__/\___
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
From http://www.puppyos.com/test/ you need:
- development/compiler environment squashfs file, devx_202.sfs
- patched kernel source, linux-2.6.16.7-squashfs3.0patch.tar.gz
plus the kernel config file for 2.02. I think this will be found in Puppy 2.02 itself, in /lib/modules/2.6.16.7/
To compile the kernel source, see http://www.puppylinux.com/development/compilekernel.htm
Superquick howto:
Uncompress the kernel source into /usr/src/
Now put the 2.02 config file into /usr/src/linux-2.6.16.7/ and rename it to ".config"
Make sure that /usr/src/linux is a symbolic link to /usr/src/linux-2.6.16.7
Make sure that /lib/modules/2.6.16.7/build is a symbolic link to /usr/src/linux-2.6.16.7
cd /usr/src/linux-2.6.16.7
make menuconfig (Save changes > YES)
make modules
The other steps should not be necessary since the kernel is unchanged, you're just setting up the kernel source tree.
Regarding linux-wlan-ng-0.2.3, this won't compile under the 2.6.16 kernel until you apply this patch (I think I got it from the Gentoo forum) and even then, enable only the USB driver (and maybe PLX) driver because the PCMCIA driver will still fail.
- development/compiler environment squashfs file, devx_202.sfs
- patched kernel source, linux-2.6.16.7-squashfs3.0patch.tar.gz
plus the kernel config file for 2.02. I think this will be found in Puppy 2.02 itself, in /lib/modules/2.6.16.7/
To compile the kernel source, see http://www.puppylinux.com/development/compilekernel.htm
Superquick howto:
Uncompress the kernel source into /usr/src/
Now put the 2.02 config file into /usr/src/linux-2.6.16.7/ and rename it to ".config"
Make sure that /usr/src/linux is a symbolic link to /usr/src/linux-2.6.16.7
Make sure that /lib/modules/2.6.16.7/build is a symbolic link to /usr/src/linux-2.6.16.7
cd /usr/src/linux-2.6.16.7
make menuconfig (Save changes > YES)
make modules
The other steps should not be necessary since the kernel is unchanged, you're just setting up the kernel source tree.
Regarding linux-wlan-ng-0.2.3, this won't compile under the 2.6.16 kernel until you apply this patch (I think I got it from the Gentoo forum) and even then, enable only the USB driver (and maybe PLX) driver because the PCMCIA driver will still fail.
- Attachments
-
- linux-wlan-ng-0.2.3-kernel-2.6.16.patch.gz
- (295 Bytes) Downloaded 392 times
ZD1211 (no B) 2.02 driver?
Does anyone have a ZD1211 driver that will work with 2.02? The only one I have been able to find appears to support only ZD1211b, but not ZD1211?
Something like the excellent drivers by tempestuous mentioned at the start of this topic, i.e. -
http://www.dotpups.de/dotpups/Wifi/wire ... 11-r76.pup
perhaps based on the latest ZD1211 driver (r83?) Thanks!
Something like the excellent drivers by tempestuous mentioned at the start of this topic, i.e. -
http://www.dotpups.de/dotpups/Wifi/wire ... 11-r76.pup
perhaps based on the latest ZD1211 driver (r83?) Thanks!
Looking at the ZyDAS site, it appears that the driver file name is the same for either zd1211 or zd1211b. And the file size looks the same. I think the modprobe chooses the correct branch, that is, modprobe zd1211 or modprobe zd1211b.Does anyone have a ZD1211 driver that will work with 2.02? The only one I have been able to find appears to support only ZD1211b, but not ZD1211?
I'm using the AirLink AWLL3026 wireless adapter, but done so in 2.01r2. Went back from 2.02 because other issues. Wireless works good.
Don
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
tempestuous
When you compile wireless drivers for Puppy 2.0/2.01, how is it different than just generally compiling the wireless drivers. And, I guess I'm asking what do you have to do to compile for 2.02. Also, I notice there is a WPA supplicant on the ZyDAS site. Can this be brought into Puppy?
I know these questions may sound dumb, but could you get me thinking? Thanks.
Don
I stand corrected. I think you mentioned this before, but missed the point.No, they're two separate modules.
When you compile wireless drivers for Puppy 2.0/2.01, how is it different than just generally compiling the wireless drivers. And, I guess I'm asking what do you have to do to compile for 2.02. Also, I notice there is a WPA supplicant on the ZyDAS site. Can this be brought into Puppy?
I know these questions may sound dumb, but could you get me thinking? Thanks.
Don
Re: Wireless driver packages for Puppy2
I have an internally mounted NL-5354MP Plus Aries2(F) - 1.00tempestuous wrote: Plus there are updated versions of drivers I earlier provided for Puppy 1.0.4-1.0.9 at http://mymirrors.homelinux.org/puppy/wireless/
- acx (TexasInstruments), adm8211, Hostap (Prism2/3), HostAP Daemon, ipw2100, ipw2200, linux-wlan-ng (Prism2/3 USB), MADWiFi (Atheros), Orinoco-with-rfmon-patch, Prism54, ralink-legacy, rt2x00 (Ralink), rtl8180-sa2400 (Realtek), zd1211 (Zydas), and wpa_supplicant.
The chip is labeled Atheros AR5213A-00 A19911C 1804
The drivers are missing from this location and not on the 2.00, 2.01 location.
Other locations possible?
Thanks! doc
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
donde,
"drivers" is a loose Windows-esque term for what is, in Linux parlance, "modules".
Modules are kernel-specific. So when the kernel changes, all modules must change with it. Puppy 2.02 has the same kernel version as 2.0/2.01, but its kernel configuration is significantly different, so the modules are incompatible.
I have already provided wpa_supplicant as a dotpup at http://www.dotpups.de/dotpups/Wifi/wireless-drivers/. It's a "helper" utilty for various wifi drivers, and I see that the zd1211 driver is now (apparently) compatible.
You can use wpa_supplicant in ANY version of Puppy, since it's a utility, not a driver. I know it's confusing being amongst drivers, so I will ask Mark to re-organise the download directories.
edoc,
The Puppy 1.0.4-1.0.9 wifi drivers at http://mymirrors.homelinux.org/puppy/wireless/ were corrupted in June and have just been removed completely. I didn't think that there was a demand for these drivers any more.
But I'm organising alternative arrangements at the moment.
"drivers" is a loose Windows-esque term for what is, in Linux parlance, "modules".
Modules are kernel-specific. So when the kernel changes, all modules must change with it. Puppy 2.02 has the same kernel version as 2.0/2.01, but its kernel configuration is significantly different, so the modules are incompatible.
You need the compiling tools and the configured kernel source. See my post at the top of this page.donde wrote:I guess I'm asking what do you have to do to compile for 2.02
I have already provided wpa_supplicant as a dotpup at http://www.dotpups.de/dotpups/Wifi/wireless-drivers/. It's a "helper" utilty for various wifi drivers, and I see that the zd1211 driver is now (apparently) compatible.
You can use wpa_supplicant in ANY version of Puppy, since it's a utility, not a driver. I know it's confusing being amongst drivers, so I will ask Mark to re-organise the download directories.
edoc,
The Puppy 1.0.4-1.0.9 wifi drivers at http://mymirrors.homelinux.org/puppy/wireless/ were corrupted in June and have just been removed completely. I didn't think that there was a demand for these drivers any more.
But I'm organising alternative arrangements at the moment.
All is working now. Guess it executed so fast I didn't even see it!tempestuous wrote: The Puppy 1.0.4-1.0.9 wifi drivers at http://mymirrors.homelinux.org/puppy/wireless/ were corrupted in June and have just been removed completely. I didn't think that there was a demand for these drivers any more.
But I'm organising alternative arrangements at the moment.
Showed up when I powered back up this morning.
Thanks! doc
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
tempestuous wrote:
So, as I understand it, the WPA supplicant you show in your drivers list should work with my zd1211b, by following the readme?
Don
Thanks for making more clear about kernels, modules and drivers.I have already provided wpa_supplicant as a dotpup at http://www.dotpups.de/dotpups/Wifi/wireless-drivers/. It's a "helper" utilty for various wifi drivers, and I see that the zd1211 driver is now (apparently) compatible.
So, as I understand it, the WPA supplicant you show in your drivers list should work with my zd1211b, by following the readme?
Don
We have renamed the folders on the server, to avoid confusion about different Puppyversions.
If you try to download a file, and it is not available, go here and search in the subfolders:
http://dotpups.de/dotpups/Wifi
Mark
If you try to download a file, and it is not available, go here and search in the subfolders:
http://dotpups.de/dotpups/Wifi
Mark
That is great news!!MU wrote:We have renamed the folders on the server, to avoid confusion about different Puppyversions.
If you try to download a file, and it is not available, go here and search in the subfolders:
http://dotpups.de/dotpups/Wifi
Mark
Thanks! doc
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Yes.donde wrote:So, as I understand it, the WPA supplicant you show in your drivers list should work with my zd1211b, by following the readme?
The correct command line parameter for wpa_supplicant to interact with the Zydas driver is the generic "wext", so your main command will be -
wpa_supplicant -i wlan0 -D wext -c /etc/wpa_supplicant.conf -dd
tempestuous wrote
Once encryption is enabled, is there a way to disable it, and then enable it again?
Don
Thanks very much. Would not have known about "wext". Another question:Yes.
The correct command line parameter for wpa_supplicant to interact with the Zydas driver is the generic "wext", so your main command will be -
Once encryption is enabled, is there a way to disable it, and then enable it again?
Don
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Encryption settings are contained within your wifi access point/router. Refer to your router's documentation.
Normally you access these settings with a web browser from an ethernet-connected workstation.
When setting up a wifi driver for the first time, it's certainly a good idea to initially disable encryption, to isolate potential problems.
Normally you access these settings with a web browser from an ethernet-connected workstation.
When setting up a wifi driver for the first time, it's certainly a good idea to initially disable encryption, to isolate potential problems.
- Spindoctor
- Posts: 118
- Joined: Sat 15 Jul 2006, 20:32
- Location: Vienna, Austria
- Contact:
I just tried to use the bcm43xx-devicescape driver with my Belkin F5D7011 PCMCIA-Card.
It doesn't actually work...
It says
I'm going to use ndiswrapper again, which is - as some people say - not so good.
Any suggestions?
It doesn't actually work...
It says
Code: Select all
sh-3.1# modprobe bcm43xx-d80211
WARNING: Error inserting 80211 (/lib/modules/2.6.16.7/net/d80211/80211.ko): Invalid module format
FATAL: Error inserting bcm43xx_d80211 (/lib/modules/2.6.16.7/net/wireless/bxm43xx-d80211/bcm43xx-d80211.ko): Invalid module format
Any suggestions?
donde, I don't know that I'ld be getting the latest drivers from their site any more. Atheros apparently just bought them out a few days ago, and the ZyDAS site is now a mirror of the Atheros site. There is no information for the ZYDAS products, the old download links are now broken, and the new URLs have been changed and pretty much hidden.donde wrote:Looking at the ZyDAS site...
(To get there, click "Products & Technology", scroll down to the bottom of the links on the left and then click -
"Taiwan Research & Development Center", then click "Downloads".)
My understanding is that while the original Linux driver was contributed by ZyDAS, the ZD1211 driver is being actively maintained by the open source community -
http://zd1211.ath.cx
and the download page at -
http://zd1211.ath.cx/download/
A quick check confirmed that the most recent files contained in the driver on the ZyDAS site are several months older than the latest version (r83) found at the link above.
These same folks are also working on a complete rewrite of a new, improved Linux driver, called ZD1211rw, see -
http://zd1211.ath.cx/wiki/DriverRewrite
They gave a short presentation about this at the Linux Wireless developers summit, see -
http://www.deine-taler.de/zd1211/zd1211-wisu.pdf
Which says, among other things, that...
Their new rewrite version has now been included in the official mainline Linux kernals as of 2.6.18-rc1."Zydas was not capable of writing a decent driver"
Unfortunately, they are not providing backwards compability for the older kernals, and I think Puppy is still a few versions behind that?
As indicated on that site, there are different versions of the AirLink 101 AWLL3026 with different USB ID's, some (mine) require the 1211 driver, others the 1211b.donde wrote:I'm using the AirLink AWLL3026 wireless adapter...
That works great for me as well, using the previous Puppy drivers tempestuous was kind enough to provide, I just can't get 2.02 to work!donde wrote:...but done so in 2.01r2...
The only ZD1211 driver that I could find for 2.02 was provided by kirk, who for some reason included only the ZD1211b version and not the ZD1211!
What other issues were you having with 2.02? If there are good reasons to avoid 2.02 for now and just use 2.01r2, I would be interested in hearing about them!donde wrote:...Went back from 2.02 because other issues.
Mark, I looked there, but I could find no distinction between the completely incompatible Puppy V2.01 vs V2.02 drivers, just a generic directory called "drivers-for-Puppy-2".MU wrote:We have renamed the folders on the server, to avoid confusion about different Puppyversions.
If you try to download a file, and it is not available, go here and search in the subfolders:
http://dotpups.de/dotpups/Wifi
Mark, apparently I'm not the only one still confused. Spindoctor, did you download that driver from the site Mark mentioned above? I'm just guessing, but I suspect that the reason for the error message may be that the driver you downloaded is not compatible with the current version of Puppy?Spindoctor wrote:I just tried to use the bcm43xx-devicescape driver with my Belkin F5D7011 PCMCIA-Card.
It doesn't actually work...
It says...
Invalid module format
Are any of these drivers compatible with the current version of Puppy?
Where do I need to go to get a Puppy ZD1211 driver that works with V2.02?