OpenCore General Discussion

[markl18]

Hi I get this hang it doesn’t kp just

[Synapsis]

On 5/19/2020 at 3:35 AM, markl18 said:

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

 

you can assign it, either as a device (for .img files) by adding

-device if=virtio,format=raw,file=/path/to/device 
-device if=ide,format=raw,file=/path/to/image,id=someId

... or simply with

-cdrom /path/to/iso

Qemu has some very good docs, read those first. It covers a lot and there are examples.

You can find a lot in other places.

 

Windows is a {censored} - so for virtio to work you must (!?!) a virtual driver made by redhat or

use if=ide instead of if=virtio, go with if=ide if you dont plan a long-term VM use otherwise download the iso with drivers

from fedora: 'google virtio drivers win10 iso'

 

---

 

Dude, you need to clean that screen... gross!

4 minutes ago, markl18 said:

Hi I get this hang it doesn’t kp just

Dude, you need to clean that screen... gross!

Edited May 20, 2020 by Synapsis

[insanefrancis]

1 hour ago, MacNB said:

 

Catalina is on separate NVMe drive and yes it's on the first partition.

Mojave is on separate SSD drive and it's the only partition.

Widows is on yet another SSD and it's effectively the first partition followed by High Sierra.

 

I think you are right in that OC can't really boot Windows and seems to default to the NVMe drive (with Catalina).

 

I love the OC documentation, but the description of the new DeduplicateBootOrder is not super clear to me.

 

 

Thanks for the tip.

I had AdviseWindows = NO in 0.5.8 it worked fine.

But I tried setting AdviseWindows = Yes in the current 0.5.9 and it made no difference.

 

I can boot Windows but only via boot picker - not via Startup Disk selection.

 

Something in 0.5.9 has changed for me.

Need to go back to 0.5.8 and try again.

 

UPDATE: reverting back to 0.5.8 and all is working - switching between macOS and Windows via Startup disk and Windows Bootcamp control panel. Hmmmm

 

 

 

This bit from the docs is interesting.

Quote

2. AdviseWindows Type: plist boolean Failsafe: false Description: Forces Windows support in FirmwareFeatures. Added bits to FirmwareFeatures:

 

• FW_FEATURE_SUPPORTS_CSM_LEGACY_MODE (0x1) - Without this bit it is not possible to reboot to Windows installed on a drive with EFI partition being not the first partition on the disk.

• FW_FEATURE_SUPPORTS_UEFI_WINDOWS_BOOT (0x20000000) - Without this bit it is not possible to reboot to Windows installed on a drive with EFI partition being the first partition on the disk.

 

 

[arsradu]

3 minutes ago, markl18 said:

Hi I get this hang it doesn’t kp just

 

 

That's funny... :)) Cause I was literally talking about this a few posts above. In a whole another context though. But yeah. I'm guessing you probably need to fix your graphics.

 

So I would recommend taking a look at Intel Framebuffer patching and, in case you haven't already, while you're at it, add Lilu + WhateverGreen kexts to your /Kexts folder inside OC.

 

[markl18]

1 minute ago, arsradu said:

 

 

That's funny... :)) Cause I was literally talking about this a few posts above. In a whole another context though. But yeah. I'm guessing you probably need to fix your graphics.

 

So I would recommend taking a look at Intel Framebuffer patching and, in case you haven't already, while you're at it, add Lilu + WhateverGreen kexts to your /Kexts folder inside OC.

 

Believe me those are the first once’s I put in now as far my graphics are concerned I need some serious help it’s oldy hd4400 if any one has any pointers I will take what I can get

[arsradu]

34 minutes ago, markl18 said:

Believe me those are the first once’s I put in now as far my graphics are concerned I need some serious help it’s oldy hd4400 if any one has any pointers I will take what I can get

 

Well you're in luck. Cause I'm using a Haswell CPU (as you can probably tell from my signature). It's a Desktop CPU though, so things might be different for you. But...I think I could help.

 

