Xircom cbem56g-100 + omnibook 800ct + slackwa

  • zebra_01c

    zebra_01c - 2005-01-02

    Hi folks.  I can't ping anything with this setup.  Please note, when I boot this omnibook to windows, the xircom network card works fine.  I can ping and do everything normally.  It's when I boot to Slackware 10.0 I lose functionality.

    In windows the card is set up like so:


    Start  000c0000
    End    00ffffff
    Length 00001000

    PORT IO 1000 - 107F

    IRQ 11

    (works fine)

    When booting to Linux... well, here's a dump of some relevance:

    root@laptop:/# lsmod
    Module                  Size  Used by    Not tainted
    usbcore                59308   1
    vlsi_ir                 8908   0  (unused)
    irda                   84060   0  [vlsi_ir]
    xircom_cb               5696   0  (unused)
    xircom_tulip_cb        12280   1
    crc32                   2880   0  [xircom_tulip_cb]
    ds                      6548   2
    yenta_socket           10336   2
    pcmcia_core            39972   0  [ds yenta_socket]
    ide-scsi                9328   0

    root@laptop:/# route -n
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface   U     0      0        0 eth0       U     0      0        0 lo         UG    1      0        0 eth0

    (from /etc/pcmcia/config)
    card "Xircom CBEM56G-100 CardBus 10/100 Ethernet + 56K Modem"
      version "Xircom", "*", "CBEM56G"
      bind "tulip_cb" to 0, "serial_cb" to 1

    root@laptop:/# ifconfig
    eth0      Link encap:Ethernet  HWaddr 00:10:A4:A7:9B:4B
              inet addr:  Bcast:  Mask:
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:121 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
              Interrupt:9 Base address:0x8800

    lo        Link encap:Local Loopback
              inet addr:  Mask:
              UP LOOPBACK RUNNING  MTU:16436  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:0
              RX bytes:98 (98.0 b)  TX bytes:98 (98.0 b)

    root@laptop:/# ping
    PING ( 56(84) bytes of data.
    From icmp_seq=1 Destination Host Unreachable
    From icmp_seq=2 Destination Host Unreachable
    From icmp_seq=3 Destination Host Unreachable

    --- ping statistics ---
    6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5019ms
    , pipe 3

    root@laptop:/# dmesg

    Intel ISA PCIC probe: not found.
    Databook TCIC-2 PCMCIA probe: not found.
    PCI: Assigned IRQ 5 for device 00:04.0
    PCI: Assigned IRQ 9 for device 00:04.1
    Yenta ISA IRQ mask 0x0ad8, PCI irq 5
    Socket status: 30000006
    Yenta ISA IRQ mask 0x08d8, PCI irq 9
    Socket status: 30000020
    cs: cb_alloc(bus 6): vendor 0x115d, device 0x0003
    PCI: Enabling device 06:00.0 (0000 -> 0003)
    PCI: Enabling device 06:00.1 (0000 -> 0003)
    ttyS04 at port 0x8880 (irq = 9) is a 16550A
    cs: IO port probe 0x0c00-0x0cff: clean.
    cs: IO port probe 0x0820-0x08ff: clean.
    cs: IO port probe 0x0800-0x080f: clean.
    cs: IO port probe 0x03e0-0x04ff: clean.
    cs: IO port probe 0x0100-0x03af: excluding 0x220-0x22f 0x330-0x337 0x388-0x38f
    cs: IO port probe 0x0a00-0x0aff: clean.
    xircom_tulip_cb.c derived from tulip.c:v0.91 4/14/99 becker@scyld.com
    unofficial 2.4.x kernel port, version 0.91+LK1.1, October 11, 2001
    PCI: Setting latency timer of device 06:00.0 to 64
    eth0: Xircom Cardbus Adapter rev 3 at 0x8800, 00:10:A4:A7:9B:4B, IRQ 9.
    eth0:  MII transceiver #0 config 3100 status 7809 advertising 01e1.
    PCI: Found IRQ 10 for device 00:06.0
    vlsi_ir: IrDA PCI controller VLSI Technology Inc 82C147 detected
    PCI: Setting latency timer of device 00:06.0 to 64
    NETDEV WATCHDOG: eth0: transmit timed out
    NETDEV WATCHDOG: eth0: transmit timed out
    NETDEV WATCHDOG: eth0: transmit timed out
    NETDEV WATCHDOG: eth0: transmit timed out
    NETDEV WATCHDOG: eth0: transmit timed out
    NETDEV WATCHDOG: eth0: transmit timed out

    The NETDEV WATCHDOG part appears after trying to ping.  Host at is definitely there and pings fine from windows.

    Out of my depth here.  Any help much appreciated!

    • zebra_01c

      zebra_01c - 2005-01-04

      Okay.  When I use an older kernel (2.2.16) and older "cardmgr" (3.1.16), everything works fine.  Here's a module dump:

      laptop / # lsmod
      Module                  Size  Used by
      serial_cb               1076   1
      tulip_cb               32508   2
      cb_enabler              2320   4  [serial_cb tulip_cb]
      ds                      6204   2  [cb_enabler]
      i82365                 21576   2
      pcmcia_core            48384   0  [cb_enabler ds i82365]
      ide-scsi                7216   0

      Instead of yenta_socket, i82365 is used.  I can't even force i82365 to load when running kernel 2.4.26.  I'm not sure why but tulip_cb seems to work better with my network card than the newer xircom_tulip_cb.

      Right now I'm not sure of a good way to get the network running with a more recent kernel.  I plan to try to graft the older pcmcia card drivers from 2.2.16 into a newer kernel source tree and compile that way.

      I'm guessing this is not advisable but I don't know a better way to make networking function properly with cbem56g-100 and a newer kernel.

      I'll post back with my results.

    • zebra_01c

      zebra_01c - 2005-01-07

      My results:

      This was a no brainer.  (Guess that's why it took me days to figure it out.)  I had no idea that the bootup state of the pcmcia card port could be adjusted thought the BIOS.  I had to set it to cardbus mode.  When I did this the default modules in the 2.4.26 kernel worked fine.  My machine is doing networking now.  After all of this meandering it seems the best advice I could give someone facing the issues I was facing is to simply try changing the BIOS settings relating to PCMCIA devices and see if that doesn't help.  Comments, corrections, advice and flames are welcome.  ; )


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks