Two other drivers show up in the Ports dropdown:
/dev/cu.Bluetooth-Incoming-Port /dev/cu.Bluetooth-Modem
along with
/dev/cu.PL2303-000012FD
On Thu, Jul 9, 2015 at 2:14 PM, Dave Nathanson KG6ZJO@nathanson.org wrote:
Pat, What are the exact names of any other ports/drivers that show up in CHIRP? I'd consider disabling them (not forever, just as a diagnostic) and seeing if that helps at all. I'm wondering if one of the other drivers is competing somehow. You might also have some leftover old drivers that are doing something.
Best, Dave Nathanson KG6ZJO
On Jul 9, 2015, at 7:00 AM, Pat Anderson anderson5420@gmail.com wrote:
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
Thanks!
Pat Anderson KD7OAC _______________________________________________
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com