wrote:
> I have been experimenting with eCS 2.0 RC4 on my
> Tyan K8WE S2895 motherboard.
> This is an SMP board with 2 Opterons and 2 GiB ram.
> RC4 will install, but the
> network does NOT work. I selected the GenMac nForce
> 4 driver for the 10DE:0057
> chipset. The network adapter configuration shows
> W10DEX0057_NIF. When it boots,
> peer will not start.
Hi Tom,
I have an older Tyan MB (2865, I think it is) that
will be going into the tower system, but not for
awhile. It is one CPU but x2 dual core, with a single
NIC.
> Another item: This board has two NICs, but I only
> have one defined in MPTS. I
> have tried booting with the cable connected to both
> RJ-45 jacks, same story.
>
> Any suggestions?
I can't answer the earlier questions, but I can
reprise my experiences with an older Shuttle XPC,
which also had two NICs. This was unusual at the
time, circa 2004. And it was also before all this PHY
business, which seems to complicate the whole NIC
situation by a fair margin. (From what I recall
reading, if any of your NIC designations have a "PHY"
at the end of it, the prospects of it having support
in eCS -- Genmac or No -- do not appear to be very
good. I hope I am mistaken in this, because this type
of built-in NIC is becoming pretty standard on many
MBs.)
Even if you can determine that that PHY thing is not
the issue here, my experience is that the eCS
installer can not cope with dual NICs. (This extends
from at least 1.1 up through 2.0 RC-2 -- the last time
I tried.) It became fatally confused, and for me
always trashed the install at that point. PEER did
not go on, Internet Apps / Utilities / Problem
Determination Tools never got installed (probably some
other stuff too), and the TCP/IP might not be correct
or usable.
Anyway, what I got out of a couple Help Desks is that
our support for dual NICs does not function the way
that it does on the Dark Side, where they are
hot-swappable at will by just changing where you
connect the ethernet plug. With eCS, no matter what
you have accounted for in MPTS and in Config.Sys, no
more than one of the two NICs will be found at bootup
and will be usable. (If anyone has contradictory
experience, I would love to hear about it.) At the
Help Desk, Steven was able bob & weave between boots
-- with various adjustments I wasn't too able to
follow -- changing *which* of the two NICS got
discovered at bootup and was then usable. IIRC, he
_may have_ said that this process could perhaps be
automated by means of some type of script, but that is
beyond me and I have to question whether it would be
worth going to that much trouble, in order to
approximate what is effortless in Windoze.
Jordan
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
<< Previous Message <<
Return to [ 14 |
February |
2008 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
