Sonoma 14.6?

[mariosprt]

Hi Steve

I initially used Startup Options, Erased the boot volume but maybe because I had another volume on the same SSD I got an error and I could not “validate” my MacBook due to some problem on Apple validations servers in the last week or so - long story.

All this to explain I had to use a friend’s Mac to “Restore” my MacBook, it was quick and easy and after that it booted into Startup Options and I was able install Sonoma, and yes it’s the latest version 14.6.1 and yes, the MOTU Audio Driver installed and work!

I guess what Mike says about being “something” in our system that causes the MOTU driver to not load is accurate, because a fresh install solves it.

I will add the links in case you need it.

Similar “failed to validate device” issue I found on Apple Discussions:
https://discussions.apple.com/thread/25 ... ortBy=rank

Which led me to the solution:
https://support.apple.com/en-us/108900

Reports of the problem on Apple servers:
https://www.reddit.com/r/MacOS/comments ... utm_term=1

Good luck.

Mario

PS: the path to downgrade the macOS is long and twisty and as you can see unnecessary because the drivers work on Sonoma 14.6.1 as long as the offending gremlin is not there.

[cuttime]

Just updated to 14.7 with no apparent problems.

[James Steele]

Just updated to 14.7 with no apparent problems.

Same here. Haven't tested DP or other DAW apps, but I think it's gonna be fine. Gonna be quite some time before I try Sequoia though!

[mikehalloran]

I guess what Mike says about being “something” in our system that causes the MOTU driver to not load is accurate, because a fresh install solves it.

I think you missed my point. I don't think anyone has had problems with a fresh install.

[joelfriedman]

I updated to 14.7 last night and am about to get back to work. I had a momentary fright when it booted up to my 2nd monitor and my main monitor went black and didn’t show up . A shut down-restart fixed it. DP booted fine.


Sent from my iPhone using Tapatalk

[mariosprt]

I guess what Mike says about being “something” in our system that causes the MOTU driver to not load is accurate, because a fresh install solves it.

I think you missed my point. I don't think anyone has had problems with a fresh install.

Hi Mike

I was hoping I could solve it without a full install but …
Anyway I don’t think I will make any updates anytime soon.

I will go Sequoia a year from now, when a new version is being launched to minimize the updates I will have to deal with.

[mikehalloran]

I was hoping I could solve it without a full install but …

...without MOTU doing a screenshare to see the conflict, that wasn't going to happen. They will do this only on interfaces that are still supported. In my case, the offending .kxt was found when they helped me through the MIDI install on my supported micro lite — afterward, the Audio driver install on my unsupported unit went smoothly.

Anyway I don’t think I will make any updates anytime soon.

I will go Sequoia a year from now, when a new version is being launched to minimize the updates I will have to deal with.

I have my 828mkII FW and my MTP AV & micro lite units running just fine over Sequoia. Since both were fresh installs, zero problems (as long as the MIDI driver is installed first).

Audio MIDI Setup.app AUDIO — MOTU, M•Audio.jpg (319.51 KiB) Viewed 5379 times

Audio MIDI Setup.app MIDI MOTU, M•Audio.jpg (155.33 KiB) Viewed 5379 times

[mariosprt]

I have my 828mkII FW and my MTP AV & micro lite units running just fine over Sequoia. Since both were fresh installs, zero problems (as long as the MIDI driver is installed first).

You are a brave man
That’s good to hear, but from what I understood any point update could give you problems, like 14.4 broke it and then 14.6 solved it, am I right?

Anyway this is my hobby, not my job so I can stay one OS version behind, but doing a fresh install means a week installing software instead of making music

[HCMarkus]

I had to reinstall Ventura awhile back; something got corrupted. It installed right over my existing system and has worked great since, including my fairly recent migration to Sonoma.

[mikehalloran]

I had to reinstall Ventura awhile back; something got corrupted. It installed right over my existing system and has worked great since, including my fairly recent migration to Sonoma.

Huh????

I wish I could test that. Problem is that, if it messed up, it would take days to restore the 5.5TB data I have on my System drive.

[HCMarkus]

I won't be testing that again (unless I absolutely have to)... sorry Mike.

[mikehalloran]

I won't be testing that again (unless I absolutely have to)... sorry Mike.

No problemo!

I work on just enough Macs now and then to keep a jar of these guys handy. I tried both on my Sequoia Test Volume—worst case, I could delete and start again. No go, unfortunately.

Screenshot 2024-09-20 at 11.46.36 AM.png (1.92 MiB) Viewed 5274 times

[stevesper@gmx.de]

what a ride…

I tried to update to 14.7 via System Preferences and also via appstore. both didnt work, „the update could not be personalised“ (in german). I saw in several forums that this seemed to be a common problem which should be solved by apple „soon“.
I didnt want to wait any more, so I completely erased the disk and installed the latest Sonoma again, which is 14.7. Then used my latest timemachine backup to restore everything… took like 8hours…

After that, still no Motu hardware.

I forgot to change the security options. so I went back to startup options to set the security startup settings according to the motu help. To complete that step, OsX asked for my admin password, but it declined the pw I had. So again, no way to get the Motu running. The password was definitely the correct password.

Next, I created a new admin user and tried this one in the startup security settings…. no effect, pw is still rejected.

Then, I found in a mac forum, that using the terminal and type „reset passwort“ in recovery mode lets you reset the password. so. i did that and finally was able to complete the startup security settings dialogue.

After that….. still no Motu….what the ••••?

So, in a very final, last final, final final attempt I reinstalled the lates Motu driver.

AND…. Surprise!!!! ! I was prompted again for that unallowed new extension and I WAS ABLE TO ALLOW IT!!! like a virgin!!

After that, my Motu 896mk3 hybrid came back to life..

I was really close to sell my mac and stick to hardware only…
have to make a 3 day vacation now.

thanks everybody for help and ideas
steve

[primeevolutionary]

My problem didn't happen until I went from 14.6 to 14.7, but, then, had the same exact problem as everyone else with my 896mk3. I did a fresh install of the OS and it works. I tried all of the other things first.