From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: serial cable/port problem?
Date: Wed, 20 Jul 2005 17:35:21 -0600 (Mountain Daylight Time) [thread overview]
Message-ID: <Pine.WNT.4.63.0507201733380.2024@merlin> (raw)
In-Reply-To: <20050720155908.GA27792@lava-net.com>
My guess would in fact be that you have a bent pin if the cable works
fine on a different machine. It is either that, or a short on the serial
board itself. If it is just a bent pin, you may be able to fix that by
straightening that. Of course, you take the risk of snapping it off
completely if you do it.
--
It's not one damn thing after another, it's the same damn thing over and
over. (History repeats itself)
Joseph C. Lininger
jbahm@pcdesk.net
Verification: 5eab38a77ac40416e075be8f50607ff7
And so it came to pass that on Wed, 20 Jul 2005, Igor Gueths said
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hi all. Quite recently, I thought that my serial port up and ddied on
my
> laptop. However, it resorted to being quite flaky at best; it decided
> to work fine on Windblows. Every so often, even with my 2.6.6 kernel,
> the port would act quite flaky. My conclusion that it was the cable
that
> was at fault. However, on another machine that I have (my server)
> running 1.6.11.7, the cable worked just fine with that particular
port.
> Could it be that some pins on the laptop port are bent? Reason I say
> that is as of now, I can only plug the cable in part way so that the
> Dectalk gets successfully probed. If I plug the cable in all the way,
> the device probe fails. Doe asyone have any other ideas that I may not
> have thought of? I really don't want to have to fry this port just so
I
> get Dell to replace it. Thanks!
> - --
> How many chunks could checkchunk check if checkchunck could check
chunks?
> - -- Alan Cox
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.0 (GNU/Linux)
>
> iQIVAwUBQt50y6e2pgKIdGq4AQoNqxAAtkRLRZCqU69tBNdk60/PlPeAbjiGO7wQ
> iuNqCZ1aM0QkLturTtRx/zZuFfh1BC4PgWvabdV3sMuoSwXArlUqhX8TH9NRhL/R
> P9P87QKxiMZV+kJBSvAGkhw9c+vwrXkr3SnqmImp5FnoyTMqy/BZ9NDXk2IGDShy
> wSU+ifJPvXpExVf4A7JUpeO+rHBB6IU7AJ4L17kgpeUZ2S+QyfGbgWFmJYOzNYJ5
> kLr+FSqtDEoZthBj6OlOvx90WO6IIHf3W1MrEuUAnk7F5y7WpAsvxJ71HT/0bQ39
> uN08nNHSFmESx+v8vdYmfdLvp1ta1duV02U3JKJUzIV7Ss7wyOy1x0gfiRv59JPW
> dnkWkkbCeeGvKFB0IjgLBNw9cCZescVz3c2+KqYWmbvLEytY16+B1rfbjksClTIk
> l0sgHNeOnfErkXwhrhfR1GnAKBzsc/FZpANMkQ/SRBZGSDCu0mEWucdX+c9HyBSE
> udTEhLHPXv27LEFwq8KqPxsYobvG9m3P8pkN9OK1SCPpqkpEgQKmc/isLLZZvP0F
> E4qkPP7Vx3/wd1VcOSkUpVgRSDgq3KE1XiH3h9WbdilLSmGaAmg38bK9j9mGt2NM
> wU9uHdzn/kDzuJeAT+X6hIeeVH5VEGPFX+CM4U6dAAx1UIYKzlbvXVObt/BLOBYl
> JaK8CJ0xT6I=
> =Ig/a
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` Joseph C. Lininger [this message]
` Igor Gueths
` Joseph C. Lininger
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.WNT.4.63.0507201733380.2024@merlin \
--to=jbahm@pcdesk.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).