-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The driver can not be loaded in OS X El Capitan: "System extention cannot be used" #64
Comments
El captain is still in beta mode. This may be a bug in El Captain. In your video the message says
Can you please post the messages in the logs ? Maybe that gives more details. |
Hjalte reported the same issue. The website of el captain is this https://www.apple.com/osx/elcapitan-preview/ which is why I assumed El Captain is still in beta mode. But it also says "Coming September 30" while it's already october 2. So apple's info on this is confusing. |
This is the actual El Capitan page: https://www.apple.com/osx/ |
Maybe someone using ElCaptain can try if this works
|
Ah thanks, apparently apple has currently TWO pages on El Captain, one indicating it's in beta and one that it is current. |
I installed the release of El Capitan (non-beta), updated Yosemite.
So, after this.
Kernel log message:
|
Edit- I did not see that error that fell off the screen
|
So still not working. Did you see more messages in the kernel log apart from the "not found for unload"? Not loadable - I expect some message complaining about the extension not being signed. |
|
Thanks. That confirms it's indeed Apple's increased security policy in El Capitan making this problem. |
@vitalibondar maybe apple has already disabled the rootless=0 option too. I read on https://pikeralpha.wordpress.com/2015/07/28/apples-kext-signing-bypassed/ that there are more possibilities. Maybe you can also have a look there. One is to run the Security Configurator utility and disable the System Integrity Protection. Can you try that? |
I digged further and found this
Does that work? |
In other posts I read that after the cmd-R boot you need to enter this command
|
It's okay, I just went to sleep :) but returned. |
Playback (iTunes, any DAW) ok, despite the error. |
Used the 'csrutil disable' command and it worked perfectly! |
@djohayn Recording? |
sorry saying it works perfectly might be an overstatement. I only use my mac setup for playback. So that works smoothly without any error messages or anything. Don't know how the recording might work. But it looks fine when I checkout the input in system pref. I went to recovery mode holding cmd+r during boot and then put the csrutil disable command in the terminal there. |
Thanks for all the testing. So if i wrap up, in El Capitano, the command However, recording does not work properly. I will make a new ticket for that. |
Added instructions in the readme for enabling developer kext on El Capitano. |
Cracks during recording, even with large buffer size( |
@kornerious, recording under El Capitan issue is known #65. |
oh. can you tell when will be some news?) 2015-10-20 23:39 GMT+03:00 Wouter1 notifications@github.com:
|
i5 2500+8gb DDR 2015-10-21 0:43 GMT+03:00 ALexandr Kiliyevich kornerious@gmail.com:
|
@kornerious, this ticket has been closed already 2 weeks ago and it's neither about Yosemite nor about cracks. Please post in the correct ticket or make a new one. I made one for you #73. |
My English is bad, so I have reproduced this problem in the video:
https://cloudup.com/cugKp1TU9d7
Before installing I opened a terminal and run the following command:
sudo nvram boot-args="kext-dev-mode=1"
Then I rebooted my machine.
Maybe, your driver not ready yet for El Capitan? I must roll back to Yosemite?
The text was updated successfully, but these errors were encountered: