Jump to content
8755 posts in this topic

Recommended Posts

1 hour ago, nmano said:

Thanks for new update 0.5.9 Image work smooth. 

https://github.com/acidanthera/OcBinaryData

How to enable OCEFIAudio_en_Files config.plist?

Thanks for your support.

 

1383652533_ScreenShot2020-05-23at12_41_34AM.thumb.png.c7fde3499f6348e5442488e2ddc8d60b.png

 

567208809_ScreenShot2020-05-23at12_47_39AM.thumb.png.3731f2ad6e20e85d428c347ecffc7910.png

 https://dortania.github.io/OpenCore-Desktop-Guide/extras/gui.html

4 hours ago, makk said:

how to get the OpenCore boot log ?  in Mojave 

--would like to see all the messages during OC bootloader startup.

 

apparently there are several errors relating to APCI and ACPI and a few SSDT CpuPm, P-states, C-states 

and a Truncated 64-bit constant in a 32-bit table

 

Use OpenCore DEBUG version, set config: Misc -> Debug -> Target to 83, for example (this will also save as a file so you can examine it later), and enjoy! :)  Log will be saved to your EFI partition.

 

More info about that you can find in the Configuration.pdf. (page 33/34)

Edited by arsradu
10 hours ago, mathew2019 said:

Hi Guys

 

Is there anyone tried  latest i9 10900K CPU and  Z490motherboard with OpenCore? I am stuck at Apple boot screen.

 

Thanks

 

We can't afford it. :) I mean, at least I can't. :))

Check here if you've got everything set up correctly. Especially APCI.

On 5/27/2019 at 12:13 PM, Andrey1970 said:

There a name which you see in the menu OC.

 

221591836_2019-05-2714_11_23.png.df6873556fc39939dbe2506d36cf2347.png

 

Hi, I was referred to this post by @arsradu - thanks. I am not using bootcamp, have windows on a separate disk and use OC 0.5.8 with OpenCanopy bootpicker. I want to change the name of the Windows drive shown in bootpicker. I mounted the Windows disk, then placed a plain text file ".contentDetails" in EFI/Boot as shown here with the name I want:

792920648_Screenshot2020-05-23at08_19_10.png.fbf16e69355bffaf7e0304d8a7272ce2.png

 

On reboot, nothing changes, drive still called "Windows". I guess I am misunderstanding something. Can anyone help me please?

 

 

1 hour ago, Humanate said:

 

Hi, I was referred to this post by @arsradu - thanks. I am not using bootcamp, have windows on a separate disk and use OC 0.5.8 with OpenCanopy bootpicker. I want to change the name of the Windows drive shown in bootpicker. I mounted the Windows disk, then placed a plain text file ".contentDetails" in EFI/Boot as shown here with the name I want:

792920648_Screenshot2020-05-23at08_19_10.png.fbf16e69355bffaf7e0304d8a7272ce2.png

 

On reboot, nothing changes, drive still called "Windows". I guess I am misunderstanding something. Can anyone help me please?

 

 

 

OK, I had to test this myself. :D Aaand yes, it seems to be working. And I don't think it has anything to do with BootCamp. But it might have something to do with your Picker configuration.

 

So .contentDetails added to the Windows EFI partition. That looks ok.

OC config: Misc -> Boot -> Picker Attributes: 1

Picker Mode: External. That's probably already set up.

 

Aaand...at least for me, that worked out brilliantly.

I'm using 0.5.9 though... But I don't think that makes a difference. But if you do, you can find attached the one I built a few days ago.

 

IMG_0089.thumb.jpg.f947f004d6d022cd57756b544fdbbcdd.jpg

OpenCore-0.5.9-RELEASE.zip

Edited by arsradu
  • Like 1
32 minutes ago, arsradu said:

 

OK, I had to test this myself. :D Aaand yes, it seems to be working. And I don't think it has anything to do with BootCamp. But it might have something to do with your Picker configuration.

 

So .contentDetails added to the Windows EFI partition. That looks ok.

OC config: Misc -> Boot -> Picker Attributes: 1

Picker Mode: External. That's probably already set up.

 

Aaand...at least for me, that worked out brilliantly.

I'm using 0.5.9 though... But I don't think that makes a difference. But if you do, you can find attached the one I build a few days ago.

 

 

OpenCore-0.5.9-RELEASE.zip

 

Thanks for testing. I am obviously missing something being a noob and all :unsure:

 

I looked at your attached 0.5.9 for some insight but I think this is just the release, no config. plist in the attached file

 

Can I check the basics?

 

1. Do I make a plain .txt file called ".contentDetails" and put the name I want in there or do I find an existing file somewhere and modify it?

2. I have tried making a .txt file as above and then mounting my windows drive (within macOS, not Bootcamp though) and placing the .txt file called ".contentDetails" in EFI/Boot, nothing changes

3. I do have Picker Attributes: 1 now, it was set to 0 and Picker Mode is External

Edited by Humanate
1 hour ago, arsradu said:

 

We can't afford it. :) I mean, at least I can't. :))

Check here if you've got everything set up correctly. Especially APCI.


It’s not a icelake 10nm cpu brother the 10900k is a cometlake 14nm cpu or in other words a coffeelake cpu with two more cores glued on.

theres no support for it in Catalina yet though.

  • Like 1
1 minute ago, AudioGod said:


It’s not a icelake 10nm cpu brother the 10900k is a cometlake 14nm cpu or in other words a coffeelake cpu with two more cores glued on.

theres no support for it in Catalina yet though.

I see... Alright then. I didn't know that. :D I've learned something new today. Thank you! :) 

19 minutes ago, Humanate said:

 

Thanks for testing. I am obviously missing something being a noob and all :unsure:

 

I looked at your attached 0.5.9 but I think this is just the release, no config. plist in the attached file

 

Can I check the basics?

 

1. Do I make a plain .txt file called ".contentDetails" and put the name I want in there or do I find an existing file somewhere and modify it?

2. I have tried making a .txt file as above and then mounting my windows drive (within macOS, not Bootcamp though) and placing the .txt file called ".contentDetails" in EFI/Boot, nothing changes

3. I do have Picker Attributes: 1 now, it was set to 0 and Picker Mode is External

 

Yes, that's how it comes out when you build it from sources. You need to replace only certain files. Ok, let's leave that for another time then. :))

 

You need to make a blank file, so not txt, called .contentDetails. The content on that file needs to be the name you want to show up on the boot picker. In my case (attached), I named it "Windows 10 Pro". You can edit this one if you want.

 

To make a blank file, you can use Sublime Text, for example, on MacOS. Or any text editor. But again, it's not a .txt file. It's a blank file. There's no extension on it.

 

So, in Sublime for example, you just go to File -> New File -> enter your custom name in that file -> Save As -> ".contentDetails". 

 

In order to be able to create that hidden file, you need to set hidden files to visible. To do that, easiest way is to press: CMD (or Windows key if you're on a Windows keyboard) + Shift + . (yes, that's the dot symbol on your keyboard). So CMD + SHIFT + .

To disable (make hidden files invisible again), just repeat the same command.

 

Here's the before and after. The file is present in both cases, but one is with hidden files disabled, the other one is with them enabled.

 

1710014908_Screenshot2020-05-23at11_42_25.thumb.png.849bb85eb6d1e63cc6d5f2535f0d8f1e.png

 

 

Screenshot 2020-05-23 at 11.42.44.png

 

.contentDetails

Edited by arsradu
1 minute ago, eSaF said:

 

Hmmmm - A wealth of information ....... 'She canna take anymore captain she'll blow I tell yah, she'll blow' - nice one AG :thumbsup_anim:


:startreck:

 

I picked up my sample Z490 Master yesterday. Woooaaahhhhh it’s a lovely board Mr eSaF,

I have no intention of buying a 10900k though, if I get one for free as well then I won’t complain but my 9900k is a good enough furnace for me to keep my warm toastie.. :hysterical:

  • Like 2
7 minutes ago, eSaF said:

AG your post sent a second wave of thought through me - A Z490?, man that thing coupled with a 10900k would smoke OC all day long!!!!!


Yes and it would smoke your kippers and your toast and cook your beans too.

Them cpus are juicy hot. :fiery:

:hysterical:

im very interested to see how it performs under Catalina though via OC.
Bring on the compatibility and let’s find out!  

27 minutes ago, arsradu said:

 

Yes, that's how it comes out when you build it from sources. You need to replace only certain files. Ok, let's leave that for another time then. :))

 

You need to make a blank file, so not txt, called .contentDetails. The content on that file needs to be the name you want to show up on the boot picker. In my case (attached), I named it "Windows 10 Pro". You can edit this one if you want.

 

To make a blank file, you can use Sublime Text, for example, on MacOS. Or any text editor. But again, it's not a .txt file. It's a blank file. There's no extension on it.

 

So, in Sublime for example, you just go to File -> New File -> enter your custom name in that file -> Save As -> ".contentDetails". 

 

In order to be able to create that hidden file, you need to set hidden files to visible. To do that, easiest way is to press: CMD (or Windows key if you're on a Windows keyboard) + Shift + . (yes, that's the dot symbol on your keyboard). So CMD + SHIFT + .

To disable (make hidden files invisible again), just repeat the same command.

 

Here's the before and after. The file is present in both cases, but one is with hidden files disabled, the other one is with them enabled.

