<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I don't know anything about Linux and have no problems with the many cables I have with the fake Prolific chips in them. Not that hard to roll back the driver if need be. <br><br>Jardy Dawson WA7JRD<div>Message sent through sub space hailing frequencies <span style="font-size: 13pt;">using the Universal Translator. </span></div><div><span style="font-size: 13pt;"><br></span></div></div><div><br>On Nov 13, 2016, at 12:37, Nigel A. Gunn G8IFF/W8IFF <<a href="mailto:nigel@ngunn.net">nigel@ngunn.net</a>> wrote:<br><br></div><blockquote type="cite"><div><span>Try not using Windows. No driver problems with Linux.</span><br><span></span><br><span></span><br><blockquote type="cite"><span>On 13 November 2016 at 15:19 Jardy Dawson via chirp_users <<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>For Windows, try rolling your Prolific driver back to 3.2.0.0. Also, make sure cable is FIRMLY pushed in.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Jardy Dawson</span><br></blockquote><blockquote type="cite"><span>WA7JRD Ham Radio</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Message relayed from secret Hillary Clinton server, located in the basement of her house. OOPS, you aren't supposed</span><br></blockquote><blockquote type="cite"><span>to know that!</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>On Nov 13, 2016, at 08:49, Robert Carter <<a href="mailto:carterrj@verizon.net">carterrj@verizon.net</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I picked up my general license this year due to an incident I was </span><br></blockquote><blockquote type="cite"><span>involved in -- remote accident with no communications. Just sucked. </span><br></blockquote><blockquote type="cite"><span>Should have studied for the extra license too and gotten them all over </span><br></blockquote><blockquote type="cite"><span>on the same day.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Anyway, I picked up a new Yaesu FT2D yesterday. I'm trying to get over </span><br></blockquote><blockquote type="cite"><span>the programming hump. In the box with the FT2D was a USB programming cable.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Win7:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Yeasu in-the-box supplied Prolific cable and driver from Yeasu's web </span><br></blockquote><blockquote type="cite"><span>site won't run. v1.8 driver fails to install. I downloaded and the </span><br></blockquote><blockquote type="cite"><span>latest v1.16 driver from Prolific's web site, still no love.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Ubutnu 14.04 LTS:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Now it gets interesting. lsubb reports PID/VID for this cable:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> Bus 005 Device 016: ID 26aa:0001</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>The pl2303 kernel module doesn't recognize this PID/VID as a serial </span><br></blockquote><blockquote type="cite"><span>device. When the cable is inserted, the kernel doesn't load the serial </span><br></blockquote><blockquote type="cite"><span>USB module. "modinfo pl2303" doesn't list this Yeasu cable's PID/VID.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>When inserting the USB-serial cable, while the FT2D is in "clone" mode, </span><br></blockquote><blockquote type="cite"><span>syslog reports:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Nov 13 10:20:53 booger kernel: [ 4471.004031] usb 5-1: new full-speed </span><br></blockquote><blockquote type="cite"><span>USB device number 16 using uhci_hcd</span><br></blockquote><blockquote type="cite"><span>Nov 13 10:20:58 booger kernel: [ 4476.361065] usb 5-1: New USB device </span><br></blockquote><blockquote type="cite"><span>found, idVendor=26aa, idProduct=0001</span><br></blockquote><blockquote type="cite"><span>Nov 13 10:20:58 booger kernel: [ 4476.361073] usb 5-1: New USB device </span><br></blockquote><blockquote type="cite"><span>strings: Mfr=0, Product=0, SerialNumber=0</span><br></blockquote><blockquote type="cite"><span>Nov 13 10:20:58 booger mtp-probe: checking bus 5, device 16: </span><br></blockquote><blockquote type="cite"><span>"/sys/devices/pci0000:00/0000:00:1d.3/usb5/5-1"</span><br></blockquote><blockquote type="cite"><span>Nov 13 10:20:58 booger mtp-probe: bus: 5, device: 16 was not an MTP device</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I tried manually to force load the kernel modules and force the PID/VID </span><br></blockquote><blockquote type="cite"><span>into the drivers -- but still nada:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> sudo modprobe pl2303 vendor=0x26aa product=0x0001</span><br></blockquote><blockquote type="cite"><span> sudo modprobe usbserial vendor=0x26aa product=0x0001</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I looked over the CHIRP source code and with the kernel modules "forced" </span><br></blockquote><blockquote type="cite"><span>and the FT2D still in "clone' mode, then launched minicom on </span><br></blockquote><blockquote type="cite"><span>/dev/ttyUSB0. Set the baud rate to 38400 8N1 -- nada. Nothing to/from </span><br></blockquote><blockquote type="cite"><span>the FD2R.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I'm willing to guinea pig here and run some experiments. If anyone has </span><br></blockquote><blockquote type="cite"><span>any ideas, I'd like to hear them.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>This should be this hard (well, except for windows).</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I checked over the last year of the CHIRP mailing list and didn't find </span><br></blockquote><blockquote type="cite"><span>any posts relative to the FT1D or FT2D, so I guess I'm breaking new ground.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>/KC1FAC/</span><br></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>chirp_users mailing list</span><br></blockquote><blockquote type="cite"><span><a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a></span><br></blockquote><blockquote type="cite"><span><a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a></span><br></blockquote><blockquote type="cite"><span>This message was sent to Jardy at <a href="mailto:jardy72@yahoo.com">jardy72@yahoo.com</a></span><br></blockquote><blockquote type="cite"><span>To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@intrepid.danplanet.com</a></span><br></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>chirp_users mailing list</span><br></blockquote><blockquote type="cite"><span><a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a></span><br></blockquote><blockquote type="cite"><span><a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a></span><br></blockquote><blockquote type="cite"><span>This message was sent to Nigel Gunn, W8IFF at <a href="mailto:nigel@ngunn.net">nigel@ngunn.net</a></span><br></blockquote><blockquote type="cite"><span>To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@intrepid.danplanet.com</a></span><br></blockquote><span>_______________________________________________</span><br><span>chirp_users mailing list</span><br><span><a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a></span><br><span><a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a></span><br><span>This message was sent to Jardy at <a href="mailto:jardy72@yahoo.com">jardy72@yahoo.com</a></span><br><span>To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@intrepid.danplanet.com</a></span><br></div></blockquote></body></html>