OpenCore General Discussion

[vit9696]

@Mike Ranger, without keepsyms=1 it is a bit hard to say definitely, but it looks like you have APFS filesystem failure. On the root volume I guess.

[Mike Ranger]

Hi Vit

I can still boot using the previous version (0.5.8)....

Will enable keepsyms=1 and take a shot.

let's see

 

Thanks, Mike

 

 

Update:

Removing NvmeFix did the trick... booting fine again..... 

So currently NvmeFix prevents me from booting and seems to cause kernel panic.

 

 

Edited June 2, 2020 by Mike Ranger

[Paksman]

9 minutes ago, Mike Ranger said:

Hi Vit

I can still boot using the previous version (0.5.8)....

Will enable keepsyms=1 and take a shot.

let's see

 

Thanks, Mike

 

 

Update:

Removing NvmeFix did the trick... booting fine again..... 

So currently NvmeFix prevents me from booting and seems to cause kernel panic.

 

 

Did you compile NVMeFix.kext from latest source ? I also had KP after commit https://github.com/acidanthera/NVMeFix/commit/009a13233f04484907dcac348bd6bfe1ee1db2a0

[Mike Ranger]

 I compiled it today... so yes... if I did not do a copy mistake it was from latest source.

 

Best, Mike

[pitrysha]

@vit9696

 

look this is not a table of masks?

Found on the Internet

CPUID_table.png.zip

[vit9696]

@pitrysha, 

 

Use https://www.intel.com/content/dam/www/public/us/en/security-advisory/documents/sa00329-microcode-update-guidance.pdf

or http://www.cpu-world.com (CPUID signature fiend).

 

It will be great if you could make & maintain the table, as we also do not have one.

[pitrysha]

11 minutes ago, vit9696 said:

@pitrysha, 

 

Use https://www.intel.com/content/dam/www/public/us/en/security-advisory/documents/sa00329-microcode-update-guidance.pdf

or http://www.cpu-world.com (CPUID signature fiend).

 

It will be great if you could make & maintain the table, as we also do not have one.

I can’t handle it, knowledge is not enough. I take advantage of the fact that I find on the Internet.

[MacNB]

15 hours ago, SavageAUS said:

Also how does the new CrScreenshotDxe.efi work? Do we press a "F" key to get screenshot?

 

Press F10 and OC will save a PNG on the root of the ESP from where it booted.

 

From Page 55 of Configuration.pdf:

"CrScreenshotDxe* Screenshot making driver saving images to the root of OpenCore partition (ESP) or any avail- able writeable filesystem upon pressing F10. This is a modified version of CrScreenshotDxe driver by Nikolaj Schlej."

 

 

[el_charlie]

7 hours ago, tluck said:

 

 

i have HD3000 and before Whatevergreen.kext, used a variety of methods to get backlight. the rehabman SSDT-PNLF method still works. But i can also revert to basic PNLF definition and get the same result. 

 

                Device (PNLF)
                {
                    Name (_ADR, Zero)  // _ADR: Address
                    Name (_HID, EisaId ("APP0002"))  // _HID: Hardware ID
                    Name (_CID, "backlight")  // _CID: Compatible ID
                    Name (_UID, 14)  // _UID: Unique ID
                    Name (_STA, 0x0B)  // _STA: Status
                }
 

so PNLF above + Whatevergreen = backlight

 

and in ioreg -l 

 

