Use this page to discuss wireless network adapter issues. Before posting, be sure you've checked the Linux Wireless LAN Howto, as well as any relevant sections of the PCMCIA-HOWTO, such as: Particularly useful bits of information to post include your laptop's make and model; the type(s) of card(s) you are using; and, of course, any relevant system log messages.

Messages Inline: 0 1

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

Note Re: CDPD with the Sierra Wireless AirCard

Re: Question CDPD with the Sierra Wireless AirCard (dkap)
Date: 2000, Jan 24
From: Roy Murphy Royster

I don't think that the Sierra Wireless Aircard 300 has been made to work. Jeff Schoby's patches are for the 200 and the 210.

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

Note IRQ troubles...

Re: Question Netwave AirSurfer Plus and DELL Inspiron 7500 (Ronny Bremer)
Date: 2000, Feb 25
From: Jean Tourrilhes jt

	Try to make the driver use another IRQ (using exclude in config.opt).
	And try to give more info in your bug reports.

	Jean

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!

News Enabling roaming...

Re: Ok WaveLAN PCMCIA works with 3.0.14 (Ed Swierk)
Date: 2000, Feb 24
From: Jean Tourrilhes jt

	Hi,

	With kernel 2.2.14+ and Pcmcia 3.1.2+, the "official"
way to do this is :
		iwconfig ethX mode Managed
	To disable roaming :
		iwconfig ethX mode Ad-Hoc

	As a side note, I did some extensive changes to the
Pcmcia driver (try to get it SMP compliant), which will be
going in 3.1.12. I can't test the roaming support, so somebody
will have to tell me if I did goof up...
	Thanks...

	Jean

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

None 3.1.8 can't figure out the interrupt routing

Re: Question lucent ieee turbo pci adapter (Bob Cohen)
Date: 2000, Jan 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Try again with pcmcia-cs-3.1.9; it should be able to deduce the PCI
interrupt assignment for the TI 1225 bridge.  Then set:

    PCIC_OPTS="irq_mode=0"

which tells the i82365 driver that the TI 1225 does not have any ISA
interrupt connections.

-- Dave

Sad didn't work

Re: None 3.1.8 can't figure out the interrupt routing (David Hinds)
Date: 2000, Jan 31
From: Bob Cohen bonobob

That didn't work. Looks like the minimal set of options necessary to get the wavelan module to load is:

 PCIC_OPTS="pci_int=1 irq_mode=0 pci_csc=1 pci_irq_list=7,7"

With this, the module loads, but again interrupts don't work (both card services, and the driver's interrupts). Also, irq7 seems to be the only one that works. How do you find out what irqs are valid for PCI? If I don't specify pci_irq_list, it doesn't work, so obviously probing isn't working.

This may be a red herring, but my bios has a field "reserve irq5", which allows irq5 to be devoted to "legacy isa devices" (whatever that means). I tried turning this on, and using isa interrupts - this didn't work either.

None Fixed...

Re: Sad didn't work (Bob Cohen)
Date: 2000, Feb 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The interrupt routing problem is fixed in the latest (3.1.11) drivers.

-- Dave

Question "3.1.8 can't figure out the interrupt routing"

Re: None 3.1.8 can't figure out the interrupt routing (David Hinds)
Date: 2000, Feb 18
From: Gerald Richter richter

I have the same problem with a lucent WaveLan IEEE and a CL 6729 PCI Controller. I can access the card, but no interrupts are coming thru. The lspci shows that

"pin A routed to IRQ 11"

but I am not able to set anything to irq 11. When I don't specify an irq, the irq of the wvlan_cs driver is set to 5 and no irq is comming thru (/proc/interrupts shows 0).

What are the correct irq that the wvlan_cs driver should use, how can I debug this problem further?

Thanks for any help

Gerald

None This is a somewhat rare configuration

Re: Question "3.1.8 can't figure out the interrupt routing" (Gerald Richter)
Date: 2000, Feb 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The current PCMCIA drivers can't handle the CL 6729 PCI card properly;
the drivers are not set up to allow use of PCI interrupts with this
bridge type.  Fixing this is in my queue of things to do, but I have
not gotten to it yet.

-- Dave

None RE: This is a somewhat rare configuration

Re: None This is a somewhat rare configuration (David Hinds)
Date: 2000, Feb 18
From: Gerald Richter richter

Hi,
>
> The current PCMCIA drivers can't handle the CL 6729 PCI card properly;
> the drivers are not set up to allow use of PCI interrupts with this
> bridge type.  Fixing this is in my queue of things to do, but I have
> not gotten to it yet.
>
thanks for your fast answer. Is there a PCI card (which chip should it
contain?)  that you know that handle interrupts correctly, or is this a
general problem with all PCI PCMCIA bridges?

Gerald

None It's true for most bridges like this

Re: None RE: This is a somewhat rare configuration (Gerald Richter)
Date: 2000, Feb 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

At the moment, there is no support for PCI-to-PCMCIA (16-bit-only)
bridges that are only wired for PCI interrupts.  PCI-to-CardBus
bridges are ok.

The only exception is the TI PCI1031 PCI-to-PCMCIA bridge, which is
more like a CardBus bridge with some of the CardBus support disabled.
The 3.1.11 drivers try to support this (I don't actually have one, so
I'm working with someone to verify that this works).

-- Dave

Idea Twosamples here...

Re: None 3.1.8 can't figure out the interrupt routing (David Hinds)
Date: 2000, Feb 25
From: Jean Tourrilhes jt

	David,

	I've got two samples here (PCI). I could lend you one
for debugging if you need. I also have one ISA sample which
work fine with 3.1.11 (but not with 2.3.47 ;-).
	By the way, I plan sooner or later to get the PCI
bridges into Linux box, so I'm interested as well...

	Regards,

	Jean

Feedback same problem for me!

Re: Question lucent ieee turbo pci adapter (Bob Cohen)
Date: 2000, Mar 26
From: Guillaum Dallaire gd

Hi,

I also have a PCI TI1225 from wavelan and the wavelan driver load, then I get :

wvlan_cs: wvlan0 Tx timed out! Resetting card

nothing to do, the card isn't usable!

(I use 3.11.13, kernel 2.2.14)

what finally happen ?

thanks!!

More Contact Andy...

Re: Feedback same problem for me! (Guillaum Dallaire)
Date: 2000, Mar 27
From: Jean Tourrilhes jt

	Please send a bug report to Andy. He will probably ask
you to enable debugging in the driver to know exactly what is
happening...

	Jean

None PCI interrupt routing?

Re: Feedback same problem for me! (Guillaum Dallaire)
Date: 2000, Mar 27
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Can you post the PCMCIA startup messages from your system log?  This
could just be an interrupt routing problem.

-- Dave

More pcmcia startup

Re: None PCI interrupt routing? (David Hinds)
Date: 2000, Mar 30
From: Guillaum Dallaire gd

Hi,

Here is the log :

ar 27 14:09:33 localhost pcmcia: Starting PCMCIA services:

Mar 27 14:09:34 localhost pcmcia:  modules
Mar 27 14:09:34 localhost kernel: Linux PCMCIA Card Services 3.1.13 
Mar 27 14:09:34 localhost kernel:   kernel build: 2.2.14 #4 SMP lun mar 13 05:09:51 EST 2000 
Mar 27 14:09:34 localhost kernel:   options:  [pci] [cardbus] 
Mar 27 14:09:34 localhost kernel: PCI routing table version 1.0 at 0xf0b40 
Mar 27 14:09:34 localhost kernel:   unknown PCI interrupt router 10b9:1533 
Mar 27 14:09:34 localhost kernel: Intel PCIC probe:  
Mar 27 14:09:34 localhost kernel:   TI 1225 PCI-to-CardBus at slot 00:0a, mem 0x68000000 
Mar 27 14:09:34 localhost kernel:     host opts [0]: [isa irq] [no pci irq] [lat 32/176] [bus 32/34] 
Mar 27 14:09:34 localhost kernel:     host opts [1]: [isa irq] [no pci irq] [lat 32/176] [bus 35/37] 
Mar 27 14:09:34 localhost kernel:     ISA irqs (default) = 3,4,5,7,9,11,12,15 polling interval = 1000 ms 
Mar 27 14:09:34 localhost pcmcia:  cardmgr.
Mar 27 14:09:34 localhost rc: Starting pcmcia succeeded
Mar 27 14:09:34 localhost cardmgr[343]: starting, version is 3.1.13
Mar 27 14:09:34 localhost cardmgr[343]: watching 2 sockets
Mar 27 14:09:34 localhost kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Mar 27 14:09:34 localhost kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x290-0x297 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7 
Mar 27 14:09:34 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Mar 27 14:09:34 localhost cardmgr[343]: initializing socket 0
Mar 27 14:09:34 localhost kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. 
Mar 27 14:09:34 localhost cardmgr[343]: socket 0: Lucent Technologies WaveLAN/IEEE Adapter
Mar 27 14:09:34 localhost cardmgr[343]: executing: 'insmod /lib/modules/2.2.14/pcmcia/wvlan_cs.o port_type=3 channel=3 station_name=dev-1'
Mar 27 14:09:34 localhost kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4 
Mar 27 14:09:34 localhost kernel: wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de> 
Mar 27 14:09:35 localhost kernel: wvlan_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f 
Mar 27 14:09:35 localhost kernel: wvlan_cs: Registered netdevice wvlan0 
Mar 27 14:09:35 localhost kernel: wvlan_cs: Valid channels: 1 2 3 4 5 6 7 8 9 10 11  
Mar 27 14:09:35 localhost kernel: wvlan_cs: MAC address on wvlan0 is 00 60 1d 03 8a df  
Mar 27 14:09:35 localhost cardmgr[343]: executing: './network start wvlan0'
Mar 27 14:09:35 localhost cardmgr[343]: initializing socket 1
Mar 27 14:09:35 localhost cardmgr[343]: socket 1: Anonymous Memory
Mar 27 14:09:36 localhost cardmgr[343]: executing: 'insmod /lib/modules/2.2.14/pcmcia/memory_cs.o'
Mar 27 14:09:36 localhost kernel: memory_cs: mem0: anonymous: unknown size 
Mar 27 14:09:36 localhost cardmgr[343]: executing: './memory start mem0'

None The "unknown interrupt router" problem

Re: More pcmcia startup (Guillaum Dallaire)
Date: 2000, Mar 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> Mar 27 14:09:34 localhost kernel: PCI routing table version 1.0 at 0xf0b40 
> Mar 27 14:09:34 localhost kernel:   unknown PCI interrupt router 10b9:1533 

This is the crucial "bad thing".  This adapter card uses a PCI
interrupt to communicate with the system.  The Linux kernel does not
know how to deduce the interrupt routing for your host bridge, which
appears to be an Acer M1533.  Without that information, the drivers
report "no pci irq", and can't set up interrupt handling correctly.

I've contacted Acer to find out if I can get a datasheet for this host
bridge.

-- Dave

Sad I see the same thing..

Re: Question lucent ieee turbo pci adapter (Bob Cohen)
Date: 2000, Apr 10
From: Mark Geib geib

I help with a school installing a wireless network, all Linux. We just received some new machines and the WaveLan PCI adapters (20 of them). I have the same problem.

I will do whatever I can to help resolve this issue, loan cards and adapters, etc... just let me know.

Mark.

None This is mostly fixed; if not, then tell me more

Re: Sad I see the same thing.. (Mark Geib)
Date: 2000, Apr 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

This problem has already been fixed for most configurations.

You should try the current (3.1.13) PCMCIA driver package, and specify
PCIC_OPTS="irq_mode=0" in /etc/sysconfig/pcmcia.  If the problem
persists, then I need a lot more information about your specific
situation.  System log messages in particular.

-- Dave

Sad no luck, here is more info..

Re: None This is mostly fixed; if not, then tell me more (David Hinds)
Date: 2000, Apr 12
From: Mark Geib geib

No luck as yet. I set irq_mode=0. But now whenever I
insert the WaveLan card I hear one beep and the system
hangs until I remove the card.

Here is the output from messages.log, dmes, and an lspci.

Thanks ahead of time...

tail of messages.log from /var/log

Apr 12 11:31:30 localhost kernel: PCI: Probing PCI hardware 
Apr 12 11:31:30 localhost kernel: Linux NET4.0 for Linux 2.2 
Apr 12 11:31:30 localhost kernel: Based upon Swansea University Computer Society NET3.039 
Apr 12 11:31:30 localhost kernel: NET4: Unix domain sockets 1.0 for Linux NET4.0. 
Apr 12 11:31:30 localhost kernel: NET4: Linux TCP/IP 1.0 for NET4.0 
Apr 12 11:31:30 localhost kernel: IP Protocols: ICMP, UDP, TCP, IGMP 
Apr 12 11:31:30 localhost kernel: TCP: Hash tables configured (ehash 65536 bhash 65536) 
Apr 12 11:31:30 localhost kernel: Initializing RT netlink socket 
Apr 12 11:31:30 localhost kernel: Starting kswapd v 1.5  
Apr 12 11:31:30 localhost kernel: Detected PS/2 Mouse Port. 
Apr 12 11:31:30 localhost kernel: Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled 
Apr 12 11:31:30 localhost kernel: pty: 256 Unix98 ptys configured 
Apr 12 11:31:30 localhost kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.9) 
Apr 12 11:31:30 localhost kernel: Real Time Clock Driver v1.09 
Apr 12 11:31:30 localhost kernel: RAM disk driver initialized:  16 RAM disks of 4096K size 
Apr 12 11:31:30 localhost kernel: PCI_IDE: unknown IDE controller on PCI bus 00 device f9, VID=8086, DID=2411 
Apr 12 11:31:30 localhost kernel: PCI_IDE: not 100% native mode: will probe irqs later 
Apr 12 11:31:30 localhost kernel:     ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio 
Apr 12 11:31:30 localhost kernel:     ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio 
Apr 12 11:31:30 localhost kernel: hda: Maxtor 90651U2, ATA DISK drive 
Apr 12 11:31:30 localhost kernel: hdc: SAMSUNG CD-ROM SN-124, ATAPI CDROM drive 
Apr 12 11:31:30 localhost kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 
Apr 12 11:31:30 localhost kernel: ide1 at 0x170-0x177,0x376 on irq 15 
Apr 12 11:31:30 localhost kernel: hda: Maxtor 90651U2, 6149MB w/512kB Cache, CHS=784/255/63 
Apr 12 11:31:30 localhost kernel: hdc: ATAPI 24X CD-ROM drive, 128kB Cache 
Apr 12 11:31:30 localhost kernel: Uniform CDROM driver Revision: 2.56 
Apr 12 11:31:30 localhost kernel: Floppy drive(s): fd0 is 1.44M 
Apr 12 11:31:30 localhost kernel: FDC 0 is a National Semiconductor PC87306 
Apr 12 11:31:30 localhost kernel: md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 
Apr 12 11:31:30 localhost kernel: raid5: measuring checksumming speed 
Apr 12 11:31:30 localhost kernel: raid5: MMX detected, trying high-speed MMX checksum routines 
Apr 12 11:31:30 localhost kernel:    pII_mmx   :  1109.472 MB/sec 
Apr 12 11:31:30 localhost kernel:    p5_mmx    :  1165.479 MB/sec 
Apr 12 11:31:30 localhost kernel:    8regs     :   855.726 MB/sec 
Apr 12 11:31:30 localhost kernel:    32regs    :   480.060 MB/sec 
Apr 12 11:31:30 localhost kernel: using fastest function: p5_mmx (1165.479 MB/sec) 
Apr 12 11:31:30 localhost kernel: scsi : 0 hosts. 
Apr 12 11:31:30 localhost kernel: scsi : detected total. 
Apr 12 11:31:30 localhost kernel: md.c: sizeof(mdp_super_t) = 4096 
Apr 12 11:31:30 localhost kernel: Partition check: 
Apr 12 11:31:30 localhost kernel:  hda: hda1 hda2 < hda5 hda6 > 
Apr 12 11:31:30 localhost kernel: RAMDISK: Compressed image found at block 0 
Apr 12 11:31:30 localhost kernel: autodetecting RAID arrays 
Apr 12 11:31:30 localhost kernel: autorun ... 
Apr 12 11:31:30 localhost kernel: ... autorun DONE. 
Apr 12 11:31:30 localhost kernel: VFS: Mounted root (ext2 filesystem). 
Apr 12 11:31:30 localhost kernel: autodetecting RAID arrays 
Apr 12 11:31:30 localhost kernel: autorun ... 
Apr 12 11:31:30 localhost kernel: ... autorun DONE. 
Apr 12 11:31:30 localhost kernel: VFS: Mounted root (ext2 filesystem) readonly. 
Apr 12 11:31:30 localhost kernel: change_root: old root has d_count=1 
Apr 12 11:31:30 localhost kernel: Trying to unmount old root ... okay 
Apr 12 11:31:30 localhost kernel: Freeing unused kernel memory: 64k freed 
Apr 12 11:31:30 localhost kernel: Adding Swap: 24056k swap-space (priority -1) 
Apr 12 11:31:30 localhost atd: atd startup succeeded
Apr 12 11:31:31 localhost crond: crond startup succeeded
Apr 12 11:31:31 localhost pcmcia: Starting PCMCIA services:
Apr 12 11:31:31 localhost pcmcia:  modules
Apr 12 11:31:31 localhost kernel: Linux PCMCIA Card Services 3.1.13 
Apr 12 11:31:31 localhost kernel:   kernel build: 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999 
Apr 12 11:31:31 localhost kernel:   options:  [pci] [cardbus] [apm] [pnp] 
Apr 12 11:31:31 localhost kernel: PCI routing table version 1.0 at 0xfbc40 
Apr 12 11:31:31 localhost kernel:   01:07.0 -> irq 9 
Apr 12 11:31:31 localhost kernel:   01:07.1 -> irq 9 
Apr 12 11:31:31 localhost kernel: PnP: PNP BIOS installation structure at 0xc00fe2d0 
Apr 12 11:31:31 localhost kernel: PnP: PNP BIOS version 1.0, entry at f0000:e2f4, dseg at 40 
Apr 12 11:31:31 localhost kernel: Intel PCIC probe:  
Apr 12 11:31:31 localhost kernel:   TI 1225 PCI-to-CardBus at slot 01:07, mem 0x68000000 
Apr 12 11:31:31 localhost kernel:     host opts [0]: [pci only] [pci irq 9] [lat 64/176] [bus 32/34] 
Apr 12 11:31:31 localhost kernel:     host opts [1]: [pci only] [pci irq 9] [lat 64/176] [bus 35/37] 
Apr 12 11:31:31 localhost kernel:     PCI card interrupts, PCI status changes 
Apr 12 11:31:31 localhost pcmcia:  cardmgr.
Apr 12 11:31:31 localhost cardmgr[355]: starting, version is 3.1.13
Apr 12 11:31:31 localhost rc: Starting pcmcia succeeded
Apr 12 11:31:31 localhost cardmgr[355]: watching 2 sockets
Apr 12 11:31:31 localhost kernel: cs: IO port probe 0x0c00-0x0cff: clean. 
Apr 12 11:31:31 localhost kernel: cs: IO port probe 0x0800-0x08ff: clean. 
Apr 12 11:31:31 localhost kernel: cs: IO port probe 0x0100-0x04ff: clean. 
Apr 12 11:31:31 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Apr 12 11:31:31 localhost inet: inetd startup succeeded
Apr 12 11:31:31 localhost lpd: lpd startup succeeded
Apr 12 11:31:31 localhost keytable: Loading keymap: Loading system font: 
Apr 12 11:31:31 localhost rc: Starting keytable succeeded
Apr 12 11:31:32 localhost sendmail: sendmail startup succeeded
Apr 12 11:31:33 localhost gpm: gpm startup succeeded
Apr 12 11:31:33 localhost xfs: xfs startup succeeded
Apr 12 11:31:33 localhost linuxconf: Linuxconf final setup
Apr 12 11:31:33 localhost xfs: Warning: The directory "/usr/X11R6/lib/X11/fonts/100dpi" does not exist. 
Apr 12 11:31:33 localhost xfs:          Entry deleted from font path. 
Apr 12 11:31:34 localhost kernel: cs: socket 1 timed out during reset 
Apr 12 11:31:35 localhost rc: Starting linuxconf succeeded
Apr 12 11:31:43 localhost PAM_pwdb[484]: (login) session opened for user root by LOGIN(uid=0)
Apr 12 11:31:52 localhost cardmgr[355]: initializing socket 0
Apr 12 11:31:52 localhost cardmgr[355]: socket 0: Lucent Technologies WaveLAN/IEEE
Apr 12 11:31:52 localhost kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. 
Apr 12 11:31:52 localhost cardmgr[355]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/wavelan2_cs.o'
Apr 12 11:31:54 localhost kernel: eth0: WaveLAN/IEEE, HCF failure: "Card not found (ejected unexpectedly)" 
Apr 12 11:31:54 localhost cardmgr[355]: get dev info on socket 0 failed: No such device
Apr 12 11:31:58 localhost cardmgr[355]: shutting down socket 0
Apr 12 11:31:58 localhost cardmgr[355]: executing: 'rmmod wavelan2_cs'

dmesg output

Linux version 2.2.12-20 (root@porky.devel.redhat.com) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Sep 27 10:40:35 EDT 1999
Detected 498488945 Hz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 496.44 BogoMIPS
Memory: 61388k/64128k available (1008k kernel code, 412k reserved, 976k data, 64k init)
DENTRY hash table entries: 262144 (order: 9, 2097152 bytes)
Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
VFS: Diskquotas version dquot_6.4.0 initialized
CPU: Intel Pentium III (Katmai) stepping 03
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.35a (19990819) Richard Gooch (rgooch@atnf.csiro.au)
PCI: PCI BIOS revision 2.10 entry at 0xfc0ce
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
TCP: Hash tables configured (ehash 65536 bhash 65536)
Initializing RT netlink socket
Starting kswapd v 1.5 
Detected PS/2 Mouse Port.
Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled
pty: 256 Unix98 ptys configured
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.9)
Real Time Clock Driver v1.09
RAM disk driver initialized:  16 RAM disks of 4096K size
PCI_IDE: unknown IDE controller on PCI bus 00 device f9, VID=8086, DID=2411
PCI_IDE: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
hda: Maxtor 90651U2, ATA DISK drive
hdc: SAMSUNG CD-ROM SN-124, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: Maxtor 90651U2, 6149MB w/512kB Cache, CHS=784/255/63
hdc: ATAPI 24X CD-ROM drive, 128kB Cache
Uniform CDROM driver Revision: 2.56
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
raid5: measuring checksumming speed
raid5: MMX detected, trying high-speed MMX checksum routines
   pII_mmx   :  1109.472 MB/sec
   p5_mmx    :  1165.479 MB/sec
   8regs     :   855.726 MB/sec
   32regs    :   480.060 MB/sec
using fastest function: p5_mmx (1165.479 MB/sec)
scsi : 0 hosts.
scsi : detected total.
md.c: sizeof(mdp_super_t) = 4096
Partition check:
 hda: hda1 hda2 < hda5 hda6 >
RAMDISK: Compressed image found at block 0
autodetecting RAID arrays
autorun ...
... autorun DONE.
VFS: Mounted root (ext2 filesystem).
autodetecting RAID arrays
autorun ...
... autorun DONE.
VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=1
Trying to unmount old root ... okay
Freeing unused kernel memory: 64k freed
Adding Swap: 24056k swap-space (priority -1)
Linux PCMCIA Card Services 3.1.13
  kernel build: 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999
  options:  [pci] [cardbus] [apm] [pnp]
PCI routing table version 1.0 at 0xfbc40
  01:07.0 -> irq 9
  01:07.1 -> irq 9
PnP: PNP BIOS installation structure at 0xc00fe2d0
PnP: PNP BIOS version 1.0, entry at f0000:e2f4, dseg at 40
Intel PCIC probe: 
  TI 1225 PCI-to-CardBus at slot 01:07, mem 0x68000000
    host opts [0]: [pci only] [pci irq 9] [lat 64/176] [bus 32/34]
    host opts [1]: [pci only] [pci irq 9] [lat 64/176] [bus 35/37]
    PCI card interrupts, PCI status changes
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
cs: socket 1 timed out during reset
cs: memory probe 0xa0000000-0xa0ffffff: clean.
eth0: WaveLAN/IEEE, HCF failure: "Card not found (ejected unexpectedly)"
VFS: Disk change detected on device fd(2,0)


