Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8755 posts in this topic

Recommended Posts

makk
makk
Posted
Posted

from WEG?  I used that originally for OpenCore and received this error and then rehabman's both give this error

 

ACPI Warning: truncated.

Must be the MaciASL version I'm using switching to one that does not cause this problem.

 

I had Rehabman's MaciASL on another machine v6.2 which I use normally.

On this machine, using Acidanthera version.  

 

 

 

makk
makk
Posted
Posted

Greetings,

No it's not the app or file.  strange.

 

At first I recompiled and then used it. It was fine.  I rebooted several times. 

 

2 parts:

1 When the SSDT-PNLF attaches to DSDT statement and kext is when the truncate messages occurs.

 

2 Once I rename GFX0 to IGPU or vise versa, is when the message occurs.  

 

Also, patched DSDT with PNLF leaving the PNLF at IGPU as originally for Rehabmans

Acidanthera one I think if not mistaken is GFX0 I used that several hours ago.  After a reboot

the issue happened.  To see if this would follow, I used Clover EFI samething.

 

So gathering Rehabmans research helping others, I tested each SSDT and a DSDT.  Recompiled each one

and ticked off each one nice feature of OC easy to test without having to destroy.  and then reboot

clear nvram and reboot many times. 

 

Still figuriing this out.

 

 

makk
makk
Posted
Posted (edited)

on the acidanthera version of MaciASL, there's three to choose from:  legacy, stable, dev.

when I use legacy, and then stable on the same file, get an error and it crashes.  vice versa.

such as too many messages remarks and warnings. when you fix the, the dsdt don't work.

 

this is Asus old aptio so it has lots of weird stuff and language like AMD for instance SBRG instead LPCB for LPC

all kinds of strange.  

Its been a struggle to get this to work.  one minute it works fine next it don't.

rather weird.

 

possible CMOS corruption. BIOS where the files are stored. block of storage space.

acpidump brought out 255 dsdt.dat. each one the same.

 

ssdtprgen ran twice to see if this would help.  it's always SSDT-PNLF.aml whichever one doesn't matter
At first after recompiling no problem. Rebooted to test.  passed. later problem again occured

I it may be the DSDT itself.  Have to figure this out

Thanks 

 

SOLVED:  problem was lack of statements in DSDT.

Resoled it by placing the PNLF into Device 

works out great.

 

upload DSDT

I remembered doing this before, copying over PNLF file into DSDT once upon at time.

 

 

DSDT.aml.zip

Edited by makk
SOLVED
tluck
tluck
Posted
Posted
7 hours ago, vit9696 said:

@tluck, could you make sure that you use the latest DEBUG versions of all the drivers (e.g. OpenCanopy and OpenRuntime) and OpenCore itself? Also, please switch to HFSPlus and not VboxHfs.

 

After you accomplish this, please set Target to 67 and then provide us a log when you install macOS update and believe OpenCore defaults to a wrong boot entry.

 

Also, does NVRAM work correctly for your system? It is not (always) possible to select a correct boot entry without working NVRAM.

switching to HFSPlusLegacy.efi was a nice change - it allows me to boot from a USB macOS installer. The issue I previously asked about doesnt seem to be an OC bug or problem. i am using Dosdude1 USB installer and it behaves the same way with CLover - if one launches it from macOS it doesnt seem to be setting efi-boot-device nvram. But if i boot the USB installer directly it works as expected. i was just a bit suprised to not see a picker option for the installer when the USB copies the bits to the OS location.  
 

one thing i noticed was that with too many devices OpenCanopy goes off the edges of the screen and doesnt seem to scroll left or right.

Also, was there a recent change in OpenShell? i had to revert to one from last week. the latest just hung for me.

 

Otherwise OC is pretty cool :)

SavageAUS
SavageAUS
Posted
Posted

Yeah it’s possible. I think scanpolicy is set to 0 at the moment. I’m not sure how that all works yet but I can try the scan policy you linked.

Mind you I don’t have a “Linux” entry in my firmware just a uefi os entry.

 

 

Sent from my iPhone using Tapatalk

[mention]apianti [/mention] I just installed arch on an ssd in my desktop and it is listed as NO NAME entry in OC and it boots just fine. I installed it the same way as I did on my laptop but no entry exists for it. I’ll try reinstall the boot loader for arch on my laptop and try again and see how it goes. Now to figure out how to rename the NO NAME to Arch Linux on my desktop.

 

 

