Odd Xircom Realport Tulip Behavior

From: Jordan Mendelson (jordy@napster.com)
Date: Thu Aug 31 2000 - 15:39:30 EST

[this message was previously cc'ed to tulip-bug]

It seems that my Xircom report refuses to work correctly when first
initialized. I'm running Linux 2.4.0-test7 with the standard
xircom_tulip_cb driver. I can get the Xircom to work just fine, but I
seem to always need to go through a song and dance to do so.

When the driver is first initialized, ifconfig eth0 with an IP and
adding the default route will not work correctly. To get the realport to
work, I have to:

# ifconfig eth0 a.b.c.d netmask x.x.x.x
# ifconfig eth0 down
# ifconfig eth0 up
# route add default gw l.m.n.o

As soon as I bring it back up for the second time, it mysteriously
starts working correctly.

Here are the relevant kernel messages on boot:

cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x330-0x337
0x388-0x38f 0x398-0x39f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
PCI: Setting latency timer of device 04: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)
eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at
0x1c00, 00:10:A4:EB:58:4C, IRQ 9.
eth0: MII transceiver #0 config 3100 status 7809 advertising 01e1.

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

This archive was generated by hypermail 2b29 : Thu Aug 31 2000 - 21:00:28 EST