Jump to content

Hervé

Moderators
  • Content Count

    9627
  • Joined

  • Last visited

  • Days Won

    391

Everything posted by Hervé

  1. I see: no display detected on 1st output port. I would suggest 2 x things: try MBP11,3 SMBIOS inject boolean property @0,AAPL,boot-display (set to 1) to 1st output port
  2. You could possibly try and inject properties for the 1st output port NVDA,[email protected] in an attempt to redefine its properties; can't say if it'd work but nothing to lose really. Also, in order to avoid all confusion on the matter, I'd rename GFX0 (@00020000) to iGPU, then PEGP (@00010000) to GFX0. Try and post a zipped copy of your IOReg if you can.
  3. eDP models were out of luck as far as built-in LCD is concerned (see @nsmartin last post in M4800 thread I linked above). I've not seen anything that changed this in the last 4 years. @Xeon3D quite clearly confirms this too... This being said, I remember the days when Precision M4600 with nVidia graphics would too end up in a black screen when using MBP8,x Sandy Bridge SMBIOS. See here (Chameleon/Enoch) and here (Clover) for instance. People obtained a black screen unless they using a specifically tuned MBP6,x SMBIOS where the board-id was replaced by that of nVidia GPU-based MBP10,1 (Credits to @DuongTH from memory). MBP8,x models were either HD3000 (MBP8,1) or dual HD3000 + AMD Radeon HD 6xxx graphics (MBP8,2/MBP8,3). So, given that: MBP6,x were Arrandale platforms running with dual 1st gen Intel HD + nVidia GeForce GT 330M (Tesla 2.0 GT216) graphics MBP10,1 was Ivy Bridge platform running with dual Intel HD4000 + nVidia GeForce GT 650M (Kepler GK107) graphics MBP11,1 was Haswell platform running with Intel Iris 5100 graphics only MBP11,3 was Haswell platform running with dual Intel Iris Pro 5200 + nVidia GeForce GT 750M (Kepler GK107) graphics MBP11,5 was Haswell platform running with dual Intel Iris Pro 5200 + AMD Radeon R9 M370X (Tropo GCN1.0) graphics and that: Precision M4800: nVidia Quadro K1100M is Kepler GK107 nVidia Quadro K2100M is Kepler GK106 AMD FirePro M5100 is Venus GCN1.0 Precision M6800: nVidia Quadro K3100M is Kepler GK104 nVidia Quadro K4100M is Kepler GK104 nVidia Quadro K5100M is Kepler GK104 AMD FirePro M6100 is Saturn GCN2.0 it may be worth looking into the SMBIOS matter again even as a desperate last attempt. Can't remember if that were ever considered or looked into in the past. NB: MacBookPro11,x were last Mac laptops fitted with nVidia graphics to date.
  4. If you're installing 10.15.4, that's normal because my pack contained an XCPM-enabled Clover config. 10.15.4 breaks this as stated in our article about the update. You need to revert to good old SSDT-based power management method using the attached config + your CPU-specific SSDT generated using Pike R Alpha's well-known script: config.plist.zip The guide has just been amended to that effect.
  5. As stated in our March 2020 news article, 10.15.4 breaks XCPM capability. If you used that, revert to good old CPU-specific power management SSDT generated by Pike R Alpha''s well-known generator script. Revised Catalina pack #2 provided to that effect. But, as suggested by @Bronxteck, XCPM should be back with Clover r5117 or above. I certainly verified this with r5118. Clover_r5118.pkg.zip
  6. Broadcom BCM43224 14e4:4353 is subject to whitelisting: And, very obviously, those DW1820A-related injected properties do not apply to your Apple card so remove them. It's always essential to pay attention to full computer's hardware specs, especially when re-using someone else's config files...
  7. Boot in single-user mode or boot your USB installer. One or the other should allow you to: mount your Catalina partition and remove the offending kext from /L/E and rebuild your cache or mount your EFI partition and remove the offending kext from E/C/k/O But I must say that your KP seems more related to that EnergyDriver kext. Isn't this installed by IntelGadget app? I'd say the kext just does not agree with Slice's HWMonitorSMC2. Maybe you should revert to the previous version of the FakeSMC-related app.
  8. You go to the Options menu at Clover main boot screen and you manually enter that text as a boot option.
  9. Hervé

    E7440 WIFI problem

    It's not a good card for Hackintosh purposes. Replace it with a Broadcom compatible model. Of course, it's important you consult the correct wireless card inventory to that effect and read things with all due attention...
  10. You're never going to get anywhere with such a Clover config. You can't just select all ACPI fixes and expect things to work. Undo all that and only select those fixes that may be needed like FixRegions, FixHeader, Halt Enabler. As for graphics, I believe Clover Configurator explains things pretty clearly: As far as I knew, Intel HD510 was unsupported but, according to old discussions from 2017 with Rehabman that I found after a quick search, support would have been added in macOS Sierra at some point. Indeed, looking at the SKL framebuffer kexts of High Sierra, Mojave and Catalina, I see that the list of supported devices does include 0x19028086. <key>IOClass</key> <string>AppleIntelFramebufferController</string> <key>IOMatchCategory</key> <string>IOFramebuffer</string> <key>IOPCIClassMatch</key> <string>0x03000000&0xff000000</string> <key>IOPCIPrimaryMatch</key> <string>0x19168086 0x191E8086 0x19268086 0x19278086 0x19128086 0x19328086 0x19028086 0x19178086 0x193B8086 0x191B8086</string> <key>IOProbeScore</key> <integer>80005</integer> <key>IOProviderClass</key> <string>IOPCIDevice</string> <key>IOSourceVersion</key> <string>0.0.0.0.0</string> <key>PMTControl</key> <dict> <key>DisplayEngineCounting</key> <integer>0</integer> </dict> So, remove that GPU id faking you've inserted in your Clover config. No guarantee it'll work though, I see plenty people reported lots of graphics glitches/defects for HD510.
  11. Skylake HD510 is unsupported. You'll need either a different CPU with a supported iGPU or a compatible add-on graphics card.
  12. Guys, you may want to consult this old thread that explained a few things... And @Xeon3D's repo is quite extensive on the matter too. It's a highly recommended reading as far as I'm concerned.
  13. We have a dedicated thread to M.2 compatible cards. Why don't you consult it?
  14. You may adjust the port type definitions in the tool if required. Apart from that, it's that simple, yes.
  15. Please consult our FAQ section and search the forum before posting. Thank you.
  16. Hardly any discussion/threads/posts about OC on this forum. Given the amount of issues reported with OC at InsanelyMac, you may wish to stick to good old Clover. OpenCore is still quite far from being what most of us consider mature yet. But, by all means, feel free to experiment and post your results/feedback.
  17. It's been said several times in people's posts but I too confirm that booting the 7490 with my patched DSDT usually causes issues. For some reasons that I've yet to identify, it works for me because I boot Clover off an SD card. However, if I boot Clover in a more classic way off a HDD or SSD, I cannot use the patched DSDT.
  18. According to @influenist, this WWAN module works with the kext he posted here.
  19. You could do a bit of research, you know... https://www.insanelymac.com/forum/topic/339175-brcmpatchram2-for-1015-catalina-broadcom-bluetooth-firmware-upload/
  20. It appears you chose to use NonPatchRAM2 AND PatchRAM3 and inject kexts that are not for injection but caching... I would suggest you read up on the matter and opt for the latest Bluetooth injector/firmware patching build (v2.5.3 last time I checked), especially if you inject kexts rather than cache them. Right now, you're doing things incorrectly.
  21. What version of Clover are you using? What version of Catalina are you installing? If 10.15.4, make sure you use at least Clover r5107 and, as stated in the 10.15.4 news update, you may have to boot with -disableigfxfirmware boot parameter until your installation has fully completed.
  22. No problem to be expected...
  23. That Bluetooth-related setup is incorrect. You never said if you use the same SSID for 2.4 and 5GHz. If this is the case, there could be a chance that, on wake, your laptop picks up the 2.4GHz network for which there is interference from Bluetooth. If at all, possible, differentiate 2.4 from 5GHz network using different SSIDs, then compare behaviour. NB: no double post on the forum please.
×
×
  • Create New...