tulip.90 k results

[Robert G. Brown]

On Wed, 10 Feb 1999, Douglas Eadline wrote:

> Here is the funny thing, there are two idential NICs (KTI)
> in this machine.  When I use the .90k I can not
> get eth0 to come up (ifup eth0), but I can get
> the second interface to come up (ifup eth1).

Oooo, this really sounds like the bloody bios bug, too, that the patch
fixes.  I just found (the hard way, of course) that even with 2.0.36 and
0.89H in spanking new dual PII's, my old REAL (21141) KNE-100's still
barf on the old ioport bug.  Things are a bit better, perhaps.  The
symptom now is that the FIRST boot from a hard reset, the KNE-100 comes
up on 0xec00, ifconfigs "normally", and then just doesn't work.  The
second (warm) boot, it comes up on 0xec80 and works fine.  The third
(warm) boot, it comes up on 0xec00 and hangs.  And so it continues...

The patch in 0.89H does seem to shift the ioport on the first (cold)
boot to 0xec80 and the system works fine.  This alternating behavior,
though, as I recall, is new -- I think that in the old days a warm boot
would put you back at the original ioport and it would hang every time
unless you did the insmod/rmmod/insmod fix thingie kludge.

I personally, with my animistic projections on inanimate hardware, think
that the real problem is that my older tulip cards just don't "like"
ioport 0xec00.  Perhaps it dropped one of the cards on its electronic
head when it was a baby or something.  The proper solution is to put the
cards in therapy -- if they have a chance to talk it all out with an
understanding CPU, perhaps they'll get over this mindless animosity.

   rgb

Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu