Marty Landman <[EMAIL PROTECTED]> writes:
>
> so I could've just done
>
> %ifdown -a && ifup -a

Yes, that would work.  In fact, "ifdown eth0 && ifup eth0" would just
restart the specific interface.  The "-a" flag just means all
interfaces flagged with "auto" in "/etc/network/interfaces".

> A fast steady blink, normal color (green for that particular nic). The
> steadiness is what made it look strange,

Okay, so, for whatever reason, the switch didn't like what the NIC was
doing and, probably, disabled the port.

> Newbie here, where are the kernel logs? I'm not ashamed to admit being
> an idiot, obviously ;x

All the logs are in "/var/log".  Kernel messages, and just about
everything else, are written to the "syslog" series of files.  Like
almost all the files in "/var/log", these files are rotated
periodically (for "syslog", it's on a daily basis), so you'll find the
most recent messages in "syslog", the next most recent in "syslog.0",
and older ones in "syslog.1.gz" through "syslog.6.gz".  Because
"syslog" is rotated daily, the relevant messages may have already
fallen off the end if this happened more than a week ago.

Fortunately, there's also a dedicated kernel logfile that contains
only kernel messages, the "kern.log*" series.  These are rotated once
a week, so you should be able to find your messages in there, if you
can't find them in "syslog*".

> If it's either the nic or the driver I vote for the driver since that
> nic's identical twin is installed on my wife's workstation which is
> running w98.

But your specific unit could be faulty.  For that matter, the cable
between your NIC and the switch might be flakey, or the specific port
on the switch might have a problem.

Since you're fortunate enough to have a twin NIC, I would suggest
swapping the NICs, being careful to swap the cable and port connection
at the same time (so your wife's machine is using the same
NIC-cable-port combination that you ran into trouble with on your
machine).  If the problem resurfaces, you have very strong evidence
for a driver problem.

-- 
Kevin <[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to