* Trouble with serial ports
@ 2002-10-15 4:31 Alan Womack
2002-10-15 6:46 ` Ray Olszewski
2002-10-15 14:09 ` lawson_whitney
0 siblings, 2 replies; 8+ messages in thread
From: Alan Womack @ 2002-10-15 4:31 UTC (permalink / raw
To: Majordomo leben.com
OK, made a loop back cable. Works great on the windows box, fast and accurate.
On the linux box it's INCREDIBLY slow, makes 300 baud look blazing. Take like 2 hours to print the whole dmesg:
cat dmesg (I have it saved to a file) >/dev/ttyS01
on second terminal
od -v /dev/ttyS01
nothing is dropped, but it is SLOW SLOW SLOW
So I connect a cable up between the two machines, nothing nada zip nat. NOTHING comes over from either direction.
So I take the cable off the linux end, connect it to the windows workstation and swap the gender to go from com1 to com2. I still get absolutely nothing.
Therefore I checked the cable, pin 2 to pin 3 on the other end, that is all correct.
I pulled my STB 4Com card out of the linux box, changed interrupts around to:
3 for port 1 on 02A8
12 for port 2 on 02E8
15 for port 3 on 02F8
15 for port 4 on 03E8
put the loopback on ttyS00, the motherboard serial port. Works great, very fast.
put the loopback on the new TTYS01, finally got a quick response.
cabled between the two computers, nothing.
Put loopback on TTYS02, VERY SLOW
Put loopback on TTYS03, VERY SLOW
Put loopback on TTYS04, error
alan@webby:alan $ od -v -t a /dev/ttyS04
od: /dev/ttyS04: Input/output error
0000000
What baffles me the most is I don't get communications between windows com ports com1 and com2 with a cable, and the same with the linux machine. That defies what I know of serial communcations.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Trouble with serial ports
2002-10-15 4:31 Trouble with serial ports Alan Womack
@ 2002-10-15 6:46 ` Ray Olszewski
2002-10-15 14:09 ` lawson_whitney
1 sibling, 0 replies; 8+ messages in thread
From: Ray Olszewski @ 2002-10-15 6:46 UTC (permalink / raw
To: Alan Womack, linux-newbie
Your style of reporting makes this hard to interpret. Here are a few thoughts.
Initially, a style note -- case counts in Unix/Linux, and the correct names
are ttyS00, ttyS01, and so forth ... so TTYS02, TTYS03, and the like are
not designators for serial ports on Linux systems.
Now the substantive reactions ...
First, you tell us what you changed the STB 4Com card interrupts *to*, but
not what you changed them *from*. Since both ttyS00 and ttyS01 seem to work
with the STB 4Com card IRQs you tell us about, it's a good guess that the
prior settings caused some problem. But without knowing what the prior
settings were, I can only guess wildly as to what it might have been.
Second, when you connect the Linux and the Windows hosts (or the 2 serial
ports on the Windows host), I assume you are using a null-modem cable
(since you say "pin 2 to pin 3 on the other end, that is all
correct"). But there are several flavors of null-modem cables ... the only
commonalities among them is that they connect
pin 2 <---> pin 3
pin 3 <---> pin 2
pin 7 <---> pin 7
(using the DB-25 pin numberings, not the different DB-9 numberings). So it
is not meaningful to say "that all is correct", since there are several
options for the other handshaking pins, and you have to tell us which ones
your cable uses.
Third, when you try and fail to communicate with a cable, what applications
are you using in the tests? How are they handling handshaking? Is this
consistent with the cabling choice you made (and for that matter, are the
two ends handling handshaking consistently)?
Fourth, after you changed the IRQs on the STB 4Com card, did you use
setserial to assign the appropriate IRQ and ioport values to ttyS02,
ttyS03, and ttyS04 (and presumably ttyS05, though you didn't mention
testing it)? If not, you might run setserial in probe mode (e.g.,
"setserial /dev/ttyS02") to see where each device expects to find its UART.
At 09:31 PM 10/14/02 -0700, Alan Womack wrote:
>OK, made a loop back cable. Works great on the windows box, fast and
>accurate.
>
>On the linux box it's INCREDIBLY slow, makes 300 baud look blazing. Take
>like 2 hours to print the whole dmesg:
>
>cat dmesg (I have it saved to a file) >/dev/ttyS01
>
>on second terminal
>
>od -v /dev/ttyS01
>
>nothing is dropped, but it is SLOW SLOW SLOW
>
>So I connect a cable up between the two machines, nothing nada zip
>nat. NOTHING comes over from either direction.
>
>So I take the cable off the linux end, connect it to the windows
>workstation and swap the gender to go from com1 to com2. I still get
>absolutely nothing.
>
>Therefore I checked the cable, pin 2 to pin 3 on the other end, that is
>all correct.
>
>I pulled my STB 4Com card out of the linux box, changed interrupts around to:
>
>3 for port 1 on 02A8
>12 for port 2 on 02E8
>15 for port 3 on 02F8
>15 for port 4 on 03E8
>
>put the loopback on ttyS00, the motherboard serial port. Works great,
>very fast.
>put the loopback on the new TTYS01, finally got a quick response.
>
>cabled between the two computers, nothing.
>
>Put loopback on TTYS02, VERY SLOW
>Put loopback on TTYS03, VERY SLOW
>Put loopback on TTYS04, error
>alan@webby:alan $ od -v -t a /dev/ttyS04
>od: /dev/ttyS04: Input/output error
>0000000
>
>
>What baffles me the most is I don't get communications between windows com
>ports com1 and com2 with a cable, and the same with the linux
>machine. That defies what I know of serial communcations.
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA ray@comarre.com
-------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Trouble with serial ports
2002-10-15 4:31 Trouble with serial ports Alan Womack
2002-10-15 6:46 ` Ray Olszewski
@ 2002-10-15 14:09 ` lawson_whitney
1 sibling, 0 replies; 8+ messages in thread
From: lawson_whitney @ 2002-10-15 14:09 UTC (permalink / raw
To: arwbackup; +Cc: linux-newbie
On Mon, 14 Oct 2002, Alan Womack wrote:
> OK, made a loop back cable. Works great on the windows box, fast and accurate.
>
> On the linux box it's INCREDIBLY slow, makes 300 baud look blazing. Take like 2 hours to print the whole dmesg:
>
> cat dmesg (I have it saved to a file) >/dev/ttyS01
>
> on second terminal
>
> od -v /dev/ttyS01
>
> nothing is dropped, but it is SLOW SLOW SLOW
>
HUH? Are you reading it back from the same port you wrote it to?
What does that have to do with the cable? You can set a serial port to
echo the input, but it just seems odd.
One other thing: if you connect 2 serial ports, and write to one at one
speed and read from the other at a different speed, you will get either
_Nothing_ or garbage. You can see or set the speed with
stty -F <device>
but the app can and probably will change it when it opens the port.
Lawson
---oops---
________________________________________________________________
GET INTERNET ACCESS FROM JUNO!
Juno offers FREE or PREMIUM Internet access for less!
Join Juno today! For your FREE software, visit:
http://dl.www.juno.com/get/web/.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Trouble with serial ports
@ 2002-11-03 16:25 Alan Womack
2002-11-03 17:01 ` Ray Olszewski
2002-11-03 23:07 ` lawson_whitney
0 siblings, 2 replies; 8+ messages in thread
From: Alan Womack @ 2002-11-03 16:25 UTC (permalink / raw
To: Majordomo leben.com
I have a chance to get back to this issue, it appears actually that none of the STB 4Com ports are working "correctly" I can get some "data" from od -v /dev/ttyS01 but it is a file of ^@ the control character and the longer I leave it up the more it gets whether data is being sent or not. I have tested /dev/ttyS00 with a null modem cable and details follow. I want to work on just /dev/ttyS01 at this moment.
>> First, you tell us what you changed the STB 4Com card interrupts *to*, but
>>
>> not what you changed them *from*. Since both ttyS00 and ttyS01 seem to
>> work
>> with the STB 4Com card IRQs you tell us about, it's a good guess that the
>> prior settings caused some problem. But without knowing what the prior
>> settings were, I can only guess wildly as to what it might have been.
The STB 4Com card came to me used, I have attempted to set the card up in a manner as such:
setserial /dev/ttyS04 baud_base 9600 irq 15 port 0x03E8 ^fourport ^skip_test
setserial /dev/ttyS03 baud_base 9600 irq 15 port 0x02F8 ^fourport ^skip_test
setserial /dev/ttyS02 baud_base 9600 irq 15 port 0x02E8 ^fourport ^skip_test
setserial /dev/ttyS01 baud_base 9600 irq 3 port 0x02A8 ^fourport ^skip_test
setserial -a /dev/ttyS01
setserial -a /dev/ttyS02
setserial -a /dev/ttyS03
setserial -a /dev/ttyS04
root@webby:root# ./serial.ports
/dev/ttyS01, Line 1, UART: 16550A, Port: 0x02a8, IRQ: 3
Baud_base: 9600, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS02, Line 2, UART: 16550A, Port: 0x02e8, IRQ: 15
Baud_base: 9600, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS03, Line 3, UART: 16550A, Port: 0x02f8, IRQ: 15
Baud_base: 9600, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS04, Line 4, UART: unknown, Port: 0x03e8, IRQ: 15
Baud_base: 9600, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
>> Second, when you connect the Linux and the Windows hosts (or the 2 serial
>> ports on the Windows host), I assume you are using a null-modem cable
>> (since you say "pin 2 to pin 3 on the other end, that is all
>> correct"). But there are several flavors of null-modem cables ... the
>> only
>> commonalities among them is that they connect
>> pin 2 <---> pin 3
>> pin 3 <---> pin 2
>> pin 7 <---> pin 7
I have constructed a null modem cable, I have tested it between COM1 and COM2 on my windows workstation, and between COM1 and /dev/ttyS00 successfully. e.g. a 50K + test file with no apparent garabage or corruption using 9600 8 n 1. I was successful in going from windows to linux and from linux to windows without issue on /dev/ttyS00. /dev/ttyS00 is the motherboard serial port.
The cable pin out is db9:
2 -- 3
3 -- 2
4 -- 6+1
5 -- 5
6+1 -- 4
7 -- 8
8 -- 7
>> Third, when you try and fail to communicate with a cable, what
>> applications
>> are you using in the tests? How are they handling handshaking? Is this
>> consistent with the cabling choice you made (and for that matter, are the
>> two ends handling handshaking consistently)?
On windows I am using Terra Term Pro, a freeware serial/telnet client. I have no flow control selected and 9600 8 n 1 as my settings.
On linux I have used term with term /dev/ttyS00 9600 8 n 1
I have used od -v /dev/ttyS00
I have used stty -F /dev/ttyS00 raw -echo 9600 ; cat /dev/ttyS00 > /tmp/0.txt
>> Fourth, after you changed the IRQs on the STB 4Com card, did you use
>> setserial to assign the appropriate IRQ and ioport values to ttyS02,
>> ttyS03, and ttyS04 (and presumably ttyS05, though you didn't mention
>> testing it)? If not, you might run setserial in probe mode (e.g.,
>> "setserial /dev/ttyS02") to see where each device expects to find its
>> UART.
root@webby:root# setserial /dev/ttyS01
/dev/ttyS01, UART: 16550A, Port: 0x02a8, IRQ: 3
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Trouble with serial ports
2002-11-03 16:25 Alan Womack
@ 2002-11-03 17:01 ` Ray Olszewski
2002-11-03 23:07 ` lawson_whitney
1 sibling, 0 replies; 8+ messages in thread
From: Ray Olszewski @ 2002-11-03 17:01 UTC (permalink / raw
To: linux-newbie
OK. Since you've only been testing ttyS01 (the first of the 4 ports), we
really do not know if the others are working or not. Your cabling looks
good (subject to one hesitation; see below) and your other test standards
look good too. So I'm drawn to the difference between the first STB 4Com
port and the others in your configuration.
At 08:25 AM 11/3/02 -0800, Alan Womack wrote:
>I have a chance to get back to this issue, it appears actually that none
>of the STB 4Com ports are working "correctly" I can get some "data" from
>od -v /dev/ttyS01 but it is a file of ^@ the control character and the
>longer I leave it up the more it gets whether data is being sent or
>not. I have tested /dev/ttyS00 with a null modem cable and details
>follow. I want to work on just /dev/ttyS01 at this moment.
[...]
>setserial /dev/ttyS01 baud_base 9600 irq 3 port 0x02A8 ^fourport ^skip_test
[...]
>root@webby:root# ./serial.ports
>/dev/ttyS01, Line 1, UART: 16550A, Port: 0x02a8, IRQ: 3
> Baud_base: 9600, close_delay: 50, divisor: 0
> closing_wait: 3000
> Flags: spd_normal
Since the setserial probe finds a UART type associated with ttyS01, that
device is configured correctly for *some* serial port. But since it also is
using the standard values for the second serial port ... does your mobo
have 1 or 2 serial ports (an onboard modem port counts)? My first thought
is that you have an irq/ioport conflict (newer kernels support irq sharing,
but you can't share ioports). If you do, either move S01 to a different
itq/ioport combination, or make sure the modem/serial port is diaabled in
the mobo's BIOS.
If that is not the problem ... I don't have experience with the specific
4-port card you are using, but I do recall that some multiport cards (the
old BocaBoard 8 comes to mind) did not provide all of the control signals
(DTR/DSR. RTS/CTS, DCD), while onboard serial ports pretty reliably do. You
might want to retest with a null-modem cable that loopbacks the control
signals rather than one that passes them through (even appropriately
crossed, as your cable does).
If none of that helps ... the only thing I am left with is wondering if the
card itself works. You might want to repeat the tests using the port
associated with ttyS02 as a check.
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA ray@comarre.com
-------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Trouble with serial ports
2002-11-03 16:25 Alan Womack
2002-11-03 17:01 ` Ray Olszewski
@ 2002-11-03 23:07 ` lawson_whitney
1 sibling, 0 replies; 8+ messages in thread
From: lawson_whitney @ 2002-11-03 23:07 UTC (permalink / raw
To: arwbackup; +Cc: linux-newbie
On Sun, 3 Nov 2002, Alan Womack wrote:
> The STB 4Com card came to me used, I have attempted to set the card up in a manner as such:
>
> setserial /dev/ttyS04 baud_base 9600 irq 15 port 0x03E8 ^fourport ^skip_test
> setserial /dev/ttyS03 baud_base 9600 irq 15 port 0x02F8 ^fourport ^skip_test
> setserial /dev/ttyS02 baud_base 9600 irq 15 port 0x02E8 ^fourport ^skip_test
> setserial /dev/ttyS01 baud_base 9600 irq 3 port 0x02A8 ^fourport ^skip_test
Wy are you doing this? The baud_base of a 16550a is 115200 unless this
is very strange hardware indeed. The baud base is just used by the
serial driver to choose which divisor to set for a requested speed.
A baud base of 9600 with a requested speed of 9600 give a divisor of 1,
which will make a normal 16550a run at 115200.
It won't see anything coming over the cable at 9600, or maybe a little
garbage.
> setserial -a /dev/ttyS01
> setserial -a /dev/ttyS02
> setserial -a /dev/ttyS03
> setserial -a /dev/ttyS04
>
> root@webby:root# ./serial.ports
> /dev/ttyS01, Line 1, UART: 16550A, Port: 0x02a8, IRQ: 3
> Baud_base: 9600, close_delay: 50, divisor: 0
> closing_wait: 3000
> Flags: spd_normal
>
> /dev/ttyS02, Line 2, UART: 16550A, Port: 0x02e8, IRQ: 15
> Baud_base: 9600, close_delay: 50, divisor: 0
> closing_wait: 3000
> Flags: spd_normal
>
> /dev/ttyS03, Line 3, UART: 16550A, Port: 0x02f8, IRQ: 15
> Baud_base: 9600, close_delay: 50, divisor: 0
> closing_wait: 3000
> Flags: spd_normal
>
> /dev/ttyS04, Line 4, UART: unknown, Port: 0x03e8, IRQ: 15
> Baud_base: 9600, close_delay: 50, divisor: 0
> closing_wait: 3000
> Flags: spd_normal
>
> I have constructed a null modem cable, I have tested it between COM1 and COM2
on my windows workstation, and between COM1 and /dev/ttyS00 successfully.
e.g. a 50K + test file with no apparent garabage or corruption using 9600 8 n 1
I was successful in going from windows to linux and from linux to windows
without issue on /dev/ttyS00. /dev/ttyS00 is the motherboard serial port.
Probably because you didn't mess with the baud_base.
>
> The cable pin out is db9:
>
> 2 -- 3
> 3 -- 2
> 4 -- 6+1
> 5 -- 5
> 6+1 -- 4
> 7 -- 8
> 8 -- 7
>
>
> On windows I am using Terra Term Pro, a freeware serial/telnet client. I have no flow control selected and 9600 8 n 1 as my settings.
>
> On linux I have used term with term /dev/ttyS00 9600 8 n 1
> I have used od -v /dev/ttyS00
> I have used stty -F /dev/ttyS00 raw -echo 9600 ; cat /dev/ttyS00 > /tmp/0.txt
>
What do you have against minicom or cu? Or try if Wine will run Terra
Term Pro.
Lawson
--
---oops---
________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit www.juno.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Trouble with serial ports
@ 2002-11-04 5:27 Alan Womack
0 siblings, 0 replies; 8+ messages in thread
From: Alan Womack @ 2002-11-04 5:27 UTC (permalink / raw
To: Majordomo leben.com, linux-newbie
>> OK. Since you've only been testing ttyS01 (the first of the 4 ports), we
>> really do not know if the others are working or not. Your cabling looks
>> good (subject to one hesitation; see below) and your other test standards
>> look good too. So I'm drawn to the difference between the first STB 4Com
>> port and the others in your configuration.
>> At 08:25 AM 11/3/02 -0800, Alan Womack wrote:
>> >I have a chance to get back to this issue, it appears actually that none
>> >of the STB 4Com ports are working "correctly" I can get some "data" from
>> >od -v /dev/ttyS01 but it is a file of ^@ the control character and the
>> >longer I leave it up the more it gets whether data is being sent or
>> >not. I have tested /dev/ttyS00 with a null modem cable and details
>> >follow. I want to work on just /dev/ttyS01 at this moment.
>> [...]
>> >setserial /dev/ttyS01 baud_base 9600 irq 3 port 0x02A8 ^fourport
>> ^skip_test
>> [...]
>> >root@webby:root# ./serial.ports
>> >/dev/ttyS01, Line 1, UART: 16550A, Port: 0x02a8, IRQ: 3
>> > Baud_base: 9600, close_delay: 50, divisor: 0
>> > closing_wait: 3000
>> > Flags: spd_normal
>> Since the setserial probe finds a UART type associated with ttyS01, that
>> device is configured correctly for *some* serial port. But since it also
>> is
>> using the standard values for the second serial port ... does your mobo
>> have 1 or 2 serial ports (an onboard modem port counts)? My first thought
>> is that you have an irq/ioport conflict (newer kernels support irq
>> sharing,
>> but you can't share ioports). If you do, either move S01 to a different
>> itq/ioport combination, or make sure the modem/serial port is diaabled in
>> the mobo's BIOS.
My motherboard only has one physical serial port, and I am sure the built in modem jumper is in the diabled position.
My kernel is 2.4.18 built from www.linuxfromscratch.org book 3.3
>> If that is not the problem ... I don't have experience with the specific
>> 4-port card you are using, but I do recall that some multiport cards (the
>> old BocaBoard 8 comes to mind) did not provide all of the control signals
>>
>> (DTR/DSR. RTS/CTS, DCD), while onboard serial ports pretty reliably do.
>> You
>> might want to retest with a null-modem cable that loopbacks the control
>> signals rather than one that passes them through (even appropriately
>> crossed, as your cable does).
>> If none of that helps ... the only thing I am left with is wondering if
>> the
>> card itself works. You might want to repeat the tests using the port
>> associated with ttyS02 as a check.
I have physically installed the board into an old windows workstation and verified that port 1 with
IRQ3 port 0x2a8 works via my cable and talking between windows machines.
I am going to remove the card and change each different port to this configuration and retest, that way I can know that all of them physically function or not.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Trouble with serial ports
@ 2002-11-04 5:33 Alan Womack
0 siblings, 0 replies; 8+ messages in thread
From: Alan Womack @ 2002-11-04 5:33 UTC (permalink / raw
To: Majordomo leben.com
>> > The STB 4Com card came to me used, I have attempted to set the card up
>> in a manner as such:
>> >
>> > setserial /dev/ttyS04 baud_base 9600 irq 15 port 0x03E8 ^fourport
>> ^skip_test
>> > setserial /dev/ttyS03 baud_base 9600 irq 15 port 0x02F8 ^fourport
>> ^skip_test
>> > setserial /dev/ttyS02 baud_base 9600 irq 15 port 0x02E8 ^fourport
>> ^skip_test
>> > setserial /dev/ttyS01 baud_base 9600 irq 3 port 0x02A8 ^fourport
>> ^skip_test
>> Wy are you doing this? The baud_base of a 16550a is 115200 unless this
>> is very strange hardware indeed. The baud base is just used by the
>> serial driver to choose which divisor to set for a requested speed.
>> A baud base of 9600 with a requested speed of 9600 give a divisor of 1,
>> which will make a normal 16550a run at 115200.
>> It won't see anything coming over the cable at 9600, or maybe a little
>> garbage.
It is certainly not clear in the documentation. That's one of my biggest time wasters with linux is the ambiguity of documentation. A clear usage example would go a LONG WAYS in helping in the man page. Maybe someday I will know enough to make some of those updates, make the diff patch and send it off to the maintainer to get it ignored.
>> Probably because you didn't mess with the baud_base.
I believe you may be correct, a quick grep of my .bash_history showed no setserial on that line.
>> >
>> > The cable pin out is db9:
>> >
>> > 2 -- 3
>> > 3 -- 2
>> > 4 -- 6+1
>> > 5 -- 5
>> > 6+1 -- 4
>> > 7 -- 8
>> > 8 -- 7
>> >
>> >
>> > On windows I am using Terra Term Pro, a freeware serial/telnet client.
>> I have no flow control selected and 9600 8 n 1 as my settings.
>> >
>> > On linux I have used term with term /dev/ttyS00 9600 8 n 1
>> > I have used od -v /dev/ttyS00
>> > I have used stty -F /dev/ttyS00 raw -echo 9600 ; cat /dev/ttyS00 >
>> /tmp/0.txt
>> >
>> What do you have against minicom or cu? Or try if Wine will run Terra
>> Term Pro.
I use Terra Term Pro on the windows box, there is no X on my lfs box. Minicom I read was difficult to work with a make sure it did what you told it to do, therefor I'm using term and od and stty now for testing.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2002-11-04 5:33 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-10-15 4:31 Trouble with serial ports Alan Womack
2002-10-15 6:46 ` Ray Olszewski
2002-10-15 14:09 ` lawson_whitney
-- strict thread matches above, loose matches on Subject: below --
2002-11-03 16:25 Alan Womack
2002-11-03 17:01 ` Ray Olszewski
2002-11-03 23:07 ` lawson_whitney
2002-11-04 5:27 Alan Womack
2002-11-04 5:33 Alan Womack
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.