.contentDetails

 

Easy when you know how! I tried several times and still not working, then realised your file, attached, was downloaded to my desktop as "contentDetails" and not ".contentDetails" - when I added the all important "." to make it a hidden file it works perfectly. Thank you so much for helping me fix this niggle. Still have much to learn with OC!

  • Like 2
4 minutes ago, Humanate said:

 

Easy when you know how! I tried several times and still not working, then realised your file, attached, was downloaded to my desktop as "contentDetails" and not ".contentDetails" - when I added the all important "." to make it a hidden file it works perfectly. Thank you so much for helping me fix this niggle. Still have much to learn with OC!

 

Yep, that "." is what makes it hidden. 

 

Happy to help! That's why we're here. :) And if you think I'm any less of a noob, you're wrong. I'm learning new things about OC every day. And make mistakes every day. So don't worry. We both learned something new today. Since, as I told you before, I actually never needed to rename anything on my drives. So haven't personally tested this. But now I did, so I could help you get yours fixed, as well. :) So...it's a win-win.

 

Cheers!

Edited by arsradu
  • Thanks 1
34 minutes ago, AudioGod said:

Is there any Ryzen 3000 OpenCore users on this thread by any chance that can share there thoughts on there build without being a AMD troll about it?

Well, there is no trolling... while it runs "fine" for many people (by their personal definition of "fine" I suppose), you have all sorts of limitations, including power management, DRM, app compatibility, virtualisation compatibility, delayed updates and so on.

 

@MacNB HideSelf now works by detecting the OC boot file and discarding that entry, it does no longer refer to the source paritition specifically.

  • Thanks 1
17 minutes ago, Download-Fritz said:

Well, there is no trolling... while it runs "fine" for many people (by their personal definition of "fine" I suppose), you have all sorts of limitations, including power management, DRM, app compatibility, virtualisation compatibility, delayed updates and so on.


That’s what I found the last time I tried it for myself too. I was hoping things may of got better but I guess no real Apple support is always going to make things difficult really.

I think Apple are missing a trick if they don’t start using the upcoming 4000 series, I know they have there ARM aspirations but still it makes so much more sense for Apple to use the upcoming lineup,

I think it would be win win for everybody. One can only hope. :) 

Still quite new to OC, couple questions

 

1. I notice that it takes a lot longer for the OC OpenCanopy boot picker to appear when my rig starts up - the time taken to go from the American Megatrends message to the boot picker. Clover was much quicker in this regard. Is there anything I can do to speed this up?

 

2. Catalina 10.15.4 seems to take a long time to load. I have fast m.2 nvme SSD system drives for macOs and Windows, the latter loads much more quickly than Catalina. Is this just something I have to accept or is there anything I can do to optimise/speed up. I was expecting faster load times with nvme....

 

I'm using OC 0.5.8 at the moment, let me know if attaching files will help

9 minutes ago, Humanate said:

Still quite new to OC, couple questions

 

1. I notice that it takes a lot longer for the OC OpenCanopy boot picker to appear when my rig starts up - the time taken to go from the American Megatrends message to the boot picker. Clover was much quicker in this regard. Is there anything I can do to speed this up?

 

2. Catalina 10.15.4 seems to take a long time to load. I have fast m.2 nvme SSD system drives for macOs and Windows, the latter loads much more quickly than Catalina. Is this just something I have to accept or is there anything I can do to optimise/speed up. I was expecting faster load times with nvme....

 

I'm using OC 0.5.8 at the moment, let me know if attaching files will help

 

I have noticed this as well for OC 0.5.8. There's a 3-5 sec delay from OEM logo to bootpicker.

And fyi and I didn't really have this much delay with OC 0.5.5-7.

46 minutes ago, Humanate said:

Still quite new to OC, couple questions

 

1. I notice that it takes a lot longer for the OC OpenCanopy boot picker to appear when my rig starts up - the time taken to go from the American Megatrends message to the boot picker. Clover was much quicker in this regard. Is there anything I can do to speed this up?

 

2. Catalina 10.15.4 seems to take a long time to load. I have fast m.2 nvme SSD system drives for macOs and Windows, the latter loads much more quickly than Catalina. Is this just something I have to accept or is there anything I can do to optimise/speed up. I was expecting faster load times with nvme....

 

I'm using OC 0.5.8 at the moment, let me know if attaching files will help

 

Do you have boot chime set up, as well? What about Clover? Did you have boot chime set up with that one?

 

Something I've learned on my own is that the boot time (after you select your boot drive), can increase a lot if you have your iGPU set up in BIOS. So for example if you have your graphics set to dedicated (PEG in my case) + multi-monitor support turned ON, and you have your ig-platform-id set to something other than a "headless" connection, that can increase your boot time a LOT. In my tests (and I'm not using NVMe but I am using a SATA SSD), the difference was about 15 seconds. Which is a lot.

 

