While I've spent some time with Linux (mostly SuSE and some Red Hat), I've never tried serial/USB converters at all. However, based on zero experience with the application, I'll take a guess and say it may be the Linux drivers are more "cooperative". In fact, do you know if you loaded drivers that came with the cable or relied on native Linux drivers? My point being that perhaps the Prolific drivers are as much to blame as anything. The logical conclusion is to build a Linux machine to support CHIRP and Prolific cables - talk about reinventing the Zippo to light a campfire...
73 de KC3DOO Rick
On 8/29/2016 1:01 PM, Drew from Zhrodague wrote:
On 8/27/16 7:42 PM, Richard B. Emerson wrote:
Following the traffic here, I think the following should be (if it isn't) a FAQ item. Nonetheless it bears repeating here:
FTDI conversion chips and drivers are extremely stable. Anything else, including Prolific, is a gamble with poor odds. It's that simple.
This is true for Windows, and for OSX - for the most part. I've had wacky behavior and performance with the knock-off Prolific things on OSX.
However crappy the Prolific chips are, they seem to work just fine with all of the different Linux distributions I've tried. Simply plug them in, and they work. For this reason, I usually buy the Prolific $1.40 knock-off usb/serial dongles from EBay. _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to KC3DOO at pavilion@pinefields.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com