OpenCore General Discussion

[arsradu]

3 hours ago, Emanuele-1998 said:

Hi, I have a big problem. always use this efi for opencore and it has always worked but since i formatted it doesn't start anymore. same thing with clover. I tried to format the usb but nothing.

 

My EFI OC


https://mega.nz/file/elFzHQiQ#3ytnCZUHHb69g0IV27jYjVxJDsGRN0CdKe0wSjoVf5A

Hi, I have a big problem. always use this efi for opencore and it has always worked but since i formatted it doesn't start anymore. same thing with clover. I tried to format the usb but nothing.

 

Kinda hard to read what's on that photo... If you can take another one, that might help.

 

Also, what do you mean by this: "since I formatted it doesn't start anymore"?

 

Where do you have OC now? On a USB drive? What did you format? And how? 

Are you trying to boot off of the USB drive or HDD/SSD? If the EFI stayed the same...and you only formatted the USB or SSD or whatever, that shouldn't result in an unbootable system, in my opinion. Unless you did something wrong, or missed an important step.

 

So..what did you format it as? It should be GUID partition table & HFS+ (MacOS Extended Journaled) or APFS. But if it's on a USB drive, I think it should be HFS+ (please, correct me if I'm wrong). But regardless, it should be GUID Partition Map. That's esential. Because that also gives your that EFI partition you need.

 

When you go to Erase in Disk Utility, it should look something like this.

 

Your EFI folder should also reside inside the EFI partition you created.

 

 

So...I would check that first. I don't think it's an issue with OC itself. I think it's just something not properly formatted.

 

Also, this looks like an older version of OC. Not a problem. But if you updated OC, as well, make sure you replaced all necessary files with correct ones and made all necessary adjustments to the config. If you didn't update OC, and the same exact EFI folder worked before, then I'm back to my initial thought. Which is that it's probably something with the formatting. Not OpenCore itself. But let's see.  

 

First look over the EFI you provided seems ok. But it could be that I missed something. I mean, it's an older version, but I don't think that's the reason for the boot failure. Especially since you've got the same result with Clover.

Edited May 18, 2020 by arsradu

[MacNB]

2 hours ago, markl18 said:

 

SSDT-5.aml

 

not sure what you are trying to achieve but try attached.

SSDT-5.aml

[Pavo]

3 hours ago, Synapsis said:

 

OSK="ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"

 

With using VirtualSMC.kext you do not need this.

[markl18]

3 hours ago, MacNB said:

 

not sure what you are trying to achieve but try attached.

SSDT-5.amlSSDT---.dsl

sorry wrong file

[MacNB]

1 hour ago, markl18 said:

sorry wrong file

 

 The file you posted had errors.

I fixed the errors and posted it back.

 

[markl18]

8 hours ago, Synapsis said:

sudo qemu-system-x86_64 \
    -M q35 \
    -m 6144\
    -enable-kvm\
    -cpu host \
    -smp 12,sockets=1,cores=6,threads=2 \
    -bios /usr/share/ovmf/x64/OVMF_CODE.fd \
    -device virtio-gpu \
    -display gtl,gl=on \
    -drive file=/dev/nvme0n1,format=raw,if=ide \
    -cdrom /Volumes/archive/iso/19628.1.1000_MULTI_X64_EN-US.ISO \
;

 

hi I ma trying my hardest to figure out how to boot my windows machine from bootable iso same one you got except the Russian version 

[markl18]

1 hour ago, eSaF said:

 

Actually in the installation when you get as far as 'Disk Utility' if you hit the 'Back Button' it will give you the Option to change Language. Another sure and easy way is before you start the installation, change this value in the config.plist for English as shown. Hope this helps.

I am trying to figure out how to identify iso file as something that emu can understand as in your emu script

[markl18]

11 hours ago, Synapsis said:

sudo qemu-system-x86_64 \
    -M q35 \
    -m 6144\
    -enable-kvm\
    -cpu host \
    -smp 12,sockets=1,cores=6,threads=2 \
    -bios /usr/share/ovmf/x64/OVMF_CODE.fd \
    -device virtio-gpu \
    -display gtl,gl=on \
    -drive file=/dev/nvme0n1,format=raw,if=ide \
    -cdrom /Volumes/archive/iso/19628.1.1000_MULTI_X64_EN-US.ISO \
;

 

hi can you explain how to get the iso file to be recognized qemu that it should work booting into windows into msdos partiton

 

[Guest]

in my case using a Proxmox ISO installation  is mandatory to have a full working OSX  on TRX40 chip..but from this I can use happily all OS I want to use:

 

 

In this case Catalina and HighSierra are separated passed OSX disk (via passthrough)
Windows OS is a VM file disk 

 

