-
Posts
10013 -
Joined
-
Last visited
-
Days Won
560
Content Type
Profiles
Articles, News and Tips
Forums
Everything posted by Hervé
-
Didn't I write "in the Ventura pack of my E7270 guide" ? It's all there; don't know what else we can do here...
-
Please describe what you boot and how, in a proper and explicit enough manner. The above is far too poor. I assume your request is macOS-related since you're posting here. Please provide your full system's specs and a zipped copy of your boot loader. Do specify the target macOS version and the bootloader version.
-
Just modify your OC config using any plist editor app (eg: Xcode, ProperTree, PlistEditPro, etc.) or basic text editor (eg: TextEdit) or dedicated app such as OpenCoreConfigurator (OCC). How else did you build your setup? Or did you just copy/paste a complete OpenCore EFI folder from somewhere and somehow got lucky?
-
IOReg and OC config show you're using KBL mobile framebuffer 0x591e0000 rather than desktop framebuffer 0x59120000 as expected and recommended by the WhateverGreen User Manuel. ID: 59120000, STOLEN: 38 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0000110B 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: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 0, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP [3] busId: 0x06, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 01050900 00040000 87010000 02040A00 00040000 87010000 03060A00 00040000 87010000 Note that this framebuffer defines 3 x DP outputs so you may have to patch the connectors depending on your own physical output ports. No support for VGA of course. Your OC config currently changes connectors con1 and con2 to HDMI type, leaving con0 unmodified. You should also change SMBIOS from iMac18,2 to iMac18,1 since former uses AMD dGPU whilst latter uses KBL iGPU only. NB: you're injecting iGPU unifiedmem property with value 0x80000000, i.e. 2GB; as such your graphics info should show 2048MB in About this Mac, not "[...] 1532MB or whatever the MB [...]".
-
You may try the PS2 controller kext posted in the Ventura pack of my E7270 guide.
-
You'll need to be specific about your wireless card and tell us what model it is. ITLWM support for Ventura is currently at early alpha stage so, indeed, you may find your model is not fully supported at the present time. Re: audio, you'll have to identify the codec; being an E5440, I'm tempted to say ALC292 as per other Haswell Latitude E Series in which case injecting layout-id 12 normally does the trick. Basically, the exact same thing as per previous macOS versions. Again, make sure to stay away from any OCLP audio patches as that will affect your system.
-
Perfectly normal; you can't install Ventura without a supported SMBIOS; same goes for OTA updates. Once Ventura is installed, revert to Haswell SMBIOS and boot with -no_compat_check boot arg. Then apply the OCLP root patches.
-
You must revert to the SMBIOS of unsupported Haswell platform for the OCLP patch to work: MBP11,x or MBA6,2. You installed Ventura with SMBIOS MBP14,1 which is a Kaby Lake platform. That's unsuitable for OCLP patching. Make sure you apply the OCLP root patches and absolutely nothing else on your Hackintosh.
-
No, he did not; he's got no graphics acceleration -> Intel HD Graphics 4400 4MB. It's not "Ventura done" per sé but Ventura installed and running in reduced VESA mode for the time being... NB: As per our published rules, no double post on the forum please.
-
@ABOFE, if your touchscreen is USB, I expect you'll need to apply the USB HID Fix patch. You can look it up on the Web but this patch is mandatory since Big Sur (because Apple then dropped support for older USB technology) and it's missing in the OC config you uploaded in post #1. Please follow the link I gave you above and apply the patch in your config accordingly. Make sure you've properly mapped all your USB ports, including the internal ones of course. It's as simple as that...
-
[Solved] Latitude 7400: unable to install Ventura with OpenCore
Hervé replied to Xristomania's topic in 7000 Series
Development for Intel wireless cards under macOS Ventura remains at alpha stage for the moment as clearly indicated on the ITLWM Github repo. Support under alpha version 2.2.0 is known to be pretty poor for some cards as can be expected; there should be not surprise there. Best indeed to opt for Monterey unless using a supported Broadcom card. https://github.com/OpenIntelWireless/itlwm/releases https://openintelwireless.github.io/itlwm/FAQ.html#installation- 25 replies
-
- open core
- latitude 7400
-
(and 1 more)
Tagged with:
-
[Solved] Latitude 7400: unable to install Ventura with OpenCore
Hervé replied to Xristomania's topic in 7000 Series
Should do but only one way to know... https://dortania.github.io/Anti-Hackintosh-Buyers-Guide/Storage.html Make sure you use the NVMEFix kext.- 25 replies
-
- open core
- latitude 7400
-
(and 1 more)
Tagged with:
-
[Solved] Latitude 7400: unable to install Ventura with OpenCore
Hervé replied to Xristomania's topic in 7000 Series
Logs? Zipped copy of OC EFI/setup? Something? Anything?- 25 replies
-
- 1
-
- open core
- latitude 7400
-
(and 1 more)
Tagged with:
-
Identify the model and nature of touchscreen (PCIe/IC2 vs. USB) through SysInfo or IOReg. If USB, expect an Atmel device and look here to apply the USB HID Fix which is likely to be necessary. This is what the touchscreen looks like on my Skylake Latitude E7270:
-
HP All-in-One (Coffee Lake): no display on built-in/internal screen
Hervé replied to Tridon's topic in HP Systems
Maybe you're not using the correct graphics settings for a desktop Hackintosh. CFL framebuffer 0x3e920000 is a mobile layout which defines the following output ports: ID: 3E920000, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0000130B TOTAL STOLEN: 58 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 172 MB, MAX OVERALL: 173 MB (181940224 bytes) Model name: Intel HD Graphics CFL CRB Camellia: CamelliaDisabled (0), Freq: 0 Hz, FreqMax: 0 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 i.e. 1 x LVDS/eDP output and 2 x DP outputs. Did you experience similar issues with the CFL layouts recommended for desktops, i.e. 0x3EA50000 and 0x3E9B0007? Cf. WEG user manual. I would also recommend you try and identify the type of display connector used for your built-in/internal screen (DP? eDP? LVDS?) so that you may patch the appropriate framebuffer connector accordingly. The CFL layout recommended for desktops is 0x3E9B0007. Layout 0x3EA50000 is the default one if nothing is specified in your config. Those define the following properties: ID: 3E9B0007, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00801302 TOTAL STOLEN: 58 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 172 MB, MAX OVERALL: 173 MB (181940224 bytes) Model name: Intel UHD Graphics 630 Camellia: CamelliaDisabled (0), Freq: 0 Hz, FreqMax: 0 Hz Mobile: 0, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [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 is a desktop layout which defines 3 DP outputs. ID: 3EA50000, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00030B0B TOTAL STOLEN: 58 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 172 MB, MAX OVERALL: 173 MB (181940224 bytes) Model name: Intel HD Graphics CFL CRB Camellia: CamelliaDisabled (0), Freq: 0 Hz, FreqMax: 0 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 This is a mobile layout which defines 1 LVDS/eDP output and 2 x DP outputs. Of course, Mac mini is not an ideal SMBIOS either given that such models do not come with built-in screen; I'd recommend you opt for a Coffee Lake iMac/iMacPro SMBIOS instead. Intel i7-8700T CPU integrates UHD 630 iGPU with native PCI id 0x3E92; as such, no need to inject any device-id in your config; id 0x3E92 is fully and natively supported by macOS CFL drivers. Your OC config is Ok on that front. On the other hand, I find it to be incorrect on the following front: You inject the framebuffer layout incorrectly; due to the endianness used by Apple, make sure you specify all hexadecimal properties in "reverse bytes order" if you'll allow the expression. As such, framebuffer 0x3e920000 is injected as follows: AAPL,ig-platform-id 0000923E DATA I would suggest you experiment with the correct CFL framebuffer (and nothing else) to begin with and before attempting to patch framebuffer's connectors. -
Try and inject the following iGPU property: enable-max-pixel-clock-override 1 NUMBER See here for details.
-
Unrelated to HDMI output of course but note that reducing stolenmem to 34MB is not required if DVMT is set to 64MB or above in BIOS; also, it'll prevent support for 4K output, something the OP is after here... For the rest, the only noticeable differences are: the use of KBL framebuffer 0x5916000 and KBL iGPU device id 0x5916. the lack of max pixel clock override.
-
Did you try and inject your screen' EDID as suggested previously?
-
Your posted IOReg shows: external display on con2 (FB @2), not con1 (FB @1) con1 patched to HDMI type (as per your OC config) -> [...]con1-alldata 01051200 00080000 ... con2 patched to DP type (as per your OC config) -> [...]con2-alldata 02041200 00040000 ... If your external display on con2 is indeed HDMI, you need to patch its type accordingly, i.e. not to DP (0x0400) but HDMI (0x0800). NB: No need to patch fbmem or stolenmem for Azul frame buffers (i.e. Haswell iGPU HD4200/HD4400/HD4600/etc.). You can remove those from your config and only retain the cursormem patch if you found it necessary (in case of cursor graphics corruption).
-
Dell Inspiron 17 5570: screen issues with Intel HD 620
Hervé replied to deivi1's topic in Other Dell laptops
What if you also fake ABL iGPU id 0x87c0 rather than keep native KBL id 0x5916? AAPL,ig-platform-id 0500c087 DATA device-id c0870000 DATA Cf. WhateverGreen User Manual. -
Dell Inspiron 17 5570: screen issues with Intel HD 620
Hervé replied to deivi1's topic in Other Dell laptops
IOReg shows you're injecting framebuffer layout 0x87c00005 in Ventura, something normally used for Amber Lake platforms. Any reason for not using KBL layout 0x59160000 or 0x591b0000 as would be expected? -
Dell Inspiron 17 5570: screen issues with Intel HD 620
Hervé replied to deivi1's topic in Other Dell laptops
Typical values for the DVMT register are: 1 -> 32MB 2 -> 64MB 3 -> 96MB It's always a multiple of 32MB. See here. Check out your register possibilities through the ModGrub CLI help if that's available. -
For your info, on a laptop Hackintosh: internal built-in screen usually is -if not always- attached to FB@0 (i.e. con0) and should always register as AppleBacklightDisplay. external screens usually are attached to FB@1/@2/@3 (i.e. con1/con2/con3) and should always register as AppleDisplay.
-
E7450: Intermittent and sporadic trackpad gestures on Ventura
Hervé replied to Justin Wallis's topic in The Archive
The (now) old PS2Controller kext from Dr Hurt (version R6 compiled by Bronxteck) for Alps touchpads should work Ok on the E7450 platform. Certainly did on all my old Sandy Bridge to Broadwell E Series laptops: E6220, E6230, E6440 and E7250. Said kext is available in our R&D->Kernel Extensions forum section and in my E7250 guide.