[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Proxim RangeLAN-DS on Dell Latitude 3200



I have an old Dell Latitude 3200 (c. 2000 I would guess) and have just bought a Proxim RangeLAN-DS wireless card to use with a new Debian install. I have a bit of linux experience but am new to Debian.

I've installed a bare-bones install from an image called bf2.4-3.0.23-mini.iso, which included pcmcia-cs 3.1.22 and kernel 2.4, as well as orinoco_cs which is apparently the correct driver for the RangeLAN-DS (Prism2 chipset).

If I boot the computer and login, I can then insert the card and cardmgr tells me the memory area is clean. "cardctl ident" gives the name of the card and manfid 0x0126,0x8000. I can "modprobe orinoco_cs" which installs the module (listed by lsmod, along with hermes and pcmcia_cs), but I can't get it to bring up eth0. On Red Hat I would set alias eth0 orinoco_cs in modules.conf and that'd be it. I set it in /etc/modules/modutils/aliases and ran update-modules, but no luck.

A second but related issue: if I eject and reinsert the card (forcibly or with cardctl) there is a long pause and then I get a "cs: socket 0 timed out during reset". This happens every time I insert or reset the card unless I have just rebooted *and* waited until all the modules are loaded before inserting the card.

I then edited /etc/pcmcia/config and added a line to bind the driver:
card "Proxim RangeLAN-DS"
	manfid 0x0126,0x8000
 	bind orinoco_cs

This now gives the "timed out during reset" error whenever I insert the card, I assume because during the binding process it sends a reset command to the card.

The card is an 8430, f/w 0.7.6. I have read about upgrading the firmware to 0.8.0 or 0.8.3 but haven't been able to figure out how to do that. The updater I downloaded from zcomax refuses to acknowledge the card with either zcomax or Proxim drivers (under Windows Me).

I assume this problem is based in the time out error on the socket (it happens in both card slots). I've found a few postings about this error, and many seem to involve network cards, but I haven't got much farther.

I would greatly appreciate any help or direction on this problem.

Yours,
Hugo Mallinson



Reply to: