July 21, 2014 at 3:22 pm #64572
I just updated to DP4 and DPS is broken now. It did run in DP3, but now gives the following error: Couldn’t fetch the Digital Power station device. Please reboot to resolve the issue. Rebooting does not fix the issue!July 22, 2014 at 2:01 pm #64584
I installed some other sound tools to get my DPS-quality music back.
Boom didn’t install too, so something clearly changed in the audio output with DP4. I tried Hear too, but that tool makes music worse, the default presets give lots of distortion! (ouch) So I think I have 2 options: wait for a fix or install Mavericks again.
Let’s install Mavericks again. Wait, I can’t download Mavericks from the App Store because it requires Snow Leopard, Lion or Mountain Lion! Ouch again! I guess the only thing I can do is start up from the recovery partition and do a clean install. Install all my software again? No way…
So, I’m waiting for a fix lol. It’s in times like this that you realize how good DPS is…July 25, 2014 at 12:56 pm #64583raleighingParticipant
I installed the Yosemite Public Beta yesterday and it DPS is now broken for me too.July 26, 2014 at 4:17 pm #64582
so it seems the latest build of Yosemite requires a change in how kexts (like our audio driver) are signed for security. this *should not be a difficult fix. i will let you know our progress as we chase this one down.August 1, 2014 at 11:12 am #64581Dan RiceKeymaster
Regarding the reported Yosemite beta/DPS plugin compatibility problem. We have a workaround. Please use this at your own risk, for testing purposes only. I am unsure what system security implications this workaround may present to your system.
In terminal, paste:
sudo nvram boot-args=”kext-dev-mode=1″
DPS should work. This method disables Apple’s new app (kernal extension) signing requirement. It is unclear whether this requirement will make it to the final release of Yosemite.August 1, 2014 at 3:13 pm #64580
I tried your sudo command and it didn’t work. So, I removed the “” and it worked! 🙂
sudo nvram boot-args=kext-dev-mode=1
Thanks for your tip! How do we revert back to normal? mode=2?August 4, 2014 at 8:58 am #64579Dan RiceKeymaster
It seems odd that you had to leave out the quotes. From what I’m reading, it seems those quotes are pretty important. Glad it worked for you!
To revert to default, and to have the system boot normally without any extra options try:
sudo nvram boot-args=””
sudo nvram -d boot-argsAugust 4, 2014 at 11:16 am #64578
Back to normal is probably mode=0. That is standard for a default setting.August 4, 2014 at 5:12 pm #64577
I can confirm that the command drice gave, (sudo nvram boot-args=”kext-dev-mode=1″ ) does indeed work. Just be sure to reboot after.
Pasting this again without quotes will simply place an additional value in “nvram”, that may, or may not do anything. You can see the current value of nvram by typing:
Unless you delete boot-args argument first before typing in the one without quotes, you’ll end up with two entries. If this happens,
to be safe, run:
sudo nvram -d boot-args
and then re run the command that drice posted avbove.
to revert, simply:
sudo nvram -d boot-args
to clear your boot time arguments.August 6, 2014 at 9:49 am #64576
We are working on getting the kext signed now. It seems, yet again, there are some undocumented requirements for this no one is aware of. I will keep you guys updated…August 6, 2014 at 12:55 pm #64575
I am consistently impressed with the Bonjiovi DPS team. Your interaction, and willingness to listen and take feedback from the community of DPS users has been phenomenal. Many “bigger” companies should take note! Keep up the great work!August 15, 2014 at 4:12 pm #64574avincent98122Participant
Freaky Friday greetings. All good. I suspect the quote in the sudo cmd is the culprit, as deleting the quote is what caused DPS to load properly w/ the work-around. Of all the extras I miss for Yosemite incompatibility, DPS was tops on the list. Now .. Happy Friday!
AnthonyAugust 17, 2014 at 7:43 pm #64573
Seems to only be a problem if you are copying and pasting (at least, for me). Likely something to do with text encodings. If you type it in manually, it works.
- You must be logged in to reply to this topic.