KazuDante Posted July 28, 2023 Share Posted July 28, 2023 I have a laptop with i5-7200U HD620. How can I get acceleration to work? I've been at it for almost 2 months on ventura and sonoma beta 1 beta 2 and beta 3 and still no luck at all. Link to comment Share on other sites More sharing options...
Administrators Hervé Posted July 28, 2023 Administrators Share Posted July 28, 2023 @KazuDante KBL HD620 is natively supported in Sonoma with the usual settings. The KBL graphics drivers remain provided as detailed in my Sonoma beta #1 thread. You must be using an incorrect config, especially if you have no success in Ventura. Please post your system's hardware specs, a zipped copy of your Sonoma EFI config (config file + kexts folder + ACPI folder, the rest is not needed) and, ideally, an IOReg extract too. You should be using the settings recommended in the Whatevergreen User Manual, i.e. KBL frame buffer layout 0x59160000, default being 0x591B0000. ID: 59160000, STOLEN: 34 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00000B0B TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 103 MB, MAX OVERALL: 104 MB (109588480 bytes) Model name: Intel HD Graphics KBL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000800, flags: 0x00000187 - ConnectorHDMI 00000800 02000000 98000000 01050900 00040000 87010000 02040A00 00080000 87010000 ID: 591B0000, STOLEN: 38 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000130B TOTAL STOLEN: 39 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 136 MB, MAX OVERALL: 137 MB (144191488 bytes) Model name: Intel HD Graphics KBL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS [2] busId: 0x04, pipe: 10, type: 0x00000800, flags: 0x00000187 - ConnectorHDMI [3] busId: 0x06, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 00000800 02000000 98000000 02040A00 00080000 87010000 03060A00 00040000 87010000 Framebuffer 0x59160000 natively supports HDMI output out of connector con1 but you'll need to patch the connector's type to HDMI (00080000) to obtain HDMI audio. Framebuffer 0x591B0000 requires to patch con1's Index and Bus Id from 0204 to 0105. If your laptop's BIOS sets DVMT to 32MB by default, you'll have to inject the properties that patch fbmem to 9MB and stolenmem to 19MB. See our dedicated thread on the matter ins our FAQ forum section for details. No such patches are required if DVMT is set to 64MB or above. Intel i5-7200U CPU integrates HD620 iGPU with id 0x5916 which is natively supported by the KBL driver so absolutely no need to fake any iGPU device. Finally, make sure you use MBP15,2 SMBIOS for Sonoma. In Ventura, it should be MBP14,1. Link to comment Share on other sites More sharing options...
KazuDante Posted August 5, 2023 Author Share Posted August 5, 2023 That is what ive been doing for the longest and still can't get it to work , started seeing refrences to dual-link, idk . HD620 works for everyone else but i think the major diff is that there internal display is not a 17" so im thinking since bios is severly locked-down i cant make any changes to DVMT, i think dvmt might be set higher then 32 or ever higher the 64 . All i wanted was to use it as a normal laptop , no need for hdmi/extra monitors , for now just a smooth ui experience is all i need . also heres the best part , i installed Big Sur and still getting black-screened after verbose , same on ventura same on sonoma . something is def wrong with this laptop Link to comment Share on other sites More sharing options...
Administrators Hervé Posted August 6, 2023 Administrators Share Posted August 6, 2023 The only thing likely to be wrong is not your laptop but your setup... Can't see why you have some of those properties injection, especially the framebuffer flags. Try to use only the following: AAPL,ig-platform-id 00001659 DATA framebuffer-patch-enable 1 NUMBER framebuffer-con1-enable 1 NUMBER framebuffer-con1-type 00080000 DATA This assumes MBP14,1 SMBIOS for Ventura of course, MBP15,2 for Sonoma. Link to comment Share on other sites More sharing options...
KazuDante Posted August 8, 2023 Author Share Posted August 8, 2023 (edited) @Hervé Did try and same issue . heres what i found and maybe you could help me understand why something finally worked for me . i installed Big Sur amd the usual methods did not work , but i stumbled onto an EFI for an HP and simply tried it as is and it actually worked , but the author even stated that on ventura the graphics arent accelerated. Can i send you the EFI to take a look because i would def like to use Sonoma instead of Big Sur Edited August 8, 2023 by KazuDante Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted August 9, 2023 Moderators Share Posted August 9, 2023 Post the efi folder + IOreg file using IORegistryExplorer.app Link to comment Share on other sites More sharing options...
KazuDante Posted August 9, 2023 Author Share Posted August 9, 2023 @Hervé @Jake Lo ioregdump.ioreg efi was too large , will remove kext and try uploading again EFI.zip Link to comment Share on other sites More sharing options...
Administrators Hervé Posted August 9, 2023 Administrators Share Posted August 9, 2023 This is a complete (bad) joke, right? Booted OS was Big Sur (kernel 20.6.0, build 20G1426) and your OC config + IOReg show you're injecting Skylake settings! SKL framebuffer 0x10160000 and SKL iGPU id 0x1916... So, not only are you incorrectly using 6th gen. Skylake settings on a 7th gen. Kaby Lake laptop, must we also remind you that Skylake graphics are unsupported since Ventura? And it was also stated before that you should be using MBP15,2 SMBIOS, not MBP15,3. If you follow what was previously suggested, I'm sure you'll get somewhere... Use the correct settings in your config file, save it and make sure to reset NVRAM at OC Picker when you reboot. Link to comment Share on other sites More sharing options...
KazuDante Posted August 10, 2023 Author Share Posted August 10, 2023 ive been trying with 00001659 09001659 00001B59 sine ventura 13.4-13.5 Sonoma beta 1-3 and all i get are black screen and not 3min black screen . heck i even tried using some of these configs but with 00001659and still black-screen ,regarding nvram i always reset ,with 00001659 on sonoma only thing i added in boot-arg is the -no_compat_check to avoid the not supported issue . im simply trying to figure out why everyone else on sonoma can have HD620 working and mines refuses to work , i even went as far as thinkin that maybe its the screen size so maybe dvmt shouldnt be set to 32 ,test with 34 38 64 96 128 all same results , no hdmi output as well also p.s after i saw this random efi worked i did try the your suggestion on Big Sur and it was black-screen as well Link to comment Share on other sites More sharing options...
KazuDante Posted August 10, 2023 Author Share Posted August 10, 2023 Now im thinking maybe spoofing the GPU is the only way for this laptop to have working graphics Link to comment Share on other sites More sharing options...
Recommended Posts