Jump to content

[pre-release] macOS Ventura

fantomas

By fantomas,
in New Releases and Updates

 Share
3338 posts in this topic

Recommended Posts

PC IT
PC IT
Posted
Posted
8 hours ago, aben said:


I'm afraid that I am unable to help any further as I simply cannot see the root cause for your LVDS to stay "off" only when booting macOS 13 even with settings provided earlier, quite strange tbh. Can help with one more EFI - have included more boot-args + device properties that could potentially fix the issue, test and see, if still no dice then I'm not sure how else this issue can be fixed, maybe try experimenting with other KBL profiles listed here .

 

Also, clear NVRAM before you boot - have included the option in OC picker. Good luck!

EFI.zip 2.4 MB · 3 downloads

Thank you again for all your support, same dimmed black screen, now am doing a fresh installation again using wegvesa boot arg, by which the installer works, will try inject the kbl fb in the 2nd boot phase and will see what will happen, i need to know how can i install kexts and folders to the SLE directory? as this directory is always locked, will keep trying, the other kbl profiles too, thank you so much, will keep in touch. 

7 hours ago, The Tech said:

Probably because you need to reverse the bytes. 

 

ig-platform-id = 00001B59

device-id = 16590000

Thank you so much, tried reversing the bytes as suggested, same issue, dimmed-black screen, i dont know why the screen back light controller is not working with these layout ids and fb details

 

 

The Tech
The Tech
Posted
Posted
10 minutes ago, PC IT said:

Thank you again for all your support, same dimmed black screen, now am doing a fresh installation again using wegvesa boot arg, by which the installer works, will try inject the kbl fb in the 2nd boot phase and will see what will happen, i need to know how can i install kexts and folders to the SLE directory? as this directory is always locked, will keep trying, the other kbl profiles too, thank you so much, will keep in touch. 

 

Use -igfxblr in your boot args.

SchlachtbankHS
SchlachtbankHS
Posted
Posted
11 minutes ago, PC IT said:

Thank you again for all your support, same dimmed black screen, now am doing a fresh installation again using wegvesa boot arg, by which the installer works, will try inject the kbl fb in the 2nd boot phase and will see what will happen, i need to know how can i install kexts and folders to the SLE directory? as this directory is always locked, will keep trying, the other kbl profiles too, thank you so much, will keep in touch. 

 

You don't have to install kexts on S/L/E anymore.. you need to keep the kext on OC/Kexts and load them in the config.plist

v-volodi
v-volodi
Posted
Posted
On 6/20/2022 at 9:51 PM, PC IT said:

Hello dear again, Graphics native resolution is 1600x900, i need a proper platform id and device id that is compatible for my lappy, or any other suggestions, the screen flick 2 times and stay black screen , but the system is working , i can hear the system sounds. any suggestions??

 

Hello. I Have laptop with native resolution is 1600x900 and also black screen on LVDS, any ideas?

Cyberdevs
Cyberdevs
Posted
Posted

Display loosing signal after loading macOS:

 

I made another discovery today which might be helpful to people with the same issue.

On my KabyLake (Formerly my SkyLake rig which I swapped the 6700K with a 7700K CPU) I tried to boot into Ventura using the Intel HD630, the system booted off of the iGPU and then after the second stage boot shortly after loading the desktop the display went black and i had to turn it off and on and then the signal came back and i could see the desktop,

After trying several SMBIOS settings (iMac18,1; MacPro7,1 and Macmini8,1 work fine by the way) I realized under the DeviceProperties I had this entry to disable my dGPU (R9 270X) so I decided to remove that entry and by doing so the issue got resolved.

 

  • Like 5
PC IT
PC IT
Posted
Posted
2 hours ago, aben said:


Could you please try testing with boot-arg: applbkl=0   Also try values 1, 2 and 3

Thank you for the help, tried your suggestion, still same black dimmed screen.

how can i unlock the os snapshot so i can paste the display properties in System/Library/Displays/Overrides?

do we need to modify the bios ?? i am using the latest bios version for my system

aben
aben
Posted
Posted
1 hour ago, PC IT said:

Thank you for the help, tried your suggestion, still same black dimmed screen.

how can i unlock the os snapshot so i can paste the display properties in System/Library/Displays/Overrides?

do we need to modify the bios ?? i am using the latest bios version for my system


I highly doubt this approach will have any effect since we've already tested this via alternate approach injecting display properties through AAPL00,override-no-connect.  I'd suggest omitting SSDT-PNLF as well while you're at it.

 

From what I could gather, it looks like your HD+ TN panel has a constant PWM frequency of 200 Hz that does not seem to be compatible with PWM base frequency values from KBL framebuffer. You can test this theory out by spoofing your SKL iGPU to KBL on Monterey and see if display still works. If not, that means there's only two potential, albeit not-so-viable options I see that could solve this particular use-case for macOS 13:

  • By patching "BXT_BLC_PWM_FREQ1" with help of WEG to better suit your panel when using KBL kext (not sure how this can be achieved easily with current WEG, maybe there is a configurable boot-arg or iGPU property that I'm not aware of but unless someone has access to this hardware and is willing to contribute code-wise, this option is highly unlikely)
  • Upgrade your panel to FHD IPS or TFT (more viable option)

Personally I would recommend waiting it out, testing through the beta cycle, till official release of macOS 13, given that SKL is not officially supported by Apple on Ventura, possibility of additional patches are imminent. Worse case - no choice but to stay on Monterey.

  • Like 1
jsl2000
jsl2000
Posted
Posted (edited)
1 hour ago, Hervé said:

Setting iGPU VRAM to 1536MB (unifiedmem 00000060 DATA) is useless and unnecessary, it's the default value. Does no harm of course.

 

Those who end up with black screen may try the WEG boot arg igfxonln=1 though I doubt it'll bring the built-in LCD to life.

Can you confirm the correct file size of WhateverGreen.kext for HD 530 is 526 KB (v.1.6.0) because I'm confused by the above debate about it.Also I found its file size will be changed to 525 KB automatically after successful booting.

Edited by jsl2000
SchlachtbankHS
SchlachtbankHS
Posted
Posted
2 hours ago, Hervé said:

You know how much as I do; I've no HD530 system and never had any. At this stage, I can't see why HD530 would not work just the same as HD520 does.

My HD530 works flawlessly, tbh works better with kbl framebuffer rather than with skl one

  • Like 1
jsl2000
jsl2000
Posted
Posted
2 minutes ago, SchlachtbankHS said:

My HD530 works flawlessly, tbh works better with kbl framebuffer rather than with skl one

Thanks for your info.

Can you confirm the file size of your WhatEverGreen.kext is 525KB or 526 KB for my comparison ?

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...