I guess to start off I would kill iptables and ipchains. Unless you are using this as a firewall you don't need either one of those. (I assume you have a firewall further up the network) Next I would fire up the redhat network config tool. (Enter 'neat' from the command line as root) and go through the configuration for it. If the card is already listed in there I would remove it and then add it again. When you go to add it, redhat should identify it. I think you will get a choice of the network card or “other”. If all you see is the other option or a list of devices then your card may have the new chipset in it. Also make sure you have the wireless tools installed and if you are using a custom kernel make sure that you have all of the necessary wireless options compiled in the kernel. By default they should all be there.

Here is the new error:

Cannot activate network device eth1!

Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth1 ; Invalid argument.


Determining IP Information for eth1....failed.

I'm guessing the last part is because I have DHCP enabled on it. What about the 1st section of the error?

What it looks like is happening is that Linux is trying to start the card, but with the wrong driver so the card doesn't know what to do. After while it times out giving you that error message. Because it never connects to your access point it never gets an IP address, Hence the second error. At this point I would say you probably have the new chip set and need the beta driver. I know I was getting a similar error before I installed the beta drivers, but I don't know if it is the same exact one.

When you insert the card do you get two high pitched beeps or low pitched beeps or a combination there of?

The card I am using still bears the Lucent Technologies badge on it, so I doubt it has one of the new chipsets. I did however plugin my other Proxim Orinoco card 1st. When I finally recieved my Lucent card, and plugged it in tody, it stated that my /etc/modules.conf had my alias set to wavlan_cs or something like that? I changed it to orinoco_cs.

Ring any bells?

Unfortunately not. I would say to change it back to the wavelan_cs. In my experience, which I have to admit it limited, Linux has always known better than I have.
What I would do now is start at ground zero. Disable wep if you are using it and just put the card in. Make sure that pcmcia is working correctly. Otherwise you can try and start the card all day long and get nowhere. I think some commands you can use for pcmcia are cardmgr and cardinfo. Check their man pages and the man page for pcmcia. Also if you can I would try using other pcmcia cards, wired and\or wireless.

The thing is that it warned me that it had that wavelan_cs module aliased instead of the orinoco_cs because of me putting in my other card 1st. So I changed it to orinoco_cs.

Ok my card is working now, but I still have 2 issues:

Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth1 ; Invalid argument.

Determining IP information for eth1...PING 192.168.2.1 (192.168.2.1)
56(84) bytes of data.

--- 192.168.2.1 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3999ms , pipe 3 failed.

1. I still have the 1st error message...

2. It looks like it reached out for some DHCP action while I was at my friend's house (Neither error came up till I accually got home), and remembered the stats. The problem we had while at my friend's house was that we were getting no DNS info. Any idea why?

Would the command: dhcpcd -H be needed in this case? If so, I'll try once I'm near an access point again..

Any clues??

how old are these cards. It really sounds like your just using the wrong driver...

Not sure on the age. The model info for the silver card (the only one I plan to use under Linux) is above.

Ok,

I did a cardctl ident and got the following:

Socket 0:

no product info available
Socket 1:

product info: "Lucent Technologies", "WaveLAN/IEEE", "Version 01.01", ""

One thing that helped was updating the " neat " package. I ran a test by giving the card a static IP address, and it was activated as eth1.

Try using the Wavelan driver. I know there is or at least should be one called wavelan_cs. There is also a wvlan_cs which may work.

I downloaded the orinoco_cs version 13e this morning, and installed it. I seem to be getting closer to my goal.

Ok, I have the agere systems Orinoco card. I've compiled and installed the beta drivers on a Dell Inspiron 8100 running Gentoo. When I insert it, it completely hard locks my machine. I found something on another board that in my /etc/pcmcia/config.opts I should change my port from 0x100-0x4ff to 0x300-0x4ff and exclude 0x100-0x2ff. This keeps my machine from locking, however, I then get the following error when it's trying to load the driver:

wlags49_h2_cs.o:>:init_module
wlags49_h2_cs v7.08 for PCMCIA, 07/25/2003 09:34:00 by Agere Systems, http://www.agere.com
Station Mode (STA) Support: YES
Access Point Mode (AP) Support: YES
wlags49_h2_cs.o:>>:wl_adapter_init_module
wlags49_h2_cs.o:wl_adapter_init_module wl_adapter_init_module() -- PCMCIA
wlags49_h2_cs.o:<<:wl_adapter_init_module
wlags49_h2_cs.o:<:init_module
wlags49_h2_cs.o:>:wl_adapter_attach
wlags49_h2_cs.o:>>:wl_device_alloc
wlags49_h2_cs.o:<<:wl_device_alloc
wlags49_h2_cs.o:>>:wl_adapter_event
wlags49_h2_cs.o:<<:wl_adapter_event
wlags49_h2_cs.o:>>:wl_adapter_event
wlags49_h2_cs.o:>>>:wl_adapter_insert
wlags49_h2_cs.o:>>>>:wl_insert
wlags49_h2_cs.o:wl_insert Calling hcf_connect()...
wlags49_h2_cs.o:ERROR:wl_insert hcf_connect() failed, status: 0x83
: Wireless, HCF failure: "Timeout on timer calibration during initialization process"
wlags49_h2_cs.o:ERROR:wl_insert wl_insert() FAILED

Anyone have any ideas? I know this is pretty obscure, but I'm hoping for some help.

Thanks.