ichelash Posted June 27, 2022 Share Posted June 27, 2022 8 hours ago, Aluveitie said: @asdeso you can patch in the old kexts from Big Sur, but you have to break the root volume seal and lose incremental updates. And you have to redo this after every update. Enlighten us sorry “me” the noobs on this @Aluveitie have my gt 710 around Link to comment Share on other sites More sharing options...
miliuco Posted June 27, 2022 Share Posted June 27, 2022 (edited) 20 minutes ago, Cyberdevs said: Yeah it shows the same error on my rigs as well (Both KabyLake and AlderLake) I did edit my post: Custom Memory doesn't fix this. The system seems to work very well. Edited June 27, 2022 by miliuco Link to comment Share on other sites More sharing options...
Stefanalmare Posted June 27, 2022 Share Posted June 27, 2022 Z390 iMac19.1 and Z690 iMacPro1.1 no issue with memory. Link to comment Share on other sites More sharing options...
miliuco Posted June 27, 2022 Share Posted June 27, 2022 (edited) 24 minutes ago, Stefanalmare said: Z390 iMac19.1 and Z690 iMacPro1.1 no issue with memory. Only with MacPro7,1. Even with last RestrictEvents. Edited June 27, 2022 by miliuco 1 Link to comment Share on other sites More sharing options...
D3v1L Posted June 27, 2022 Share Posted June 27, 2022 (edited) with custom memory in config.plist (in right way...i mean, with all slot compiled) ... Edited June 27, 2022 by D3v1L 1 Link to comment Share on other sites More sharing options...
PC IT Posted June 27, 2022 Share Posted June 27, 2022 On 6/26/2022 at 6:35 PM, Hervé said: Your config still doesn't look right... Granted that device if 0x591B is a fully supported iGPU id (and is perfectly usable on my Skylake/HD520 Latitude E7270), did you try device id ? As for the 2 x IOReg, what difference of context between the two? 'pretty sure you can forget about that display data kext of yours. Thank you Herv'e for the reply, i tried the 0x5916 as you mentioned before. only on external display i can get full qc, on normal display i get black screen. do you have any efi i can test or compare with mine, thank you so much Link to comment Share on other sites More sharing options...
miliuco Posted June 27, 2022 Share Posted June 27, 2022 @D3v1L Congratulations. I’ll check the config.plist tomorrow but I’m pretty sure I have also filled all 12 devices (slots). With custom memory do you load RestrictEvents? Link to comment Share on other sites More sharing options...
D3v1L Posted June 27, 2022 Share Posted June 27, 2022 1 minute ago, miliuco said: @D3v1L Congratulations. I’ll check the config.plist tomorrow but I’m pretty sure I have also filled all 12 devices (slots). With custom memory do you load RestrictEvents? Absolutely no ...Not needed... Currently im not at home...tomorrow i'll post by memory config part so you compare with yours if you want 🙂 2 Link to comment Share on other sites More sharing options...
miliuco Posted June 27, 2022 Share Posted June 27, 2022 7 minutes ago, D3v1L said: Absolutely no ...Not needed... Currently im not at home...tomorrow i'll post by memory config part so you compare with yours if you want 🙂 Thank you so much! Good night. Link to comment Share on other sites More sharing options...
D3v1L Posted June 27, 2022 Share Posted June 27, 2022 (edited) LoL i've a copy of config.plist on my laptop at work xD ... here's CustomMemory parts... Too much important part: need to be much much more than installed otherwise, it give error... 😉 CustomMemory.plist.zip btw, goooood night 😉 cheers Edited June 27, 2022 by D3v1L 1 Link to comment Share on other sites More sharing options...
miliuco Posted June 28, 2022 Share Posted June 28, 2022 10 hours ago, D3v1L said: LoL I've a copy of config.plist on my laptop at work xD ... Thank you!!! Strange, my mobo has max. memory 128 GB (137438953472 in config.plist) but it's not working if I don't set more than the max, as you say in your post, when I set 256 GB (274877906944 as in your config.plist) then it works fine. Without RestrictEvents. Note: you have in config.plist ChannelD-DIMM0 twice although I see it has no relevance in the final result. Spoiler 1 Link to comment Share on other sites More sharing options...
D3v1L Posted June 28, 2022 Share Posted June 28, 2022 5 minutes ago, miliuco said: Thank you!!! Strange, my mobo has max. memory 128 GB (137438953472 in config.plist) but it's not working if I don't set more than the max, as you say in your post, when I set 256 GB (274877906944 as in your config.plist) then it works fine. Without RestrictEvents. Reveal hidden contents Here the trick! ChannelD is my typo (old config)... need to be ChannelD-DIMM1 (one is 0 and one is 1) 1 Link to comment Share on other sites More sharing options...
miliuco Posted June 28, 2022 Share Posted June 28, 2022 (edited) @D3v1L Really this is a less elegant way to do it than RestrictEvents which avoids having ghost slots that don't really exist. Also, memory tab, although it has the slots ok, says that "Your Mac has 12 memory slots, 0 of which are installed with a 2133 MHz DDR4 memory module" but there are 4 slots filled, not 0. However, until RestrictEvents works in Ventura as in Monterey, I like to remember this other way of configuring memory with MacPro7,1 SMBIOS. With the doubt of what is the reason for having to adjust more than the maximum memory that the board supports. Thanks. Edited June 28, 2022 by miliuco 1 Link to comment Share on other sites More sharing options...
D3v1L Posted June 28, 2022 Share Posted June 28, 2022 btw...this with resctrictevents... definitely not working with Ventura 🙂 (latest beta kext from actions) 1 2 Link to comment Share on other sites More sharing options...
miliuco Posted June 28, 2022 Share Posted June 28, 2022 (edited) @D3v1L Yes, RestrictEvents doesn't work very well yet with Ventura. Edited June 28, 2022 by miliuco 3 Link to comment Share on other sites More sharing options...
aben Posted June 28, 2022 Share Posted June 28, 2022 Looks like KBL (device-id spoofed) being reported as having Metal 3 support on Beta 2; most likely a bug with early beta builds misreporting this info OR Apple actually plans to include Metal 3 support for all Intel graphics stack/iGPUs natively supported on Ventura (KBL+CFL+ICL). 3 Link to comment Share on other sites More sharing options...
Cyberdevs Posted June 28, 2022 Share Posted June 28, 2022 @aben Yeah the same on KBL and intel hd 630 6 Link to comment Share on other sites More sharing options...
Takiller Posted June 28, 2022 Share Posted June 28, 2022 On my side airplay is broken on both Ventura betas and hope it will come back in the next betas 😬 1 1 Link to comment Share on other sites More sharing options...
asdesoso Posted June 28, 2022 Share Posted June 28, 2022 On 6/27/2022 at 10:44 AM, Alexey Boronenkov said: I have a Gigabyte GT 730 2 GB DDR3 in my room, but there isn´t in use, yesterday I tried with Kepler patch from chris1111 and OCLP 0.4.7 putting the 4 requirements in OC config.plist, but nothing works, how did you make it work? Thanks. 2 Link to comment Share on other sites More sharing options...
PMheart Posted June 28, 2022 Share Posted June 28, 2022 4 hours ago, miliuco said: @D3v1L Yes, RestrictEvents doesn't work very well yet with Ventura. Could you please provide debug logs? 2 Link to comment Share on other sites More sharing options...
miliuco Posted June 28, 2022 Share Posted June 28, 2022 37 minutes ago, PMheart said: Could you please provide debug logs? Hello and thanks. I'll get debug OpenCore and RestrictEvents and do it. Do you prefer here or it's better to open an issue in the bug tracker? 1 Link to comment Share on other sites More sharing options...
PMheart Posted June 28, 2022 Share Posted June 28, 2022 8 minutes ago, miliuco said: Hello and thanks. I'll get debug OpenCore and RestrictEvents and do it. Do you prefer here or it's better to open an issue in the bug tracker? We indeed need an issue tracking this issue, so it’s better if you file it on GitHub. Thanks! You will need the debug version of Lilu and RestrictEvents; as for OpenCore it’s up to you. 3 Link to comment Share on other sites More sharing options...
miliuco Posted June 28, 2022 Share Posted June 28, 2022 (edited) @PMheart I'll do it. One question: apart of OpenCore log got from EFI partition, must I provide any other log or file? Thanks. EDIT: I've read in the bug tracker: OpenCore debug log, EFI zipped, OC and kexts last versions... Edited June 28, 2022 by miliuco 2 Link to comment Share on other sites More sharing options...
miliuco Posted June 28, 2022 Share Posted June 28, 2022 @PMheart @D3v1L @Cyberdevs Done, new issue in the bug tracker. 4 Link to comment Share on other sites More sharing options...
Guest ricoc90 Posted June 28, 2022 Share Posted June 28, 2022 (edited) 4 hours ago, aben said: Looks like KBL (device-id spoofed) being reported as having Metal 3 support on Beta 2; most likely a bug with early beta builds misreporting this info OR Apple actually plans to include Metal 3 support for all Intel graphics stack/iGPUs natively supported on Ventura (KBL+CFL+ICL). https://github.com/kendfinger/metalgpu Edited June 28, 2022 by ricoc90 Link to comment Share on other sites More sharing options...
Recommended Posts