I'm running a basic install of RH 7.3 with all "patches" as of 07/12/02.

I have a Linksys WPC11 (v1), installed in a Thinkpad T22.

On insertion I get two "high" tones, and iwconfig shows the card with wireless extentions and essid properly set, but doesn't connect to the WAP (Also a Linksys - a WAP11). This worked on my TP765L...

The only error I get is something along the lines of " WMAC - unsuccessfully negotiated". I don't have it with me (at work) but that the basic gist of the message.

The only thing out of "wack" seems to be that it loads the wvlan_cs, and based on other threads here, I got the impression it should be loading the orinoco_cs driver.

Yes, I have the hermes.conf...

Ideas? or should it be using the wvlan?

Thanks,
Drew

You probably have either a WPC11 v2.5 or v3, both of which take a little editing of the hermes.conf script in order to get cardmgr to bind the right module. If it's version 3, this should work:

card "Instant Wireless Network PC Card"
manfid 0x0274,0x1613
bind "orinoco_cs"

According to this thread

If its version 2.5,

"Linksys WPC11 v2.5"
manfid: 0x0274, 0x1612
bind "orinoco_cs"

Evidently those hacks will work, although I haven't had the hardware to test it myself. If they don't then Linksys has gone funky with the ident again and you can probably get it working by juggling that first line a little.

Cheers,

Finegan

That is is a version 1.

I've had it close to 9 months, and although I don't recall the exact text, it reports something like V01.02... Also the manfid is 0x0156, 0x0002.

As I said, I had this working on my old TP765L, with pcmcia-cs. So I know it works. ( I was using RH7.0, and compiled pcmcia-cs myself...)

Is the wvlan_cs the correct driver on RH7.3? Should I just compile the latest version of pcmcia-cs?

Thanks,
Drew

The wvlan_cs is the old driver for lucent/orinoco based cards that ran on a chipset from agere and Intersil similar to the one in the prism2 (WPC11 is one) cards. Cardmgr mis-identifies the WPC11 as a Prism1 card, the driver will not work. That .conf file should be sourced by the cardmgr and bind the orinoco_cs module (actually... 3 orinoco, orinoco_cs, and hermes), to the card.

If hermes.conf is in /etc/pcmcia, there's a common mistake that some people save it there via a web-browser like netscape that will add the .txt extension so cardmgr will ignore it. That's all I can really think of offhand... Check /var/state/pcmcia/stab (although its different in different distros, that's slack.) and compare the card ident to that in hermes.conf...

Getting a new pcmcia-cs won't help as your laptop isn't running on pcmcia-cs now, everything was moved into the kernel with 2.4.3, David Hinds isn't putting out pcmcia-cs as often anymore, mostly for legacy kit. To get pcmcia-cs to work, first you would have to re-compile the kernel without in-kernel support, then compile pcmcia-cs... and really its probably just a matter of hacking up hermes.conf

Now that all of the pcmcia configuration is user-space, the distros have slacked off and their pcmcia files are a mess, hence the lack of inclusion of a .conf script for the prism2 cards although the modules are there.

Cheers,

Finegan

OK, I've got the orinoco_cs driver loading. It finds the card
sets the essid correctly...

Now I'm getting "eth1: Tx error! resetting card" in messages.

Found some links through searches, but nothing has a
positive effect. Tried some opts for the orinoco (vcc setting)
as well as PCIC opts, but I don't think they are relevant to
yenta, which is the PCIC my Thinkpad (T22) uses.

iwconfig reports as expected...

card is using interrupt 3.

Ideas?

I got that a lot with my WPC11 v1 as well... crap. I eventually got around it by using the newer drivers, long past v.09b that comes with the 2.4.18 kernel. You can download them here. Also, if you have the option of upgrading the firmware past .8 that'll probably get it to work too... honestly, I messed with my first wpc11 so much and so long I can't remember what did the trick.

Cheers,

Finegan

In short, and without going into a lot of detail.

or in otherwords, to make a very long story short...

If your using a Linksys BEFW11S4 - V2 make sure you
do not upgrade the firmware to version 1.42.7.

After down revving to 1.40.2 ( the original), everything came
on line... 3 weeks of head banging...

Andrew