Jump to content
8755 posts in this topic

Recommended Posts

3 minutes ago, vit9696 said:

@Andres ZeroCross, you have Apple in your SMBIOS, thus you have SMC loaded. See:

https://github.com/torvalds/linux/blob/9331b6740f86163908de69f4008e434fe0c27691/drivers/hwmon/applesmc.c#L1238-L1264

This is explicitly prohibited by docs.

 

Rest: ACPI Quirks are documented in docs and given in samples. Those that are not implemented are to be written yourselves. Most likely you do not need them in the first place. And yes, it is just not for you if you cannot read, sorry about it.

 

Thank,, It's looks i need Change Vendor in SMBIOS, or set Automatic = Yes and set Spoofing Vendor :)

Edited by Andres ZeroCross

Thanks Andres-Zerocross for booting Windows (UEFI) fix with OC, it works fine on my mach with Aptio 2.0 firmware and shared EFI. Mach halt (Restart-Shutdown) is normal on my case. I never use Fast Startup nor Hibernate or Sleep with Windows, though I'm not sure... what prevents it on your mach.

Edited by Badruzeus
13 minutes ago, vit9696 said:

Yes, that's most reasonable. Having something like Acidanthera iMac15,1 (Automatic & SpoofVendor) is the recommended way to setup SMBIOS tables.


No log about AppleSMC error now,, just curious about IGPU <-> Brightness Slider in Ubuntu. I didn't use DSDT or SSDT when making a test, but still get Brightness Slider. Trying with MacPro6,1 SMBIOS but still get brighness slider. Try to disable IGPu in BIOS and Brightness slider is dissapeared. I check my OEM ACPI of DSDT and SSDT, there is no PNLF.

And as long as i read Doc, there is no options to inject PNLF (Brightness method) in config.plist. Any clue??? or what should i try?

2 minutes ago, Badruzeus said:

Thanks Andres-Zerocross for booting Windows (UEFI) fix with OC, it works fine on my mach with Aptio 2.0 firmware and shared EFI. Mach halt (Restart-Shutdown) is normal on my case. I never use FasStartup nor Hibernate or Sleep with Windows, though I'm not sure... what prevents it on your mach.


As far as i know,, 3 people including me get Fail to shutdown (when shutdown getting back to desktop screen). Need more experiment. 

So far the issues did not reproduce for us, but we probably need to be trying harder. Thing is, Windows and Linux may store preferences somewhere, and after being configured with e.g. Apple vendor during boot or installation, some preferences may be irreversible.

 

My opinion is that neither brightness slider, nor shutdown issues can appear when everything is off. In my opinion, disable everything you enabled (including custom ACPI, SMBIOS, device properties, absolutely everything), and try checking Windows and Linux.

— If the bug persists, try loading from BIOS bypassing OpenCore (not Clover please, use BIOS). I believe it will remain here, if it disappears, upload full OC folder, we will try to reinspect.

— If the bug disappears, find the offending preference.

 

Ensure that you carefully and consistently test the configuration. Also it may be reasonable to retest with your and fresh Linux installation.

  • Like 1
8 hours ago, vit9696 said:

So far the issues did not reproduce for us, but we probably need to be trying harder. Thing is, Windows and Linux may store preferences somewhere, and after being configured with e.g. Apple vendor during boot or installation, some preferences may be irreversible.

 

My opinion is that neither brightness slider, nor shutdown issues can appear when everything is off. In my opinion, disable everything you enabled (including custom ACPI, SMBIOS, device properties, absolutely everything), and try checking Windows and Linux.

— If the bug persists, try loading from BIOS bypassing OpenCore (not Clover please, use BIOS). I believe it will remain here, if it disappears, upload full OC folder, we will try to reinspect.

— If the bug disappears, find the offending preference.

 

Ensure that you carefully and consistently test the configuration. Also it may be reasonable to retest with your and fresh Linux installation.

Many thanks :D

At last, my Windows can sleep, restart and shutdown now :D

The problem is :
==============

RequestBootVarRouting
Type: plist boolean
Failsafe: false
Description: Request NVRAM driver (or AptioMemoryFix) to redirect Boot prefixed variables from EFI_GLOBAL_VARIABLE_G to OC_VENDOR_VARIABLE_GUID.

This will set special boot-redirect variable, which a compatible driver will abide after booter start. The quirk lets default boot entry preservation at times when firmwares delete incompatible boot entries.

============

I set it YES before, i set NO for now and my probelm solved. Now, i will check Linux for Brightness Slider :D

Edited by Andres ZeroCross
On 5/17/2019 at 4:33 AM, Rodion2010 said:

boot 3.zip

here is my boot file

1 no HFS+ embedded, you may use external drivers Apple's HFSPlus or VboxHFs 

2 default path changed from EFI\CLOVER\Clonerx64 back to EFI\Boot\Bootx64.efi

 

Install Clover

remove all the files and copy OC to the same device

 

 

@Rodion2010,

 

Could you please compile boot file with default path EFI\OC\OpenCore.efi instead of EFI\Boot\Bootx64.efi?

 

I have Clover installed in more than one hard drive on my legacy desktop and unless I disabled/renamed all other instances of CLOVERX64.efi on all my hard drives (installed as EFI\BOOT\BOOTX64.efi), the CLOVER GUI would load instead of OC...

 

 

Spoiler

557994533_DisabledCLOVERX64_efiBOOTX64_efi.thumb.png.ada5c0d62747473d9bb8a610ce7fb427.png 

 

This is mainly a problem if you want OC loading off a hard drive EFI instead of a USB EFI on a legacy BIOS system ---> boot file seems to load OC on USB EFI more reliably.  The boot file (when installed to hard drive EFI) looks for \EFI\BOOT\BOOTX64.efi on all other hard drive EFIs, not just the one it is actually on.

 

