Prev: Pleasantly surprised by Linux...for a couple of days...The ShortHappy Life of Francis Linux Macomber
From: Andy on 10 Aug 2010 17:02
I have two identical notebook computers both installed with Redhat 4.6
WS via the same kickstart script. These systems are both configured
with two rs-232 ports (/dev/ttyS0 and /dev/ttyS1). These system both
boot into X and use xterms that execute cu to monitor both serial
ports. Both read and display data from the serial ports correctly.
Onely one, however, is correctly sending function keys to the remote
system on the serial line.

On the working computer if I type:

> stty -F /dev/ttyS0
Speed 9600 baud; line = 0;
-brkint -imaxbel

On the not working computer I get:

> stty -F /dev/ttyS0
Speed 9600 baud; line = 0;
min = 1; time = 1;
-brkint -icrnl -imaxbel
-opost
-isig -icanon -iexten -echo -echoe -echok

How do two systems (identical hardware) that are installed with the
same kickstart script, have vastly different serial port
configurations? I cannot find any configuration file in the /etc tree
that initializes these settings on boot. This is starting to drize me
crazy. I can't seem to get my install to configure the serial ports
to a working state without first signing in as root and messing around
with setserial and stty. Can someone point me to any config files
that may hold the key to this problem?

This is a Redhat 4.6 minimal install. A small subset of packages were
added after the minimal install to get X up and running with mwm and
xterm.
From: Nico Kadel-Garcia on 11 Aug 2010 07:52
On Aug 10, 5:02 pm, Andy <drew.sulli...(a)gmail.com> wrote:
> I have two identical notebook computers both installed with Redhat 4.6
> WS via the same kickstart script.  These systems are both configured
> with two rs-232 ports (/dev/ttyS0 and /dev/ttyS1).  These system both
> boot into X and use xterms that execute cu to monitor both serial
> ports.  Both read and display data from the serial ports correctly.
> Onely one, however, is correctly sending function keys to the remote
> system on the serial line.

First: RHEL 4.6 is basically 5 years old. You should update to 5.5 if
at all possible, especially for laptop drivers.


> On the working computer if I type:
>
> > stty -F /dev/ttyS0
>
>       Speed 9600 baud;  line = 0;
>       -brkint -imaxbel
>
> On the not working computer I get:
>
> > stty -F /dev/ttyS0
>
>       Speed 9600 baud;  line = 0;
>       min = 1;  time = 1;
>       -brkint -icrnl -imaxbel
>       -opost
>       -isig -icanon -iexten -echo -echoe -echok
>
> How do two systems (identical hardware) that are installed with the
> same kickstart script, have vastly different serial port
> configurations?  I cannot find any configuration file in the /etc tree
> that initializes these settings on boot.  This is starting to drize me
> crazy.  I can't seem to get my install to configure the serial ports
> to a working state without first signing in as root and messing around
> with setserial and stty.  Can someone point me to any config files
> that may hold the key to this problem?

Investigate the "setserial" command, and investigate the motherboards
of your two "identical" computers by booting them and getting the
model number off the BIOS.

It should also be possible to install and run HylaFAX, which has the
very useful 'faxaddmodem' tool for probing modems. It's available from
your nearest RPMforge repository. It's a very solid toolkit written
mostly by Sam Leffler, the key author of TIFF and one of the authors
of BSD Linux, and It Just Works(tm).

> This is a Redhat 4.6 minimal install.  A small subset of packages were
> added after the minimal install to get X up and running with mwm and
> xterm.

You might do a side by side comparison of "rpm -qa | sort" to assure
yourself of no differences, or of the contents of "/etc/".
 | 
Pages: 1
Prev: Pleasantly surprised by Linux...for a couple of days...The ShortHappy Life of Francis Linux Macomber