Search results

The manual is wrong. The option is not anywhere in the BIOS.

It is a 13700K, but my BIOS (f28) has no aperture size parameter anywhere. That link is for the Aero G though, I have an Aero D.

Yes, if I remember correctly it won't boot without it.

I haven't had any problems specific to any BIOS version that I've flashed. F28 works fine. My system is working perfectly except it won't wake the display after sleep and no matter what I have tried I can't seem to fix that... so I just gave up and disabled sleep.

I need a software controllable relay to physically disconnect the power to the SATA connector or something. Lol.

Thank you for trying. I was hoping your SSDT would work, because I previously tried disabling the port this way... but yours also didn't work. I don't understand why my computer is so stubborn. I can put whatever garbage I want in that port's ACPI data and it will show changes in ioreg, but...

Actually I think I posted the device info that is my actual SATA port. This must be the drive itself...

It is indeed listed as internal... which it is. How can it be changed to external?

That would stop the errors, but it kind of defeats the purpose of having the drive installed in my computer. I want to use it in at least one OS without having to mess with the bios every time I want to use it.

I've seen other people with this problem before but not a way to fix it. Anyone know how to make this stop happening? Every time I reboot or shut down I have to wait quite a while longer than I should and it is annoying. It just gets stuck repeating an error: [AHCI][PRT][00170070]...

So the way I fixed this was I took @CaseySJ 's advice and added another APFS volume to the drive, then installed MacOS fresh. It booted that volume fine, so after I was convinced it was not going to break again, I used migration assistant to copy everything from the original install (which I...

Ok, nothing really died... My MOTU MIDI Express 128 is clearly not broken, because I tried it on Mavericks on my Mac Pro 5,1 and it works fine. However it doesn't work on Sonoma on my hackintosh, or on Opencored Ventura on the same Mac Pro. But it used to work fine with my hackintosh when I...

So I just disconnected my MOTU and plugged it into my Mac Pro 5,1 running Ventura, and it doesn't work there either. After the install the extension was blocked, but I enabled it. Says it's running, but it doesn't exist in Audio Midi Setup, just like on my hackintosh. So I guess Sonoma isn't...

Yes, and it was already allowed from being installed in Ventura anyway. Either that, or it never even attempted to actually install it. I have no blocked extensions, and it says it's running.

Yeah I've done all that. I have the newest MOTU driver and my USB mapping was perfect already from Ventura. I confirmed all the ports are still mapped properly and working. The thing that concerns me is that there is no new driver for Sonoma from MOTU, they just claim the old one works...

Hi, I had a working MOTU MIDI Express 128 in Ventura, but my install got corrupted and wouldn't boot, so I did a fresh install of Sonoma. The MOTU extension is installed and it says its working. IOREG reports the device. But it will not show up in Audio MIDI Setup or Logic. This is awful...

I wanted to follow up on this. It does seem that my Ventura install is just corrupted somehow. I added another APFS volume to the same drive, and installed Sonoma on it. Not exactly the best test case since it's not the same version of MacOS... but Ventura used to work just fine and if I'm...

Have not tried a CMOS reset, just a BIOS reset. The APFS volume thing is a good idea. I forgot you can do that with APFS so easily. A reinstall was going to be my next idea, so I'll try it that way.

Ah. Well it's the opposite for me, it only boots properly maybe 10% of the time.

Do you by any chance have ACPI errors during boot? I have some that have always been there and didn't seem to cause a problem. However since this started happening, I notice a pause when it hits them sometimes. It never pauses on them when it is going to boot properly, but it doesn't always...