Whether or not this can be improved on... I don't know. I'm hoping it can... But since we're talking about a pretty old machine (in my case), I'm not expecting too much.

 

So, what you can try is two things:

1. try without boot chime

2. try without iGPU in BIOS.

 

Also, try to reset NVRAM.

 

You can also boot in verbose mode (boot-args = -v added to 7C436110-AB2A-4BBB-A880-FE41995C9F82 in NVRAM) and see where is it hanging. But...in my tests, that wasn't really conclusive. One thing you can try is what i did. Which is to disable all kexts that are not mandatory for booting (so, probably all except Lilu + WEG + VirtualSMC) and see what kind of results you get.

Edited by arsradu
On 4/26/2019 at 6:23 AM, FredWst said:

 

https://github.com/acidanthera/OpenCorePkg/tree/master/Docs

 

Using on H97Wifi (iMac15,1), Optiplex 7050(iMac18,3), Optiplex 3050(iMac18,1 or Mac mini 8,1).

 

Works fine.

 

Fred

Fred, I have an OptiPlex 7040 (HD530, GT730) and unable to boot using the most recent open core. The clover it booting well. Would you mind sharing your config? Thanks

IMG_5295.jpg

1 hour ago, arsradu said:

 

Do you have boot chime set up, as well? What about Clover? Did you have boot chime set up with that one?

 

Something I've learned on my own is that the boot time (after you select your boot drive), can increase a lot if you have your iGPU set up in BIOS. So for example if you have your graphics set to dedicated (PEG in my case) + multi-monitor support turned ON, and you have your ig-platform-id set to something other than a "headless" connection, that can increase your boot time a LOT. In my tests (and I'm not using NVMe but I am using a SATA SSD), the difference was about 15 seconds. Which is a lot.

 

Whether or not this can be improved on... I don't know. I'm hoping it can... But since we're talking about a pretty old machine (in my case), I'm not expecting too much.

 

So, what you can try is two things:

1. try without boot chime

2. try without iGPU in BIOS.

 

Also, try to reset NVRAM.

 

You can also boot in verbose mode (boot-args = -v added to 7C436110-AB2A-4BBB-A880-FE41995C9F82 in NVRAM) and see where is it hanging. But...in my tests, that wasn't really conclusive. One thing you can try is what i did. Which is to disable all kexts that are not mandatory for booting (so, probably all except Lilu + WEG + VirtualSMC) and see what kind of results you get.

 

I have an i5 9400f so no onboard graphics to disable

 

So I did some experimenting, boot chime was enabled although I wasn't hearing it as I use a USB DAC, removed boot chime, much quicker now from BIOS OEM screen to Boot picker, excellent

 

I also removed all but essential kexts. Also improved boot time. Interestingly, I removed RadeonBoost.kext and ran Basemark GPU Benchmark - my score was 3677 with RadeonBoost and 4185 without, strange

 

One more question then that's it from me for today you'll be pleased to hear! The renaming thing you helped me with works perfectly but I'm now thinking I'll be better, if it's possible, to hide the duplicate Windows 10 drive (my backup clone). Reason is my wife mainly uses Windows for her work, if she clicks on the Win 10 clone it will just cause problems, so if I can hide it in Boot Picker that would be even better. Possible do you know?

 

Really appreciate your help

Edited by Humanate
5 hours ago, arsradu said:

 

Yes, that's how it comes out when you build it from sources. You need to replace only certain files. Ok, let's leave that for another time then. :))

 

You need to make a blank file, so not txt, called .contentDetails. The content on that file needs to be the name you want to show up on the boot picker. In my case (attached), I named it "Windows 10 Pro". You can edit this one if you want.

 

To make a blank file, you can use Sublime Text, for example, on MacOS. Or any text editor. But again, it's not a .txt file. It's a blank file. There's no extension on it.

 

So, in Sublime for example, you just go to File -> New File -> enter your custom name in that file -> Save As -> ".contentDetails". 

 

In order to be able to create that hidden file, you need to set hidden files to visible. To do that, easiest way is to press: CMD (or Windows key if you're on a Windows keyboard) + Shift + . (yes, that's the dot symbol on your keyboard). So CMD + SHIFT + .

To disable (make hidden files invisible again), just repeat the same command.

 

Here's the before and after. The file is present in both cases, but one is with hidden files disabled, the other one is with them enabled.

 

.contentDetails

A single line in Terminal:

echo "NAME" > /Volumes/EFI/EFI/Boot/.contentDetails

Change NAME to whatever you want. In this case "Windows 10 Pro"

Edited by Tiem
Typo
  • Like 1
×
×
  • Create New...