Jump to content

Hervé

Administrators
  • Posts

    9905
  • Joined

  • Last visited

  • Days Won

    548

Hervé last won the day on April 9

Hervé had the most liked content!

About Hervé

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Hervé's Achievements

Brigadier General

Brigadier General (17/17)

1.2k

Reputation

28

Community Answers

  1. Sorry, I've no idea what you did. You're gonna have to be a lot more specific. You've not even specified what you use in terms of bootloaders.
  2. See here and use the latest versions of the kexts mentioned in the thread: https://osxlatitude.com/forums/topic/13140-solved-dw1560-bluetooth-stopped-working
  3. Note to all those who would be confused on the matter: this thread is for information only and about wireless service in Sonoma, not Bluetooth. All support request for Bluetooth posted here will be deleted without notice.
  4. If you want to consider a suitable build with SSDTs only, I suggest you post the raw/vanilla DSDT extracted from BIOS and the patched one. We'll then be able to examine the differences between them and suggest SSDT alternatives to the patched DSDT.
  5. I wouldn't bother to try and use OpenCore or follow the Dortania guidance for an old C2D laptop. OpenCore has no proper support for CPU power management on these platforms. Stick to Clover, knowing that using SSDTs only is not restricted to OpenCore at all and can of course be used with other bootloaders such as Clover.
  6. It's just a matter of framebuffer and matching of connectors with physical outputs. On rare occasions, certain outputs may not work at all. Patching the HDMI port to type 00080000 is only required to gain HDMI output, it's not required for video output. All I can suggest is that you experiment with the various CFL/CML framebuffers and check them all out for HDMI output.
  7. That's entirely cosmetic and bears no influence on your Hackintosh. Furthermore, it probably only appears in an add-on application such as About this Hack. If you want the proper CPU model to be reported, inject its CPUID in your OC config.
  8. Seems your HP 400 G6 is fitted with a Comet Lake CPU given that the reported iGPU id is 0x9BC8. It's a desktop platform, yet you use mobile framebuffer 0x3E9B0000 which natively defines the following 3 ports: [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 00000800 02000000 98000000 01050900 00040000 87010000 02040A00 00040000 87010000 This is not suitable given that 1st output port (i.e. connector con0) is defines as an LVDS port. DP output appears to attach to 2nd connector con1 in your IOReg. I would suggest you opt for the desktop framebuffer recommended in the WEG user Manuel, i.e. 0x3E9B0007 which defines the following 3 ports: [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x000003C7 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x000003C7 - ConnectorDP [3] busId: 0x06, pipe: 8, type: 0x00000400, flags: 0x000003C7 - ConnectorDP 01050900 00040000 C7030000 02040A00 00040000 C7030000 03060800 00040000 C7030000 This should give you a better chance to obtain DP + HDMI output. If you do, identify which connector is DP and which connector is HDMI so that you may patch the HDMI one accordingly (i.e. set its type to 00080000) should you wish to enjoy HDMI audio. You may also want to switch SMBIOS from iMac20,1 to MacMini8,1.
  9. Try with SecureBootModel set to disabled.
  10. https://github.com/OpenIntelWireless/itlwm/releases Grab the alpha version labeled Sonoma14.4 if that's the macOS version you're running.
  11. You're probably using an unsuitable kext for your TouchPad. Identify your model. Check what's available in existing bootpacks for your laptop model, similar ones or models with similar TouchPads.
  12. Ok, you meant Sleep when on mains/AC. What are your sleep settings? Did you disable hibernation?
  13. Ok, so dGPU remains disabled on warm reboots from macOS into Windows. There are only a few ways to address this: you opt for the boor arg option rather than the patched ACPI code. you call on your EGPU ACPI code on macOS shutdown to re-enable the dGPU; that should be handled by an event that you need to identify. Maybe one of those EV methods. you power off your laptop when you want to boot Windows.
×
×
  • Create New...