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

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...
1 comment
Read more

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...
1 comment
Read more

Extending SNMP to run arbitrary shell script

Why are we here... This is not likely something I would have pursued under normal circumstances.  I happen to be working for a customer/client who is not afforded a lot of flexibility to accomplish their goals.  In this case, the rigor is justified.  They have to sometimes be fairly creative with how they solve problems. In this case they would like to utilize an existing snmp implementation to execute a command (or shell script) on a remote system.  They came to me with the idea of using Net-SNMP extend. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html NOTE:  This is NOT a good implementation strategy in the "real world"  it will simply allow you to test the functionality.  There are a TON of security implications which would need to be taken in to consideration. Implementation Steps: [root@rh7tst01 ~]# yum -y install net-snmp net-snmp-utils ...
Post a Comment
Read more