[insanefrancis]

Quick question. How do I rearrange the entries in Boot Picker?

Currently, Windows is #1. I want to make it macOS.

 

I'm on OC 0.5.8.

 

TIA

 

UPDATE:

Not the exact answer to my question but I was able to achieve what i wanted. I was able to set the default entry by using CTRL + Enter key on the boot picker.

Edited May 19, 2020 by insanefrancis

[arsradu]

Hi guys,

 

For those of you who did set up the boot chime, do you still hear it with the latest changes of OC 0.5.9?

 

Trying to figure out why mine is not playing anymore. The resources are up to date. OC should be up to date (including AudioDxe.efi), the config seems to be properly set up. In fact I don't remember changing anything in there that could affect the boot sound. So...that should be fine, as well. Still...no sound.

 

Just curious if you guys have the same issue or if it's just me.

 

I will also try an older version I have laying around to see if it's something with OC 0.5.9 or...something else I might have missed/changed without realising it. But I just wanted to get your opinion on this. 

 

Cheers!

Edited May 19, 2020 by arsradu

[pkdesign]

Can I make a suggestion? I'd like to discuss opencanopy more but would hate to clutter this forum with those questions. Can we make an opencanopy thread? Forgive me if there already is one since the search function doesn't work anymore.

[arsradu]

1 hour ago, eSaF said:

Nope - Boot-Chime borked in OC 0.5.9 so until the OC Devs or some other offer a solution for us Mac Wannabes   that's it I am afraid. I even found a handy  little app instead of using Terminal to toggle it off/on (attached) still silence at boot.

Chime Enabler.zip

 

Ok, so...I'm confused. :))

 

The issue seems to be on AudioDxe side, not (necessarily) OpenCore. But...according to the AppleSupport git page, AppleSupport (I'm guessing that also includes AudioDxe) is now part of OpenCore. Which sounds great to me! Except it doesn't seem to work. Cause...if you try the latest OC without AudioDxe.efi...and assuming you don't forget to remove it from the config like I did, you still don't get any sound. So...I'm confused. Is it supposed to be removed from drivers & config? But if it is, then I'm guessing it's not yet properly implemented into OC itself? So that's why it's not working?

 

In the meantime, you can try the attached AudioDxe with the current version of OC and it should work just fine. At least as a workaround for now.  

AudioDxe.efi.zip

[vit9696]

For us AudioDxe and OpenCore from master works just fine.

[arsradu]

9 minutes ago, vit9696 said:

For us AudioDxe and OpenCore from master works just fine.

ok...that's good. But also strange. Cause that means there's probably something wrong with our builds.

 

So, just to clarify, with the latest commits, do we still need the AudioDxe.efi in Drivers and config? Or should it be removed from both places?

[vit9696]

You do, there was no change in the audio logic since 0.5.8, except the reorganisation of the repository (AudioDxe was moved from AppleSupportPkg to OpenCorePkg). There was some small refactoring of AudioDxe, but it did not change anything for our setups. If you doubt it, you can of course use the driver from AppleSupportPkg release if you suspect anything can be wrong with it.

[arsradu]

Just now, vit9696 said:

You do, there was no change in the audio logic since 0.5.8, except the reorganisation of the repository (AudioDxe was moved from AppleSupportPkg to OpenCorePkg). There was some small refactoring of AudioDxe, but it did not change anything for our setups. If you doubt it, you can of course use the driver from AppleSupportPkg release if you suspect anything can be wrong with it.

 

Thank you!  I'll be testing a little more and come back with new results. I'm suspecting there's probably something wrong on my side. I just need to figure out what.

 

Once again, thank you very much for your fast reply!

[arsradu]

@vit9696 I think I might have figured out the issue. Not sure if it's intended or not. And also, not sure why it didn't happen before, but I think the reason might actually be the drivers order/priority. So...config issues.

 

Previously, I had AudioDxe.efi followed by HFSPlus.efi. And...apparently in that configuration, it didn't work. But moving it to the last place (so AFTER HFSPlus) seems to work fine.

 

@eSaF if you could try this, as well, that would be awesome.  

 

Edited May 19, 2020 by arsradu

[arsradu]

18 minutes ago, eSaF said:

Crazy thing is that is exactly the order in which the drivers are in my config.plist, I have combed and crossed reference my config.plist to see if there any anomalies that I've missed and for the love of all things good I can see none and still no Chime at boot. Clutching at straws I've arranged the drivers in the drivers folder to suit the arrangement in the config.plist and still nothing. At this moment my brain is on overload so I will take a break and do a fresh OC compile tomorrow and start afresh because at the moment I can feel the heat coming off the grey matter. Thanks to you and vit9696 for the input, the problem is obviously at my end.

 

I know you're probably boiling on the inside right now. Believe me, I know the feeling! Also, I love your sense of humour! Also, there's no defeat until you've given up. Which, for as far as I can tell, you didn't.  

 

One thing I would recommend: don't mix and match stuff from multiple places (you're probably not, but just in case). Just compile using official sources, using the build_oc tool. Worked perfectly fine for me.

 

