Jump to content

Hervé

Administrators
  • Posts

    9556
  • Joined

  • Last visited

  • Days Won

    499

Hervé last won the day on October 29

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.1k

Reputation

16

Community Answers

  1. @sensui20 SSDT table "SSDT-PLUG-DRTNIA" is corrupt. Make sure to replace it by a valid one. Other tables look Ok. https://dortania.github.io/Getting-Started-With-ACPI/ssdt-platform.html#laptop
  2. Assuming there's no hardware-related issue with your keyboard, I guess the kext (driver) you're using may not be appropriate. It's probably I2C hardware but from which manufacturer? ALPS, Synaptics, Elan?
  3. Graphics settings look a bit odd to me for a Kaby Lake U/Kaby Lake R laptop with HD 620/UHD 620 graphics (i.e. 7th or 8th gen)... For clarification, you should add your system's specs in signature or post them in your introductory post (we don't have crystal balls, sorry). Never seen the need to change built-in LCD connector's pipe for instance. The recommend settings for an 8th gen Kaby Lake R laptop with UHD 620 graphics used to be: framebuffer layout 0x591b0000 (I use 0x59160000 for Mojave and 0x59160009 for Catalina on my 8th gen KBL R Latitude 7490), 0x87c00000 being for Amber Lake laptops (Dortania's documentation says otherwise but...) fake iGPU id 0x5916 See the WEG user manual. Details of KBL framebuffers in questions are as follows: ID: 87C00000, STOLEN: 34 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0000078B TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 103 MB, MAX OVERALL: 104 MB (109588480 bytes) Model name: Intel HD Graphics KBL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [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 ID: 591B0000, STOLEN: 38 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000130B TOTAL STOLEN: 39 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 136 MB, MAX OVERALL: 137 MB (144191488 bytes) Model name: Intel HD Graphics KBL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS [2] busId: 0x04, pipe: 10, type: 0x00000800, flags: 0x00000187 - ConnectorHDMI [3] busId: 0x06, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 00000800 02000000 98000000 02040A00 00080000 87010000 03060A00 00040000 87010000 ID: 59160000, STOLEN: 34 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00000B0B TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 103 MB, MAX OVERALL: 104 MB (109588480 bytes) Model name: Intel HD Graphics KBL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [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: 0x00000800, flags: 0x00000187 - ConnectorHDMI 00000800 02000000 98000000 01050900 00040000 87010000 02040A00 00080000 87010000 ID: 59160009, STOLEN: 38 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00830B0A TOTAL STOLEN: 39 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 115 MB, MAX OVERALL: 116 MB (122171392 bytes) Model name: Intel HD Graphics KBL CRB Camellia: CamelliaV3 (3), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x000001C7 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x000001C7 - ConnectorDP 00000800 02000000 98000000 01050900 00040000 C7010000 02040A00 00040000 C7010000 It's worth noting that, on the 7490, HDMI output required connector con1 to be configured (i.e. patched) as follows: 01051200 00080000 87010000 The patch therefore varies according to the FB used. I see no reason why things would be different on an 8th gen 7390.
  4. You use SKL framebuffer atout 0x19120000 which defines the following properties: ID: 19120000, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000110F TOTAL STOLEN: 56 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes) Model name: Intel HD Graphics SKL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [255] busId: 0x00, pipe: 0, type: 0x00000001, flags: 0x00000020 - ConnectorDummy [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP FF000000 01000000 20000000 01050900 00040000 87010000 02040A00 00040000 87010000 As suggested by Jake, once you've identified in IOReg which connector your HDMI output attaches to (in all likelihood con1, [email protected] but it may be con2, i.e [email protected]), patch its type by adding the following lines to your injected iGPU properties set: framebuffer-conX-enable 1 NUMBER framebuffer-conX-type 00080000 DATA where X is 1 or 2. HDMI output can also be a little difficult at times on Skylake HD5x0. Make sure to add Whatevergreen boot arg igfxonln=1 in your bootloader config. See the Whatevergren documentation and user manual.
  5. HDMI audio only works on Haswell Hackintosh if: you patch the associated framebuffer connector to HDMI type (00080000) -> not the case in the last IOReg you posted but corrected in Jake's last config you rename ACPI device B0D3 device to HDAU -> that was the case in the last IOReg you posted Make sure you select the HDMI audio output, it has to be done manually and volume is controlled on the HDMI device itself, not the laptop.
  6. If you still have Windows, I'd also check it out in Device Manager... But it does not look like the touchscreen of the XPS 12 9Q33 is USB-based but, in fact, connected to the I2C bus alongside the TouchPad. There's probably little chance to get it working under macOS... https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=4p1td&oscode=w864&productcode=xps-12-9q33
  7. I'm pretty sure you're mistaken here... What you show here is an Intel sensor of some sort. I don't believe it's the touchscreen at all. Dell has been fitting Atmel touchscreens to their XPS and Latitude laptops for years.
  8. Again, this can only work if your touchscreen is USB-based. Do you see it in SysInfo->Hardware->USB? Would be something looking like this:
  9. Absolutely nothing with the IOHIDFamily kext, it's just a patch to be specified in the bootloader config. I have the same patch in the OpenCore pack I posted in my Vostro 200 guide if you want to double check the patch in OC. Make sure to reset NVRAM at OC Picker when you reboot.
  10. If the stuff I posted on p1 does not work or suffice, you may seek inspiration from here. For graphics, an old Nvidia (Tesla) card would be a lot easier to get working. I don't know if the dGPU is MXM-based or soldered. If former, you may manage to replace your Radeon HD 3670 by an Nvidia Quadro FX 7xxM model (supported OOB up to High Sierra).
  11. So... BIOS: F.20 (with AHCI support it would seem) CPU: Intel Penryn C2D P8400 FSB-1066 @2.26GHz RAM: 4GB DDR2-800 (PC2-6400) dGPU: ATI Mobility Radeon HD 3670 2GB (PCI id 1002:9593) Display: 1680x1050 built-in LCD Audio: Analog Devices AD1984A Codec IO Controller: Intel ICH9-M USB: USB2.0 ports Disk: 160GB Hitachi HTS543216L9A300 5400rpm SATA-II HDD LAN: Intel 82567LM Gigabit Ethernet Wireless: Intel Wifi Link 5300 AGN TouchPad: Synaptics SD card reader: Ricoh R/RL/5C476(II) (PCie) Optical drive: TSSTcorp TS-L633M CD/DVD writer Should run macOS High Sierra pretty well, though it'll be slow on that SATA-II 5400rpm HDD which you should consider replacing by a SATA SSD. I see the you've been posting on various forums these last few months to try and get macOs installed on this old laptop so I assume you're now familiar with bootloader, etc. I suggest that: you use Clover and start with an older version installed as follows: Clover for UEFI booting only Install Clover in the ESP UEFI Drivers AudioDxe DataHubDxe FSInject SMCHelper ApfsDriverLoader AptioMemoryFix Fat PartitionDxe Ps2MouseDxe UsbMouse.Dxe VBoxHfs Themes (optional) Install Clover Preference Pane (optional) you may use version r5035 for instance: Clover_v2.5k_r5035.pkg.zip once Clover is installed, run Clover Configurator app and mount the freshly created EFI partition of the USB installer Clover Configurator.zip open this EFI partition and transfer the files & folders from the Clover pack below to the EFI/Clover folder. The pack may not be100% complete to match all of your hardware (keep looking for kexts as required) but should get you going: EliteBook_8730w_Clover_Pack.zip For audio, experiment with the various layout ids specified in the AppleALC wiki. For your Synaptics touchpad, look here though it's old stuff (I've no experience with anything other than ALPS touchpads). For your Intel Wireless card, look here. For graphics acceleration, you'll have to experiment with the various ATI framebuffer personalities that may apply to Mobility Radeon HD 3670 (I've no experience with this): This is all without any guarantee of any kind so be prepared for additional home work. Good luck!
  12. You did reset NVRAM at OC Picker after you changed your config and rebooted, right? I also note you never got rid of the stolenmem patch...
  13. Touchscreens usually are USB based. However, recent macOS versions require that you apply a patch (called "USB HID fix") to support those USB accessories because, since Big Sur, Apple dropped support for older/legacy USB technology. The patch is readily available on Hackintosh forums and provided in my E7270 guide. Look it up.
  14. I'm very pessimistic about likely success of graphics acceleration in Big Sur for R7 240. There were many many posts at IM on the matter with zero success afaik. Does not appear to be supported beyond Mojave with which it already required patching.
×
×
  • Create New...