Re: minicom questions, need expert

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Gene Heskett wrote:
On Monday 12 May 2008, Gene Heskett wrote:
Greetings;

I'm trying to make an antique computer talk to this linux box via a
usb<->serial adaptor and a long USB extension cord that has a hub kit in
the far end of it.

When I plug in the cable to a 7 port extension hub here, dmesg reports:

May 12 14:00:58 coyote kernel: [314986.418050] usb 1-1.3: new full speed USB
device using ehci_hcd and address 33 May 12 14:00:58 coyote kernel:
[314986.503819] usb 1-1.3: configuration #1 chosen from 1 choice May 12
14:00:58 coyote kernel: [314986.504986] hub 1-1.3:1.0: USB hub found May 12
14:00:58 coyote kernel: [314986.509657] hub 1-1.3:1.0: 4 ports detected May
12 14:00:58 coyote kernel: [314986.818989] usb 1-1.3.4: new full speed USB
device using ehci_hcd and address 34 May 12 14:00:58 coyote kernel:
[314986.910261] usb 1-1.3.4: configuration #1 chosen from 1 choice May 12
14:00:58 coyote kernel: [314986.910630] ftdi_sio 1-1.3.4:1.0: FTDI USB
Serial Device converter detected May 12 14:00:58 coyote kernel:
[314986.910684] ftdi_sio: Detected FT232RL May 12 14:00:58 coyote kernel:
[314986.910721] usb 1-1.3.4: FTDI USB Serial Device converter now attached
to ttyUSB1

And I have sent several very long directory listings up the cable, but
nothing, not a single character is being output to the minicom screen.
I do not know if the minicom utility can reach out into that FT232RL to
tell it what the baud rate is or not, no clue.  If minicom can't do that,
then what linux utility can perform this initialization?

Thanks all.
PEBKAC. It turned out that the serial port params on the legacy machine were
a bit foobared. And to minicom, it is now working well. A small copy/paste:
 Directory of /dd/cmds   2008/05/12 14:42

Owner  Last modified   Attributes Sector Bytecount Name
----- ---------------- ---------- ------ --------- ----
   0  2006/04/21 13:38  --e-rewr   1EBF8      1B00 asm
   0  2006/04/21 13:38  --e-rewr   1EBFC       1FF attr


I can put the fixes for that in the startup file for the coco3/nitros9 machine.
Now, I would like to be able to put something in my own rc.local that would
first tune that /dev/ttyUSB1 port for the proper params, then go away and
allow a "cat /dev/ttyUSB1 >/lp3" to be done, the idea being to use the linux
box to convert that text into something for a modern printer which doesn't
understand P.O.A. (Plain Old Ascii). I need to be able to make paper copies
of program src, probably from the assembler.
Suggestions gleefully checked out, thanks all.
Forgot "man stty" as well.  Sorry!
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer                       [email protected] -
- Hosting Consulting, Inc.                                           -
-                                                                    -
-                 All generalizations are false.                     -
----------------------------------------------------------------------

--
fedora-list mailing list
[email protected]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux