KazuDante Posted September 10, 2023 Author Share Posted September 10, 2023 @Hervé Now getting stuck here . any clues in the last couple of lines ? Link to comment Share on other sites More sharing options...
Administrators Hervé Posted September 11, 2023 Administrators Share Posted September 11, 2023 Looks like graphics are not initialising and system hangs. Link to comment Share on other sites More sharing options...
KazuDante Posted September 14, 2023 Author Share Posted September 14, 2023 @Hervé Does this mean that it's picking my HD620 properly now ? Still no acceleration, attached is the ioreg MacBook Pro.ioreg Link to comment Share on other sites More sharing options...
Administrators Hervé Posted September 14, 2023 Administrators Share Posted September 14, 2023 No, you still get it wrong! You inject AAPL,ig-platform-id with hexadecimal value 16590000 when it should be 00001659. This is getting ridiculous not to say tiring when you were provided with all the correct settings on p1 all those weeks ago. It would also appear that you inject: framebuffer-stolenmem with hexadecimal value 26000000 when it should be 00003001 (or no injection if DVMT set to 64MB or above) framebuffer-fbmem with hexadecimal value 00000000 when it should be 00009000 (or no injection if DVMT set to 64MB or above) see here for details and eventual further adjustments In addition, make sure you boot with: latest version of Whatevergreen kext relevant lilu beta boot args (-lilubetaall or -lilubeta -wegbeta -alcbeta) SMBIOS MBP14,1 + -no_compat_check boot arg -igfxonln=1 if necessary (mostly for HDMI output) Link to comment Share on other sites More sharing options...
KazuDante Posted September 14, 2023 Author Share Posted September 14, 2023 @Hervé I know those values are not the recommended one but the recommended one don't work at all . Since bios has no option to change dvmt I tested setting it around 63 since for many kbl I saw fbmem to 0 to see if something different would make a difference . Guess this weird kaby lake laptop can't be properly hackintoshed . Link to comment Share on other sites More sharing options...
Administrators Hervé Posted September 15, 2023 Administrators Share Posted September 15, 2023 Injecting value 16590000 for a KBL framebuffer is as useful as injecting value 12345678. It's invalid so will not get you anywhere. The list of valid KBL framebuffers is available in the WEG manual here. Reminder: Hexadecimal value 0x12345678 is injected as DATA value 78563412 in a bootloader's config. Link to comment Share on other sites More sharing options...
KazuDante Posted September 15, 2023 Author Share Posted September 15, 2023 @Hervé normally for platform-id I write 00001659 and for device I write 16590000 as recommended with the dvmt 32mb patch , I get a black screen with backlight on . Then I try injecting property into igpu for the latest alternative backlight registers showned in whatevergreens and still the same outcome , then I even tried bus-id patching from bus 00 to 06 to see if there's an output and still the same outcome and then even pulled EDID hex and injected it and still same outcome. I think normally it should of worked since other HD620 don't even need all that to work properly , so I must assume HP did something weird on this laptop variant that macOS can't work properly with this laptop's configuration. That weird EFI that I stumbled upon to is the only one that gets graphic acceleration but can only use it as high as Monterey sadly . Link to comment Share on other sites More sharing options...
Administrators Hervé Posted September 15, 2023 Administrators Share Posted September 15, 2023 Try alternative KBL FBs like 0x591B0000 then. Link to comment Share on other sites More sharing options...
KazuDante Posted September 16, 2023 Author Share Posted September 16, 2023 @Hervé already tried 00001B59 several times . Could my situation be related to AGDP ? Saw some old post regarding some iMac facing black screen and they had to disable it . Link to comment Share on other sites More sharing options...
KazuDante Posted September 16, 2023 Author Share Posted September 16, 2023 (edited) @Hervé so far only the I assume is a headless platform-id ( 0x59180002 and 0x59180003 ) and the invalid ID of 12345678 gives an output by internal display , all other kabylake related platform-id are black-screened and backlight. Spent the night and re-tried them all Edited September 16, 2023 by KazuDante Wrote teied instead of tried Link to comment Share on other sites More sharing options...
Recommended Posts