public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hello Bello" <domician@gmail.com>
To: linux-serial@vger.kernel.org
Subject: Re: serial port cannot be read in linux
Date: Sat, 2 Jun 2007 23:40:49 +0200	[thread overview]
Message-ID: <730b6c6b0706021440y7bb07837l104f1afbc25ee4fa@mail.gmail.com> (raw)
In-Reply-To: <730b6c6b0706021439w41923cddvbf9fe953255190c0@mail.gmail.com>

Hello,

I am trying to use a serial port in linux. My architecture is:
-compaq evo n600c
-debian GNU Linux 3.1
-vanilla kernel: Linux furge 2.6.21 #2 SMP Sat Jun 2 21:25:42 CEST
2007 i686 GNU/Linux

This is my dmesg output:
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS2 at I/O 0x3e8 (irq = 3) is a 16550A
00:02: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

I am trying to test the serial port by jumpering the receive and
transmit pins of the serial port.

Using this hardware, windows XP serial port tester program echos back
the characters written to the port, so the hardware is ok.

However, in Linux, the port stays dumb. I can write to it, but there
is nothing to be read from it.
e.g.
cat /dev/ttyS0 > /tmp/serial.txt &; echo "a" > /dev/ttyS0; cat /tmp/serial.txt
or
cp /dev/ttyS0 /dev/tty1; echo "a" > /dev/ttyS0

I have read through the "Cannot write but not read" topic in this
mailing list, but without any success.
Also I have tried several serial port testing programs, all in vain.
Kernel recompilations made no luck.


I would really appreciate your help,
Thanks,
Gabor

       reply	other threads:[~2007-06-02 21:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <730b6c6b0706021439w41923cddvbf9fe953255190c0@mail.gmail.com>
2007-06-02 21:40 ` Hello Bello [this message]
2007-06-04  6:46   ` serial port cannot be read in linux kees
     [not found]     ` <730b6c6b0706051644j16cefd81y882b52602bad98f6@mail.gmail.com>
2007-06-06 17:38       ` Hello Bello

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=730b6c6b0706021440y7bb07837l104f1afbc25ee4fa@mail.gmail.com \
    --to=domician@gmail.com \
    --cc=linux-serial@vger.kernel.org \
    /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