open issues with Xircom RBEM56G100TX as of 2.3.99pre3

From: Alessandro Suardi (asuardi@uninetcom.it)
Date: Sat Mar 25 2000 - 20:55:32 EST

  • Next message: David Elliott: "Re: Cylinder limits jumper for drives over 32GB"

    Hi all,

     (pcmcia-cs is 3.1.13 though cardmgr -V reports 3.1.11)

    1. card is not recognized as supported by cardmgr under new kernels
        resulting in a "bad" stab file:

    Socket 0:
      no product info available
    Socket 1:
      no product info available

      I worked around this by cheating in rc.pcmcia:

    <begin snippet>
        else
            if [ -r $RUN/stab ] ; then
            cat $RUN/stab | cleanup
            fi
            echo " cardmgr."
            /sbin/cardmgr $CARDMGR_OPTS
        fi
    #
    # OK - here we don't come up because cardmgr doesn't dig the Xircom,
    # so we do cardmgr's work after cp'ing a "good" copy of the stab
    # file over the "bad" one cardmgr just wrote.
    #
        cp $RUN/stab-fixed $RUN/stab
        (cd /etc/pcmcia; ./network start eth0; ./serial start ttyS1)
    #
    <end snippet>

    2. Even with the above, cardbus modem doesn't work (minicom is dead
        on /dev/ttyS1, 'AT' isn't even echoed).

    3. CardBus Watcher oopses on pcmcia stop:

    tulip_detach(eth0)
    cs: cb_free(bus 3)
    unloading PCMCIA Card Services
    Unable to handle kernel paging request at virtual address c884bf24
     printing eip:
    c884bf24
    *pde = 01258063
    *pte = 00000000
    Oops: 0000
    CPU: 0
    EIP: 0010:[<c884bf24>]
    EFLAGS: 00010213
    eax: 00000000 ebx: 00000246 ecx: 00000246 edx: 00000000
    esi: c1351fe8 edi: c884e674 ebp: c884e640 esp: c1351fa8
    ds: 0018 es: 0018 ss: 0018
    Process CardBus Watcher (pid: 346, stackpage=c1351000)
    Stack: 00000f00 c7bd5edc c884e640 c884e640 c1350000 c1350000 01234567 c1350000
           00000000 00000000 c1351fe8 00000000 01234567 c1350000 c884e678 c884e678
           c1351fe8 00000000 c0108cdc c884e640 00000078 c7feb000
    Call Trace: [<c884e640>] [<c884e640>] [<c884e678>] [<c884e678>] [<c0108cdc>] [<c884e640>]
    Code: Bad EIP value.

    4. at boot I get two kmem_grow messages plus usual failure
       about allocating PCI resource 0. Note that if I repeat the
       pcmcia startup the resource allocation message doesn't pop up
       anymore, as well the first kmem_grow (512) doesn't occur.

     Linux PCMCIA Card Services 3.1.11
      kernel build: 2.3.99-pre3 #1 Sat Mar 25 22:06:43 CET 2000
      options: [pci] [cardbus] [pm]
    Adding cardbus controller 0: Texas Instruments PCI1131
    Yenta IRQ list 0418, PCI irq11
    Socket status: 30000006
    Adding cardbus controller 1: Texas Instruments PCI1131 (#2)
    Yenta IRQ list 0418, PCI irq11
    Socket status: 30000020
    cs: cb_alloc(bus 3): vendor 0x115d, device 0x0003
    PCI: Enabling device 03:00.0 (0000 -> 0003)
    tulip_attach(03:00.0)
    PCI: Increasing latency timer of device 03:00.0 to 64
    xircom_tulip_cb.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
    kmem_grow: Called nonatomically from int - size-512
    eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x1400, 00:10:A4:F9:19:A0, IRQ 11.
    kmem_grow: Called nonatomically from int - size-2048
    eth0: MII transceiver #0 config 3100 status 7809 advertising 01e1.
    PCI: Failed to allocate resource 0 for PCI device 115d:0103
    PCI: Enabling device 03:00.1 (0000 -> 0003)

    Suggestions welcome, thanks in advance

    --alessandro <asuardi@uninetcom.it> <asuardi@it.oracle.com>

    Linux 2.2.14/2.3.99-pre3 glibc-2.1.2-11 gcc-2.95.2 binutils-2.9.5.0.31

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/



    This archive was generated by hypermail 2b29 : Sat Mar 25 2000 - 21:53:10 EST