1808 = 0x710 and all is good.

    | +-o PNLF@0  <class IOACPIPlatformDevice, id 0x10000015b, registered, matched, active, busy 0 (39 ms), retain 9>

    | | | {

    | | |   "compatible" = <"backlight">

    | | |   "AppleBacklightAtBoot" = 4436

    | | |   "AppleMaxBrightness" = 1808

    | | |   "_UID" = "14"

    | | |   "device-properties" = {"acpi-device"="IOACPIPlatformDevice is not serializable","acpi-path"="IOACPIPlane:/_SB/PCI0@0/IGPU@20000/PNLF@0"}

    | | |   "ApplePanelRawBrightness" = 1808

    | | |   "_STA" = 11

    | | |   "_ADR" = 0

    | | |   "name" = <"APP0002">

    | | | }

    | | |

    | | +-o AppleIntelPanelA  <class AppleIntelPanelA, id 0x100000352, registered, matched, active, busy 0 (0 ms), retain 6>

    | |     {

    | |       "IOProbeScore" = 2000

    | |       "CFBundleIdentifier" = "com.apple.driver.AppleBacklight"

    | |       "IOMatchCategory" = "IODisplayParameters"

    | |       "IOClass" = "AppleIntelPanelA"

    | |       "IOProviderClass" = "IOACPIPlatformDevice"

    | |       "CFBundleIdentifierKernel" = "com.apple.driver.AppleBacklight"

    | |       "IONameMatch" = "backlight"

    | |       "IONameMatched" = "backlight"

    | |       "IODisplayParameters" = {"commit"={"reg"=0}}

    | |       "ApplePanel" = {"F14Txxxx"=<00110000003400520073009400be00fa0136017201c5022f02b90360041a050a060e0710>}

    | |     }

 

 

He's referring that by using a PLNF device he gets graphic glitches that end up in UI freezes with HD3000. Those freezes didn't happen for him on Sierra, they do happen since High Sierra or Mojave with HS kexts. I experience those glitches on my laptop. I've tried everything.

 

Do you have those errors?

[Paksman]

4 hours ago, Mike Ranger said:

Hi Vit

I can still boot using the previous version (0.5.8)....

Will enable keepsyms=1 and take a shot.

let's see

 

Thanks, Mike

 

 

Update:

Removing NvmeFix did the trick... booting fine again..... 

So currently NvmeFix prevents me from booting and seems to cause kernel panic.

 

 

Should be fixed in master. I compiled new version and no more kernel panic. Thanks to all developers.

[makk]

 

9 hours ago, tluck said:

 

 

i have HD3000 and before Whatevergreen.kext, used a variety of methods to get backlight. the rehabman SSDT-PNLF method still works. But i can also revert to basic PNLF definition and get the same result. 

 

                Device (PNLF)
                {
                    Name (_ADR, Zero)  // _ADR: Address
                    Name (_HID, EisaId ("APP0002"))  // _HID: Hardware ID
                    Name (_CID, "backlight")  // _CID: Compatible ID
                    Name (_UID, 14)  // _UID: Unique ID
                    Name (_STA, 0x0B)  // _STA: Status
                }
 

so PNLF above + Whatevergreen = backlight

 

and in ioreg -l 

 

1808 = 0x710 and all is good.

    | +-o PNLF@0  <class IOACPIPlatformDevice, id 0x10000015b, registered, matched, active, busy 0 (39 ms), retain 9>

    | | | {

    | | |   "compatible" = <"backlight">

    | | |   "AppleBacklightAtBoot" = 4436

    | | |   "AppleMaxBrightness" = 1808

    | | |   "_UID" = "14"

    | | |   "device-properties" = {"acpi-device"="IOACPIPlatformDevice is not serializable","acpi-path"="IOACPIPlane:/_SB/PCI0@0/IGPU@20000/PNLF@0"}

    | | |   "ApplePanelRawBrightness" = 1808

    | | |   "_STA" = 11

    | | |   "_ADR" = 0

    | | |   "name" = <"APP0002">

    | | | }

    | | |

    | | +-o AppleIntelPanelA  <class AppleIntelPanelA, id 0x100000352, registered, matched, active, busy 0 (0 ms), retain 6>

    | |     {

    | |       "IOProbeScore" = 2000

    | |       "CFBundleIdentifier" = "com.apple.driver.AppleBacklight"

    | |       "IOMatchCategory" = "IODisplayParameters"

    | |       "IOClass" = "AppleIntelPanelA"

    | |       "IOProviderClass" = "IOACPIPlatformDevice"

    | |       "CFBundleIdentifierKernel" = "com.apple.driver.AppleBacklight"

    | |       "IONameMatch" = "backlight"

    | |       "IONameMatched" = "backlight"

    | |       "IODisplayParameters" = {"commit"={"reg"=0}}

    | |       "ApplePanel" = {"F14Txxxx"=<00110000003400520073009400be00fa0136017201c5022f02b90360041a050a060e0710>}

    | |     }

 

 

