Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. Today
  3. @fechaa My posted EFI (attached to Post #1) is specifically for my hack which uses DP->DVI adapters for graphics. The DeviceProperties (graphics and audio) are those necessary for working graphics and working wake from sleep with DP->DVI adapters. Since you are not using graphics adapters (i.e., you have DP->DP), you will want to follow this suggestion in the instructions The graphics DeviceProperties in the provided config.plist are for systems using DP->DVI adapters for their displays. You may need to edit your own config.plist DeviceProperties if you are using different displays (e.g. if you are using DP or HDMI ports without adapters). See here for example DeviceProperties that may be suitable for your graphics. That should get you pointed in the right direction. You'll need to modify DeviceProperties for both PciRoot(0x0)/Pci(0x1F,0x3) and PciRoot(0x0)/Pci(0x2,0x0). EDIT: I do not use Open Core configurators (like OCAT). I have nothing against them and see that many have success when using them. It's just that I don't want to introduce another variable into my testing and debugging (i.e., I don't want to have to consider a possible OCAT bug if I have any problems with my modified EFI). I use Apple's Xcode to edit my config.plist and I manually update/replace OC driver files, kexts, etc. After you modify your config.plilst, use Open Core's ocvalidate in the downloaded Open Core package (Utilities / ocvalidate).
  4. Hiya, I am not familiar with your machine but I found this example here - https://github.com/search?q=Dell XPS 15 9570&type=repositories - among others but this was the most recent. Inside you'll find the EFI Folder that you can try also take notice of the 'Read Me' note inside. I have taken the liberty to update OC and kexts versions to the latest. If successful, you'll have to furnish the config.plist with your own machine's data, i.e S/N, ROM, MLB etc. Good luck. xps9570-hackintosh-main.zip
  5. Hi Community, I'm new to the Community and need some help. On my Dell XPS 15 9570, I'm attempting to install macOS Ventura, but I'm having trouble. The specifications of my system are as follows: CPU: Intel Core i7-8750H GPU: NVIDIA GTX 1050 Ti/Intel UHD 630 RAM: 16GB SSD: 512GB NVMe I've followed different guides and created a bootable USB with OpenCore. The installation starts, but it gets stuck at "Apple logo" screen. I suspect it might be related to my graphics configuration, but I'm not entirely sure. I've disabled the NVIDIA GPU in the BIOS and configured the config.plist according to the OpenCore guide for Coffee Lake but no luck so far. Has anyone installed macOS Ventura successfully on a setup similar to this one? Any advice or pointers would be extremely valuable. I appreciate your assistance in advance! With Regards, James Bolt Flutter Online
  6. @AslashA I think that @lorys89 fork doesn’t need the boot arg. Try yourself.
  7. Hello, first of all, many thanks to deeveedee for maintaining such a good work over the years for keeping the HP 800 G4 Mini uptodate. Just for fun I installed 13.6.7 on a HP 800 G4 Mini with 65W i5-8600 and it was the easiest installation I ever had. I have been using Clover over the years until some time ago on three laptops and a desktop with some fiddling around for making them up and running. I also tried a HP800 G1 SFF with opencore, which gave me a lot of headache, because minor changes in config.plist and kexts broke the installation. I got it running but not as stable as the other computers before. Therefore I do have a lot of respect not to change too much to the config.plist in post #1 of this thread for OC1.0 R001 version. In fact I have two left hands as it concerns computers. To enter MLB, serial, uuid, Rom I used OC configurator (version for OC0.98) with success. However OCAT (version 240001) did not work (...two left hands). It gave me errors when opening the current config.plist, so I used OCC instead, despite people warning against it. In post #6 (Rev. 1.0.7, 27 march 2024) of this thread it says "delete No-hda-gfx from the config.plist" for the case that one would like to have audio on the monitor speakers. Monitor is connected DP to DP with plain DP cable. Is it possible to simply delete the no-hda-gfx key under DeviceProperties (in device 0x1f,0x3) in OC configurator? Maybe I could also simply delete the three lines <key>No-hda-gfx</key> <data>AAAAAA==</data> <key>device_type</key> in the config.plist text-file. Or is it in addition necessary to add or modify the keys in 0x2,0x0 or whatever device to get the sound on monitor speakers? Thank you for your help.
  8. Yesterday
  9. @PG7 Did you see this?
  10. It seems that Bluetooth is not just a hack problem. My real Mac is losing the keyboard and mouse connection when starting up.
  11. If I use kext forked by @lorys89, is the revpatch=sbvmm value always active? Or is it only activated when updating? Who can tell?
  12. @fed9027 You are welcome. Please add a signature to your Account Details.
  13. Thank you, I did come across that one but they are beta versions. I was ideally hoping for the final release.
  14. Maybe this site will have what you want: https://install.appcenter.ms/orgs/rdmacios-k2vy/apps/microsoft-remote-desktop-for-mac/distribution_groups/all-users-of-microsoft-remote-desktop-for-mac
  15. Use this and done. EFI LindaH Final.zip Don't need change or dd nothing, just enjoy!
  16. The site is acpica.org but don't expect to find explanation about names in YOUR dsdt. You need somehow programming skill to rule what is what. Anyway, why you still don't have a signature?
  17. @Slice This user has also a repo for Clover: https://github.com/5T33Z0/Clover-Crate
  18. Thanks again everyone for helping out, I was even able to take my old installation from my old machine and everything just worked OOB, even filevault! 🤩 I still wanted to understand where I went wrong because this is really a really fascinating world with endless directions to follow and learn. I spend the whole evening reading up and trying to figure out, and if I understood it correctly, my issue was the USB controller being defined for PXSX in the DSDT as _SB.PC00.* when I made it with SSDTime? I disassembled the AML (btw, OEM ID of LindaH 😍) and it has none of this in the Scope (\_SB.PC00) but only the generic USB injecting (I'm going to map the USB next). When comparing the AML files, It is wild how little definitions were actually needed VS what the generator did. btw, it is really hard to find any good websites with info on this stuff and what all these names and acronyms mean
  19. OK, but I tried "latest" and it is not working. The working solution is "1.4". Can you verify your line?
  20. Hi @Slice It is line 267 in buildme script. Thanks.
  21. Last week
  22. this lilu fix from github might be important https://github.com/acidanthera/Lilu/commit/a7fc69b7cc3ebb08ed72c41e873ae7c5f2451731 here's the binarys from github build i'm using this lilu debug version for building nblue/whatevergreen Lilu-1.6.8-DEBUG.zipLilu-1.6.8-RELEASE.zip use the debug release only if you using xcode to build binarys use the lilu release in the /EFI/Kexts folder to update lilu this are the new binarys of nblue/whatevergreen bulid for new lilu WhateverGreen.kext.zipWhateverGreen-master.zipNootedBlue.kext.zipNootedBlue-master.zip
  23. Can I please take credit for the recommendation? Just kidding. Enjoy your machine. Well done maestro, shall we say another satisfied customer??!! Not that I had any doubt in your ability to come to the rescue.
  1. Load more activity
×
×
  • Create New...