output of lspci -vv


00:00.0 Host bridge: Intel Corporation: Unknown device 7124 (rev 03)
	Subsystem: Unknown device 1028:00b4
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
	Latency: 0 set

00:01.0 VGA compatible controller: Intel Corporation: Unknown device 7125 (rev 03)
	Subsystem: Unknown device 1028:00b4
	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: 0 set
	Interrupt: pin A routed to IRQ 9
	Region 0: Memory at f4000000 (32-bit, prefetchable)
	Region 1: Memory at ff000000 (32-bit, non-prefetchable)
	Capabilities: [dc] Power Management version 1
		Flags: PMEClk- AuxPwr- DSI+ D1- D2- PME-
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:1e.0 PCI bridge: Intel Corporation: Unknown device 2418 (rev 02)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0 set
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fe000000-feffffff
	Prefetchable memory behind bridge: f9000000-f9ffffff
	BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-

00:1f.0 ISA bridge: Intel Corporation: Unknown device 2410 (rev 02)
	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: 0 set

00:1f.1 IDE interface: Intel Corporation: Unknown device 2411 (rev 02) (prog-if 80)
	Subsystem: Unknown device 8086:2411
	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: 0 set
	Region 4: I/O ports at ffa0

00:1f.2 USB Controller: Intel Corporation: Unknown device 2412 (rev 02)
	Subsystem: Unknown device 8086:2412
	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: 0 set
	Interrupt: pin D routed to IRQ 11
	Region 4: I/O ports at ff80

00:1f.3 Class 0c05: Intel Corporation: Unknown device 2413 (rev 02)
	Subsystem: Unknown device 8086:2413
	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 B routed to IRQ 10
	Region 4: I/O ports at ecd0

01:07.0 CardBus bridge: Texas Instruments: Unknown device ac1c (rev 01)
	Subsystem: Unknown device 104c:ac1c
	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, cache line size 08
	Interrupt: pin A routed to IRQ 9
	Region 0: Memory at <ignored> (32-bit, non-prefetchable)
	Bus: primary=00, secondary=20, subordinate=22, sec-latency=176
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
	16-bit legacy interface ports at 0007

01:07.1 CardBus bridge: Texas Instruments: Unknown device ac1c (rev 01)
	Subsystem: Unknown device 104c:ac1c
	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, cache line size 08
	Interrupt: pin A routed to IRQ 9
	Region 0: Memory at <ignored> (32-bit, non-prefetchable)
	Bus: primary=00, secondary=23, subordinate=25, sec-latency=176
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
	16-bit legacy interface ports at 0007

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

None Re: Question: Lucent WaveLAN IEEE in ISA PCMCIA Brigde hangs on FTP downloads

Re: Question Lucent WaveLAN IEEE in ISA PCMCIA Brigde hangs on FTP downloads (Gerald Richter)
Date: 2000, Feb 19
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Dumb question: you say the hardware differs slightly.  So, what is the
slight hardware difference?

-- Dave

None RE: Question: Lucent WaveLAN IEEE in ISA PCMCIA Brigde hangs on FTP downloads

Re: None Re: Question: Lucent WaveLAN IEEE in ISA PCMCIA Brigde hangs on FTP downloads (David Hinds)
Date: 2000, Feb 19
From: Gerald Richter richter

> Dumb question: you say the hardware differs slightly.  So, what is the
> slight hardware difference?
>

They have different motherboards. The one that works is on a ASUS P2B
Motherboard with a Pentium II 350 Mhz and 100 MHz Bus clock, the one that
doesn't work has an other motherboard (I don't no which exactly), with
onboard network adapter (Intel 82558) and onboard vga (ati rage pro) and an
Intel 400Mhz Celeron and 66Mhz Bus clock. Both uses the Intel BX chipset.

I have tried to disable as much onboard components as possible, have choosen
different irqs and i/o port, but this doesn't make any difference. Then I
have taken the harddisk and put it in the box that works, and here this
software also works. So it can only be a problem of the hardware (or the the
combination of hard- and software).

Thanks for any hint

Gerald

News new Wavelan IEEE driver & debugging

Re: Question Lucent WaveLAN IEEE in ISA PCMCIA Brigde hangs on FTP downloads (Gerald Richter)
Date: 2000, Feb 25
From: Jean Tourrilhes jt

	A few comments...

	Debugging :
	The first thing is to really pin-point the fault on
the Wavelan. I'm sorry, FTP is not a good enough test, because
it test the file system as well. For example, in 2.3.47, I
can't run FTP because the file system is ****.
	I recommend you to fetch netperf and run it for a
while. Then we can accuse the Wavelan.

	Solving :
	If my memory serves me correctly, 2.2.14 did fix some
file system issues. You may want to upgrade.
	The most likely cause of trouble is of course the
wvlan_cs driver. Andy is about to release a new version, and
he has dramatically improved the handling of IRQs. This might
fix your problem.
	You may also want to check the system logs. Of course,
in case of a hang, it's likely that the important message
won't have been flushed to the disk.

	Regards,

	Jean

None RE: News: new Wavelan IEEE driver & debugging

Re: News new Wavelan IEEE driver & debugging (Jean Tourrilhes)
Date: 2000, Feb 28
From: Gerald Richter richter

>
>         A few comments...
>
>         Debugging :
>         The first thing is to really pin-point the fault on
> the Wavelan. I'm sorry, FTP is not a good enough test, because
> it test the file system as well. For example, in 2.3.47, I
> can't run FTP because the file system is ****.
>         I recommend you to fetch netperf and run it for a
> while. Then we can accuse the Wavelan.
>

I don't found netperf on the net, but it's surely not an ftp problem. FTP
works via ethernet (some files, some hosts). I get the same problem with an
HTTP Request which is just printed to stdout...

>         Solving :
>         If my memory serves me correctly, 2.2.14 did fix some
> file system issues. You may want to upgrade.

2.2.14 is still beta, I will do as soon as it is out.

>         The most likely cause of trouble is of course the
> wvlan_cs driver. Andy is about to release a new version, and
> he has dramatically improved the handling of IRQs. This might
> fix your problem.

I think I wait for new driver.

>         You may also want to check the system logs. Of course,
> in case of a hang, it's likely that the important message
> won't have been flushed to the disk.
>

I really checked out everything. Nothing in the syslog, even not if I
compile and run with debug on.

Thanks for your help

Gerald



-------------------------------------------------------------
Gerald Richter    ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting

Post:       Tulpenstrasse 5         D-55276 Dienheim b. Mainz
E-Mail:     richter@ecos.de         Voice:    +49 6133 925151
WWW:        http://www.ecos.de      Fax:      +49 6133 925152
-------------------------------------------------------------

None A Wavelan update is imminent

Re: None RE: News: new Wavelan IEEE driver & debugging (Gerald Richter)
Date: 2000, Feb 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> 2.2.14 is still beta, I will do as soon as it is out.

2.2.14 has been out for a couple months.  2.2.15 is still in beta.

> I think I wait for new driver.

I just got a wvlan_cs update and it will be in the next PCMCIA beta.

-- Dave

None RE: A Wavelan update is imminent

Re: None A Wavelan update is imminent (David Hinds)
Date: 2000, Feb 29
From: Gerald Richter richter

>
> If you reply to this message at HyperNews@pcmcia.sourceforge.org, include:
> In-Reply-To: <20000228125448.B5441@valinux.com>
>
> > 2.2.14 is still beta, I will do as soon as it is out.
>
> 2.2.14 has been out for a couple months.  2.2.15 is still in beta.
>

Oops, sorry you are right. My browser fooled me. I look just before I wrote
you the last mail, but my browser load the page out of his cache and showed
me the old one. After a Reload I see that 2.2.14 is really there since two
month. I try to upgrade.

> > I think I wait for new driver.
>
> I just got a wvlan_cs update and it will be in the next PCMCIA beta.
>

Good news :-)

Gerald




-------------------------------------------------------------
Gerald Richter    ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting

Post:       Tulpenstrasse 5         D-55276 Dienheim b. Mainz
E-Mail:     richter@ecos.de         Voice:    +49 6133 925151
WWW:        http://www.ecos.de      Fax:      +49 6133 925152
-------------------------------------------------------------

Ok Already there !!!

Re: None RE: A Wavelan update is imminent (Gerald Richter)
Date: 2000, Feb 29
From: Jean Tourrilhes jt

	Gosh !!! David is so quick that the beta is already
released, and you'll find it in the NEW directory as
pcmcia-cs.28-Feb-00...
	Enjoy !!!

	Jean

None RE: A Wavelan update is imminent

Re: None A Wavelan update is imminent (David Hinds)
Date: 2000, Mar 01
From: Gerald Richter richter

>
> 2.2.14 has been out for a couple months.  2.2.15 is still in beta.
>

I have upgraded to 2.2.14, but no changes...

> > I think I wait for new driver.
>
> I just got a wvlan_cs update and it will be in the next PCMCIA beta.
>
>...
>         Gosh !!! David is so quick that the beta is already
> released, and you'll find it in the NEW directory as
> pcmcia-cs.28-Feb-00...

I have also tested this new driver, but still the same problem:

ping works, ftp and http makes the initial tcp connection (things like "ls"
works, also), but a download of a file (also if it's not saved to the
filesystem) hangs (ping still works at the same time).

Since it must be a hardware problem (because it works with all other
computers I tested), the next I will try is to use the TI PCI1031
PCI-to-PCMCIA bridge, which David told me that it should work, which I will
get soon.

Thanks for all the help

Gerald


-------------------------------------------------------------
Gerald Richter    ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting

Post:       Tulpenstrasse 5         D-55276 Dienheim b. Mainz
E-Mail:     richter@ecos.de         Voice:    +49 6133 925151
WWW:        http://www.ecos.de      Fax:      +49 6133 925152
-------------------------------------------------------------

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

Idea See the Howto

Re: Question Wireless card choice (Duane Gustavus)
Date: 2000, Mar 15
From: Jean Tourrilhes jt

http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/

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

Sad WMAC did not have enough RAM to build unsollicited frame!

Re: Question Problem with Cabletron RoamAbout (Danilo Godec)
Date: 2000, Mar 23
From: Danilo Godec danci

When I start the pcmcia services, this is what I get (with RoamAbout card inserted):

Linux PCMCIA Card Services 3.1.13
  kernel build: 2.2.14 #2 Tue Mar 21 09:11:38 CET 2000
  options:  [pci] [cardbus]
PCI routing table version 1.0 at 0xfdf20
Intel PCIC probe:
  Vadem VG-469 ISA-to-PCMCIA at port 0x3e2 ofs 0x00
    host opts [0]: none
    host opts [1]: none
    ISA irqs (scanned) = 3,4,5,7,9,15 status change on irq 15
cs: IO port probe 0x0c00-0x0cff: excluding 0xc00-0xc3f 0xca0-0xca7 0xcf8-0xcff
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x370-0x37f 0x4d0-0x4d7
cs: IO port probe 0x1000-0x17ff: excluding 0x1040-0x109f 0x1480-0x14ff
cs: IO port probe 0x0a00-0x0aff: 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 5, 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 6d 92 0d 00

Thw wvlan0 device gets configured (IP, etc.) but when I try to use it (ping, telnet, etc.), I get the message from the subject.

Could someone with a similar card (Lucent WaveLan, ...) check if his wvlan_cs messages are similar or am I missing something (memory region perhaps)?

Thanks, Danilo

Feedback Solved (sort of)

Re: Sad WMAC did not have enough RAM to build unsollicited frame! (Danilo Godec)
Date: 2000, Mar 23
From: Danilo Godec danci

It seems my machines were out of range (in building, through the walls). Now I moved them closer together and ping started to work. However the WMAC messages were still there until I removed and reinserted one of the cards.

After that, all seems fine. It would still be nice to know if someone else gets the same behaviour if no other cards are in range...

Danilo

Ok Solved (for good, by Andy)

Re: Question Problem with Cabletron RoamAbout (Danilo Godec)
Date: 2000, Mar 29
From: Danilo Godec danci

Ok, Andy contacted me and explained, that this message is actually generated by the card itself and only reported by the driver. He also contacted folks at Lucent and they told him that this message it's HARMLESS (they even modified their driver to simply not report the message any more).

Thanks, folks!

   D.

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!!

Sad Ouch ! Not supported yet...

Re: Question two PCMCIA-ISA adapters (Guillaum Dallaire)
Date: 2000, Mar 27
From: Jean Tourrilhes jt

	Hi,

	Neither Andy or me has tested such a configuration. As
you can see, most of the hooks are in place, we just need to
fix the bugs. Unfortunately, I don't know when we will have
the time for it...
	Once we fix it, you would be able to set each card
separately via Wireless Extensions. I even sent a patch to
David to automate that...
	Sorry...

	Jean

P.S. : Contact Andy, just in case...

None Support for multiple WaveLAN/IEEE cards on one host.

Re: Sad Ouch ! Not supported yet... (Jean Tourrilhes)
Date: 2000, Mar 27
From: Guillaum Dallaire gd

Hi,

In the Andy's home page of his driver, there is:

- Support for multiple WaveLAN/IEEE cards on one host.

I have sent an email to Andy.

thanks!

More Same problem, 2 pcmcia cards on one isa adapter (with 2sockets)

Re: Question two PCMCIA-ISA adapters (Guillaum Dallaire)
Date: 2000, May 18
From: Raul Elizondo Sato1

i got the same problem, but i got a isa adapter with 2 pcmcia sockets. PCMCIA-HOWTO says to set network.opts as:

case "$ADDRESS" in
*,0,*,*)
  # definition socket 0
  ;;
*,1,*,*)
  # definition socket 1
  ;;
esac

but the second one i inserts says:

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

what can i do? (RH 6.2, pcmcia-3.1.8, wavelan2_cs-6.00.tar.gz, hw: ieee802.11 Wavelan Bronze turbo)

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?

Sad Likely not possible...

Re: Question Wavelan Linux Bridge (Benny Brown)
Date: 2000, Mar 30
From: Jean Tourrilhes jt

	This is becomming almost a FAQ. You can't use
promiscuous mode for bridging because of MAC retries.
	For more info, read :
http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Linux.Wireless.mac.html#topology

	Jean

Question How do base stations do it, then?

Re: Sad Likely not possible... (Jean Tourrilhes)
Date: 2000, Apr 18
From: Marcel Waldvogel mwa

How do base stations (like the AirPort) do it, then?

They just use an unmodified WaveLan/IEEE card and some software, AFAIK.

-Marcel

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 

Idea A few suggestions...

Re: Question "receive buffer overflow" with wavelan driver (John Ruttenberg)
Date: 2000, Apr 03
From: Jean Tourrilhes jt

	Food for thoughts :
	o You are using the binary Wavelan driver. You should
contact Lucent directly for support.
	o There is 2 versions of this driver, 4.00 and 6.00.
Please try both.
	o You may want to try the GPL driver (from Andy). At
least, we can have a look at what the problem is.
	Good luck...

	Jean

More Oups !

Re: Idea A few suggestions... (Jean Tourrilhes)
Date: 2000, Apr 03
From: Jean Tourrilhes jt

	Sorry, sorry, sorry ! I'm sleeping there...
	I thought you were using a Wavelan IEEE, there are so few
people still using the good old Wavelan. Let's get back into
context...

	So, a few suggestions :
	o I did a big upgrade of the driver in 3.1.12. Could you check
is 3.1.11 makes any difference ?
	o David seems to have troubles with IRQs with some chipset. I
saw some messages related to that in your log. Could you check it ?
	And sorry for beeing asleep...

	Jean

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? ;)

None Windows and Linux may be using incompatible settings

Re: Question Cross-platform communications problems (Dagmar d'Surreal)
Date: 2000, Apr 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I'm not familiar with the details, but I know there have been changes
in the default configuration for the ray_cs driver recently.

Check with Corey Thomas, the ray_cs driver author.

-- Dave

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.

None This is the wrong driver for the IEEE card

Re: Question WaveLan PCMCIA card Problems (Zach Berke)
Date: 2000, Apr 10
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Your card is a WaveLAN/IEEE card, however, you seem to be loading the
wavelan_cs driver, which is the driver for the older non-IEEE WaveLAN
cards.  I suspect that you modified /etc/pcmcia/config so that this
would happen?  (that's an important detail to mention)

There are two WaveLAN/IEEE drivers for linux.  One, the wvlan_cs
driver, is included in the current PCMCIA driver release; the other,
which was developed by Lucent, is available on the PCMCIA FTP site in
the contrib area.  You need to use one of these drivers, and not
wavelan_cs.

-- Dave

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

None Need more information

Re: Warning Problem with TI1225 and Lucent Wavelan (even in 3.1.14) (Alen Salamun)
Date: 2000, Apr 12
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You should post the startup messages from the PCMCIA drivers.  I can't
really guess without seeing them.  Maybe it is an IO port conflict.
You might try recompiling the PCMCIA package with "PnP BIOS support"
switched on.

-- Dave

More More info on the problem

Re: None Need more information (David Hinds)
Date: 2000, Apr 12
From: Alen Salamun ALiEN

Hi!

This is the cutout of the log file:

Apr 12 20:08:45 hal9000 kernel:   options:  [pci] [cardbus] [apm]
Apr 12 20:08:45 hal9000 kernel: PCI routing table version 1.0 at 0xfd490
Apr 12 20:08:45 hal9000 kernel:   00:14.0 -> irq 10
Apr 12 20:08:45 hal9000 kernel:   00:14.1 -> irq 10
Apr 12 20:08:45 hal9000 kernel: Intel PCIC probe:
Apr 12 20:08:45 hal9000 kernel:   TI 1225 rev 01 PCI-to-CardBus at slot 00:14, mem 0xe8001000
Apr 12 20:08:45 hal9000 kernel:     host opts [0]: [pci only] [pci irq 10] [lat 64/176] [bus 224/0]
Apr 12 20:08:45 hal9000 kernel:     host opts [1]: [pci only] [pci irq 10] [lat 64/176] [bus 228/0]
Apr 12 20:08:45 hal9000 kernel:     PCI card interrupts, PCI status changes
Apr 12 20:08:45 hal9000 cardmgr[233]: starting, version is 3.1.14
Apr 12 20:08:45 hal9000 cardmgr[233]: watching 2 sockets
Apr 12 20:08:45 hal9000 kernel: cs: IO port probe 0x1000-0x17ff: clean.
Apr 12 20:08:45 hal9000 kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x370-0x37f 0x4d0-0x4d7
Apr 12 20:08:45 hal9000 kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Apr 12 20:08:45 hal9000 cardmgr[233]: initializing socket 0
Apr 12 20:08:45 hal9000 kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Apr 12 20:08:45 hal9000 cardmgr[233]: socket 0: Lucent Technologies WaveLAN/IEEE
Apr 12 20:08:45 hal9000 cardmgr[233]:   product info: "Lucent Technologies", "WaveLAN/IEEE", "Version 01.01", ""
Apr 12 20:08:45 hal9000 cardmgr[233]:   manfid: 0x0156, 0x0002  function: 6 (network)
Apr 12 20:08:45 hal9000 cardmgr[233]: executing: 'insmod /lib/modules/2.2.14-15mdk/pcmcia/wavelan2_cs.o medium_r
eservation=500 enable_encryption=Y key_1=XXXXX network_name=XXXXX station_name=XXXXX'

This is the last line in the log. I have tried with Bios PNP on and off, same results. I must say that with older pcmcia source, machine did not lockup except if doing "cardstat ident".

It works flawlessly with ISA controler...

Bye, Alen

More Same with me... see posting in thread "6."

Re: Warning Problem with TI1225 and Lucent Wavelan (even in 3.1.14) (Alen Salamun)
Date: 2000, Apr 13
From: Mark Geib geib

Same thing here. I grabbed 3.1.14 did a make... changed only /etc/sysconf/pcmcia to use "irq_mode=0" and the system will hang on a card insert, come to life after a card remove.

If I change the option to "irq_mode=1" everthing seems fine but I get a "Transmit timeout" when I try to bring up the interface...

I have posted my logs in thread number 6 of this forum.

News FIX for Lucent's wavelan driver! Now it "works" with TI1225!

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

Hi!

David Hinds <dhinds@valinux.com> has made a simple hack to Lucent's wavelan driver and now they work!

BUT! If you try to shutdown PCMCIA without removing the card before your machine will hang. I hope this will be fixed soon too!

This is the diff:

1187,1192d1186

<         if ((hcfStatus = hcf_action (lp->hcfCtx, HCF_ACT_INT_ON)) !=
<             HCF_SUCCESS)
<         {
<             goto hcf_failed;
<         }
<           

Remove this lines in wavelan2_cs.c and you are in the business! :)

Disagree This patch doesn't work for me (details inside)

Re: News FIX for Lucent's wavelan driver! Now it "works" with TI1225! (Alen Salamun)
Date: 2000, Apr 18
From: Michael Vasilenko acid

pieces of /var/log/messages:

kernel: Linux PCMCIA Card Services 3.1.14
kernel:   kernel build: 2.2.14 #1 Tue Apr 18 19:48:31 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[569]: starting, version is 3.1.14
cardmgr[569]: 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[569]: initializing socket 0
kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
cardmgr[569]: socket 0: Lucent Technologies WaveLAN/IEEE
cardmgr[569]: executing: 'insmod /lib/modules/2.2.14/pcmcia/wavelan2_cs.o port_type=3 station_name=STU network_name=AP000'
kernel: eth1: WaveLAN/IEEE, HCF failure: "Card not found (ejected unexpectedly)"
cardmgr[569]: get dev info on socket 0 failed: No such device

News Beta wavelan driver from Lucent

Re: Warning Problem with TI1225 and Lucent Wavelan (even in 3.1.14) (Alen Salamun)
Date: 2000, Apr 19
From: David Hinds <dhinds@pcmcia.sourceforge.org>

A new version (6.01BETA) of Lucent's Wavelan driver is on the PCMCIA FTP site: this version should fix the TI 1225 card dock difficulties.

-- Dave

Sad Where is the beta driver?

Re: News Beta wavelan driver from Lucent (David Hinds)
Date: 2000, May 09
From: Tommy Svensson tommy23

I have serach Wavelan ftp site up and down ftp.wavelan.com but don't find the 6.01BETA driver for Linux I have look in the following directory

/pub/SOFTWARE/IEEE/PC_CARD/LINUX" /pub/SOFTWARE/IEEE/UPDATE/*

But don't find it... I find only the 6.00 driver from mars.

Please help me.

None It is on the Linux PCMCIA ftp site

Re: Sad Where is the beta driver? (Tommy Svensson)
Date: 2000, May 09
From: David Hinds <dhinds@pcmcia.sourceforge.org>

ftp://sourceforge.org/pcmcia/contrib

-- Dave

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

None These cards do not work in standard PCMCIA slots

Re: Question Apple Airport cards in a PC (Kelly Murray)
Date: 2000, Apr 14
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I have heard from people who have tried these cards, who confirm that
they do not work in an ordinary PCMCIA slot.  There is something
peculiar about them, and a standard slot will not even detect that a
card is present.  I suspect this was done on purpose to prevent people
from using the cards on other systems.

-- Dave

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

News /proc/net/wireless in ad-hoc mode...

Re: Question Untitled (Jonathan Chan)
Date: 2000, Apr 18
From: Jean Tourrilhes jt

	Hi,

	The hardware work sligthly differently, which explain
the difference. The old Wavelan report the values for the last
received packet, whereas the new report the value for the last
packet from the Access Point. As you don't have any Access
Point, no values...
	However, in the wvlan_cs, I did introduce a useful
hack : in ad-hoc mode, /proc/net/wireless report the values
for the first address in the spy list. Of course, you need to
set something in the spy list for this to work...
	So, on each node, just set with "iwspy" the address
of the partner, and you will get what you want in
/proc/net/wireless. You may used the new "wireless.opts" stuff
in 3.1.14 to do that automatically each time you insert the
card...
	Good luck !

	Jean

Question iwspy on WaveLAN operating at other sub-band frequencies

Re: News /proc/net/wireless in ad-hoc mode... (Jean Tourrilhes)
Date: 2000, Apr 18
From: Jonathan Chan jchan

Hi Jean,

Thanks for your helpful suggestion as usual...

If iwspy can be used to "spy" on the link layer status of another card, I assume it works when these cards operate on the same sub-band frequency...

I am wondering if the "new generation" iwspy can be used to "spy" on a card working at another sub-band frequency. Of course, this should be done with "minimal" interruptions to the on-going traffic!?

If this cannot be done in ad-hoc mode, could a mobile host be handed over from one Access Point to another even though these Access Points are using different sub-band frequencies??

If it is possible, does it mean that there is a common control channel (at frequency X) in which Access Point or WaveLAN cards send out and detect other's link layer beacons?? OR am I asking too much for a wireles LAN...

Thanks again for any comments...

Cheers, Jonathan

Sad Untitled

Re: Question iwspy on WaveLAN operating at other sub-band frequencies (Jonathan Chan)
Date: 2000, Apr 24
From: Jean Tourrilhes jt

	Nope...
	A radio receiver can be tuned only on one frequency.
You may scan sequencially a bunch of frequencies, but you need
to temporaly quit the network. And the Wavelan has no
interface to trigger that.

	Jean

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'

Idea Possible fix

Re: Sad Lucent WaveLAN/IEEE fails with updated firmware (Michael Vasilenko)
Date: 2000, Apr 21
From: Atanu Ghosh atanu

I have seen a similar initialization problem with new Lucent cards which I believe are using version 6.

wvlan_cs: Initialization failed!

So I looked through source wireless/wvlan_cs.c the error occurs in the routine "wvlan_hw_config"

A number of initializations are performed in this function. It wasn't clear which had actually failed. So I recompiled with debugging.

The call that failed was: wvlan_cs: hcf_put_info(0xfc82:0x92a) returned 0xff

From wvlan_mdd.h: #define CFG_FRAGMENTATION_THRH 0xFC82 //[STA] Fragment length for unicast Tx-message

From wvlan_cs.c: rc = wvlan_hw_setthreshold(&local->ifb, frag_threshold, CFG_FRAGMENTATION_THRH);

So I commented out the threshold setting in this routine and the device was correctly initialized.

I had a quick look at the Lucent driver they don't seem to touch this option.

	Atanu.

Feedback Lucent wavelan2_cs driver works

Re: Sad Lucent WaveLAN/IEEE fails with updated firmware (Michael Vasilenko)
Date: 2000, Apr 27
From: Charlie Price cprice

The Lucent "supported" drivers work with new firmware.

The most recent driver from Lucent for Linux,
the wavelan2_cs v6.00 driver, works for
WaveLAN/IEEE cards with firmware 6.04
(this is the "Station Functions firmware").
This is available under:

   http://www.wavelan.com/support/software/

Both the wvlan_cs v1.0.4 driver (in PCMCIA 3.1.14)
and the wavelan2_cs v6.00. driver
worked for me on a card with firmware 4.32.

FYI: the newest Windows drivers don't work
with the downrev firmware.

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?

News Wireless Extensions is more than Wavelan or 802.11

Re: Question Changing mode of Lucent WaveLAN/IEEE card?
Date: 2000, Apr 24
From: Jean Tourrilhes jt

	It's perfectly normal...

	The Wireless Extensions is a generic API supporting
all kind of Wireless LANs out there. I designed it to support
802.11 cards, like the Wavelan IEEE, but also HiperLAN, Proxim
OpenAir and a bunch of proprietary cards.
	So, don't be surprised if the Wireless Extensions and
"iwconfig" offer features that don't make sense for 802.11
cards... For example, you can't set the NWID with 802.11
cards.
	Another factor is that not all drivers support all the
functionality of the underlying hardware, because it take
effort to code. However, "wvlan_cs" is amongst the most
complete as far as Wireless Extensions goes.

	Now, comming back to the mode : the 802.11
specification defines only 2 modes for stations, ad-hoc and
managed. You could use "auto" to let the driver choose, but
this is not implemented in the Wavelan driver. Master and
Secondary are there to support Proxim Open Air, and Repeater
is designed for the HiperLan standard (no product yet).

	Happy now ?

	Jean

Question port_type: 3 choices

Re: News Wireless Extensions is more than Wavelan or 802.11 (Jean Tourrilhes)
Date: 2000, Apr 25
From: Guillaum Dallaire gd

Hi,

in the wvlan_cs man, I see:

port_type=n
	Select WaveLAN port type: [1] BSS - Basic Service Set (default), [2] WDS - Wireless Distribution System, [3] Pseudo-IBSS - ad-hoc network (no Access-Point, PtP).

what is the WDS - Wireless Distribution System ?

thanks!

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

None Yes, there is something funky with interrupts

Re: Question Wavelan IEEE, Sony Vaio N505 VE, and suspend/resume (Jürgen Botz)
Date: 2000, Apr 24
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Unfortunately, I've been totally unable to figure out what the
specific problem is.  The CardBus bridge appears to be configured
absolutely identically before and after the suspend, but after the
suspend, it doesn't deliver any interrupts until you reboot.  There
must be some hidden state information in the bridge that is getting
messed up, but I can't figure out what it could be.

-- Dave

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 

None Hmmm, maybe a hardware failure?

Re: Question cs: socket 0 timed out during reset (Peter Kropf)
Date: 2000, Apr 25
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Do you have any other PCMCIA cards that you can try?  This is a fairly
low level failure in a fairly well tested part of the driver, and I'm
wondering if this card (or the adapter??) could be fried.  If you've
got a wireless network, you must have several of the cards: can you
swap them around and see if the problem is the card or the adapter?

I assume you've done a cold boot and that didn't help?  I'd also try
re-seating the PCMCIA adapter card, and the Wavelan card.

-- Dave

Agree Looks that way

Re: None Hmmm, maybe a hardware failure? (David Hinds)
Date: 2000, Apr 25
From: Peter Kropf peterk

Changing cards was the one thing that I didn't do. And it looks like the WaveLAN card itself has failed.

I've inserted the card from a laptop and the server is now working as expected.

Thanks! Now I have to see about a replacement...

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

None Same problem No Mac address

Re: Sad Hardware address not showing-up with WaveLAN Turbo (oscar Rodriguez)
Date: 2000, Apr 26
From: Robert Jackson toyssan

I am running 2.2.14 and have upgraded my pcmcia to 3.1.13. The interface comes up, and I can assing an IP, put with the hardwared address of 00:00:00:00:00:00.

Apr 26 15:04:52 localhost cardmgr[5220]: initializing socket 0
Apr 26 15:04:52 localhost kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Apr 26 15:04:52 localhost cardmgr[5220]: socket 0: Lucent Technologies WaveLAN/IEEE Adapter
Apr 26 15:04:53 localhost cardmgr[5220]: executing: 'insmod /lib/modules/2.2.14-5.0/pcmcia/wvlan_cs.o'
Apr 26 15:04:53 localhost kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4
Apr 26 15:04:53 localhost kernel: wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de>
Apr 26 15:04:53 localhost kernel: wvlan_cs: index 0x01: Vcc 5.0, irq 9, io0x0100-0x013f
Apr 26 15:04:53 localhost kernel: wvlan_cs: Registered netdevice wvlan0
Apr 26 15:04:53 localhost kernel: wvlan_cs: Initialization failed!
Apr 26 15:04:53 localhost cardmgr[5220]: executing: './network start wvlan0'

Question Was this solved? I've got something similar...

Re: None Same problem No Mac address (Robert Jackson)
Date: 2000, Jul 28
From: Bob Cook bcook

I've been chasing something like this (the wvlan_cs driver reporting the initialization failed) for a few days now on my system. So far I haven't had any success although I've been able to isolate it down to being unable to read reliably from the card ioport.

Have you had any luck? Maybe your solution would work for me too!

None Try the other Wavelan-IEEE driver, for comparison

Re: Sad Hardware address not showing-up with WaveLAN Turbo (oscar Rodriguez)
Date: 2000, Apr 26
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I'd suggest trying the Lucent driver (wavelan2_cs, available from the
contrib directory on the PCMCIA FTP site) and see if it behaves any
differently.

