Jump to content

Precision 5510: unable to install Ventura


Justin Wallis

Recommended Posts

I tried Booting Ventura with the Monterey 4k EFI with the added the bootarg -no_compat_check. I tried it with the original 13,3 but also 14,1 and 14,3 (on the plist and within the USBPorts_5510.kext). I reset the nvram before reboots, and also checked the patches were still applied.

 

It started every time, but without acceleration

 

I wonder how dnsdk's 5510 Ventura 4K / 530 EFI still has glitches on mine. Isn't it the same hardware?   Do you think i should try his EFI with the BIOS patches undone. How does he do it without the framebuffer-men, etc? It says nothing in his thing about if he patched his BIOS.  Just some things i was thinking. Not sure if valid.

 

And I also wasn't aware that is was possible to have 64G of DDR4 Ram. 

164303575_ScreenShot2022-12-29at7_32_03PM.png.048071f2bf415c7f18f349c61dbf4833.png

How do i do that? I thought the max was 32gb for this laptop? I asked him both questions on Github, maybe i will get a reply

 

Will the trick in the with the Legacy Patcher you posted on your E7450 page work with mine maybe?

Link to comment
Share on other sites

  • Administrators

You need to understand that -no_compat_check boot arg applies to SMBIOS/Mac models dropped by the targeted macOS version. The parameter's sole purpose is to allow installing and/or booting a given macOS version on an officially unsupported platform; it's of no (direct) use for graphics acceleration. As such, it's entirely useless with SMBIOS MBP14,x, these Mac models remaining officially and fully supported under macOS Ventura. You would only use it with SMBIOS MBP13,x.

 

Until now, unlike Haswell and Broadwell counterparts, Skylake systems have been able to obtain full graphics acceleration by using/faking KBL graphics with KBL SMBIOS and without any need for OCLP patching. Granted graphics acceleration has been difficult to obtain on HD 530 iGPU, not to say impossible on some platforms. You may consult the threads I had posted for Ventura beta (now in the Archive), my current E7270 guide or the initial Ventura beta thread at InsanelyMac. This being said, feel free to experiment with OCLP if you wish.

 

The Precision 5510 EFI you've referred to clearly makes no use of stolenmem/fbmem patches/injections because DVMT already has the required value (64MB appears to be the default value according to your screenshot on p2). Do take good note that, if DVMT is set to 32MB, it is absolutely necessary to patch it for 4K output. Patching stolenmem and fbmem framebuffer properties won't do. That is clearly mentioned in Jake's FAQ on DVMT BIOS patching to which you had previously referred. In your case, you may experiment patching DVMT to higher values than 64MB.

 

It also looks like you need to learn about the stolenmem/fbmem patches so you have some catching-up to do; it's been covered in all angles since 2015 when gurus such as Firewolf troubleshooted the issue of KP on Broadwell platforms due to DVMT vs. BDW framebuffer native settings.

 

As for the RAM, it really is off-topic and unrelated to Hackintosh but it wouldn't be the 1st time Dell specs state something that's not entirely true on the matter (eg: good old Latitude D630/D830). How do you go about fitting 64GB of RAM? The answer is very likely to be so simple and obvious that it would leave you red-faced... Real question is whether you would need 64GB or not. But, again, off-topic, so let's close the subject.

  • Like 1
Link to comment
Share on other sites

Okay. Thanks!I   That clears a bunch up!   I've also been reading a bunch from the threads u said.

 

Precision 5510 with most updated BIOS doesn't have the DVMT settings. Is it okay that my bios patched to max 2048MB ?  I like max :) Or do i need to try other sizes as well?

 

I should try again device-id and AAPL,ig-platform-id numbers, but with using the numbers in dortania's display configuration. There is two sets of numbers for kaby lake hd graphics 630, so i will try them both and even try the two crossed versions of the numbers, as it says here:

 

945506731_ScreenShot2022-12-30at8_10_06PM.png.5073e0223cb373cbfb24241773fa4490.png

 

 

Also, when comparing dnsdk on left to Jake Lo 4K EFI on the right, dnsdk has #AAPL,slot-name, treats con-1-enable differently, has a device type VGA compatible device. I don't need those things, right? :)

33180551_ScreenShot2022-12-30at10_47_37PM.thumb.png.b036c28bf12c1405bfd39e0b9c316bf1.png

 

Does the IOregfile Help?

 

Does the ioreg output change when booting from different EFI's?

 

IOReg File (Updated to Correct File): 

https://www.mediafire.com/file/3o0u53q9u76nxf5/Precision+5510+4K+Jake+Lo+14,1.ioreg/file 

 

OC Folder from EFI: https://www.mediafire.com/file/3zcsw3ahv7e43ot/OC.zip/file 

 

The Specs:

487437942_Screenshot2022-12-30at10_56_09PM.thumb.png.02d04f29595c639f57a0f98725cc027d.png

 

The Glitch: 

Untitled.thumb.gif.1ed63622169bd25d557aac03bc8f63e5.gif

 

I'm going to try these Ram (64GB 2x 32GB 4Rx4 PC4-17000L DDR4 2133 MHz). Even if it only may help rarely or little with having 200 browser tabs open and a large amount of open apps, security camera apps etc

Edited by Justin Wallis
fixed IOReg file/link to Correct one
Link to comment
Share on other sites

  • Administrators

I get the impression you don't fully understand half of what you're doing/writing.

 

1) "BIOS patched to max 2048MB" ? Very much doubt you'd need to set DVMT to that much. I don't believe macOS framebuffers will make any use of that.

On 12/31/2022 at 4:55 AM, Justin Wallis said:

[...]

Precision 5510 with most updated BIOS doesn't have the DVMT settings. Is it okay that my bios patched to max 2048MB ?  I like max :) Or do i need to try other sizes as well?

[...]

 

2) '#' character is used to comment something out in a bootloader's config and boolean values can be expressed as decimal NUMBER or 32bit hexadecimal DATA types (0 is 0 and 1 is 1, no matter the size of the data unit you opt for). You also need to understand that some of those injected properties are purely cosmetic (eg: labels, IO locations, slot names, etc.).

On 12/31/2022 at 4:55 AM, Justin Wallis said:

[...]

Also, when comparing dnsdk on left to Jake Lo 4K EFI on the right, dnsdk has #AAPL,slot-name, treats con-1-enable differently, has a device type VGA compatible device. I don't need those things, right? :)

[...]

 

3) Your linked IOReg bears no relevance to the screenshots and OC EFI you posted (it shows Monterey kernel, MBP13,3 SMBIOS and SKL iGPU settings).

 

To top it all, the Dortania display documentation you refer to is incorrect; most likely due to copy/paste errors. For instance, there's no such thing as device id 1b59006 for Intel HD 630 iGPU; trouble is that it is totally misleading and the Dortania folks are not (re)known for acknowledging and acting on requests for documentation adjustments.

 

Looks like you're getting all confused (who wouldn't?). You need to do much further reading on the matter of properties injection and graphics settings. Or maybe it's time to give it a rest...

 

I can suggest these links to begin with:

  • Like 1
Link to comment
Share on other sites

You are correct! :) I have spent 1Week/yr on average to update/learn hackintosh since 2007 (following install tuts, minimal debugging) and I'm also not great at this.  I am also new / not sound on this the graphics patching topic.  You guys have done a load of brilliant work by the time I update the OS's (clean installs), and clone them (for only myself). Catching up on new things & remembering takes a while for me. Those links help!! TY!!

 

The Patch comment: (For Precision 5510) setup_var 0x432 0x4 seems to be correct For 4k screens which sets the  DVMT GFX Mem to Max. Which shows up as 2048 MB. I've just seen other screenshots where others use 0x3 for max memory, so i was just double checking for my own understanding, since i don't see much written at all about 0x4 being used for max mem. (Just to see if i needed to possibly test others)

 

