From: Jim Wantz <jwantz@comcast.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: re: ethernet problem
Date: Mon, 7 May 2007 10:39:20 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705071038240.18894@localhost.localdomain> (raw)
In-Reply-To: <Pine.BSF.4.64.0705041806410.23780@freire2.furyyjbeyq.arg>
I tried 3 different cables. They are all almost brand new.
I ended up taking the computer to a store.
On Fri, 4 May 2007, Jude DaShiell wrote:
> Suggestion, put in a new never used ethernet cable then reboot the
> machine. It's probable your existing ethernet cable can't pass continuity
> tests anymore and when cables fail continuity tests you'll get messages
> back like that.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Jude DaShiell
` Jim Wantz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0705071038240.18894@localhost.localdomain \
--to=jwantz@comcast.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).