Thanks very much to everyone for the suggestions. I've been trying some of the ideas on the list and here's where I am. I tried the newer driver (1.05 instead of 1.03) same difference, loads, scans, can't find anything. I should point out that this is a *laptop* and that I sometimes use a directly wired interface (shows up as eth0 as I would expect) and then sometimes I pop that card out of the pcmcia slot and insert the wireless. Even after switching the modules.conf and adding this: alias eth0 xirc2ps_cs alias eth1 adm8211 The wireless card *always* shows up as eth0. I've rebooted with the card inserted, and it's still showing up as eth0. Any idea *why* that would be the case? Where could I look to resolve that? Beyond that I took a look at the wireless.opts file (/etc/pcmcia/wireless.opt) and set the default card to 'any' for the ESSID (I'm assuming that's the SSID of the AP I want to connect with). Then I noticed this little comment: # 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 ;-) Is this true? That the wireless.opt will not work with the RedHat scripts? Maybe I'm missing some pcmcia stuff that's calling a different file. I noticed there's another script 'wirelss' that's supposed to setup all the stuff related to pcmcia ... but it's refering to a 'scheme' file that I haven't edited, and in the same directory there's a 'stab' file that has my current pcmcia card in it. Should I start with reading the pcmcia howto? Is that were things are screwed up? The redhat configuration scripts show an adapter for wlan0 however fail to configure anything. I'm going to poke around and try to get this card when inserted to show up as eth1, and then I can try all the things suggested about setting up that interface with a HARDWARE address, and GATEWAY address, etc. Thanks for all the input, sorry I haven't been very responsive, I was traveling home from a job site this morning. cheers ian On Thu, 2004-04-29 at 17:08, Rick Stevens wrote: > jludwig wrote: > > On Thu, 2004-04-29 at 16:29, Terry Polzin wrote: > > > >>On Thursday 29 April 2004 14:07, Ian Wallace wrote: > >> > >>>I've searched the archives and tried numerous things however I don't > >>>seem to be able to get my wireless card to work with Fedora Core 1. > >>> > >>>I've downloaded the driver source from ADMtek and compiled it using the > >>>kernel sources for the kernel I'm running (2188.nptl). That works ok, > >>>and when I pop in the card I can see in /var/log/messages that it > >>>recognizes the card, and loads the 8211 driver. > >>> > >>>Beyond that though ... nothing. The power / activity light comes on, it > >>>tries to associated itself with eth0 however never receives an IP from > >>>the access point. > >>> > >>>I've tried the wireless howto's and am a i bit confused if this should > >>>be showing up as wlan0 or eth0, or eth1. Would someone be so kind as to > >>>point me the correct direction for information on how to configure > >>>this? Or where else things might be going wrong? > >>> > >>>TIA > >>> > >>>ian > >>> > >>>-- > >>>Ian Wallace <iwallace@xxxxxxxxxxxxxxxx> > >> > >> > >>What devices show up when you run redhat-config-network? > >>Mayby you need to restart networking as well > > > > > > I had to do some failure analysis on some wireless systems some time ago > > and found that there are at least a few "standards" and even cards from > > different manufacturers supposedly using the same standard may not work > > with each other (Google it I did). > > The key point then, is first make sure that your card(s) will actually > > work on your wireless network. > > You also need to run the iwconfig utility either manually or by > modifying the /etc/pcmcia/wireless.opts file to handle your card. > Without that, your card won't know which network to connect to. If it > can't connect to the network (channel, ESSID, key), you can't get an IP > from the DHCP server. > > See "man iwconfig" for details. > ---------------------------------------------------------------------- > - Rick Stevens, Senior Systems Engineer rstevens@xxxxxxxxxxxxxxx - > - VitalStream, Inc. http://www.vitalstream.com - > - - > - UNIX is actually quite user friendly. The problem is that it's - > - just very picky of who its friends are! - > ---------------------------------------------------------------------- -- Ian Wallace <iwallace@xxxxxxxxxxxxxxxx>