Thanks tluck!

 

Will give it a try.

 

Do you use DeviceProperties? 

Edited June 3, 2020 by makk
silly screen put this in twice

[Tiem]

26 minutes ago, makk said:

Do you use DeviceProperties? 

 

From what I've seen this really does nothing unless you're trying to inject something that is not currently there (like adding a Framebuffer for your GPU). I have most of my devices listed but they actually do nothing as OC will build them automatically anyway.

 

Edit: Here's the description:

 

Add
Type: plist dict
Description: Sets device properties from a map (plist dict) of deivce paths to a map (plist dict) of variable names and their values in plist metadata format. Device paths must be provided in canonic string format (e.g. PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)). Properties will only be set if not present and not deleted.

 

Note: Currently properties may only be (formerly) added by the original driver, so unless a separate driver was installed, there is no reason to delete the variables.

Edited June 3, 2020 by Tiem

[makk]

tluck,

 

with your hd3000, do you get garbage on your screen? and lockups?

 

were you able to install Catalina on hd3000? if so how did you get around the check?

I used, Dosdude patcher for this and error with This Mac is unsupported and stopped.

 

So far I have found that any PNLF statements create corruption in Video because 64 bit constant in a 32 bit table.  It's always PNFL. This Asus Laptop came with a separate FN key ATPK or ATKP driver to handle the calls for FN keys, brightness and so forth.  So without this driver, have a problem with hacked scripts -- SSDT-PNLF, PNLF brightness patches, so forth.  I was getting massive erroring and lockups when using SSDT-PNLF on Mojave and High Sierra.

 

[SavageAUS]

@vit9696 I have played around with different options and i can manage to boot Arch Linux and Windows 10 but i lose macOS booting. Can you or anyone see anything in my config that would prevent macOS from booting.

This is on my laptop, specs in signature.

Testing is done via USB.

config.plist

[makk]

20 minutes ago, Tiem said:

 

From what I've seen this really does nothing unless you're trying to inject something that is not currently there (like adding a Framebuffer for your GPU). I have most of my devices listed but they actually do nothing as OC will build them automatically anyway.

 

Edit: Here's the description:

 

Add
Type: plist dict
Description: Sets device properties from a map (plist dict) of deivce paths to a map (plist dict) of variable names and their values in plist metadata format. Device paths must be provided in canonic string format (e.g. PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)). Properties will only be set if not present and not deleted.

 

Note: Currently properties may only be (formerly) added by the original driver, so unless a separate driver was installed, there is no reason to delete the variables.

Thanks Time, I am using DeviceProperties since before OC which helped a great deal with less typing in config.plist. With DeviceProperties, it is a good because you can directly add into each PCIRoot portion and have it working.  

 

The problem with this laptop it is Sandybridge HD3000.  So the graphics is fine unto Sierra, from High Sierra onwards, getting the ACPI Warning: Truncate message about the PNLF being 64 bit in 32bit table.  No clue as to why. I suspect because the table is 32 bit when it comes to dealing with the backlight Function using the FNkeys.  Probably not 64 bit. this is what I am concluding to because the Asus ATKP or ATPK driver is 32 bit.   and it sits in 32bit table to be called upon.

 

 

 

 

[vodanhbk]

 I have update opencore 0.5.9 and mac 10.15.5 complete.

but i have a debug file on EFI. Some one can check and tell me that error and how to fix that. 

Thank you and best regards !

My PC

main: Z370m D3h

chipset: I7 8700

VGA : Vega 64

SMBIOS : iMac19,1

SSD: Samsung SM961

Thit is my EFI and error 

Quote

00:000 00:000 AAPL: [EB|#LOG:INIT] 2020-06-03T00:53:56
00:011 00:011 AAPL: [EB|#VERSION] boot.efi 422.120.8~3 (Official), built 2020-04-25T13:24:01-0700
00:027 00:015 AAPL: [EB|#BUILD] BUILD-INFO[298]:{"DisplayName":"boot.efi","DisplayVersion":"422.120.8~3","RecordUuid":"7F620F75-9798-4821-B304-A6B586390C25","BuildTime":"2020-04-25T13:24:01-0700","ProjectName":"efiboot","ProductName":"boot.efi","SourceVersion":"422.120.8","BuildVersion":"3","BuildConfiguration":"Release","BuildType":"Official"}
00:064 00:037 AAPL: [EB|#H:IS] 0
00:075 00:011 AAPL: [EB|#WL:MODE] 0
00:086 00:011 AAPL: [EB|#CONFIG:SRC] <default>
00:099 00:012 AAPL: [EB|#CONFIG| 0] boot-save-log : 0x0000000000000002 (0x0000000000000002 < 0xFFFFFFFFFFFFFFFF) <default>
00:118 00:018 AAPL: [EB|#CONFIG| 1] wake-save-log : 0x0000000000000002 (0x0000000000000002 < 0x0000000000000002) <default>
00:137 00:019 AAPL: [EB|#CONFIG| 2] console       : 0x0000000000000001 (0x0000000000000001 < 0x0000000000000001) <default>
00:157 00:019 AAPL: [EB|#CONFIG| 3] serial        : 0x0000000000000000 (0x0000000000000000 < 0x0000000000000000) <default>
00:177 00:020 AAPL: [EB|#CONFIG| 4] embed-log-dt  : 0x0000000000000000 (0x0000000000000000 < 0x0000000000000000) <default>
00:198 00:020 AAPL: [EB|#CONFIG| 5] timestamps    : 0x0000000000000000 (0x0000000000000000 < 0xFFFFFFFFFFFFFFFF) <default>
00:219 00:021 AAPL: [EB|#CONFIG| 6] log-level     : 0x0000000000000001 (0x0000000000000001 & 0x0000000000000001) <default>
00:240 00:021 AAPL: [EB|#CONFIG| 7] breakpoint    : 0x0000000000000000 (0x0000000000000000 & 0x0000000000000000) <default>
00:263 00:022 AAPL: [EB|#CONFIG| 8] kc-read-size  : 0x0000000000100000 (0x0000000000100000 < 0xFFFFFFFFFFFFFFFF) <default>
00:285 00:022 AAPL: [EB|#H:IS] 0
00:301 00:015 AAPL: [EB|#WL|0] 0x01 0x01   0 0x00
00:318 00:017 AAPL: [EB|#BRD:NV] Mac-AA95B1DDAB278B95
00:335 00:017 AAPL: [EB|#WL|1] 0x01 0x01   2 0x00
00:353 00:017 AAPL: [EB|`BST:IDT] {
00:370 00:017 AAPL: [EB|`BST:IDT] }
00:386 00:016 AAPL: [EB|#WL|2] 0x01 0x01   3 0x00
00:404 00:017 AAPL: [EB|#WL|3] 0x01 0x01   4 0x00
00:422 00:018 AAPL: [EB|#BRD:NV] Mac-AA95B1DDAB278B95
00:440 00:018 AAPL: [EB|#WL|4] 0x01 0x01   5 0x00
00:459 00:018 AAPL: [EB|`H:CHK] BM: 0x0000000000000000
00:477 00:018 AAPL: [EB|`H:CHK] Err(0xE) @ GV boot-signature
00:496 00:018 AAPL: [EB|#WL|5] 0x01 0x01  23 0x0E
00:515 00:018 AAPL: [EB|`H:CPM] Err(0xE), (24, 24) @ GV Persistent-memory-note
00:537 00:022 AAPL: [EB|`SB:EN] Err(0xE) @ LocP 24B73556-2197-4702-82A8-3E1337DAFBF2
00:559 00:022 AAPL: [EB|#LIMG:DP] Acpi(PNP0A03,0)/Pci(1B|4)/Pci(0|0)/?[ 0x83 0x17 0x10 0x0 0x1 0x0 0x0 0x0 0x0 0x25 0x38 0xC3 0x71 0xB0 0x84 0x42 ]/HD(Part2,SigCAF55823-C99B-436B-B8D0-756245C4D2DE)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842)
00:597 00:037 AAPL: [EB|#LIMG:FP] \EE46DEEA-45B5-4CEE-BDA8-BF165E8DA8F4\System\Library\CoreServices\boot.efi
00:622 00:025 AAPL: [EB|#LIMG:OPT] ()
00:642 00:019 AAPL: [EB|`OPT:LXF] 'LF (\\EE46DEEA-45B5-4CEE-BDA8-BF165E8DA8F4\\System\\Library\\CoreServices\\com.apple.Boot.plist)
00:671 00:028 AAPL: [EB|`LD:LF] FIO: 0, DIR: 1, P: \\EE46DEEA-45B5-4CEE-BDA8-BF165E8DA8F4\\System\\Library\\CoreServices\\com.apple.Boot.plist, DP: 0
00:701 00:030 AAPL: [EB|`LD:OFS] Err(0xE) @ OPEN (\\EE46DEEA-45B5-4CEE-BDA8-BF165E8DA8F4\\System\\Library\\CoreServices\\com.apple.Boot.plist)
00:732 00:030 AAPL: [EB|`OPT:LXF] Err(0xE) @ 'LF
02:960 02:228 AAPL: [EB|`OPT:LXF] 'LF (Library\\Preferences\\SystemConfiguration\\com.apple.Boot.plist)
02:987 00:027 AAPL: [EB|`LD:LF] FIO: 0, DIR: 1, P: Library\\Preferences\\SystemConfiguration\\com.apple.Boot.plist, DP: 0
03:016 00:029 AAPL: [EB:#KF] ()
03:038 00:022 AAPL: [EB|#MBA:CL] ()
03:061 00:022 AAPL: [EB|#MBA:NV] (slide=200)
03:083 00:022 AAPL: [EB|#MBA:KF] ()
03:106 00:022 AAPL: [EB|#MBA:OUT] (slide=200)
03:130 00:023 AAPL: [EB|`CSR:S] csr-active-config = 0x000003E7
03:156 00:025 AAPL: [EB|#OPT:BM] 0x84100
03:178 00:022 AAPL: [EB|`OPT:LXF] 'LF (\\EE46DEEA-45B5-4CEE-BDA8-BF165E8DA8F4\\System\\Library\\CoreServices\\PlatformSupport.plist)
03:210 00:031 AAPL: [EB|`LD:LF] FIO: 0, DIR: 1, P: \\EE46DEEA-45B5-4CEE-BDA8-BF165E8DA8F4\\System\\Library\\CoreServices\\PlatformSupport.plist, DP: 0
03:244 00:033 AAPL: [EB|#B:VAw]
03:268 00:024 AAPL: [EB|`P:DCCPR] Err(0xE) @ GV AAPL,CoProcessorReboot
03:295 00:027 AAPL: [EB|#P:MPI] N
03:319 00:024 AAPL: [EB|`CS:CSKSD] {
03:344 00:024 AAPL: [EB|`CS:CSKSD] Err(0xE) @ GV 8D63D4FE-BD3C-4AAD-881D-86FD974BC1DF:boot-info-payload
03:375 00:030 AAPL: [EB|#WL|6] 0x01 0x01   6 0x0E
03:401 00:026 AAPL: [EB|`CS:LFC] {
03:426 00:025 AAPL: [EB|`LD:LF] FIO: 0, DIR: 1, P: System\\Library\\Caches\\com.apple.corestorage\\EncryptedRoot.plist.wipekey, DP: 0
03:462 00:035 AAPL: [EB|`FS:AGSVH] Err(0xE) @ LocHB 59D76AE4-37E3-55A7-B460-EF13D46E6020
03:492 00:030 AAPL: [EB|`G:CS] } Ok(0)
03:523 00:031 AAPL: [EB|`LD:LF] FIO: 0, DIR: 1, P: <null string>, DP: 1
03:554 00:030 AAPL: [EB|`B:SBS] SZ: 617016
03:583 00:029 AAPL: [EB|#B:SHA] 86334d2de1b82c43d7871bf0ac2cf748e2f786c0
03:613 00:029 AAPL: [EB|`WL:PWLFNV] Err(0xE) @ GV wake-failure
03:643 00:029 AAPL: [EB|`WL:DT] Err(0xE) @ WL:PWLFNV
03:671 00:028 AAPL: [EB|`WL:PWLFRTC] ! @ RTC:R
03:700 00:028 AAPL: [EB|`WL:DT] Err(0xE) @ WL:PWLFRTC
03:728 00:028 AAPL: [EB|`FS:AGSVH] Err(0xE) @ 'AGU.0
03:757 00:028 AAPL: [EB|`FS:AGSVH] Err(0xE) @ 'AGU.1
03:786 00:028 AAPL: [EB|`FS:AGSVH] Err(0xE) @ 'AGU.2
03:816 00:029 AAPL: [EB|`FS:AGSVH] Err(0xE) @ 'AGU.3
03:845 00:029 AAPL: [EB|`FS:AGSVH] Err(0xE) @ 'AGU.4
03:875 00:029 AAPL: [EB|`FS:AGSVH] Err(0xE) @ 'AGU.5
03:905 00:029 AAPL: [EB|`FS:AGSVH] Err(0xE) @ 'AGU.6
03:935 00:029 AAPL: [EB|`LD:LKC] BPDK -> (System\Library\PrelinkedKernels\prelinkedkernel.development)
03:971 00:036 AAPL: [EB|`LD:OFS] Err(0xE) @ OPEN (System\\Library\\PrelinkedKernels\\prelinkedkernel.development)
04:007 00:036 AAPL: [EB|`LD:LKC] BPDK,!R -> (System\Library\PrelinkedKernels\prelinkedkernel)
05:374 01:367 OC: Prelink injection SMCProcessor.kext () - Invalid Parameter
05:413 00:038 OC: Prelink injection SMCSuperIO.kext () - Invalid Parameter
05:518 00:105 AAPL: [EB|`LD:LKFS] } Ok(0)
05:549 00:030 AAPL: [EB|`LD:LKC] } Ok(0)
05:580 00:031 AAPL: [EB|#FWFM] 0xFFDFFF7F
05:610 00:030 AAPL: [EB|#FWFT] 0xFD8FF576
05:641 00:030 AAPL: [EB|#CSR:OUT] 0x000003E7
05:672 00:030 AAPL: [EB|`BST:FBS] {
05:703 00:031 AAPL: [EB|`BST:FBS] BA.ADSZ: 0
05:734 00:031 AAPL: [EB|`BST:FBS] BA.KSDSZ: 0
05:767 00:032 AAPL: [EB|`B:WFDW] Err(0xE), 0 @ LocHB 71B4903C-14EC-42C4-BDC6-CE1449930E49
08:017 02:250 AAPL: [EB|#LOG:DT] 2020-06-03T00:54:04
08:050 00:033 AAPL: [EB|#LOG:EXITBS:START] 2020-06-03T00:54:04
 

myEFI.zip

[makk]

50 minutes ago, SavageAUS said:

@vit9696 I have played around with different options and i can manage to boot Arch Linux and Windows 10 but i lose macOS booting. Can you or anyone see anything in my config that would prevent macOS from booting.

This is on my laptop, specs in signature.

Testing is done via USB.

config.plist

 

Try this method:

 

I had today exactly the same problem, but with Windows instead of Linux (MSI mobo as well).

What I did:
- Mount Your EFI partition
- Move everything except BOOT (move every file except BOOTx64.efi too), APPLE and OC to Your desktop folder.
- Restart PC and check if BIOS sees OC (in my case it's named "UEFI OS (XXX)"
- if it is there, boot to macOS and add everything back on its place, then restart again PC and there should be UEFI OS and Linux

 

https://www.reddit.com/r/hackintosh/comments/dpzh3n/opencore_help_creating_a_boot_entry/

 

I would assume if no boot, use USB boot.

 

 

 

 

Edited June 3, 2020 by makk

[vit9696]

@SavageAUS, if your board is the GA 170 mentioned in your signature, I am pretty sure you need EnableWriteUnprotector to be able to boot macOS. Also, maybe you need SetupVirtualMap to be enabled and RebuildAppleMemoryMap to be disabled. Try all the 6 combinations.

[makk]

Greetings Vit

 

Is there a way to reorder the bootlicking in BootPicker?

Have not been able to find instructions on this so far.

 

I have three different macOS all using APFS container. If possible would like the boot order to be set

differently and the size of the icons to shrink? [ not sure if this is possible ]

 

thank you

[SavageAUS]

40 minutes ago, vit9696 said:

@SavageAUS, if your board is the GA 170 mentioned in your signature, I am pretty sure you need EnableWriteUnprotector to be able to boot macOS. Also, maybe you need SetupVirtualMap to be enabled and RebuildAppleMemoryMap to be disabled. Try all the 6 combinations.

 

1 hour ago, SavageAUS said:

This is on my laptop, specs in signature.

My desktop is fine this is for my laptop.

[vit9696]

Well, the advice is not really different: EnableWriteUnprotector, ProtectMemoryRegions, RebuildAppleMemoryMap, SetupVirtualMap, SyncRuntimePermissions. Try all combinations. 2^5 variants.

 

[tluck]

5 hours ago, el_charlie said:

 

He's referring that by using a PLNF device he gets graphic glitches that end up in UI freezes with HD3000. Those freezes didn't happen for him on Sierra, they do happen since High Sierra or Mojave with HS kexts. I experience those glitches on my laptop. I've tried everything.

 

Do you have those errors?

oh

sorrry. i thought it was about getting backlight working with OC. But Yes. I see occasional glitches on HighSierra and later (since on Mojave and Catalina the same gfx kexts from HS are used). A fake EDID, for some LCDs, fixed glitches and freezes on 10.9 - 10.12. On 10.13+, glitches happen on occasion. i found an 1600x900 EDID that has not froze for me on Catalina and OC. 

 

3 hours ago, makk said:

tluck,

 

with your hd3000, do you get garbage on your screen? and lockups?

 

were you able to install Catalina on hd3000? if so how did you get around the check?

I used, Dosdude patcher for this and error with This Mac is unsupported and stopped.

 

So far I have found that any PNLF statements create corruption in Video because 64 bit constant in a 32 bit table.  It's always PNFL. This Asus Laptop came with a separate FN key ATPK or ATKP driver to handle the calls for FN keys, brightness and so forth.  So without this driver, have a problem with hacked scripts -- SSDT-PNLF, PNLF brightness patches, so forth.  I was getting massive erroring and lockups when using SSDT-PNLF on Mojave and High Sierra.

 

 

my laptop with AUO LCD is prone to glitches and freezes UNLESS i inject the EDID from an LG LCD that works great. i just posted the basic PNLF device that will work and will give you backlight when coupled with Whatevergreen. So you may not need more extensive PNLF patching anymore.

 

as far as FN keys, the KB driver on macOS is voodoops2 (and custom SSDT) which remaps the FN keys (F1/F2) to the right codes for brightness up down. All this is my T420 guide or the 100s of post on this issue in the that thread. feel free to PM me, as this is not really about OC IMO.

 

And yes, dosdude1 method works with OC to get Mojave/Catalina on HD3000 boxes. see github.com/tluck for my EFI for OC.

 

[kecinzer]

On 5/28/2020 at 7:15 PM, apianti said:

 

Nah it was suggestion for the other person that the bt does indeed work in boot environment.

 

 

I think you're not understanding the part about it is still booting. It definitely makes sense a graphics change occurs right there as well.

I don't know if we understand each other correctly.

This not happens when system booting, but when I lock screen (CMD + CTRL + Q) - it also turn off all displays and then I wake it. It happens only with external display(s) connected and when laptop wasn't at sleep before.

[Tiem]

Hey guys, quick general question, but has anyone got the standard ALT/OPT key working when ShowPicker is set to 0? I really have no idea why it's not working, I can see the key is registering. I don't see anything in the docs that says any other option needs to be enabled.

 

Here's the relevant settings in OC (v0.6.0):

 

Edited June 3, 2020 by Tiem

[MacNB]

1 hour ago, Tiem said:

Hey guys, quick general question, but has anyone got the standard ALT/OPT key working when ShowPicker is set to 0? I really have no idea why it's not working, I can see the key is registering. I don't see anything in the docs that says any other option needs to be enabled.

 

Here's the relevant settings in OC (v0.6.0):

 

 

Does OpenCanopy appear when you set Show_picker = True ?

If not, then check your EFI/Resources folder for the Font, Labels & Image folders are not empty.