[chirp_users] BaoFeng UV-5RV2+ unable to download

[Eugene]

On 05/14/2016 09:15 PM, Jim Unroe wrote:
> On Sat, May 14, 2016 at 9:00 PM, Eugene <enine at ninefamily.com> wrote:
>> Everything there is windows specific.
>>
>> The 'radio does not respond' message comes after the radio reboots.
>>
>> It looks like the drivers loads fine:
>>
>> [  139.540792] usb 1-1: new full-speed USB device number 2 using xhci_hcd
>> [  139.553007] usb 1-1: New USB device found, idVendor=067b, idProduct=2303
>> [  139.553013] usb 1-1: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [  139.553017] usb 1-1: Product: USB-Serial Controller
>> [  139.553019] usb 1-1: Manufacturer: Prolific Technology Inc.
>> [  139.560429] usbcore: registered new interface driver usbserial
>> [  139.560444] usbcore: registered new interface driver usbserial_generic
>> [  139.560453] usbserial: USB Serial support registered for generic
>> [  139.561154] usbcore: registered new interface driver pl2303
>> [  139.561166] usbserial: USB Serial support registered for pl2303
>> [  139.561185] pl2303 1-1:1.0: pl2303 converter detected
>> [  139.561925] usb 1-1: pl2303 converter now attached to ttyUSB0
>>
>>
> With a Windows computer and a Prolific chip based programming cable,
> you must download, install and select the older Prolific v3.2.0.0
> device driver.
>
> Also if the programming cable was working and then stopped, then...
>
> - the device driver got upgraded to the latest (it would need to be
> downgraded again
> - the programming cable was plugged into a different USB port (this
> would install the latest device driver -- which is not what you want,
> and, assign a different com port number).
>
> Jim KC9HI
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Eugene at enine at ninefamily.com
> To unsubscribe, send an email to chirp_users-unsubscribe at intrepid.danplanet.com
>
>
I see now that I should have specified at first that I'm not running 
windows so the windows specific driver troubleshooting doesn't apply.

What is really odd is I just tried again and it worked, only thing I did 
different was remove the antenna thinking that maybe it was receiving 
something even though I was tuned to a frequency that shouldn't have 
anything on it.