-- Dave

Sad I tried the wavelan2_cs driver

Re: None Try the other Wavelan-IEEE driver, for comparison (David Hinds)
Date: 2000, Apr 27
From: oscar Rodriguez dell_7000

It also didn't work. below is the var/message I get:
Apr 26 17:38:56 wednesday cardmgr[5977]: initializing socket 1
Apr 26 17:38:56 wednesday cardmgr[5977]: unsupported card in socket 1
Apr 26 17:38:56 wednesday cardmgr[5977]:   product info: "Lucent Technologies", "WaveLAN/IEEE", "Version 01.01", ""
Apr 26 17:38:56 wednesday cardmgr[5977]:   manfid: 0x0156, 0x0002  function: 6 (network) 

Please advice. thanks for anyhelp

Oscar

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

Note machine hang if changing any wvlan config with iwconfig

Re: Question machine hang while changing freq with iwconfig (Jonathan Chan)
Date: 2000, Apr 28
From: Jonathan Chan jchan

Dear all,

I've done a couple more tests on my laptop about this issue, and these are what I found:

* I excluded some irq choices at /etc/pcmcia/config.opts and the problem still remains. (attempted irq 3, 9, 10)

* I tried to use iwconfig to change something less important (e.g. changing the "Nickname" or "essid" of the interface) and the laptop still freezed... So basically I could only try :

"./iwconfig" OR "./iwconfig --help" BUT nothing else in the argument could save me from cold-booting the laptop...

Thanks for your helps.

Cheers, Jonathan

Note problem solved by using wavelan2_cs driver

Re: Note machine hang if changing any wvlan config with iwconfig (Jonathan Chan)
Date: 2000, May 08
From: Jonathan Chan jchan

Hi all,

The problem is solved if I use the wavelan2_cs driver instead...

Cheers, Jonathan

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.

News Please check in the Howto...

Re: Sad Compaq WL200 Wireless PCI Card not supported? (Patrick Neill)
Date: 2000, May 05
From: Jean Tourrilhes jt

	Please check in the Linux Wireless LAN Howto, you will
find the answer to your question.
	Ciao...

	Jean

Idea found working PCMCIA parameters, now facing driver installation

Re: Sad Compaq WL200 Wireless PCI Card not supported? (Patrick Neill)
Date: 2000, May 09
From: Patrick Neill Patrick

In config.opts (Suse Linux 6.4) this did the trick. Mind you that I had to run the card in WIN98 first to find out the parameters.

include port 0x180-0x1bf include memory 0xc0000-0xfffff include memory 0xfccc-0xfccf exclude irq4 exclude irq3 exclude irq12

The card identifies as (cardctl ident): Socket 0: product info: "Compaq", "WL200_11Mbps_Wireless_PCI_Card", "", "" manfid: 0x0138, 0x0002 function: 6 (network)

Last time I tried to install the driver package from absoval.com the install stopped because my kernel source directory apparently had a wrong date. Does anyone have an idea how I could avoid this next time?

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

None Need a specific, detailed description of your problem

Re: Sad Problem with Lucent PCI-PCMCIA-adapter (Tommy Svensson)
Date: 2000, May 09
From: David Hinds <dhinds@pcmcia.sourceforge.org>

It might be useful to post the system log messages for the driver
combination that is supposed to work (the 3.1.14 or newer PCMCIA
drivers, and the 6.01BETA wavelan_cs driver).  You say you get errors
about "missing resources etc", but I'm not clairvoyant.

-- Dave

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'

None Well, if the module can't be loaded, that would do it

Re: Question PrismII based card, WLAN device not showing up in ifconfig (Patrick Neill)
Date: 2000, May 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I'm not familiar with the absoval PrismII driver.  Is this new?  I
also can't seem to even connect to the ftp.absoval.com server.  Your
best bet would probably be to contact Mark Matthews, the driver
author, for help with this.

-- Dave

Question Compaq WL100 WLAN Card

Re: Question PrismII based card, WLAN device not showing up in ifconfig (Patrick Neill)
Date: 2000, Aug 11
From: Talei McLeod talei

Hi Patrick,

I see that you are using the WL100 wlan card.

I am tring to get this card working without much success.

Could you please tell me what entries you added/changed in the config.opts file to get this card working ?

Thanks very much, Talei.

Sad Also greiving with a Compaq WL200, Has any one made one work??

Re: Question PrismII based card, WLAN device not showing up in ifconfig (Patrick Neill)
Date: 2000, Aug 22
From: harry campigli harryc

I had the same problem as you and found it corrected on a later compile. Try make clean and cat the output to a file or watch the subsequent compiles. It will show up in the messages if it cant find one of the souces of your kernel or pcmcia, or the make configs don't match the installed kernel or pcmcia pakage during compile of wlan-ng. I cant get it to work either but only have 3 minor messages in the compile which dont seem to matter. One is related to scan, I cant remember the details now. The problem now is getting the card to actually work!!

Sorry I cant rememeber exacly how I got arround that one but mines all up except I cant get the cards to talk. No matter what i put in the wlan config.

I have 2 of these cursed compaq cards and wish I could have could have found samsung cards when brought them!! I hear from Mark compaq use the firm ware a bit different. I should have know as Ive been caught with compaq compatibility before.

I would dearly love to hear from any one who has a WL200 on air with linux and get a copy of their config file.

good luck harry@gpssys.com

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

None I don't think this driver supports multiple cards

Re: Sad Welp having 2 ISA cards and 2 Wavelan Cards in one Linux box Don't Work! (John Savage)
Date: 2000, May 17
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Contact the driver author for more information.  But I don't think
this can work; the driver doesn't have a way of passing in multiple
sets of settings for multiple Wavelan cards.

-- Dave

More I think it's right...

Re: None I don't think this driver supports multiple cards (David Hinds)
Date: 2000, May 17
From: Jean Tourrilhes jt

Have a look at : http://pcmcia.sourceforge.org/cgi-bin/HyperNews/get/pcmcia/wireless/11.html

	The solution is to use the Lucent driver (called wavelan2_cs).

	Jean

Question Ok next question then how do you switch from the module ....

Re: More I think it's right... (Jean Tourrilhes)
Date: 2000, May 17
From: John Savage admin

How do you switch from the mudule wvlan_cs.o to use the wavelan2_cs.c there is no module made in the install for it. JohnS

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 !

None The CardBus bridge seems to be invisible

Re: Question Pci adaptor + wavelan pc card on Dell 2400 : unknown PCI interrupt router
Date: 2000, May 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Funny, I got an email from someone trying to use the same card in a
Dell PowerEdge 2400, but they got a different error message from the
i82365 driver.  You might want to see if your BIOS has any settings
related to "Plug and Play OS support", or things that sound like they
might affect how PCI devices are configured.

The unknown interrupt router is a problem but it is probably the
lesser of your problems.

The more serious problem is that the TI1225 bridge is not even showing
up in the PCI device list.  There is no way that the PCMCIA drivers
can find your bridge, if the Linux PCI subsystem doesn't know that it
exists.

Contact the PCI driver maintainer, Martin Mares, mj@ucw.cz, and he
might have some ideas.

-- Dave

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

None That doesn't sound like a resource issue

Re: Question ThinkPad 600 and Wavelan card (Jonathon Fletcher)
Date: 2000, May 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

If you are receiving data, you almost certainly don't have an irq/port
problem.  You can check /proc/interrupts to see if the interrupt count
is incrementing for the Wavelan device; and "ifconfig" will show
whether the driver thinks that packets are being sent and received.
Are you sure your network settings are correct?

-- Dave

None Asus P3B-F and Ricoh RL5C475 - mixed irq ?

Re: None That doesn't sound like a resource issue (David Hinds)
Date: 2000, May 19
From: Jonathon Fletcher jonathon

I did a little more checking and I now believe that the problem is not
with the ThinkPad - it is with the router box on the other card. Maybe
rename this thread

The router box is a generic PIII machine, Asus p3b-f motherboard (6 pci
variant) and the pcmcia adapter is a Ricoh RL5C475 in slot 2 (slot 2 has
a dedicated irq).

When I boot the router (rh 6.2, pcmcia 3.1.13 with debug up at #3) I get
the following message:

Linux PCMCIA Card Services 3.1.13
  kernel build: 2.2.14-12 #1 Tue Apr 25 12:31:52 EDT 2000
  options:  [pci] [cardbus] [apm]
PCI routing table version 1.0 at 0xf0e80
  00:0d.0 -> irq 9
  00:04.2 -> irq 9
Intel PCIC probe: 
  Ricoh RL5C475 PCI-to-CardBus at slot 00:0d, mem 0x68000000
    host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 9] [lat 32/176] [bus 32/34]
    PCI irq 9 test failed
    ISA irqs (default) = 3,4,7 polling interval = 1000 ms
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.

card insertion gives me:

wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4
wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de>
wvlan_cs: RequestIRQ: Resource in use
wvlan_cs: hcf_disable(0) returned 0x4
wvlan_cs: hcf_action(HCF_ACT_INT_OFF) returned 0x0
wvlan_cs: hcf_action(HCF_ACT_CARD_OUT) returned 0x0


my config.opts file is:

## begin
include port 0x100-0x4ff, port 0x1000-0x17ff
include memory 0xc0000-0xfffff
include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff
include port 0xa00-0xaff
exclude irq 4
exclude irq 3
exclude irq 7
exclude irq 12
## end

I have no options for loading the i82365 module. When I cat out
/proc/interrupts, irq 9 is not in the list.

Perhaps the cause of the problems is the irq routing (00:04.2 -> irq 9
in boot message). What is this likely to be and how do I go about
disabling it - irq is not listed in /proc/interrupts (and not shown at
the post-bios pre-boot screen).

When I flip into windows 98 and setup the same network informatation
(10.10.10.2/24) I can ping between the cards - everything works - apart
from the choice of OS. Looking at the properties of the card gives me a
port range of 0x1000-0x103f, an irq of 9, and a memory slice of
10000000-10000fff.

Please let me know if I need to give more information to work this one
out.

Sincerely,

Jonathon

-- 
  Jonathon Fletcher
  jonathon.fletcher@pobox.com

None Several PCI issues here

Re: None Asus P3B-F and Ricoh RL5C475 - mixed irq ? (Jonathon Fletcher)
Date: 2000, May 19
From: David Hinds <dhinds@pcmcia.sourceforge.org>

>     PCI irq 9 test failed

This is your problem.  The PCI interrupt test is unreliable for Ricoh
CardBus bridges.  This is fixed in the 3.1.15 PCMCIA drivers.  With
those drivers, you should be able to get the card to use the PCI irq
(irq 9).

Also, you will need to get the 6.01 beta version of Lucent's driver
for the Wavelan card, from sourceforge.org in /pcmcia/contrib.  The
wvlan_cs driver does not work if the card is configured to use a PCI
interrupt.

-- Dave

None Re: Several PCI issues here

Re: None Several PCI issues here (David Hinds)
Date: 2000, May 19
From: Jonathon Fletcher jonathon

Yay !

  Thank you David. Using 3.1.15 does work much better. I now have 11Mb
connectivity between the two cards.

  Both cards have taken pci irq 9. Your comment about the drivers
puzzles me - the cards seem to be behaving sensibly with the wvlan_cs
driver (1.04). I have the card firmware down at 4.52 (to stop wvlan_cs
choking on the tx threshold) - does the 6.01b driver requirement issue
relate to any firmware differences. I only ask because the cards seem to
be working great with what I believe are pci irqs. Am I likely to be
mistaking my irq types ?

Thanks again,

Jonathon

-- 
  Jonathon Fletcher
  jonathon.fletcher@pobox.com

None Hmmm, I might be wrong about the wvlan_cs driver

Re: None Re: Several PCI issues here (Jonathon Fletcher)
Date: 2000, May 19
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The Lucent driver required a patch to work with PCI-to-CardBus card
readers and I thought I had a report of trouble with the wvlan_cs
driver in this configuration that went away with the new Lucent
driver.  But I haven't actually used either driver (and don't have any
Wavelan cards) so that information may have been incorrect.

If the cards seem to work fine, I wouldn't worry about it.  The older
Lucent driver would wedge the system at card configuration time, so
you would know it if you had the same issue.

-- Dave

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

None I had same problem, but it's working now (sort of)

Re: Question WebGear/RayLink card installs/ifconfig but no ping (Kelly Murray)
Date: 2000, May 27
From: Greg Mohr gmohr

I have the same cards, and mine was working fine with the RPM version of ray_cs built for Red Hat 6.1. I know I had to make certain to set the ESSID and change the translate setting on the config line to get things to work, but the 6.1 RPM worked like a charm.

Then I upgraded to Red Hat 6.2, and my Aviator quit working. I figured I needed to rebuild the module since the kernel changed, so I downloaded pcmcia-cs-3.1.14 and built it, but I noticed the same thing you did: the card was recognized, and the diagnostics said I could send but not receive. I noticed the config files moved around, so I cut and pasted my config line into config.opts, and then every time I would try to ping, either 0 or at most 1 ping would get through. I ejected the card, started and stopped card services, reinserted the card, and it started working.

Now every time I reboot my laptop with the Aviator in the PC slot, I have to eject it and reinsert it before it will work (and something I still have to restart card services). So something isn't quite right. I'll be happy to investigate further if someone can give me a direction to start looking.

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

None It is a bug in the suggested ray_cs options

Re: Ok Debugging not compiled into ray_cs module (CS 3.1.15). Fixed (Cathelijne Hornstra)
Date: 2000, May 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Ok, I'll fix the default config.opts file to not specify a value for
pc_debug: that is certainly a bug.  If you remove that option, then
you don't need to change the Makefile.

-- Dave

None I tried that, but it didn't work

Re: None It is a bug in the suggested ray_cs options (David Hinds)
Date: 2000, May 31
From: Cathelijne Hornstra lijn

Of course that's the first thing I did... But disabling in the config.opts file didn't work for me at all...

Hey, you think I'm going over all of this code of which I know nothing about when it is easily fixed with some switch in an options file? ;-))

Bye,

Cathelijne

None You might want to try it again

Re: None I tried that, but it didn't work (Cathelijne Hornstra)
Date: 2000, May 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I'm fairly certain that the error you reported ("invalid parameter
parm_pc_debug") goes away if you modify config.opts to not specify a
pc_debug= option for the ray_cs module.

I can tell you for a fact that you do not need to turn on debugging in
order to use the ray_cs driver, because I'm doing so right now.

-- Dave

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

None Maybe your setup can't handle unusual interface names

Re: Question WaveLan IEEE, cardmgr do not know wvlan0 interface (viktor safar)
Date: 2000, May 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I don't have any specific experience with this, but it is possible
that either the (old) 2.0.* kernel, or your net tools, can't handle
the unusual "wvlan0" network interface name.  You might have better
luck after upgrading one or both of those.

Also, the wavelan2_cs driver is not "old"; it is just "different".  It
is written and maintained by Lucent, and has more features than the
wvlan_cs driver.  It is not included in the PCMCIA distribution
because it is not completely open source.  If that driver works fine
for you, I'd suggest just using it.

-- Dave

None WaveLan IEEE, cardmgr do not know wvlan0 interface 2

Re: Question WaveLan IEEE, cardmgr do not know wvlan0 interface (viktor safar)
Date: 2000, May 31
From: viktor safar 4roses

Thank You Dave for fast response.

Looks like You have right. Unfortunately we can't upgrade
from kernel 2.0.x to 2.2.x, because of shaper module. (It
works not properly under 2.2.x with aliased interfaces).
And I guess that to change nettools in different kernel
versions is not very smart. There is some differences in
2.2.x ...

Yes, wavelan2_cs is realy not old, it's old only from my
viewpoint, we use it succesfully over 1 year :-). But now
we need to settle two WaveLan cards in one linux box, one
in ad-hoc and one in BSS mode. And this works with drivers
from Andreas (according technician from Lucent Prague, CZ).

On pages of Andreas stands, that his drivers should work
with kernel 2.0.x ...

I've tried, to use a eth=1 switch with wvlan_cs.o driver,
which is designed to turn off the special naming from
"wvlan0" into obvious "eth0".
The result was that the driver registers no interface !!!

The driver yells:
 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
 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 '
funny, isn't it?

I need some suggestion, how to say to linux, that wvlan0
is a valid intarface. 

thanks again

viktor@salamon.sk

None Whoops, my mistake...

Re: None WaveLan IEEE, cardmgr do not know wvlan0 interface 2 (viktor safar)
Date: 2000, May 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Ok, after checking out another 2.0.* kernel bug report, I know what's
wrong; it isn't an issue with the wvlan_cs driver at all, it is a bug
in the 3.1.15 PCMCIA drivers that only shows up on 2.0.* kernels.