TY for the explanation of the Device Properties!!! It rly helps!

 

I fixed the above link to the Correct / Matched IoReg file. (New Link, Sorry for previously incorrect one)

 

I'm reading all of those links. Everything seems correct to me, as far as i am aware. Not sure if i should tinker around with WhateverGreen boot flags? or if there is a more likely solution.

 

The chosen id properties seems correct choice: as stated in your docs / posts (and others) for spoofing Skylake 530 as KabyLake 630:  AAPL,ig-platform-id is 00001B59 and device-id is 1B590000  So there is no need to try others i'm guessing.

 

Is the type of glitch common? I feel like it is and i've had it before when dealing with acceleration issues. Separate and distinct from the "Garbled Screen" Glitch i've had (many years ago) at login. Not sure why, but I don't see anything relevant to my specific situation in the Known Issues / Glitches Section in WhateverGreen Intel FAQ.

 

Which is more likely to cause graphics glitch do you suppose?  Incorrect DVTM patch? Bad Install (would fresh install with updated .plist help?), And/Or incorrect plist configuration (bootflags / properties etc). And for No External Display Output

 

I haven't found anyone online that had proof of a working 5510 w/ Ventura & 4k screen & w/ no glitches.  I should have tried a laptop that was not in uncharted territory, long story short, i ended up getting one (ebay seller mistake). But, tbh, I always wanted a touch version. My first precision was sold to me as a touch version, but there wasn't a touch option in the BIOS. This is my 2nd Precision and by error, i got the touch vers. I wouldn't even mind spending up to another week to try to get it working, paying for shipping to someone who can, or if all that fails, i will just stick with Monterey for the 4k/Touch 5510. I'm just a sucker for new mac OS's if possible, i enjoy the features, and also maximum shelf (compatibility) life.

 

I'm going to work on getting and uploading OC debug file or error log from following the tut on the OC Install Guide: Debugging by dortania. I actually try not to ask stupid questions, make you guys upset or break rules. Thx for the help!!    

 

All The Files for Both Ventura / Monterey:

 

Precision 5510 OC 0.8.5 Ventura 4K Touch Intel Wifi/BT - Configured by Jake Lo

Screenshot 2022-12-30 at 10.56.09 PM.png

 

1393531551_GraphicsCheckHardwareSoftware.thumb.png.b48ee82e406de5a0c03ebd0569860040.png


Downloads:
EFI's
IOReg
Debug Log


Not Working Yet:
- Glitch/Defects (pictured above, mostly happens when scrolling browser & viewing youtube/video full screen)
- External Monitors don't work at all (neither through HDMI Port, Dongle/adapter or through airplay mirroring)

- Screen Mirroring through airplay also doesn't work (the my other ventura hack builds mirror w/ my tv's no problem) 

- Black Screen after Wake from Sleep (fn+f12 does nothing, i pretty much just never let it go to sleep)
- WIFI (turns on, nothing shows up) Wifi Works now somehow
- Bluetooth - Bluetooth is working now somehow

 


Precision 5510 OC 0.8.5 Monterey 4K Touch Intel Wifi/BT - Configured by Jake Lo

1939962302_Precision5510Monterey4KSpecs.thumb.png.ce4fcc8e0441ebe8a091ead92703bf40.png


Downloads:
EFI's
IOReg
Debug Log

 

Not Working Yet:
- Bluetooth  - Bluetooth is working now somehow

- Only One external Monitor at a time and not 2.  Works all 3 ways also, through HDMI, HDMI through usb-c dongle or adapter, and also works with airplay. Just one external monitor at a time :(.

- Black Screen after Wake from Sleep (fn+f12 does nothing, i pretty much just never let it go to sleep)

 

* I added the the OC Debug Logs and IOreg files, if you are able to help me debug, since i am in over my head. :) Just lmk and i will try your suggestions. I added as well as the  Regular EFI and Debug EFI's in the above downloads (if you have a 4k Precision 5510). I will try to test all the working functions listed in Ventura Build on Jake Lo's Precision 5510 Thread.  Thanks in Advance!