Sent from my iPhone using Tapatalk

MorenoAv
MorenoAv
Posted
Posted (edited)

Hi Guys,

Today I updated my OpenCore 0.5.9 with the last build and it boots but at the start I see a notification with "OCS: No schema for HideSelf at 4 index, context <MISC>" as you could see in the picture enclosed below.

In the config.plist isn't any entry pertaining to HideSelf as was in the 0.5.8 version.

How can I solve this?

Thanks

IMG_4233.jpg

Edited by MorenoAv
Matgen84
Matgen84
Posted
Posted
1 hour ago, MorenoAv said:

Hi Guys,

Today I updated my OpenCore 0.5.9 with the last build and it boots but at the start I see a notification with "OCS: No schema for HideSelf at 4 index, context <MISC>" as you could see in the picture enclosed below.

In the config.plist isn't any entry pertaining to HideSelf as was in the 0.5.8 version.

How can I solve this?

Thanks

 

Do you mean you've removed HideSelf key in Misc -> Boot ! 

Can you post your config.plist. Please.

UefiBooter
UefiBooter
Posted
Posted

does no one bother to read the docs ...

 

https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Differences/Differences.pdf

 

you'll see HideSelf was removed

 

cmon guys your experienced users filling the thread with silly questions already covered in the documentation.

  • Like 2
  • Haha 1
Matgen84
Matgen84
Posted
Posted (edited)
1 hour ago, UefiBooter said:

does no one bother to read the docs ...

 

https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Differences/Differences.pdf

 

you'll see HideSelf was removed

 

cmon guys your experienced users filling the thread with silly questions already covered in the documentation.

 

@MorenoAv wrote that there was no entry for HideSelf. Personally, I asked for confirmation that he deleted Hideself in config.plist. Where are the stupid questions? :hysterical:

Edited by Matgen84
  • Like 1
makk
makk
Posted
Posted

Vit,

 

Inserting the patch for PNLF into the DSDT the long version, caused video corruption after a few minutes.  kinda of like kaleidoscope thing. parts start disappearing letter's become greek. Not immediate but after shutting down for a few hours. 

 

had to revert back to PNLFless DSDT. using the patch Fix Backlight from Rehabman's Laptop repository in MaciASL causes truncate message.

Using the SSDT-PNLF works yet: truncate message during system boot.  one message.

 

Used 3 different MaciASL's  6.1, 6.2, 6.3.  

 

I think originally used 5.0a?  many years ago for Sierra and left it as is. running Sierra.

Upgrading to these new ones, unable to compile a good DSDT with the same patches used

5 years ago for Sierra.  sendup with 201 errors.

 

I tossed the old APIC namely DSDT, SSDT Power,  because could no longer use them with newer MaciASL.

Errors.  version change.  cannot use every single patch without errors.

 

in Acidanthera's MaciASL 1.57 there is three options:  legacy stable dev. version is 6.3a

would like to compile without truncating. Any suggestions?

 

Thank you

 

OC is sweet.

 

In the Tab UEFI, the Reserved>HD3000 errata corruption would that work? or cause a problem?

 

 

 

 

 

vit9696
vit9696
Posted
Posted

@makk, various glitches on Intel HD 2000/3000 GPUs are indeed the case due to hardware bug. You can try using reserved memory feature to workaround it, but we cannot guarantee it.

 

As for issues with iasl, I use the latest iasl version usually and have no issues with it. Cannot comment for others.

  • Like 1
el_charlie
el_charlie
Posted
Posted (edited)
30 minutes ago, vit9696 said:

@makk, various glitches on Intel HD 2000/3000 GPUs are indeed the case due to hardware bug. You can try using reserved memory feature to workaround it, but we cannot guarantee it.

 

As for issues with iasl, I use the latest iasl version usually and have no issues with it. Cannot comment for others.

 

Can you elaborate more about that feature? Why did you develop it? I have a sandy bridge laptop and I have some glitches and then freezes on High Sierra that lead to UI freezes. I've tried everything.

 

I switched from Clover to OpenCore to see if ReservedMemory fixed anything and it doesn't.

 

Is there a place to discuss this further? 

 

The freezes seem to appear when filling the RAM with many apps/processes open. Many times I get UI freezes but the mouse still works.

 