So, for HD4400 (just like the HD4600 I'm using), you need to take a look at the ig-platform-id values posted here. How do you choose you ask? Simple. You try the default/recommended ones first. Then, if it doesn't work, you try some of the other ones. In your case, you should take a look at the ones marked with "mobile".

 

"Recommended framebuffers : for desktop - 0x0D220003 (default); for laptop - 0x0A160000 (default), 0x0A260005 (recommended), 0x0A260006 (recommended); "empty framebuffer" - 0x04120004 (default)."

 

So. For example, you can try 0x0A260005 or 0x0A260006.

 

How?

 

Simple. In your OC config.plist, you go to Device Properties, select your iGPU PCI address (obviously, this requires another machine, since you can't boot off of your laptop right now) and add, with reversed bytes:

 

either 0500260A OR 0600260A.

 

For example: if your PCI address is PciRoot(0x0)/Pci(0x2,0x0) you will add it like this:

 

DeviceProperties

  Add

     PciRoot(0x0)/Pci(0x2,0x0)

       AAPL,ig-platform-id (the key) = 0500260A (the value)

       Class should be Data.

 

Should look something like this (you can ignore the #AAPL,ig-platform-id up top; that's for headless connection and it's also disabled). And obviously, that value is for my iGPU.   So you need to replace it with yours.

 

 

 

Save the config. And try to boot again.

Edited May 20, 2020 by arsradu

[makk]

8 hours ago, vit9696 said:

@makk, sorry if that was unclear. I meant you can edit Info.plist of VoodooPS2-related kexts. Like this: https://github.com/acidanthera/VoodooPS2/commit/535e81517355d1b6d2aaaaf24e6972de15006265

 

thank you Vit

 

Will give this a shot. In the ApplePS2SmartTouchPad.kext & and AsusNBFnKeys.kext

 

For the VoodooPS2Controller, to get it to recognize CAP lock, NUMlock, other FN keys, I had a problem.  The TouchPad worked and Mouse, and Keyboard. 

 

Tried out the AsusSMC.kext and loaded the daemon.  How to unload the daemon without destruction?

 

 

[arsradu]

@markl18 I would highly recommend going through this tutorial. It's really well done. And perfect for getting you up and running.

[MacNB]

1 hour ago, insanefrancis said:

 

This bit from the docs is interesting.

 

 

 

Yes Thanks I read that and set AdviseWindows=YES but does not solve the problem.

[Tiem]

Updating to the latest Catalina beta 5 I got this:

OCUI: Entry kind 16 unsupported for IconOCB: ShowMenu failed - Unsupported
Halting on critical error

Restarted the install process and it completed the second time no issues. Using OC 0.5.9 build e7989ef

 

[arsradu]

5 minutes ago, eSaF said:

Hey guys an update on my Boot-Chime woes. It turns out that the Boot-chime was there all along but for some reason the signal from the sound card was at the headphone jack and then would switch to speaker port at the back of the case once it reaches the desktop. I would like to thank arsradu and vit9696 for all the suggestions but the big Hero of the day is the man himself Audiogod, quite an apt title. His suggestion was spot on - Change your audio output to a value until you get Boot-Chime at startup and that was the answer 

 

Awesome! Glad you managed to fix it! I think I also mentioned the Audio Out thingy in my reply.  So which value did it work for you after all?

[arsradu]

7 minutes ago, eSaF said:

 

A big fat ZERO 

LOOOOOOLLL!!!!! :))) That's good to know! Anyway, I'm really happy you managed to fix it! It's been a pleasure talking to you, man! Really. I love talking to people like you. And I'm really glad I could help (even if it wasn't really much at all).

 

Now you can sleep well tonight. And not on the rug outside the door. :))

Edited May 20, 2020 by arsradu

[arsradu]

Just now, eSaF said:

Hey how did you know about the rug thing - you been talking to my wife?  Yea it was a little stressful as I hate to know something is beating me, but alls well that ends well 

 

I just know my girlfriend would do the same. :)) So, I totally understand what you're going through, man. And yeah, I'm the same. I don't like it when things don't make sense.

 

Anyway, enjoy!  

[insanefrancis]

2 hours ago, MacNB said:

 

Yes Thanks I read that and set AdviseWindows=YES but does not solve the problem.

 

Yeah but the what do you think about the 2 bullet points there? Does it mean that when I set AdviseWindows=YES then it conditionally handles the two points? Because the first point is applicable to me, while the second are applicable to others like @arsradu. Or there's something to do besides setting it to YES.

[MacNB]

18 minutes ago, insanefrancis said:

 

Yeah but the what do you think about the 2 bullet points there? Does it mean that when I set AdviseWindows=YES then it conditionally handles the two points? Because the first point is applicable to me, while the second are applicable to others like @arsradu. Or there's something to do besides setting it to YES.

 

Yes that's what I believe happens. That is, Setting AdviceWindows = YES, sets those TWO bits in the FirmwareFeatures variable.

That variable is stored in the Platforminfo->PlatformNVRAM.

 

So it could help you.

[arsradu]

1 hour ago, insanefrancis said:

 

Yeah but the what do you think about the 2 bullet points there? Does it mean that when I set AdviseWindows=YES then it conditionally handles the two points? Because the first point is applicable to me, while the second are applicable to others like @arsradu. Or there's something to do besides setting it to YES.

 

Sorry, been busy updating to build 19F94a.  All good, by the way.

 

So..yeah. This is a bit confusing. Cause mine is set to AdviseWindows=NO (so..that would be boolean false). EFI partition is the first one. Obviously UEFI boot. And it's booting perfectly fine between BootCamp Windows and MacOS.

I was reading the documentation, as well, and I think it does that when it's set to true. Failsafe (default) is false though.

 

Now, if these FirmwareFeatures are the same ones as the ones in SMBIOS and PlatformNVRAM, I already have mine set to 37E10FE0 00000000. So...whether that's already good enough or not, I don't know. Never really understood what they do. But it sounds like it's adding both, for both cases (Legacy and UEFI boot).

 

By the way, about the updates, I absolutely love how seamless it is to update MacOS with OC. It always goes to the installer, it always selects the correct partition to boot from. Awesome! You really don't need to touch anything. You set it to update and come back when it's done.

Edited May 20, 2020 by arsradu

[MacNB]

I found a workaround to my issue with OC 0.5.9 booting Windows via System Preferences Startup Disk option. In OC 0.5.8 it worked fine but updating to 0.5.9 broke this - it would restart the system and boot the first macOS disk instead of windows.

 

I had a custom entry in Misc->Entries:

 

<key>Entries</key>
		<array>
			<dict>
				<key>Arguments</key>
				<string></string>
				<key>Auxiliary</key>
				<false/>
				<key>Comment</key>
				<string>Not signed for security reasons</string>
				<key>Enabled</key>
				<false/>
				<key>Name</key>
				<string>Windows 10 Pro</string>
				<key>Path</key>
				<string>PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0xFFFF,0x0)/HD(1,GPT,A4CE4F1A-43C6-492D-BB16-2DD6EABCE4EF,0x28,0x64000)/\EFI\Microsoft\Boot\bootmgfw.efi</string>
			</dict>
		</array>

 

...so that I could customise the name displayed in the boot Picker to "Windows 10 Pro".

 

In 0.5.8, this entry was always selected on restart.

But in 0.5.9, it's is ignored.

 

Workaround:

Disable the Misc->Entries ->0

Added the Misc->BlessOverride->0-> \EFI\Microsoft\Boot\bootmgfw.efi

 

Now OC 0.5.9 boots Windows from System Preferences Startup Disk.

 

I say this is a workaround since it's not what I wanted to happen. I wanted a custom entry so that I can label the drive name that's display on boot picker.

 

Edited May 20, 2020 by MacNB

[makk]

12 hours ago, vit9696 said:

@makk, sorry if that was unclear. I meant you can edit Info.plist of VoodooPS2-related kexts. Like this: https://github.com/acidanthera/VoodooPS2/commit/535e81517355d1b6d2aaaaf24e6972de15006265

 

The highlights in Red = delete?  

 

 

00:000 00:000 Dependency com.apple.iokit.IOHIDSystem fallback to com.apple.iokit.IOHIDFamily succeeded. Please fix your kext!
00:034 00:034 Dependency com.apple.iokit.IOHIDSystem fallback to com.apple.iokit.IOHIDFamily succeeded. Please fix your kext!
00:105 00:070 OC: Prelink injection TSCAdjustReset.kext () - Invalid Parameter
00:114 00:008 Dependency com.apple.iokit.IOHIDSystem fallback to com.apple.iokit.IOHIDFamily succeeded. Please fix your kext!

 

Thanks Vit

[makk]

Adjusting the brightness on a laptop

Method 1
Enable Clover DSDT fix AddPNLF.

 

1--Enable SetIntelBacklight and SetIntelMaxBacklight. A specific value is not necessary - it will be automatically injected according to the processor installed.

 

2--Method 2<< inserted this on boot, but when in logging in, does not stay max.  It is quite dimmer than with Clover.

Use this ACPI table: SSDT-PNLF.dsl SSDT-PNLF.aml, for CFL+ use other table SSDT-PNLFCFL.aml. without this though it is much dimmer.

 

Seeing this is written for Clover, where does one insert this in OC for Method 1--?

what is the equivalent for OC config.plist?

 

 

[arsradu]

19 minutes ago, makk said:

Adjusting the brightness on a laptop

Method 1
Enable Clover DSDT fix AddPNLF.

 

1--Enable SetIntelBacklight and SetIntelMaxBacklight. A specific value is not necessary - it will be automatically injected according to the processor installed.

 

2--Method 2<< inserted this on boot, but when in logging in, does not stay max.  It is quite dimmer than with Clover.

Use this ACPI table: SSDT-PNLF.dsl SSDT-PNLF.aml, for CFL+ use other table SSDT-PNLFCFL.aml. without this though it is much dimmer.

 

Seeing this is written for Clover, where does one insert this in OC for Method 1--?

what is the equivalent for OC config.plist?

 

More about config conversion from Clover to OC here.

More about fixing backlight on laptops with OC here.

For everything else, you can check out this page.

Also, for Laptop OC guides, you can check out this page.

Edited May 20, 2020 by arsradu

[makk]

2 minutes ago, arsradu said:

 

More about config conversion from Clover to OC here.

More about fixing backlight on laptops with OC here.

For everything else, you can check out this page.

 

Danke' arsradu

[makk]

All I need now is to fix the IOHIDFamily complaint

keyboard to work in Picker

 

FN keys to work with VoodooPS2 Controller and some SSDT fixes.  

buggy hacked DSDT to max.  also not understanding of MacOs so there is a lot of unneeded in DSDT. 

Not sure of how to edit sloppy at this.

 

Speed up graphics in Desktop mode.  << when I first booted OpenCore with .5.8 it was super fast.

then I messed with Security Vault and couldn't fix the problem so I deleted all.  darn shame.

 

The other issue is USB2.0.  does not have 3.0 speeds. 

So all these patches and so forth does not work.  Stuck with LegacyUSB.kex

 

 

 

Edited May 20, 2020 by makk

[MacNB]

1 hour ago, arsradu said:

By the way, about the updates, I absolutely love how seamless it is to update MacOS with OC. It always goes to the installer, it always selects the correct partition to boot from. Awesome! You really don't need to touch anything. You set it to update and come back when it's done.

 

Yes I agree. Way better than Clover was able to do on my system (and I have a working NVRAM).

It's specially works well while windows updates takes place where it restarts multiple times.

As you say awesome.

 

[mhaeuser]

@MacNB I think your boot entry "issue" is "by design" with the newly introduced boot policy. BlessOverride at all times was the prefered way to add options, custom entries are more or less only for the case of multiple OSes per partition, which is not a thing at all in Apple land. So to say, an extension of ours to what Apple gave us to work with. To rename an option, you can just use the .contenDetails file as described in the PDF fine with no need for a custom entry.

[insanefrancis]

On 5/19/2020 at 10:59 PM, insanefrancis said:

 

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.

 

UPDATE:

Sure enough the solution is on the Docs, set AdviseWindows=YES