Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop OEM -> system won't boot #121

Open
martinweiss opened this issue Feb 18, 2015 · 2 comments
Open

Drop OEM -> system won't boot #121

martinweiss opened this issue Feb 18, 2015 · 2 comments

Comments

@martinweiss
Copy link

My machine is acting up, and I'm not sure why.

System specifications:

  • GA-Z97N-Gaming 5 motherboard.
  • Intel i5-4460 CPU.
  • Clover UEFI bootloader.

I generated SSDT.aml using your script:
screenshot 2015-02-18 22 02 35

I placed SSDT.aml in EFI/CLOVER/ACPI/patched. When I tick off "Drop OEM" in the SSDT section in my config.plist, my computer won't boot:
screenshot 2015-02-18 22 08 40
2015-02-18 21 50 34
2015-02-18 21 50 58

I'm sure your tool is working as it should, it must be me doing something wrong. Should I have copied more files to EFI/CLOVER/ACPI/patched? Thanks in advance.

@Piker-Alpha
Copy link
Owner

Drop OEM can be problematic. Look here #102

The problem was an object defined in SSDT-4 that was used from the DSDT. First locate the SSDT that is causing the boot failures (might even be the same) and then solve it as I suggested.

@icezar
Copy link

icezar commented May 14, 2015

I personally never use Drop OEM if I'm using an SSDT. My logic is that when you tell clover to Drop OEM, it doesn't drop the tables read from the motherboard, but the ones read from the SSDT file because the SSDT file becomes the OEM table at boot... My logic might be wrong though. Just a thought.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants