[chirp_users] Once Again, Yosemite Has Broken CHIRP
dlichterman at gmail.com
Thu Jul 9 10:29:00 PDT 2015
Pat - there was a post on this group last month regarding this and the
Here is what I found. The driver is the issue with Yosemite. The built-in
FTDI driver prevents the osx-pl2303 driver from loading. The fix (not for
the faint of heart) is to do some black magic at the command line.
In Terminal, enter:
sudo nvram boot-args="kext-dev-mode=1"
This allows other drivers to load. The driver that works for me is the
Lion driver from miklor.com.
Then manually load the driver (first time only, it will load automatically
after that) with this command in Terminal:
sudo kextload /System/Library/Extensions/osx-pl2303.kext
This creates the device cu.PL2303-000012FD, be sure that is what you select
in the CHIRP Radio dialog in the Port drop-down. Again in the Terminal, do
"cd /dev", and then "ls" (without the quotes) to see that the
cu.PL2303-000012FD driver is actually loaded.
I got this technique from this website
See if that works?
On Thu, Jul 9, 2015 at 10:24 AM, Pat Anderson <anderson5420 at gmail.com>
> Thanks for the reply, but no cigar. The variable determing what works or
> doesn't work is computers and operating systems, not radios - the cable
> works great on two different Macs running Snow Leopard, but simply doesn't
> work on a Mac running Yosemite. Because it works of two different
> computers, I know I have it plugged in correctly. When I plug the cable
> into the USB slot, I can see the device in my /dev directory, and it shows
> up in the System Information app. The Mac running Yosemite is configured
> to load unsigned drivers and I manually load the oxs-PL2303.kext from the
> Terminal (I know this is Greek to Windows people). In CHIRP, the driver
> shows up in the "port" drop-down and I select it. It simply doesn't work
> in Yosemite. The odd thing is that is HAS worked off and on unreliably
> from time to time. Just baffled.
> On Thu, Jul 9, 2015 at 8:43 AM, John LaMartina <JohnLa at usa.net> wrote:
>> If the cable works on one radio than it should be fine on all.
>> Let me refer you to http://www.miklor.com/COM/UV_ErrorMess.php
>> If it’s a generic cable, reinstall the driver that works with your other
>> My best guess it will be Prolific 220.127.116.11
>> It sounds like the way the cable is plugged in, or you changed COM ports
>> and a new driver loaded.
>> I hope this helps.
>> John ‘Miklor’
>> *From:* chirp_users-bounces at intrepid.danplanet.com [mailto:
>> chirp_users-bounces at intrepid.danplanet.com] *On Behalf Of *Pat Anderson
>> *Sent:* Thursday, July 09, 2015 10:00 AM
>> *To:* Discussion of CHIRP
>> *Subject:* [chirp_users] Once Again, Yosemite Has Broken CHIRP
>> When I first put Yosemite on my late 2011 Macbook Pro, CHIRP continued
>> to run fine to program my Baofeng UV-5R. Then for no apparent reason,
>> since I didn't change anything, all I could get was "The radio did not
>> respond." I am using the latest daily build of CHIRP. So then I went to
>> the net to research Yosemite and drivers and found the Terminal command to
>> allow unsigned drivers to load and the command to load the kext for the
>> driver that had been working. This appeared to work for a while, I was
>> able to download from radio and upload to radio, and I thought all was
>> hunky dory. Then in a day or so, once again it stopped working. Nothing I
>> try works, I have tried all the various drivers on miklor.com, although
>> they don't even mention Yosemite, they stop at Mavericks.
>> I have a programming cable from cheapham.com, which I assume is a
>> generic chipset, since it cost all of $8. This cable works reliably on my
>> 2006 white Macbook and my 2006 iMac, both running Snow Leopard, so I can
>> program my Baofeng with CHIRO, but I sure would like to be able to use my
>> Macbook Pro. Is a new more expensive "genuine" FTDI programming cable going
>> to fix the problem on Yosemite? Which one from which vendor?
>> Pat Anderson
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
>> To unsubscribe, send an email to
>> chirp_users-unsubscribe at intrepid.danplanet.com
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe at intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the chirp_users