From: David Ryan (david.ryan at domain baker.ie)
Date: Mon 20 Sep 1999 - 13:34:36 IST
My network card (PCI, 3c509 I think) has stopped working again.
Last time this happened I thought it was because I had changed my
"PNP-aware OS" to NO in order to get my sound card working, but I
could never get the NIC working again.
This time I started again from scratch with "PNP-aware OS" set to NO,
installed SuSE 6.1 with network support and all seemed well. I was
(almost) able to telnet into it from my other machine - I got the
login prompt and tried to log in as root, except was refused for
security reasons. So I went back to my SuSE machine and set up
another account and password and tried to telnet again. This time it
reported that the host had closed the connection, so I tried to open
a new session. Nothing. Tried to ping it - nothing. Looked for a
link light on the hub - nothing. Dead again.
Now, this leads me to think that it might be a dodgy NIC (I changed
the cables last time this happened and the cable worked on another
NIC), but according to the startup message the card seems to
initialise (or at least load) OK.
A few questions -
* I can also ping the machines address from itself - does this
indicate that the card is working, or does this operate at a level
above the card ?
* If I install a new NIC how do I change the driver/module/whatever
without having to resort to reinstalling SuSE again ?
* I know 3Com have some DOS utiliies on their EtherDisk which can be
used to make the card think it is in a non-PNP machine when it is and
vice-versa, but I'm not sure what way I need to have it set. My
sound card is an onboard non-pnp ISA thing, my video is an onboard
AGP job, while the NIC is pnp-PCI.
* Would I be better sticking in an ISA NIC ?
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:04:35 GMT