Also requesting if you can supply an OC boot file based on boot7 instead of boot6 (because on some legacy BIOS systems, boot7 significantly reduces boot time).

 

Thanks

 

Edit

@RodionS has already compiled a number of different duet boot files for legacy BIOS systems in the Applelife forum - link post#176.  His boot_BIOS_BlockIO solves the problem I described above :guitar:

Edited by fusion71au
Link to @RodionS's duet boot files for legacy BIOS booting
  • Like 1
5 hours ago, Andres ZeroCross said:

At last, my Windows can sleep, restart and shutdown now :D

The problem is :
==============

RequestBootVarRouting

I set it YES, i set NO and now it solved. Now, i will check Linux for Brightness Slider :D

Weird yah, on my case I set "RequestBootVarRouting" to "YES" and having no problem with mach halt under Windows. Could be specific issue on diff firmware version?

Screenshot 5.png

Edited by Badruzeus

Oho, this is really bad. This one is not supposed to be broken. Could you please dump NVRAM variables in EFI_GLOBAL_VARIABLE_GUID (see Configuration.pdf for GUID) via dmpstore from Shell or something. Make sure you have RequestBootVarRouting set to NO at the dump time.

20 minutes ago, vit9696 said:

Oho, this is really bad. This one is not supposed to be broken. Could you please dump NVRAM variables in EFI_GLOBAL_VARIABLE_GUID (see Configuration.pdf for GUID) via dmpstore from Shell or something. Make sure you have RequestBootVarRouting set to NO at the dump time.


I will upload ASAP, for my current config.plist (best setup in UBUNTU, Windows and macOS) i have set RequestBootVarRouting set to NO. 

Edited by Andres ZeroCross
1 hour ago, vit9696 said:

Oho, this is really bad. This one is not supposed to be broken. Could you please dump NVRAM variables in EFI_GLOBAL_VARIABLE_GUID (see Configuration.pdf for GUID) via dmpstore from Shell or something. Make sure you have RequestBootVarRouting set to NO at the dump time.


Sorry for waiting,, 

i use openCore Shell,, and make entry of shell in OC. then i boot to it

I type 
====
dmpstore 8BE4DF61-93CA-11D2-AA0D-00E098032B8C
====
Then i get output about "no variable name", then i tried to
====

dmpstore -all
====

Then i got many log in Shell,, then i tried to dump all to file, i type

====
dmpstore -all > nvram.txt

====
And i got output about invalid parameter, and can't redirect bla bla bla.

How to dump into txt file???  with shell of Clover i can do it with "dmpstore -all > blablabla.txt" 

Just now, vit9696 said:

You probably forgot to choose a writeable filesystem. Try typing fs0: and pressing enter. 0 can be other disk.

OMG,, you're right. I didn't choose writeable file system. Rebooting now

5 minutes ago, vit9696 said:

You probably forgot to choose a writeable filesystem. Try typing fs0: and pressing enter. 0 can be other disk.

I got error about no variable name match with "dmpstore 8BE4DF61-93CA-11D2-AA0D-00E098032B8C"

so i use command "dmpstore -all > nvramall.txt"


I attached the nvramall.txt

nvramall.txt

Well, with OC I previously made a mistake on config.plist and I correct it via OpenCoreShell. Once rebooted it won't be boot bcoz I set Require Vault: Yes. I then reaccess it via Shell to "No". And now it says "config corrupted" hmmb.. So, I can only repair it via a running mac, or.. is vault generator script also run-able on linux or Shell? Thanks.

Edited by Badruzeus
23 minutes ago, Badruzeus said:

Well, with OC I previously made a mistake on config.plist and I correct it via OpenCoreShell. Once rebooted it won't be boot bcoz I set Require Vault: Yes. I then reaccess it via Shell to "No". And now it says "config corrupted" hmmb.. So, I can only repair it via a running mac, or.. is vault generator script also run-able on linux or Shell? Thanks.

Maybe itu should "NO" not No,, i try edit with nano then the value should be <false/> or <true/>. Maybe CaseSensitive

Edited by Andres ZeroCross
12 minutes ago, Andres ZeroCross said:

Maybe itu should "NO" not No,, i try edit with nano then the value should be <false/> or <true/>. Maybe CaseSensitive

Yeah, with xml it shown as true or false. So, on OpenCore Shell I

fs0:

cd efi\oc

edit config.plist

set it to <false/>

F3 [Enter] to Save

reset

Hi folks,

 

Just been trying the latest OC build and Drivers etc and noticed I can't boot if the Picker is enabled, with the settings below it boots fine straight into macOS but if I enable ShowPicker I get the error below.

 

28977925_Screenshot2019-06-22at15_04_37.png.ec474b01c0519a0babefc800d63263a3.png

 

546166530_Screenshot2019-06-22at15_05_16.thumb.png.0479bce4a8b21064aaef46974e473f2a.png

 

Is this still related to the possible bug mentioned a few pages ago?

7 minutes ago, D-an-W said:

Hi folks,

 

Just been trying the latest OC build and Drivers etc and noticed I can't boot if the Picker is enabled, with the settings below it boots fine straight into macOS but if I enable ShowPicker I get the error below.

 

28977925_Screenshot2019-06-22at15_04_37.png.ec474b01c0519a0babefc800d63263a3.png

 

546166530_Screenshot2019-06-22at15_05_16.thumb.png.0479bce4a8b21064aaef46974e473f2a.png

 

Is this still related to the possible bug mentioned a few pages ago?


it's not bug, you have wrong configurations about Lilu.kext. Make sure you have Lilu.kext in your EFI/OC/Kexts. How about set ShowPicker = YES??

Edited by Andres ZeroCross
×
×
  • Create New...