Jump to content

Hervé

Administrators
  • Posts

    10026
  • Joined

  • Last visited

  • Days Won

    561

Everything posted by Hervé

  1. Make sure to Reset NVRAM each time you make a change to your OC config. If all that you did was add/delete the afore mentioned boot args, no reason why you would not boot back into Big Sur.
  2. Given the continuing lack of clarity, same comments and questions as before: Webcam is USB internal and is therefore expected to be listed in SysInfo->USB. Is it the case? If it's not you still have not properly mapped your USB ports (I noticed you still have XhciPortLimit enabled). If it is, consider the webcam unsupported. You may also want to check that the camera works in, say, Windows to rule out a physical problem (bad connection, defective device). All in your hands...
  3. 2 x 1st comments: I don't think yo need that SSDT-ALC292 table. I don't think you ought to have those power settings defined under HDEF device in your patched DSDT. In your Clover config: remove -xcpm and kext-dev-mode=1 boot args; those are completely deprecated (kext-dev-mode=1 applied only to Yosemite!). InjectIntel and ig-platform-id no longer need to be enabled/defined with Lilu + WEG kexts; the patched DSDT also contains the properties injection required for Haswell HD4x00; no need to duplicate those settings everywhere. there are lots of kext patches that can be removed. The deprecated AppleHDA patches are disabled, just remove them; same applied to IOGraphicsFamily patches, totally deprecated Basically, do clean-up your config to return to a sound base without all those duplicates and unnecessary settings.
  4. The E6440 I had several years ago was also fitted with ALC292; headphones regularly went silent and I always had to put the computer to sleep and wake it to recover headphones audio. I would also have no audio at all if warm booting into OS X:macOs from Windows; I always had to do a cold boot. Post your EFI folder so that we look at it in case there's something obvious in it on the audio front.
  5. Haswell platforms with HD4x00/5000 iGPUs remain fully supported. The only requirements is to switch to MacBookPro11,4 SMBIOS. Otherwise, same story as mentioned before: macOS 12 beta1 installs and runs with the exact same settings as Big Sur's (Clover or OpenCore). HD4400 VGA output remains supported OOB!
  6. Lilu & PlugIns now updated to support macOS 12 Monterey. Available off the Dortania Opencore kexts repo. After updating the kexts, the beta boot args are no longer necessary. Early reports of problems with Bluetooth. Remove your BT injectors and patched kexts if you encounter issues.
  7. Today, you should avoid patching a DSDT and concentrate of patching ACPI stuff through bootloader config (eg: device/function renaming) and SSDT substitutes.
  8. You're referring to something specific affecting the Latitude Precision M 4800/6800 Series. Matter has been discussed at great length In numerous threads on the forum over the years. It's not a matter of Kepler supporting or not supporting eDP displays, you got that wrong. Black internal (eDP) screen situation with Optimus disabled has endured for years due to physical implementation choices made by Dell and lack of Optimus support under OS X/macOS due to Apple's own choices. It's got nothing to do with Kepler drivers and macOS 12 Monterey will change absolutely nothing on that front.
  9. No reason why a Kepler card could not support eDP but your query is too vague to be properly answered. Clarify the exact nature and specifics of your query.
  10. Bluetooth is a little buggy for the moment in Monterey 1st beta. You'll probably have to wait. Also keep in mind that, if you've kept the same versions of Lilu + PlugIns as ou used in Big Sur, you probably need the beta boot arg for all. As stated at IM, PMHeart has now updated Lilu & PlugIns for Monterey so I would advise you to update and renew your tests. Just check the usual Dortania repo: https://github.com/dortania/build-repo/releases
  11. The bootpacks posted in my guides provide all you need for the D830. Everything is already tuned for optimum performance: graphics and CPU power management; as such, you have nothing further to do. DW360 is an old Bluetooth 2.0 module that was optionally fitted to the old D series and many other Dell laptops from 13-to-15years ago. If all you want is very basic support for things like Bluetooth mouse or connections to Bluetooth speakers, that'll probably do but if you want full Apple services like AirDrop or Continuity, forget it. These require a fully supported BT4.0 module in which case you would want an appropriate combo card (Wifi + Bluetooth). The D830 offers 2 x full-size mini-PCIe slots: 1 x WLAN and 1 WWAN. If you want 802.11ac wireless + fully supported Bluetooth, go for something like a real Apple BCM94360xxx model installed into a mini-PCIe adapter that you'll fit into the WWAN slot. Although it really is an ideal card -if not THE ideal one-, you may have to stay away from the BCM94360CD model because it requires 4 x antennas and, instead, look at other models that use 2 or 3 antennas only. Pay attention to the card's antenna connectors because the D Series have the old bigger antenna plugs rather than the smaller ones fitted to newer M.2 cards. There are adapters though, you can look this up. Such adapters would be required if you opted for an M.2 card installed on a mini-PCIe adapter (eg: Fenvi BCM94360NG, DW1820A, etc.). You found the inventories in the Wifi technical info section, look at the other useful threads posted there too. But it's all hardly worth it in 2021, those C2D Latitude D series laptops really are long in the tooth now and mostly obsolete for recent macOS versions.
  12. Try it and let the community know. If you check the "macOS 12 Monterey on Unsupported Macs" thread at MacRumors, you'll see that some people already got Ivy Bridge MBP10,1 running Monterey and graphics acceleration for HD4000 is not achieved of course but is an on-going research matter. No problem for the Kepler dGPUs of course...
  13. You run an incorrect setup and need to review and fix it. For instance: renaming of _OSI method to XOSI but no SSDT-XOSI table. They go together! totally incorrect iGPU property injection for the Haswell cursor memory size (invalid key, invalid type!); that's the most likely reason you experience those crashes... duplicate and inappropriate properties injection in your patched DSDT for your iGPU (other devices not checked); that's also likely to contribute to the crashes... https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md
  14. Further to the announcement made at today's WWDC event, Apple released the 1st beta of macOS 12 Monterey to developers. It can be downloaded after installing the latest devs Beta access utility available in all good places such as here or by using the associated InstallAssistant as stated here. On the bad news front, not much to say other than support for Ivy Bridge HD4000 is dropped as could be expected given that it remained unofficially supported in Big Sur. On the good news front, we'll note that: although support for pre-2015 Haswell-based iMac/MacBook Pro/MacBook Air models appears officially dropped, support for Haswell-based Mac mini Late-2014 has remained and with it, support for Haswell graphics! support for nVidia Kepler card has remained too! Other good news is that Monterey beta1 installs with the exact same settings as Big Sur. Pending the usual necessary kexts' update, the only additional requirements I found for my Skylake/HD520 Latitude E7270 were: Lilu's -lilubetaall boot arg to avoid system reset. WhateverGreen's -wegbeta boot arg to avoid KP on wake. Other than that, nothing at all and I was even able to install, boot and run Monterey beta1 with Clover r5133. Ace! So far, but it's only been a very very short time, everything works fine and as per Big Sur. Installation was much much quicker than what I have experienced with all versions of Big Sur and it only required 2 x reboots. Bootloader recommendations: Clover r5133 or later OpenCore 0.6.9 or later
  15. Fenvi BCM94360NG works OOB with full Bluetooth support, so...
  16. Or you disable the entry for USBInjectAll and add/enable USBMap... Just the usual, really.
  17. Assuming the E5420 specs will be similar or very close to the E6x20 models, you can lookup existing guides for those and build from there. Use Clover, it'll be easier.
  18. Cable certainly appears to meet the 4K @60Hz specs so that's out of the way. Given that you're now using a DP-only nVidia card, your HDMI2.0 property injection for your iGPU is irrelevant and you should concentrate on nVidia dGPU properties. Consider injecting nVidia usual properties and envisage investigating the NVCAP matter; this defines the output ports.
  19. In the future, please try and extract the main info for specs in order to post the essential stuff rather than your original raw dump that hardly anyone will bother to read... i7-10850H is Comet Lake; it was therefore not appropriate to use my Kaby Lake R guide for your system. Look up any existing Coffee Lake or Comet Lake guide but keep in mind that you may not manage to obtain graphics acceleration for your UHD 630 iGPU. This would thereby render your platform unworthy as a Hackintosh.
  20. Your adapter has to be 4K capable; not all are. I have an Ivanky mini-DP to HDMI adapter and it's limited to 1920x1080@60Hz; I have the 4K-capable version on order.
  21. Kepler GK208-based GT710/720/730 are only capable of 4K @24Hz (or is it 30Hz?) given that they have HDMI1.4 connectors so what you obtained was perfectly normal. I got exactly the same out of my GT730. The great thing is that this is obtained completely OOB. Getting 4K @60Hz out of your Skylake HD530 could turn into quite a bit of a challenge. If you check the specs go your i5-6500 CPU, you'll see that you get only 4K @24Hz out of HDMI but DP is supposed to support 4K @60Hz. You'll probably have to add some WEG parameters and it's also highly likely that you'll have to adjust/increase DVMT to support 4K.
  22. Use the forum Search facility; if you don't find anything, there would be no tutorial, no. Seek inspiration in existing guides for Ivy Bridge laptops. You stated you have a Full HD display so I'll assume it is HiRes 1920x1080. This requires to use single-port Capri FB layout 0x01660004, not 4-port LoRes layout 0x01660003. Patching of the HiRes layout will therefore be required should you wish to gain DP and/or HDMI output. You may look this up in our dedicated HD4000 patching guide.
  23. I would invite you to consult our threads about minimum requirements for running OS X/macOS and supported/unsupported graphics. https://osxlatitude.com/forums/topic/2998-min-requirements-for-os-xmacos https://osxlatitude.com/forums/topic/8238-supportedunsupported-gpus-graphics-cards I would invite you to consult Dortania's most excellent documentation, starting with the pre-requisites: https://dortania.github.io/OpenCore-Install-Guide/prerequisites.html#prerequisites
  24. Is that a question? If so, it depends on the hardware specs.
×
×
  • Create New...