Note from November of 2015: This stopped working for me. I have not tried to make this work in El Capitan. I am now using the app. It’s not cheap at $29.99 (£22.99), but it works. I’ve not had any problems with any USB serial adapter (including USB consoles of Cisco devices) since I started using it. Highly recommended! Note from December 2015: You might try the driver from.
Go there, select Resources, then Software & Driver. It has been reported that this driver works on El Capitan.
If you are an OS X user, you know that a new OS has come out. New OS upgrades are always shiny, but also come with some level of risk. I have an old MacBook that had been running the Yosemite beta, so I wasn’t too worried about upgrading my primary laptop when the Yosemite final was released. All was fine and dandy until I was onsite and couldn’t console into a router because my wasn’t working I’ve been using this particular model of adapter for a long time. They have had the occasional driver issue, but they’ve been good and reliable overall, so I was surprised when I tried to open the device it wasn’t present. This was odd, but I immediately realized it probably had to do with the OS upgrade.
No problem, I’ll just reinstall the driver, problem solved! The device still wasn’t loading. At this point, I’m becoming concerned.
I ran Console and saw this error when I plugged in my USB adapter: 10/30/14 14:32:09.553 com.apple.kextd19: ERROR: invalid signature for com.prolific.driver.PL2303, will not load Well, that’s not good. After a bit of searching, I discover that it’s Windows Vista all over again. Well, it’s not actually that bad, but it did remind me of a behavior change in Vista that required all drivers to be signed with a trusted signature. Apparently, Mavericks has been helpfully logging warnings about this, but since nothing had stopped working, I guess no one did anything to fix it.
Now with Yosemite, all kernel extensions must be signed or they won’t load. No problem, I’ll just install the updated driver! The device driver is the same as the one I already have. Fortunately, I’d already found the workaround.
With Windows Vista, you could hit F8 at boot and boot in a dev mode that allowed any driver to load. You had to do that every time you booted. Fortunately, with Mac you only need to run this command once and reboot, after which it’s set: sudo nvram boot-args='kext-dev-mode=1' After rebooting, I found that I had to manually load the kext the first time, but it seems to have been auto-loading ever since. To manually load the kext: sudo kextload /System/Library/Extensions/ProlificUsbSerial.kext If you check your logs, you’ll see its back to a warning when the kext is loaded: 11/12/14 19:12:41.747 com.apple.kextd19: kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext '/System/Library/Extensions/ProlificUsbSerial.kext' More importantly, you’ll have your device working and can finally fix that router you’re supposed to be fixing FIN. I have the same problem and followed the instructions above.
When I manually load the driver “sudo kextload /System/Library/Extensions/ProlificUsbSerial.kext” I get the following in Console: 12/15/14 4:18:23.754 PM com.apple.kextd19: kext file:///System/Library/Extensions/ProlificUsbSerial.kext/ is in hash exception list, allowing to load However, I still do not get the USB adapter to show up in /dev after it is plugged in to the USB port. (Running OS X 10.10.1/ latest Prolific driver) Ayn suggestions? You probably need to modify the /System/Library/Extensions/ProlificUsbSerial.kext/Contents/Info.plist file. Compare the ‘idProduct’ and ‘idVendor’ keys with the values in the System Report (About This MAC - System Report - USB). Note you’ll need to plug in your cable in order to see these values. Modify the 2303 key and reboot.
Pl2303 Serial Port Usb-serial Controller Drivers For Mac
You should then see /dev/tty.usbserial and /dev/cu.usbserial. 067B2303 CFBundleIdentifier com.prolific.driver.PL2303 IOClass comprolificdriverPL2303 IOProviderClass IOUSBInterface bConfigurationValue 1 bInterfaceNumber 0 idProduct 8200 idVendor 1367. Both of my USB to Serial adapters (Belkin and (yes) Radio Shack adapters) stopped working after upgrading to Yosemite. I’ve been using I had to follow this to allow the unsigned kernel extensions to load: Basically this is the important command: sudo nvram boot-args=”kext-dev-mode=1” After the above, the devices were recognized, but connecting to devices with screen (routers, firewalls, switches) resulted in a blank screen with no data passing in either direction.
Pl2303 Serial Port Usb-serial Controller Drivers For Mac Download
I then found you could buy an updated driver (new kext package) to get it to work (here: ). However, I opted to download the source for the project from and then compiled it myself using Xcode. There were problems still so I made some changes to the code, but it appears to be working great now. Please let me know if you need any assistance with the above. I actually have a built version which is linked below.
Let me know if you have any questions or problems with it. I havent been able to get usb-serial connection working. I installed PL2303MacOSXv1.5.1 drivers, installation went fine but if I try to establish a connection I just get a blinking cursor and nothing happends.
Here’s what I see: er$ kextstat grep 2303 151 0 0xffffff7f838c9000 0xb000 0xb000 nl.bjaelectronics.driver.PL2303 (1.0.0d1) 152 0 0xffffff7f838d4000 0x7000 0x7000 com.prolific.driver.PL2303 (1.5.1) er$ ls /dev grep usb cu.usbserial tty.usbserial r$ ls /dev grep 2303 cu.PL234 tty.PL234 I’ve tried to manually load the kext, no change. I’ve also tried unload the kext for both of the above and nothing. Any suggestion?
All welcome!:). Thanks; in my case, it may actually be something more with Parallels. What I’m using the usb-serial cable for, is my UPS that only has a serial connection and Windows software, so I’d been using it in a virtual machine for a long time just fine.
I’d load up my Windows VM and run the UPSMON software so I could check on the UPS’s health, etc., from time to time. Now, when I reinstall Prolific, all’s good until I run Parallels. It no longer works within the VM, and it never releases the USB Controller D device back to the OS. So it may be something I’ll need to ask Parallels about. Never could get Serial to work, though, but perhaps I don’t need it for my purposes?