EDIT: also, why 256MB the reserverd memory size? I have 8GB of RAM and macOS sets up 512MB for the HD3000. I even tried that on the config.plist. same results.

Edited by el_charlie
Tiem
Tiem
Posted
Posted (edited)
27 minutes ago, MorenoAv said:

Hi @Matgen84, @UefiBooter,

I asked because I didn't see HideSelf in config.plist, neither in the documentation and at boot I see the mention to it... 

 

config.plist

It was removed. The notice you see at boot is simply notifying you of this.

 

Edit: You also have a typo in your boot arguments, missing the equals sign: -v keepsyms=1 debug=0x100 alcid 7

It should read: -v keepsyms=1 debug=0x100 alcid=7

Edited by Tiem
  • Like 1
makk
makk
Posted
Posted
24 minutes ago, el_charlie said:

 

Can you elaborate more about that feature? Why did you develop it? I have a sandy bridge laptop and I have some glitches and then freezes on High Sierra that lead to UI freezes. I've tried everything.

 

I switched from Clover to OpenCore to see if ReservedMemory fixed anything and it doesn't.

 

Is there a place to discuss this further? 

 

The freezes seem to appear when filling the RAM with many apps/processes open. Many times I get UI freezes but the mouse still works.

 

EDIT: also, why 256MB the reserverd memory size? I have 8GB of RAM and macOS sets up 512MB for the HD3000. I even tried that on the config.plist. same results.

Charlie

 

Yes, I have these too.  What I found is have to have minimal in DSDT,  overloading it with GFX HDEF specifics causes serious Console>Desktop to not respond> Froze state. Mouse and Keyboard works but the console is not giving you a Workable Display as in normal. 

 

Been able to narrow this down to certain two problems, but have not found the root as in completely without a bench testing  unit where there is no HDD SDD purely bench.

 

Can't debug with full house

 

have to have bench to place one item at a time to see which 'thing' is causing problem.


While in a live unit, such as our Desktops, Laptops it's running full steam with many apps. Hard to narrow it down because too many programs using the same things that causes the problem then it multiplies.

 

DSDT. should have minimal regarding HD3000 and leave it in GFX0 renaming it causes more issues.

Such as ACPI Warning:  Truncated 64 bit constant found in 32 bit Table> SSDT DSDT problem that is not actually  the root of the problem it is within the BIOS and the way it was written ACPI portion handling of hardware to software,  handoffs, toss the ball from me to you sorta thing.

 

narrowed it down to on my system SSDT-PNLF <Backlight for Display it worked in Sierra. Switching to High Sierra big problems.  What was hidden surfaces.  Sierra was not so defined in ACPI. Also HD3000 is not so good.

 

Sandybridge is sandy and washes a lot.

 

Plus this PC is a PC not a Mac.

 

To upgrade to High Sierra need a HD400 and better.

 

DSDT editing have to figure out how far one can go without causing Lockups.  

At the moment the interaction between HD3000 and the switches to make it smooth are the problem.

 

> Display to be able to dim and brighten.

> Display to be able to use GL/QE/CL to use apps.

> Display to be able to sleep

 

1 DSDT what's in it?

2 SSDT to use instead of DSDT full and complete.

3 Use Drivers/kexts to read APIC with good logic. So the machine parts know how to act and when and appropriately.

 

DSDT is like one part of a big library more like a dictionary or Encyclopedia.  The Book. And A driver needs to be able to understand this book.  

 

need a bench tester to iron out the problem

 

For my end, as long as no SSDT-PNLF and no PNLF in DSDT no lockups or freezes.

These two cannot live happy without causing some issue.  So need a clear fix.

 

In Clover I used ADD PNLF 0x0A and removed the PNLF from DSDT. 

But in Opencore no other function but to use SSDT-PNLF.

 

So now looking at Fkeys without FN adapatin; extension keys to switch to PC keys to find a solution to get Brightness back.

 

When the Console your Desktop Freezes, it's a graphics related issue in DSDT / SSDT conflict.

 

Boot your system -v and see if you see:

 

ACPI Warning: Truncated 64 Bit constant found in 32 Bit Table fffffffffffffff0 => fffffff0 (some numbers) -dsobject 832

 

ACPI table is not syncing correctly

 

 Share
Go to topic listing
×
×
  • Create New...