-
Notifications
You must be signed in to change notification settings - Fork 8
Complete noob here. where do I put these files and why can't I find some? #3
Comments
You can find this files from this repo as mentioned in README.
You just need to replace working Your OpenCore EFI to Our OpenCore-Catalina's EFI directory.
Yes. And last place BaseSystem.img and mac_hdd_ng.img to root of this repo. |
Thanks! I have gotten farther.
and after setting my GPU device ID in boot.sh, trying to boot returns the output:
I did try a different method before this, would you recommend that I start with a fresh Ubuntu install and try again? something seems to be conflicting. |
Okay, so I reinstalled Ubuntu, Now after following the guide and running boot.sh, I get:
it seems like something (maybe my UI) is already using i915, so it wont detach, a couple of warnings, then "no iommu_group found." I still get the same output as I posted above for opencore-rebuild.sh |
Yes you are right. You need to find out what else is using i915 driver. Try to do ssh to your target machine and run line by line of boot.sh (Try to unload i915 from ssh session - It will help you to debug the issue).
Have you enabled iommu group? (I think I need to add this to the guide) 😃. |
So, after disabling the GUI in Ubuntu alltogether, the command "sudo modprobe -r i915" still says "FATAL: Module i915 is in use." there is not any UI running on the host right now, it's sitting on the TTY login screen and I am using ssh to run commands. even after blacklisting i915, it still is in use somehow by something. anyway, this is what i get from boot.sh now:
I cannot find a clear answer on how to enable iommu groups, I do have intel_iommu=on in my grub command line though. |
If TTY is there, may be that still means iGPU used by host. Check this legendary article, https://worthdoingbadly.com/gpupassthrough/
This clearly means IOMMU not enabled in your grub bootloader somehow. follow arch linux guide on enabling IOMMU. It has more clearer explanation 😃 . |
Yes seems worth it to downgrade. |
Okay, I am now running ubuntu 19.10.
so, if my assumption is correct, passthrough is working and it's just not booting? nothing shows up on the host's screen, but it does turn off. |
This is strange. You need to check by running one line by line of boot.sh Is display showing anything regarding OpenCore booting up? |
@4mirfor3v3r, Can you share the complete logs for better understanding? - I think this is not complete, May be terminal scrolled up?. |
Same issue |
@awnrt, It looks like the issue of OpenCore. But I can see passthru is working (Anything like: screen goes black? OR OpenCore window showing up?). Can you share the config.plist? |
@vivekmiyani Kernel panic when passthrough |
@awnrt, Just few more questions, When this error coming up? - After Apple logo OR before / after OpenCore boot? Similar error I was faced when opening chrome browser. (Check the README.md's issues section) |
@vivekmiyani |
@awnrt, Can you let me know hardware information, particularly CPU generation and model. |
@vivekmiyani both gpus connected to one monitor, igpu through hdmi and dgpu through dp |
I am getting the same error as at the top when running the rebuild command
Also, in my case after running boot.sh my screen turns off and I only have a blinking caps lock indicator, not sure how to collect logs for this. |
@Ryhon0, Can you create separate issue for this.? And regarding caps-lock blinking, I've also faced similar issue randomly in my case. The reason is unknown to me. And regarding Resources directory error, you can skip that as of now. It's only because of |
@legop3, Is this still an issue for you? |
Hello, I am having some trouble. I set up a VM using OSX-KVM, and it works, this is my next step. I cannot find the files opregion.bin, bdsmSize.bin anywhere, and I do not know where to even put the rest of the files. My KVM folder has an OpenCore folder with an EFI folder, is this my working OpenCore? should I put these files in that folder, or put that folder in these files before I do ./opencore-rebuild.sh
The text was updated successfully, but these errors were encountered: