After reading some other posts, the below should probably be just a guidline: For instance, eth0 might need to be eth1, wavelan2_cs may not be compatible with your card. Proceed with caution
I've never used redhat or other commercial distros, so I'm not familiar with their fanciness. From what I've heard, it's scripts are all mangled, but I'm sure somebody here can probably tell you where to put what information. Okay, here's what I think...
1) Hopefully you control the access point you're trying to connect to. If so, disable any encryption and allow access to all (meaning do not restrict access by MAC address, etc.). The less complex the better for right now.
2) Edit your config scripts to disable DHCP for the time being. If something fails, DHCP takes a long time to time out and just adds complexity. Let's get the card recognized first.
To disable dhcp, I'd probably start with the ifcfg-eth0 file and change BOOTPROTO="dhcp" line. Please help me out, redhat guys...
If you only have one nic, wireless or otherwise, card services should try to set it up as eth0. iwconfig reporting "lo: ..." suggests to me that eth0 is not configured and the network is not running. At the very least, should see:
lo no wireless extensions
eth0 no wireless extensions
However, if lsmod reports that wvlan_cs and ds are loaded, then it seems like the hardware is working alright. You can try to manually start the network and see what happens. (This is where redhat knowledge comes in...) I'm guessing that you should be able to do
/etc/pcmcia/network start eth0
Now type iwconfig again. You should see eth0 in there.
Let me know if any of that works. If it does, then you're getting somewhere. You have a couple options, also. You should get away from the wvlan_cs driver and move up to either wavelan2_cs or orinoco_cs. I'll explain all of that when you get there.
Hope some of this helps.