Link to comment
Share on other sites

After the past week of using this laptop with both MO and VE:

Both Wifi and Bluetooth started working for both OS's. Maybe after so many restarts? i'm not really sure why it wasn't or why it fixed. 

 

I got around to testing airplay mirroring and some other things. I updated the above post and added some minor details about the remaining issues.

 

I feel like if there was a way to fix the external monitor issues on both (MO is no Dual External Monitors, and VE is no External Monitors at all), i can live with the ventura glitches (since it only really happens scrolling on full screen), and black screen after sleep (since i can either just restart or never let sleep).

 

With the wake from sleep issue, I asked An from [Solved] Dell Precision 5510 black screen after sleep if he's tried ventura yet on his 4k precision 5510. I also tried the boot-args darkwake=no, (changed it from 0), and also "igfxonln=1", and still had the issue. He used the FixEDID patch in his post (i think he's using catalina / clover though, since his github is catalina / clover) to fix it? (myb not) I wonder if that is my option. Just searching around and trying different things. But, i guess fixing sleep can be caused by the other issues i have according to dortania guide on fixing sleep.  I guess i should probably focus on the monitor and glitch issues first, it seems like sleep issue should probably be last thing to try to fix after all else is working properly.

 

Let me know if you might know somewhere i may be able to research to fix, thank you!! 

 

I might post soon on a couple other forums and reddit to see if there is any insight out there.  I just feel like precision is the new latitude and worth the effort, if it's possible. Not sure i can do myself tho. I've always felt latitude was the best hack laptop ever, and the precision is just twice as fast. I hope they both work with upcoming OS's. 

 

Link to comment
Share on other sites

  • Administrators

Unrelated to HDMI output of course but note that reducing stolenmem to 34MB is not required if DVMT is set to 64MB or above in BIOS; also, it'll prevent support for 4K output, something the OP is after here...

 

For the rest, the only noticeable differences are:

  1. the use of KBL framebuffer 0x5916000 and KBL iGPU device id 0x5916.
  2. the lack of max pixel clock override.
Link to comment
Share on other sites

I've been using Ventura on the 4K Precision the past couple weeks, and, although not preferable, i can live with: 

1. The Graphics Glitch

2. No Extra Monitor

3. No Wake from Sleep.

 

This is why:

1. The graphics glitch; albiet definitely very disorienting, I use this laptop for working in the homelab, so I am not rly using it for fullscreen video, therefore the glitch isn't pronounced as much. I also noticed, SOMETIMES, if small things are constantly moving on the screen, such as a loading icon, it can set the glitch off, but that is somewhat rare, in my experience. That being said, it may still glitch about 60- 100x/hour for me, which is a lot, but most of the time, i haven't found it to be bad enough to switch to monterey. Close though, and definitely when watching video full screen.

 

2. No Extra Monitor doesn't suck as much, since I am using it as a mobile workstation, and i don't need external monitors as much.  If i do need 1 external monitor, i just reboot to the Monterey i have installed on the 2'nd internal hard drive. The 1 monitor limitation isn't that bad, since i am on the go with this laptop.

 

3. No wake from Sleep thing actually occurs on both Ventura and Monterey unfortunately, i've found out from using it (updated above post).  If i put it to sleep and wake it up immediately, usually it wakes without a black screen, but on both OS's, if it is sleep for more than a minute or two, game over, i have to hard restart the machine.  It sucks, but also not a dealbreaker for me, since this laptop has a twice as fast startup as compared to the E7450

 

All that as a drawback compared to non 4K model with no drawbacks, I still find use for it. Not sure if it helps anyone, but figured i'd mention this for those interested in the 4k/touch.  Okay, thanks for reading. 

Link to comment
Share on other sites

×
×
  • Create New...