Jean Tourrilhes's pages, where this one said that the "ZyDAS ZD1211 driver (USB dongles)" were supported.
Downloaded zd1211-firmware1.1.tar.bz2 from this Sourceforge page.. Copied it to floppy, then on adam, mount /media/floppy cp -p zd1211.bz2 zd1211.bz2 tar -jxf zd*2 which created a zd1211-firmware directory. The README in there said to copy everything to /lib/firmware/zd1211, so I cd zd1211-firmware mkdir /lib/firmware/zd1211 cp -p * /lib/firmware/zd1211 and rebooted. Nothing much has changed. Time to dig deeper. There's a lsusb command that says there are 2 USB devices, Bus 001 Device 002: ID 0ace:1215 ZyDAS Bus 001 Device 001: ID 0000:0000 In /var/log/messages, there are 3 sets of USB lines from the 3 times I booted with this device plugged in, e.g. Jun 27 10:27:36 adam kernel: usb 1-1: new full speed USB device using address 2 Nothing too interesting, though. Back to the web. That Jean Tourrihes page had two other links,
This is for manually configuring the stick as client for an AP, see Configuration for other setups.
See WPAConfiguration for WPA(2) setup instructions.
# This shell script will combine the raw kernel & patch file I've burned
# on CD that I'm presuming is mounted at /media/cdrom. What I do is
# - Unzip /media/cdrom/linux-2.6.17.tar.gz
# - Apply /media/cdrom/patch-2.6.18-rc2.bz2
# to /usr/src/kernels/linux-2.6.17
cd
if [ -d /usr/src/kernels/linux-2.6.17 ]
then echo "Erasing /usr/src/kernels/linux-2.6.17 ..."
rm -rf /usr/src/kernels/linux-2.6.17
echo "Done erasing."
fi
cd /usr/src/kernels
echo "Un-gzip-ing /media/cdrom/linux-2.6.17.tar.gz to /usr/src/kernels/linux-2.6.17 ..."
gzip -d < /media/cdrom/linux-2.6.17.tar.gz | tar xf -
echo "Done with that. Now applying 2.6.18-rc2 patches."
cd /usr/src/kernels/linux-2.6.17
bzip2 -d < /media/cdrom/patch-2.6.18-rc2.bz2 | patch -p1
-----------------------------------------------------------------------------------
I have a Cisco Aironet 340 Series Wireless card, aka PCM340.
The first problem was, when I do the ifup eth1, I get this error message
"airo_cs device eth1 does not seem to be present, delaying initialization.
This went away when I updated the kernel from kernel-2.4.21-4, to 2.4.21-15.
(Well actually, those messages are still there during boot time, but the radio
does soon associate seconds later and AFS comes up just fine.)
But I still could not associate. According to forums, I need to downgrade
the firmware from V5.30.17 to 4.25.30, so I did. This didn't help matters.
(Later, I saw that v5.30.17 was supported, so I reverted it back.)
-----------------------------------------------------------------------------------
Web Links (the more *'s, the more helpful it was)
* http://www.linux-thinkpad.org
* http://bellet.info/laptop/t40.html#wireless
*** http://sourceforge.net/projects/airo-linux
** http://airo-linux.sourceforge.net/
*** Jean Tourrilhes' most excellent Wireless LAN resources for Linux page,
http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/
* David Hinds's Linux PCMCIA Information Page, http://pcmcia-cs.sourceforge.net/
** Cisco's Linux driver, http://www.cisco.com/pcgi-bin/tablebuild.pl/aironet-utils-linux
where I downloaded c:\junk\linux-acu-driver-v21.tar.gz
and the Release Notes PDF file, which I saved at both
c:\junk\Linux-ACU-Driver-v21ReleaseNotes.pdf
and ~jasper/aixnotes/linux/Linux-ACU-Driver-v21ReleaseNotes.pdf
This file told me that firmware v5.30.17 was indeed supported.
** http://www.goonda.org/wireless
* http://thunk.org/tytso/linux/t40.html
-----------------------------------------------------------------------------------
Other commands to explore ...
ifconfig
iwspy = Get wireless statistics from specific nodes
iwlist = Get wireless statistics from specific nodes
iwevent = Display Wireless Events generated by drivers and setting changes
iwpriv = Configure optionals (private) parameters of a wireless network interface
wireless (7)
dhcpcd eth1 (To get an interface to renew the DHCP address)
There's some documentation in /usr/share/doc/wireless-tools-26. It points to
files in the /etc/pcmcia directory, including wireless, wireless.opts, and shared,
but these don't seem to apply. There's this comment in wireless.opts,
Note also that this script will work only with the original
Pcmcia scripts, and not with the default Red Hat scripts.
Send a bug report to Red Hat ;-)
----------------------------------------------------------------------------------
There are (at least) 3 ways to set the WEP key, but only the last appears to work.
1) iwconfig eth1 key 11113333555577779999000022
Doing this gave me these error messages when I do the ifup eth1 command,
Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth1 ; Invalid argument
Determining IP information for eth1...
then after a long time waiting, "failed" get appended after those dots.
Google-ing that error, I found http://www.linuxformat.co.uk/modules.php?op=modload
&name=phpBB_14&file=index&action=viewtopic&topic=8034&forum=1&1
where somebody else was having this same error. He referred to
https://bugzilla.redhat.com/bugzilla/long_list.cgi?buglist=88566
and remarked " It would seem that an 's:' is being insreted into the key in error."
I found /etc/sysconfig/network-scripts/keys-eth1, which contained
KEY=s:111133335555...000022
I removed that 's:' and I now get no errors on the ifup eth1 command. It still
doesn't associate, but at least there are no errors.
Other iwconfig command incantations are,
iwconfig eth1 essid "Radio Free Delphion 2"
iwconfig eth1 essid any (or off)
iwconfig eth1 mode Managed
iwconfig eth1 channel 9
iwconfig eth1 ap any
iwconfig eth1 ap 00:40:96:2a:82:57 (for air2)
iwconfig eth1 ap 00:40:96:2a:2b:ad (for air3)
The above two commands "write" into /proc/driver/aironet/eth1/APList
iwconfig eth1 key 111133335555...000022 restricted
but none of these were doing any good. The web page at
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=109394
is interesting. I can see by
cat /proc/driver/aironet/eth1/Config
that just like this bug says, that none of the redhat-config-network or iwconfig
commands I've been doing, are making any difference. For example, I was trying
iwconfig eth1 channel 11
and the channel wasn't changing.
2) echo 0 11:11:33:33:55:55:77:77:99:99:00:00:22 > /proc/driver/aironet/eth1/WepKey
The web page I got this command from came with a warning that it writes the WEP
key into the card's firmware, but maybe that's for a different card than this
old 340 I have (350, maybe?). I dunno. As far as I could see, this command
made no difference to anything.
Other similar echo-ing into /proc/driver/aironet/eth1,
echo "Mode: Managed" >> /proc/driver/aironet/eth1/Config (Note the double >> !!)
echo "SSID: foo" >> /proc/driver/aironet/eth1/Config
echo "Channel: 10" >> /proc/driver/aironet/eth1/Config
This last command caused even more confusion. The "Channel:" line in
cat /proc/driver/aironet/eth1/Config
is one less than what you specify with a
iwconfig eth1 channel n
command.
3) Add this line to /etc/sysconfig/network-scripts/ifcfg-eth1,
WIRELESS_KEY="11113333555577779999000022 restricted"
I did run into strange problems when I was mucking around with this config file.
Being conscientious, I made a copy of the original
cd /etc/sysconfig/network-scripts
cp -p ifcfg-eth1 ifcfg-eth1.save
This caused a bizarre problem though, when rebooting. Evidently, Linux scans this
directory and tries to start both eth1 & eth1.save, causing this obscure error msg,
Starting pcmcia: Yenta IRQ List 06b8, PCI irq11
Socket Status: 30000010
Yenta IRQ List 06b8, PCI irq11
Socket Status: 30000006
And hangs there. I had to boot into single-user mode to rename ifcfg-eth1.save
to save.ifcfg-eth1. Bizarre.
-----------------------------------------------------------------------------------
Over on the "AP Radio Advanced" page of the WAP's web interface, I found and changed
"Require Use of Radio Firmware 5.02L:" from "yes" to "no".
But as I found out later, this didn't have to be done and I undid it.
-----------------------------------------------------------------------------------