Try the 31-May-00 beta on sourceforge.org in /pcmcia/NEW.

-- Dave

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.

Idea UDP over Wireless == not that great

Re: Question NFS over Wavelan (Rui-Tao Dong)
Date: 2000, May 31
From: Jean Tourrilhes jt

	Most 802.11 MAC protocol are optimised  for TCP
traffic. For example, in my opinion, the number of MAC retries
in the Wavelan is not sufficient for UDP. And let's not forget
about broadcast which is totally crap over Wireless...
	And guess what ? Sun designed NFS over UDP...
	Solution ? Use NFSv3, aka NFS over TCP...

	Jean

None You might try playing with the MTU for the interface

Re: Question NFS over Wavelan (Rui-Tao Dong)
Date: 2000, May 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Some of this might be ameliorated by making the MTU (maximum transfer
unit) for the wireless interface smaller.  You should get fewer lost
packets if the packets are smaller.  The default ethernet MTU is
around 1500 bytes; you can say "ifconfig eth0 mtu XXX" to set a
smaller value.

A smaller MTU will give somewhat lower peak performance, however.

-- Dave

More Slow but no hanging

Re: None You might try playing with the MTU for the interface (David Hinds)
Date: 2000, Jun 01
From: Rui-Tao Dong rdong

I tried setting MTU to 552 and 296.  It works OK at 552,
so I leave it there.  I still need to figure out how to run
NFS over TCP.

BTW, I got a lot of invalid:misc from iwconfig.  Is that
normal?  The data rate drops from 11M from time to time. 
On certain channels, it can barely stay at 2M.  Are there
any hints and tips on tuning the performance?

I am using Andreas Neuhaus <andy@fasta.fh-dortmund.de>'s
wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4.   (Lucent
doesn't have a driver for Alpha.)

The iwconfig log is below.

wvlan0    IEEE 802.11-DS  ESSID:"non-specified SSID !!"  Nickname:"HERMES I" 
          Frequency:2.437GHz  Sensitivity:1/3  Mode:Ad-Hoc   
          Access Point: 00:00:00:00:00:00 
          Bit Rate:5.5Mb/s   RTS thr:off   Fragment thr:off    
          Encryption key:off 
          Power Management:off 
          Link quality:9/92  Signal level:-87 dBm  Noise level:-96 dBm 
          Rx invalid nwid:0  invalid crypt:0  invalid misc:221067 

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

None More info would help... but...

Re: Question WaveLan PCI adapter wierdness (Neil Radisch)
Date: 2000, Jun 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> 
> that can't be right, can it?

For the Wavelan PCI adapters, you must:

- use current PCMCIA drivers
- use the 6.0.1 beta wavelan2_cs driver from Lucent
- specify "irq_mode=0" for the i82365 driver module

-- Dave

More Did that, didn't help

Re: None More info would help... but... (David Hinds)
Date: 2000, Jun 01
From: Neil Radisch nradisch

Didn't help. The logs show a complete inability to find a PCI interrupt. Even if I specify them with pci_int_list=... it just fails.

Below is the result of lspci -vv and my start logs

BTW, perhaps it has something to do with my motherboard. It's a Tyan Tomcat. Intel i810 chipset with no ISA slots (PC99 compatible and all that).

00:00.0 Host bridge: Intel Corporation 82810-DC100 GMCH [Graphics Memory Controller Hub] (rev 03)
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
	Latency: 0 set

00:01.0 VGA compatible controller: Intel Corporation 82810-DC100 CGC [Chipset Graphics Controller] (rev 03) (prog-if 00 [VGA])
	Subsystem: Intel Corporation: Unknown device 0200
	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: 0 set
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at f8000000 (32-bit, prefetchable)
	Region 1: Memory at ffe80000 (32-bit, non-prefetchable)
	Capabilities: [dc] Power Management version 1
		Flags: PMEClk- AuxPwr- DSI+ D1- D2- PME-
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:1e.0 PCI bridge: Intel Corporation 82801AA 82810 PCI Bridge (rev 02) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0 set
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
	I/O behind bridge: 0000d000-0000dfff
	Memory behind bridge: ffc00000-ffcfffff
	Prefetchable memory behind bridge: f6a00000-f6afffff
	BridgeCtl: Parity+ SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-

00:1f.0 ISA bridge: Intel Corporation 82801AA 82810 Chipset ISA Bridge (LPC) (rev 02)
	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: 0 set

00:1f.1 IDE interface: Intel Corporation 82801AA 82810 Chipset IDE (rev 02) (prog-if 80 [Master])
	Subsystem: Intel Corporation: Unknown device 2411
	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: 0 set
	Region 4: I/O ports at ffa0

00:1f.2 USB Controller: Intel Corporation 82801AA 82810 Chipset USB (rev 02) (prog-if 00 [UHCI])
	Subsystem: Intel Corporation: Unknown device 2412
	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: 0 set
	Interrupt: pin D routed to IRQ 9
	Region 4: I/O ports at ef80

00:1f.3 SMBus: Intel Corporation 82801AA 82810 Chipset SMBus (rev 02)
	Subsystem: Intel Corporation: Unknown device 2413
	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 B routed to IRQ 10
	Region 4: I/O ports at efa0

00:1f.5 Multimedia audio controller: Intel Corporation 82801AA 82810 AC'97 Audio (rev 02)
	Subsystem: Analog Devices: Unknown device 5340
	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: 0 set
	Interrupt: pin B routed to IRQ 10
	Region 0: I/O ports at e800
	Region 1: I/O ports at ef00

01:04.0 Ethernet controller: Lite-On Communications Inc: Unknown device c115 (rev 25)
	Subsystem: Lite-On Communications Inc: Unknown device c001
	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: 8 min, 56 max, 64 set, cache line size 08
	Interrupt: pin A routed to IRQ 11
	Region 0: I/O ports at d800
	Region 1: Memory at ffcfff00 (32-bit, non-prefetchable)
	Expansion ROM at ffc80000 [disabled]
	Capabilities: [44] Power Management version 1
		Flags: PMEClk- AuxPwr- DSI- D1+ D2+ PME-
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:0a.0 CardBus bridge: Texas Instruments PCI1225 (rev 01)
	Subsystem: SCM Microsystems: Unknown device 2023
	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: 168 set, cache line size 08
	Interrupt: pin A routed to IRQ 0
	Region 0: 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
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
	16-bit legacy interface ports at 0001

01:0a.1 CardBus bridge: Texas Instruments PCI1225 (rev 01)
	Subsystem: SCM Microsystems: Unknown device 2023
	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: 168 set, cache line size 08
	Interrupt: pin A routed to IRQ 0
	Region 0: 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
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
	16-bit legacy interface ports at 0001

May 31 23:10:36 Mozart pcmcia: Starting PCMCIA services:
May 31 23:10:36 Mozart pcmcia:  modules
May 31 23:10:36 Mozart kernel: Linux PCMCIA Card Services 3.1.15 
May 31 23:10:36 Mozart kernel:   kernel build: 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 
May 31 23:10:36 Mozart kernel:   options:  [pci] [cardbus] [apm] 
May 31 23:10:36 Mozart kernel: Intel PCIC probe:  
May 31 23:10:36 Mozart kernel:   TI 1225 rev 01 PCI-to-CardBus at slot 01:0a, mem 0x68000000 
May 31 23:10:36 Mozart kernel:     host opts [0]: [pci only] [no pci irq] [lat 168/176] [bus 32/34] 
May 31 23:10:36 Mozart kernel:     host opts [1]: [pci only] [no pci irq] [lat 168/176] [bus 35/37] 
May 31 23:10:36 Mozart kernel:     *NO* card interrupts, polling interval = 1000 ms 
May 31 23:10:37 Mozart pcmcia:  cardmgr.
May 31 23:10:37 Mozart cardmgr[572]: starting, version is 3.1.15
May 31 23:10:37 Mozart rc: Starting pcmcia succeeded
May 31 23:10:37 Mozart cardmgr[572]: watching 2 sockets
May 31 23:10:37 Mozart kernel: cs: IO port probe 0x1000-0x17ff: clean. 
May 31 23:10:37 Mozart kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x290-0x297 0x300-0x307 0x378-0x37f 0x400-0x47f 0x4d0-0x4d7 
May 31 23:10:37 Mozart kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
May 31 23:10:37 Mozart inet: inetd startup succeeded
May 31 23:10:37 Mozart lpd[600]: restarted
May 31 23:10:37 Mozart lpd: lpd startup succeeded
May 31 23:10:37 Mozart cardmgr[572]: initializing socket 0
May 31 23:10:37 Mozart cardmgr[572]: socket 0: Lucent Technologies WaveLAN/IEEE
May 31 23:10:37 Mozart kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. 
May 31 23:10:37 Mozart keytable: Loading keymap: 
May 31 23:10:37 Mozart cardmgr[572]: executing: 'modprobe wavelan2_cs port_type=3'
May 31 23:10:37 Mozart kernel: wavelan2_cs: RequestIRQ: Resource in use 
May 31 23:10:38 Mozart keytable: Loading /usr/lib/kbd/keymaps/i386/qwerty/us.kmap.gz
May 31 23:10:38 Mozart keytable: Loading system font: 
May 31 23:10:38 Mozart rc: Starting keytable succeeded
May 31 23:10:38 Mozart cardmgr[572]: get dev info on socket 0 failed: Resource temporarily unavailable
May 31 23:10:39 Mozart sendmail: sendmail startup succeeded

More more info dump_pirq

Re: None More info would help... but... (David Hinds)
Date: 2000, Jun 01
From: Neil Radisch nradisch

dump_pirq says no PCI interrupt routing table found, and no interrupt routers found.

Neil

Ok Problem solved

Re: None More info would help... but... (David Hinds)
Date: 2000, Jun 01
From: Neil Radisch nradisch

I had to use both pci_irq_list=11,11 irq_mode=0

and swap PCI slots with the wavelan adapter and my other network card.

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

Sad wvlan_cs vs wavelan2_cs

Re: Question Wavelan IEEE problems... (Avijit Banerjee)
Date: 2000, Jun 02
From: Jean Tourrilhes jt

  Hi,

  As I explain in my howto, each Wavelan IEEE driver has
its strength and its weakness...

> One has to do with the wavelan2_cs driver from lucent. It
> misreports the link quality stats.

  Wireless Extensions are far more advanced in wvlan_cs,
and I know that many neat WE features are not implemented in
wavelan2_cs. It's just the case of cut'n'paste my code from
one driver to another, but it seem that nobody at Lucent is
able to do this simple task...

> 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):

  There are known issues with firmware 6.X, but it
should work with firmware 4.X. Please try to use wvlan0 as the
interface name, and give us a lot more info on what's
happening (like messages in the log).

  Jean

Feedback Here's more info...

Re: Sad wvlan_cs vs wavelan2_cs (Jean Tourrilhes)
Date: 2000, Jun 02
From: Avijit Banerjee avi

Thank you for you quick response.

>   As I explain in my howto, each Wavelan IEEE driver has
> its strength and its weakness...

I've read your howto... it got me up and running with the wavelan2_cs driver.... until I found out the link stats don't work...

>   Wireless Extensions are far more advanced in wvlan_cs,
> and I know that many neat WE features are not implemented in
> wavelan2_cs. It's just the case of cut'n'paste my code from
> one driver to another, but it seem that nobody at Lucent is
> able to do this simple task...

>   There are known issues with firmware 6.X, but it
> should work with firmware 4.X. Please try to use wvlan0 as >the
> interface name, and give us a lot more info on what's
> happening (like messages in the log).

at boot time, log (/var/log/messages) showed:

Linux PCMCIA Card Services 3.1.15
  kernel build: 2.2.13 #127 Thu Oct 21 13:13:20 CDT 1999
  options: [pci] [cardbus]
PCI routing table version 1.0 at 0xfdee0
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 (scanned) = 4,5,7,15 polling interval = 1000ms
cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x290-0x297 0x370-0x37f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.

I do the following: insmod /lib/modules/2.2.13/pcmcia/wvlan_cs.o port_type=3 station_name=mypc

and get the following in the log (/var/log/messages):

wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4
wvlan_cs: (c) Adreas Neuhaus <andy@fasta.fh-dortmund.de>

that's it... In addition, trying to do "ifconfig wvlan0 up" gives me a "wvlan0: No such device"... and doing "iwconfig wvlan0" gives me "wvlan0 no wireless extensions."

Is there more you need? what am I doing wrong here...

FYI:

kernel: 2.2.13 (slackware 7.0 distro), Card Services: 3.1.15, Firmware Version: 4.52

Thanks again

Avijit

None You should not insmod the driver by hand

Re: Feedback Here's more info... (Avijit Banerjee)
Date: 2000, Jun 02
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Fri, Jun 02, 2000 at 11:28:56AM -0700, Avijit Banerjee wrote:
> 
> I do the following: insmod /lib/modules/2.2.13/pcmcia/wvlan_cs.o
> port_type=3 station_name=mypc

You can't just insmod the wvlan_cs driver.  You have to modify
/etc/pcmcia/config to indicate that wvlan_cs should be bound to your
card.

The way PCMCIA modules work... loading the module by itself has no
effect.  When a card is inserted, the cardmgr daemon looks it up in
the config file and tells the PCMCIA subsystem that "card X needs
driver Y", so when driver Y is loaded, the PCMCIA subsystem tells it
to deal with card X.

It sounds like your /etc/pcmcia/config file still says that your card
should be bound to the wavelan2_cs driver.

-- Dave

Ok Problem Solved!

Re: None You should not insmod the driver by hand (David Hinds)
Date: 2000, Jun 02
From: Avijit Banerjee avi

> You can't just insmod the wvlan_cs driver.  You have to modify
> /etc/pcmcia/config to indicate that wvlan_cs should be bound >to your
 card.

That particular file was fine, it *did* say that the card was bound to the wvlan_cs driver. However, the culprit seems to be a little file in /etc/pcmcia. It's called wavelan2_cs.conf. Upon removal and running /etc/rc.d/rc.pcmcia restart, the card was recognized properly and the driver installed and wvlan0 interface showed up using ifconfig! (sorry for the run-on sentence).

To check that this was indeed the culprit, what I actually did was to rename the wavelan2_cs.conf file (without that .conf part basically) and restarted the card services. Everything worked all peachy. Then I changed the name back to the original and restarted card services. Bingo! I got a high then a low beep.... Then I decided to delete the file altogether, and restart card services, and again, everything was all peachy.

> The way PCMCIA modules work... loading the module by itself has no
> effect.  When a card is inserted, the cardmgr daemon looks it up in
> the config file and tells the PCMCIA subsystem that "card X needs
> driver Y", so when driver Y is loaded, the PCMCIA subsystem tells it
> to deal with card X.

Makes sense.

Thank you to Jean and David for your help! This problem had been perplexing me for a little while now... I should've come here much earlier.

Again, Thank you,

Avijit

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 :( ..

None [no pci irq] is the problem

Re: Sad Yet more fun with that PCI -> Orinoco Card (Alan Knowles)
Date: 2000, Jun 07
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> 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

The "[no pci irq]" thing is the bad thing.

What are the messages right before this?  Do you get a message about a
PCI routing table?  What do you get if you run the "dump_pirq" script
in the debug-tools directory?

-- Dave

Ok pcmcia all working

Re: None [no pci irq] is the problem (David Hinds)
Date: 2000, Jun 08
From: Alan Knowles alan_k

as posting to the hypernews email didn't work - after a few emails from david 
- the following line in /etc/pcmcia.conf (debian's config file) made it work!
  CORE_OPTS="cb_pci_irq=11"

note that the wvlan_cs (the Open source driver DOES work!!) and I can now ping both ways :)

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.

None Fishy modules.conf setup??

Re: Sad Problems with 3.1.15 + wavelan2_cs driver (Bjorn Knutsson)
Date: 2000, Jun 08
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Thu, Jun 08, 2000 at 04:39:29AM -0700, Bjorn Knutsson wrote:

>  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 

Well it certainly asked for wavelan2_cs to be loaded.

The only thing I can think of is that you've got a line in
/etc/modules.conf that aliases wavelan2_cs to wvlan_cs.  The 3.1.15
drivers use modprobe by default so aliases will be followed... but
3.1.14 uses insmod.  As for where the alias came from, you've got me.

-- Dave

Disagree No fish in my conf.modules.

Re: None Fishy modules.conf setup?? (David Hinds)
Date: 2000, Jun 08
From: Bjorn Knutsson bjorn

I wish it was that simple, but my conf.modules is fishless. It does not deal with anything related to PCMCIA modules, only sound and tpctl (Thinkpad control program) modules.

And don't forget: cardmgr died when the card was inserted. If it was only a broken alias, I would hope that cardmgr would be robust enough to survive that.

If there are any additional things you want me to do, I'll be happy to experiment.

None Re: Disagree: No fish in my conf.modules.

Re: Disagree No fish in my conf.modules. (Bjorn Knutsson)
Date: 2000, Jun 09
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I would try issuing that modprobe command by hand, adding a "-v", and
see what it does.

The log doesn't seem to include any hints about how/when cardmgr might
have died.  I guess you just noticed it wasn't running any more after
you inserted the card?

I guess I'd also look at /lib/modules/.../modules.dep and examine the
dependencies for wavelan2_cs.o.

-- Dave

News Same old problem, new pcmcia_cs-version.

Re: None Re: Disagree: No fish in my conf.modules. (David Hinds)
Date: 2000, Jul 18
From: Bjorn Knutsson bjorn

I'm sorry about not getting back about the problem, but I was swamped with work.

I just installed pcmcia-cs 3.1.18 + wavelan2_cs 6.01BETA from contrib, and my troubles continue. When I insert the Wavelan card, cardmgr dies.

> I would try issuing that modprobe command by hand, adding a "-v", and see what it does.

Loading the module is not a problem. It just echos the insmod-line and nothing more.

> The log doesn't seem to include any hints about how/when cardmgr might have died. I guess you just noticed it wasn't running any more after you inserted the card?

It now definitely dies at the point where it loads the module. It now logs no more messages after the modprobe for wavelan2_cs, and checking the system immediately after, the wavelan2_cs module is loaded, and cardmgr is not around anymore.

> I guess I'd also look at /lib/modules/.../modules.dep and examine the dependencies for wavelan2_cs.o.

No problems there either, from what I can see.

I have experimented some more. This is what happens now:

If I insert a card, say my old 3c562C, it configures OK. So I unplug it, and insert my Wavelan. It comes to the modprobe wavelan2_cs, and then I see no more messages in the logs (I run cardmgr with -v). And looking around, cardmgr is no longer running. Now, if I at this point manually run cardmgr -v -f, it will complain about "could not adjust resource" for memory and IO ports, but will then initialize socket 0 and correctly configure the wavelan2_cs driver and everything is fine.

Remove all cards and restart pcmcia. I now insert my 3c562c in socket 0. It configures OK. I then insert the Wavelan in socket 1. cardmgr dies, as before, after the modprobe. I, again, run 'cardmgr -v -f'. Lots of "could not adjust resource" as before, but the card in socket 0 is now identified as "Anonymous Memory". The wavelan2_cs driver is again configured correctly, and everything is fine with the wavelan card.

So to conclude: cardmgr seems to die when or soon after the modprobe for wavelan2_cs is issued. It seems that it will configure correctly when the module is already loaded (and whatever else cardmgr may have node). I did, however, try to modprobe the module and then insert the card, but then my machine locked up.

Here's the log:

Jul 18 17:07:14 foobar cardmgr[480]: initializing socket 0
Jul 18 17:07:14 foobar cardmgr[480]: socket 0: Lucent Technologies WaveLAN/IEEE
Jul 18 17:07:14 foobar kernel: cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0ffffff 
Jul 18 17:07:14 foobar kernel: cs: memory probe 0x60000000-0x60ffffff: clean. 
Jul 18 17:07:14 foobar cardmgr[480]:   product info: "Lucent Technologies", "WaveLAN/IEEE", "Version 01.01", ""
Jul 18 17:07:14 foobar cardmgr[480]:   manfid: 0x0156, 0x0002  function: 6 (network)
Jul 18 17:07:14 foobar cardmgr[480]: 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\"'

Restarted cardmgr:

Jul 18 17:07:31 foobar cardmgr[625]: starting, version is 3.1.18
Jul 18 17:07:31 foobar cardmgr[625]: watching 2 sockets
Jul 18 17:07:31 foobar cardmgr[625]: could not adjust resource: IO ports 0xc00-0xcff: Device or resource busy
Jul 18 17:07:31 foobar cardmgr[625]: could not adjust resource: IO ports 0x800-0x8ff: Device or resource busy
Jul 18 17:07:31 foobar cardmgr[625]: could not adjust resource: IO ports 0x100-0x4ff: Device or resource busy
Jul 18 17:07:31 foobar cardmgr[625]: could not adjust resource: memory 0xc0000-0xfffff: Input/output error
Jul 18 17:07:31 foobar cardmgr[625]: could not adjust resource: memory 0x60000000-0x60ffffff: Input/output error
Jul 18 17:07:31 foobar cardmgr[625]: could not adjust resource: IO ports 0xa00-0xaff: Device or resource busy
Jul 18 17:07:31 foobar cardmgr[625]: initializing socket 0
Jul 18 17:07:31 foobar cardmgr[625]: socket 0: Lucent Technologies WaveLAN/IEEE
Jul 18 17:07:31 foobar cardmgr[625]:   product info: "Lucent Technologies", "WaveLAN/IEEE", "Version 01.01", ""
Jul 18 17:07:31 foobar cardmgr[625]:   manfid: 0x0156, 0x0002  function: 6 (network)
Jul 18 17:07:31 foobar kernel: eth0: WaveLAN/IEEE, io_addr 0x100, irq 3, mac_address xx:xx:xx:xx:xx:xx 
Jul 18 17:07:31 foobar cardmgr[625]: executing: './network start eth0'
Jul 18 17:07:32 foobar pumpd[638]: starting at (uptime 0 days, 0:03:55) Tue Jul 18 17:07:32 2000  
Jul 18 17:07:32 foobar pumpd[638]: configured interface eth0
Jul 18 17:07:32 foobar cardmgr[625]: exiting

(I edited the mac_address)

None Fixed: a really dumb bug

Re: News Same old problem, new pcmcia_cs-version. (Bjorn Knutsson)
Date: 2000, Jul 22
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The bug is fixed in the 21-Jul-00 beta on projects.sourceforge.net in
/pub/pcmcia-cs/NEW.  The long list of module options was overrunning a
fixed-length buffer.

-- Dave

Ok Re: Fixed: a really dumb bug

Re: None Fixed: a really dumb bug (David Hinds)
Date: 2000, Jul 22
From: Bjorn Knutsson bjorn

> The bug is fixed in the 21-Jul-00 beta on projects.sourceforge.net in
> /pub/pcmcia-cs/NEW.  The long list of module options was overrunning a
> fixed-length buffer.

I'm out of office again, but I brought the WaveLAN card this time. I compiled and installed the new version, and it now configures the card properly (well, since I don't have a WaveLAN net around, all I really know is that it gets past the point where cardmgr used to die and it starts DHCP:ing for an address).

Thanks! Great work!

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 :(

None Probably not a tested configuration

Re: Question Wavelan/IEEE and Alpha Linux problem (Mikael Kanto)
Date: 2000, Jun 09
From: David Hinds <dhinds@pcmcia.sourceforge.org>

This driver probably hasn't been tested on the Alpha.  I'd try simple
things like excluding IO ports and interrupts, and I'd try contacting
the driver author to see if he has any ideas.  He may be better able
to localize exactly where the driver is failing.

-- Dave

News Use PPC patch...

Re: None Probably not a tested configuration (David Hinds)
Date: 2000, Jun 12
From: Jean Tourrilhes jt

  It seem that wvlan_cs has trouble with endianness. If I remember well, there is a patch for wvlan_cs to make it work on Power PC platform that fix of lot of endianess issues. Maybe you could try to apply this patch...
  The link should be on my web page...

  Jean

None Alpha is little endian

Re: News Use PPC patch... (Jean Tourrilhes)
Date: 2000, Jun 12
From: David Hinds <dhinds@pcmcia.sourceforge.org>

sorry ;)

