Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I bought the same card at version 2.5 hoping Linksys had changed something in version 3 that made it not work with Linux anymore. No luck there though. I am still getting the BONG when I insert the card or restart pcmcia.
Took you advice and downloaded the latest orinoco drivers and rebuilt them. Also hacked the hermes.conf file. No luck.
dmesg didn't appear as if my laptop was trying to load any libraries for the card. Very strange.
I just ordered the D-Link card and will pick it tomorrow. Hopefully, I will get this thing to work! With my luck though, it will work with my laptop and the WAP will not recognize it ;-)
Thanks for all the suggestions! I'll keep you posted on how the new card works out.
I don't know if you have fixed your problem, but I have found a site that might be of help. www.yahoogroups.com has a group specifically for Linux on Dell laptops (linux-dell-laptops). The maintainer of the site has an faq on how to set up the wireless lan card, along with the proper scripts. I have an Inspiron 4100 with the Dell TrueMobile wireless card running pretty smoothly, thanks to this site. I would HIGHLY recommend it to anybody running a Dell laptop with linux, and maybe of interest to other general linux-laptop users... The maintainer's website is: http://www.whacked.net/oss/ldl/
I previously said my wireless lan card was running PRETTY smoothly. That is because I'm using a Linksys WAP11 wireless access point. So far in my experience with it in linux, after I boot my laptop, and my pcmcia wireless card is loaded, I then have to cycle the power on my WAP11 the get the card to recognize and communicate with the AP. Maybe I have some setting wrong in linux, though, as I don't have to do this in WinXP. Anyone else have this problem or know of a fix?
You mean you actually have to cycle the power of the wireless router to get it to talk to the network card? That's pretty strange. It might have to do with channel sorting. What are the configuration values you've given to the wireless card. Also what's the model and driver set you're using?
Sorry it has taken so long to reply, but I've been upgrading to RH 7.3, so I haven't had a chance to get back here, yet.
Anyway, here's the weird thing: I have the exact same wireless access point (Linksys WAP11) at home as I do at work, but I've never had to recycle the power on my home unit. I've checked, and I have the APs set up the same. I use my laptop at home and work, just changing my 'ifconfig' and 'route' settings. I'm now trying to study the config files and am just confusing myself. In /etc/pcmcia I have these config files: wireless.opts, config.opts, hermes.conf. I see that config is used by 'network' when loading, but when is wireless (and wireless.opts) used? I didn't see it listed anywhere in /etc/init.d/pcmcia or network.
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Thanks for replying to my the thread on the same forum. And sorry I was so tied up at work, I didnt logon much at home.. hence the delay. Since this thread had more information regarding my post, I thought it is appropriate for me to carry on the conversation here rather than at the thread I started.
Here is my original post, just in case: http://www.linuxquestions.org/questi...ighlight=WPC11
In your reply you had asked whether my card (WPC11) is a v3. yes it is. I downloaded hermes.conf and saved it under /etc/pcmcia as you'd suggested. Then I did a pcmcia restart. Doesnt seem to help.
here's my /etc/sysconfig/networking/pcmcia/ifcfg-wlan0
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
Yep, you're dead right. The hermes.conf file only has info in it for v.2 of the card. I haven't had to fool with 3.0 yet, but probably will soon as I smoked my 2.0 and mailed it back to Linksys (I don't recommend doing this, getting an RMA out of them is pulling teeth.)
I helped one guy hack through getting 2.5 to work by just changing the card id goop in hermes.conf to reflect his card. You can't really break anything, so just play with it and force restart pcmcia between tries so that cardmgr re-reads the .conf file.
This might also require that you compile the newer version of the drivers. (what's current is about 4 minor versions ahead of the shipping kernel). You can d/l them from a link off of Jean's page about the orinoco drivers.
Post back if none of that works, there are a few more, clumpier, alternatives,
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Finegan, you rock!!
This post comes from my wireless equipped Linux laptop. I just added the following lines to hermes.conf.
card "Instant Wireless Network PC Card"
then did a restart. This time when the services came up, it beeped twice ( two high pitched tones ). So I wrote an ifcfg-eth1 for the new device and it all worked like magic)!!!!!!!!!!!!!
Hope this helps someone else.
Not very necessary at this poing, but hey, do you know what chipset the WPC11 v3 is based on?
Now I'm on my way to fiddle with wireless.opts and enable encryption. Thanks for all your help folks.
Prism2 chipset from Intersil, probably with firmware 0.8 or so. I've pulled 40-bit wep with reliability once in a while, but WEP is pants really and VPN is a hastle, so really: get to know your neighbors because if any of them has the inclination, they can airsnort your packets if they feel like it.
Excellent on getting v3 to work, that fills a big hole in things I was worried about.
Us the command line commands "iwconfig ethX" and "ifconfig ethX" to give it the correct settings. Offhand check "dmesg" to make sure that the kernel device logger isn't spitting a bunch of errors. That second beep means cardmgr is happy, but doesn't mean you're always out of the woods.
iwconfig will change the wireless settings of the card. You need to know your wireless routers network name, also called its essid. Set that with (ethX where X is the number of the eth device, if nothing else you'll figure that out from dmesg... oh also if SuSe is still in the stone ages you may have loaded the reallllly old wvlan_cs drivers and your device may or may not be wvlan0):
Oh, first bring up the device:
ifconfig ethX up
iwconfig ethX essid mysillynetwork
Configure the key (if your using them, WEP sucks, so I never really bother, I haven't got any geek neighbors.)
iwconfig ethX enc 1234123412
If your router is running as a master, then make this one managed(it defaults to ad-hoc depending on the version of the drivers your using. ad-hoc works with a master anyway, but doesn't allow for channel hopping, which will cut down on overhead if there are a bunch of laptops on the LAN.)
iwconfig ethX mode managed
Assuming that you've got one of those router in a box dealy-whoos... this should grab an IP:
Now, as long as the router is configured right:
That should be just about everything. To automate all of this, put those values in /etc/pcmcia/wireless.opts. Also, there are a few mile long threads in the archives here if you have any other, smaller problems.
Its on the SuSe CDs, somewhere, part of an RPM package called wireless_toolsXX.rpm where XX is the version number, hopefully 24-ish. Or download the RPM from here. They stuck it in ap4!!! Made it hard to find.
"iwconfig" without any arguments, will only show the current status of devices that are UP and have an IP address.
If that gives something, then configure it with:
iwconfig eth1 essid nameofnetwork
iwconfig eth1 rate auto
iwconfig eth1 mode managed
iwconfig eth1 enc 1234123412 (if you are using encryption...)
dhcpcd eth1 (if you are in range of the wireless router)
You can set all of this to be configured automagically by editing the file /etc/pcmcia/wireless.opts and changing the info for your card's entry, then if you add a file called... hmmm... gotta look up SuSe.... /etc/rc.config
I, however, have not dealt with SuSe on a laptop, so it may be best to just call dhcp by hand every time you want to use wireless with: