Hi Alberto, I wanted to thank you very much for your page on getting ATMEL wireless working on a PCMCIA card. I have referred to it often in my struggles to get my 3COM OfficeConnect PCMCIA card working under RedHat 8.0 (on a Dell Inspiron 4000), and finally (with Igor Fedulov's detailed RH8 directions) was able to succeed tonight, and am writing this email over the 802.11 link even now. I had a couple of comments on the whole process, and one question (at the end). Feel free to share any and all of this with Igor. First, in order to compile the drivers I needed to install the kernel-source RPM as well as the ncurses-devel RPM (needed for the applications, I think). I realize this will be obvious to most Linux cognosceti, but both facts were something I needed to learn the hard way. And as far as I can tell, the need for these packages is not mentioned specifically on any of the help pages. Next, Igor's directions for pulling the code over on CVS worked for me, where the directions given on the atmelwlandriver.sourceforge.net website have not, ever. Don't know quite what to make of that, but there it is. Next, I noticed two syntax errors in the latest version of the /etc/pcmcia/config file. I'm not sure but I believe these were inserted by the atmelwlandriver install. These caused complaints on the startup of pcmcia services, so I was able to correct them: > diff config~ config 1053c1053 < manfid: 0x028a, 0x0002 --- > manfid 0x028a, 0x0002 2127a2128 > bind "xircom_cb" Here you can see that one "manfid" line incorrectly had a colin inserted, and the entry for one of the Xircom devices failed to identify the driver to "bind". Next, once I had the driver installed & working, and properly associating itself with my PCMCIA card, I tried to configure my wireless connection using the redhat-config-network tool (neat) and also the wireless tools (iwconfig). I discovered that in order for the card to properly associate itself with my network I needed to put it in "Managed" mode (rather than the RedHat default of "Auto", which it did not recognize, or the alternative "Ad Hoc"). I also needed to set it to "essid any" but presumably I could also have entered the actual network essid in the "neat" tool if I wanted to do that. Now we come to the part where I am still having trouble. Despite setting up the wireless configuration in neat, correctly as far as I can tell, and getting the correct messages in /var/log/messages (see Igor's writeup) when I insert the card or restart cardmgr services, I am still unable to automatically start networking over the wireless card and get an IP address. No one mentions any additional steps that are required here so I am at a loss. I did see your recommendation of manually attempting a "/sbin/pump -i eth1" and was able to determine that the equivalent command for my system is "/sbin/dhclient eth1", and this was indeed the magic that finally got my system working. But "/etc/init.d/network start" and "neat" still fail to get the network up on their own. So my question for you and/or Igor is: What am I still doing wrong? What command is "neat" attempting to run that fails to have the salutory effects of a simple "dhclient eth1"? As I said at the start, you have been more than sufficiently helpful already so don't worry about this one if you don't have the time. But it is an annoying little thing I still need to get resolved, and I would be grateful for any ideas you might have. Thanks again for the assistance, Cheers, Derek Fox -- ----------------------------------------------------------------------------- Derek Fox Cell: +1 626 676 4729 Postdoctoral Scholar Phone: +1 626 395 4421 Caltech Astronomy MS 105-24 Fax: +1 626 568 9352 1200 E. California Blvd Internet: derekfox(at)astro.caltech.edu Pasadena, CA 91125-2400 http://astro.caltech.edu/~derekfox/ USA -----------------------------------------------------------------------------