-- Dave

Question Link?

Re: News Use PPC patch... (Jean Tourrilhes)
Date: 2000, Jun 13
From: Mikael Kanto mkanto

Where excacly is the link to the PPC patch? I've searched, but can't find it...

More Here...

Re: Question Link? (Mikael Kanto)
Date: 2000, Jun 13
From: Jean Tourrilhes jt

http://www.roelle.com/wvlanPPC/recipe_download.html

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.

Feedback binary driver works in this config

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

I have tested the binary driver- it seems to work ok, although the config /integration with pcmcia tools is not as nice as the GPL one :)

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'

-

None Fixed in 6.01beta driver

Re: Question Wavelan 11 Mb/s Problem (Randy Broman)
Date: 2000, Jun 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>

You have to use the 6.01 beta driver, which is on sourceforge.org in
/pcmcia/contrib.

-- Dave

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

Question version ?

Re: Question Cannot set "mode" with iwconfig on WaveLan IEEE (viktor safar)
Date: 2000, Jun 16
From: Jean Tourrilhes jt

  Which version of iwconfig are you using ? And which version of the kernel are you using ?
  To get "mode", you need wireless tools version 20, which in turn require kernel 2.2.14+.
  And by the way, it seem the the Wavelan firmware has trouble switching from managed to ad-hoc on the fly...

  Jean

Ok Ooops, yes, this is it!

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

Im sorry, that was really the "bug" :-) . We used the older version 1.19 of iwconfig. Looks like with 2.0 works it OK. We have successfully set up two WaveLan IEEE adapters, in one linux together with 3Com Etherlink ISA NIC. The goal is to make a multipoint connection between WavePoint and this linux, and than "retranslate" the connection to another hidden place over second WaveLan in Point-to-point mode. So this linux should work as a cheap mediator to place, where we have no direct connection to WavePoint, and in the same time should be connected to LAN. That is why we need to set up one card Managed and one Ad-Hoc. OK. So, we have not yet set up the second ptp path, thouhgt it will be without difficultiess... The next problem is, that this works only on kernel 2.2.x, and not on 2.0.x. We have set up a shaper on aliased ethernet interfaces, which works for us very fine on 2.0.x. Unfortunatelly, on 2.2.x this works not anymore, but this is not a subject of this list...

The next question is the bridgeing. In Andy's man page to wvlan_cs driver we can read: It's currently not possible to use the WaveLAN/IEEE as a bridge (MAC level). This is not a restricton of the driver, the NIC firmware doesn't allow to send out packets with another source MAC address than its own. OK. How works than this on Wavepoint and Ethernet convertor? Both acts as bridge, with IEEE cards...

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?

None Resource conflict?

Re: Question wvlan_cs: Initialization failed! (Lukas Zimmermann)
Date: 2000, Jun 16
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> kernel: wvlan_cs: wvlan0 Tx timed out! Resetting card
> kernel: wvlan_cs: Initialization failed!

I think my first guess would be an interrupt delivery problem.  Are
you sure that irq 5 is free?  Can you swap things around so the
ethernet card is on irq 5 and the Wavelan card is on the other irq
(which should be ok)?

-- Dave

Disagree Doesn't seem to be a resource conflict.

Re: None Resource conflict? (David Hinds)
Date: 2000, Jun 16
From: Lukas Zimmermann lukas

> I think my first guess would be an interrupt delivery problem.  Are
> you sure that irq 5 is free?  Can you swap things around so the
> ethernet card is on irq 5 and the Wavelan card is on the other irq
> (which should be ok)?

The Wavelan card does the same thing if it uses the same irq and io as the working ethernet card.

None Ok...

Re: Disagree Doesn't seem to be a resource conflict. (Lukas Zimmermann)
Date: 2000, Jun 16
From: David Hinds <dhinds@pcmcia.sourceforge.org>

In that case I'd give the Lucent wavelan2_cs driver a try.

-- Dave

Sad Compilation of wavelan2_cs.c fails

Re: Disagree Doesn't seem to be a resource conflict. (Lukas Zimmermann)
Date: 2000, Jun 19
From: Lukas Zimmermann lukas

 > In that case I'd give the Lucent wavelan2_cs driver a try.

I tried to compile the pcmcia package 3.1.16 with the wavelan2_cs-6.00 on a system with a 2.0.38 kernel. The compilation fails:

wavelan2_cs.c:149: warning: `spin_lock_init' redefined
../include/pcmcia/k_compat.h:136: warning: this is the location of the previous definition
wavelan2_cs.c:153: warning: `capable' redefined
../include/pcmcia/k_compat.h:259: warning: this is the location of the previous definition
wavelan2_cs.c:148: conflicting types for `spinlock_t'
../include/pcmcia/k_compat.h:138: previous declaration of `spinlock_t'

Do you have any hints?
Thanks a lot so far!

Lukas

Ok Compilation succeeded

Re: Sad Compilation of wavelan2_cs.c fails (Lukas Zimmermann)
Date: 2000, Jun 19
From: Lukas Zimmermann lukas

Seems that wavelan2_cs.c defines some things that are already defined in k_compat.h. I removed the respective lines from wavelan2_cs.c.

cardmgr still bails out about missing dependency information for module wavelan2_cs.

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

More More info...

Re: Question Can't boot using WaveLAN ISA Adapter (Alan Ostroff)
Date: 2000, Jun 18
From: Alan Ostroff alan

I tried changing the port address to no avail. I also recompiled pcmcia to use pnp, that didn't help either. My /proc/ioports is:

0000-001f : dma1 0020-003f : pic1 0040-005f : timer 0060-006f : keyboard 0070-007f : rtc 0080-008f : dma page reg 00a0-00bf : pic2 00c0-00df : dma2 00f0-00ff : fpu 01f0-01f7 : ide0 0220-022f : soundblaster 02f8-02ff : serial(auto) 0300-031f : NE2000 0330-0333 : MPU-401 UART 0388-038b : Yamaha OPL3 03c0-03df : vga+ 03f6-03f6 : ide0 03f8-03ff : serial(auto) fc00-fcbe : aic7xxx

I even tried exluding these ranges in the /etc/pcmcia/config.opts. That didn't help either.

Just wondering also why I have PCMCIA and PCMCIA.N services in linuxconf and why there are several *.O files in the /etc/pcmcia directory?

Here's my latest message log: t]n 18 14:05:28 shell1 kernel: Linux PCMCIA Card Services 3.1.16

Jun 18 14:05:28 shell1 kernel:   kernel build: 2.2.14-12 #4 Thu Jun 8 18:30:10 CEST 2000 :05:28 shell1 kernel:   options:  [pci] [cardbus] [apm] [pnp]
Jun 18 14:05:28 shell1 kernel: PnP: PNP BIOS installation structure at 0xc00fa660 n 18 14:05:28 shell1 kernel: PnP: PNP BIOS version 1.0, entry at f0000:a754, dseg at 400 5:28 shell1 kernel: Intel PCIC probe:
Jun 18 14:05:28 shell1 kernel:   Vadem VG-469 rev 00 ISA-to-PCMCIA at port 0x3e0 ofs 0x00 05:28 shell1 kernel:     host opts [0]: none
Jun 18 14:05:28 shell1 kernel:     host opts [1]: none
Jun 18 14:05:28 shell1 kernel:     ISA irqs (scanned) = 9 polling interval = 100Jun 18 14:05:28 shell1 cardmgr[1228]: starting, version is 3.1.16
Jun 18 14:11:39 shell1 syslogd 1.3-3: restart.
Ju

None Re: More: More info...

Re: More More info... (Alan Ostroff)
Date: 2000, Jun 19
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> I even tried exluding these ranges in the /etc/pcmcia/config.opts. That
> didn't help either.

Excluding the ranges in /proc/ioports can never help: PCMCIA knows
about those devices.

> Just wondering also why I have PCMCIA and PCMCIA.N services in linuxconf
> and why there are several *.O files in the /etc/pcmcia directory?

When you upgrade your PCMCIA drivers, some files are automatically
replaced (but backed up as *.O).  The startup script is not replaced;
the new version is installed as pcmcia.N instead, because there are
situations where installing the new one might break things.

-- Dave

Sad No luck...

Re: None Re: More: More info... (David Hinds)
Date: 2000, Jun 19
From: Alan Ostroff alan

I've tried to exlude everything :( Here's my config.opts:

#
# Local PCMCIA Configuration File
#
# System resources available for PCMCIA devices
#
include port 0x100-0x4ff, port 0x1000-0x17ff include memory 0xc0000-0xfffff include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff # exclude prot 0x0090-0x009f

exclude port 0x00e0-0x00ef

exclude port 0x01f8-0x021f

exclude port 0x038c-0x03bf

exclude port 0x03e0-0x03f5

exclude port 0x03f7-0x03f7

exclude port 0x0400-0xfbff

exclude port 0xfcbf-0xffff

#
# 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
# PS/2 Mouse controller port, comment this out if you don't have a PS/2
# based mouse
exclude irq 12 #

I haven't yet tried to insert a pcmcia card. What else can I try? Thanks, Alan

None Re: Sad: No luck...

Re: Sad No luck... (Alan Ostroff)
Date: 2000, Jun 19
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Like I said, excluding things that show up in /proc/ioports is futile:
the drivers are already smart enough to figure out those conflicts.
Your config.opts says:

  include port 0x100-0x4ff, port 0x1000-0x17ff

and I'd try just changing that to one of the following:

  include port 0x100-0x1ff
or
  include port 0x200-0x2ff
or
  include port 0x300-0x3ff

-- Dave

Ok Success

Re: None Re: Sad: No luck... (David Hinds)
Date: 2000, Jun 22
From: Alan Ostroff alan

Including only the range 0x200-0x2ff worked fine.

Much thanks for you help. Glad I bought LNUX :)

Alan

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

None Some things to try

Re: Question card recognition problem with wavelan pcmcia-isa adapter (Arne Michaelsen)
Date: 2000, Jun 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The drivers are scanning the 0xc0000-0xfffff memory region for a
window that is usable for PCMCIA.  If you know about your memory
layout, you can try cutting this window down to something that you are
more sure should be free.  It is defined in /etc/pcmcia/config.opts.

If your BIOS settings have any options for changing the clock speed of
the ISA bus, you could try fiddling with those.

You can also try using:

    PCMCIA_CORE_OPTS="cis_speed=500"

to add some extra wait states.

There is only one other Vadem controller option in the i82365 module,
"cable_mode".  You could try flipping that on, but I don't think that
will make a difference.

-- Dave

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

News AnyPoint == Symphony/SWAP

Re: Idea Intel AnyPoint Wireless (Kelly Murray)
Date: 2000, Jun 19
From: Jean Tourrilhes jt

  As Proxim has hijacked the HomeRF standard, the Symphony line is supposed to migrate sooner or later to SWAP. Intel is a strong supporter of SWAP. Moreover, the Anypoint Pcmcia card just look like a Symphony card from Proxim.
  If you go on my page, you'll find a link to the Symphony driver. However, there is a fair probability that the driver doesn't support these newest cards (ask Dave). USB is probably not supported, because Linux still has some immaturity there...
  If you want solutions that are well supported under Linux, have a look at the list on my web page...

  Jean

Ok Who to ask to get driver info?

Re: News AnyPoint == Symphony/SWAP (Jean Tourrilhes)
Date: 2000, Jun 19
From: Kelly Murray kem

The Symphony seems to have similiar specs.

I am particularly interested in the USB version
of the Intel product, it solves a lot of problems.

Shouldn't it be possible to figure out the USB
interface by watching the USB bus and seeing what 
data is passed back and forth to the device?

Would be much easier if intel just released the 
specs/docs.   No luck finding anyone to even ask.

-Kelly Murray   kem@netnimble.com

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

None A tricky problem

Re: Sad USB and PCMCIA (ray_cs) hangs (Justin Cormack)
Date: 2000, Jun 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

My first guess was also going to be a USB problem, until you said that
the Xircom card does not misbehave this way.

If you hear no beeps, that should mean that the lock-up happens before
the ray_cs driver is loaded or the card is configured.  That is odd,
because the pre-beep actions should be the same for all cards, and the
Xircom card should behave the same. 

My Webgear cards normally don't generate any beeps for several seconds
after card insertion, because the cards take several seconds to signal
"ready".  Maybe there is something subtle about how the USB driver
reacts to the timing of the shared interrupt from the CardBus bridge.

It isn't really addressing the problem, but you could try setting:

    PCIC_OPTS="pci_int=0 pci_csc=0"

in /etc/sysconfig/pcmcia to tell the PCMCIA subsystem not to use PCI
interrupts.  I'm not sure if that will do any good with this Ricoh
bridge; some bridges always generate PCI interrupts whether you like
it or not.

To address the real problem, you would need to pin down exactly where
the kernel lockup happens, using the tips in the PCMCIA-HOWTO.

-- Dave

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

None Looks like it might be a routing issue

Re: Question Can't ping Wavelan/IEEE in ad-hoc mode (Alan Ostroff)
Date: 2000, Jun 22
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Thu, Jun 22, 2000 at 10:34:44AM -0700, Alan Ostroff wrote:
>   
> 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?

Not unless you tell ifconfig what the IP address is.  How would it
know?  (ifconfig is a low level tool; it doesn't read configuration
files, it is what you use to set the IP address)

> 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.

It looks like your linux box also has eth0 configured for the *same*
192.168.0.* network.  You can't do that: your box might be responding
to the wireless pings by sending packets out on eth0, because your
routing is ambiguous.

-- Dave

Sad Routing??

Re: None Looks like it might be a routing issue (David Hinds)
Date: 2000, Jun 22
From: Alan Ostroff alan

Oh-oh. Not really sure how to proceed?  If I bring up wvlan0 with 192.168.1.1 and add a route - something like route add -net 192.168.1.0 netmask 255.255.255.0 wvlan0 I can ping the WIN95 client sucessfully from the linux box and vice-versa.  But IP Masq doesn't work.  

I even tried executing:
/sbin/ipchains -A forward -s 192.168.1.0/14 -j MASQ
in the vain attempt that IP Masq would simply work.

By defining wvlan0 on a different subnet, am I precluding the use of IP Masq?  Is my route table correct?
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.1     *               255.255.255.255 UH    0      0        0 eth0
212.155.245.9   *               255.255.255.255 UH    0      0        0 ppp0
192.168.1.0     *               255.255.255.0   U     0      0        0 wvlan0
192.168.0.0     *               255.255.255.0   U     0      0        0 eth0
127.0.0.0       *               255.0.0.0       U     0      0        0 lo
default         212.155.245.9   0.0.0.0         UG    0      0        0 ppp0    

Not really sure what to do next.
Alan

Idea Hum... ad-hoc in config.opts might help...

Re: Question Can't ping Wavelan/IEEE in ad-hoc mode (Alan Ostroff)
Date: 2000, Jun 22
From: Jean Tourrilhes jt

  My personal experience is the the firmware of the Wavelan is not very happy when switching on the fly from managed mode to ad-hoc mode so close to the card initialisation (so, in essence triggered via wireless.opts).
  On the other hand, all other operation seem to work fine. So, set ad-hoc mode in config.opts by default, and use wireless.opts for all others and to switch to managed mode. That might work better.
  Please tell us if it help...

  Jean

Question Ad-hoc mode

Re: Idea Hum... ad-hoc in config.opts might help... (Jean Tourrilhes)
Date: 2000, Jun 23
From: Alan Ostroff alan

If ad-hoc was correctly initialized, will this allow me to configurate the wvlan0 interface on, say 192.168.0.4, keeping my ethernet adapter on 192.168.0.1 and be able to ping sucessfully to another ad-hoc wavelan adapter running WIN95? My goal is to get IP Masq going through the Wavelan/IEEE interface. This works fine on the ethernet interface now.

Dave suggested that I have a routing problem, so I configured the wvlan0 interface on another subnet - 192.169.1.1. Is this unecessary with ad-hoc mode?

None Jean is leading you astray on this one

Re: Question Ad-hoc mode (Alan Ostroff)
Date: 2000, Jun 23
From: David Hinds <dhinds@pcmcia.sourceforge.org>

No, your problem is with routing, not with the selection of ad-hoc
mode.  (that is confirmed by the fact that the interface works fine
with the same wireless settings when you put it on a different subnet)

-- Dave

Ok Success!

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

By creating two subnets, one for the wvlan0 interface and following the instructions to enable IP Masq with multiple subnets from the IP Masq HOWTO, everything works fine.

Thanks for you help. Cheers, Alan

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

Ok Solved!!!!

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

I used the solution from thread 21 (comment out a couple of lines in wvlan_cs.c),
compiled pcmcia (of course), 2x restarted pcmcia services
and WOW!!

it worked!!!!

(i'm writing this message wireless) :-)))

but i am still interested why it does not work with normal driver.
Anybody some idea???

Leo

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

More More info

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

I would like to add that I am using the Wavelan IEEE card on a desktop with a PCI interface card. The IRQ is getting set to 9. The ifconfig shows correct network parameters that match a working windows box running the same card. It seems like the I am not getting to the eth0 adapter for some reason. The /var/state/pcmcia/stab file show the correct config for the Wavelan card.

Any ideas?

Mike

Ok Solved

Re: Question Wavelan IEEE getting "Destination Host Unreachable" (Mike Bates)
Date: 2000, Jul 01
From: Mike Bates mbates

Well I solved the problem. It seems the system could not resolve the PCI Cardbus IRQ. Once set it worked fined.

Mike

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?

None Interrupt delivery problem, probably

Re: Question Problems with Breezecom Wireless Lan - long ping times
Date: 2000, Jul 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Can you tell if you are getting any interrupts?  (look at
/proc/interrupts).

The PCMCIA drivers in RH 6.2 are not new enough to work with PCI card
docks.  You will need to upgrade to a newer PCMCIA package (3.1.17 is
current) and then specify:

  PCIC_OPTS="irq_mode=0"

in /etc/sysconfig/pcmcia.

-- Dave

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

Feedback Yea, it's not working !!

Re: Question Wavelan/Linux cannot talk to Wavelan/Windows (Mubashir Cheema)
Date: 2000, Aug 04
From: Alex Lam <alex.lam@radiata.com>

Hi !

I have exactly the same problem !!
Did you get your problem solved ?
The can talk via an access point, but not in the
ad-hoc mode.

I suspect it's the network name too.. but...
what can I do ?? 

Alex

Sad me too, it's not working

Re: Question Wavelan/Linux cannot talk to Wavelan/Windows (Mubashir Cheema)
Date: 2000, Oct 17
From: Yaddi K Rustandi yaddi

Hi all =)

I have the same problem,
I use Orinoco card, it's work in mode Ad-Hoc at Windows and windows, but not work if i use in windows and Linux.

Is this Windows and Linux problem ?
or only My setting problem ?

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

Sad I am having similar problems, and many more also.

Re: Question 2 wavelan2_cs cards in one machine (Wynand Theunissen)
Date: 2000, Jul 05
From: R J Delmar Delmar

Yeah, I have been stumbling through the same problems myself. I thought maybe the idea was to have two card sections in the wireless.opts but I cant get that to do anything at all. Any settings I try to use in the wireless.opts file seem to get ignored. The only settings that seem to effect card operation are in config.opts. Besides, there doesn't seem to be any way of setting up a second card in the network.opts either.

My problem is, I need to get two WaveLan/IEEE PCMCIA cards (in two seperate PCI PCMCIA adaptors) in the same system, working with seperate freq/channel/security settings. My network topology allows me to have the same IP info on both cards, because the links are point to point and Linux doesn't care if u set it up right. They seem to spit at each other and do wierd things due to them using the same channel/freq settings. I would like to seperate these at least. Whats the easiest way to do this? I am running kernel 2.2.16 with pcmcia-cs 3.1.16-2. I have tried nabbing the later pcmcia-cs packages and installing these to see if there is extra functionality, but the system totally locks up, with only 1 card let alone 2, when ever pcmcia services are started. Another question, if the encryption KEY feature is supported, when I specify the KEY, is this locked into the card so I can remove this piece of text once the card/s have been initialized with the key?. What modes should the cards be used in for PtP links?

Lastly, someone flashed one of the handful of cards we have, with the latest firmware update which aparantly, should work with the latest drivers.. 6.0 or something? I tried re-compiling the pcmcia-cs 3.1.16-2 and latest pcmcia-cs packages with these new drivers. They lockup the system with any of the cards. With the current pcmcia-cs 3.1.16-2 which works fine, the flashed card fails to initialize.

