• Resolving installation and configuration problems
• PCMCIA network adapters

Messages Inline: [ 0 ]  [ All ]  Outline: [ 1 ]  [ 2 ]  [ All ] 

Ok: Uniden Data 2000 wireless CDPD internet card works Date: 1999, Nov 05 From: Bryce Nesbitt brycen

CDPD is a wireless digital IP service available in many cities in the USA. Uniden will claim the Data 2000 card is for the Windows only, but it can be made to work under Linux with little trouble. You may need to upgrade card services if the machine locks up when the card is recognized. This version works: stetson:/etc/X11> uname -rv 2.0.36 #1 Tue Oct 13 22:17:11 EDT 1998 stetson:/etc/X11> cardctl -V cardctl version 3.0.14 I set the modem up under Windows first. Use the undocumented "ATDT2" command, and a static IP, to start SLIP mode in Unix. I did not get PPP to work: 'ABORT' 'BUSY' 'ABORT' 'ERROR' 'ABORT' 'NO CARRIER' 'ABORT' 'NO DIALTONE' 'ABORT' 'Invalid Login' 'ABORT' 'Login incorrect' '' 'ATZ' 'OK' 'ATDT2' 'CONNECT' '' The Data 2000 card sucks rocks, and is nearly unusable on battery. With the power adaptor, it functions at about 1/4 the speed of Uniden's own Data 1000 external modem. Sierra Wireless or Novatel modems may be a better choice. Sierra technical supports says the old cards work on Linux, but the newest card is actually a network adaptor, not a modem. Linux support is unknown, but Sierra is aware of the issue.

Sad: Inet Spider II -- see posting in serial/modem forum Date: 1999, Dec 24 From: Scott Petrack scott.petrack

I have posted to the serial/modem forum a question about getting an Inet Spider wireless CDPD modem to work. I'm putting a link here because it is in fact a wireless networking card (even though my problem is serial/modem related): http://pcmcia.sourceforge.org/cgi-bin/HyperNews/get/pcmcia/serial/9.html Apologies if this is inappropriate -- I put the link here because it might help someone in the future. Thanks, Scott

Question: CDPD with the Sierra Wireless AirCard Date: 2000, Jan 11 From: dkap dkap

I seem to be having trouble getting the Sierra Wireless AirCard300 to be recognized, and used. Does anyone have any reccomendations ... Thanks, -dkap

1. Note: Re: CDPD with the Sierra Wireless AirCard by Roy Murphy, 2000, Jan 24

Question: Netwave AirSurfer Plus and DELL Inspiron 7500 Date: 2000, Jan 24 From: Ronny Bremer rbremer

I switched from a Toshiba Tecra 730 to a DELL Inspiron 7500. Using my old Netwave AirSurfer Plus card and the 3.1.6 pcmcia package I had no problems on the Toshiba, however, on the Dell I get a kernel trap in cardmgr when loading the asplus_cs module. Xircom Ethernet and Madge Tokenring works fine and the card shows no problem on Windows 98. Any ideas? Thank you for your time. Ronny

1. Note: IRQ troubles... by Jean Tourrilhes, 2000, Feb 25

Ok: WaveLAN PCMCIA works with 3.0.14 Date: 2000, Jan 29 From: Ed Swierk eswierk

My old WaveLAN PCMCIA card (not IEEE) works with an unmodified RedHat 6.1 installation, which includes pcmcia-cs-3.0.14. All I had to do to get it to work was add this line to /etc/pcmcia/config.opts: module "wavelan_cs" opts "do_roaming=1" Yay!

1. News: Enabling roaming... by Jean Tourrilhes, 2000, Feb 24

Question: lucent ieee turbo pci adapter Date: 2000, Jan 31 From: Bob Cohen bonobob

kernel version: 2.2.12-20 pcmcia driver version: 3.1.8 I'm having problems with a Lucent Wavelan IEEE Turbo wireless networking card. The wavelan is a pcmcia card that lucent bundles with a PCI adapter for desktop machines. The PCI adapter is based on a TI 1225 chipset. The wavelan configures properly, but interrupts appear not to be working, as I get transmition timeout error messages, and packets are never received by the driver. Also, I get error messages from card services saying: cs: socket 1 timed out during reset so, it seems that interrupts relating to card events also aren't happening. I've tried various combinations of options pertaining to interrupts to the i82365 pcic by modifying /etc/sysconfig/pcmcia, to no avail. Here's what dmesg sez about the pcic probe: Intel PCIC probe:   TI 1225 PCI-to-CardBus at bus 2 slot 10, mem 0x68000000, 2 sockets     host opts [0]: [pwr save] [isa irq] [no pci irq] [lat 168/176] [bus 32/34]     host opts [1]: [pwr save] [isa irq] [no pci irq] [lat 168/176] [bus 35/37]     ISA irqs (default) = 4,7,12 polling interval = 1000 ms cs: IO port probe 0x1000-0x17ff: clean. cs: IO port probe 0x0100-0x04ff: excluding 0x400-0x47f 0x4d0-0x4d7 cs: IO port probe 0x0a00-0x0aff: clean. cs: memory probe 0xa0000000-0xa0ffffff: clean. Here's what dmesg sez about the wavelan card: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.1 wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de> wvlan_cs: index 0x01: Vcc 5.0, irq 7, io 0x0100-0x013f wvlan_cs: Registered netdevice wvlan0 wvlan_cs: Valid channels: 1 2 3 4 5 6 7 8 9 10 11 wvlan_cs: MAC address on wvlan0 is 00 60 1d 1e 78 83 Knowing nothing about any of this stuff, I played around a little with lspci - here's what it says about the card: 02:0a.0 CardBus bridge: Texas Instruments: Unknown device ac1c (rev 01)     Subsystem: Unknown device 104c:ac1c     Flags: bus master, medium devsel, latency 168     Memory at <ignored> (32-bit, non-prefetchable)     Bus: primary=00, secondary=20, subordinate=22, sec-latency=176     16-bit legacy interface ports at 0007 02:0a.1 CardBus bridge: Texas Instruments: Unknown device ac1c (rev 01)     Subsystem: Unknown device 104c:ac1c     Flags: bus master, medium devsel, latency 168     Memory at <ignored> (32-bit, non-prefetchable)     Bus: primary=00, secondary=23, subordinate=25, sec-latency=176     16-bit legacy interface ports at 0007 Why doesn't it list an interrupt? When I do lspci -v -b, I get: 02:0a.0 CardBus bridge: Texas Instruments: Unknown device ac1c (rev 01)     Subsystem: Unknown device 104c:ac1c     Flags: bus master, medium devsel, latency 168, IRQ 255     Memory at 68000000 (32-bit, non-prefetchable)     Bus: primary=00, secondary=20, subordinate=22, sec-latency=176     16-bit legacy interface ports at 0007 02:0a.1 CardBus bridge: Texas Instruments: Unknown device ac1c (rev 01)     Subsystem: Unknown device 104c:ac1c     Flags: bus master, medium devsel, latency 168, IRQ 255     Memory at 68001000 (32-bit, non-prefetchable)     Bus: primary=00, secondary=23, subordinate=25, sec-latency=176     16-bit legacy interface ports at 0007 What is the implication of IRQ 255? Any Suggestions? Bob Cohen bonobob@pacbell.net

1. 3.1.8 can't figure out the interrupt routing by David Hinds, 2000, Jan 31 1. Sad: didn't work by Bob Cohen, 2000, Jan 31 1. Fixed... by David Hinds, 2000, Feb 18 2. Question: "3.1.8 can't figure out the interrupt routing" by Gerald Richter, 2000, Feb 18 1. This is a somewhat rare configuration by David Hinds, 2000, Feb 18 ... 2 Message(s) 3. Idea: Twosamples here... by Jean Tourrilhes, 2000, Feb 25 2. Feedback: same problem for me! by Guillaum Dallaire, 2000, Mar 26 1. More: Contact Andy... by Jean Tourrilhes, 2000, Mar 27 2. PCI interrupt routing? by David Hinds, 2000, Mar 27 1. More: pcmcia startup by Guillaum Dallaire, 2000, Mar 30 ... 1 Message(s) 3. Sad: I see the same thing.. by Mark Geib, 2000, Apr 10 1. This is mostly fixed; if not, then tell me more by David Hinds, 2000, Apr 10 (_ Sad: no luck, here is more info.. by Mark Geib, 2000, Apr 12

Question: Lucent WaveLAN IEEE in ISA PCMCIA Brigde hangs on FTP downloads Date: 2000, Feb 18 From: Gerald Richter richter

Hi, I have an Lucent WaveLan IEEE Turbo Card and have troube when makeing FTP downloads, while ping works without problems. Also FTP uploads works without problems. So it seems to me that there is a problem with receiving large packages. The currious thing is that I have two Linux boxes. On one box it works in both directions on the other I get the trouble, also both have an identical software and configuration. Only the hardware differs slitly. Software is Linux 2.2.13, pcmcia-cs-3.1.10 Hardware is on both boxes Intel BX chipset and VADEM VG 469 ISA to PCMCIA brigde. I have tried various things with different irqs, setting irqs to ISA in the bios, but nothing helps. I also have tried to lower down the MTU size and exchanges the isa and pcmcia boards to exclude a hardware failiure. Any ideas where to search? Thanks Gerald

1. Re: Question: Lucent WaveLAN IEEE in ISA PCMCIA Brigde hangs on FTP downloads by David Hinds, 2000, Feb 19 1. RE: Question: Lucent WaveLAN IEEE in ISA PCMCIA Brigde hangs on FTP downloads by Gerald Richter, 2000, Feb 19 2. News: new Wavelan IEEE driver & debugging by Jean Tourrilhes, 2000, Feb 25 1. RE: News: new Wavelan IEEE driver & debugging by Gerald Richter, 2000, Feb 28 (_ A Wavelan update is imminent by David Hinds, 2000, Feb 28 1. RE: A Wavelan update is imminent by Gerald Richter, 2000, Feb 29 ... 1 Message(s) 2. RE: A Wavelan update is imminent by Gerald Richter, 2000, Mar 01

Question: Wireless card choice Date: 2000, Mar 15 From: Duane Gustavus duane

Hi, I am in the process of building a PC/104 Linux system to put on a robot. I have not yet purchased the wireless ethernet link hardware, and am wondering if folks here have suggestions. I would prioritize stability over performance, and can accept an indoor range of 150 feet or so. If it matters, I am using Redhat 6.1 with kernel 2.2.14 and pcmcia services 3.1.12. Aironet 4800 seems interesting, but I have no experience at all in this technology. Thanks, Duane

1. Idea: See the Howto by Jean Tourrilhes, 2000, Mar 15

Question: Problem with Cabletron RoamAbout Date: 2000, Mar 21 From: Danilo Godec danci

I have linux 2.2.14 and pcmcia-cs-3.1.13. Everything seems to be just fine, modules load up, the wvlan0 interface is configured. But when I try to use the card (ping, telnet...), I get this message: wvlan_cs: WMAC did not have sufficient RAM to build unsollicited frame! What should I check? Thanks, Danilo

1. Sad: WMAC did not have enough RAM to build unsollicited frame! by Danilo Godec, 2000, Mar 23 1. Feedback: Solved (sort of) by Danilo Godec, 2000, Mar 23 2. Ok: Solved (for good, by Andy) by Danilo Godec, 2000, Mar 29

Note: Maybe harmless, ask Andy... Date: 2000, Mar 23 From: Jean Tourrilhes jt

Hi, I never saw that with my various Wavelan IEEE cards, but I remember that Andy mentionned it. I think it's a message comming from the card itself (not the driver) and that it is harmless, but send him a quick e-mail... Jean

Question: two PCMCIA-ISA adapters Date: 2000, Mar 26 From: Guillaum Dallaire gd

Hi, I'm testing 2 PCMCIA to ISA bridge with 1 wavelan card each (in the same machine). When two card ard inserted, only one is working. When I insert the second card, I get : wvlan_cs: Initialization failed! When I type iwconfig, I get : wvlan0 IEEE 802.11-DS ESSID="test" Nickname:"dev-1" Frequency:2.422GHz Sensitivity:1/3 Mode:Ad-Hoc .... ...... wvlan1 IEEE 802.11-DS ESSID="" Frequency:52Mhz Sensitivity:0/3 Mode:Ad-Hoc Access Point: FF:BF:01:00:01:01 Bit Rate=0kb/s RTS thr=0 B Fragment thr=0 B is there any way to get the second card working ? how can I setup different config (station_name, channel, etc) to the second card when the card is inserted ? thanks!!

1. Sad: Ouch ! Not supported yet... by Jean Tourrilhes, 2000, Mar 27 1. Support for multiple WaveLAN/IEEE cards on one host. by Guillaum Dallaire, 2000, Mar 27 2. More: Same problem, 2 pcmcia cards on one isa adapter (with 2sockets) by Raul Elizondo, 2000, May 18

Question: Wavelan Linux Bridge Date: 2000, Mar 30 From: Benny Brown Benny

Hi to all, My problem is to join two LAN through a Linux BOX, having 2 network cards, one 3COM 3C509B and one Wavelan/IEEE Card with ISA/PCMCIA adapter. I have tried to make a bridge between the two cards, using the last version of the Andy's drivers that would have to support promiscous mode... I have scrupulously read the Bridging HOWTO, but my bridge still does not work! Is There someone that succeed to make a linux bridge with the wavelan?

1. Sad: Likely not possible... by Jean Tourrilhes, 2000, Mar 30 (_ Question: How do base stations do it, then? by Marcel Waldvogel, 2000, Apr 18

Sad: Linux Bridge Date: 2000, Mar 30 From: Benny Brown Benny

Has anyone been able to configure a Linux bridge between a Wavelan and a regular Ethernet board? I haven't! Thanks for all the help you can give me...

Question: "receive buffer overflow" with wavelan driver Date: 2000, Apr 02 From: John Ruttenberg rutt

I am running linux 2.2.14 and pcmcia 3.1.13 on a new dell inspiron 5k. Sometimes during largish downloads, I get the following messages: ewrfp 2368 lp->rfp 3954 Apr 2 11:48:25 alice kernel: eth0: wv_interrupt(): receive buffer overflow Apr 2 11:48:25 alice kernel: eth0: wv_packet_rcv(): no new frame: i593_rfp 3181 stop 4627 newrfp 6559 lp->rfp 182 Here is a more complete extract from the syslog: Apr 2 11:31:09 alice kernel: Linux PCMCIA Card Services 3.1.13 Apr 2 11:31:09 alice kernel: kernel build: 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 Apr 2 11:31:09 alice kernel: options: [pci] [cardbus] [apm] [pnp] Apr 2 11:31:09 alice kernel: PCI routing table version 1.0 at 0xfdf50 Apr 2 11:31:09 alice kernel: PnP: PNP BIOS installation structure at 0xc00f7220 Apr 2 11:31:09 alice kernel: PnP: PNP BIOS version 1.0, entry at f0000:a77c, dseg at 400 Apr 2 11:31:09 alice kernel: Intel PCIC probe: Apr 2 11:31:09 alice kernel: TI 1225 PCI-to-CardBus at slot 00:04, mem 0x68000000 Apr 2 11:31:09 alice kernel: host opts [0]: [ring] [serial pci & irq] [pci irq 11] [lat 168/32] [bus 32/34] Apr 2 11:31:09 alice kernel: host opts [1]: [ring] [serial pci & irq] [pci irq 11] [lat 168/32] [bus 35/37] Apr 2 11:31:09 alice kernel: PCI irq 11 seems to be wedged! Apr 2 11:31:09 alice kernel: PCI irq 11 test failed Apr 2 11:31:09 alice kernel: ISA irqs (default) = 10 polling interval = 1000 ms Apr 2 11:31:09 alice cardmgr[1005]: starting, version is 3.1.13 Apr 2 11:31:09 alice cardmgr[1005]: watching 2 sockets Apr 2 11:31:09 alice kernel: cs: IO port probe 0x1000-0x17ff: clean. Apr 2 11:31:09 alice kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x370-0x37f Apr 2 11:31:09 alice cardmgr[1005]: could not adjust resource: IO ports 0x300-0x3ff: Device or resource busy Apr 2 11:31:09 alice cardmgr[1005]: could not adjust resource: IO ports 0x200-0x27f: Device or resource busy Apr 2 11:31:09 alice cardmgr[1005]: initializing socket 0 Apr 2 11:31:09 alice kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. Apr 2 11:31:09 alice cardmgr[1005]: socket 0: Digital RoamAbout/DS Apr 2 11:31:10 alice cardmgr[1005]: executing: 'insmod /lib/modules/2.2.14-5.0/pcmcia/wavelan_cs.o' Apr 2 11:31:10 alice kernel: eth0: WaveLAN: port 0x100, irq 10, hw_addr 08:00:0E:21:55:35, nwid off, PCMCIA, 915 MHz Apr 2 11:31:10 alice cardmgr[1005]: executing: './network start eth0' Apr 2 11:32:12 alice PAM_pwdb[878]: (su) session closed for user root Apr 2 11:35:55 alice kernel: eth0: wv_interrupt(): receive buffer overflow Apr 2 11:35:55 alice kernel: eth0: wv_packet_rcv(): no new frame: i593_rfp 7469 stop 698 newrfp 2496 lp->rfp 4286 Apr 2 11:36:05 alice kernel: eth0: wv_interrupt(): receive buffer overflow Apr 2 11:36:05 alice kernel: eth0: wv_packet_rcv(): no new frame: i593_rfp 1003 stop 2444 newrfp 6643 lp->rfp 261 Apr 2 11:36:55 alice kernel: eth0: wv_interrupt(): receive buffer overflow Apr 2 11:36:55 alice kernel: eth0: wv_packet_rcv(): no new frame: i593_rfp 4461 stop 5876 newrfp 5831 lp->rfp 7615 Apr 2 11:37:20 alice kernel: eth0: wv_interrupt(): receive buffer overflow Apr 2 11:37:20 alice kernel: eth0: wv_packet_rcv(): no new frame: i593_rfp 5229 stop 6690 newrfp 4407 lp->rfp 6237 Apr 2 11:37:30 alice kernel: eth0: wv_interrupt(): receive buffer overflow Apr 2 11:37:30 alice kernel: eth0: wv_packet_rcv(): no new frame: i593_rfp 3115 stop 4556 newrfp 4813 lp->rfp 6623 Apr 2 11:37:55 alice kernel: eth0: wv_interrupt(): receive buffer overflow Apr 2 11:37:55 alice kernel: eth0: wv_packet_rcv(): no new frame: i593_rfp 2861 stop 4276 newrfp 2400 lp->rfp 4184 Apr 2 11:38:05 alice kernel: eth0: wv_interrupt(): receive buffer overflow Apr 2 11:38:05 alice kernel: eth0: wv_packet_rcv(): no new frame: i593_rfp 3501 stop 4705 newrfp 5518 lp->rfp 7091 Apr 2 11:38:10 alice kernel: eth0: wv_interrupt(): receive buffer overflow Apr 2 11:38:10 alice kernel: eth0: wv_packet_rcv(): no new frame: i593_rfp 1005 stop 2439 newrfp 4141 lp->rfp 5944 Apr 2 11:38:20 alice kernel: eth0: wv_interrupt(): receive buffer overflow Apr 2 11:38:20 alice kernel: eth0: wv_packet_rcv(): no new frame: i593_rfp 5482 stop 6923 newrfp 2838 lp->rfp 4648 Apr 2 11:38:30 alice kernel: eth0: wv_interrupt(): receive buffer overflow Apr 2 11:38:30 alice kernel: eth0: wv_packet_rcv(): no new frame: i593_rfp 7789 stop 801 newrfp 7707 lp->rfp 1088 Apr 2 11:39:10 alice kernel: eth0: wv_interrupt(): receive buffer overflow Apr 2 11:39:10 alice kernel: eth0: wv_packet_rcv(): no new frame: i593_rfp 365 stop 1792 newrfp 1982 lp->rfp 3778

1. Idea: A few suggestions... by Jean Tourrilhes, 2000, Apr 03 (_ More: Oups ! by Jean Tourrilhes, 2000, Apr 03

Question: Cross-platform communications problems Date: 2000, Apr 05 From: Dagmar d'Surreal Dagmar_dSurreal

I have a pair of the Airport 2.4Ghz wireless cards made by Webgear. (For $130-170 these kits really can't be beaten) Now that I've finally gotten the things to begin connecting regularly I've noticed something annoying... Windows cannot talk to Linux using these things and vice-versa. Is there something I am overlooking? With linux on both ends the cards work fine. With Windows on both ends the cards work fine. Trying to get either machine to see each other when the OSes are different is rather problematic. The second LED flashes as if they were seeing packets from each other, but for some reason simply don't choose to acknowledge them. Is this a WEP thing and if so does anyone know how to break it? ;)

1. Windows and Linux may be using incompatible settings by David Hinds, 2000, Apr 05

Question: WaveLan PCMCIA card Problems Date: 2000, Apr 09 From: Zach Berke zberke

hey there. I'm having a little trouble getting the WaveLan (or Orinico or whatever) wireless PCMCIA card working on my Dell Inspiron 7000 laptop. I wonder if anyone can help. I think the problem is that the computer for some reason thinks that the card is my ethernet card, so it trys to access the ethernet card's MAC address. Everytime it does this (which is whenever I pop the wavelan card in), the computer freezes up completely. Here's what happens if i do a tail -f /var/log/messages right before I pop the card in: (i'm copying this down by hand so any typos are my fault, not a big bug). cardmgr[471]: initializing socket 1 cardmgr[471]: socket 1: Lucent Technologies WaveLAN/IEEE cardmgr[471]: executing: 'insmod /lib/modules/2.2.14-5.0/pcmcia/wavelan_cs.o' cardmgr[471]: eth0: wv_hw_config(): modem not connected or not a wavelan card cardmgr[471]: executing: './network start eth0' kernel: wv_82593_cmd: wv_82593_config(): configure timeout, status0 0x00 kernel: eth0: wavelan_watchdog: wathdog timer expired kernel: eth0: wavelan_watchdog: abort failed, trying reset kernel: eth0: wv_mmc_init(): Invalid MAC address: FF:FF:FF:... and now it's frozen thanks a lot for any help you can give me.

1. This is the wrong driver for the IEEE card by David Hinds, 2000, Apr 10

Warning: Problem with TI1225 and Lucent Wavelan (even in 3.1.14) Date: 2000, Apr 12 From: Alen Salamun ALiEN

Hi! There are still big problems with TI1225 controler from Lucent. I have 2.2.14 and just compiled PCMCIA 3.1.14. Now just right after initialisation my system HANGS!!! I can only see: Socket 0: Lucent... And then it halts....I tired with PCIC_OPTS="irq_mode=0" but it doesn't help. Bye, Alen

1. Need more information by David Hinds, 2000, Apr 12 1. More: More info on the problem by Alen Salamun, 2000, Apr 12 2. More: Same with me... see posting in thread "6." by Mark Geib, 2000, Apr 13 3. News: FIX for Lucent's wavelan driver! Now it "works" with TI1225! by Alen Salamun, 2000, Apr 16 1. Disagree: This patch doesn't work for me (details inside) by Michael Vasilenko, 2000, Apr 18 4. News: Beta wavelan driver from Lucent by David Hinds, 2000, Apr 19 1. Sad: Where is the beta driver? by Tommy Svensson, 2000, May 09 (_ It is on the Linux PCMCIA ftp site by David Hinds, 2000, May 09

Question: Apple Airport cards in a PC Date: 2000, Apr 14 From: Kelly Murray kem

I would like to use the Apple Airport cards in an intel PC or laptop. In Jean_Tourrilhes excellent wireless writeup, it says the cabletron Wavelan cards are the same as the Airport, but >Note that the interface doesn't seem to be Pcmcia compatible > even is the connector is the same, so this card can't be > used in the normal PC-Card slot of other laptops Having looked at the apple card, it certainly LOOKS like a standard PCMCIA card piggy-backed onto some MAC carrier. It doesn't make sense to me that it would be different. Has anyone actually tried the apple card in a laptop? The Apple cards are significantly cheaper, and when you are buying a lot of them, the cost is very significant. -Kelly Murray kem@htrd.com

1. These cards do not work in standard PCMCIA slots by David Hinds, 2000, Apr 14

Question: Untitled Date: 2000, Apr 18 From: Jonathan Chan jchan

Dear all, I have a pair of WaveLAN IEEE (silver) cards installed in my laptop (Toshiba 300CT) and a desktop (P 133), but the values of link layer status are all zero at /proc/net/wireless. Except this, everything works fine... (ping, telnet, etc) I attempted to use both wvlan_cs and wavelan2 drivers, they both had the same problem. Now if I changed the cards to be the old WaveLAN, its link layer status was shown in /proc/net/wireless without any problem!! Did I miss something?? I am using: - redhat 6.2 - kernel 2.2.14 (with CONFIG_NET_RADIO=y) - pcmcia_cs 3.1.14 - wireless_tools 20 At /etc/pcmcia/config.opts, I use the fault values: module "wvlan_cs" opts "port_type=3 channel=1 station_name=MY_PC" Thanks in advance for your suggestions... Cheers, Jonathan

1. News: /proc/net/wireless in ad-hoc mode... by Jean Tourrilhes, 2000, Apr 18 (_ Question: iwspy on WaveLAN operating at other sub-band frequencies by Jonathan Chan, 2000, Apr 18 (_ Sad: Untitled by Jean Tourrilhes, 2000, Apr 24

Sad: RoamAbout fails to initialize with new firmware Date: 2000, Apr 18 From: Chris Hanson <cph@zurich.ai.mit.edu>

I recently got a Cabletron RoamAbout DS card, which worked fine using the wvlan_cs driver from pcmcia-cs 3.1.14. As shipped, the card uses firmware version 4.0. However, when I updated the card to firmware version 6.0 (file "RoamAbout-AP-60000-fw.zip" on Cabletron's web site), the GPL driver stopped working. The non-free driver, called "roamabout_cs", still works fine (I think that is a repackaged version of "wavelan2_cs"). The GPL driver fails with the following error messages: Apr 17 09:46:42 ravna kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4 Apr 17 09:46:42 ravna kernel: wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de> Apr 17 09:46:42 ravna kernel: wvlan_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f Apr 17 09:46:42 ravna kernel: wvlan_cs: Registered netdevice wvlan0 Apr 17 09:46:42 ravna kernel: wvlan_cs: Initialization failed! Apr 17 09:46:48 ravna kernel: wvlan_cs: wvlan0 Tx timed out! Resetting card Apr 17 09:46:48 ravna kernel: wvlan_cs: Initialization failed! Apr 17 09:46:58 ravna kernel: wvlan_cs: wvlan0 Tx timed out! Resetting card Apr 17 09:46:58 ravna kernel: wvlan_cs: Initialization failed! Apr 17 09:47:08 ravna kernel: wvlan_cs: wvlan0 Tx timed out! Resetting card Apr 17 09:47:08 ravna kernel: wvlan_cs: Initialization failed! Apr 17 09:47:18 ravna kernel: wvlan_cs: wvlan0 Tx timed out! Resetting card Apr 17 09:47:18 ravna kernel: wvlan_cs: Initialization failed! Anyone seen this before? Got any clues as to what is going on?

Sad: Lucent WaveLAN/IEEE fails with updated firmware Date: 2000, Apr 18 From: Michael Vasilenko acid

I have two Lucent WaveLAN/IEEE Turbo 11Mb cards. Recently I've updated firmware on one of it from v4.52 to v6.04 And for now, pcmcia-cs's wvlan_cs driver unable to startup it: wavelan2_cs driver has problems too (on both cards) - see thread 16 (not sure about number) kernel: Linux PCMCIA Card Services 3.1.14 kernel: kernel build: 2.2.14 #1 Tue Apr 18 10:11:28 EEST 2000 kernel: options: [pci] [cardbus] kernel: PCI routing table version 1.0 at 0xfdf10 kernel: Intel PCIC probe: kernel: TI 1225 rev 01 PCI-to-CardBus at slot 00:10, mem 0xea000000 kernel: host opts [0]: [pci only] [pci irq 10] [lat 64/176] [bus 188/0] kernel: host opts [1]: [pci only] [pci irq 10] [lat 64/176] [bus 192/0] kernel: PCI card interrupts, PCI status changes cardmgr[757]: starting, version is 3.1.14 cardmgr[757]: watching 2 sockets kernel: cs: IO port probe 0x1000-0x17ff: clean. kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x290-0x297 0x4d0-0x4d7 kernel: cs: IO port probe 0x0a00-0x0aff: clean. cardmgr[757]: initializing socket 0 kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. cardmgr[757]: socket 0: Lucent Technologies WaveLAN/IEEE Adapter cardmgr[757]: executing: 'insmod /lib/modules/2.2.14/pcmcia/wvlan_cs.o port_type kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4 kernel: wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de> kernel: wvlan_cs: index 0x01: Vcc 5.0, irq 10, io 0x0100-0x013f kernel: wvlan_cs: Registered netdevice wvlan0 kernel: wvlan_cs: Initialization failed! cardmgr[757]: executing: './network start wvlan0'

1. Idea: Possible fix by Atanu Ghosh, 2000, Apr 21 2. Feedback: Lucent wavelan2_cs driver works by Charlie Price, 2000, Apr 27

Question: Changing mode of Lucent WaveLAN/IEEE card? Date: 2000, Apr 20 From: PinkFreud

I noticed that iwconfig has the ability to change a wireless card's mode, with valid options (apparently) being Auto, Ad-hoc, Managed, Master, Repeater, and Secondary. However, with my WaveLAN/IEEE card, pcmcia utils 3.1.14, and wireless extensions 20, I get an 'SIOCSIWMODE: Invalid argument' whenever I try to use any of these modes, other than ad-hoc or managed. Any ideas as to why?

1. News: Wireless Extensions is more than Wavelan or 802.11 by Jean Tourrilhes, 2000, Apr 24 (_ Question: port_type: 3 choices by Guillaum Dallaire, 2000, Apr 25

Question: Wavelan IEEE, Sony Vaio N505 VE, and suspend/resume Date: 2000, Apr 24 From: Jürgen Botz jbotz

On my Sony VAIO N505 VE the wavelan card (with either the wvlan_cs or the wavelan2_cs drivers) works after initial system boot, but not after a suspend/resume. That is, either with the card in the slot when the suspend resume happens OR if inserting the card after the machine has gone through a suspend/resume cycle! For every packet I attempt to send it gives a message about "TX timeout" and the IRQ counter in /proc/interrupts does not increase. No packets get through. My regular ethernet card (3Com 3c589C) sort of works, but after suspend/resume there are messages (in dmesg) about dropped interrupts on eth0. However, it does seem to get all (most?) packets through. This is with either kernel 2.2.14 or 2.3.99-pre5. Clearly there's something funky with interrupts on the PC card slot after suspend/resume on the VAIO. Anyone have any ideas? - Jürgen

1. Yes, there is something funky with interrupts by David Hinds, 2000, Apr 24

Question: cs: socket 0 timed out during reset Date: 2000, Apr 25 From: Peter Kropf peterk

I had a WaveLAN IEEE Gold card working in my Linux server and routing from the wireless lan through the ethernet card out to the Internet. (Surfing from the back porch is very cool...) However, something seems to have gone wrong. When I came home yesterday, the server was hung. So I rebooted. Now I'm receiving timed out during reset messages whenever the pcmcia service is started. I traced it to the insertion of the WaveLAN card into the PCMCIA-ISA adapter but haven't been able to get much further. Any help would be great! Thanks! Apr 25 10:44:49 wacko kernel: Linux PCMCIA Card Services 3.1.14 Apr 25 10:44:49 wacko kernel: kernel build: 2.2.15-2.5.0 #3 SMP Wed Apr 12 22:30:30 PDT 2000 Apr 25 10:44:49 wacko kernel: options: [pci] [cardbus] [apm] Apr 25 10:44:49 wacko kernel: Intel PCIC probe: Apr 25 10:44:49 wacko kernel: Vadem VG-469 rev 00 ISA-to-PCMCIA at port 0x3e2 ofs 0x00 Apr 25 10:44:49 wacko kernel: host opts [0]: none Apr 25 10:44:49 wacko kernel: host opts [1]: none Apr 25 10:44:49 wacko kernel: ISA irqs (scanned) = 5 polling interval = 1000 ms Apr 25 10:44:49 wacko cardmgr[1652]: starting, version is 3.1.14 Apr 25 10:44:49 wacko cardmgr[1652]: watching 2 sockets Apr 25 10:44:49 wacko kernel: cs: IO port probe 0x1000-0x17ff: clean. Apr 25 10:44:49 wacko kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x240-0x24f 0x290-0x297 0x300-0x307 0x388-0x38f 0x4d0-0x4d7 Apr 25 10:44:49 wacko kernel: cs: IO port probe 0x0a00-0x0aff: clean. Apr 25 10:44:52 wacko kernel: cs: socket 0 timed out during reset

1. Hmmm, maybe a hardware failure? by David Hinds, 2000, Apr 25 (_ Agree: Looks that way by Peter Kropf, 2000, Apr 25

Sad: Hardware address not showing-up with WaveLAN Turbo Date: 2000, Apr 26 From: oscar Rodriguez dell_7000

Hi, I have a Dell Inspirion 7000 running RH 6.1 (kernel 2.2.12-20) with a fresh install of pcmcia-cs-3.1.14. When I insert a WaveLAN card, it beeps, and wvlan0 shows up in ifconfig, but the hardware address is 00:00:00:00:00:00 instead of something useful and it doesn't work. /var/log/messages shows: kernel: wvlan_cs: wvlan0 Tx timed out! resetting card kernel: wvlan_cs: Initialization failed! This card (and others) work fine in a Sony laptop. Where should we look? Thanks, Mangk

1. Same problem No Mac address by Robert Jackson, 2000, Apr 26 1. Question: Was this solved? I've got something similar... by Bob Cook, 2000, Jul 28 2. Try the other Wavelan-IEEE driver, for comparison by David Hinds, 2000, Apr 26 1. Sad: I tried the wavelan2_cs driver by oscar Rodriguez, 2000, Apr 27

Question: machine hang while changing freq with iwconfig Date: 2000, Apr 27 From: Jonathan Chan jchan

Dear all, When I try to change the freq of my WaveLAN IEEE card using iwconfig, the linux laptop is frozen, and nothing is logged in the /var/log/messages file. This is the details of my machine: - toshiba portege 300CT - redhat 6.2 - linux 2.2.14 - pcmcia-cs 3.1.13 - wireless_tools 20 Now if I use a old WaveLAN card (wavelan_cs driver) instead of the WaveLAN IEEE card (wvlan_cs driver), iwconfig can change its freq without any troubles... Problem in the wvlan_cs driver?? Not quite. If I go into the /etc/pcmcia/config.opts and change the freq option there, I can obtain whatever freq I want after a reboot... Problem in the wireless_tools?? Not quite... I have a basestation running "exactly" the same software (redhat, linux, pcmcia_cs and wireless_tools) except the WaveLAN IEEE card being slotted into a pcmcia-isa adaptor, and the iwconfig program works fine for everthing!! It would be appreciate so much if someone can tell me how to approach this strange problem... Thanks for your time... Cheers, Jonathan

1. Note: machine hang if changing any wvlan config with iwconfig by Jonathan Chan, 2000, Apr 28 (_ Note: problem solved by using wavelan2_cs driver by Jonathan Chan, 2000, May 08

Sad: Compaq WL200 Wireless PCI Card not supported? Date: 2000, May 05 From: Patrick Neill Patrick

The Compaq WL200 Wireless PCI Card runs with the PrismII chipset and might therefore work with the drivers available from www.aboval.com The PCI card contains a CirrusLogic PD6729 chipset that interfaces the actual wireless interface to the PCI Bus. I tried to install it with Redhat 6.2 straight from the box and also with SUSE Linux 6.4 updated with the latest 3.1.14 PCMCIA drivers. Whatever configuration options I tried, LINUX would always freeze trying to start PCMCIA. Has anyone got past this stage and been successful in installing this card.

1. News: Please check in the Howto... by Jean Tourrilhes, 2000, May 05 2. Idea: found working PCMCIA parameters, now facing driver installation by Patrick Neill, 2000, May 09

Sad: Problem with Lucent PCI-PCMCIA-adapter Date: 2000, May 09 From: Tommy Svensson tommy23

I have much problem to get my Lucnet PCI-PCMCIA Adapter to work under Linux. I have read articel on this maillinglistor which address this issue, but it didn't help. I have upgrade to the latest version of both Linux kernel 2.2.15 and PCMCIA utils (have test both with the beta in 3.1.15 and the realse 3.1.14). I have test with both Lucent Wavelan driver (version 6.00 and 6.01BETA) and also the Andy GPL driver, but nothing work. It find the PCI-PCMCIA adapter it find the wavelan card and load the right driver but the driver complain about missing resources etc. How do I fix this problem or should I use other PCMCIA adapters, which is no problem for ous to buy new. But we running homemaid software for remote-monitoring of weather-equiment. Please help me! //Tommy

1. Need a specific, detailed description of your problem by David Hinds, 2000, May 09

Question: ELAN PCI/PCMCIA Adapter and Samsung Wireless Card Date: 2000, May 10 From: Gary Spivey DrTerp

I have been trying for quite a long time (and with frequent e-mails to the linux-wlan group) to get my system up and running in linux. I have a Samsung wireless card (MagicWave SWL-1000). Supplied with this card is a PCI/PCMCIA adapter (also from Samsung). After much travail I was led to believe that the adapter would not support the interrupt mechanisms require. I was also told that there was a card from a company called ELAN (the P111) that does work with the latest pcmcia packages. So, I ordered the card, but alas,it is worse. Got it installed, (took a little bit to get it working under windows - had to rearrange my cards in my PCI slots). But, it doesn't work at all in Linux. It thinks the card is a memory card. The pcmcia package doesn't respond to the different probes. I tried the probe utility in the pcmcia package directly, but nada. Nothing found. To me, this appears to be a bad sign. I thought it might be something in the setup until I plugged in the Samsung card and it got as close as it had been in the past. Card detected, everything works, except that it doesn't handle the interrupts properly (and I have the irq_mode=1 set in the /etc/sysconfig/pcmcia). By saying everything works, what I mean is that I get both high beeps, all of the modules are loaded, I just never see the interrupts increment and the ethernet doesn't function. Any Ideas? I attached the messages file for both adapters pcmcia sections ... Cheers, Gary spivey@ieee.org The following is from the SAMSUNG PCI/PCMCIA Adapter May 4 22:58:28 achilles pcmcia: cardmgr. May 4 22:58:29 achilles rc: Starting pcmcia succeeded May 4 22:58:29 achilles cardmgr[307]: starting, version is 3.1.14 May 4 22:58:29 achilles keytable: Loading keymap: May 4 22:58:29 achilles cardmgr[307]: watching 2 sockets May 4 22:58:29 achilles kernel: cs: IO port probe 0x0240-0x04ff: excluding 0x388-0x38f May 4 22:58:29 achilles kernel: cs: IO port probe 0x0a00-0x0aff: clean. May 4 22:58:29 achilles cardmgr[307]: initializing socket 1 May 4 22:58:29 achilles kernel: cs: memory probe 0x0d0000-0x0dffff: clean. May 4 22:58:29 achilles cardmgr[307]: socket 1: Samsung MagicWave May 4 22:58:29 achilles cardmgr[307]: executing: 'insmod /lib/modules/2.2.14-15mdk/pcmcia/am930_cs.o' May 4 22:58:29 achilles keytable: Loading /usr/lib/kbd/keymaps/i386/qwerty/us.kmap.gz May 4 22:58:29 achilles kernel: Linux WLAN 0.3.4 May 4 22:58:29 achilles kernel: am930: io=0x240 irq=9 May 4 22:58:29 achilles kernel: am930: Firmware Banner: PCnetMobile:v2.01 101498 API005 May 4 22:58:29 achilles kernel: f/w version:2.01 date:101498 api:5 May 4 22:58:29 achilles kernel: am930hw_construct: Reset and f/w TestInterface are successful May 4 22:58:29 achilles kernel: am930hw_init_tx_queues: Allocated 5 tx slots May 4 22:58:29 achilles kernel: am930llc_construct: Device eth0 registered May 4 22:58:29 achilles cardmgr[307]: executing: './wlan start eth0' May 4 22:58:30 achilles cardmgr[307]: + wlan scanning channels to May 4 22:58:30 achilles kernel: am930mgr_scanbegin: scanning channel 1 May 4 22:58:30 achilles keytable: Loading system font: May 4 22:58:30 achilles rc: Starting keytable succeeded May 4 22:58:30 achilles gpm: gpm startup succeeded May 4 22:58:30 achilles PAM_pwdb[367]: (su) session opened for user xfs by (uid=0) May 4 22:58:31 achilles PAM_pwdb[367]: (su) session closed for user xfs May 4 22:58:31 achilles xfs: xfs startup succeeded May 4 22:58:31 achilles cardmgr[307]: + Detected BSSs: May 4 22:58:31 achilles cardmgr[307]: + ch bssid bcn cap_info ssid May 4 22:58:31 achilles cardmgr[307]: + ------------------------------------------------------ May 4 22:58:31 achilles cardmgr[307]: + May 4 22:58:31 achilles kernel: ethconv=rfc1042 May 4 22:58:31 achilles cardmgr[307]: + wlan failed to find ssid=HOME_BSS May 4 22:58:31 achilles cardmgr[307]: start cmd exited with status 1 The following is from the ELAN P111 PCI/PCMCIA Adapter May 4 23:07:39 achilles pcmcia: Starting PCMCIA services: May 4 23:07:39 achilles pcmcia: modules May 4 23:07:39 achilles kernel: Linux PCMCIA Card Services 3.1.14 May 4 23:07:39 achilles kernel: kernel build: 2.2.14-15mdk #1 Tue Jan 4 22:24:20 CET 2000 May 4 23:07:39 achilles kernel: options: [pci] [cardbus] [apm] [pnp] May 4 23:07:39 achilles kernel: PCI routing table version 1.0 at 0xfdcb0 May 4 23:07:39 achilles kernel: unknown PCI interrupt router 1106:0586 May 4 23:07:39 achilles kernel: PnP: PNP BIOS installation structure at 0xc00fbef0 May 4 23:07:39 achilles kernel: PnP: PNP BIOS version 1.0, entry at f0000:bf18, dseg at f0000 May 4 23:07:39 achilles kernel: Intel PCIC probe: May 4 23:07:39 achilles kernel: Unknown [104c ac50] rev 00 PCI-to-PCMCIA at slot 00:09, port 0x3000 May 4 23:07:39 achilles kernel: host opts [0]: none May 4 23:07:39 achilles kernel: host opts [1]: none May 4 23:07:39 achilles kernel: ISA irqs (default) = 3,9 polling interval = 1000 ms May 4 23:07:39 achilles pcmcia: cardmgr. May 4 23:07:39 achilles rc: Starting pcmcia succeeded May 4 23:07:39 achilles cardmgr[314]: starting, version is 3.1.14 May 4 23:07:39 achilles keytable: Loading keymap: May 4 23:07:39 achilles cardmgr[314]: watching 2 sockets May 4 23:07:39 achilles kernel: cs: IO port probe 0x0240-0x04ff: excluding 0x388-0x38f May 4 23:07:39 achilles kernel: cs: IO port probe 0x0a00-0x0aff: clean. May 4 23:07:40 achilles keytable: Loading /usr/lib/kbd/keymaps/i386/qwerty/us.kmap.gz May 4 23:07:40 achilles cardmgr[314]: initializing socket 0 May 4 23:07:40 achilles kernel: cs: memory probe 0x0d0000-0x0dffff: excluding 0xd0000-0xdffff May 4 23:07:40 achilles kernel: cs: memory probe 0x0c0000-0x0cffff: excluding 0xc0000-0xcffff May 4 23:07:40 achilles cardmgr[314]: socket 0: Anonymous Memory May 4 23:07:40 achilles cardmgr[314]: executing: 'insmod /lib/modules/2.2.14-15mdk/pcmcia/memory_cs.o' May 4 23:07:40 achilles keytable: Loading system font: May 4 23:07:40 achilles kernel: memory_cs: mem0: anonymous: unknown size May 4 23:07:40 achilles cardmgr[314]: executing: './memory start mem0' May 4 23:07:40 achilles rc: Starting keytable succeeded May 4 23:07:41 achilles gpm: gpm startup succeeded May 4 23:07:41 achilles cardmgr[314]: initializing socket 1 May 4 23:07:41 achilles cardmgr[314]: socket 1: Anonymous Memory May 4 23:07:41 achilles cardmgr[314]: executing: './memory start mem1' May 4 23:07:41 achilles kernel: memory_cs: mem1: anonymous: unknown size May 4 23:07:41 achilles PAM_pwdb[381]: (su) session opened for user xfs by (uid=0) May 4 23:07:41 achilles PAM_pwdb[381]: (su) session closed for user xfs May 4 23:07:41 achilles xfs: xfs startup succeeded May 4 23:07:42 achilles xfs: Warning: The directory "/usr/X11R6/lib/X11/fonts/100dpi" does not exist. May 4 23:07:42 achilles xfs: Entry deleted from font path. May 4 23:07:52 achilles PAM_pwdb[424]: (kde) session opened for user root by (uid=0)

Question: Manual control over Wavelan Roaming Date: 2000, May 11 From: Mark Dennehy Sparks

Does anyone know of a reasonable method of convincing an IEEE 802.11 Bronze Wavelan card in Managed mode to select a different Access Point than the closest one ? In other words, a means of directly specifying the Access Point, without going to Ad-Hoc mode (which doesn't work because the Access Point isn't in Ad-Hoc mode and won't talk to the Wavelan card).

Question: PrismII based card, WLAN device not showing up in ifconfig Date: 2000, May 11 From: Patrick Neill Patrick

Hello My configuration is as follows: - Redhat 6.2 - 3.1.8 PCMCIA package - Compaq WL 200 PCI card (the drivers seems to think it is a WL100, the manfid for both cards is the same however) - PrismII drivers from www.absoval.com When the drivers have loaded, ifconfig doesn't show an additional device apart from my already installed NE2000. The output from messages shows some unresolved symbols. Does anyone have any idea what could be preventing the wlan device from showing up in ifconfig? Thanks May 12 00:19:39 hsg7960 pcmcia: Starting PCMCIA services: May 12 00:19:39 hsg7960 pcmcia: modules May 12 00:19:39 hsg7960 kernel: Linux PCMCIA Card Services 3.1.8 May 12 00:19:39 hsg7960 kernel: kernel build: 2.2.14-5.0 #1 Tue Mar 7 20:53:41 EST 2000 May 12 00:19:39 hsg7960 kernel: options: [pci] [cardbus] [apm] [pnp] May 12 00:19:39 hsg7960 kernel: PnP: PNP BIOS installation structure at 0xc00f9560 May 12 00:19:39 hsg7960 kernel: PnP: PNP BIOS version 1.0, entry at f0000:9660, dseg at 400 May 12 00:19:39 hsg7960 kernel: Intel PCIC probe: May 12 00:19:39 hsg7960 kernel: Cirrus PD6729 PCI-to-PCMCIA at bus 0 slot 15, port 0xfff4, 2 sockets May 12 00:19:39 hsg7960 kernel: host opts [0]: [ring] [1/5/0] [1/20/0] May 12 00:19:39 hsg7960 kernel: host opts [1]: [ring] [1/5/0] [1/20/0] May 12 00:19:40 hsg7960 kernel: ISA irqs (default) = 5,10,11 polling interval = 1000 ms May 12 00:19:40 hsg7960 pcmcia: cardmgr. May 12 00:19:40 hsg7960 cardmgr[480]: starting, version is 3.1.8 May 12 00:19:40 hsg7960 rc: Starting pcmcia succeeded May 12 00:19:40 hsg7960 cardmgr[480]: watching 2 sockets May 12 00:19:40 hsg7960 kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x470-0x477 May 12 00:19:40 hsg7960 cardmgr[480]: initializing socket 0 May 12 00:19:40 hsg7960 kernel: cs: memory probe 0x0d0000-0x0dffff: clean. May 12 00:19:40 hsg7960 cardmgr[480]: socket 0: Compaq WL100 11Mb/s WLAN Card May 12 00:19:40 hsg7960 lpd: lpd startup succeeded May 12 00:19:40 hsg7960 lpd[494]: restarted May 12 00:19:40 hsg7960 cardmgr[480]: executing: 'insmod /lib/modules/2.2.14-5.0/pcmcia/prism2_cs.o' May 12 00:19:40 hsg7960 cardmgr[480]: + /lib/modules/2.2.14-5.0/pcmcia/prism2_cs.o: unresolved symbol p80211pb_alloc_p80211 May 12 00:19:40 hsg7960 cardmgr[480]: + /lib/modules/2.2.14-5.0/pcmcia/prism2_cs.o: unresolved symbol p80211pb_free May 12 00:19:40 hsg7960 cardmgr[480]: + /lib/modules/2.2.14-5.0/pcmcia/prism2_cs.o: unresolved symbol register_wlandev May 12 00:19:40 hsg7960 cardmgr[480]: + /lib/modules/2.2.14-5.0/pcmcia/prism2_cs.o: unresolved symbol p80211netdev_rx May 12 00:19:40 hsg7960 cardmgr[480]: + /lib/modules/2.2.14-5.0/pcmcia/prism2_cs.o: unresolved symbol unregister_wlandev May 12 00:19:40 hsg7960 cardmgr[480]: + /lib/modules/2.2.14-5.0/pcmcia/prism2_cs.o: unresolved symbol wlan_setup May 12 00:19:40 hsg7960 cardmgr[480]: + /lib/modules/2.2.14-5.0/pcmcia/prism2_cs.o: unresolved symbol p80211ind_sniff May 12 00:19:40 hsg7960 cardmgr[480]: + /lib/modules/2.2.14-5.0/pcmcia/prism2_cs.o: unresolved symbol wlan_unsetup May 12 00:19:40 hsg7960 cardmgr[480]: insmod exited with status 1 May 12 00:19:40 hsg7960 cardmgr[480]: executing: 'modprobe prism2_cs'

1. Well, if the module can't be loaded, that would do it by David Hinds, 2000, May 15 2. Question: Compaq WL100 WLAN Card by Talei McLeod, 2000, Aug 11 3. Sad: Also greiving with a Compaq WL200, Has any one made one work?? by harry campigli, 2000, Aug 22

Question: System works for a while, then stops Date: 2000, May 13 From: Gary Spivey DrTerp

Now that I have this wireless lan card and pci adapter working, I have another issue. Occasionally, it simply quits working. If I do a pcmcia stop/start followed by a network start. Everything is fine. This could however pose a problem if I have ssh working or somesuch. In windows, there is a monitor for the driver. Occasionally I will lose the connection to the station, and it will detect this and cycle through until it reconnects. Is my problem here simply an issue of the driver not reconnecting? Is this a pcmcia or a wlan issue? ... it just happened again as I was attempting to preview the message. The card is still getting interrupts when I cat /proc/interrupts, but the network just goes down. Cheers, Gary spivey@rincon.com

Question: network level failure with MELCO 11Mb card Date: 2000, May 14 From: Jonathon Fletcher jonathon

[text-mangling by the input box on the web-page] I have two Melco WLI-PCM-L11 cards, which are (I believe) clones of the WaveLAN cards for the Japanese market. I am trying to get them working as peers in an Ad-Hoc network. I have the cards and the pcmcia interaction okay - inserting the card brings up the interface and the wireless extensions look okay. I just cannot seem to get the cards to 'hear' each other. My two hosts are 'A' and 'B'. In each machine, the Melco card is setup as eth1. Both machines are redhat 6.2 installs, with the 3.1.13 pcmcia bundle on top (1.0.4 wavelan gpl driver). The /etc/pcmcia/config.opts line for the wvlan_cs driver is something like: module "wvlan_cs" opts "eth=1 port_type=3 network_name=01020304050607 channel=14" (station name only is different). All other settings are the default. rate is set to auto. a# ifconfig eth1 ; iwconfig eth1 eth1 Link encap:Ethernet HWaddr 00:60:1D:AA:AA:AA inet addr:10.10.10.1 Bcast:10.10.10.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1 errors:0 dropped:0 overruns:0 frame:0 TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:10 Base address:0x100 eth1 IEEE 802.11-DS ESSID:"01020304050607" Nickname:"A" Frequency:2.484GHz Sensitivity:1/3 Mode:Ad-Hoc Access Point: 00:00:00:00:00:00 Bit Rate:2Mb/s RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 invalid crypt:0 invalid misc:0 b# ifconfig eth1 ; iwconfig eth1 eth1 Link encap:Ethernet HWaddr 00:60:1D:BB:BB:BB inet addr:10.10.10.2 Bcast:10.10.10.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:3 Base address:0x100 eth1 IEEE 802.11-DS ESSID:"01020304050607" Nickname:"B" Frequency:2.484GHz Sensitivity:1/3 Mode:Ad-Hoc Access Point: 00:00:00:00:00:00 Bit Rate:2Mb/s RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 invalid crypt:0 invalid misc:0 In both 'A' and 'B' the cards seem okay, the power light is on, and the interface is up. When I try to ping out of one interface to the other there is a blinking on the data led of the sender. When I tcpdump the interface I do see the arp requests going out. The problem is that although I appear to be able to send I cannot receive any data on the other card. The link/signal/noise readings all sit at zero. The cards appear to be deaf. Is there something obvious that I can try to make the connection work ? I must be missing something simple, but I cannot work out what. Thanks, Jonathon

Question: Elsa AirLancer MC-2 Date: 2000, May 15 From: Peter Zimmer pzimmer

does somebody knows if the airlancer-mc2 card from elsa is working with linux ?? do i have to use the wavelan-driver for this ?? thanks

Sad: Welp having 2 ISA cards and 2 Wavelan Cards in one Linux box Don't Work! Date: 2000, May 17 From: John Savage admin

I have tried and read till blue in the Eyes and there seems to be a severe issue on runing 2 ISA slot cards with 2 Wavelan Turbo cards inserted, When together they switch slots that activate and only one card will configure even tho is shows in the var state that there is two slots: linux-2.2.14]# pcmciastat Socket 0: Lucent Technologies WaveLAN/IEEE Adapter 0 network wvlan_cs 0 wvlan0 Socket 1: empty How Do I get the second slot to configure wvlan1 as the card is in the slot but will not be recognized or configure properly. Thanks and God Bless JohnS admin@tri-net.org

1. I don't think this driver supports multiple cards by David Hinds, 2000, May 17 (_ More: I think it's right... by Jean Tourrilhes, 2000, May 17 (_ Question: Ok next question then how do you switch from the module .... by John Savage, 2000, May 17

Question: Pci adaptor + wavelan pc card on Dell 2400 : unknown PCI interrupt router Date: 2000, May 18 From: Blitter

Hi, we want to install a pci adaptor card and wavelan turbo card on a Dell 2400 server. The adaptor uses the T1225 chip. We are getting following complaints in /var/log/messages : May 18 12:51:56 callisto pcmcia: Starting PCMCIA services: May 18 12:51:56 callisto pcmcia: modules May 18 12:51:56 callisto kernel: Linux PCMCIA Card Services 3.1.14 May 18 12:51:56 callisto kernel: kernel build: 2.2.13-0.13smp #1 SMP Tue Jan 11 13:26:01 EST 2000 May 18 12:51:56 callisto kernel: options: [pci] May 18 12:51:56 callisto kernel: PCI routing table version 1.0 at 0xfc330 May 18 12:51:56 callisto kernel: unknown PCI interrupt router 1166:0200 May 18 12:51:56 callisto kernel: Intel PCIC probe: not found. May 18 12:51:56 callisto kernel: ds: no socket drivers loaded! May 18 12:51:56 callisto pcmcia: /lib/modules/2.2.13-0.13smp/pcmcia/i82365.o: init_module: Device or resource busy May 18 12:51:56 callisto cardmgr[488]: starting, version is 3.1.14 May 18 12:51:56 callisto pcmcia: cardmgr. May 18 12:51:56 callisto pcmcia: /lib/modules/2.2.13-0.13smp/pcmcia/ds.o: init_module: Device or resource busy May 18 12:51:56 callisto cardmgr[488]: no pcmcia driver in /proc/devices May 18 12:51:56 callisto cardmgr[488]: exiting Uses the motherboard of this server a proprietary pci interrupt router ? I looked in the code a bit and found that only intel, one via and some ali pci irq routers are supported. lspci gives following output : [root@callisto modules]# /sbin/lspci 00:00.0 Host bridge: Pequr Technology: Unknown device 0009 (rev 05) 00:00.1 Host bridge: Pequr Technology: Unknown device 0009 (rev 05) 00:02.0 PCI bridge: Intel Corporation: Unknown device 0962 (rev 01) 00:08.0 Ethernet controller: Intel Corporation 82557 (rev 08) 00:0e.0 VGA compatible controller: ATI Technologies Inc: Unknown device 4759 (rev 7a) 00:0f.0 ISA bridge: Pequr Technology: Unknown device 0200 (rev 4f) 01:04.0 SCSI storage controller: Adaptec 7890 (rev 01) 01:06.0 SCSI storage controller: Adaptec AIC-7880U (rev 01) 02:06.0 SCSI storage controller: Adaptec 2940U2 02:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 8139 (rev 10) [root@callisto modules]# Any suggestions ? Can I add myself some code to do the init and links in the pci_fixup.c file to this Pequr thing ? Or could I cheat and change the codes to for example and intel thing (perhaps they are compatible ?) Or am I missing the point completely here ? Greetings !

1. The CardBus bridge seems to be invisible by David Hinds, 2000, May 18

Question: ThinkPad 600 and Wavelan card Date: 2000, May 18 From: Jonathon Fletcher jonathon

Does anyone have any experience making a wavelan card work in an IBM ThinkPad 600. I have things to the point of being able to receive data (I get arp request from the other side when I use tcpdump on the ThinkPad) - but it will not send. I suspect this is just an irq/port problem - any suggestions what settings I should be using in /etc/pcmcia/config.opts ? Jonathon

1. That doesn't sound like a resource issue by David Hinds, 2000, May 18 (_ Asus P3B-F and Ricoh RL5C475 - mixed irq ? by Jonathon Fletcher, 2000, May 19 (_ Several PCI issues here by David Hinds, 2000, May 19 (_ Re: Several PCI issues here by Jonathon Fletcher, 2000, May 19 (_ Hmmm, I might be wrong about the wvlan_cs driver by David Hinds, 2000, May 19

Question: WebGear/RayLink card installs/ifconfig but no ping Date: 2000, May 26 From: Kelly Murray kem

I've got a WebGear Aviator 2.4 in a ISA bridge. It works fine under Windows 95. I compiled and installed the pcmcia-cs-3.1.14 stuff. It recognizes the card, and I can ifconfig eth0, but no traffic occurs. I turned on debugging, and recompiled the ray_cs module, and it seems to transmit, but never gets a reply. Looking at the source code of ray_cs, I don't see any debug messages saying the card attached or started on a network. I'm thinking I need to do something more than ifconfig to get it setup correctly. Any help appreciated! Is there a mailing list specifically for this hardware? thanks, kelly murray

1. I had same problem, but it's working now (sort of) by Greg Mohr, 2000, May 27

Ok: Debugging not compiled into ray_cs module (CS 3.1.15). Fixed Date: 2000, May 28 From: Cathelijne Hornstra lijn

After compiling and installing the latest (3.1.15) pcmcia-cs, I found in my /var/log/messages that cardmgr couldn't load the ray_cs module: cardmgr[3112]: executing: 'modprobe ray_cs pc_debug=0 essid=DUSART hop_dwell=128 beacon_period=256 translate=0' cardmgr[3112]: + /lib/modules/2.2.14-12/pcmcia/ray_cs.o: invalid parameter parm_pc_debug cardmgr[3112]: + /lib/modules/2.2.14-12/pcmcia/ray_cs.o: insmod /lib/modules/2.2.14-12/pcmcia/ray_cs.o failed cardmgr[3112]: + /lib/modules/2.2.14-12/pcmcia/ray_cs.o: insmod ray_cs failed cardmgr[3112]: modprobe exited with status 255 Seemed that debugging wasn't compiled in :-( Not bothered by any knowledge of programming at all, I had a look at the code and found the following lines in pcmcia-cs-3.1.15/wireless/ray_cs.c: #ifdef RAYLINK_DEBUG #define PCMCIA_DEBUG RAYLINK_DEBUG #endif Done some grepping, but didn't find this defined anywhere, so no surprise it doesn't get compiled in. I then had a look at Corey's sources (version 1.70) and found that he uses a line like this in his ray_cs.mk file: all: $(MAKE) -C modules MODULES=ray_cs.o CFLAGS="-O2 -Wall -Wstrict-prototypes -Winline -pipe -DRAYLINK_DEBUG=0" So I ended up changing 3.1.15/wireless/Makefile: CPPFLAGS += $(PCDEBUG) -D__KERNEL__ -DMODULE became: CPPFLAGS += $(PCDEBUG) -D__KERNEL__ -DMODULE -DRAYLINK_DEBUG=0 and all worked fine after that. Regards, Cathelijne Hornstra

1. It is a bug in the suggested ray_cs options by David Hinds, 2000, May 30 (_ I tried that, but it didn't work by Cathelijne Hornstra, 2000, May 31 (_ You might want to try it again by David Hinds, 2000, May 31

Question: WaveLan IEEE, cardmgr do not know wvlan0 interface Date: 2000, May 30 From: viktor safar 4roses

Hi, My config is: Linux kernel 2.0.36 ISA-to-PCMCIA card: Vadem VD 469 Network card: Lucent WaveLan IEEE Turbo silver PCMCIA driver: 3.1.15 (from Andreas Neuhaus} Symptoms: Cardservices finds sokets in ISA card. OK Cardservices locates WaveLan card in soket 1. OK There is no irq, i/o or memory failures. OK Device driver register WaveLan wvlan0 interface. OK Cardmgr trying to start network. OK And now! Cardmanager did not recognize interface "wvlan0" !!! Here is the dmesg story: Linux PCMCIA Card Services 3.1.15 kernel build: 2.0.36 #2 Tue May 30 14:10:29 2000 options: [pci] PCI routing table version 1.0 at 0xf85c0 00:07.2 -> irq 10 Intel PCIC probe: Vadem VG-469 rev 00 ISA-to-PCMCIA at port 0x3e0 ofs 0x00 host opts [0]: [ext mode] [isa buf] host opts [1]: [ext mode] [isa buf] ISA irqs (scanned) = 3,4,5,7,11,15 status change on irq 15 cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff cs: IO port probe 0x0800-0x08ff: clean. cs: IO port probe 0x0100-0x04ff: excluding 0x4d0-0x4d7 cs: IO port probe 0x0a00-0x0aff: clean. cs: memory probe 0x0d0000-0x0dffff: excluding 0xd0000-0xdffff cs: memory probe 0x0c0000-0x0cffff: excluding 0xc0000-0xcffff wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4 wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de> wvlan_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f wvlan_cs: Registered netdevice wvlan0 wvlan_cs: Valid channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 wvlan_cs: MAC address on wvlan0 is 00 60 1d 04 05 93 cardmgr[47]: executing: './network start wvlan0' cardmgr[47]: + wvlan0: unknown interface. ***************************************** Note: The network card works with old driver (wavelan_cs2.o) fine, because it fires up "eth1" instead "wvlan0". Is there anybody with some suggestions, how to say to linux that wvlan0 is a valid interface? thanx, viktor safar viktor@salamon.sk

1. Maybe your setup can't handle unusual interface names by David Hinds, 2000, May 30 2. WaveLan IEEE, cardmgr do not know wvlan0 interface 2 by viktor safar, 2000, May 31 1. Whoops, my mistake... by David Hinds, 2000, May 31

Question: NFS over Wavelan Date: 2000, May 31 From: Rui-Tao Dong rdong

I am using a pair of Wavelan silver cards between 2 UDBs and quite happy with the performance. I routinely get about 5Mb/s on ftp transfers. (RH 6.1 + 2.2.14 + cs 3.13). However, I have a hard time with NFS over the link. The mount will hang for minutes when I access mounted fs and I get a lot kernel: nfs: task xxxxx can't get a request slot in the log file.

1. Idea: UDP over Wireless == not that great by Jean Tourrilhes, 2000, May 31 2. You might try playing with the MTU for the interface by David Hinds, 2000, May 31 1. More: Slow but no hanging by Rui-Tao Dong, 2000, Jun 01

Question: WaveLan PCI adapter wierdness Date: 2000, Jun 01 From: Neil Radisch nradisch

I only get errors and transmit timeouts, thought the card is active and seems to be configured correctly. The only thing that seems strange is lspci -vv says that the card has "pin A routed to IRQ 0". that can't be right, can it? Neil

1. More info would help... but... by David Hinds, 2000, Jun 01 1. More: Did that, didn't help by Neil Radisch, 2000, Jun 01 2. More: more info dump_pirq by Neil Radisch, 2000, Jun 01 3. Ok: Problem solved by Neil Radisch, 2000, Jun 01

Question: Wavelan IEEE problems... Date: 2000, Jun 02 From: Avijit Banerjee avi

Hello there, I have two Wavelan IEEE silver cards. One is on my PC with the ISA-to-PCMCIA adapter. The other is on an older laptop (pentium 100). I'm using ad-hoc mode. I have two problems. One has to do with the wavelan2_cs driver from lucent. It misreports the link quality stats. I can bring up interfaces, ping the other computer, etc. But those link quality stats is what I'm after. Doing a 'cat /proc/net/wireless' gives me the following: Inter-|sta| Quality | Discarded packets face |tus|link level noise| nwid crypt misc eth1 00 0. 154. 154. 0 0 0 (or eth0 in the case of the laptop). The second problem has to do with the wvlan_cs driver, I can install the module, but can't bring up any interface using ifconfig. Neither 'eth1' (or eth0) nor 'wvlan0' are recognized. I keep getting the following message (when I specify a IP address): SIOCSIFADDR: No such device eth1: unknown interface: No such device (or wvlan0 in place of eth1) OTOH, when I just try to bring the interface up without specifying the IP address, I get: eth1: unknown interface: No such device actually, any action with the iwconfig program comes back with a SIOCSXXXXXX: No such device I'm using kernel 2.2.13, pcmcia-cs 3.1.15, wireless extensions 19, and the slackware 7.0 distribution. The lucent driver I'm using is 6.00 (with HCF 4.6). Firmware on cards is 4.52. Any help would be greatly appreciated... Thanx Avijit

1. Sad: wvlan_cs vs wavelan2_cs by Jean Tourrilhes, 2000, Jun 02 (_ Feedback: Here's more info... by Avijit Banerjee, 2000, Jun 02 (_ You should not insmod the driver by hand by David Hinds, 2000, Jun 02 (_ Ok: Problem Solved! by Avijit Banerjee, 2000, Jun 02

Sad: Yet more fun with that PCI -> Orinoco Card Date: 2000, Jun 07 From: Alan Knowles alan_k

Having spent most of the afternoon trying to get it to work, Here is my current situation (with experiences!). Any helpfull hints etc would be appreciated :) Basic Plan: 1 toshiba protable with the lucent card, - this seems to be working OK with the wvlan_cs module - eg. no error messages seem to be comming out of dmesg or /var/log/syslog. - its a debian install with kernel 2.2.15 (from deb package) and pcmcia 3.1.15 (from source) , seems to be quite easy - relative to the next machine! 1 ibm netfinity using the PCI -> PCMCIA adapter. I did try this adapter at home, however it appeared not to be picked up by the bioses on 2 machines - probably needs musical chairs played with the slots.. After doing alot of experimenting - and rereading this list a number of times. I have tried wvlan driver - got pretty much the same messages as mentioned before on this list - It seems to install but I get timeout errors on the system. wavelan2_cs driver (6BETA)- binary from sourceforge contrib - following one of the later posts on this list.. the basic 3 points wher for this combination - only the 6BETA and PCIC_OPTS="irq_mode=0" in /etc/init.d/pcmcia (I havent bothered with /etc/pcmcia.conf (typical debian) the pretty much module "wavelan2_cs" opts "port_type=3" in /etc/pcmcia/config.opts now WITHOUT the irq_mode=0 Intel PCIC probe: TI 1225 rev 01 PCI-to-CardBus at slot 00:12, mem 0xefef7000 host opts [0]: [isa irq] [no pci irq] [lat 168/176] [bus 32/34] host opts [1]: [isa irq] [no pci irq] [lat 168/176] [bus 35/37] ISA irqs (default) = 5 polling interval = 1000 ms cs: IO port probe 0x0c00-0x0cff: clean. cs: IO port probe 0x0800-0x08ff: clean. cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x388-0x38f cs: IO port probe 0x0a00-0x0aff: clean. cs: memory probe 0xa0000000-0xa0ffffff: clean. eth1: WaveLAN/IEEE, io_addr 0x100, irq 5, mac_address 00:60:1D:F2:38:11 eth1: Transmit timeout. eth1: Transmit timeout. eth1: Transmit timeout...... AND SO ON! Now WITH the irq_mode=0 Intel PCIC probe: TI 1225 rev 01 PCI-to-CardBus at slot 00:12, mem 0xefef7000 host opts [0]: [pci only] [no pci irq] [lat 168/176] [bus 32/34] host opts [1]: [pci only] [no pci irq] [lat 168/176] [bus 35/37] *NO* card interrupts, polling interval = 1000 ms cs: IO port probe 0x0c00-0x0cff: clean. cs: IO port probe 0x0800-0x08ff: clean. cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x388-0x38f cs: IO port probe 0x0a00-0x0aff: clean. cs: memory probe 0xa0000000-0xa0ffffff: clean. wavelan2_cs: RequestIRQ: Resource in use now WITH PCIC_OPTS="irq_mode=0 ,pci_irq_list=5,5 " same as above except TI 1225 rev 01 PCI-to-CardBus at slot 00:12, mem 0xefef7000 host opts [0]: [pci only] [pci irq 5] [lat 168/176] [bus 32/34] host opts [1]: [pci only] [pci irq 5] [lat 168/176] [bus 35/37] PCI irq 5 test failed *NO* card interrupts, polling interval = 1000 ms even trying irq_masq on the config.opt line for wavelan2_cs make no difference... As you can see, I have definatly had enough of this for one day :( ..

1. [no pci irq] is the problem by David Hinds, 2000, Jun 07 (_ Ok: pcmcia all working by Alan Knowles, 2000, Jun 08

Sad: Problems with 3.1.15 + wavelan2_cs driver Date: 2000, Jun 08 From: Bjorn Knutsson bjorn

Today I upgraded my TP600X to kernel 2.2.16 and while I was at it, I also upgraded från pcmcia-cs 3.1.14 to 3.1.15. Since I'm using a WaveLAN (Silver 11Mbps), I also added the wavelan2_cs driver, like I had in 3.1.14. When I inserted the WaveLAN card, cardctl promptly died, and checking the logs, this is what I found: Jun 8 13:23:17 foobar cardmgr[427]: initializing socket 0 Jun 8 13:23:17 foobar cardmgr[427]: socket 0: Lucent Technologies WaveLAN/IEEE Jun 8 13:23:17 foobar kernel: cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0ffffff Jun 8 13:23:17 foobar kernel: cs: memory probe 0x60000000-0x60ffffff: clean. Jun 8 13:23:17 foobar cardmgr[427]: executing: 'modprobe wavelan2_cs station_name=foobar enable_encryption=y transmit_key_id=1 channel=0 port_type=1 network_name=FOOBAR key_1=\"snafu\"' Jun 8 13:23:17 foobar kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4 Jun 8 13:23:17 foobar kernel: wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de> It seems it tried to load two different drivers. I then configured, compiled and installed from the 3.1.14 sources, and 3.1.14 + wavelan2_cs works fine under 2.2.16. Something must have been introduced in 3.1.15 that either breaks with wavelan2_cs, or with kernel 2.2.16.

1. Fishy modules.conf setup?? by David Hinds, 2000, Jun 08 (_ Disagree: No fish in my conf.modules. by Bjorn Knutsson, 2000, Jun 08 (_ Re: Disagree: No fish in my conf.modules. by David Hinds, 2000, Jun 09 (_ News: Same old problem, new pcmcia_cs-version. by Bjorn Knutsson, 2000, Jul 18 (_ Fixed: a really dumb bug by David Hinds, 2000, Jul 22 (_ Ok: Re: Fixed: a really dumb bug by Bjorn Knutsson, 2000, Jul 22

Question: Wavelan/IEEE and Alpha Linux problem Date: 2000, Jun 09 From: Mikael Kanto mkanto

I've got an Digital Alpha machine running RedHat 6.2. After a little trouble I got the Vadem VG469 ISA card working as it should. When I insert the Wavelan card it find the right card and tries to load the wvlan module. Then it says initilasation failed. The wavelan card gets an irq and also an io adress. It also shows up in ifconfig and gets all ip setting ok. It doesn't seem to find any mac-adress though. Has anyone had any similar problem with the wavelancard. Using the drivers from wavelan's official page is out of the question because it only exists for intel systems :(

1. Probably not a tested configuration by David Hinds, 2000, Jun 09 (_ News: Use PPC patch... by Jean Tourrilhes, 2000, Jun 12 1. Alpha is little endian by David Hinds, 2000, Jun 12 2. Question: Link? by Mikael Kanto, 2000, Jun 13 1. More: Here... by Jean Tourrilhes, 2000, Jun 13

Question: iwconfig hangs machine (ISA/wavelan & SMP, wvlan2_cs) Date: 2000, Jun 10 From: Alan Knowles alan_k

It's a bit difficult to debug, as all the evidence disappears as soon as I run iwconfig to make a modification. anyway heres the machine config, if you have any ideas, let me know (I am currently compiling the pcmcia drivers with the lucent binary) uname -a Linux alanathome 2.2.15 #1 SMP Wed Jun 7 02:49:14 HKT 2000 i686 unknown dmesg cutting Linux PCMCIA Card Services 3.1.15 kernel build: 2.2.15 unknown options: [pci] [cardbus] [pnp] PCI routing table version 1.0 at 0xfdd90 PnP: PNP BIOS installation structure at 0xc00fbe80 PnP: PNP BIOS version 1.0, entry at f0000:bea8, dseg at f0000 Intel PCIC probe: Vadem VG-469 rev 00 ISA-to-PCMCIA at port 0x3e0 ofs 0x00 host opts [0]: none host opts [1]: none ISA irqs (default) = 5,9 polling interval = 1000 ms cs: IO port probe 0x1000-0x17ff: excluding 0x1220-0x122f 0x1330-0x1337 0x1388-0x138f 0x1620-0x162f 0x1730-0x1737 0x1788-0x178f cs: IO port probe 0x0100-0x04ff: excluding 0x388-0x38f cs: IO port probe 0x0a00-0x0aff: excluding 0xa28-0xa2f cs: memory probe 0x0d0000-0x0dffff: clean.

1. Feedback: binary driver works in this config by Alan Knowles, 2000, Jun 11

Question: Downgrading Wavelan IEEE firmware Date: 2000, Jun 12 From: Mikael Kanto mkanto

Has anyone tried downgrading the software in the Wavelan IEEE card? After what I've read it should work with the wvlan_cs driver.

Question: Wavelan 11 Mb/s Problem Date: 2000, Jun 15 From: Randy Broman rbroman

Attempting to install Wavelan 11 Mb/s PCMCIA card(s) in "non-laptop" using Wavelan PCI adapter. RedHat system with 2.2.14 kernel. Using Wavelan 6.00 driver from their site, and PCMCIA 3.1.16. System logs below .... to me it looks like PCMCIA services comes up OK .... but when the card is inserted the system freezes. On insertion card emits one high beep, on removal a high and a low. Ideas appreciated, Randy Following an /etc/rc.d/init.d/pcmcia start Jun 12 18:05:00 jboat kernel: Linux PCMCIA Card Services 3.1.16 Jun 12 18:05:00 jboat kernel: kernel build: 2.2.14-12test8 #5 Sun Jun 11 06:11:38 EDT 2000 Jun 12 18:05:00 jboat kernel: options: [pci] [cardbus] [apm] [pnp] Jun 12 18:05:00 jboat kernel: PCI routing table version 1.0 at 0xfdd50 Jun 12 18:05:00 jboat kernel: 00:12.0 -> irq 5 Jun 12 18:05:00 jboat kernel: 00:12.1 -> irq 5 Jun 12 18:05:00 jboat kernel: PnP: PNP BIOS installation structure at 0xc00fbf00 Jun 12 18:05:00 jboat kernel: PnP: PNP BIOS version 1.0, entry at f0000:bf28, dseg at f0000 Jun 12 18:05:00 jboat kernel: Intel PCIC probe: Jun 12 18:05:00 jboat kernel: TI 1225 rev 01 PCI-to-CardBus at slot 00:12, mem 0xdf002000 Jun 12 18:05:00 jboat kernel: host opts [0]: [pci only] [pci irq 5] [lat 32/176] [bus 32/34] Jun 12 18:05:00 jboat kernel: host opts [1]: [pci only] [pci irq 5] [lat 32/176] [bus 35/37] Jun 12 18:05:00 jboat kernel: PCI card interrupts, PCI status changes Jun 12 18:05:00 jboat cardmgr[924]: starting, version is 3.1.16 Jun 12 18:05:00 jboat cardmgr[924]: watching 2 sockets Jun 12 18:05:00 jboat kernel: cs: IO port probe 0x1000-0x17ff: clean. Jun 12 18:05:00 jboat kernel: cs: IO port probe 0x0100-0x04ff: clean. Now the Wavelan card is inseted into the PCMCIA slot ...... the machine freezes ...... and then the card is removed It looks like the card is recognized, a socket is set up, the driver is loaded, but then something goes wrong. Jun 12 18:05:26 jboat cardmgr[924]: initializing socket 0 Jun 12 18:05:26 jboat kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. Jun 12 18:05:26 jboat cardmgr[924]: socket 0: Lucent Technologies WaveLAN/IEEE Jun 12 18:05:27 jboat cardmgr[924]: executing: 'modprobe wavelan2_cs network_name=Ocean station_name=Wave2' Jun 12 18:05:28 jboat kernel: eth2: WaveLAN/IEEE, HCF failure: "Card not found (ejected unexpectedly)" Jun 12 18:05:29 jboat cardmgr[924]: get dev info on socket 0 failed: No such device Jun 12 18:05:31 jboat cardmgr[924]: shutting down socket 0 Jun 12 18:05:31 jboat cardmgr[924]: executing: 'modprobe -r wavelan2_cs' -

1. Fixed in 6.01beta driver by David Hinds, 2000, Jun 15

Question: Cannot set "mode" with iwconfig on WaveLan IEEE Date: 2000, Jun 16 From: viktor safar 4roses

Hi all, here I am again... So I have tried to use wireless.opts to set some parameters of WaveLan IEEE runnig with Andys driver and with PCMCIA driver 3.1.16 from Dave. Everything works fine (freq, essid, rate etc...) except "mode". I am not able to set this para- meter, 'cos it looks like not embeded in iwconfig. It is funny, because in generic example (and all other examples) of wireless.opts the "mode" parameter is PRESENT !!! Has anybody tried ever run this script ??? If I run iwconfig manually, for example: iwconfig wvlan1 mode Managed or iwconfig wvlan0 mode Ad-Hoc iwconfig yells: invalid argument: mode and than comes a list of available parameters, of course without mode... Is there another special version of iwconfig? Many thanx for any suggestions... viktor@salamon.sk

1. Question: version ? by Jean Tourrilhes, 2000, Jun 16 2. Ok: Ooops, yes, this is it! by viktor safar, 2000, Jun 19

Question: wvlan_cs: Initialization failed! Date: 2000, Jun 16 From: Lukas Zimmermann lukas

I'm trying to set up wireless network using Lucent WaveLAN IEEE pccards. I compiled the pcmcia package 3.1.16 on a system with a 2.0.36 kernel (for an embedded system). On insertion of the card I get: cardmgr[67]: initializing socket 1 cardmgr[67]: socket 1: Lucent Technologies WaveLAN/IEEE Adapter cardmgr[67]: executing: 'modprobe wvlan_cs port_type=3 channel=1 station_name=MY_PC' kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4 kernel: wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de> kernel: wvlan_cs: index 0x01: Vcc 5.0, irq 5, io 0x0100-0x013f kernel: wvlan_cs: Registered netdevice wvlan0 kernel: wvlan_cs: Initialization failed! cardmgr[67]: executing: './network start wvlan0' kernel: wvlan_cs: wvlan0 Tx timed out! Resetting card kernel: wvlan_cs: Initialization failed! last two lines repeating An ethernet card is running fine. Does anyone have an idea what's wrong?

1. Resource conflict? by David Hinds, 2000, Jun 16 (_ Disagree: Doesn't seem to be a resource conflict. by Lukas Zimmermann, 2000, Jun 16 1. Ok... by David Hinds, 2000, Jun 16 2. Sad: Compilation of wavelan2_cs.c fails by Lukas Zimmermann, 2000, Jun 19 1. Ok: Compilation succeeded by Lukas Zimmermann, 2000, Jun 19

Question: Can't boot using WaveLAN ISA Adapter Date: 2000, Jun 17 From: Alan Ostroff alan

I'm running RH6.1 and installed pcmcia-cs-3.1.16. After installed the WaveLAN ISA adapter, the computer hangs if PCMCIA services was enabled. My /etc/sysconfig/pcmcia is: PCMCIA=yes PCIC=i82365 PCIC_OPTS= CORE_OPTS= CARDMGR_OPTS= The card uses the Vadem VG-469 chip and the factory address hasn't been changed: 0x3e2. The following was in my /var/log/messages: Jun 17 09:50:59 shell1 pcmcia: Starting PCMCIA services: Jun 17 09:50:59 shell1 pcmcia: modules Jun 17 09:51:00 shell1 kernel: Linux PCMCIA Card Services 3.1.16 Jun 17 09:51:00 shell1 kernel: kernel build: 2.2.14-12 #4 Thu Jun 8 18:30:10 CEST 2000 Jun 17 09:51:00 shell1 kernel: options: [pci] [cardbus] [apm] Jun 17 09:51:00 shell1 kernel: Intel PCIC probe: Jun 17 09:51:00 shell1 kernel: Vadem VG-469 rev 00 ISA-to-PCMCIA at port 0x3e2 ofs 0x00 Jun 17 09:51:00 shell1 kernel: host opts [0]: none Jun 17 09:51:00 shell1 kernel: host opts [1]: none Jun 17 09:51:00 shell1 kernel: ISA irqs (scanned) = 3,4,7,9 polling interval = 1000 ms Jun 17 09:51:00 shell1 pcmcia: cardmgr. Jun 17 09:51:00 shell1 cardmgr[442]: starting, version is 3.1.16 Jun 17 09:51:00 shell1 rc: Starting pcmcia succeeded Jun 17 10:24:26 shell1 syslogd 1.3-3: restart. Any clues how to continue? Thanks, Alan

1. More: More info... by Alan Ostroff, 2000, Jun 18 (_ Re: More: More info... by David Hinds, 2000, Jun 19 (_ Sad: No luck... by Alan Ostroff, 2000, Jun 19 (_ Re: Sad: No luck... by David Hinds, 2000, Jun 19 (_ Ok: Success by Alan Ostroff, 2000, Jun 22

Question: card recognition problem with wavelan pcmcia-isa adapter Date: 2000, Jun 19 From: Arne Michaelsen amich

if have problems recognizing my wavelan IEEE 802.11 wireless network card. i'm using the wavelan isa-pcmcia adapter (vadem 469) in a hp visualize workstation (550mhz, 256mb) running Suse 6.4 (kernel 2.2.14, pcmcia 3.1.11). the howto says: The low level socket drivers, tcic and i82365, have various bus timing parameters that may need to be adjusted for certain systems with unusual bus clocking. Symptoms of timing problems can include card recognition problems, (!) lock-ups under heavy loads, high error rates, or poor device performance. Only certain host bridges have adjustable timing parameters: check the corresponding man page to see what options are available for your controller. Here is a brief summary: For Vadem VG-468 controllers, the async_clock flag changes the relative clocking of PCMCIA bus and host bus cycles. setting this flag adds extra wait states to some operations. However, I have yet to hear of a laptop that needs this. so i tested the async_clock flag (without success). here are some settings and results of my tests: /etc/rc.config: START_PCMCIA="yes" PCMCIA="i82365" PCMCIA_PCIC_OPTS="extra_sockets=1 async_clock=1" # also tested PCMCIA_PCIC_OPTS="" PCMCIA_CORE_OPTS="" /etc/pcmcia/config.opts (suse standart)? # System resources available for PCMCIA devices include port 0x100-0x4ff, port 0x800-0x8ff, port 0xc00-0xcff include memory 0xc0000-0xfffff include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff # High port numbers do not always work... # include port 0x1000-0x17ff # Extra port range for IBM Token Ring include port 0xa00-0xaff # Resources we should not use, even if they appear to be available # First built-in serial port exclude irq 4 # Second built-in serial port #exclude irq 3 # First built-in parallel port exclude irq 7 /etc/pcmcia/config: ... device "wavelan2_cs" class "network" module "wavelan2_cs" ... ------------------------------------------- www:~ # probe PCI bridge probe: not found. Intel PCIC probe: Vadem VG-469 found, 2 sockets. www:~ # rcpcmcia start PCMCIA: Starting services: PCMCIA: using scheme: SuSE PCMCIA: cardmanager is running done www:~ # lsmod Module Size Used by ds 6568 2 i82365 22128 2 pcmcia_core 45184 0 [ds i82365] usb-uhci 17000 0 (unused) autofs 9076 4 (autoclean) pcnet32 10944 1 (autoclean) dummy0 968 1 (autoclean) serial 42612 0 (autoclean) memstat 1476 0 (unused) usbcore 42344 1 [usb-uhci] ncr53c8xx 51988 3 /var/log/messeges: Jun 15 11:45:46 www rcpcmcia: /sbin/insmod /lib/modules/2.2.14/pcmcia/pcmcia_core.o Jun 15 11:45:46 www kernel: Linux PCMCIA Card Services 3.1.11 Jun 15 11:45:46 www kernel: kernel build: 2.2.14 #1 Sat Mar 25 00:46:59 GMT 2000 Jun 15 11:45:46 www kernel: options: [pci] [cardbus] [apm] Jun 15 11:45:46 www kernel: PCI routing table version 1.0 at 0xfdf30 Jun 15 11:45:46 www rcpcmcia: /sbin/insmod /lib/modules/2.2.14/pcmcia/i82365.o extra_sockets=1 async_clock=1 Jun 15 11:45:46 www kernel: Intel PCIC probe: Jun 15 11:45:46 www kernel: Vadem VG-469 ISA-to-PCMCIA at port 0x3e0 ofs 0x00 Jun 15 11:45:46 www kernel: host opts [0]: [async] Jun 15 11:45:46 www kernel: host opts [1]: [async] Jun 15 11:45:46 www kernel: ISA irqs (scanned) = 3,4,14 polling interval = 1000 ms Jun 15 11:45:46 www rcpcmcia: /sbin/insmod /lib/modules/2.2.14/pcmcia/ds.o Jun 15 11:45:46 www cardmgr[12082]: starting, version is 3.1.11 Jun 15 11:45:46 www cardmgr[12082]: watching 2 sockets Jun 15 11:45:46 www kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff Jun 15 11:45:46 www kernel: cs: IO port probe 0x0800-0x08ff: clean. Jun 15 11:45:46 www kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x220-0x22f 0x300-0x307 0x378-0x37f 0x388-0x38f 0x3f0-0x3ff 0x4d0-0x4d7 Jun 15 11:45:46 www kernel: cs: IO port probe 0x0a00-0x0aff: clean. wavelan card inserted low and high beep Jun 15 11:47:31 www cardmgr[12082]: initializing socket 0 Jun 15 11:47:31 www kernel: cs: memory probe 0x0d0000-0x0dffff: excluding 0xd0000-0xdffff Jun 15 11:47:31 www kernel: cs: memory probe 0x0c0000-0x0cffff: excluding 0xc0000-0xcffff Jun 15 11:47:31 www cardmgr[12082]: socket 0: Anonymous Memory Jun 15 11:47:31 www cardmgr[12082]: executing: 'insmod /lib/modules/2.2.14/pcmcia/memory_cs.o' Jun 15 11:47:31 www kernel: memory_cs: mem0: anonymous: unknown size Jun 15 11:47:31 www cardmgr[12082]: executing: './memory start mem0' www:~ # cardctl ident Socket 0: no product info available Socket 1: no product info available www:~ # cardctl status Socket 0: 5V 16-bit PC Card function 0: [ready] Socket 1: no card www:~ # dump_cis Socket 0: no CIS present Socket 1: no CIS present

1. Some things to try by David Hinds, 2000, Jun 20

Idea: Intel AnyPoint Wireless Date: 2000, Jun 19 From: Kelly Murray kem

Intel has recently released its "AnyPoint" wireless adapters. They have a PCMCIA card and a USB interface. Their website states no plans to support Linux. I find this interesting in that Intel has invested in RedHat. In any case, does anyone have any information on these products so a Linux driver can be written, or a contact at Intel to pursue it? thanks, kelly murray kem@netnimble.com

1. News: AnyPoint == Symphony/SWAP by Jean Tourrilhes, 2000, Jun 19 (_ Ok: Who to ask to get driver info? by Kelly Murray, 2000, Jun 19

Sad: USB and PCMCIA (ray_cs) hangs Date: 2000, Jun 20 From: Justin Cormack jpc

I am having some problems with since installing USB support on my machine (2.2 backport of usb-2.3.99-pre7-1, pcmcia 3.1.16, kernel 2.2.15). PCMCIA and USB share IRQ 9: 00:13.0 CardBus bridge: Ricoh Co Ltd RL5c475 Subsystem: Citicorp TTI: Unknown device 105a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 64 set Interrupt: pin A routed to IRQ 9 Region 0: Memory at <ignored> (32-bit, non-prefetchable) Bus: primary=00, secondary=01, subordinate=01, sec-latency=176 I/O window 0: 00000000-00000003 I/O window 1: 00000000-00000003 BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 00:01.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) (prog-if 00 [UHCI]) Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Interrupt: pin D routed to IRQ 9 Region 4: I/O ports at f4e0 If I have the uhci USB module installed and insert the ray_cs card the system hard locks wothout beeping. If I insert uhci when the card is already in there is no problem and both run fine. The Xircom CEM56 modem/ether card seems to behave ok (though it may hang occasionally). Unfortunately I get no logging messages before it dies, but here are the normal startup messages: Jun 20 12:52:08 localhost kernel: Linux PCMCIA Card Services 3.1.16 Jun 20 12:52:08 localhost kernel: kernel build: 2.2.15 #10 Mon Jun 19 21:57:09 BST 2000 Jun 20 12:52:08 localhost kernel: options: [pci] [cardbus] [apm] [pnp] Jun 20 12:52:08 localhost kernel: PCI routing table version 1.0 at 0xfdf80 Jun 20 12:52:08 localhost kernel: PnP: PNP BIOS installation structure at 0xc00f66a0 Jun 20 12:52:08 localhost kernel: PnP: PNP BIOS version 1.0, entry at f0000:b664, dseg at 400 Jun 20 12:52:08 localhost kernel: Intel PCIC probe: Jun 20 12:52:08 localhost kernel: Ricoh RL5C475 rev 00 PCI-to-CardBus at slot 00:13, mem 0x68000000 Jun 20 12:52:08 localhost kernel: host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 9] [lat 64/176] [bus 1/1] Jun 20 12:52:08 localhost kernel: ISA irqs (default) = 10,11,15 PCI status changes Jun 20 12:52:08 localhost cardmgr[2691]: starting, version is 3.1.16 Jun 20 12:52:08 localhost cardmgr[2691]: watching 1 sockets Jun 20 12:52:08 localhost kernel: cs: IO port probe 0x1000-0x17ff: clean. Jun 20 12:52:08 localhost kernel: cs: IO port probe 0x0100-0x04ff: clean. Jun 20 12:52:08 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean. Jun 20 12:52:10 localhost cardmgr[2691]: initializing socket 0 Jun 20 12:52:10 localhost kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. Jun 20 12:52:10 localhost cardmgr[2691]: socket 0: RayLink PC Card WLAN Adapter Jun 20 12:52:10 localhost cardmgr[2691]: executing: 'modprobe ray_cs' Jun 20 12:52:10 localhost kernel: ray_cs.c,v 1.19 2000/06/05 23:00:51 root Exp - Corey Thomas corey@world.std.com Jun 20 12:52:10 localhost kernel: ray_cs Detected: WebGear PC Card WLAN Adapter Version 4.88 Jan 1999 Jun 20 12:52:10 localhost kernel: eth0: RayLink, irq 10, hw_addr 00:00:F1:11:1D:60 Jun 20 12:52:10 localhost cardmgr[2691]: executing: './network start eth0' Of course this may just be a USB problem, but the fact that it only happens with one card suggests it may not be... With uhci installed here is a log with the Xircom card: Jun 20 13:33:16 localhost kernel: uhci.c: USB UHCI at I/O 0xf4e0, IRQ 9 Jun 20 13:33:16 localhost kernel: uhci.c: detected 2 ports Jun 20 13:33:16 localhost kernel: usb.c: new USB bus registered, assigned bus number 1 Jun 20 13:33:16 localhost kernel: usb.c: USB new device connect, assigned device number 1 Jun 20 13:33:16 localhost kernel: hub.c: USB hub found Jun 20 13:33:16 localhost kernel: hub.c: 2 ports detected Jun 20 13:33:55 localhost kernel: Linux PCMCIA Card Services 3.1.16 Jun 20 13:33:55 localhost kernel: kernel build: 2.2.15 #10 Mon Jun 19 21:57:09 BST 2000 Jun 20 13:33:55 localhost kernel: options: [pci] [cardbus] [apm] [pnp] Jun 20 13:33:55 localhost kernel: PCI routing table version 1.0 at 0xfdf80 Jun 20 13:33:55 localhost kernel: PnP: PNP BIOS installation structure at 0xc00f66a0 Jun 20 13:33:55 localhost kernel: PnP: PNP BIOS version 1.0, entry at f0000:b664, dseg at 400 Jun 20 13:33:55 localhost kernel: Intel PCIC probe: Jun 20 13:33:55 localhost kernel: Ricoh RL5C475 rev 00 PCI-to-CardBus at slot 00:13, mem 0x68000000 Jun 20 13:33:55 localhost kernel: host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 9] [lat 64/176] [bus 1/1] Jun 20 13:33:55 localhost kernel: ISA irqs (default) = 10,11,15 PCI status changes Jun 20 13:33:55 localhost cardmgr[1196]: starting, version is 3.1.16 Jun 20 13:33:55 localhost cardmgr[1196]: watching 1 sockets Jun 20 13:33:55 localhost kernel: cs: IO port probe 0x1000-0x17ff: clean. Jun 20 13:33:55 localhost kernel: cs: IO port probe 0x0100-0x04ff: clean. Jun 20 13:33:55 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean. Jun 20 13:33:56 localhost cardmgr[1196]: initializing socket 0 Jun 20 13:33:56 localhost kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. Jun 20 13:33:56 localhost cardmgr[1196]: socket 0: Xircom CEM56 Ethernet/Modem Jun 20 13:33:56 localhost cardmgr[1196]: executing: 'modprobe xirc2ps_cs' Jun 20 13:33:56 localhost kernel: xirc2ps_cs.c 1.31 1998/12/09 19:32:55 (dd9jn+kvh) Jun 20 13:33:56 localhost cardmgr[1196]: executing: 'modprobe serial_cs' Justin

1. A tricky problem by David Hinds, 2000, Jun 20

Question: Reducing the range of Lucent Wavelan cards Date: 2000, Jun 21 From: Mattis Fjällström Mattis

Is there anyone out there who knows how to reduce the signal strength of Lucent wavelan cards by software? We're about to perform some tests of Ad-Hoc routing protocols on the University where I am currently employed, but with a range of 200 meters it won't work very well. It seems to make sense to me that there might be some parameters to set in order to reduce range - would at least be useful for Lucent technicians while testing. This is unfortunately the kind of feature that is not covered in your average user manual... :-)

Question: Can't ping Wavelan/IEEE in ad-hoc mode Date: 2000, Jun 22 From: Alan Ostroff alan

I'm trying to setup a Wavelan/IEEE card in a linux box already configured with IP Masq and an NE2000 card and communicate with a stand alone WIN95 laptop using the same card. I've configured the WIN95 Wavelan driver with "ANY" as the Network Name and selected Ad-Hoc demo mode. It's IP address is 192.168.0.5. To test it, I configured another WIN95 laptop with the same config and was able to ping each machine. Back to Linux... I've removed the comments and modified the wireless.opts file to: # Lucent Wavelan IEEE # Note : wvlan_cs driver only, and version 1.0.4+ for encryption support *,*,*,00:60:1D:*) INFO="Wavelan IEEE example (Lucent default settings)" ESSID="ANY" MODE="ad-hoc" RATE="auto" ;; This seems to work fine because when I run iwconfig (wireless tools.20) I get: lo no wireless extensions. eth0 no wireless extensions. ppp0 no wireless extensions. wvlan0 IEEE 802.11-DS ESSID:"" Nickname:"shell1.alan.com" Frequency:2.422GHz Sensitivity:1/3 Mode:Ad-Hoc Access Point: 00:00:00:00:00:00 Bit Rate:11Mb/s RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 invalid crypt:0 invalid misc:0 Strangly enought, when I run ifconfig wvlan0 up to bring up the wireless interface, I see: eth0 Link encap:Ethernet HWaddr 00:80:AD:A7:FD:32 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:782 errors:0 dropped:0 overruns:0 frame:0 TX packets:890 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:127 errors:0 dropped:0 overruns:0 frame:0 TX packets:127 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 ppp0 Link encap:Point-to-Point Protocol inet addr:213.36.65.189 P-t-P:212.155.245.193 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:917 errors:32 dropped:0 overruns:0 frame:32 TX packets:979 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 wvlan0 Link encap:Ethernet HWaddr 00:60:1D:F1:51:24 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 And no IP address is identified for the wvlan0 interface. However, if I run netcfg and reactive the wvlan0 interface, I get: wvlan0 Link encap:Ethernet HWaddr 00:60:1D:F1:51:24 inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 I can ping 192.168.0.4 sucessfully from the linux box. Shouldn't the IP address be assigned to the interface when I run ifconfig wvlan0 up? Anyway, the real problem is that even at this stage, if I ping from the linux box to 192.168.0.5 I get nothing. If I ping from the WIN95 box to 192.168.0.4 I get nothing, however if I run iwconfig I see the rx packet counter increase. Any ideas? Thanks, Alan

1. Looks like it might be a routing issue by David Hinds, 2000, Jun 22 1. Sad: Routing?? by Alan Ostroff, 2000, Jun 22 2. Idea: Hum... ad-hoc in config.opts might help... by Jean Tourrilhes, 2000, Jun 22 1. Question: Ad-hoc mode by Alan Ostroff, 2000, Jun 23 (_ Jean is leading you astray on this one by David Hinds, 2000, Jun 23 3. Ok: Success! by Alan Ostroff, 2000, Jun 23

Question: Lucent WaveLAN/IEEE works with wavelan2_cs but not with wvlan_cs Date: 2000, Jun 29 From: Leo Scharf ll

Hi! I have a problem: my Silver WaveLAN/IEEE does not work with wvlan_cs driver. Driver says: Jun 29 20:56:53 flux kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4 Jun 29 20:56:53 flux kernel: wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de> Jun 29 20:56:53 flux kernel: wvlan_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f Jun 29 20:56:53 flux kernel: wvlan_cs: Registered netdevice wvlan0 Jun 29 20:56:53 flux kernel: wvlan_cs: Initialization failed! Jun 29 20:57:24 flux kernel: wvlan_cs: wvlan0 Tx timed out! Resetting card Jun 29 20:57:24 flux kernel: wvlan_cs: Initialization failed! ifconfig says: wvlan0 Linkverkapselung:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.5.241 Bcast:192.168.5.255 Maske:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Empfangene Pakete:0 Fehler:0 Weggeworfen:0 Überlauf:0 Rahmen:0 Verschickte Packete:0 Fehler:0 Weggeworfen:0 Überlauf:0 Rahmen:0 Kollisionen:0 Sendewarteschlangenlänge:100 Basisadresse:0x100 (sorry, my locale is german) output from iwconfig looks fine: wvlan0 IEEE 802.11-DS ESSID:"non-specified SSID !!" Nickname:"flux" Frequency:2.422GHz Sensitivity:1/3 Mode:Ad-Hoc Access Point: 00:00:00:00:00:00 Bit Rate:2Mb/s RTS thr:off Fragment thr=2347 B Encryption key:off Power Management:off Link quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 invalid crypt:0 invalid misc:0 Actually, i'd like to drive my wireless network with encoding and only this driver can do this to my card. wavelan2_cs (ver. 6.00) works, but i can not use encryption with it. I use Debian woody with 2.2.15 kernel, wireless utilities v20, pcmcia 3.1.15. I will be thankfull for any help. Leo

1. Ok: Solved!!!! by Leo Scharf, 2000, Jun 29

Question: Wavelan IEEE getting "Destination Host Unreachable" Date: 2000, Jun 30 From: Mike Bates mbates

I have a Wavelan IEEE card on a desktop trying to configure for RH 6.2 with pcmcia_cs 3.1.11 and Wavelan 6.00 drivers. Looks like I followed the directions but I am getting "Destination Host Unreachable" when ping outside of my machine. The network traffic hits loopback. The lights look fine, I get a double beep, and my laptop works fine with windows. Please any ideas? Thanks Mike

1. More: More info by Mike Bates, 2000, Jun 30 2. Ok: Solved by Mike Bates, 2000, Jul 01

Question: Problems with Breezecom Wireless Lan - long ping times Date: 2000, Jun 30 From: interdart

I am trying to setup Redhat 6.2 with a Breezecom card. The card loads ok, and the network estblishes a connection, however the ping times are in to 200 to 1000 ms range. This is not a radio signal strength problem, the same card in a 486 W95 gices ping 0-90ms I am using a desktop machine with an Elan P111 PCI card adapter (TI chipset?). Other pcmcia ethernet cards work at an acceptable speed though the Kingston (ne) gives ping of 20ms. Can anyone suggest where to start looking for a for a solution toothis probvlem?

1. Interrupt delivery problem, probably by David Hinds, 2000, Jul 05

Question: Modem and ORiNOCO Gold PC Card don't like eachother Date: 2000, Jul 03 From: Max Enders <menders@drizzle.com>

Greetings, This problem exists for me in both Windows and Linux. I have an internal modem and the ISA adapter in my desktop box. The other computer is my notebook. The communication between the two computers is fine. The problem is when I'm trying to use my modem and the WaveLAN card at the same time. My Internet connection becomes unusable or I'll get disconnected. I can ping www.yahoo.com for 5 minutes with no loss, for example, and as soon as I try to access the other computer over the WaveLAN connection it starts dropping packets. Any suggestions? Any advice is immensely appreciated. Thanks! -- Max Enders, Microsoft Certified Systems Engineer Email: menders@drizzle.com Public PGP key: http://www.drizzle.com/~menders

Question: Wavelan/Linux cannot talk to Wavelan/Windows Date: 2000, Jul 04 From: Mubashir Cheema cheema

I have got several Cabletron cards working under Linux. They talk to other Linux laptops (there is no Access Point). Now I am trying to add a Windows laptop in the mix. I cannot get the Windows laptop to see any of the other Linux laptops out there. On the Linux side I have tried using both the wvlan_cs and the wvlan2_cs modules but no go, they talk to each other just fine, but not to the Windows laptop. On the Windows side I have tried changing the following configuration options: - Wireless network name [Tried blank and tried "home".] - Station name [Tried blank and tried "laptop4"] Thats pretty much it. I was under the impression that the "Wireless network name" was all that needed changing and everything else was automatic. I am using Linux kernel version 2.2.14 and pcmcia version 3.1.8. Any pointers would be greatly apreciated. Thanks. -Cheema

1. Feedback: Yea, it's not working !! by Alex Lam, 2000, Aug 04 2. Sad: me too, it's not working by Yaddi K Rustandi, 2000, Oct 17

Question: 2 wavelan2_cs cards in one machine Date: 2000, Jul 05 From: Wynand Theunissen Masked

I've installed 2 PCMCIA 11 Meg lucent wavelan2_cs cards in one machine. The cards are all found and installed right but I have the following problem: The wavalan2_cs module is initialized with the network_name found in the config.opts of the pcmcia services .... thus both the cards are initialized with the same network_name cause they are both identified as the same. How do I tell the pcmcia stuff to ininitialize each card with different options although both cards seem exactly the same ? Regards Wynand Theunissen

1. Sad: I am having similar problems, and many more also. by R J Delmar, 2000, Jul 05 (_ Feedback: 2 card hassles by Wynand Theunissen, 2000, Jul 05

2xPCMCIA WaveLan cards working great in the same system Date: 2000, Jul 05 From: R J Delmar Delmar

I dunno what the crap was wrong with me before. The whole thing is so damn easy. It was starin me in the face. Feelin quite stupid :). I did have a problem with my wireless tools, which when fixed, the wireless.opts kicked into life. The rest was easy. I am running Debian Woody, kernel 2.2.16, pcmcia-cs 3.1.16-2, wireless tools-20 etc. Drivers are stock standard from the pcmcia-cs package. I have tried my best to get the wavelan2_cs-6.00 drivers to compile in with the pcmcia-cs 3.1.16 and 3.1.17 source packages, but the system just locks up when pcmcia services are started and I have given up on that. Not sure I am missing out on much compared to the wavelan drivers which come with pcmcia-cs 3.1.16-2 anyway. SO...For those that are trying to get two cards workin on one system.... The Wireless.opts and Network.opts are layed out real simple. In fact, it's the same way for both. I choose to use the hardware address to define which card to configure... naturally XX:XX:XX:XX:XX:XX is the hardware address of the adaptor, which is printed on the PCMCIA card. Wireless.opts brief example... #Card 0 *,*,*,XX:XX:XX:XX:XX:XX) INFO="Your Options go here..." ESSID="More options...." MODE="More Options....." (you will find a list of all the options you can use already in the file) #Card 1 *,*,*,XX:XX:XX:XX:XX:XX) INFO="Whatever" ESSID"something else" MODE="yadda yadda" --- Network.opts brief example.... #Card 0 *,*,*,XX:XX:XX:XX:XX:XX) IPADDR="123.123.123.123" NETMASK="255.255.255.0" (you get the idea..... ) #Card 1 *,*,*,XX:XX:XX:XX:XX:XX) (and the same here.... ) Basically easy once I opened my eyes and realised how it was meant to work. I still have some tests to run on a few things....but i am stoked. Cheers, Delmar.

1. 2xPCMCIA WaveLan cards working great in the same system by Wynand Theunissen, 2000, Jul 05

Sad: Lucent PCI/PCMCIA adapter + Wavelan IEEE silver Date: 2000, Jul 13 From: Douglas S. J. De Couto decouto

hi. i am trying to get my lucent wavelan ieee silver pcmcia card work with my lucent pci/pcmcia expansion card. i have read this board, and tried various things but still have transmit timeouts and ridiculously long ping times (> 4 seconds). setup: redhat 6.2, kernel 2.2.14, pcmcia 3.1.18 2-way SMP PIII i have tried the following: using the wvlan_cs driver: PCIC_OPTS="irq_list=11" # works but with poor ping times. i had to specify only the # single irq for it to work at all using the wavelan2_cs lucent driver: PCIC_OPTS="cb_pci_irq=11" # doesn't work, option not recognized (i saw this on the board somewhere) PCIC_OPTS="irq_list=11" # slow pings and timeouts PCIC_OPTS="irq_mode=0" # can't find pci irq: e.g. host opts [0]:... [no pci irq] PCIC_OPTS="pci_irq_list=11 irq_mode=0" # gives: host opts [0]:... [pci irq 11] # but still get: wavelan2_cs: RequestIRQ: Resource in use PCIC_OPTS="pci_irq_list=11,11 irq_mode=0" # as in previous case i have also seen my computer lock up using the PCIC_OPTS="irq_list=11" and the lucent driver... any ideas? thanks, doug --------------------- some other output: bermuda% cat /proc/interrupts CPU0 CPU1 0: 350442 335519 IO-APIC-edge timer 1: 5573 5662 IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 12: 28942 30998 IO-APIC-edge PS/2 Mouse 13: 1 0 XT-PIC fpu 14: 13276 10843 IO-APIC-edge ide0 19: 6333 6444 IO-APIC-level aic7xxx, aic7xxx 21: 3520 3551 IO-APIC-level Intel EtherExpress Pro 10/100 Ethernet NMI: 0 ERR: 0

1. Question: Ping time ? by Jean Tourrilhes, 2000, Jul 13 2. Need more information by David Hinds, 2000, Jul 13 1. More: more info. by Douglas S. J. De Couto, 2000, Jul 13 (_ Strange interrupt routing information by David Hinds, 2000, Jul 13 (_ not working still by Douglas S. J. De Couto, 2000, Jul 13 3. Question: same problems on single processor by Douglas S. J. De Couto, 2000, Jul 16 1. No interrupt routing table by David Hinds, 2000, Jul 17 (_ Re: No interrupt routing table by Douglas S. J. De Couto, 2000, Jul 18 (_ Oops, I left out something important by David Hinds, 2000, Jul 18 (_ Re: Oops, I left out something important by Douglas S. J. De Couto, 2000, Jul 20

Question: Help getting Webgear Aviator 2.4 working under linux Date: 2000, Jul 13 From: Robert Lowery reddwarf

Hi, I am having some trouble getting my WebGear Aviator 2.4 PCMCIA card working under linux. It is running perfectly on my two laptops running Windows 98SE, but I cannot get it to work on my firewall (ie desktop machine with the supplied ISA card). I am runnning RedHat 6.1, with kernel 2.2.16 and pcmcia-cs-3.1.18 I have had this working in the past, but that was with less other network cards and with pcmcia-cs-3.1.15. The server now has 3 wired network cards in it, all working (smc-ultra, 3c509 and ne). but when I do a /etc/rc.d/init.d/pcmcia start /sbin/ifconfig seems to be ok eth3 Link encap:Ethernet HWaddr FF:00:FF:48:FF:B3 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:5 but cat /proc/ray_cs says Card doing acquisition and never Acquisition complete like it did in the past, and neither of my Win 98 laptops can access the server. Raylink Wireless LAN driver status ray_cs.c,v 1.19 2000/06/05 23:00:51 root Exp - Corey Thomas corey@world.std.com Firmware version = 4 - Use dump_cis for more details Adhoc network ESSID = "RALPHHOME" BSSID = 00:00:00:00:00:00 Country code = 1 Card status = Card doing acquisition Framing mode = Encapsulation Last pkt signal lvl = 0 No beacons received I modified the configuration files for pcmcia in the following way config.opts module "ray_cs" opts "essid=XXXXXX translate=0 pc_debug=3" network.opts IPADDR="192.168.1.1" NETMASK="255.255.255.0" NETWORK="192.168.1.0" BROADCAST="192.168.1.255" GATEWAY="192.168.1.1" wireless.opts *,*,FF:00:FF:48:FF:B3,*) INFO="Raylink/Aviator2.4 example (Aviator default ad-hoc setting)" ESSID="XXXXXX" MODE="Ad-Hoc" RATE="auto" IWPRIV="set_framing 0" ;; Any ideas? -Robert Lowery

1. More info by Robert Lowery, 2000, Jul 13 2. Ok: Problem solved - I think there is a bug in 3.1.18 by Robert Lowery, 2000, Jul 13 3. Question: I think I spoke too soon by Robert Lowery, 2000, Jul 13 4. Sad: ray_cs.c and wireless.opts by Jean Tourrilhes, 2000, Jul 13 5. Bad hw address by David Hinds, 2000, Jul 15

News: Wavelan IEEE : state of the wvlan_cs driver... Date: 2000, Jul 14 From: Jean Tourrilhes jt

Hi,   I managed to find a bit of time collect all my info about the wvlan_cs driver and put that on a web page :   http://bougret.hpl.hp.com/~jt/Linux/Wavelan-IEEE.html   Please check it out befores asking me the same question for the 45th time ;-)   Jean

1. Sad: Correct URL by Jean Tourrilhes, 2000, Jul 18

Question: Any experience with PCI docking cards? Date: 2000, Jul 17 From: Stephane Laroche slaroche

I'm looking into buying PCI cards to make our desktop computers wireless (under Linux) and I was wondering if the people over here have any good or bad experiences with such adapters? Any specific cards should be avoided? The desktop computers themselves are quite new (Dell, IBM). Thanks, -Stephane

1. Warning: bad experiences... by Douglas S. J. De Couto, 2000, Jul 18

Question: Lucent Wavelan IEEE Turbo 11M Date: 2000, Jul 18 From: Kirmo Koistinen kikoisti

Howdy. I have problem with this lucent card. I use kernel 2.2.16, pcmcia 3.1.17 and wireless tools 20. I have compiled Wireless extension support to kernel and I have tested both GPL-driver and Wavelan2 6.00, 6.01Beta drivers. When I use GPL driver iwconfig find card normally but when I try to configure card with it whole system jamms. When I use Wavelan2 driver iwconfig wont find card at all("eth0 no wireless extensions"). Log's shows that cardmgr install's card "correctly".I need to use wavelan2 driver because I need the encryption support. Both lights blinks but I dunno if this is right or wrong. Please help me. I am getting pretty tired up with this card. :) - Kirmo

1. Need more detailed information by David Hinds, 2000, Jul 18 (_ here are logs. by Kirmo Koistinen, 2000, Jul 19 (_ Problem solved. by Kirmo Koistinen, 2000, Jul 27

Question: Cannot config. WaveLan IEEE Turbo after kernel upgrade Date: 2000, Jul 19 From: Tim DIckerson n9nu

I am having a problem getting my WaveLan ISA/PCMCIA card to configure properly when i upgraded to the newest stable kernel 2.2.16. With 2.2.15 it detects and configures properly without any problems. I just compiled the new kernel to include all the necessary support and still no go. I have no resource conflicts.... an "ifconfig" shows the "wvlan0" card is present. I also re-compiled the PCMCIA drivers for the new kermel. I am using Linux Mandrake 7.1, Kernel 2.2.16, pcmcia-cs-3.1.18, and the Lucent WaveLan 802.11 ISA Bronze Turbo card. This is ONLY used for my INET connection... not my home network. Tnx for help Tim

1. That does not sound familiar by David Hinds, 2000, Jul 19

Question: Looking for LRP/Wavelan prototype Date: 2000, Jul 20 From: J Will JWill

Does anyone have a working LRP floppy image of a simple router between a Wavelan PC card (in a wavelan ISA adaptor) and a standard nic card (ie 3c509) that they would care to share? I've been working with the dummy image that Mark Lachniet posted (ftp://lachniet.com/pub .....) but it won't work with anything but his specific hardware (his README indicates this and I found out the hard way after many days of trying). I am most certainly willing to have a piping hot extra large Pizza Hut pizza with all of your favorite toppings delivered right to your door to the noble individual who is willing to help me with my dilema. I thank you, my wife and kids thank you, my dog thanks you .....

Question: Wavelan Problem Date: 2000, Jul 20 From: Peter Zimmer pzimmer

Everthing seems to work allright: it beeps two times when insering card , that is displayed in logfile: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4 Jul 20 17:31:08 fly kernel: wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de> Jul 20 17:31:08 fly kernel: wvlan_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f Jul 20 17:31:08 fly kernel: wvlan_cs: Registered netdevice wvlan0 Jul 20 17:31:08 fly kernel: wvlan_cs: MAC address on wvlan0 is 00 60 1d 21 df 90 Jul 20 17:31:08 fly cardmgr[1197]: executing: './network start wvlan0' but nothing show up on ifconfig. the device is missing and i cant configure it. whats wrong ??

1. Re: Question: Wavelan Problem by David Hinds, 2000, Jul 20

wvlan_cs fails on startup with "Resource temporarily unavailable" Date: 2000, Jul 21 From: Bob Cook bcook

My configuration includes the WaveLAN in an ISA adapter plus two ethernet cards (eth0 and eth1) and I expect the WaveLAN card to become 'eth2'. So far I've had no luck with either wvlan_cs or wavelan2_cs for drivers. Note that this is a brand-new card and I don't really have another way to test if its good or not. kernel: Linux PCMCIA Card Services 3.1.17 kernel: kernel build: 2.2.12-20 #3 Fri Feb 25 23:42:22 PST 2000 kernel: options: [pci] [cardbus] kernel: Intel PCIC probe: kernel: Vadem VG-469 rev 00 ISA-to-PCMCIA at port 0x3e0 ofs 0x00 kernel: host opts [0]: none kernel: host opts [1]: none kernel: ISA irqs (scanned) = 3,4,5,7,11,15 status change on irq 15 cardmgr[9171]: starting, version is 3.1.17 cardmgr[9171]: watching 2 sockets kernel: cs: IO port probe 0x0c00-0x0cff: clean. kernel: cs: IO port probe 0x0800-0x08ff: clean. kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x3b8-0x3e7 cardmgr[9171]: initializing socket 0 kernel: cs: memory probe 0x0d0000-0x0dffff: clean. cardmgr[9171]: socket 0: Lucent Technologies WaveLAN/IEEE cardmgr[9171]: executing: 'modprobe wvlan_cs port_type=3 eth=1' kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4 kernel: wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de> cardmgr[9171]: get dev info on socket 0 failed: Resource temporarily unavailable Thanks for any hints or suggestions.

1. More: does HCF_ERR_NO_NIC mean bad hardware? by Bob Cook, 2000, Jul 26 (_ A shot in the dark by David Hinds, 2000, Jul 26 (_ Feedback: No luck... Where can I get details about the WaveLAN? by Bob Cook, 2000, Jul 28 (_ More: On Andy's page... by Jean Tourrilhes, 2000, Jul 29 (_ Question: Some questions about your message by Bob Cook, 2000, Jul 29 1. Sad: Hum... by Jean Tourrilhes, 2000, Jul 31 2. The PCI->PCMCIA adapters are the tricky ones by David Hinds, 2000, Jul 31

Question: Aironet 4800 slowness Date: 2000, Jul 26 From: Matthew Winther <winther@rni.net>

I am using an aironet pcmcia 4800 adapter with linux kernel 2.2.16 and pcmcia card services 3.1.19. All seems well, the drivers load I can ping across the link, however when I ftp across the link the session seems to be very unstable. The transfer rate is slow over all, the transmission seems to stop at times. when the transmission stops pings and telnet sessions still seem to work. The problem only seems to exist with bulk data transfers. Any thoughts on how I can trouble shoot this would be greatly appreciated. Matt

Question: Wavelan & PCMCIA & 2.2.13 Kernel Date: 2000, Jul 26 From: J Will JWill

I don't have a full blown linux machine to work from. I want to create a single floppy LRP (inux router) with a Wavelan nic and a 3c509 nic. I've been able to find and modify idiot images that have one or the other working but not both. My attempt to modify the dummy image from Mark Lachniet (ftp://lachniet.com) to use a 3c509 was unsuccessful. (yes I found a 3c509.o compiled for the right kernel - 2.2.11 and put it in the right place) The wavelan side worked great though, I could ping the world (it was talking to an access point connected to the internet). Mark's README indicates that that image won't work with anything but his specific hardware (I found this out the hard way after many days of trying). I then found an eth-eth LRP which allowed me to set the 3c509 up and it works great, just no wavelan. I'd like to add the wavelan support to this working image, it uses the 2.2.13 kernel. I believe all I need to add is this: /lib/modules/2.2.13/pcmcia_core.o /lib/modules/2.2.13/i82365.o /lib/modules/2.2.13/ds.o /lib/modules/2.2.13/wavelan2_cs.o /etc/init.d/pcmcia /sbin/cardmgr /etc/pcmcia/network /etc/pcmcia/network.opts /etc/pcmcia/shared /etc/pcmcia/config /etc/pcmcia/config.opts Please correct me if I'm wrong. Problem is, without a full linux system to work from I can't build the appropriate pcmcia and wavelan drivers. Anybody care to be a good samaritan and compile these drivers with the 2.2.13 kernel for me. I would be eternally greatful. If I get this working, I'll gladly put the resulting "idiot" image on my ftp server for all to benefit from. Thanks.

Question: Ping returns BAD CHECKSUM on Cabletron Roamabout Date: 2000, Jul 29 From: Jesse Byler jbyler

Hello all, I have a Cabletron Roamabout 802.11 DS wireless NIC, which I understand is the same card as the Lucent Wavelan IEEE, in an embedded linux system running RedHat 6.2. The hardware consists of an Ampro CoreModule/4GV PC/104 CPU, a Diamond-MM-16 A/D card, and a PCMCIA card for which I don't know the manufacturer off-hand. All 3 modules are PC/104 boards. The software started out as a standard RedHat 6.2 installation (kernel 2.2.14-5.0). I compiled my own kernel from the 2.2.14 sources and added the PCMCIA cardservices package version 3.1.15 with Lucent's wavelan2_cs binary driver version 6.02. I'm trying to get this card to talk to an Apple Airport, which has a Lucent WaveLAN IEEE/silver card inside it. Actually, the Cabletron card *does* talk to the airport. I can sometimes even connect to the embedded system using ssh, though usually outgoing ssh (from the embedded system) doesn't get very far. Most network connections will hang for long periods of time and then sometimes continue, sometimes time out. The key piece of evidence is that ping shows a high corruption rate on the echo replies it receives. Here is a portion of a ping transcript: PING 10.0.1.4 (10.0.1.4) from 10.0.1.21 : 56(84) bytes of data. 64 bytes from 10.0.1.4: icmp_seq=0 ttl=255 time=9.1 ms 64 bytes from 10.0.1.4: icmp_seq=1 ttl=255 time=10.2 ms (BAD CHECKSUM!) wrong data byte #28 should be 0x1c but was 0x1e bd 14 81 39 16 84 3 0 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1 b 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 64 bytes from 10.0.1.4: icmp_seq=2 ttl=255 time=8.0 ms 64 bytes from 10.0.1.4: icmp_seq=3 ttl=255 time=8.9 ms 64 bytes from 10.0.1.4: icmp_seq=4 ttl=255 time=8.0 ms (BAD CHECKSUM!) wrong data byte #48 should be 0x30 but was 0x32 c0 14 81 39 cd 83 3 0 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1 b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 64 bytes from 10.0.1.4: icmp_seq=5 ttl=255 time=8.0 ms (BAD CHECKSUM!) wrong data byte #32 should be 0x20 but was 0x22 c1 14 81 39 54 92 3 0 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1 b 1c 1d 1e 1f 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 64 bytes from 10.0.1.4: icmp_seq=6 ttl=255 time=7.9 ms 64 bytes from 10.0.1.4: icmp_seq=7 ttl=255 time=7.9 ms <...> --- 10.0.1.4 ping statistics --- 100 packets transmitted, 79 packets received, +21 corrupted, 21% packet loss round-trip min/avg/max = 4.8/6.0/15.4 ms This corruption does *not* appear if I ping myself, but it does appear when I ping any other host (local wireless net or internet with NAT). I don't know for sure that the ping client I have on the MacOS laptops which make up the remainder of the wireless network checks the checksum, but I don't see any BAD CHECKSUM errors with it. I know the airport works as there is an existing wireless network using it, generally with no problems. The Cabletron card works fine when installed on a Windows 95 system. I've tried both the binary driver from Lucent (latest version) and the GPL driver from Andreas Neuhaus. I've tried with and without 40-bit WEP encryption. In all cases the behaviour is similar, though the severity of the problem changes. Sometimes almost no network connections succeed; other times I can do alot. Anyone have any ideas what the problem might be? =) Perhaps the Cabletron isn't really exactly the same as the Lucent Wavelan IEEE? Maybe the card is flaky? Perhaps the PCMCIA board is causing the problem? Or is it a software issue? Thanks in advance! -Jesse

Question: Wavelan as Access Point Date: 2000, Jul 30 From: Kelly Murray kem

What does it take to configure a lucent 11mbps card as an Access Point (AP) like an Airport Base Station? Otherwise, I can't talk to my main wireless base computer unless I have an actual Access Point doing the talking. If I configure the base computer in adhoc mode, then it can't talk to the AP's. I've looked at the sources and available docs for the wvlan_cs driver, and didn't see anything about this. Is this port_mode 2 ? mode 1 = client, mode 3 = adhoc, but what is mode 2 ? much thanks for any info, or a pointer to it. -Kelly Murray kem@netnimble.com

1. Sad: Not possible... by Jean Tourrilhes, 2000, Jul 31

Question: Problem with Wavelan Turbo 11Mbps Date: 2000, Jul 31 From: Alex Lam <alex.lam@radiata.com>

Hi There, I am using a desktop with the PCI adapter + Kernel 2.2.16 + PCMCIA-3.1.19 + wvlan_cs driver and I am problem sending data out using the wvlan0 interface. The interface is there and it responds to iwconfig. However, when I send data through it, the led doesn't blink at all. This is what I get when I type iwconfig wvlan0 IEEE 802.11-DS ESSID:"any" Nickname:"gileswave" Frequency:2.422GHz Sensitivity:1/3 Mode:Ad-Hoc Access Point: 00:00:00:00:00:00 Bit Rate=11Mb/s RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 invalid crypt:0 invalid misc:0 Can you see anything wrong ? And when I try to ping another machine with the same configuration, I get the following. PING willowwave.radiata.com (10.200.20.11) from 10.200.20.10 : 56(84) bytes of data. From gileswave.radiata.com (10.200.20.10): Destination Host Unreachable Any ideas ? Thanks in advance. Alex

1. More: More info... by Alex Lam, 2000, Jul 31 1. Sad: Timeout cause... by Jean Tourrilhes, 2000, Jul 31 2. Sounds like an interrupt problem; need more messages by David Hinds, 2000, Jul 31 1. More: Very similar problem here by Elliot Lee, 2000, Aug 02 ... 4 Message(s)

Sad: problem compiling wvlan_cs.c and kernel 2.40-pre5 Date: 2000, Aug 01 From: Brett Eldridge beldridg

I can't seem to compile the wvlan_cs PCMCIA module with the 2.4.0-test5 kernels. I sent mail to Andy but I think he is too busy. I built the kernel with: # CONFIG_PCMCIA is not set I am using pcmcia-cs-3.1.19 When I build the module, here are the errors: wvlan_cs.c: In function `wvlan_detach': wvlan_cs.c:2809: warning: implicit declaration of function `kfree_s And, of course, when I try to insmod: [root@tool wireless]# modprobe wvlan_cs /lib/modules/2.4.0-test5/pcmcia/wvlan_cs.o: unresolved symbol kfree_s BTW - this same compilation error occurs on the airo_cs module. I think it is a problem with the includes and the new kernel. I've tried -D__IN_PCMCIA_PAKAGE_ plus a lot of other minor adjustments, but nothing seems to work. Please help. Thanks, - brett

1. Already fixed in current beta by David Hinds, 2000, Aug 01

Question: Lucent WaveLan don't update statistics Date: 2000, Aug 02 From: Vladimir Vlach vladaman

Hi, I am using TurboLinux Server 6.0 + PCMICA_CS 3.1.14 and kernet 2.2.14. WaveLan works well, but statistics in /proc/net/wireless are still the same :( $ cat /proc/net/wireless Inter-| sta-| Quality | Discarded packets face | tus | link level noise | nwid crypt misc eth2: 0000 0. 154. 154. 0 6 16865 Where can be problem? Where can I found any additional informations about link Quality? Many thanks Vladimir Vlach vvlach@danet.cz

1. More: Firmware version by Vladimir Vlach, 2000, Aug 02 2. Agree: same with me by Marcio Gomes, 2000, Aug 10

SWL-2000P 11Mbps Wireless LAN PCI Card + Linux Date: 2000, Aug 02 From: Wynand Theunissen Masked

Ive been playing with pcmcia-cs-3.1.19 and .17 and the Samsung MagicLAN SWL-2000P PCI card. The pcmcia core modules are loaded find and then it gives me the following error during the initialization of the 11meg card: Bad Vcc when a do a cardctl it says Vcc 3.3V I've tried these cards on different boxes and even swapped out the card to make sure its not faulty hardware. Anyone have any ideas regarding this ? Wynand Theunissen

1. Re: SWL-2000P 11Mbps Wireless LAN PCI Card + Linux by David Hinds, 2000, Aug 03

Question: Interrupt problem with P60, WaveLAN/IEEE and TI-1221 Date: 2000, Aug 02 From: Sami Pitko spitko

The problem is that WaveLAN/IEEE is initialized properly but it gives "transmit timeout" errors. The configuration works with NT4 on same hardware (tested by swapping harddrives). Hardware: - AST Bravo MS P/60 (BIOS dated 1995) - Lucent/Orinoco WaveLAN/IEEE Linux distribution RedHat 6.2 (Zoot) # uname -rv 2.2.14-5.0 #1 Tue Mar 7 20:53:41 EST 2000 # cardctl -V cardctl version 3.1.18 #dmesg ...... Linux PCMCIA Card Services 3.1.18   kernel build: 2.2.14-5.0 #1 Tue Mar 7 20:53:41 EST 2000   options: [pci] [cardbus] [apm] Intel PCIC probe:   TI 1221 rev 00 PCI-to-CardBus at slot 00:09, mem 0x68000000     host opts [0]: [isa irq] [no pci irq] [lat 16/176] [bus 32/34]     host opts [1]: [isa irq] [no pci irq] [lat 16/176] [bus 35/37]     ISA irqs (default) = 10 polling interval = 1000 ms cs: IO port probe 0x1000-0x17ff: clean. cs: IO port probe 0x0400-0x04ff: clean. cs: IO port probe 0x0a00-0x0aff: clean. cs: memory probe 0xa0000000-0xa0ffffff: clean. eth1: WaveLAN/IEEE, io_addr 0x400, irq 10, mac_address 00:60:1D:22:28:EC eth1: Transmit timeout. # # dump_pirq No PCI interrupt routing table was found. No known PCI interrupt routers were found. # # lspci -v 00:00.0 Host bridge: VLSI Technology Inc 82C592-FC1         Flags: bus master, medium devsel, latency 16 00:01.0 ISA bridge: VLSI Technology Inc 82C593-FC1         Flags: bus master, medium devsel, latency 0 00:09.0 CardBus bridge: Texas Instruments PCI1221         Subsystem: SCM Microsystems: Unknown device 1233         Flags: bus master, medium devsel, latency 16         Memory at <ignored> (32-bit, non-prefetchable)         Bus: primary=00, secondary=20, subordinate=22, sec-latency=176         I/O window 0: 00000000-00000003         I/O window 1: 00000000-00000003         16-bit legacy interface ports at 0001 00:09.1 CardBus bridge: Texas Instruments PCI1221         Subsystem: SCM Microsystems: Unknown device 1233         Flags: bus master, medium devsel, latency 16         Memory at <ignored> (32-bit, non-prefetchable)         Bus: primary=00, secondary=23, subordinate=25, sec-latency=176         I/O window 0: 00000000-00000003         I/O window 1: 00000000-00000003         16-bit legacy interface ports at 0001 # The interrupt counter is not incrementing in /proc/interrupts # cat /proc/interrupts  10: 0 XT-PIC wavelan2_cs And when the error messages go to /var/log/messages, they go in bursts, like after filling up interrupt queue. # tail /var/log/messages Aug 2 23:26:13 kernel: eth1: Transmit timeout. Aug 2 23:27:33 last message repeated 3 times Aug 2 23:28:43 last message repeated 3 times I have tested with various PCIC_OPTS (irq_mode=1 or 0) and CORE_OPTS, but none of them seem to work. Is it simply too old hardware as dump_pirq cannot find anything?

1. Need to determine the PCI interrupt by David Hinds, 2000, Aug 02 1. Strange IRQ info on NT by Sami Pitko, 2000, Aug 03 (_ I think you are out of luck by David Hinds, 2000, Aug 05 2. Feedback: Same kind of problem, works with 3.0.5! by Kelly Murray, 2000, Aug 03

Question: Problems with Lucent Wavelan IEEE and IPv6 Date: 2000, Aug 03 From: Antti Tuominen antti

Hello! Has anyone got a working Wavelan IEEE and IPv6? I just set up a system where I have to nodes with Lucent cards (with Andreas Neuhaus's driver v1.0.1) in ad-hoc mode. I have perfectly functioning IPv4 connection between the two, but when I try using IPv6 over the link nothing works. The sending node is trying to do neighbour discovery but the receiving end never sees the packets. IPv6 ND uses special 33:33:xx:xx:xx:xx (where xx:xx:xx:xx is ff and last 3 octets of the IPv6 address) multicast MAC address and I was wondering if this might be the cause. I've read the driver source and seems like the card has a hardware filter for multicast addresses but when put into either ALLMULTI or PROMISC mode it should receive all multicast packets regardless. I tried both and used ethereal packet analyzer to see where the packets are lost. Well, all I can see is that the packets seem to leave successfully sending node's wvlan0 interface. On the other end all I see is IPv4 packets from other nodes but no IPv6 packets. If anyone has a clue what is wrong, please do tell. Thanks. - Antti Tuominen

Question: Windows-2-Linux communication problems Date: 2000, Aug 06 From: Andrew Fernandes <andrew@fernandes.org>

I have three Lucent WaveLan/IEEE Gold cards, all with firmware-6.06. I use two of the cards in latops under win95 and win2k, and have no problems. My linux box uses the VG469 ISA bridge, and the wvlan_cs driver *seems* to be working correctly. All the iwconfig commands work flawlessly, I can set/get all card parameters, and readling through the output of "pc_debug=65535" shows nothing out of the ordinary occurring. I'm using Red Hat's 2.2.16 kernel, modified with pcmcia-cs-3.1.19. Heck, if I tcpdump the wireless ethernet port, the transmition of the "arp-who-has" messages coincides precisely with the little flashing light on the pc-card. So, as far as I can tell, the card is working just fine. The problem is that linux and the windoze boxen cannot communicate at all. They do not appear in the slightest on each other's radar. I have fiddled very carefully with every combination of ESSID (on or off), encryption, frequency, mode, bit rate, etc., etc., etc. that I can, on both the linux box and the windoze boxen, and the OSes completely ignore each other. Communication is always swell between the windozen. It doesn't matter if I rotate cards among machines. A sample output of iwconfig is as follows. The essid, nickname, frequency, mode... etc. all can be changed quite flawlessly with iwconfig. eth2 IEEE 802.11-DS ESSID:"Studio20" Nickname:"Herbie" Frequency:2.457GHz Sensitivity:1/3 Mode:Ad-Hoc Access Point: 00:00:00:00:00:00 Bit Rate:2Mb/s RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 invalid crypt:0 invalid misc:0 Notice that everything from "link quality" onwards is zero. Those numbers never change, no matter how many hundreds of packets that ifconfig reports have gone out over the interface. Ifconfig always reports zero Rx packets on the interface. On the windows side, the "network spy" utilites refuse, no matter what settings I use, to see or recognize the linux box in any way. I very, very rarely get (from the wvlan_cs driver) wvlan_cs: eth2 Tx timed out! Resetting card messages. These do not fill me with happiness. I don't seem to have interrupt conflicts, though... from the dmesg file: Linux PCMCIA Card Services 3.1.19 kernel build: 2.2.16-4 #1 Thu Aug 3 11:12:13 EDT 2000 options: [pci] [cardbus] [apm] [pnp] PCI routing table version 1.0 at 0xf0d10 PnP: PNP BIOS installation structure at 0xc00fd110 PnP: PNP BIOS version 1.0, entry at f0000:d140, dseg at f0000 Intel PCIC probe: Vadem VG-469 rev 00 ISA-to-PCMCIA at port 0x3e2 ofs 0x00 host opts [0]: none host opts [1]: none ISA irqs (default) = 11 polling interval = 500 ms cs: IO port probe 0x0c00-0x0cff: clean. cs: IO port probe 0x0800-0x08ff: clean. cs: IO port probe 0x0100-0x04ff: clean. cs: memory probe 0x0d0000-0x0dffff: clean. wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4 wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de> wvlan_cs: index 0x01: Vcc 5.0, irq 11, io 0x0100-0x013f wvlan_cs: Registered netdevice eth2 wvlan_cs: Valid channels: 1 2 3 4 5 6 7 8 9 10 11 wvlan_cs: MAC address on eth2 is 00 60 1d f2 cb 55 I have only two hints about what may be going on, but I don't know what they mean. 1) For the 21-July driver release from Lucent (NDIS 3 miniport driver 6.14, firmware 6.06), using a Point-to-Point network with a blank network-id causes the windoze drivers to lock up on both 95 and 2k. However, locking up the windows drivers sometimes makes the linux driver count a few "invalid misc" packets. This is the ONLY way I can get any received packets on the linux driver. 2) I tried using Lucent's wavelan2_cs driver (6.02)... it compiles and installs into the kernel just fine... but after the module initializes, the module hangs. Compling with debugging, and turning on full debugging gives me nothing more than an initialization string in "dmesg". The wvlan_cs driver has no problem getting the wireless ether device up and running... The inability to properly initialize may be a hint that Andy's wvlan_cs driver may only SEEM to be functioning properly... who knows? I'd be happy to provide (a) pizza, or (b) beer, if someone can help me figure this one out. Many thanks, -Andrew.

1. Sad: Ad-Hoc mode by Jean Tourrilhes, 2000, Aug 08 2. More: Silly Lucent by Andrew Fernandes, 2000, Aug 09 3. News: The problem is in Cardmgr! by Andrew Fernandes, 2000, Aug 28 1. More: 'Twas a buffer overflow error... by Andrew Fernandes, 2000, Aug 31

Question: Lucent Wavelan/Orinocco PC card - What is inside ? Date: 2000, Aug 06 From: Martin Prasek NTPT

Anybody know where I can find schematics and/or chipset description of the lucent wavelan/orinoco PC card ?

1. What's Inside? by Glenn Elmore, 2000, Aug 14

Idea: wvlan_cs PPC port/patches Date: 2000, Aug 09 From: David D. Johnson ddj

I have a pair of WaveLan/Orinoco 11mb/s cards, and have been successfully communicating in AdHoc mode, between my 486dx/66 server+firewall machine running Linux 2.0.38+pcmcia-cs-3.1.19 and my PowerBook G3 1998 machine running LinuxPPC 2000, 2.2.17-pre5 kernel and patched pcmcia-cs-3.1.19. It also works with MacOS 9.04 using the Lucent drivers (as opposed to the airport drivers). It took me a long time to realize that I had to set the channel to 3 before it would work between MacOS and linux. Not willing to leave well enough alone, I've started to look into fixing the PPC driver patches so they can be incorporated into the mainline pcmcia-cs code. What I've found is that the wvlan_hcfcfg.h file is using macros under #ifdef __linux__ which assume an x86 platform. The IN_PORT_WORD and OUT_PORT_WORD macros are defined to use inw and outw and the IN_PORT_STRING and OUT_PORT_STRING macros are defined in terms of the IN_PORT_WORD and OUT_PORT_WORD macros. On x86 platforms, this is fine, but clumsy given the availability of insw and outsw (and the insw_ns and outsw_ns macros in include/pcmcia/k_compat.h). On the PPC, the inw and outw macros do byteswapping. This is fine if the code expects it, but in this case the IN_ and OUT_PORT_STRING macros end up reswapping everything. The available driver patch makes up for this by reunswapping everywhere the data should have been treated as byte strings. I am trying to work out a cleaner solution where the __linux__ section of wvlan_hcfcfg.h makes better use of <asm/io.h> and avoids as much swapping back and forth and back again as possible, using insw_ns and outsw_ns for raw data and cpu_to_le16 and le16_to_cpu where it needs to be interpreted as short integers. I haven't got it quite right yet (hangs my machine when a packet comes in), but it does configure properly via iwconfig. But when I can get the same source to work on x86 and PPC, I'd like to have it rolled back into the distribution. So, any comments or objections to my going ahead? Is anyone else working along these same lines? Who should I forward the patches to for review? Thanks, -- ddj Dave Johnson ddj@brown.edu

1. Sounds great to me... by David Hinds, 2000, Aug 09 1. News: Hum, better patch... by Jean Tourrilhes, 2000, Aug 09 2. Angry: Please check PPC patch ! by Jean Tourrilhes, 2000, Aug 09 1. Feedback: Yes, I've checked the PPC patches... by David D. Johnson, 2000, Aug 09 (_ Sad: Oups ! by Jean Tourrilhes, 2000, Aug 09

Question: wvlan_cs and BIOS PnP problems? Date: 2000, Aug 10 From: Matthew GUthaus mobius314

I'm using kernel 2.3.99-pre9, pcmcia-cs-3.1.19, and wvlan_cs. Whenever I disable PnP in my BIOS (on a Sony Z505HS) the PCMCIA services lock up. However, I need PnP disabled to use the ALSA sound drive. I had compiled wavelan2_cs before with this same configuration, but I had to reinstall everything and now that won't compile due to an error that it's trying to "inline __mmdrop" in function mmdrop. A solution to either would be sufficient... Thanks, Matt

1. More: oh and more info... by Matthew GUthaus, 2000, Aug 11 2. Interrupt or IO port probe failure? by David Hinds, 2000, Aug 14 1. Ok: My fault (didn't RTFM) by Matthew GUthaus, 2000, Aug 14

Question: Compaq WL100 WLAN Card - Not detected Date: 2000, Aug 11 From: Talei McLeod talei

Hi, Has anyone had any experience with this card ? I am not sure what parameters I need to specify in the config.opts file. (I feel like I have tried everything). When I insert the card I get a low beep followed by a high beep. If I run cardctl ident I get the correct info, however running cardinfo it says that I have anonymous memory. On a different PC (with Win98 installed) I obtained the following information : PC Card Reader : Memory Range : 0c002000-0c002fff Compaq WLan Card : IRQ : 10 I/O 1800-183f Is this information from a different PC valid for my Linux pc ? I added these lines to my config.opts include memory 0xc002000-0xc002fff include port 0x1800-0x183f Is this correct ??? This did not work for me. Thanks in advance, Talei.

1. Question: Simple question... by Jean Tourrilhes, 2000, Aug 11 1. More: My setup is as follows by Talei McLeod, 2000, Aug 12 2. did it ever work by harry campigli, 2000, Aug 22

Feedback: WebGear Aviator2.4 Pro? Date: 2000, Aug 11 From: Justin Gaither jgaither

I was wondering if it is worth it to upgrade the firmware of my Aviator2.4 cards to Aviator2.4pro? It seems WebGear is stopping support for the Aviator2.4. Anyone got any comments?

1. News: Aviator2.4 and 2.4Pro by Jean Tourrilhes, 2000, Aug 11

Sad: Can't get RayLink cards to connect Date: 2000, Aug 11 From: Richard Smith smithbone

I have 2 raylink cards that I can't seem to make connect. Both claim that they are starting a network. I cranked up debug to level 5 and as far as I can tell the configurations are identical. They are in the same room about 20ft apart. The card reports the noise level as 53 and 54. Any ideas? For what its worth I can't get them to connect under windows 98 or windows 95 either.

Question: wavelan turbo 11 mb will not answer ioctl calls Date: 2000, Aug 13 From: Mathieu Lacage mathieu

hi all, I have been trying to get my wavelan card for a few days now but could not suceed. I have kernel 2.2.14 patched ext3 and pcmcia-cs-something-19 Ok, so, the card is recognized by the pcmcia servuices (2 high beeps). It even works at work: there is a small mac who has an airport and the card seems to be configured by default to work with this kind of network. So, pump -i wvlan0 works there because it can talk to the airport which assigns my card an IP address. I can then ping the netwrok. The pb is that my real network uses another set of settings and I want to specify them through the wireless-tools package They seem to create a socket and expect the card to be behind this socket. They make ioctl calls to the socket, obviously expecting the driver's ioctl callback to answer. The point is that the driver's ioctl callback is NEVER called (I enabled debugging and even added some of mine). The open callbacks of the driver are however called (debugging says so) I have traced the driver behaviour till the attach call but could not go further. Any idea to help me figure out why his f*** ioctl stuff is not called ? Mathieu

1. Question: CONFIG_NET_RADIO by Jean Tourrilhes, 2000, Aug 14 2. A guess: kernel configuration? by David Hinds, 2000, Aug 14

Question: Receive interrupt does not seem to be incrementing properly Date: 2000, Aug 15 From: Richard Smith smithbone

Using the test_network script I get... "Recive interrupt does not seem to be incrementing properly." What exactly does this mean?

1. Some context would help by David Hinds, 2000, Aug 15 (_ Re: Some context would help by Richard Smith, 2000, Aug 15 (_ Not sure if it is an interrupt issue; gateway set wrong? by David Hinds, 2000, Aug 15 1. Re: Not sure if it is an interrupt issue; gateway set wrong? by Richard Smith, 2000, Aug 15 2. Raylink problem solved.. by Richard Smith, 2000, Aug 15 1. Configuration files by David Hinds, 2000, Aug 15

Question: Compaq card detected but no wlan0-device Date: 2000, Aug 18 From: Per Olesen polesen

Hi I'm trying to get a Compaq WLAN100 PCMCIA kort working under Linux and I have nearly made it :-) The card is detected correctly and i hear 2 of the high beeps at insertion. But when I do ifconfig only loopback device is shown and when I look in /var/log/messages I see: Aug 16 14:33:39 polesen cardmgr[4209]: executing: './wlan-ng start wlan0' Aug 16 14:33:39 polesen cardmgr[4209]: + message=dot11req_mibset Aug 16 14:33:39 polesen cardmgr[4209]: + mibattribute=dot11DesiredSSID=WLAN_PRISM2 Aug 16 14:33:39 polesen cardmgr[4209]: + resultcode=success Aug 16 14:33:39 polesen cardmgr[4209]: + message=dot11req_associate Aug 16 14:33:39 polesen cardmgr[4209]: + peerstaaddress=no_value Aug 16 14:33:39 polesen cardmgr[4209]: + associatefailuretimeout=no_value Aug 16 14:33:39 polesen cardmgr[4209]: + cfpollable=no_value Aug 16 14:33:39 polesen cardmgr[4209]: + cfpollreq=no_value Aug 16 14:33:39 polesen cardmgr[4209]: + privacy=no_value Aug 16 14:33:39 polesen cardmgr[4209]: + listeninterval=0 Aug 16 14:33:39 polesen cardmgr[4209]: + resultcode=success Aug 16 14:33:39 polesen cardmgr[4209]: + usage: ifup <device name> It seems like the name "wlan0" is not known :-( I'm running: Kernel: 2.2.14-0.5 PCMCIA: pcmcia-cs-3.1.8 wlan: linux-wlan-ng-0.1.7 I have tried adding an alias line for "wlan0" in /etc/conf.modules but with no success. What to do?

1. The interface is fine; the problem is with ifup by David Hinds, 2000, Aug 18

Question: Power management? Date: 2000, Aug 19 From: Brian Mays brian

Are there any plans to provide support for iwconfig's power management configuration for wireless cards in the /etc/pcmcia/wireless script? Thanks, - Brian

1. Ok: With wvlan_cs by Jean Tourrilhes, 2000, Aug 23

Question: Peer-to-Peer w/wvlan_cs or wavelan2_cs drivers Date: 2000, Aug 20 From: Craig Nelson cnelso007

Windows 2000 doesn't seem tolike the older versions of the wavelan drivers (I bluescreened like crazy!). Therefore, I updated my cards with the latest firmware, and installed the latest drivers. Between Windows hosts, everything works fine. But, I can't seem to get Linux to work in "peer to peer" mode. I've tried both the lucent and wvlan_cs drivers to no avail. From the W2k console, I can see that I'm using channel 10. I set the channel to 10 with iwconfig, but still no go.. Anyone have success with Linux-W2k communication with the latest drivers/firmware?

1. Question: More info... by Jean Tourrilhes, 2000, Aug 24 (_ News: peer-to-peer vs. ad-hoc by Andrew Fernandes, 2000, Sep 07

Note: Encryption using wavelan2_cs Date: 2000, Aug 20 From: Sami Pitko spitko

I did get everything working with Ad-Hoc network against laptop running NT4 WKS, so I decided to add encryption. Everytime when I added "enable_encryption=y key_1=\"xxxxx\"" to config.opts, the card initialization failed. "Failed" means network did not work, no errors on dmesg. Then I found that when doing "/etc/rc.d/init.d/pcmcia start" (yes, it is RedHat 6.2) twice, it worked just fine. I even changed (dirty hack) the init.d/pcmcia script to be: ...     start)         $0 startorig         sleep 2         $0 startorig         EXITCODE=$?         ;;     startorig)         echo -n "Starting PCMCIA services:" ... Any thoughts of why it is not starting up properly in the first time (increasing timeout, where?), but works fine if started twice. wavelan2_cs version is: # strings wavelan2_cs.o | grep wavelan2_cs.c wavelan2_cs.c 6.00 03/02/2000 11:00:00 (Lucent Technologies) Here is part of messages (notice the delay of 2 seconds before starting pcmcia second time): Aug 19 23:18:27 kernel: Linux PCMCIA Card Services 3.1.18 Aug 19 23:18:27 kernel: kernel build: 2.2.14-5.0 #1 Tue Mar 7 20:53:41 EST 2000 Aug 19 23:18:27 kernel: options: [pci] [cardbus] [apm] Aug 19 23:18:27 kernel: Intel PCIC probe: Aug 19 23:18:27 kernel: Vadem VG-469 rev 00 ISA-to-PCMCIA at port 0x3e0 ofs 0x00 Aug 19 23:18:27 kernel: host opts [0]: [ext mode] [isa buf] Aug 19 23:18:27 kernel: host opts [1]: [ext mode] [isa buf] Aug 19 23:18:27 kernel: ISA irqs (scanned) = 3,4,10,12 polling interval = 1000 ms Aug 19 23:18:27 cardmgr[2130]: starting, version is 3.1.18 Aug 19 23:18:27 cardmgr[2130]: watching 2 sockets Aug 19 23:18:27 kernel: cs: IO port probe 0x1000-0x17ff: clean. Aug 19 23:18:27 kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f Aug 19 23:18:27 kernel: cs: IO port probe 0x0a00-0x0aff: clean. Aug 19 23:18:28 cardmgr[2130]: initializing socket 0 Aug 19 23:18:28 kernel: cs: memory probe 0x0c0000-0x0cffff: excluding 0xc0000-0xc7fff Aug 19 23:18:28 kernel: cs: memory probe 0x0d4000-0x0fffff: excluding 0xf0000-0xfffff Aug 19 23:18:28 cardmgr[2130]: socket 0: Lucent Technologies WaveLAN/IEEE Aug 19 23:18:28 cardmgr[2130]: executing: 'modprobe wavelan2_cs port_type=3 microwave_robustness=y station_name=street\ address enable_encryption=y key_1=\"xxxxx\"' Aug 19 23:18:30 cardmgr[2154]: starting, version is 3.1.18 Aug 19 23:18:30 cardmgr[2154]: watching 2 sockets Aug 19 23:18:30 cardmgr[2154]: could not adjust resource: IO ports 0x1000-0x17ff: Device or resource busy Aug 19 23:18:30 cardmgr[2154]: could not adjust resource: IO ports 0x100-0x4ff: Device or resource busy Aug 19 23:18:30 cardmgr[2154]: could not adjust resource: memory 0xc0000-0xfffff: Input/output error Aug 19 23:18:30 cardmgr[2154]: could not adjust resource: memory 0x60000000-0x60ffffff: Input/output error Aug 19 23:18:30 cardmgr[2154]: could not adjust resource: memory 0xa0000000-0xa0ffffff: Input/output error Aug 19 23:18:30 cardmgr[2154]: could not adjust resource: IO ports 0xa00-0xaff: Device or resource busy Aug 19 23:18:30 cardmgr[2154]: initializing socket 0 Aug 19 23:18:30 cardmgr[2154]: socket 0: Lucent Technologies WaveLAN/IEEE Aug 19 23:18:30 kernel: eth2: WaveLAN/IEEE, io_addr 0x100, irq 10, mac_address 00:60:1D:22:28:A4 Aug 19 23:18:30 cardmgr[2154]: executing: './network start eth2'

Question: ORiNOCO Outdoor Router Client Supported? Date: 2000, Aug 21 From: Richard Smith smithbone

My ISP now offers wireless service using the wavelan2 cards. The geographics between me and thier antenna should allow me to get service. They claim, however, you have to use the outdoor router client with a key that they issue to log onto thier network. I looked over the wavelan site and I don't see any mention of an outdoor router client for Linux. I see that the wavelan2 driver supports WEP is this the same thing? or am I just in the dark until someone produces a linux client?

1. Sad: no way by Marcio Gomes, 2000, Aug 26

Question: Has anyone made a COMPAQ WL200 or 100 finally work?? Date: 2000, Aug 22 From: harry campigli harryc

hi all, The Compaq WL200 pci card will come up ok in the end with the modules and all will look good with routing, pcmcia modules ect will all work. However the device will not associate. I have tried all options, but can't figure out how to make 2 identical linux systems (in every way) actually talk with these cards. the error is frame dropped because its not associated. so my question now is........ Has any one made a WL200 work as an ap or bss ? If so can I please please have a copy of your wglan-ng.opts file to see what mibs you used? harry@gpssys.com

1. Ok: Compaq WL200 and WL100 working!! by Jean Luc Gorinas, 2000, Aug 29

Warning: problems with rarp and wavelan silver card Date: 2000, Aug 26 From: Blorp Blorp blorp

The problem is that the check in for whether or not to encapsulate the packet doesn't work properly if either byte of the packet type is > 127 (signed versus unsigned bug). I wasted an awful lot of time today tracking this down... Here's a patch to fix it. BTW, what is the significance of the magic number 1500? I suspect none... shouldn't it be a more meaningful value? *** wvlan_cs.c~ Fri Aug 25 18:32:37 2000 --- wvlan_cs.c Fri Aug 25 18:36:53 2000 *************** int wvlan_tx (struct sk_buff *skb, struc *** 2053,2059 **** struct net_local *local = (struct net_local *)dev->priv; unsigned long flags; int rc, len; ! char *p; DEBUG(DEBUG_CALLTRACE, "-> wvlan_tx(%s)\n", dev->name); --- 2053,2059 ---- struct net_local *local = (struct net_local *)dev->priv; unsigned long flags; int rc, len; ! unsigned char *p; DEBUG(DEBUG_CALLTRACE, "-> wvlan_tx(%s)\n", dev->name);

1. Thanks for the patch... by David Hinds, 2000, Aug 26

Question: WaveLAN Gold and RG-1000 gateway Date: 2000, Aug 26 From: Chris Hill cnh

Hi, Anyone got any advice/experience with getting a WaveLAN Gold card to work with the Orinoco RG-1000 gateway. I have a setup working great under Win98 but under RH6.2 (2.2.14-05) I can't seem to get the card and the RG to see each other. Have tried both the GPL wvlan and the Lucent wavelan2. I have had some success with local ping to the Gold card but I suspect the card is failing to see/handshake ok with the RG-1000. Can't find much on the net re. RG-1000 and Linux. Thanks, Chris

1. More: RG-1000 == Airport by Jean Tourrilhes, 2000, Aug 28

Feedback: 2 X PCI + ISA or 2 x PCI, with orinoco pcmcia silver problems Date: 2000, Aug 26 From: Marcio Gomes Marcio

0) If i remove one card (PCMCIA ) the other works fine. all tests are under : Kernel 2.2.16, wireless tools X.20 and pcmcia package x.19 Test 01 : With 1 X PCI->PCMCIA and 1X ISA->PCMCIA driver wavelan2_cs 6.02 I reproduce the list item 11.2 : May 18 03:28:49 xd kernel: eth3: WaveLAN/IEEE, HCF failure: "Error code 131" May 18 03:28:49 xd cardmgr[7886]: get dev info on socket q failed: No such device Test 02 : 2Xpci->PCMCIA 02.1 ) Wavelan2_cs driver Aug 26 16:57:13 XX kernel: PCI routing table version 1.0 at 0xf0d00 Aug 26 16:57:13 XX kernel: Intel PCIC probe: Aug 26 16:57:13 XX kernel: TI 1225 rev 01 PCI-to-CardBus at slot 00:09, mem 0x68000000 Aug 26 16:57:13 XX kernel: host opts [0]: [pci only] [pci irq 12] [lat 32/176] [bus 32/34] Aug 26 16:57:13 XX kernel: host opts [1]: [pci only] [pci irq 12] [lat 32/176] [bus 35/37] Aug 26 16:57:13 XX kernel: PCI card interrupts, PCI status changes Aug 26 16:57:13 XX kernel: TI 1225 rev 01 PCI-to-CardBus at slot 00:0b, mem 0x68002000 Aug 26 16:57:13 XX kernel: host opts [0]: [pci only] [pci irq 11] [lat 32/176] [bus 38/40] Aug 26 16:57:13 XX kernel: host opts [1]: [pci only] [pci irq 11] at 32/176] [bus 41/43] Aug 26 16:57:13 XX kernel: PCI card interrupts, PCI status changes Aug 26 16:57:13 XX cardmgr[229]: starting, version is 3.1.19 Aug 26 16:57:13 XX cardmgr[229]: watching 4 sockets Aug 26 16:57:13 XX kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff Aug 26 16:57:13 XX kernel: cs: IO port probe 0x0800-0x08ff: clean. Aug 26 16:57:13 XX kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x290-0x297 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7 Aug 26 16:57:13 XX kernel: cs: IO port probe 0x0a00-0x0aff: clean. Aug 26 16:57:14 XX cardmgr[229]: initializing socket 0 Aug 26 16:57:14 XX kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. Aug 26 16:57:14 XX cardmgr[229]: socket 0: Lucent Technologies WaveLAN/IEEE Aug 26 16:57:14 XX cardmgr[229]: executing: 'modprobe wavelan2_cs port_type=3' Aug 26 16:57:14 XX kernel: eth1: WaveLAN/IEEE, io_addr 0x100, irq 12, mac_address 00:60:1D:23:DD:E0 Aug 26 16:57:14 XX cardmgr[229]: executing: './network start eth1' Aug 26 16:57:14 XX cardmgr[229]: + cat: /var/lib/pcmcia/scheme: No such file or directory Aug 26 16:57:14 XX cardmgr[229]: initializing socket 2 Aug 26 16:57:14 XX cardmgr[229]: socket 2: Lucent Technologies WaveLAN/IEEE Aug 26 16:57:15 XX kernel: eth2: WaveLAN/IEEE, HCF failure: "Error code 256" Aug 26 16:57:15 XX cardmgr[229]: get dev info on socket 2 failed: No such device ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 02.2 ) wlan_cs Driver. Reproduce list item 11.0 wvlan0 IEEE 802.11-DS ESSID="test" Nickname:"dev-1" Frequency:2.422GHz Sensitivity:1/3 Mode:Ad-Hoc .... ...... wvlan1 IEEE 802.11-DS ESSID="" Frequency:52Mhz Sensitivity:0/3 Mode:Ad-Hoc Access Point: FF:BF:01:00:01:01 Bit Rate=0kb/s RTS thr=0 B Fragment thr=0 B the 02.2 test is only to compile all informations here, i know, wlan_cs do not support multiples wavelan. Any idea ? Thanks, Marcio Gomes

1. Sad: wvlan_cs module parameters by Jean Tourrilhes, 2000, Aug 28 (_ not work by Marcio Gomes, 2000, Sep 30

Question: Problems setting ESSID on airo_cs Date: 2000, Aug 27 From: aheitnerATandrewDOTcmuDOTedu

ibm tp600, debian woody, 2.2.16, pcmcia-cs 3.1.17 (i know i know should get the latest). when i run 'iwconfig eth0' it tells me 'wireless extensions not supported'. If i do a 'iwconfig eth0 essid "FOO"' i get something like 'SIOCSESSID: option not supported'. anyone know anything about this? is this an airo_cs problem, or am i not setting things up right?

1. Sad: Complain to Ben by Jean Tourrilhes, 2000, Aug 28

Question: Wavelan IEEE 6.02 driver compatibility Date: 2000, Aug 28 From: Mike jabbera

I don't suppose anyone has any idea if any progress has been made making wvlan_cs compatable with the new Peer-Peer mode in the windows driver?

1. News: Try latest driver by Jean Tourrilhes, 2000, Oct 26

Xircom Wireless Ethernet Adapter (CISCO 340 Aironet Series) Date: 2000, Sep 04 From: TeeJin TeeJin

Need help urgently here. Xircom will be launching its Wireless Adapters using the CISCO AIRONET 340 / 4800 series card. I have tried using CISCOs Aironet 4800 pcmcia cards and it worked perfectly fine. However upon plugging in the Xircomised version , cardmgr reports unsupported card, detect product as Xircom Wireless adapter, function 6 (network). Cardctl ident reports manfid: 0x0150, 0x0007 I have tried adding an entry into "config" file /etc/pcmcia and binding "airo_cs" driver to it but it does not work. Is anyone familiar with these drivers? Any help is deeply appreciated. Rgds TeeJin

Sad: Lucent WaveLAN/IEEE Silver card does not obtain IP address form Access Point Date: 2000, Sep 21 From: Charlie ianc

Hi everyone, I'm trying to connect a Lucent WaveLAN/IEEE sliver pcmcia card to my Access Point. Running iwconfig, I can see my Access Point and its associated MAC address. However, the Access Point will not lease out an IP address either statically or via DHCP. The Lucent and Access Point are in the same IP range 192.168.5.1 (AP) 192.168.5.8 (Lucent WaveLAN) netmask 255.255.255.0 On the Access Point side, I can see the MAC address of the of the Lucent card. Any help would be great. By the way, I'm using the wvlan_cs driver with the card. P.S. I also have an Orinoco base that I'd like to connect to. Any suggestions would be great.

Angry: No Lucent(Grrr) PCI Adapter found Date: 2000, Oct 06 From: Alexander Bögl alex43

I have tested the Lucent PCI - PCMCIA Bridge on 5 PCs, but it runs only on the newer one, on all other the card can't be find in the /proc/pci or at boot time of the PC (BIOS). BIOS updates dosn't help to, it seems do be only recognize by newer Mainboards. The PCI Card is the Standart Lucent Adapter (based on TI1225). Sorry, my english is a bit broken, if you need more Information, please ask me. alexander.boegl@comteam.at comteam IT - Solutions Mozartstr. 22 3300 Amstetten Austria

1. Lucent documents this by David Hinds, 2000, Oct 06 (_ Sad: My Mainboards are PCI 2.2 compilant! by Alexander Bögl, 2000, Oct 06

Question: Something instead of Orinoco Outdoor Router Client. Date: 2000, Oct 29 From: Stefan Holmer roofa

My ISP uses Orinoco Outdoor Router Client (CQI) to let me communicate with the router, and it wants me to send a correct License Key and configure the CQI with the correct Pass Phrase and channel frequency (1-10) and so on. Now I wonder if there are any program for this in linux and where I get it. If you know how to help me, or know that it's impossible, please mail me now! Thanks - Stefan Holmer

Question: Linux Support for INM Hi Rate Wireless Lan PC Card Date: 2000, Nov 16 From: Michael H. Frey mhfrey

I was wondering if there is Lunix pcmcia support for the IBM High Rate Wireless LAN PC Card, Version 01.01. This appears to be an OEM pc-card from Lucent (label on back), after Lucent there is a part number PC24E-H-FC, but I am not sure if this is IBM's or Lucent's. The Linux cardctl ident command gives the following: Socket 0: product info: "IBM Corporation", IBM High Rate Wireless LAN PC Card", "Version 01.01","" manfid: 0x0156, 0x0002 function: 6 (network) Any useful advice or directions to get this card working would greatly appreciated.

1. It should work by David Hinds, 2000, Nov 16 (_ More: Still not working. by Michael H. Frey, 2000, Nov 17

Question: 100 mw pcmcia prismII cards Date: 2000, Nov 21 From: hd1531

Does anyone know of any prism II PCMCIA card manufacturers with output power of 100 mw and non-intergrated antenna??? Thanks.

Question: Interoperability between Farallon SkyLINE and ORiNOCO Cards using "Peer-to-Peer" Date: 2000, Nov 30 From: Yuji Minegishi mine

Hello, I have a question regarding "Peer-to-Peer" communications using Lucent's ORINOCO card. I can't get it to communicate with Farallon SkyLINE 11Mb (PN473) which is set to "Ad-Hoc" mode. This leads to another question. Why is it that the configuration parameters for "Peer-to-Peer" in the ORINOCO cards different from that of Farallon's configuration paramters for "Ad-Hoc" mode? Farallon (and most Intersil based cards I have tried) usually lets you set a channel in Ad-Hoc mode and the SSID parameter has no effect. However the ORINOCO card doesn't let you set channels and only lets you set an SSID (the default channel seems to be 10 if it doesn't find another "compatible" card running in Peer-to-Peer mode with the same SSID). I tried setting up the Farallon card to channel 10 and I also set the SSID to the same value as the ORINOCO card but nothing happens. Is "Ad-Hoc" in Intersil based cards the same as "Peer-to-Peer" in Lucent based cards? Please help. By the way, I've tried this with Farallon and SAMSUNG cards and experienced the same results.

[ Add Message ]  to: "PCMCIA Wireless Network Adapter Issues"

[ Members ]  [ Subscribe ]  [ Admin Mode ] 
[ Show Frames ]  [ Help for HyperNews at pcmcia-cs.sourceforge.net 1.10 ]