KazuDante

@Hervé Ok , guess close and delete this thread .

@Hervé I was asking if theres anything useful because I really don't see what else to do regarding this . Spoofing as a Skylake gives an output on screen but no acceleration.

@Hervé Do you see anything interesting in this picture ? Something that might open a diff door .

@Hervé yes collected from windows 11 , for some odd reason I can't install any Linux on this anymore , need to find another windows that's not messed around with to create a fresh usb-installer of at least Ubuntu to see if the same issue occurs if not then I'll see if the EDID hex from Ubuntu are the same

@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

@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 .

@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 .

@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 .

@Hervé Does this mean that it's picking my HD620 properly now ? Still no acceleration, attached is the ioreg MacBook Pro.ioreg

@Hervé Now getting stuck here . any clues in the last couple of lines ?

@Hervé my bad i misread it , thats what ive been doing to test configurations to find what would get acceleration working , i had already tried a minimal setup with no fbmem and no stolenmem , just the unified , at one point even tried just the AAPL-ig-platform of 00001659 then 09001659 , all those always end with a blacks screen with backlight on

@Hervé Mac is already installed on the laptop , i am trying to get graphic acceleration working so that the UI can run smoothly, that is my only issue for months

@Hervé thank you , seems like i might be getting closer , i removed fbmem and only set stolen-mem , set it to about 30mb. rebooted , reset nvram but still got to backlight and black screen. many attempts at adding other tweaks like backlight fix backlight-alternatie-fix ... nothing still a blackscreen with backlight on . Then i looked at hackintosh tool since my only need is internal display i only set con0 in config but tried something ( just testing ) i also set the connectors always connected to change the flags , copied over reaults of the alldat to con0. when rebooted and test ( after reseting vnram ) verbose loaded as normal until it gotten to the IGPU part then about less then 20 lines after the backlight dimmed slightly as if it was about to ouput a display . so thats a step foward. Now even after reading busID patching im still confused . what i want to test out is to re-route for example con2'ouput to con0 so im asking whats need to be swapped to do that ?

went back to win11 to check on something , does this mean that my laptop's DVMT is preset to 128MB and not 32-64-96 ? if so should i remove fbmem and stolen-mem ?

sadly for me my bios is locked , cant change anything important . also tried to re-direct con2 to con0 and still blackscreen with backlight on , even tho i added backlight-register-alternative-fix thats meant for kbl. i seriously dont understand why this is so difficult when other HD620 users are already up and running fine

that config was janked , found it at random and it was from a diff laptop that had a dgpu i think an rx470 (something like that ) and it worked on big sur but what it did was i guess spoofed my native kbl to a skylake and spoofed it to use kbl drivers , using same config on ventura and up does not work . So now im going back to trying to make it work properly . this is my laptop https://support.hp.com/ee-en/document/c05392764

no other gpu , only HD 620 back to square 1 i guess .

another question , in your working HD620 on sonoma , does the laptop panel have a ACPI path , like _SB.PCI0.GFX0.XXXX ? Sadly i did not take a screenshot when i had win11 installed but during the process of pulling EDID info i saw it showed 3 options but 3rd was the only active( i assume its the internal display ) , so im guessing that maybe connector2 is my internal and not con0 or con1

Question, is it normal when using igfxvesa or invalid I'd like 12345678 that the OS sees the display as being screen mirroring ?

went back to Sonoma , and back to the same issues , i seriously dont understand whats going on , if i dont use igfxvesa or platform 12345678 i only get black screen after verbose outputs .

Now im thinking maybe spoofing the GPU is the only way for this laptop to have working graphics

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

@Hervé @Jake Lo ioregdump.ioreg efi was too large , will remove kext and try uploading again EFI.zip

@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

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