Lotsa problems for me :( and many hours getting nowhere.

TIA for any help.

Delmar

Feedback 2 card hassles

Re: Sad I am having similar problems, and many more also. (R J Delmar)
Date: 2000, Jul 05
From: Wynand Theunissen Masked

You should try getting pcmcia-cs-3.1.17 and the wavelan2_cs_BETA6.01 package. 

Compiled and installed fine for me.

In the network.opts you can allocate IP's according to the cards hardware address (Its in the HOWTO)... the problem is the wavelan2_cs needs to be installed with the network_name option. You can't seem to do that afterwards. Might be able to do it with iwconfig afterwards but its not a very clean solution.

I'm trying to setup these machines as routers .... and this is causing a major problem for me at the moment. 

Does anyone know if you can move the network_name to the wireless.opts file ?

Wynand Theunissen

None 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.

None 2xPCMCIA WaveLan cards working great in the same system

Re: None 2xPCMCIA WaveLan cards working great in the same system (R J Delmar)
Date: 2000, Jul 05
From: Wynand Theunissen Masked

Yeah I managed to get the 2 cards using their own network settings via the networks.opts BUT

the wavelan2_cs doesnt support many of the wireless extensions.

for example you cannot do:
#iwconfig eth2 essid test
SIOCSIWESSID: Operation not supported

Thus it seems to me you can ONLY set the network name when the drives is insmod'd which is very lame.
Both cards are the same so they both get insmod'd with the same module options.

I have the following in my /etc/pcmcia/config.opts:

module "wavelan2_cs" opts "network_name=Test station_name=MyWorkStation"

This Machines needs to be used as a router via these 2 interfaces and I need to get the interfaces setup with different network names and channels.

If anyone knows how to get past this one .. please contact me

Wynand Theunissen

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

Question Ping time ?

Re: Sad Lucent PCI/PCMCIA adapter + Wavelan IEEE silver (Douglas S. J. De Couto)
Date: 2000, Jul 13
From: Jean Tourrilhes jt

  What do you mean by poor ping time ? It sounds to me like an interrupt problem in your configuration...

  Jean

None Need more information

Re: Sad Lucent PCI/PCMCIA adapter + Wavelan IEEE silver (Douglas S. J. De Couto)
Date: 2000, Jul 13
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> PCIC_OPTS="cb_pci_irq=11" 

The cb_pci_irq parameter goes in CORE_OPTS.

> PCIC_OPTS="pci_irq_list=11,11 irq_mode=0"

I think I need to see the startup messages from the PCMCIA modules
with no special PCIC_OPTS or CORE_OPTS settings.  I would also want to
see the output of the "dump_pirq" script from the debug-tools
directory.

Are you just guessing that this card's PCI interrupt is hooked up to
irq 11?

-- Dave

More more info.

Re: None Need more information (David Hinds)
Date: 2000, Jul 13
From: Douglas S. J. De Couto decouto

hi,

here is some more output and information.  i also wanted to
say thanks for having such good and extensive documentation.  

fyi, by ``long ping times'' in my previous message, i meant
~4000 milliseconds or failure when pinging another wavelan.

i also had tx timeouts with a pcmcia ethernet card using the gpl driver.

here are messages from `pcmcia start' and no pcmcia card
inserted.  there are no options set in config.opts for 
CORE_OPTS or PCIC_OPTS, and i am using the lucent driver:


Jul 13 16:15:12 bermuda kernel: Linux PCMCIA Card Services 3.1.18 
Jul 13 16:15:12 bermuda kernel:   kernel build: 2.2.14 #10 SMP Wed Apr 19 16:07:14 EDT 2000 
Jul 13 16:15:12 bermuda kernel:   options:  [pci] [cardbus] [pnp] 
Jul 13 16:15:12 bermuda kernel: PCI routing table version 1.0 at 0xfdf00 
Jul 13 16:15:12 bermuda kernel: PnP: PNP BIOS installation structure at 0xc00f6cd0 
Jul 13 16:15:12 bermuda kernel: PnP: PNP BIOS version 1.0, entry at f0000:a89e, dseg at 400 
Jul 13 16:15:12 bermuda kernel: Intel PCIC probe:  
Jul 13 16:15:12 bermuda kernel:   TI 1225 rev 01 PCI-to-CardBus at slot 00:0b, mem 0x68000000 
Jul 13 16:15:12 bermuda kernel:     host opts [0]: [isa irq] [no pci irq] [lat 168/176] [bus 32/34] 
Jul 13 16:15:12 bermuda kernel:     host opts [1]: [isa irq] [no pci irq] [lat 168/176] [bus 35/37] 
Jul 13 16:15:12 bermuda kernel:     ISA irqs (default) = 5,9,10,11,15 polling interval = 1000 ms 
Jul 13 16:15:12 bermuda cardmgr[2716]: starting, version is 3.1.18
Jul 13 16:15:12 bermuda cardmgr[2716]: watching 2 sockets
Jul 13 16:15:12 bermuda kernel: cs: IO port probe 0x1000-0x13ff: clean. 
Jul 13 16:15:12 bermuda kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x370-0x37f 
Jul 13 16:15:12 bermuda kernel: cs: IO port probe 0x0a00-0x0aff: clean. 


and inserting the wavelan card (pcmcia.opts set to use dhcp):

Jul 13 16:16:23 bermuda cardmgr[2716]: initializing socket 0
Jul 13 16:16:23 bermuda cardmgr[2716]: socket 0: Lucent Technologies WaveLAN/IEEE
Jul 13 16:16:23 bermuda kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. 
Jul 13 16:16:23 bermuda cardmgr[2716]: executing: 'modprobe wavelan2_cs network_name=Chaos'
Jul 13 16:16:23 bermuda kernel: eth1: WaveLAN/IEEE, io_addr 0x100, irq 9, mac_address 00:60:1D:23:A7:21 
Jul 13 16:16:23 bermuda cardmgr[2716]: executing: './network start eth1'
Jul 13 16:16:23 bermuda pumpd[2734]: starting at Thu Jul 13 16:16:23 2000  
Jul 13 16:16:30 bermuda kernel: eth1: Transmit timeout. 
Jul 13 16:17:01 bermuda last message repeated 3 times
Jul 13 16:17:11 bermuda kernel: eth1: Transmit timeout. 
Jul 13 16:17:20 bermuda sshd[448]: log: Generating new 768 bit RSA key.
Jul 13 16:17:20 bermuda sshd[448]: log: RSA key generation complete.
Jul 13 16:17:21 bermuda kernel: eth1: Transmit timeout. 
Jul 13 16:17:23 bermuda cardmgr[2716]: + Operation failed.


and now removing the card:

Jul 13 16:18:34 bermuda kernel: alloc_skb called nonatomically from interrupt c0160937 
Jul 13 16:18:34 bermuda cardmgr[2716]: shutting down socket 0
Jul 13 16:18:34 bermuda cardmgr[2716]: executing: './network stop eth1'
Jul 13 16:18:34 bermuda cardmgr[2716]: + eth1: error fetching interface information: Device not found
Jul 13 16:18:34 bermuda cardmgr[2716]: + Operation failed.
Jul 13 16:18:34 bermuda cardmgr[2716]: + eth1: unknown interface: No such device
Jul 13 16:18:34 bermuda cardmgr[2716]: executing: 'modprobe -r wavelan2_cs'
Jul 13 16:18:34 bermuda cardmgr[2716]: + ds: Device or resource busy

and now executing `pcmcia stop':

Jul 13 16:19:30 bermuda cardmgr[2716]: exiting
Jul 13 16:19:30 bermuda kernel: unloading PCMCIA Card Services 

______________________________________________________________

here is the dump_pirq output:

Interrupt routing table found at address 0xfdf00:
  Version 1.0, size 0x00e0
  Interrupt router is device 00:12.0
  PCI exclusive interrupt mask: 0x0000
  Compatible router: vendor 0x8086 device 0x122e

Device 00:10.0 (slot 1):
  INTA: link 0x60, irq mask 0xdcb8
  INTB: link 0x65, irq mask 0xdcb8
  INTC: link 0x66, irq mask 0xdcb8
  INTD: link 0x67, irq mask 0xdcb8

Device 00:0d.0 (slot 2):
  INTA: link 0x61, irq mask 0xdcb8
  INTB: link 0x66, irq mask 0xdcb8
  INTC: link 0x67, irq mask 0xdcb8
  INTD: link 0x65, irq mask 0xdcb8

Device 00:0c.0 (slot 0):
  INTA: link 0x63, irq mask 0xdcb8
  INTB: link 0x63, irq mask 0xdcb8

Device 00:0b.0 (slot 3):
  INTA: link 0x62, irq mask 0xdcb8
  INTB: link 0x67, irq mask 0xdcb8
  INTC: link 0x65, irq mask 0xdcb8
  INTD: link 0x66, irq mask 0xdcb8

Device 00:0e.0 (slot 0):
  INTA: link 0x65, irq mask 0xdcb8

Device 00:09.0 (slot 4):
  INTA: link 0x63, irq mask 0xdcb8
  INTB: link 0x65, irq mask 0xdcb8
  INTC: link 0x66, irq mask 0xdcb8
  INTD: link 0x67, irq mask 0xdcb8

Device 00:12.0 (slot 0):
  INTD: link 0x65, irq mask 0xdcb8

Device 00:14.0 (slot 0):

Device 00:01.0 (slot 0):
  INTA: link 0x65, irq mask 0xdcb8
  INTB: link 0x66, irq mask 0xdcb8
  INTC: link 0x67, irq mask 0xdcb8
  INTD: link 0x64, irq mask 0xdcb8

Device 00:0f.0 (slot 0):
  INTA: link 0x65, irq mask 0xdcb8
  INTB: link 0x66, irq mask 0xdcb8
  INTC: link 0x67, irq mask 0xdcb8
  INTD: link 0x64, irq mask 0xdcb8

Device ff:04.0 (slot 5):
  INTA: link 0x64, irq mask 0xdcb8
  INTB: link 0x65, irq mask 0xdcb8
  INTC: link 0x66, irq mask 0xdcb8
  INTD: link 0x67, irq mask 0xdcb8

Device ff:07.0 (slot 6):
  INTA: link 0x67, irq mask 0xdcb8
  INTB: link 0x64, irq mask 0xdcb8
  INTC: link 0x65, irq mask 0xdcb8
  INTD: link 0x66, irq mask 0xdcb8

Interrupt router at 00:12.0: Intel 82371AB PIIX4/PIIX4E PCI-to-ISA bridge
  PIRQ1 (link 0x60): unrouted
  PIRQ2 (link 0x61): unrouted
  PIRQ3 (link 0x62): unrouted
  PIRQ4 (link 0x63): unrouted
  Serial IRQ: [disabled] [quiet] [frame=21] [pulse=4]

_____________________
end of message

None Strange interrupt routing information

Re: More more info. (Douglas S. J. De Couto)
Date: 2000, Jul 13
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Your interrupt routing table looks pretty strange to me.  I'd try:

   CORE_OPTS="cb_pci_irq=11"
   PCIC_OPTS="irq_mode=0"

and see how that works.  Maybe try different values in place of 11.
The thing I don't understand is why your dump_pirq output shows all
PCI interrupt pins as "unrouted":

> Interrupt router at 00:12.0: Intel 82371AB PIIX4/PIIX4E PCI-to-ISA bridge
>   PIRQ1 (link 0x60): unrouted
>   PIRQ2 (link 0x61): unrouted
>   PIRQ3 (link 0x62): unrouted
>   PIRQ4 (link 0x63): unrouted
>   Serial IRQ: [disabled] [quiet] [frame=21] [pulse=4]

This makes me think my suggestion is unlikely to work, because PCI
interrupts are not being routed in a way that I understand.

But this is an SMP box so maybe this is an IO APIC issue, and the
interrupt routing table doesn't apply.  In that case this is over my
head: maybe contact Martin Mares <mj@ucw.cz> and ask him how to figure
out or fix the interrupt assignment for a PCI device on an SMP box
when the BIOS doesn't fill in the PCI interrupt line register.  He may
tell you that this combination won't work with a 2.2 kernel.

-- Dave

None not working still

Re: None Strange interrupt routing information (David Hinds)
Date: 2000, Jul 13
From: Douglas S. J. De Couto decouto

hi,  tried your suggestion for new options in config.opts, but 
no good.  i have tried PCIC_OPTS="irq_mode=0" and 
CORE_OPTS="cb_pci_irq=n" for n in 3,..,15, but it only ever 
tries 11, unsuccessfully.  here are the log messages.  i will 
follow up on your suggestion and contact Martin.  Thanks.

-------------------------------

Jul 13 18:44:36 bermuda kernel: Linux PCMCIA Card Services 3.1.18 
Jul 13 18:44:36 bermuda kernel:   kernel build: 2.2.14 #10 SMP Wed Apr 19 16:07:14 EDT 2000 
Jul 13 18:44:36 bermuda kernel:   options:  [pci] [cardbus] [pnp] 
Jul 13 18:44:36 bermuda kernel: PCI routing table version 1.0 at 0xfdf00 
Jul 13 18:44:36 bermuda kernel: PnP: PNP BIOS installation structure at 0xc00f6cd0 
Jul 13 18:44:36 bermuda kernel: PnP: PNP BIOS version 1.0, entry at f0000:a89e, dseg at 400 
Jul 13 18:44:36 bermuda kernel: Intel PCIC probe:  
Jul 13 18:44:36 bermuda kernel:   TI 1225 rev 01 PCI-to-CardBus at slot 00:0b, mem 0x68000000 
Jul 13 18:44:36 bermuda kernel:     host opts [0]: [pci only] [pci irq 11] [lat 168/176] [bus 32/34] 
Jul 13 18:44:36 bermuda kernel:     host opts [1]: [pci only] [pci irq 11] [lat 168/176] [bus 35/37] 
Jul 13 18:44:36 bermuda kernel:     PCI irq 11 test failed 
Jul 13 18:44:36 bermuda kernel:     *NO* card interrupts, polling interval = 1000 ms 
Jul 13 18:44:36 bermuda cardmgr[3829]: starting, version is 3.1.18
Jul 13 18:44:36 bermuda cardmgr[3829]: watching 2 sockets
Jul 13 18:44:36 bermuda kernel: cs: IO port probe 0x1000-0x13ff: clean. 
Jul 13 18:44:36 bermuda kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x370-0x37f 
Jul 13 18:44:36 bermuda kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Jul 13 18:44:37 bermuda cardmgr[3829]: initializing socket 0
Jul 13 18:44:37 bermuda cardmgr[3829]: socket 0: Lucent Technologies WaveLAN/IEEE
Jul 13 18:44:37 bermuda kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. 
Jul 13 18:44:37 bermuda cardmgr[3829]: executing: 'modprobe wavelan2_cs network_name=Chaos'
Jul 13 18:44:37 bermuda kernel: wavelan2_cs: RequestIRQ: Resource in use 
Jul 13 18:44:38 bermuda cardmgr[3829]: get dev info on socket 0 failed: Resource temporarily unavailable

Question same problems on single processor

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

Hi,

I am still having problems getting my wavelan ieee to work with a
PCI/PCMCIA adapter.  Setup is kernel 2.2.14, pcmcia-cs-3.1.18, on a
single processor machine.  Any suggestions?  I have tried to access
Jean's recent document
(http://bougret.hpl.hp.com/~jt/Linux/Wavelan-IEEE.html) but i couldn'y
get through to his web page...

when i try with /etc/sysconfig/pcmcia as follows:

PCMCIA=yes
PCIC=i82365
PCIC_OPTS=""
CORE_OPTS=""


i get the following log messages:

Jul 16 13:23:13 mindwipe kernel: Linux PCMCIA Card Services 3.1.18 
Jul 16 13:23:13 mindwipe kernel:   kernel build: 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 
Jul 16 13:23:13 mindwipe kernel:   options:  [pci] [cardbus] [apm] 
Jul 16 13:23:13 mindwipe kernel: Intel PCIC probe:  
Jul 16 13:23:13 mindwipe kernel:   TI 1225 rev 01 PCI-to-CardBus at slot 00:0f, mem 0x68000000 
Jul 16 13:23:13 mindwipe kernel:     host opts [0]: [isa irq] [no pci irq] [lat 168/176] [bus 32/34] 
Jul 16 13:23:13 mindwipe kernel:     host opts [1]: [isa irq] [no pci irq] [lat 168/176] [bus 35/37] 
Jul 16 13:23:13 mindwipe kernel:     ISA irqs (default) = 3,4,5,7,9,14 polling interval = 1000 ms 
Jul 16 13:23:13 mindwipe cardmgr[4744]: starting, version is 3.1.18
Jul 16 13:23:13 mindwipe cardmgr[4744]: watching 2 sockets
Jul 16 13:23:13 mindwipe kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x12e8-0x12ef 0x16e8-0x16ef 
Jul 16 13:23:13 mindwipe kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x1c8-0x1cf 0x2e8-0x2ef 0x378-0x37f 0x3f0-0x3ff 0x4d0-0x4d7 
Jul 16 13:23:13 mindwipe kernel: cs: IO port probe 0x0a00-0x0aff: excluding 0xae8-0xaef 
Jul 16 13:23:13 mindwipe cardmgr[4744]: initializing socket 0
Jul 16 13:23:13 mindwipe kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. 
Jul 16 13:23:13 mindwipe cardmgr[4744]: socket 0: Lucent Technologies WaveLAN/IEEE Adapter
Jul 16 13:23:13 mindwipe cardmgr[4744]: executing: 'modprobe wvlan_cs'
Jul 16 13:23:13 mindwipe kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4 
Jul 16 13:23:13 mindwipe kernel: wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de> 
Jul 16 13:23:14 mindwipe kernel: wvlan_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f 
Jul 16 13:23:14 mindwipe kernel: wvlan_cs: Registered netdevice wvlan0 
Jul 16 13:23:14 mindwipe kernel: wvlan_cs: MAC address on wvlan0 is 00 60 1d f0 77 ba  
Jul 16 13:23:14 mindwipe cardmgr[4744]: executing: './network start wvlan0'
Jul 16 13:23:39 mindwipe kernel: wvlan_cs: wvlan0 Tx timed out! Resetting card 
Jul 16 13:23:39 mindwipe kernel: wvlan_cs: MAC address on wvlan0 is 00 60 1d f0 77 ba 
<lots more Tx timeouts...>

the wavelan card does not work, e.g. pings fail, etc.

i then tried with the following options as suggested on the message
board:

PCMCIA=yes
PCIC=i82365
PCIC_OPTS="irq_mode=0"
CORE_OPTS=""

and get the following output in my log:

Jul 16 13:22:15 mindwipe kernel: Linux PCMCIA Card Services 3.1.18 
Jul 16 13:22:15 mindwipe kernel:   kernel build: 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 
Jul 16 13:22:15 mindwipe kernel:   options:  [pci] [cardbus] [apm] 
Jul 16 13:22:15 mindwipe kernel: Intel PCIC probe:  
Jul 16 13:22:15 mindwipe kernel:   TI 1225 rev 01 PCI-to-CardBus at slot 00:0f, mem 0x68000000 
Jul 16 13:22:15 mindwipe kernel:     host opts [0]: [pci only] [no pci irq] [lat 168/176] [bus 32/34] 
Jul 16 13:22:15 mindwipe kernel:     host opts [1]: [pci only] [no pci irq] [lat 168/176] [bus 35/37] 
Jul 16 13:22:15 mindwipe kernel:     *NO* card interrupts, polling interval = 1000 ms 
Jul 16 13:22:16 mindwipe cardmgr[4692]: starting, version is 3.1.18
Jul 16 13:22:16 mindwipe cardmgr[4692]: watching 2 sockets
Jul 16 13:22:16 mindwipe kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x12e8-0x12ef 0x16e8-0x16ef 
Jul 16 13:22:16 mindwipe kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x1c8-0x1cf 0x2e8-0x2ef 0x378-0x37f 0x3f0-0x3ff 0x4d0-0x4d7 
Jul 16 13:22:16 mindwipe kernel: cs: IO port probe 0x0a00-0x0aff: excluding 0xae8-0xaef 
Jul 16 13:22:16 mindwipe cardmgr[4692]: initializing socket 0
Jul 16 13:22:16 mindwipe kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. 
Jul 16 13:22:16 mindwipe cardmgr[4692]: socket 0: Lucent Technologies WaveLAN/IEEE Adapter
Jul 16 13:22:16 mindwipe cardmgr[4692]: executing: 'modprobe wvlan_cs'
Jul 16 13:22:16 mindwipe kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4 
Jul 16 13:22:16 mindwipe kernel: wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de> 
Jul 16 13:22:16 mindwipe kernel: wvlan_cs: RequestIRQ: Resource in use 
Jul 16 13:22:17 mindwipe cardmgr[4692]: get dev info on socket 0 failed: Resource temporarily unavailable


here is the output of dump_pirq:

-------------
No PCI interrupt routing table was found.

Interrupt router at 00:07.0: Intel 82371SB PIIX3 PCI-to-ISA bridge
  PIRQ1 (link 0x60): unrouted
  PIRQ2 (link 0x61): irq 10
  PIRQ3 (link 0x62): irq 11
  PIRQ4 (link 0x63): unrouted
  Serial IRQ: [disabled] [quiet] [frame=17] [pulse=4]
---------------

and parts of lspci -vv:

---------------

00:0f.0 CardBus bridge: Texas Instruments PCI1225 (rev 01)
	Subsystem: SCM Microsystems: Unknown device 2023
	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: 168 set, cache line size 08
	Interrupt: pin A routed to IRQ 0
	Region 0: 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
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
	16-bit legacy interface ports at 0001

00:0f.1 CardBus bridge: Texas Instruments PCI1225 (rev 01)
	Subsystem: SCM Microsystems: Unknown device 2023
	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: 168 set, cache line size 08
	Interrupt: pin A routed to IRQ 0
	Region 0: 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
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
	16-bit legacy interface ports at 0001

None No interrupt routing table

Re: Question same problems on single processor (Douglas S. J. De Couto)
Date: 2000, Jul 17
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> No PCI interrupt routing table was found.

Well, that's bad.  That means we don't know which PCI devices are
connected to which PCI interrupt (PIRQ) pins:

> Interrupt router at 00:07.0: Intel 82371SB PIIX3 PCI-to-ISA bridge
>   PIRQ1 (link 0x60): unrouted
>   PIRQ2 (link 0x61): irq 10
>   PIRQ3 (link 0x62): irq 11
>   PIRQ4 (link 0x63): unrouted

What I would do is to first try setting:

    PCIC_OPTS="pci_irq_list=10,10"

and see if that works.  If not, try 11,11.  If that also fails, then
try moving the adapter to another PCI bus slot and repeat the tests.

-- Dave

None Re: No interrupt routing table

Re: None No interrupt routing table (David Hinds)
Date: 2000, Jul 18
From: Douglas De Couto decouto

> > No PCI interrupt routing table was found.
> 
> Well, that's bad.  That means we don't know which PCI devices are
> connected to which PCI interrupt (PIRQ) pins:
> 
> > Interrupt router at 00:07.0: Intel 82371SB PIIX3 PCI-to-ISA bridge
> >   PIRQ1 (link 0x60): unrouted
> >   PIRQ2 (link 0x61): irq 10
> >   PIRQ3 (link 0x62): irq 11
> >   PIRQ4 (link 0x63): unrouted
> 
> What I would do is to first try setting:
> 
>     PCIC_OPTS="pci_irq_list=10,10"
> 
> and see if that works.  If not, try 11,11.  If that also fails, then
> try moving the adapter to another PCI bus slot and repeat the tests.
> 
> -- Dave


thanks for the new info.  unfortunately i have tried the card in every
pci slot, with each permutation of PCIC_OPTS="",
PCIC_OPTS="pci_irq_list=10,10", and PCIC_OPTS="pci_irq_list=11,11",
and i still get Tx timeouts from the card.

Where does the trouble lie?  Is it that the PCI/PCMICA bridge doesn't
correctly interface with PCI (because all my other devices are
working!)?

thanks for your help

d
-- 
Douglas S. J. De Couto    decouto@lcs.mit.edu

None Oops, I left out something important

Re: None Re: No interrupt routing table (Douglas De Couto)
Date: 2000, Jul 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Oh wait.  Back up and try:

    PCIC_OPTS="irq_mode=0 pci_irq_list=10,10"

and

    PCIC_OPTS="irq_mode=0 pci_irq_list=11,11"

again for different slots.

-- Dave

None Re: Oops, I left out something important

Re: None Oops, I left out something important (David Hinds)
Date: 2000, Jul 20
From: Douglas S. J. De Couto decouto

thanks for your help dave; unfortunately the PCI/PCMCIA card still
doesn't work; i am going to put my hands on an old laptop...

d


-- 
Douglas S. J. De Couto    decouto@lcs.mit.edu

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

None More info

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

when I run test_network I get the following

PCMCIA network settings are coming from /etc/pcmcia/network.opts.
  /etc/sysconfig/network-scripts/ifcfg-eth0 also exists??

Checking network interface eth3 (ray_cs driver):

  Current ifconfig settings:
  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:83 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:100
            Interrupt:5

  The interface is configured and running.
  TX looks ok, but there seems to be an RX problem.

  You have not configured a gateway or default route.

  Enter a numeric IP address to ping: 192.168.1.1

  Pinging 192.168.1.1 ... response received!
  The device interrupt does not seem to be incrementing normally.

What does this mean?

Ok Problem solved - I think there is a bug in 3.1.18

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

I have gone back to 3.1.15 and my Aviator2.4 now works again. Somewhere between 3.1.15 and 3.1.18 a bug has been introduced. I will try to step though the versions and track it down

-Robert

Question I think I spoke too soon

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

I'm getting tired of talking to myself here ;)

I am now running 3.1.17 and the ray_cs driver loads fine. I could not notice anything that stuck out in the diffs for 3.1.18, so there is either a bug in there, or something has changed. I will try 3.1.18 again tomorrow (it is now 2am in Australia).

I seem to have created more problems for myself however, as during my trying to get it all working, I upgraded the firmware on the cards to the latest version on Webgears web site.

So now even though the linux driver seems to load ok, I cannot communicate with the win 98 machines (running the new driver compatible with the new version 5 firmware)

Previously when I was using the old driver/version 4 firmware I was using translate=0 country=0 psm=0 successfully

With the new driver I have unsuccessfully tried various combinations of the above mixed with translate=1, country=8 (Australia), psm=1 (matched with the corresponding setting in Win98 of course)

Has anyone had any success with the new firmware on Linux/Windows? Does the linux driver support it?

Time for sleep

-Robert

Sad ray_cs.c and wireless.opts

Re: Question Help getting Webgear Aviator 2.4 working under linux (Robert Lowery)
Date: 2000, Jul 13
From: Jean Tourrilhes jt

  Please don't use wireless.opts with the ray_cs driver, it doesn't work yet. Corey never managed to fix the remaining bugs, so this support should be considered as experimental. For example it definitely doesn't work in BSS mode.

  Jean

None Bad hw address

Re: Question Help getting Webgear Aviator 2.4 working under linux (Robert Lowery)
Date: 2000, Jul 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> wireless.opts *,*,FF:00:FF:48:FF:B3,*)

This hw ethernet address is bogus.  Webgear cards should have
addresses starting with 00:00:86.

I don't think there have been any changes in ray_cs in recent
releases.

-- Dave

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

Sad Correct URL

Re: News Wavelan IEEE : state of the wvlan_cs driver... (Jean Tourrilhes)
Date: 2000, Jul 18
From: Jean Tourrilhes jt

  I'm stupid. I gave you the URL inside the firewall. The external web page is at :

http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Wavelan-IEEE.html

  Sorry !

  Jean

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

Warning bad experiences...

Re: Question Any experience with PCI docking cards? (Stephane Laroche)
Date: 2000, Jul 18
From: Douglas S. J. De Couto decouto

hi

i have been unable to get the lucent PCI dock to work with linux 2.2.14/pcmcia 3.1.18 on a either PIII SMP or a PII uniprocessor. I believe they both have intel motherboards.

but i know some people have it working!

d

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

None Need more detailed information

Re: Question Lucent Wavelan IEEE Turbo 11M (Kirmo Koistinen)
Date: 2000, Jul 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Is this a desktop system or a laptop?  System log messages would be
very helpful.

-- Dave

None here are logs.

Re: None Need more detailed information (David Hinds)
Date: 2000, Jul 19
From: Kirmo Koistinen kikoisti

wavelan2_cs driver log:
Jul 20 09:39:46 yok126 cardmgr[568]: executing: 'modprobe -r wavelan2_cs'
Jul 20 09:39:47 yok126 cardmgr[568]: initializing socket 0
Jul 20 09:39:47 yok126 cardmgr[568]: socket 0: Lucent Technologies WaveLAN/IEEE
Jul 20 09:39:47 yok126 cardmgr[568]: executing: 'modprobe wavelan2_cs'
Jul 20 09:39:47 yok126 cardmgr[568]: executing: './network start eth0'
Jul 20 09:39:47 yok126 kernel: eth0: WaveLAN/IEEE, io_addr 0x100, irq 3,
mac_address 00:60:1D:F1:F2:58

wvlan_cs driver log:

Jul 20 09:49:39 yok126 cardmgr[710]: initializing socket 0
Jul 20 09:49:39 yok126 cardmgr[710]: socket 0: Lucent Technologies WaveLAN/IEEE Adapter
Jul 20 09:49:39 yok126 cardmgr[710]: executing: 'modprobe wvlan_cs'
Jul 20 09:49:39 yok126 kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4 
Jul 20 09:49:39 yok126 kernel: wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de> 
Jul 20 09:49:39 yok126 cardmgr[710]: executing: './network start wvlan0'
Jul 20 09:49:39 yok126 kernel: wvlan_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f 
Jul 20 09:49:39 yok126 kernel: wvlan_cs: Registered netdevice wvlan0 
Jul 20 09:49:39 yok126 kernel: wvlan_cs: MAC address on wvlan0 is 00 60 1d f1 f2 58  

and it's laptop system. ThinkPad 560.

- Kirmo

None Problem solved.

Re: None here are logs. (Kirmo Koistinen)
Date: 2000, Jul 27
From: Kirmo Koistinen kikoisti

Ok I got this card working propertly with Lucent driver. I havent managed to get this driver to support wireless extensions and I dont think there are any support for that to wavelan2_cs driver. I havent found any software to monitor connect withoout wireless extensions support. If there is some I would be very pleased. :)

 - Kirmo

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

