Skip to main content

Using Keyspan USA-19HS with RHEL (minicom)

Using the keyspan is fairly simple - however, I do occasionally run into issues using it in Linux so I thought it would be good to document a working configuration


$ sudo tail -f /var/log/messages
Oct 19 09:05:07 neo kernel: usb 1-1.1: new full speed USB device number 9 using ehci_hcd
Oct 19 09:05:07 neo kernel: usb 1-1.1: New USB device found, idVendor=06cd, idProduct=0121
Oct 19 09:05:07 neo kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 19 09:05:07 neo kernel: usb 1-1.1: Product: Keyspan USA-19H
Oct 19 09:05:07 neo kernel: usb 1-1.1: Manufacturer: Keyspan, a division of InnoSys Inc.
Oct 19 09:05:07 neo kernel: usb 1-1.1: configuration #1 chosen from 2 choices
Oct 19 09:05:07 neo kernel: usbcore: registered new interface driver usbserial
Oct 19 09:05:07 neo kernel: USB Serial support registered for generic
Oct 19 09:05:07 neo kernel: usbcore: registered new interface driver usbserial_generic
Oct 19 09:05:07 neo kernel: usbserial: USB Serial Driver core
Oct 19 09:05:07 neo kernel: USB Serial support registered for Keyspan - (without firmware)
Oct 19 09:05:07 neo kernel: USB Serial support registered for Keyspan 1 port adapter
Oct 19 09:05:07 neo kernel: USB Serial support registered for Keyspan 2 port adapter
Oct 19 09:05:07 neo kernel: USB Serial support registered for Keyspan 4 port adapter
Oct 19 09:05:07 neo kernel: keyspan 1-1.1:1.0: Keyspan 1 port adapter converter detected
Oct 19 09:05:07 neo kernel: usb 1-1.1: Keyspan 1 port adapter converter now attached to ttyUSB0
Oct 19 09:05:07 neo kernel: usbcore: registered new interface driver keyspan
Oct 19 09:05:07 neo kernel: keyspan: v1.1.5:Keyspan USB to Serial Converter Driver
Oct 19 09:05:07 neo modem-manager: (ttyUSB0) opening serial device...
Oct 19 09:05:19 neo modem-manager: (ttyUSB0) closing serial device...
Oct 19 09:05:20 neo modem-manager: (ttyUSB0) opening serial device...
Oct 19 09:05:26 neo modem-manager: (ttyUSB0) closing serial device...


[root@neo ~]# yum -y install minicom
[root@neo ~]#  minicom -s
Select:
| Serial port setup        |

Then select A and change the value to /dev/ttyUSB0 (from /var/log/messages)
Then select E, then C (to change the speed to 9600)
Hit Enter twice
and
            | Save setup as dfl        |    









Labels:

Comments

  1. AnonymousApril 20, 2022 at 6:35 AM

    Using Keyspan Usa-19Hs With Rhel (Minicom) >>>>> Download Now

    >>>>> Download Full

    Using Keyspan Usa-19Hs With Rhel (Minicom) >>>>> Download LINK

    >>>>> Download Now

    Using Keyspan Usa-19Hs With Rhel (Minicom) >>>>> Download Full

    >>>>> Download LINK wM

    ReplyDelete

Post a Comment

Popular posts from this blog

RHN Satellite Server (spacewalk) repomd.xml not found

"repomd.xml not found" If you add a channel, or if your RHN cache gets corrupted, and one of your guests complains that it cannot find repomd.xml for jb-ews-2-x86_64-server-5-rpm (for example) - you need to rebuild your repodata cache. Normally this is an automated job - which is exemplified by the fact that you have obviously built out your entire Satellite environment and never had to do any of the steps you are about to do. So - some prep work: Open 3 terminals to your Satellite Server and run: # Term 1 cd /var/cache/rhn watch "ls -l | wc -l" # Term 2 pwd cd /var/log/rhn tail -f rhn_taskomatic_daemon.log # Term 3 satellite-sync --channel=jb-ews-2-x86_64-server-5-rpm Once the satellite-sync has completed, you >should< see the count increment by one.  If you are unlucky (like me) you will not. You then need to login to the Satellite WebUI as the satellite admin user. Click on the Admin tab (at the top) Task Schedules (on the left) fin
Post a Comment
Read more

Install RHEL 7 on old HP DL380 g5

Someone at work had been running RHEL on an HP DL380 G5 and blew it up.  After several attempts at doing an installation that made me conclude the hardware was actually bad... I kept digging for the answer. Attempt install and Anaconda could not find any disks - try a Drivers Disk (dd.img) both cciss and hpsa.   -- once we did that, when the system would reboot it would say it could not find a disk. hmmm. Boot from your installation media and interrupt the startup at grub. Add hpsa.hpsa_allow_any=1 hpsa.hpsa_simple_mode=1 to the line starting with linuxefi press CTRL-X to boot. Once the system restarts after the install, you need to once again interrupt the startup and add the line from above. After the system starts, edit /etc/default/grub and add those 2 parameters to the end of the line starting with GRUB_CMDLINE_LINUX (which likely has quiet at the end of the line currently). then run # cp /boot/grub2/grub.cfg /boot/grub2/grub.cfg.orig # grub2-mkconfig -o /boot/grub2
Post a Comment
Read more

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un
1 comment
Read more