<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)">Thanks Aubrey.  lsusb is at least familiar to me.  The before and after are:</div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">n4lbl@eel:~$ lsusb</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Bus 001 Device 004: ID 13d3:5702 IMC Networks UVC VGA Webcam</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Bus 002 Device 002: ID 045e:0737 Microsoft Corp. Compact Optical Mouse 500</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default"><br></div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">n4lbl@eel:~$ lsusb</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Bus 001 Device 004: ID 13d3:5702 IMC Networks UVC VGA Webcam</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default"><span style="background-color:rgb(255,255,0)">Bus 002 Device 005: ID 0584:b03a RATOC System, Inc. </span></div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Bus 002 Device 002: ID 045e:0737 Microsoft Corp. Compact Optical Mouse 500</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub</div></div></blockquote><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)">At this moment the radio isn&#39;t connected to the cable as it is being recharged. </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">n4lbl@eel:~$ tail -f /var/log/syslog</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:45:17 eel mtp-probe: bus: 2, device: 6 was not an MTP device</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:46:21 eel kernel: [155678.200326] usb 2-2: USB disconnect, device number 6</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:47:35 eel kernel: [155752.168182] usb 2-2: new full-speed USB device number 7 using uhci_hcd</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:47:35 eel kernel: [155752.370019] usb 2-2: New USB device found, idVendor=0584, idProduct=b03a</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:47:35 eel kernel: [155752.370035] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:47:35 eel kernel: [155752.370046] usb 2-2: Product: USB-Serial Converter</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:47:35 eel kernel: [155752.370056] usb 2-2: Manufacturer: RATOC Systems,Inc.</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:47:35 eel mtp-probe: checking bus 2, device 7: &quot;/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-2&quot;</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:47:35 eel mtp-probe: bus: 2, device: 7 was not an MTP device</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:49:39 eel kernel: [155876.104263] usb 2-2: USB disconnect, device number 7</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">     <span style="background-color:rgb(255,255,0)">comment: inserted cable here</span></div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:51:18 eel kernel: [155975.080158] usb 2-2: new full-speed USB device number 8 using uhci_hcd</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:51:18 eel kernel: [155975.280118] usb 2-2: New USB device found, idVendor=0584, idProduct=b03a</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:51:18 eel kernel: [155975.280129] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:51:18 eel kernel: [155975.280138] usb 2-2: Product: USB-Serial Converter</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:51:18 eel kernel: [155975.280146] usb 2-2: Manufacturer: RATOC Systems,Inc.</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:51:18 eel mtp-probe: checking bus 2, device 8: &quot;/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-2&quot;</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><div class="gmail_default">Feb 12 10:51:18 eel mtp-probe: bus: 2, device: 8 was not an MTP device</div><div class="gmail_default"><br></div></div></blockquote><font color="#000066" face="arial, helvetica, sans-serif"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102);display:inline">​I wish I knew what to do next!</div></font><div><font color="#000066" face="arial, helvetica, sans-serif"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102);display:inline"><br></div></font></div><div><font color="#000066" face="arial, helvetica, sans-serif"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102);display:inline">thanx,,,</div></font></div><div><font color="#000066" face="arial, helvetica, sans-serif"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102);display:inline">   Alan,,,   n4lbl​</div><br></font></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 12, 2015 at 9:40 AM, Aubrey Turner <span dir="ltr">&lt;<a href="mailto:aubrey.c.turner@gmail.com" target="_blank">aubrey.c.turner@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    Alan,<br>
    <br>
    Something that might be easier to work with than dmesg is lsusb.<br>
    <br>
    If you run the &#39;lsusb&#39; command you will see what devices Linux
    thinks are attached to the USB.  What I do if I&#39;m in doubt is to run
    lsusb before plugging in the cable, then run it again after plugging
    in the cable to see what, if anything, shows up that is different.<br>
    <br>
    On my system, running lsusb before plugging in the cable shows the
    following:<br>
    <blockquote><tt>Bus 002 Device 002: ID 8087:8000 Intel Corp. </tt><tt><br>
      </tt><tt>Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0
        root hub</tt><tt><br>
      </tt><tt>Bus 001 Device 003: ID 13d3:3404 IMC Networks </tt><tt><br>
      </tt><tt>Bus 001 Device 002: ID 8087:8008 Intel Corp. </tt><tt><br>
      </tt><tt>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0
        root hub</tt><tt><br>
      </tt><tt>Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0
        root hub</tt><tt><br>
      </tt><tt>Bus 003 Device 003: ID 051d:0002 American Power
        Conversion Uninterruptible Power Supply</tt><tt><br>
      </tt><tt>Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying
        Receiver</tt><tt><br>
      </tt><tt>Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0
        root hub</tt><tt><br>
      </tt></blockquote>
    <br>
    Running it *after* plugging in the cable shows this:<br>
    <blockquote><tt>Bus 002 Device 002: ID 8087:8000 Intel Corp. </tt><tt><br>
      </tt><tt>Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0
        root hub</tt><tt><br>
      </tt><tt>Bus 001 Device 003: ID 13d3:3404 IMC Networks </tt><tt><br>
      </tt><tt>Bus 001 Device 002: ID 8087:8008 Intel Corp. </tt><tt><br>
      </tt><tt>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0
        root hub</tt><tt><br>
      </tt><tt>Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0
        root hub</tt><tt><br>
      </tt><b><tt>Bus 003 Device 006: ID 067b:2303 Prolific Technology,
          Inc. PL2303 Serial Port</tt></b><tt><br>
      </tt><tt>Bus 003 Device 003: ID 051d:0002 American Power
        Conversion Uninterruptible Power Supply</tt><tt><br>
      </tt><tt>Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying
        Receiver</tt><tt><br>
      </tt><tt>Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0
        root hub</tt><tt><br>
      </tt></blockquote>
    Note the difference.<br>
    <br>
    Another approach is to use the &#39;tail&#39; command to watch the system
    logs as you plug in the cable.<br>
    <br>
    For example, if you run &quot;tail -f /var/log/syslog&quot; (this is in Ubuntu
    14.04) and then plug in the cable, you should see something like the
    following:<br>
    <br>
    <blockquote><tt>Feb 12 10:24:35 runabout kernel: [696555.274063]
        usbcore: registered new interface driver usbserial</tt><tt><br>
      </tt><tt>Feb 12 10:24:35 runabout kernel: [696555.274073] usbcore:
        registered new interface driver usbserial_generic</tt><tt><br>
      </tt><tt>Feb 12 10:24:35 runabout kernel: [696555.274080]
        usbserial: USB Serial support registered for generic</tt><tt><br>
      </tt><tt>Feb 12 10:24:35 runabout kernel: [696555.275486] usbcore:
        registered new interface driver pl2303</tt><tt><br>
      </tt><tt>Feb 12 10:24:35 runabout kernel: [696555.275495]
        usbserial: USB Serial support registered for pl2303</tt><tt><br>
      </tt><tt>Feb 12 10:24:35 runabout kernel: [696555.275511] pl2303
        3-9:1.0: pl2303 converter detected</tt><tt><br>
      </tt><tt>Feb 12 10:24:35 runabout kernel: [696555.276716] usb 3-9:
        pl2303 converter now attached to ttyUSB0</tt><tt><br>
      </tt></blockquote>
    The above is pretty much what dmesg will give you, although you are
    seeing it in &quot;real time&quot; as it were.<br>
    <br>
    (Note that &quot;-f&quot; means that tail will continuously follow the file,
    so you have to press Ctrl-C to stop)<br>
    <br>
    Of course, you mileage may vary, as it will depend on what chipset
    the Yaesu cable is using.  I suspect they aren&#39;t using the PL2303
    that I&#39;m using (the above is for a typical Chinese UV-5R programming
    cable as I don&#39;t have a FT-1D or either of its programming cables).<br>
    <br>
    Good luck,<br>
    Aubrey - K5ACT<div><div class="h5"><br>
    <br>
    <br>
    <br>
    <div>On 02/12/2015 10:02 AM, n4lbl wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)">Paul:</div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><br>
        </div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)">You
          might be correct here, but I suspect the reasons may be
          different from most radios.  FT-1Ds come with either a Yaesu
          SCU-18 or SCU-19 cable depending on their vintage.  Yaesu
          provides Windows drivers.  I just went back and looked and
          there are no Mac instructions.  The drivers for the &#39;18 and
          the &#39;19 are packaged separately and I suppose that they may be
          different.  I suspect that I just didn&#39;t get lucky and find
          that the standard out-of-the-box Linux driver worked.</div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><br>
        </div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)">I&#39;d
          like to know if the author of the Chirp code for the FT-1D
          tested with Linux.  On 04 Feb. I sent a note to this list
          asking if the SCU-18s or SCU-19s presented any issues under
          Linux.  I wonder if I&#39;m the first to try it.</div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><br>
        </div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)">I&#39;m
          game to try to wrestle this to the ground if I have a modest
          expectation of success.  Knowing that I&#39;m not the first would
          be sufficient.  If all I wanted to do was back the radio up I
          could try 1) Chirp with Windows, 2) Yaesu&#39;s ADM-6 software
          with Windows, and 3) I suspect that if I re-read the manual
          I&#39;d find a backup command to the microSD card in the radio.</div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><br>
        </div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)">Backtracking
          to previous issues, I just discovered that the default
          scrollback limit with Ubuntu is 512 lines.  Gak!!</div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><br>
        </div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)">thanks,,,</div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"> 
             Alan,,,   n4lbl</div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Thu, Feb 12, 2015 at 7:40 AM, W Paul
          Mills <span dir="ltr">&lt;<a href="mailto:AC0HY@wpmills.com" target="_blank">AC0HY@wpmills.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Problem
            is, this is an operating system / cable hardware issue.
            There<br>
            would need to be different instructions for each operating
            system and<br>
            possible cable type. All for something that is not a part of
            chirp. If<br>
            anyone should be providing this information, it should be
            the<br>
            manufacturer of the cable you are using.<br>
            <br>
            By default, linux users tend to be somewhat on their own on
            these<br>
            things, regardless of manufacturer. Things linux users need
            to<br>
            understand to some degree are the /dev/ directory, lsusb
            command, and<br>
            groups and sometimes file permissions.<br>
            <br>
            And windows users don&#39;t get a free ride either, because of
            the things<br>
            that often get done behind your back. One needs to be
            familiar with<br>
            device manager, and need to know about rolling back drivers
            in some<br>
            cases. And this can become a major pain. This can even be a
            problem when<br>
            using factory supplied software.<br>
            <br>
            Add to this numerous problems caused by some manufacturers
            using<br>
            counterfeit chips, and chip makers attempting to protect
            themselves from<br>
            this.<br>
            <span><br>
              On 02/12/2015 05:44 AM, Brian Carling wrote:<br>
              &gt; I wish they would put all the stuff on the chirp
              website so we can<br>
              &gt; actually use it!<br>
              &gt;<br>
              &gt; Best regards - Brian Carling<br>
              &gt; AF4K Crystals Co.<br>
              &gt; 117 Sterling Pine St.<br>
              &gt; Sanford, FL 32773<br>
              &gt;<br>
              &gt; Tel: +USA <a href="tel:321-262-5471" value="+13212625471" target="_blank">321-262-5471</a><br>
              &gt;<br>
              &gt;<br>
              &gt;<br>
              &gt;<br>
              &gt; On Feb 11, 2015, at 10:37 PM, Amber Fechko &lt;<a href="mailto:amber@dendriticspine.com" target="_blank">amber@dendriticspine.com</a><br>
            </span>
            <div>
              <div>&gt; &lt;mailto:<a href="mailto:amber@dendriticspine.com" target="_blank">amber@dendriticspine.com</a>&gt;&gt;
                wrote:<br>
                &gt;<br>
                &gt;&gt; Make sure you&#39;re not running through an
                external USB hub or anything;<br>
                &gt;&gt; connect directly to the computer.<br>
                &gt;&gt;<br>
                &gt;&gt; Try disconnecting the cable, and then running:<br>
                &gt;&gt;<br>
                &gt;&gt; user@host:~$ dmesg<br>
                &gt;&gt; (a ton of system messages should stream by)<br>
                &gt;&gt;<br>
                &gt;&gt; Then reconnect your cable, turn on radio/volume
                up (shouldn&#39;t be<br>
                &gt;&gt; necessary for dmesg output, but might as well
                do it now), and run the<br>
                &gt;&gt; same command:<br>
                &gt;&gt;<br>
                &gt;&gt; user@host:~$ dmesg<br>
                &gt;&gt; (all of the previous system messages, and
                hopefully something new<br>
                &gt;&gt; indicating a usb-&gt;serial device like below)<br>
                &gt;&gt; [430941.789785] usb 2-1.7: new full-speed USB
                device number 49 using<br>
                &gt;&gt; ehci-pci<br>
                &gt;&gt; [430941.883258] usb 2-1.7: New USB device
                found, idVendor=067b,<br>
                &gt;&gt; idProduct=2303<br>
                &gt;&gt; [430941.883267] usb 2-1.7: New USB device
                strings: Mfr=1, Product=2,<br>
                &gt;&gt; SerialNumber=0<br>
                &gt;&gt; [430941.883272] usb 2-1.7: Product: USB-Serial
                Controller<br>
                &gt;&gt; [430941.883277] usb 2-1.7: Manufacturer:
                Prolific Technology Inc.<br>
                &gt;&gt; [430941.883801] pl2303 2-1.7:1.0: pl2303
                converter detected<br>
                &gt;&gt; [430941.885384] usb 2-1.7: pl2303 converter now
                attached to ttyUSB0<br>
                &gt;&gt;<br>
                &gt;&gt; Assuming your system registers the
                usb-&gt;serial cable, you should see<br>
                &gt;&gt; it in dmesg w/the device it was assigned
                (/dev/ttyUSB0 in my case --<br>
                &gt;&gt; vdir /dev/ttyUSB* is faster if you just need
                the device ID, but if<br>
                &gt;&gt; vdir isn&#39;t showing anything, dmesg might give
                you a hint as to why).<br>
                &gt;&gt;<br>
                &gt;&gt; I had to enter /dev/ttyUSB0 manually in the
                &quot;Port&quot; section of CHIRP --<br>
                &gt;&gt; it didn&#39;t show by default unless I restarted
                CHIRP after the cable was<br>
                &gt;&gt; connected.<br>
                &gt;&gt;<br>
                &gt;&gt; -Amber<br>
                &gt;&gt;<br>
                &gt;&gt; On Wed, Feb 11, 2015 at 7:11 PM, n4lbl &lt;<a href="mailto:alan.schulman@gmail.com" target="_blank">alan.schulman@gmail.com</a><br>
              </div>
            </div>
            <span>&gt;&gt; &lt;mailto:<a href="mailto:alan.schulman@gmail.com" target="_blank">alan.schulman@gmail.com</a>&gt;&gt;
              wrote:<br>
              &gt;&gt;<br>
              &gt;&gt;     Thanks.  I suspect that this is interesting:<br>
              &gt;&gt;<br>
              &gt;&gt;         n4lbl@eel:~$ vdir /dev/ttyUSB<br>
              &gt;&gt;         vdir: cannot access /dev/ttyUSB: No such
              file or directory<br>
              &gt;&gt;<br>
              &gt;&gt;<br>
              &gt;&gt;<br>
              &gt;&gt;     On Wed, Feb 11, 2015 at 4:10 PM, W Paul Mills
              &lt;<a href="mailto:AC0HY@wpmills.com" target="_blank">AC0HY@wpmills.com</a><br>
            </span>
            <div>
              <div>&gt;&gt;     &lt;mailto:<a href="mailto:AC0HY@wpmills.com" target="_blank">AC0HY@wpmills.com</a>&gt;&gt;
                wrote:<br>
                &gt;&gt;<br>
                &gt;&gt;         Should be showing as /dev/ttyUSB0 or
                something similar. From a<br>
                &gt;&gt;         text box<br>
                &gt;&gt;         or terminal screen type &quot;vdir
                /dev/ttyUSB*&quot; and see what the<br>
                &gt;&gt;         results<br>
                &gt;&gt;         show. If nothing shows, your cable is
                not being recognised. If<br>
                &gt;&gt;         it shows,<br>
                &gt;&gt;         but not in chirp text box, type it in,
                and it should work.<br>
                &gt;&gt;<br>
                &gt;&gt;         On 02/11/2015 02:49 PM, n4lbl wrote:<br>
                &gt;&gt;         &gt; When trying to download I get the
                message:<br>
                &gt;&gt;         &gt;<br>
                &gt;&gt;         &gt;     An error has occurred<br>
                &gt;&gt;         &gt;     Could not configure port: (5,
                &#39;Input/output error&#39;)<br>
                &gt;&gt;         &gt;<br>
                &gt;&gt;         &gt; ​The environment is Ubuntu 14.04,
                Chirp daily -20150210,<br>
                &gt;&gt;         cable SCU-18<br>
                &gt;&gt;         &gt; with power light on, HT in CLONE
                mode.<br>
                &gt;&gt;         &gt;<br>
                &gt;&gt;         &gt; ​The Radio box presents port
                choices /dev/ttyS0 thru<br>
                &gt;&gt;         /dev/ttyS31 and I<br>
                &gt;&gt;         &gt; have tried many of these but not
                all, and always received<br>
                &gt;&gt;         the same exact<br>
                &gt;&gt;         &gt; message.  There were no USB
                possibilities presented.​<br>
                &gt;&gt;         &gt;<br>
                &gt;&gt;         &gt; The message said nothing of
                permissions.  I did check anyway<br>
                &gt;&gt;         and saw:<br>
                &gt;&gt;         &gt;<br>
                &gt;&gt;         &gt;     n4lbl@eel:~$ groups n4lbl<br>
                &gt;&gt;         &gt;     n4lbl : n4lbl adm dialout fax
                cdrom floppy tape audio<br>
                &gt;&gt;         dip video<br>
                &gt;&gt;         &gt;     plugdev fuse scanner lpadmin
                netdev sambashare<br>
                &gt;&gt;         &gt;<br>
                &gt;&gt;         &gt; ​so that seems OK.​<br>
                &gt;&gt;         &gt;<br>
                &gt;&gt;         &gt; The HT&#39;s internal code is
                ancient:  from when I bought it in<br>
                &gt;&gt;         Nov. or<br>
                &gt;&gt;         &gt; Dec. &#39;13.  My intention was to
                back it up before upgrading<br>
                &gt;&gt;         the code.<br>
                &gt;&gt;         &gt;<br>
                &gt;&gt;         &gt; This is sure to be a knuckleheaded
                mistake or something I<br>
                &gt;&gt;         didn&#39;t read or<br>
                &gt;&gt;         &gt; forgot.<br>
                &gt;&gt;         &gt; ​  Thanks,,,<br>
                &gt;&gt;         &gt;<br>
                &gt;&gt;         &gt; Alan,,,   n4lbl​<br>
                &gt;&gt;         &gt;<br>
                &gt;&gt;         &gt;<br>
                &gt;&gt;         &gt;
                _______________________________________________<br>
                &gt;&gt;         &gt; chirp_users mailing list<br>
                &gt;&gt;         &gt; <a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
              </div>
            </div>
            &gt;&gt;         &lt;mailto:<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a>&gt;<br>
            <div>
              <div>&gt;&gt;         &gt; <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
                &gt;&gt;         &gt; Unsubscribe:<br>
                &gt;&gt;         <a href="http://intrepid.danplanet.com/mailman/options/chirp_users--" target="_blank">http://intrepid.danplanet.com/mailman/options/chirp_users--</a><br>
                /*************************************************<br>
                * Amateur Radio Station AC0HY                    *<br>
                * W. Paul Mills         SN807                    *<br>
                * Assistant EC Alpha-1 ARES Shawnee/Wabunsee, KS *<br>
                * President Kaw Valley Amateur Radio Club        *<br>
                *************************************************/<br>
                _______________________________________________<br>
                chirp_users mailing list<br>
                <a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
                <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
                Unsubscribe: <a href="http://intrepid.danplanet.com/mailman/options/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/options/chirp_users</a></div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
chirp_users mailing list
<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a>
Unsubscribe: <a href="http://intrepid.danplanet.com/mailman/options/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/options/chirp_users</a></pre>
    </blockquote>
    <br>
  </div></div></div>

<br>_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
Unsubscribe: <a href="http://intrepid.danplanet.com/mailman/options/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/options/chirp_users</a><br></blockquote></div><br></div>