If you're getting stuck at this point, there's likely an issue with loading the kernel, main culprits: This is where macOS's bootloader(boot.efi) comes onto the scene, specifically what it does is prep the environment for the kernel to load and where OpenCore injects kexts. If you're having issues booting at this point, main things to check for:įor the rest of the possible issues, see here: OpenCore loads and shows you all possible boot options.ACPI Tables are loaded from EFI/OC/ACPI.Graphics Output Protocol(GOP) is installed. EFI drivers are loaded from EFI/OC/Drivers.BOOT圆4.efi is loaded which then chain-loads OpenCore.efi from EFI/OC/.System locates BOOT圆4.efi on your OpenCore USB under EFI/BOOT/.System powers on and searches for boot devices.This section will be brief, as OpenCore boot issues are fairly rare and usually simple user error: While this page won't solve all your issues, it should at least help better understand where in the macOS boot-process you're getting stuck and hopefully give some ideas as to why you're stuck. So with troubleshooting a hackintosh, it can be a bit difficult to really understand where you're getting stuck as the exact keyword you're trying to search for may not match anything on google. Getting started with ACPI (opens new window).To replace the kernel on the device, you will need to flash it to the device: $ fastboot flash boot myboot. The above will only boot your kernel once and the old kernel will be used again when you reboot the device. Once the device is in fastboot mode, you can boot it with your own kernel, for example: $ fastboot boot myboot.img To use the fastboot command you first need to put your device in fastboot mode: $ adb reboot bootloader Just use sudo, fast boot needs Root Permission Solution 3 Simpler just to fix the permissions in the long run. But then you need to run every command that talks to the device as root, which tends to cause other complications. The even shorter cheesy version is to just run fastboot as root. Then verify the device node permissions have changed: ls -Rl /dev/bus/usb It's ok if that file does not yet exist create it with a line like this, inserting your own username and vendor id: SUBSYSTEMS="usb", ATTRS="18d1", MODE="0640", OWNER="mbp" Run lsusb -v | less and find the relevant section which will look something like this: Bus 001 Device 027: ID 18d1:4e30 Google Inc.Ĭouldn't open device, some information will be missing To fix it (on Ubuntu other systems may be slightly different): The USB id is different in fastboot mode, so you can easily have permission to it in adb but not in fastboot. The short version of the page linked by D Shu (and without the horrible popover ads) is that this "waiting for device" problem happens when the USB device node is not accessible to your current user.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |