minicom with a USB to RS-232 converter
Hi Guys,
I am having problems configuring minicom to work with a usb to RS-232 serial converter, the problem which I am having is outlined below, I was wondering whether anyone else has come across this problem also. I've tried searching google with no luck.
Outline:
My laptop is running Redhat 9, kernel: 2.4.20-8
I'm trying to gather output from Serial A port with various Sun Servers and capture the output with minicom. I haven't got a serial connection on my laptop so i've purchased a usb to RS-232 serial converter (ATEN).
I run '$insmod usbserial' and receive
-------------------
bash-2.05b# insmod usbserial
Using /lib/modules/2.4.20-8/kernel/drivers/usb/serial/usbserial.o
insmod: a module named usbserial already exists
--------------------
I also run '$insmod pl2303' and receive
--------------------
bash-2.05b# insmod pl2303
Using /lib/modules/2.4.20-8/kernel/drivers/usb/serial/pl2303.o
insmod: a module named pl2303 already exists
----------------------
So i assume that the correct modules have been installed (?)
When i unplug and plug in the converter into the serial port I receive the following logs in /var/log/messages
------------------------
Nov 12 17:51:34 speculator kernel: hub.c: new USB device 00:03.0-1, assigned address 8
Nov 12 17:51:34 speculator kernel: usbserial.c: PL-2303 converter detected
Nov 12 17:51:34 speculator kernel: usbserial.c: PL-2303 converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
Nov 12 17:51:37 speculator /etc/hotplug/usb.agent: Setup pl2303 for USB product
557/2008/1
Nov 12 17:51:38 speculator devlabel: devlabel service started/restarted
-------------------------
When i fire up minicom (9600 8N1) connecting to /dev/usb/ttyUSB0 I am unable to gather any output from Serial A on the server. The coverter itself lights up indicating that there is data transmitting over the connection however I believe that minicom may be inconfigured properly.
I've used the same hardware setup with hyperterminal on the windoze partition with hyperterminal and it seems to capture the output fine, however, keeping the same physical connection with Linux doesn't seem to work. I can only deduce that the problem lies at the application layer.
Is minicom configured to work with /dev/usb/ttyUSBx ?
Any clues on which other parameters need configuring to make minicom compatible?
I've read that some other adapters work fine (e.g. Keyspan/Belkin) however i've already invested $ on this converter (unfortunately)
Any advice would be greatly appreciated.
Hoa.
|