Contribute
Register

[Success] Install Ventura on the HP ProDesk 600 G3 with OC 0.8.6

can you set DVMT in your bios to 64MB?

what happens when you remove the invalid device-id?
DVMT is at 128MB (I doubled it a few tries before). Removing the device ID, which I think is the correct value now that I know how to properly enter it, and the frame buffer (00001259 is another valid one which gives crazy colors as well). I tried 00002359 which is one several suggested in Whatevergreen FAQs just to see what would happen.. What is strange that the device is 0x5912b (=00001259) is listed when I specified 0x2359b (00002359). Is this value stored somewhere? Myconfig.plist as 0x5923 (=000002359) but Display still shows device as 0x5912. Anyway, same result. All I did was delete the device-id line. I am going by this:

WhateverGreen/FAQ.IntelHD.en.md at master · acidanthera/WhateverGreen · GitHub



Screenshot 2022-11-25 at 19.23.34.png
Screenshot 2022-11-25 at 19.23.23.png
 

Attachments

  • Screenshot 2022-11-25 at 19.34.42.png
    Screenshot 2022-11-25 at 19.34.42.png
    109.6 KB · Views: 28
  • Screenshot 2022-11-25 at 19.37.33.png
    Screenshot 2022-11-25 at 19.37.33.png
    55.5 KB · Views: 30
Last edited:
I also see this info in Whatevergreen FAQ. No idea what to do with these? Could this help?
 

Attachments

  • Screenshot 2022-11-25 at 20.19.40.png
    Screenshot 2022-11-25 at 20.19.40.png
    83.3 KB · Views: 15
platform ID should be 00001259

may not need deviceID (as you have that in wrong as well)

What is weird is that when I had the platform-id incorrectly set, the display colors were perfect, however the display vram was 650.7 MB (from memory) instead of the expected 1536 MB.

I also see that a real iMac18,2 has the i5-7500 processor but Radeon Pro 560 graphics. Probably using the iGPU for decoding? I have search and searched but cannot find someone who has gotten this working.
 
DVMT is at 128MB (I doubled it a few tries before). Removing the device ID, which I think is the correct value now that I know how to properly enter it, and the frame buffer (00001259 is another valid one which gives crazy colors as well). I tried 00002359 which is one several suggested in Whatevergreen FAQs just to see what would happen.. What is strange that the device is 0x5912b (=00001259) is listed when I specified 0x2359b (00002359). Is this value stored somewhere? Myconfig.plist as 0x5923 (=000002359) but Display still shows device as 0x5912. Anyway, same result. All I did was delete the device-id line. I am going by this:

WhateverGreen/FAQ.IntelHD.en.md at master · acidanthera/WhateverGreen · GitHub



View attachment 558750View attachment 558751
then you do not need framebuffer-patch-enable if you can set dvmt to 64MB+
 
then you do not need framebuffer-patch-enable if you can set dvmt to 64MB+

I removed framebuffer-patch-enable. This made no difference. I tried id=59120000 (i know not per Guide) and device-id=1259 and the colors are fine. Same if I remove device-id. VARM is 7M and now I get 24-bt graphics, instead of 30-bit. Whatever combination I try, whenever I get 24-bit graphics the colors are OK. I also checked my 8300 hack with Radeon RX 560 dGPU I see that it shows 30-bit graphics. iMac18,2 has the same video. Is that a clue what to try next? Is the 0.8.6 Guide correct for Ventura?

Edit: I am using an DP to HDMI cable. Could that be an issue? Perhaps I need a DP to DP cable?
 

Attachments

  • Good colors.png
    Good colors.png
    28.4 KB · Views: 24
  • Bad colors.png
    Bad colors.png
    33.1 KB · Views: 22
Last edited:
I removed framebuffer-patch-enable. This made no difference. I tried id=59120000 (i know not per Guide) and device-id=1259 and the colors are fine. Same if I remove device-id. VARM is 7M and now I get 24-bt graphics, instead of 30-bit. Whatever combination I try, whenever I get 24-bit graphics the colors are OK. I also checked my 8300 hack with Radeon RX 560 dGPU I see that it shows 30-bit graphics. iMac18,2 has the same video. Is that a clue what to try next? Is the 0.8.6 Guide correct for Ventura?

Edit: I am using an DP to HDMI cable. Could that be an issue? Perhaps I need a DP to DP cable?

device-id=1259 is invalid


if you can get it to work, then what is the issue?

try not to use adaptors etc, as they can cause issues
 
device-id=1259 is invalid


if you can get it to work, then what is the issue?

try not to use adaptors etc, as they can cause issues

Actually it should be 1259000, but that makes not difference. I can even remove device-id line and Ventura still shows the right Device Id as 0x5912 but stil wrong colors.

The colors are screwed up when I follow the 0.8.6 Guide and use the frame buffer given for Kaby Lake. Plus it takes several seconds to maximize/minimize Safari, so I am concluding there is no acceleration either. Same frame buffer is in WhateverGreen FAQ:



When I used some other number like (59120000, for example, which is obviously in the wrng format) I get right colors and still not hardware acceleration.

I will get a DP to DP cable to try.
 

Attachments

  • Screenshot 2022-11-26 at 18.46.23.png
    Screenshot 2022-11-26 at 18.46.23.png
    31.4 KB · Views: 21
device-id=1259 is invalid


if you can get it to work, then what is the issue?

try not to use adaptors etc, as they can cause issues

I got a DP-Dp connector and used my 2K monitor to test. Same result. There seems to be some acceleration because I can rotate the Chess board smoothly, but dock is not transparent, and it takes (literally) seconds to minimize/maximize Safari window and the animation is slooow. However, dragging windows on the desktop is pretty snappy. The colors are still wrong. I attached my EFI file, screen captures of the Graphics/Display windows with both monitor connections. I also attached IORegistry. Not sure what to look in there for.

Edit: I took a picture of the screen with wrong colors with my phone. When I attached it I see that the colors on the icon on my screen are correct.

I really appreciate your help @Feartech @trs96. Thank you. It seems so close.

The only other unresolved issue are POST error (005) which is a minor inconvenience and sleep, with which I could live with.
 

Attachments

  • Dp to DP connection 2k monitor.png
    Dp to DP connection 2k monitor.png
    40.9 KB · Views: 42
  • EFI.zip
    9.3 MB · Views: 77
  • IoRegistry.ioreg
    6.3 MB · Views: 25
  • Bad colors.png
    Bad colors.png
    33.1 KB · Views: 46
  • PXL_20221129_025044810.jpg
    PXL_20221129_025044810.jpg
    3.7 MB · Views: 44
Last edited:
I think I see the problem. Red and Blue colors are reversed on the display. Whites are OK because RGB colors combine into while. When I go on www.tonymacx86.com the apple on my monitor is blue and the little leaf is green. On my MacBook the apple is red and the leaf is green. Hence I conclude that the Red and Green colors are reversed. The same is the case on my other monitor which is connected with a DP>DP cable. DP->HDMI and DP->DP cable both work fine on my other build. Colors ar fine in Windows. So it must be the ProBook outputting the wrong color signals on the DP port.

Please help explain and how to fix.
 
I think I see the problem. Red and Blue colors are reversed on the display. Whites are OK because RGB colors combine into while. When I go on www.tonymacx86.com the apple on my monitor is blue and the little leaf is green. On my MacBook the apple is red and the leaf is green. Hence I conclude that the Red and Green colors are reversed. The same is the case on my other monitor which is connected with a DP>DP cable. DP->HDMI and DP->DP cable both work fine on my other build. Colors ar fine in Windows. So it must be the ProBook outputting the wrong color signals on the DP port.

Please help explain and how to fix.
you may have to inject your EDID to get the correct colours

may have to add the property:
AAPL00,override-no-connect
into PciRoot(0x0)/Pci(0x2,0x0)

this may help:
 
Back
Top