Bug 164267 - cat < /dev/ttyS0 gives no output
cat < /dev/ttyS0 gives no output
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
4
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Jones
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-07-26 09:55 EDT by Rueh Hänä
Modified: 2015-01-04 17:21 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-08-26 17:44:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Rueh Hänä 2005-07-26 09:55:52 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
Hi there

None of the components listed, have to do with my problem, so far i think. 

I have two FC4 Servers with same configuration. They should communicate over a serial cable, that is plugged into /dev/ttyS0. 

If i do host A:

echo "sometext" > /dev/ttyS0

i should receive the text on Host B with

cat < /dev/ttyS0

But there is no text. 

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
HOST A
echo "sometext" > /dev/ttyS0

HOST B
cat < /dev/ttyS0

Actual Results:  Nothing

Expected Results:  The text should have reached the other Host (B)

Additional info:

Both Servers are HP ProLiant DL120's with 2.4Ghz CPU, 1GB Memory
Comment 1 Jack Aboutboul 2005-07-26 10:14:14 EDT
This is a kernel issue. Changed component for now, should resolve later today
after I confirm a few things.
Comment 2 Dave Jones 2005-08-26 17:44:48 EDT
This works fine here with the current kernel.

Check your cabling, and be sure you've actually plugged it into ttyS0.
It sounds like a hardware problem to me.

Note You need to log in before you can comment on or make changes to this bug.