From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ns.pcdesk.net ([65.100.173.137] helo=pcdesk.net) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1DvO6T-0005VJ-00 for ; Wed, 20 Jul 2005 19:35:53 -0400 Received: from merlin.pcdesk.net ([::ffff:192.168.0.13]) (AUTH: LOGIN jbahm@pcdesk.net, TLS: TLSv1/SSLv3,128bits,RC4-MD5) by pcdesk.net with esmtp; Wed, 20 Jul 2005 17:35:16 -0600 id 01C0F9A3.42DEDFB4.00002CD1 Date: Wed, 20 Jul 2005 17:35:21 -0600 (Mountain Daylight Time) From: "Joseph C. Lininger" To: "Speakup is a screen review system for Linux." In-Reply-To: <20050720155908.GA27792@lava-net.com> Message-ID: References: <20050720155908.GA27792@lava-net.com> X-X-Sender: jbahm@pcdesk.net@imap.pcdesk.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: serial cable/port problem? X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2005 23:35:53 -0000 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 >