#SWINSIAN APPLE REMOTE CONTROL INSTALL#
#SWINSIAN APPLE REMOTE CONTROL DRIVERS#
#SWINSIAN APPLE REMOTE CONTROL UPDATE#

Its booting from firmware which loads EFI drivers from firmware then loads OC which loads more EFI drivers from EFI partition. Using your logic, it's not booting from OC. Other useful drivers for Startup Manager would be the Screenshot driver, NVMe driver, these new USB drivers, UGA on GOP driver, Thunderbolt driver (to support Thunderbolt booting one day). I already have the apfs driver working this way (or at least the apfs.efi driver from Apple). I would like to see OpenCore split into parts where some of its drivers are loaded by the Driver# mechanism so that the Startup Manager can benefit from those drivers (to enable boot screen for Startup Manager to allow bypassing OpenCore). Maybe this mechanism doesn't work on some newer Macs but I know it at least works on the MacPro3,1. The loading of OC happens after the Startup Manager would load (when you hold the option key at boot) but this can be changed by having firmware load the drivers earlier from EFI partition using the Driver# mechanism. What difference does it make where the drivers are loaded from (firmware or EFI)? The point is that macOS can now be booted from USB pcie. A working USB3 will be even more useful now with 0.4.1’s booting capability.Ĭlick to expand.Using your logic, it's not booting from OC. If others see the problem as well I would follow up for a potential patch. If anyone else with a nanoTECH USB3 board (or similar with the FL1100 chipset) could confirm one way or the other, that would be great. I know it works in Monterey for see post #3364. It always works with 11.x.y.Ĭould be due to my specific nanoTECH card still.

Feeding in some auxiliary power doesn't help. A keyboard or mouse connected to USB3 work fine.Īttached is a verbose boot output which points to a missing NMI. Īn SSD with Monterey, connected via USB3, is correctly seen by OCLP, but then booting fails - has to fail, because it fails the same way when the SSD is on an on-board USB port and any USB storage medium (a memory stick e.g.) is connected to USB3. And it works well in BigSur which is very useful, see post. The new OCLP 0.4.1 provides support for booting from USB3. I currently have Big Sur on my internal fusion drive (so that it works more 'natively' without post-install patch) and wanted to test a little more Monterey before installing it on my main drive.Ībout a USB3 expresscard (nanoTECH) again after a while. I don't know it that's a known issue/limitation (wasn't able to find out) or if that could get fixed in the future?

#SWINSIAN APPLE REMOTE CONTROL INSTALL#

However, when I select the EFI Boot to use OCLP I cannot see this macOS Installer anymore (even if I press the space bar), so no possibility to install any update. If I hold the option key down, I see the 'macOS Installer' volume. I go to System Preferences, the download starts, prepares, then the Mac reboots and then things get complicated.

#SWINSIAN APPLE REMOTE CONTROL UPDATE#

The problem is: I cannot update this version through my iMac: It is installed on an external ssd and works well. I don't know if this is a known issue but I'm currently testing macOS Monterey on my iMac 14,3. Hi, hope someone will be able to help me out (I opened an Isue on OCLP Github but was told to use forums instead)

Swinsian apple remote control