None That does not sound familiar

Re: Question Cannot config. WaveLan IEEE Turbo after kernel upgrade (Tim DIckerson)
Date: 2000, Jul 19
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I would carefully compare the PCMCIA messages under the 2.2.15 and
2.2.16 kernels, to see if the card is being configured any
differently.  There should not be a problem with 2.2.16.

-- Dave

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 ??

None Re: Question: Wavelan Problem

Re: Question Wavelan Problem (Peter Zimmer)
Date: 2000, Jul 20
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> Jul 20 17:31:08 fly kernel: wvlan_cs: Registered netdevice wvlan0

What shows up if you do "ifconfig wvlan0"?

-- Dave

None 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.

More does HCF_ERR_NO_NIC mean bad hardware?

Re: None wvlan_cs fails on startup with "Resource temporarily unavailable" (Bob Cook)
Date: 2000, Jul 26
From: Bob Cook bcook

Thanks to Dave Hind for the suggestion for my previous problem (I had conflicting information in my config files). That change now allows me to get the wvlan_cs driver started although it still won't initialize properly.

In wvlan_hcfio.c, the hcfio_string() function, on line ~346 there is a test of memory. Specifically there is a test at the ioport+0x28 for the bytes 0x7d37.

This test fails on my setup. It finds either 0xFFFF (on the first attempt) or 0x0000 on successive attempts.

I'm suspicious of believing the pcmcia card is faulty because I've gotten it to successfully initialize under Win98 and in a Mac. I don't have a way to verify my ISA bridge, but it seems to function ok because the card insertion is detected and recognizied.

By the way, I should mention that I'm running this on an old 486 box. This shouldn't make any difference but I wonder about bus speeds (its an AT bus) or something. I don't know enough about this sort of thing to be knowledgable but I'm certain I'm not the first to try this sort of thing and I can't seem to find references of anyone else having such problems.

TIA for any assistance or suggestions.

None A shot in the dark

Re: More does HCF_ERR_NO_NIC mean bad hardware? (Bob Cook)
Date: 2000, Jul 26
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I don't have experience with this specific card, but I'd try bumping
it to another IO port range (exclude 0x100-0x13f in your config.opts
file) just in case this is a conflict with some other device.

-- Dave

Feedback No luck... Where can I get details about the WaveLAN?

Re: None A shot in the dark (David Hinds)
Date: 2000, Jul 28
From: Bob Cook bcook

I've tried fiddling around with various ioport and interrupt combinations and nothing seems to help this problem.

I definitely can see that the driver is unable to read data from the wavelan card although it appears that the ISA->PCMCIA bridge is working (card identity is known, insert/remove events are registering). This is probably some sort of issue with bus timings on my crappy old h/w; of course I know nothing about this sort of stuff but I guess I'll get my hands dirty as I go (advice appreciated).

This theory is sort of confirmed via my earlier attempts at using the Lucent binary driver (wavelan2_cs). It would complain about events not occuring within a specific time. Unfortunately I don't have the exact error message text and since its only a binary driver (and I can't hack on it very easily) its hard to want to spend any more time with it.

I need to get a data sheet or other docs that describes programming the WaveLAN IEEE. I've been unable to find one but I'm *sure* there must be one available.

I'll also need some information about how the ISA->PCMCIA bridge works; I guess this is wrapped up in the i82365.c file somewhere?

Is there anyone else having similar problems with the WaveLAN IEEE card using an ISA->PCMCIA bridge? Maybe we can pool information to figure out why it works for everyone else but us... :^)

Any hints on hacking the wvlan_cs driver? Don't be shy, please pass them along.

More On Andy's page...

Re: Feedback No luck... Where can I get details about the WaveLAN? (Bob Cook)
Date: 2000, Jul 29
From: Jean Tourrilhes jt

  Hi,

  I can understand your frustration. It seem that the Pcmcia adapter from Lucent are a big source of trouble, we have many instance of them not working the way they should under Linux or Windows.
  For the spec of Pcmcia, I would start in the Pcmcia Howto.

  For the spec of the Wavelan, Lucent has published a very short document. It's almost useless, and looking in the driver is uselly more useful, anyway it's on Andy's page :
http://www.fasta.fh-dortmund.de/users/andy/wvlan/

  Now, if you are hacking the driver, you may want to synchronise with the others doing it, in particular Harald and Benjamin. Check details on my web page :
http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Wavelan-IEEE.html

  Good luck !

  Jean

Question Some questions about your message

Re: More On Andy's page... (Jean Tourrilhes)
Date: 2000, Jul 29
From: Bob Cook bcook

> I can understand your frustration. It seem that the
> Pcmcia adapter from Lucent are a big source of trouble,
> we have many instance of them not working the way they
> should under Linux or Windows.

Do you mean to say that the ISA->PCMCIA boards are faulty? Or did you mean that the current versions of the driver(s) have difficulty with these boards?

Can you recommend a better ISA->PCMICA board? This one was not very expensive and I'd be happy to spend money for one that would work...

> Now, if you are hacking the driver, you may want to
> synchronise with the others doing it, in particular
> Harald and Benjamin. Check details on my web page :
> ttp://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/
> Wavelan-IEEE.html

Will do. Thanks for putting together a very good web page on this subject!

> Good luck !

Thanks, looks like I'll need it. :^)

Sad Hum...

Re: Question Some questions about your message (Bob Cook)
Date: 2000, Jul 31
From: Jean Tourrilhes jt

  The Pcmcia package doesn't interact well with those adapters and the machine BIOS. I think you can't pin-point the blame on one, but usually the software is supposed to work around the hardware...

  Jean

None The PCI->PCMCIA adapters are the tricky ones

Re: Question Some questions about your message (Bob Cook)
Date: 2000, Jul 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Fri, Jul 28, 2000 at 10:43:14PM -0700, Bob Cook wrote:

> Do you mean to say that the ISA->PCMCIA boards are faulty? Or did you
> mean that the current versions of the driver(s) have difficulty with
> these boards?

The ISA->PCMCIA boards are not troublesome; the PCI->PCMCIA boards are
troublesome.

-- Dave

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

Sad Not possible...

Re: Question Wavelan as Access Point (Kelly Murray)
Date: 2000, Jul 31
From: Jean Tourrilhes jt

  This is not possible. Use Ad-Hoc mode and configure NAT or routing.

  Jean

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

More More info...

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

When I look at /var/log/messages, I see

Jul 31 14:43:32 giles kernel: wvlan_cs: wvlan0 Tx timed out! Resetting card 

Thanks
Alex

Sad Timeout cause...

Re: More More info... (Alex Lam)
Date: 2000, Jul 31
From: Jean Tourrilhes jt

  There is 2 cause of the "timeout message".

  The first one is using the old version of the driver with the new firmware. It usually look like this :
http://pcmcia.sourceforge.org/cgi-bin/HyperNews/get/pcmcia/wireless/51.html
  The solution is described on my page :
http://pcmcia.sourceforge.org/cgi-bin/HyperNews/get/pcmcia/wireless/67/1.html

  The other cause is an interrupt problem. David will tell you to play with various irq settings...

  Jean

None Sounds like an interrupt problem; need more messages

Re: More More info... (Alex Lam)
Date: 2000, Jul 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The messages from the pcmcia_core and i82365 modules are important.

-- Dave

More Very similar problem here

Re: None Sounds like an interrupt problem; need more messages (David Hinds)
Date: 2000, Aug 02
From: Elliot Lee sopwith

I'm having a very similar problem.

Kernel: 2.2.16-17 (the one that comes with Red Hat pinstripe beta), with associated pcmcia-cs 3.1.19.

Hardware: ActionTec PC-750 PCI <-> PCMCIA adapter thing in a generic Pentium II on one end, a Casio Fiva MPC-501 on the other end.

In both machines, Lucent WaveLAN/IEEE (turbo 11Mb Gold). I haven't any idea what the firmware version is.

Symptoms: 
Everything seems to load fine, ifconfig & iwconfig work fine, but no data gets through.

Matt Wilson (a coworker) had a known-to-work-in-other-situations card (silver version of the above) in his laptop. He got things to the point where pinging the wireless broadcast IP address would cause the Rx/Tx light to flash on the desktop machine, but no interrupts were coming through on the desktop.

[root@test152 wireless]# grep wvlan /proc/interrupts 
  4:          4          XT-PIC  wvlan_cs

When trying to send pings from the desktop machine, a bunch of
'wvlan0 Tx timed out! Resetting card' msgs would be generated. Matt tried a bunch of different IRQ's on the desktop box to see if changing that would help - no joy.

Communication from Matt's laptop to the Fiva did not work either, although the 'wvlan0 Tx timed out! Resetting card' message did not show up on the Fiva when pinging from it.

(The Fiva also crashes hard if the WaveLAN card is removed/inserted while pcmcia service is running, dunno if this is related, but would be happy just to get the WaveLAN working soon. :-)

Syslog info on wvlan_cs load:
Aug  2 20:12:41 test152 kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4
Aug  2 20:12:41 test152 kernel: wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de>
Aug  2 20:12:41 test152 kernel: wvlan_cs: index 0x01: Vcc 5.0, irq 4, io 0x0100-0x013f
Aug  2 20:12:41 test152 kernel: wvlan_cs: Registered netdevice wvlan0

ActionTec PC-750 'lspci -v' output on the desktop box:
00:0b.0 CardBus bridge: Texas Instruments PCI1225 (rev 01)
	Subsystem: Action Tec Electronics Inc: Unknown device 0293
	Flags: bus master, medium devsel, latency 32, IRQ 10
	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:0b.1 CardBus bridge: Texas Instruments PCI1225 (rev 01)
	Subsystem: Action Tec Electronics Inc: Unknown device 0293
	Flags: bus master, medium devsel, latency 32, IRQ 9
	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

None Your case is much easier

Re: More Very similar problem here (Elliot Lee)
Date: 2000, Aug 03
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Your lspci output shows a PCI interrupt for the CardBus bridge.  You
just need to specify:

  PCIC_OPTS="irq_mode=0"

to force the i82365 module to use only PCI interrupts.

-- Dave

Sad Nope.

Re: None Your case is much easier (David Hinds)
Date: 2000, Aug 03
From: Elliot Lee sopwith

No go (I had already tried this while looking at back msgs).

When starting up with irq_mode=0:

Aug  2 21:27:14 test152 kernel: PCI routing table version 1.0 at 0xf0a90
Aug  2 21:27:14 test152 kernel: Intel PCIC probe: 
Aug  2 21:27:14 test152 kernel:   TI 1225 rev 01 PCI-to-CardBus at slot 00:0b, mem 0x68000000
Aug  2 21:27:14 test152 kernel:     host opts [0]: [pci only] [pci irq 10] [lat 32/176] [bus 32/34]
Aug  2 21:27:14 test152 kernel:     host opts [1]: [pci only] [pci irq 9] [lat 32/176] [bus 35/37]
Aug  2 21:27:14 test152 kernel:     PCI irq 10 test failed
Aug  2 21:27:14 test152 kernel:     *NO* card interrupts, polling interval = 1000 ms
Aug  2 21:27:14 test152 cardmgr[747]: starting, version is 3.1.19
Aug  2 21:27:14 test152 cardmgr[747]: watching 2 sockets
Aug  2 21:27:14 test152 kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
Aug  2 21:27:14 test152 kernel: cs: IO port probe 0x0800-0x08ff: clean.
Aug  2 21:27:14 test152 kernel: cs: IO port probe 0x0200-0x04ff: excluding 0x200-0x207 0x220-0x22f 0x290-0x297 0x330-0x337 0x388-0x38f 0x4d0-0x4d7
Aug  2 21:27:15 test152 cardmgr[747]: initializing socket 0
Aug  2 21:27:15 test152 kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Aug  2 21:27:15 test152 cardmgr[747]: socket 0: Lucent Technologies WaveLAN/IEEE Adapter
Aug  2 21:27:15 test152 cardmgr[747]:   product info: "Lucent Technologies", "WaveLAN/IEEE", "Version 01.01", ""
Aug  2 21:27:15 test152 cardmgr[747]:   manfid: 0x0156, 0x0002  function: 6 (network)
Aug  2 21:27:15 test152 cardmgr[747]: executing: 'modprobe wvlan_cs port_type=3 channel=1'
Aug  2 21:27:15 test152 kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4
Aug  2 21:27:15 test152 kernel: wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de>
Aug  2 21:27:15 test152 kernel: wvlan_cs: RequestIRQ: Resource in use

Dunno if it is relevant, but once I have started & stopped pcmcia with irq_mode=0, this error continues to happen subsequent times when I start pcmcia without rebooting.

None Re: Sad: Nope.

Re: Sad Nope. (Elliot Lee)
Date: 2000, Aug 03
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Hmmm.  Try each of these combinations:

  PCIC_OPTS="irq_mode=3 irq_list=0"

  PCIC_OPTS="irq_mode=0 p2cclk=1"

  PCIC_OPTS="irq_mode=3 irq_list=0 p2cclk=1"

-- Dave

News Yay! Works

Re: None Re: Sad: Nope. (David Hinds)
Date: 2000, Aug 03
From: Elliot Lee sopwith

The first one on that list (irq_mode=3 irq_list=0) worked for me, thanks much.

I want to say something about it being nice to do this stuff automatically, but I'm afraid I'd just be showing utter ignorance of the complexities of the hardware involved. :)

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

None Already fixed in current beta

Re: Sad problem compiling wvlan_cs.c and kernel 2.40-pre5 (Brett Eldridge)
Date: 2000, Aug 01
From: David Hinds <dhinds@pcmcia.sourceforge.org>

If you intend to use a very recent experimental kernel, you should
always first try the latest beta PCMCIA package.

-- Dave

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

More Firmware version

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

Additional informations: I think, that is problem with version of Firmware. I am using some 6.x firmware in my WaveLan Orinoco TurboCard Silver + using original driver from Lucent Technologies version 6.x

Many thanks Vladimir

Agree same with me

Re: Question Lucent WaveLan don't update statistics (Vladimir Vlach)
Date: 2000, Aug 10
From: Marcio Gomes Marcio

I am having same problems.

Inter-| sta-|   Quality        |   Discarded packets
 face | tus | link level noise |  nwid  crypt   misc
  eth2: 0000    0     0     0        0      0  88657     

Marcio Gomes

None 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

None Re: SWL-2000P 11Mbps Wireless LAN PCI Card + Linux

Re: None SWL-2000P 11Mbps Wireless LAN PCI Card + Linux (Wynand Theunissen)
Date: 2000, Aug 03
From: David Hinds <dhinds@pcmcia.sourceforge.org>

What driver are you using?  The "next generation" linux-wlan driver
from absoval.com?

You might have better luck asking your question on one of the
linux-wlan mailing lists. 

-- Dave

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?

None Need to determine the PCI interrupt

Re: Question Interrupt problem with P60, WaveLAN/IEEE and TI-1221 (Sami Pitko)
Date: 2000, Aug 02
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I don't know how interrupts are routed for this PCI bridge chipset.
You could try using:

    PCIC_OPTS="irq_mode=0 pci_irq_list=N,N"

where N is whatever the PCI interrupt number for the cardbus bridge
and card is under NT.

-- Dave

None Strange IRQ info on NT

Re: None Need to determine the PCI interrupt (David Hinds)
Date: 2000, Aug 03
From: Sami Pitko spitko

NT Diagnostic gives following information:

IRQ Device Bus Type
...
06 Floppy 0 Isa
10 WVLAN41 0 Internal
11 E100B 0 Pci
...

What surprises me is that WaveLAN interrupt is of type Internal (whatever it means?). Maybe there is some kind of driver to produce/process those interrupts in NT.

Is there a way to find the interrupt which TI-1221 is using on NT? At least "Administrative Tools/Windows NT Diagnostics" only gives IRQ for WaveLAN adapter and on the "Control Panel/PCMCIA" there is only memory area as a resource for PCMCIA Controller.

On the linux side:

If I set the WaveLAN to use IRQ 10, it doesn't work. All PCI interrupts are giving "PCI irq N test failed", unless I set do_scan=0.

I was able to get some pings through when I set it to use the same interrupt as eepro100 is using (IRQ 11), but the ping packets only went through when there were network traffic going on (== interrupts generated by) the eepro100...

None I think you are out of luck

Re: None Strange IRQ info on NT (Sami Pitko)
Date: 2000, Aug 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Hmmm.  I was actually surprised that this worked at all under NT.  Now
I think I understand.

I bet that NT has not figured out the interrupt routing either.  And
when it says "Internal", it means that it is faking the interrupt in
software.

Without a datasheet for your PCI bridge chipset (the VLSI one), I
don't think there is anything I can do to help you.

Your best bet would probably be to use an ISA-to-PCMCIA adapter card
instead of this PCI adapter.

-- Dave

Feedback Same kind of problem, works with 3.0.5!

Re: Question Interrupt problem with P60, WaveLAN/IEEE and TI-1221 (Sami Pitko)
Date: 2000, Aug 03
From: Kelly Murray kem

On my Dell XPi laptop with TI CardBus, it also couldn't find interrupts. It worked fine with the older 3.0.5 card services, so I ended up fixing up the sources for the wvlan driver to compile with the older card services and got it to work. perhaps this isn't helpful without all the details, but thought I'd say something... I gave up after fiddling for hours with all the module parameters..

-kelly

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.

Sad Ad-Hoc mode

Re: Question Windows-2-Linux communication problems (Andrew Fernandes)
Date: 2000, Aug 08
From: Jean Tourrilhes jt

  Hi,

  As far as I know, in Ad-Hoc mode the Windows driver force the usage of channel 3 (2.422 GHz) and doesn't use the ESSID at all (or it use to be that way).
  So, could you try to set the Wavelan on this channel ?

  Other things that may matter :
  The firmware 6.06 and windows driver 6.14 are supposed to have "improved ad-hoc networking". That may be a source of incompatibilities, so you may want to downgrade your Windows and card setup to earlier version.
  Some firmware release of the Wavelan don't like tcpdump.
  Try Linux-Linux communications if you can, that may tell you were the trouble is.

  Jean

More Silly Lucent

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

Thanks, Jean!

I've poked around the source for Lucent's wavelan2_cs (v 6.02) driver, and I found the cryptic comment that as of the 6.06 firmware, Lucent no longer supports their "ad-hoc" mode, which was a nonstandard quasi-IBSS-type service.

Instead, they are supporting full 802.11(b) IBSS standard peer-to-peer networking. Going from the Windoze drivers, this mode seems to need the ESSID, and can be on any channel, not just channel 3 (seems to auto-hunt and negotiate the channel). As far as I can tell, this is mainly a firmware issue, and driver software changes to support this should be small.

I'd take a look to see what Lucent's driver is doing, but it just hangs... even with full debugging on. Looks like I'll have to try to custom frutz their code to see what changes need to be made on the wvlan_cs code.

All my cards are on the same firmware (I doublechecked). I suspect that the software only needs a tweak to get it to run.

Lucent, I have three little letters for you... GPL!!! Grr...

Thanks,

-Andrew.

News The problem is in Cardmgr!

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

Bhaha!

After an intense weekend of debugging, I've discovered that the Lucent driver actually (sort-of) DOES work!

The scenario: all cards and OSes have the 21-July release of Lucent's drivers and firmware. The wvlan_cs driver loads up, starts the net device, but can't talk to windows boxes. The wavelan2_cs driver won't even load up.

It turns out that the reason the wavelan2_cs driver doesn't load is because cardmgr dies BEFORE it can send the device a DS_BIND_DEVICE ioctl! Stepping through cardmgr with a debugger, it shows all the signs of classic memory corruption. Harmless calls like "syslog" lock up forever, and previously valid instructions cause "illegal instruction" and "segmentation fault" errors.

So... when using the wavelan2_cs driver: if I jump over all the "syslog" calls, which should theoretically not make any difference, the net device is correctly brought up by the module. Yay!

I still can't talk to the windows box, but there may still be something funny going on. Even thought I delicately stepped through cardmgr with my debugger (and things inside it were corrupted), it reported several "could not adjust resource" (memory and I/O errors).

So, until I (or David!) can track down the corruption in cardmgr, it may be possible to use Lucent's driver with the latest firmware to talk to windows boxes...

Whew!

-Andrew.

More 'Twas a buffer overflow error...

Re: News The problem is in Cardmgr! (Andrew Fernandes)
Date: 2000, Aug 31
From: Andrew Fernandes <andrew@fernandes.org>

It turns out that I was using a waaaaay too long

 module "wavelan2_cs" opts "irq_list=11 network_name=Studio20 port_type=3 station_name=Herbie channel=10 enable_encryption=y key_1=xxxxxxxxxxxxx transmit_key_id=1 pc_debug=0x7fffffff debug_flags=0xffffffff"

The line blew cardmgr's internal buffers.

That's the good news.

The bad news is now I can bring up both the Lucent and the GPL driver... and neither of them can talk to Windows.

I'm not impressed, Lucent...

I'll call their tech support and kvetch...

(David - I'll email my patch to you to look at)!

-Andrew.

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 ?

None What's Inside?

Re: Question Lucent Wavelan/Orinocco PC card - What is inside ? (Martin Prasek)
Date: 2000, Aug 14
From: Glenn Elmore n6gn

I've looked inside and can read what's on the components but I'm afraid I don't have schematics. 
However, I have had a bit of a look at the physical layer side, including tx/rx antennas, internal/external switching
as well as the desktop external antenna and power control & shutdown circuitry.
I've also looked at the power output and spectral characteristics at the various data rates. 
  Its probably not whay you want but if any of this is of interest I'd be happy to share my findings.
Glenn Elmore

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

None Sounds great to me...

Re: Idea wvlan_cs PPC port/patches (David D. Johnson)
Date: 2000, Aug 09
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Forward patches to me and Andreas Neuhaus.

-- Dave

News Hum, better patch...

Re: None Sounds great to me... (David Hinds)
Date: 2000, Aug 09
From: Jean Tourrilhes jt

  David,

  Andy seems to be very busy, and I don't think that he will do much Wavelan IEEE hacking in the future.
  Moreover, Harrald has a fully functional PPC patch on his web page that has been extensively tested. That would be the patch that I would prefer in the Pcmcia package.
  He has also a patch for the Pcmcia package that you may want to look into (if you have not already done it). And he has a better version of the wvlan_cs patch, but experimental.
  See :
    http://www.roelle.com/wvlanPPC/index.html
  I suggested Harrald to become the new wvlan_cs maintainer, I got no answer from him yet, but maybe you want to contact him directly.
  I also did an update of the Howto, with 2 new drivers (Airport, Samsung) and minor changes there and there.

  Jean

Angry Please check PPC patch !

Re: Idea wvlan_cs PPC port/patches (David D. Johnson)
Date: 2000, Aug 09
From: Jean Tourrilhes jt

  Hi,

  Before redoing a whole bunch of work that already exist, please, please, please check the howto. Harrald Roelle has already done an extensive PPC patch, available at :
    http://www.roelle.com/wvlanPPC/index.html
  In fact, Harrald sent me a second version of the patch (not on his page) that was *very* promising.
  The patch of Harrald is not in the main Pcmcia distribution because Andy has been busy lately and Harrald doesn't feel confident enough to send them to David.
  Please contact Harrald to know how you can help.
  That's all...

  Jean

Feedback Yes, I've checked the PPC patches...

Re: Angry Please check PPC patch ! (Jean Tourrilhes)
Date: 2000, Aug 09
From: David D. Johnson ddj

The version I have running (prior to my own changes) is indeed the latest version I could find on Harrald's site. As I discussed, the things that needed to be swapped are being swapped only by accident, and Harrald's patch basically unswaps all the things that shouldn't have been in the first place.

I don't know what's in the "unreleased" patch, not having seen it. If it addresses these concerns, fine, I've only wasted two days. Otherwise, I am willing to put in the time to debug and polish the code, especially since it is becoming a model for other wireless drivers. Once I have it working as well for me as Harrald's version works, I would offer it as a patch to pcmcia-cs-3.1.19 for others to try before submitting any changes to the codebase.

I certainly don't wish to trample on anyone's toes, and I have the utmost admiration for those who have made these devices work at all. I just think it can/should be made more straightforward and understandable.

	-- ddj

Sad Oups !

Re: Feedback Yes, I've checked the PPC patches... (David D. Johnson)
Date: 2000, Aug 09
From: Jean Tourrilhes jt

  I've got to offer you my sincere apologies. I didn't exactly understand where you were going and I did jump on my guns too quickly.
  Now, all I can say is to go ahead with what you are doing, because it's worthwhile. And if you end up beeing the maintainer of the wvlan_cs driver, the better.
  Just try to sync with Harrald and Benjamin, because both are working on this stuff. The patch of Harrald is comming via e-mail...
  Again, sorry...

  Jean

P.S. : For me, I've got lot's of admiration for people willing to jump on the train and contribute further ;-)

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

More oh and more info...

Re: Question wvlan_cs and BIOS PnP problems? (Matthew GUthaus)
Date: 2000, Aug 11
From: Matthew GUthaus mobius314

I didn't have PnP compiled into the pcmcia_cs drivers. Nor do I have it compiled in my kernel...

Matt

None Interrupt or IO port probe failure?

Re: Question wvlan_cs and BIOS PnP problems? (Matthew GUthaus)
Date: 2000, Aug 14
From: David Hinds <dhinds@pcmcia.sourceforge.org>

There are two possible reasons for lockups when PCMCIA starts up, with
no cards inserted.  It is probably either an interrupt probe failure,
or an IO probe failure.  The PCMCIA-HOWTO has instructions for how to
tell them apart, and how to fix them.

Disabling/enabling PnP support may change how your built-in devices
are configured, which can change how these resource probes behave.

-- Dave

Ok My fault (didn't RTFM)

Re: None Interrupt or IO port probe failure? (David Hinds)
Date: 2000, Aug 14
From: Matthew GUthaus mobius314

Yes, limiting the IRQs with PCIC_OPTS="irq_list=3,5" fixed my problem. This was in the how-to, but I didn't read that far. :)

Matt

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.

Question Simple question...

Re: Question Compaq WL100 WLAN Card - Not detected (Talei McLeod)
Date: 2000, Aug 11
From: Jean Tourrilhes jt

  Just a simple question : what driver are you using with this card ?
  By the way, it's usually good practice to give a bit more info on the setup (version of kernel, pcmcia, driver).

  Jean

More My setup is as follows

Re: Question Simple question... (Jean Tourrilhes)
Date: 2000, Aug 12
From: Talei McLeod talei

I am using kernel 2.4.0-test5 and i am using the PCMCIA driver 3.1.20.

I am using Prism II WLAN driver from Absoval which has been updated by Compaq at www.handhelds.org.

I have been able to get one other card (non WLAN)to work with my system, just not this one.

Any help would be much appreciated.

Thanks Talei.

None did it ever work

Re: Question Compaq WL100 WLAN Card - Not detected (Talei McLeod)
Date: 2000, Aug 22
From: harry campigli harryc

did you get the card to work in the end?

harry@gpssys.com

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?

News Aviator2.4 and 2.4Pro

Re: Feedback WebGear Aviator2.4 Pro? (Justin Gaither)
Date: 2000, Aug 11
From: Jean Tourrilhes jt

  Hi,

  The 2 firmware revisions are incompatible over the air. This mean that all your devices *MUST* have the same firmware.
  The new firmware is fully 802.11-FH compliant (hurra !), whereas the old one is not. In theory the Linux driver should support both firmware, but the new firmware has probably been less tested.
  What I would say is that as long as you don't need to use W2k and don't buy any new devices, stick with what works, and upgrade only if needed or you are adventurous.

  Jean

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

Question CONFIG_NET_RADIO

Re: Question wavelan turbo 11 mb will not answer ioctl calls (Mathieu Lacage)
Date: 2000, Aug 14
From: Jean Tourrilhes jt

  Hi,

  Did you configure your kernel with the CONFIG_NET_RADIO enabled ? It's in network devices and called wireless LAN support.

  Jean

None A guess: kernel configuration?

Re: Question wavelan turbo 11 mb will not answer ioctl calls (Mathieu Lacage)
Date: 2000, Aug 14
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Maybe your kernel was not compiled with wireless tools support?
(CONFIG_NET_RADIO)

-- Dave

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?

None Some context would help

Re: Question Receive interrupt does not seem to be incrementing properly (Richard Smith)
Date: 2000, Aug 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>

That isn't the exact message, and the rest of the output would be
useful, but my guess is what it means is that you are using a wireless
network card in a PCI host adapter in a desktop system and you haven't
specified the right startup options to configure the adapter to use
PCI interrupts.

But without more context, that's just a guess.

-- Dave

None Re: Some context would help

Re: None Some context would help (David Hinds)
Date: 2000, Aug 15
From: Richard A. Smith smithbone

On Tue, 15 Aug 2000 09:59:48 -0700, David Hinds wrote:

>That isn't the exact message, and the rest of the output would be

Yeah.. I tried to wing it from memory. Should have mentioned that. Sorry.

>useful, but my guess is what it means is that you are using a wireless
>network card in a PCI host adapter in a desktop system and you haven't
>specified the right startup options to configure the adapter to use
>PCI interrupts.
>
>But without more context, that's just a guess.

My bad... I should know better. I was in the middle messing with various PNP bios 
settings and didn't prepare well enough.
 
I am using a RayLink wireless card with the adapter that came with it. But it's 
not PCI. That would probally work.  It's an ISA PNP adapter using the Ricoh 
RF5C296 bridge.

All appears to go without problems until I actually try to use the cards.  They 
both start networks when one should start and one should join.  (FWIW I can't get 
them to work under windows either)  Data on Cory's page and other web sources say 
that this is either a card failure or some sort of receive problem where the card 
dosen't get any data thus it starts a new network.

So far nothing in the debug level 5 output from ray_cs shows anything to be 
amiss.

When I found the network script and it mentioned RX seeming to have a problem I 
started to look at my IRQs'.  (I am in the middle of installing isapnptools now 
to see if I can find any more info)

Here's the output from test_network:  (more or less I am retyping)

----------

PCMCIA network settings are coming from /etc/pcmcia/network.opts

Checking network itnterface eth1 (ray_cs driver)

Kernel messages for eth1:
eth1:  RayLink, irq 5, hw_addr 00:00:8f:48:e3:03

current ifconfig setting
all pretty much std..
IP:   10.0.1.1
Bcast:  10.0.1.255
mask:  255.255.255.0
zeros on all the  RX, TX, etc stats:
Interrupt 5

The interface is configured and running
There hasn't been any traffic on this interface

There is a route to a gateway at 10.0.1.1

Pinging 10.0.1.1.... response received!
The device interrupt does not seem to be incrementing normally.

----------





--
Richard A. Smith                         Bitworks, Inc.               
rsmith@bitworks.com               501.846.5777                        
Sr. Design Engineer        http://www.bitworks.com   

None Not sure if it is an interrupt issue; gateway set wrong?

Re: None Re: Some context would help (Richard A. Smith)
Date: 2000, Aug 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Does /proc/interrupts show a non-zero interrupt count for the card?
If the count is 0, then try using a different irq (by excluding things
in /etc/pcmcia/config.opts).

> There is a route to a gateway at 10.0.1.1

There's something wrong with your network settings and this is
confusing the script.  Your gateway address seems to be the same as
your own IP address, which doesn't make any sense.

> Pinging 10.0.1.1.... response received!
> The device interrupt does not seem to be incrementing normally.

In this context, I think this doesn't mean anything: it thinks it is
pinging your gateway, but it is pinging the box itself, which doesn't
cause any packets to go out through the card.  So it won't produce any
interrupts.

I'll add a test to the script to complain if the gateway address is
the same as the IP address.

-- Dave

None Re: Not sure if it is an interrupt issue; gateway set wrong?

Re: None Not sure if it is an interrupt issue; gateway set wrong? (David Hinds)
Date: 2000, Aug 15
From: Richard A. Smith smithbone

On Tue, 15 Aug 2000 11:53:06 -0700, David Hinds wrote:

>Does /proc/interrupts show a non-zero interrupt count for the card?
>If the count is 0, then try using a different irq (by excluding things
>in /etc/pcmcia/config.opts).

Yeah it shows 107 interrupts.

>> There is a route to a gateway at 10.0.1.1
>
>There's something wrong with your network settings and this is
>confusing the script.  Your gateway address seems to be the same as
>your own IP address, which doesn't make any sense.
>

Oh... DUH!.. ID10T error. Of course...Man I can't believe I missed that.. yesh.. 
rookie mistake.

I didn't scrutinize the settings hard enough.  I guess I should note that I was 
just taking the default settings. Everything but the IP is preset in the 
network.opts so I just made the IP match the already pre-configured settings.  For 
my app (a private wireless net) at first glance they appeared to be perfect.

>In this context, I think this doesn't mean anything: it thinks it is
>pinging your gateway, but it is pinging the box itself, which doesn't
>cause any packets to go out through the card.  So it won't produce any
>interrupts.

Yeah.. thats exactly whats happening...  Crap that means I still dont have a clue 
why the cards don't talk..

>I'll add a test to the script to complain if the gateway address is
>the same as the IP address.

Glad to help *grin*  Whats that quote? Something about... no amount of idiot 
proofing is good enough for a sufficiently powered idiot.






--
Richard A. Smith                         Bitworks, Inc.               
rsmith@bitworks.com               501.846.5777                        
Sr. Design Engineer        http://www.bitworks.com   

None Raylink problem solved..

Re: None Not sure if it is an interrupt issue; gateway set wrong? (David Hinds)
Date: 2000, Aug 15
From: Richard A. Smith smithbone

I'm a talking now...

Turned out to be a good old fashioned hardware failure.  I got 2 new cards in 
about an hour ago and it was truly plug and play.

Further investagation led to finding that one of the orginal pair I have just 
dosn't work.  Looks like it works... the drivers think it works.. But something 
in the chain is broke..

This is kinda scary for me because the card worked when we originally received 
them. I am useing the card in a custom OEM application of mine where I am talking 
to it via a TI 5402 DSP.  Thus I am in the process of writeing a custom driver 
for it.  I am worried that in that process I may have done something that gacked 
the card.  If so then it was a serious gack because I re-programmed the firmware 
on the card to make sure I hadn't done that.

Oh well back to hacking.. Perhaps I can keep from breaking my new cards.

Thanks Dave for your your help.

One quick question.. In the process of all this I installed like 3 different 
pcmcia-cs versions and a couple of ray_cs driver versions all multiple times.  

Whenever I do a make install it seems that all the configuration files have write 
permissions cleared.  Doing an install over an existing install will silently 
fail to update all the settings in /etc/init.d (I use debian) and /etc/pcmcia.  

This can lead to some very confusing problems.  As such I had to do a chmod +w 
every time I changed things and then double check all the settings to make sure I 
didn't miss one.  It was quite annoying.

Are the files marked read only for a reason or is something strange about my 
setup?



--
Richard A. Smith                         Bitworks, Inc.               
rsmith@bitworks.com               501.846.5777                        
Sr. Design Engineer        http://www.bitworks.com   

None Configuration files

Re: None Raylink problem solved.. (Richard A. Smith)
Date: 2000, Aug 15
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Tue, Aug 15, 2000 at 01:51:46PM -0700, Richard A. Smith wrote:
> 
> Whenever I do a make install it seems that all the configuration
> files have write permissions cleared.  Doing an install over an
> existing install will silently fail to update all the settings in
> /etc/init.d (I use debian) and /etc/pcmcia.

I'm not sure what you mean here.  Files in /etc/pcmcia like config,
network, etc are installed read-only and are generally not intended to
be modified by the user.  If you reinstall, and the new versions
differ from what is already installed, the old files are renamed to
*.O before the new versions are installed.  The *.opts files are never
overwritten if they already exist.

The scripts in /etc/init.d will generally not be overwritten because
some distributions use startup scripts that are not directly
compatible with the startup script included in the PCMCIA package.

> This can lead to some very confusing problems.  As such I had to do
> a chmod +w every time I changed things and then double check all the
> settings to make sure I didn't miss one.  It was quite annoying.

I don't think I understand.  What things do you need to change after
doing a reinstall?  I do "make install" dozens of times per day and
never need to touch permissions or edit files.

-- Dave

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?

None The interface is fine; the problem is with ifup

Re: Question Compaq card detected but no wlan0-device (Per Olesen)
Date: 2000, Aug 18
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> Aug 16 14:33:39 polesen cardmgr[4209]: + usage: ifup <device name>
> 
> It seems like the name "wlan0" is not known :-(

The "usage: ifup <device name>" message does not mean the interface is
not known; if you do "ifconfig -a" you will see that it is there.  It
means that "ifup" could not find a network configuration file for this
interface.

The Red Hat "netconf" and "ifup" tools only know how to configure
standard ethernet devices with eth* names.  You can't use the Red Hat
network setup programs to configure this device.  So you are getting
bit by the fact that Red Hat's default PCMCIA setup installs a special
network script that calls their tools.

If you install the standard PCMCIA network configuration scripts, then
you can enter your network settings in /etc/pcmcia/network.opts using
the instructions in the PCMCIA-HOWTO.

-- Dave

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

Ok With wvlan_cs

Re: Question Power management? (Brian Mays)
Date: 2000, Aug 23
From: Jean Tourrilhes jt

  If you are using the driver wvlan_cs, it's actually trivial, just add in wireless.opts something like the following :
    IWCONFIG="power 500m unicast"
  Of course, check the iwconfig man page to get all the details and syntax of the command.
  When I implemented support in wvlan_cs, I did test that everything was working. It was with firmware 4.X. However, I didn't tested the latest firmwares.

  And also, I beleive that Power Saving is not worth it, i.e. little saving and too much perf degradation, but other can probably comment on it. The better solution seem to be to eject the card manually.
  Jean

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?

Question More info...

Re: Question Peer-to-Peer w/wvlan_cs or wavelan2_cs drivers (Craig Nelson)
Date: 2000, Aug 24
From: Jean Tourrilhes jt

  We definitely need much more info. Which firmware revision do you use with Linux ? Have you set the ESSID ? What are the messages ? Do you manage to do Linux-Linux ?
  If you use wvlan_cs, please set "port_type=3" in config.opts.

  Jean

News peer-to-peer vs. ad-hoc

Re: Question More info... (Jean Tourrilhes)
Date: 2000, Sep 07
From: Andrew Fernandes <andrew@fernandes.org>

After much time on the phone with the bloody Lucent people, some nice fellow managed to track this down for me.

EVERYONE: UPDATE YOUR WEB PAGES!

First off:

Both the wavelan2_cs and wvlan2_cs drivers (the Lucent and GPL drivers, respectively) work and intercommunicate just fine ONLY if the "Station Functions Firmware" on the WaveLan/IEEE card is 6.04. Note that the latest firmare release is 6.06.

If you update your cards, then windows boxes will be able to communicate, but nothing will talk to Linux.

Not only Linux, but you can't even talk to Lucent's own Wireless Ethernet converter.

Everything will work if you have an access point, if you use the 6.06 (but I haven't tested this).

The problem is that in going from firmware 6.04 to 6.06, Lucent REMOVED support for the non-IEEE "ad-hoc" mode, and replaced it with a fully-IEEE "peer-to-peer" or "IBSS" mode.

I ranted quite a while at them over making incompatible firmware changes...

While you're at it, you can only use the 6.04 firmware with the 6.00 drivers for Windows on a windows box.

Here are some useful URLs...

The firmware: FTP://FTP.WAVELAN.COM/PUB/SOFTWARE/IEEE/UPDATE/FIRMWARE/CARD/WIN/wsu10604z.exe

The Win2000 driver: FTP://FTP.WAVELAN.COM/PUB/SOFTWARE/IEEE/PC_CARD/WIN2000/v600/wlw2_600.exe

The Win95/98/NT driver: FTP://FTP.WAVELAN.COM/PUB/SOFTWARE/IEEE/PC_CARD/WINDOWS/v600/wlwi600a.exe

There's an apple driver on Lucent's "download" site as well (http://www.wavelan.com/).

This saga is officially over. Everyone should email Lucent (mailto:usasupport@wavelan.com) and vent their displeasure.

Thanks all,

-Andrew.

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?

Sad no way

Re: Question ORiNOCO Outdoor Router Client Supported? (Richard Smith)
Date: 2000, Aug 26
From: Marcio Gomes Marcio

orinoco router, in turbo cell mode is a propietary product.

There are not linux client drivers to it.

Marcio Gomes

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

Ok Compaq WL200 and WL100 working!!

Re: Question Has anyone made a COMPAQ WL200 or 100 finally work?? (harry campigli)
Date: 2000, Aug 29
From: Jean Luc Gorinas jlgorinas

Hi there,

I have got a WL100 and a WL200 talking happily to each other (linux kernel 2.2.16 to linux or windows).

I am just using the samsung driver! (http://www.sem.samsung.com/eng/product/rf/wlan/download_linux.htm) However I found that this driver would initialise the card properly only with pcmcia 3.1.3 and not with the latest version.

This works fine in Ad-Hoc mode with no particular settings for the card services.

I am trying to use the Wlan driver from absoval to use the card in the server (WL200) as an AP, for that it seems that a firmware needs to be downloaded onto the card at initialisation...any idea where i can find this firmware??

thanks!

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);

None Thanks for the patch...

Re: Warning problems with rarp and wavelan silver card (Blorp Blorp)
Date: 2000, Aug 26
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> 
> 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?

Well, I don't really know what the driver is doing, but 1500 is the
MTU for regular ethernet.

-- Dave

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

More RG-1000 == Airport

Re: Question WaveLAN Gold and RG-1000 gateway (Chris Hill)
Date: 2000, Aug 28
From: Jean Tourrilhes jt

  The RG-1000 is *almost* identical to the Apple Airport base station. There are quite a few people having pages on the subject (Linux PPC + wvlan_cs + Airport).

  Jean

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

Sad wvlan_cs module parameters

Re: Feedback 2 X PCI + ISA or 2 x PCI, with orinoco pcmcia silver problems (Marcio Gomes)
Date: 2000, Aug 28
From: Jean Tourrilhes jt

  Hi,

  I can only talk for the wvlan_cs driver, but here are a few more details.

  One of the big culprit in the wvlan_cs driver is those stupid module parameters (that may be set in config.opts). They are global :-(
  If you look closely, the reset function always use the module parameters to reconfigure the card. As those parameters are global, if you have 2 cards you are sure that at least one of them will get screwed up.
  Using Wireless Extensions do help, because they are per-card. But at the next reset, you loose.

  The way to solve this mess is to have card configuration stored *per card*, not globally. This mean duplicate all modules parameters in the net_local structure and initialise it from module parameters in wvlan_attach. Then you replace all mention of module parameters in the code with the local version in net_local.
  My previous inspection in the wvlan_cs code lead me to beleive that it's the only issue with multiple card (no other thing is global) and that it should work with this fixed (but I've been wrong before). And as it is not terrible difficult to fix (just a bit tedious), I expect that somebody will write a patch (hint, hint...).

  Jean

P.S. David : I have trouble with the "wvlan_config" function, could you confirm that it handles dual cards properly ?

None not work

Re: Sad wvlan_cs module parameters (Jean Tourrilhes)
Date: 2000, Sep 30
From: Marcio Gomes Marcio

>   Using Wireless Extensions do help, because they are >per-card. But  at the next reset, you loose.

If I run iwconfig after boot process, it works with first
up card and not works with last up card:

iwconfig ethLASTUP rate XX  ->  Kernel panic
iwconfig ethLASTUP freq XX -> SIOCSIWFREQ: Invalid Argument
iwconfig ethLASTUP sens  XX -> Do not change sensitivity

>   The way to solve this mess is to have card configuration >stored
> *per card*, not globally. This mean duplicate all modules
> parameters in the net_local structure and initialise it from >module
> parameters in wvlan_attach. Then you replace all mention of >module
> parameters in the code with the local version in net_local.
>   My previous inspection in the wvlan_cs code lead me to >beleive
> that it's the only issue with multiple card (no other thing > is
<  global) and that it should work with this fixed (but I've be you confirm that it handles dual cards properly ?

Ok, but i am a poor C programer.


[]s
Marcio Gomes

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?

Sad Complain to Ben

Re: Question Problems setting ESSID on airo_cs
Date: 2000, Aug 28
From: Jean Tourrilhes jt

  airo_cs does not support Wireless Extensions. Fixing that would be quite trivial (cut'n'paste from wvlan-cs), but only somebody with the hardware can do it.
  So either you have a look in the source, or you ask gently to Ben...

  Jean

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?

News Try latest driver

Re: Question Wavelan IEEE 6.02 driver compatibility (Mike)
Date: 2000, Oct 26
From: Jean Tourrilhes jt

  wvlan_cs in 3.1.22 has been updated and support this properly. Give it a spin (it might still be in the NEW directory).

  Jean

None 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

None Lucent documents this

Re: Angry No Lucent(Grrr) PCI Adapter found (Alexander Bögl)
Date: 2000, Oct 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Lucent says that the card is only supported for PCI 2.2 compliant
motherboards.

-- Dave

Sad My Mainboards are PCI 2.2 compilant!

Re: None Lucent documents this (David Hinds)
Date: 2000, Oct 06
From: Alexander Bögl alex43

Okey 3 of the 5 are that.

Alex

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.

None It should work

Re: Question Linux Support for INM Hi Rate Wireless Lan PC Card (Michael H. Frey)
Date: 2000, Nov 16
From: David Hinds <dhinds@pcmcia.sourceforge.org>

>   manfid: 0x0156, 0x0002

It should work with the wvlan_cs driver.

-- Dave

More Still not working.

Re: None It should work (David Hinds)
Date: 2000, Nov 17
From: Michael H. Frey mhfrey

Thanks for the information, but it still does not work. I have tested a SCSI adapter which appears without problem to check pcmcia operation.

I have also tried 2 other drivers, wavlan_cs and wavlan2_cs without success.

I have configured the card using netconf to eth1 withous any additional parameters.

Is there a way to better diagnose what is going on other than "cardctl info"?

Thank you for the help.

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.

PCMCIA Wireless Network Adapter Issues


Add Message to: "PCMCIA Wireless Network Adapter Issues"

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