installer error #17
Comments
|
Asked two questions to BenCarlin on MacRumors
|
|
Hi Wouter, Thanks for the quick reply! Yes the prompt did ask me to enter my password. 27 Dec 2014 17:33:59 com.apple.kextd[20]: ERROR: invalid signature for org.virtualbox.kext.VBoxUSB, will not load Quite exciting to be the first user! Hopefully can get it to work! |
|
The main error is /System/Library/Extensions/EMUUSBAudio.kext failed to load - (libkern/kext) not loadable The first errors are because there is no old driver to uninstall The last error is trying to install driver linking symbols for debug purposes but those symbols are not available. Let's just disable that. |
|
Is there anyway that I can proceed or will you rewrite script file? Thanks again. |
|
Yes you can just manually copy the file to /System/Library/Extensions, fix the permissions and then triggering the kextload. The commands are literally in the kextInstall script, it's a very simple plain text script. I fixed the script but that's only to fix the last error, you have another error that I don't understand yet. |
|
Did you check the console and kernel logs? Usually the cause of the problem is also reported there. This may also be because you are not a developer. In that case you probably see some text saying that the code is not signed properly by Apple. I read about that on the web but I never saw such errors (probably because i'm a developer). |
|
Ben also wrote
|
|
I think this error (about VBoxUSB) is not relevant, it complains about VBoxUSB which is not the extension we are loading for the EMU. THe extension we are loading for the EMU is com.emu.driver.EMUUSBAudio It's quite normal apparently that you get a bunch of errors/ warnings while re-configuring the kernel. I'm getting this Note that it takes up to about half a minute between the moment you run the script (to be exact, the kextinstall command) and the moment the |
|
Hi Wouter, I'm not that tech savvy to be honest. Just to be clear though, should I already have the emu 0404 'EMUU_MacAppDrv_US_1_50_07' driver already loaded when running your script? Don't know if it makes a difference or not. This is the message I get in the console: 27/12/2014 18:56:39.919 sudo[669]: bencarlin : TTY=ttys000 ; PWD=/Users/bencarlin/Desktop/EMU-driver-master ; USER=root ; COMMAND=/sbin/kextunload /System/Library/Extensions/EMUUSBAudio.kext |
|
Ah thanks, I'm now checking the log in detail. For your question
No, it doesn't matter , the script shows an error that it can't remove the old driver because it can't find it but then it just proceeds. Just make sure the EMU is not yet on. |
|
After running the script I did try and launch the emu application from your 'controlpanel' folder. I switched my emu box on but it didn't detect it. If we do finally get it to work I will definitely record a song for you! :) |
|
This is the error
I don't have a way to sign the kext at this point. I have one suggestion and one question Question: Are you on Mavericks or on Yoshimite? Suggestion: you may want to try the 'ext not loading' suggestion on the main page. on Mavericks you could enter in the command line and reboot. After that, check the logs if the scripts now can be loaded. I don't know if this workaround is still possible on Yoshimite |
Heh that would be fun. |
|
I'm running Yosemite. Ok so I just type in that into the command prompt now and then restart. Then just launch the emu application and see if it detects? Or do I have to run that sudo command, reboot and then try the install again? sorry for being a noob! |
|
Yes, the command is to be entered in the console as one line. It used to turn the system into "kernel development extensions allowed" mode. It asks for your admin pass. Then it should report success. Then reboot. |
|
After reboot I think you need to try again. You can also just do these two lines in the console as the kext is already in place with the correct permissions, it only needs to be loaded |
|
But of course you can just try to turn on the EMU and then the control panel to see if it's already loaded. Just remember to turn off the EMU before running the kextunload or running the script. |
|
I just rebooted and launched the application.... it detected it!! So I guess should work now. Should I drag this emu application to my applications folder and get rid of the original "EMUU_MacAppDrv_US_1_50_07" application I have installed? |
|
Ah cool so the fix for this is still working. That's great to hear. No nothing needs to be installed in your applications folder. This kernel driver is all you need. Select your required sample rate with the console. Then you can start your favourite audio program (I'm using audacity), select the EMU and start recording. I'm not exactly sure what the EMUU_MacAppDrv_US_1_50_07 in your applications folder is but probably it's the original EMU driver installer. You can run that to restore your original driver. But you can also follow the instructions on the github main page https://github.com/Wouter1/EMU-driver on how to re-install the original driver. Let me know how it goes :-) |
|
Ah maybe you are referring to the control panel when you talk about "application". Yes Applications is a nice place for that. |
|
Hmm well now it detects the emu box but when I try recording with both garage band and logic pro x it doesn't record anything. Just flat line. Even though on the box it shows the mic is picking up sound. My input device is set to EMU 0404 | USB. Ahh just when I though it was getting somewhere! |
|
This is a good test drive, it helps a lot improving the stuff. I don't know how garage band and logic pro X work. It could be that something still needs to be selected. Maybe as a first test you can try to use audacity to see if the basics are working? You can then select the EMU under the Mic icon and press the record button? thanks again for the patience and sorry for the inconvenience. |
|
I'm downloading Audacity now and will see if that works! |
|
I just figured we can test even simpler. Just open the audio control panel and select the EMU for input. Do you get any signal there? |
|
I just opened the 'Sound' settings from control panel and under 'input' selected the emu 0404. It says the selected device has no input controls. Maybe thats because it does it from the box itself? |
|
Mmm this is interesting. Where do you get that message that there are no input controls? WHen you switched to the input tab and select the EMU in the input list? |
|
Ahh doesn't work in audacity either. I just gets stuck. I press record and it tires to go forward but the line stays on 0.0 |
|
No need to install, the driver is installed ok but I think the driver fails to sync with the crystal in the EMU. Can you open a console and type Then search for some text like this It's these 'notifyWrap X' messages that I'm interested in. |
|
This text should be close to the end I suppose. Can you post this text? |
|
I searched for 'UsbInputRing' and here is some text copied from around that area: Dec 27 19:27:19 Bens-MacBook-Pro.local WindowServer[149]: WSGetSurfaceInWindow : Invalid surface 747908124 for window 60 |
|
I can paste the rest in from that point on if you like? |
|
Actually there's loads so props not good to paste it all in lol |
|
Mmm this is interesting. Is there more text after that USB pipe read error? Can you give me like 30 lines after it, if there are |
|
Yeah there's loads more but yeah I'll give you around 30 lines |
|
Dec 27 19:35:56 Bens-MacBook-Pro kernel[0]: USB pipe READ error e00002ef |
|
It goes on for loads after that as well. |
|
Thanks! Looking at it |
|
From that log it seems like the EMU control panel crashed and that caused a termination of the driver. There is a crash report but decyphering it is a bit troublesome as it's not in our hands (it's provided as is by Creative). Maybe we can better first try to get the audio working (instead of debugging the control panel) Maybe you can reboot and not open the EMU control panel after reboot. Instead, straight open the system's audio control panel and try again to connect. |
|
Ok so I just reboot, go to control panel and select 'sound' under 'input' select the emu 0404 and see if that message 'The selected device has no input controls' goes away? |
|
yes. The reboot it to re-start the EMU driver as it apparently got stuck for some reason. I'm not sure in which order you did things, but the control panel was open and crashed according to that log. If you opened the system audio control panel after that then the driver was already stopped. |
|
I tried rebooting and then switching on my box. Then going to sound input settings from system preferences and making sure emu 0404 was ticked. Same message appeared "The selected device has no input controls". Doesn't look promising does it lol... |
|
No there is something wrong. With your help I maybe can fix it - it works all fine here... |
|
Ok so here is the log.... its very long! Really appreciate your help and support. 27 Dec 2014 20:26:05 kernel[0]: +EMUUSBAudioDevice[0xffffff8052e28400]::performPowerStateChange(1, 2, 0xffffff82170eb8f4) |
|
Thanks again! Really appreciate that you can help me with this. Sorry that it doesn't work as I thought it would. Going to check that log. Give me some time.... |
|
Not a problem. At least you're trying to solve this silly driver problem. It seems such a shame to get rid of some perfectly decent kit for some stupid driver glitch. Of course take all the time you need :) |
|
These are the source of the problem For some reason the USB pipe does not open properly and it gives a (for me weird) error Looking into it but this may take some time. |
|
Ahh ok strange that I have it and you didn't! Ok thanks again! |
|
First guess is that Yosemite is interpreting "kAppleUSBSSIsocContinuousFrame" differently. |
|
tried with 0 instead but that does not work here. |
|
Tried to use mBus->GetFrameNumber() that gives |
|
So Yosemite is what's causing the problem? Are you running older operating system? |
|
Yes I'm running Mavericks. I don't switch until the new OS has proven itself a number of months and shows better than the previous. Actually I skipped everything between Snow Leopard and Maverics for these reasons. I'm doing a lot of programming and setting up a new computer is a major pain so I dont want to waste time with broken OSs. Note I'm not saying Yosemite is bad, it am just waiting till it's proven better. It seems that the behaviour of reading from USB using "kAppleUSBSSIsocContinuousFrame" has been changed. This special number for the USB read command in Mavericks tells USB to pick up the next incoming USB packet, and to ignore the actual exact frame number. Keeping track of frame numbers in the original driver was broken and I was happy to remove that. It seems Yosemite does not recognise this special number and thinks it's a reference to a too-far-in-future USB packet. I'm out of time for today. I hope to find some solution tomorrow. Sorry that I could not get this fixed quickly and that I can't test on Yosemite. I will add this to the readme for now. |
|
Tried mBus->GetFrameNumber() + 1. Same error 2c2. |
|
Thanks again for your time. Not a problem about tonight. I would rather wait a few days and not have to splash out lots of money buying new sound card!! |
|
I moved this issue with reading from the pipe on Yosemite to new ticket as the installer errror problem was fixed |
http://forums.macrumors.com/showthread.php?s=b7d660127f5bbd50631d656f3888c9ae&p=20530636#post20530636
Installer gives error
The text was updated successfully, but these errors were encountered: