OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Scott Franzyshen (sfranzyshenlazerlink.net)
Date: Mon Feb 05 2001 - 14:41:55 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    The compaq WL200's ships with a CIS that doesn't request an IRQ from the
    PCMCIA-CS.
    All drivers will load ... things seem to be there like ...
    "ifconfig -a" shows the wlan0 device etc. but nothings works ... right?
    "cat /proc/interrupts" doesn't show prism2 having an irq huh?

    then you need to create a substitute CIS for the card (or get Mark to
    release
    the prism2dl utility again and try to upload a new CIS to the card) using
    the
    dump_cis and pack_cis debug utilities from pcmcia-cs package.

    refer to http://www.lifix.fi/extarchive/lwlan/2000-12/msg00023.html from the
    mailing list archive.

    Scott Franzyshen
    http://www.getwireless.net/

    -----Original Message-----
    From: owner-linux-wlan-usernightsky.com
    [mailto:owner-linux-wlan-usernightsky.com]On Behalf Of Mark Conway Wirt
    Sent: Monday, February 05, 2001 7:45 AM
    To: linux-wlan-userabsoval.com
    Subject: Re: [lwlan-user]: Non-PCMCIA wireless cards?

    On Mon, Feb 05, 2001 at 10:59:15AM +0100, Thorsten Jungblut wrote:
    >
    > the wl200 has such a bridge ?
    >
    > i got another pci-pcmcia-brige and had problems with it.
    > do the irq's work correctly ?
    > perhaps your card shares its irq for cardservices and the build-in wl100 ?
    >

    While I've been using Linux for a long time, I can't claim to be a hardware
    expert, but I *think* everything is OK with the IRQs

    I was originally concerned that it was an IRQ issue, as lspci reports
    an IRQ of 0 for the card:

    01:06.0 PCMCIA bridge: Cirrus Logic CL 6729 (rev 07)
            Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
    \
                 Stepping+ SERR- FastB2B-
            Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort+ \
                 <TAbort- <MAbort- >SERR- <PERR-
            Interrupt: pin A routed to IRQ 0
            Region 0: I/O ports at 5800

    However, the card is configured to "use PCI interrupts," not ISA interrupts
    so I think that this is OK. I've poked around pretty extensively in the
    computer's BIOS, and there isn't really anything I can do to control the
    IRQ that this card is getting. I tried manually setting an IRQ with setpci
    as a lark, but it didn't seem to do anything.

    > if yes, try to set irq_mode=0 for the i82365.o-module

    irq_mode=0 (ISA interrupts) immediately freezes the machine David
    Hinds (the author of pcmcia-cs) assured me that this particular card
    will need PCI interrupts (irq_mode=1).

    >
    > i got a few wl100 and an elsa airlancer mc-11 (with a ti14xx-pci-pcmcia)
    > and they play together in ad-hoc mode very well (the new Ad-Hoc mode)
    >
    > there exists a pci-airlancer but i dont know wheter its a real pci-card
    >
    > has your server also isa-bus ?
    > perhaps buying a isa-pcmcia-bridge would help ?
    >

    The machine does have ISA slots, so I may have to give that a try.
    I just don't want to spend another $200US for a card and not have
    it work. I'll check to see if there is a true PCI airlancer.

    >
    > there are a few bugs left in the pcmcia-cs ...
    > perhaps you can send me the var/log/messages output ?

    Well, the messages output point to a memory probe failure. This usually
    means that one is searching the wrong memory, but I've tried so many ranges
    that it very well could actually be a PCI bus timing issue. I've tried
    many different settings, but the attached is demonstrative of what I
    see:

    elvis2 kernel: ISA irqs (default) = 3,4,5,7,9,10,14 polling interval = \
           1000 ms
    elvis2 cardmgr[17990]: starting, version is 3.1.24
    elvis2 cardmgr[17990]: watching 2 sockets
    elvis2 kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xc00- 0xc07 \
           0xc80-0xc87 0xcf8-0xcff
    elvis2 kernel: cs: IO port probe 0x0800-0x08ff: clean.
    elvis2 kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x188- \
           0x18f 0x3b8-0x3df 0x3f0-0x40f 0x418-0x43f 0x460-0x467 0x480-0x48f \
           0x4c0-0x4ff
    elvis2 kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1028 \
           -0x102f
    elvis2 kernel: cs: IO port probe 0x0a00-0x0aff: clean.
    elvis2 cardmgr[17990]: initializing socket 0
    elvis2 kernel: 1000)
    elvis2 kernel: excluding 0xc0000-0xcffff
    elvis2 cardmgr[17990]: socket 0: Anonymous Memory

    Thanks for the suggestions!

    --Mark
    -----------------------------------------------
    The Linux WLAN User's Mailing List
    For more information about this list see:
    http://www.absoval.com/linux-wlan/lists.html

    -----------------------------------------------
    The Linux WLAN User's Mailing List
    For more information about this list see:
    http://www.absoval.com/linux-wlan/lists.html