CH341SER_MAC No longer works in macOS Sierra

Hello, I have upgraded to macOS Sierra, the notorious CH341SER_MAC_2 driver stopped working. Once I plug the USB into my Arduino board, it causes a kernel panic on my Mac, how do I remove the driver? Thanks.

how do I remove the driver?

This command in terminal will remove the old driver: sudo rm -rf /System/Library/Extensions/usb.kext

After that you might install the latest CH340 driver which is promoted as being "Sierra compatible": https://github.com/adrianmihalko/ch340g-ch34g-ch34x-mac-os-x-driver

Hi, I tried the above to remove the driver, however if I plug in a board with a CH340/1 chip it still causes the kernel crash. How do i remove this to stop this from happening? FYI at this time I am not interested in getting new drivers to run the boards at this time. regards, Cup

I have some links for you; hopefully one will work with your version of OS X:

https://www.mac-usb-serial.com/wordpress/support/troubleshooting/ https://www.mac-usb-serial.com/wordpress/support/de-installation/

and for SIERRA only: https://www.simplicate.info/2016/09/16/ch340-drama-osx-10-12-sierra-16a313a/ http://www.mblock.cc/posts/run-makeblock-ch340-ch341-on-mac-os-sierra and latest driver: http://www.wch.cn/download/CH341SER_MAC_ZIP.html

Awesome, Thank you, a lot of the time us noobs don't know what to search for. I have removed the drivers and no longer get the kernal crash when plugging in a CH341 chip. I will have another look at them when I know a bit more about my Mac and how these things work. I maybe jumped in a little quickly. Also, this is he link I used to get the drivers that caused me issues http://www.wch.cn/download/CH341SER_MAC_ZIP.html I think it's the same one as you posted above, not too sure if that driver works with Sierra.

Thank you.

Cup

There’s a link to a driver that’s supposed to be compatible with Sierra at that mblock.cc link. The wch.cn driver is apparently not compatible with Sierra, though likely WCH, the manufacturer of the CH340, will fix that issue eventually.
It’s kind of ironic that Mac is supposed to be “It just works” but there have been so many reports of Arduino issues with El Capitan and Sierra.

UPDATE 2018-03-24:
The manufacturer of the CH340 fixed this incompatibility a long time ago. I don’t recommend anyone to use the 3rd party drivers anymore. Use the official drivers downloaded from the manufacturer’s website:

It's kind of ironic that Mac is supposed to be "It just works" but there have been so many reports of Arduino issues with El Capitan and Sierra.

Macs only just work when the producer of an external driver strictly obeys the rules of Macs. It is obvious that this is not the case with this driver (yet) - to install the previous version, which I use with Yosemite, I had to cheat the OS X with some root commands to pretend that it was a signed driver.

So - under normal conditions Macs are really plug and play - not like Windows (plug and pray) :)

Hi i,m very new to this type of thing and im trying to uninstall the CH341ser driver using the terminal (not used it before)

in the terminal i see this:

Last login: Fri Feb 3 09:20:12 on ttys000
Davids-MBP:~ Dave$

if i type in cd/ Librarys/Extensions at the end of Dave$ then hit enter it just reverts back to
Davids-MBP:~ Dave$

and doesnt show the driver as suggested

i’m obviously missing something here, any help would be appreciated

Dave

Try again starting from the begining. I did, it works.

Thanks to rpt007 :)

now it works for me by follow all of the steps here https://github.com/adrianmihalko/ch340g-ch34g-ch34x-mac-os-x-driver

Thanks folks

Has anyone experienced that after installing the driver, and rebooting, the computer is stuck at the loading screen after logging in? The loading bar on my computer freezes as 90 %. I left it overnight, and it's still stuck.

Tried everything; rebooting into recovery mode and setting csrutil disabled, enabled, enabled without kext etc. Nothing works, and I cannot even use the computer of try logging in. Halp!

The manufacturer of the CH340 fixed this incompatibility a long time ago. I don't recommend anyone to use the 3rd party drivers anymore. Use the official drivers downloaded from the manufacturer's website: http://www.wch.cn/download/CH341SER_MAC_ZIP.html

ronnyandre: Has anyone experienced that after installing the driver, and rebooting, the computer is stuck at the loading screen after logging in? The loading bar on my computer freezes as 90 %. I left it overnight, and it's still stuck.

Tried everything; rebooting into recovery mode and setting csrutil disabled, enabled, enabled without kext etc. Nothing works, and I cannot even use the computer of try logging in. Halp!

Do you have the device with the CH340 still connected to your computer?

Was this ever fixed?

I have the same problem. I had not removed the old drivers from my computer (just forgot), and plugged in the board yesterday for the first time in forever, and my computer crashed. I have not been able to get past the login progress bar for any user on the computer.

I removed usbserial.kext, renamed my Library/Extensions to something else, reset the RAM, tried logging in with shift, all the things they tell you to do - still no luck.

(To answer your question: naturally, I didn't leave the board plugged into my computer after the first crash.)

Please help. Thank you.

larissa_n: I have not been able to get past the login progress bar for any user on the computer.

Had the same problem. Here's how we solved it: 1. Command + R to enter recovery. 2. Start up the terminal from there. 3. Search for all usbserial.kext files on the system. (we found them in 2 directories) 4. Delete all the usbserial.kext files. 5. Restart.

Hello,
I wanted to update this thread with a solution for Mac OSX High Sierra users, specifically 10.13.4.
If you have problems with the driver using the latest OSX High Sierra please refer to this Apple KB Article:

Basically, the kernel extension needs to be approved to load and is done so in system preferences/security.

My symptoms were not a kernel panic, but I found this thread in my search and the above KB article fixed my issue.