Then just make sure you replace everything that needs to be replaced/updated. Except for the Resources folder. Since, by default that's empty. So...even if your config was perfect, there would be nothing to play. :))

 

I'm just saying. And I hope you don't mind. I'm just saying, cause I know how frustrating it can be. :)) And as you can see, I'm probably the king of stupid mistakes. So...just saying.  

 

Also, this is my UEFI - Audio

 

And NVRAM, in case you find something inspiring in there. :)) Yes, my volume is set way lower than in the docs.

 

 

By the way, since we do build AudioDxe by default, maybe it would be a good idea to include OcBinaryData, as well...? Just an idea.

Edited May 19, 2020 by arsradu

[pitrysha]

What is the advantage of the new SSDT-PLUG ?

[MacNB]

57 minutes ago, arsradu said:

@vit9696 I think I might have figured out the issue. Not sure if it's intended or not. And also, not sure why it didn't happen before, but I think the reason might actually be the drivers order/priority. So...config issues.

 

Previously, I had AudioDxe.efi followed by HFSPlus.efi. And...apparently in that configuration, it didn't work. But moving it to the last place (so AFTER HFSPlus) seems to work fine.

 

@eSaF if you could try this, as well, that would be awesome.  

 

 

This sounds like a bug I reported a while back when I was trying out NDK's boot picker but the issue was with Audiodxe and boot chime.

I reported it to the author. See thread here where @Download-Fritz and I discussed it. May be unrelated but sounds relates (pardon the intended pun ). 

[vit9696]

AudioDxe should work at any position in Drivers, and in fact all other drivers should as well. If you find a reproducible issue in this direction we should fix it as time permits, but I do not believe we reproduced anything alike so far. Please be more specific with the details.

[arsradu]

14 minutes ago, vit9696 said:

AudioDxe should work at any position in Drivers, and in fact all other drivers should as well. If you find a reproducible issue in this direction we should fix it as time permits, but I do not believe we reproduced anything alike so far. Please be more specific with the details.

 

Could this be NVRAM related? Cause, after resetting NVRAM, I lost the boot sound, as well. With the exact same config and files. No other changes.

 

Also, would some kind of log help? Is there any log or debug steps we can do to see what's going on? Cause one thing's for sure. I don't remember having this issue with earlier commits from 0.5.9, or 0.5.8. I also tried to build a specific commit...from earlier ones. But I think something changed in multiple places, cause I couldn't build anything.

 

For example, I tried to build up to this commit. But it didn't work. I get an error and build fails. I can post the error if you think that's useful. But..point is, I can't try older builds, except for 0.5.8.

 

So something did change. Well, a lot of things changed. I'm just not sure which one of them could cause this issue.

 

Edited May 19, 2020 by arsradu

[arsradu]

Ok, so a few scenarios I tried:
 

1. all files up to date, fresh build from sources -> no boot sound (at least not after nvram reset)

2. downgraded to OC 0.5.8 (official build) but kept AudioDxe from latest 0.5.9 -> no boot sound

3. replaced AudioDxe from latest 0.5.9 with the one from AppleSupport pkg 2.1.7 -> boot sound ok.

 

Config and Resources remained the same (and put AudioDxe back to 3rd place, just for consistency). All tests were performed with nvram reset in between.

 

Both AudioDxe files (used for the 0.5.9 and 0.5.8) attached. Looks like it might be related to the AudioDxe.efi after all.

 

 

AudioDxe.efi (0.5.8).zip

AudioDxe.efi (0.5.9).zip

Edited May 19, 2020 by arsradu

[insanefrancis]

On 5/15/2020 at 2:54 AM, MacNB said:

 

BCA does not run on my hack (as it's iMacPro1,1).

But I did not need it to work.

I have a Windows entry in the OC config file (Misc->Entries) and now, in System Preferences,  I have:

 

 

I click my Windows and then Restart button and OC boots Windows.

In Windows, run Bootcamp to boot back into macOS.

 

I don't have a Windows entry in my config.plist and Windows appears in the Startup Disk preference pane. But I am not able to restart to Windows with it.

 

On the Windows side, I can boot to macOS using the Bootcamp app which I installed using brigadier. But to be honest I don't know if it is really working as intended because it's still goes to the boot picker in which I have set macOS as default and waits for the 5 second delay.