-
Posts
10077 -
Joined
-
Last visited
-
Days Won
569
Content Type
Profiles
Articles, News and Tips
Forums
Everything posted by Hervé
-
Brightness usually requires injecting a SSDT-PNLF patched table. We'll see if you've included that in your bootloader's pack once you've posted your system's specs + zipped EFI folder.
-
Renaming the kexts is indeed sufficient. For instance: itlwm_mojave -> min kernel = 18.0.0, max kernel = 18.99.99 itlwm_monterey -> min kernel = 21.0.0, max kernel = 21.99.99 With Clover, you would have placed the different itlwm kexts in the dedicated macOS version folders (eg: 10.14, 12), leaving the other ones in Other folder.
-
Optiplex 3011 AIO: need help getting graphics acceleration on HD4000
Hervé replied to audiosurplus's topic in Dell Desktops
Hi, please specify the bootloader and bootloader version you're using. Post a zipped copy of the EFI folder. What's the screen resolution on this AIO? -
How can I remove an unwanted menu bar icon in macOS Ventura?
Hervé replied to Hecatomb's topic in The Archive
Ha Ok, missed that completely: Thing is OP has no RP01 bridge in his IOReg so, indeed, I'm not sure this patched SSDT does anything at all... And does he have TB3 devices that he'd want to HotPlug??? -
How can I remove an unwanted menu bar icon in macOS Ventura?
Hervé replied to Hecatomb's topic in The Archive
You did not provided the require SysInfo extract. Open System Information from Apple menu whilst pressing [Option], save it as a .spx file, zip it and post it. Anyway, it's confirmed: it's the Thunderbolt3 hardware. I don't know how or why these get reported as ExpressCards. Possibly a Ventura beta bug... -
E7440: no sound from headphone jack in Catalina 10.15.7 (OC 0.7.8)
Hervé replied to ksandbergfl's topic in The Archive
Do you have CodecCommander kext in your existing kexts set? Obviously you must only use 1 x audio layout-id in your config: either as a property injection against you audio device or as a boot arg in the NVRAM section. But not both or, at least, not 2 with different values. From memory, E7440 is fitted with same ALC292 codec as other Haswell E6x40 models and requires layout id 12 (or 0x0c in Hex). JakeLo's guide does mention a fix in both his 2018 Clover guide and his 2020 Opencore guide to sort out the very issue you mention. Did you download it and run the shell script? -
How can I remove an unwanted menu bar icon in macOS Ventura?
Hervé replied to Hecatomb's topic in The Archive
@Hecatomb A word of advice when you want to post a copy of your EFI folder: remove the itlwm kext(s). Your EFI has no less than 4 x different copies of it, totalling in excess of 64MB ! You don't need to post that. 8086:15d2 is an Intel TB3 controller; can't say why it gets registered as an ExpressCard in Ventura. No idea what that 2nd PCI device listed as XHCI controller (i.e. USB3 controller) really is, no visible PCI ids. You were asked for a SysInfo extract + an IOreg extract but so far...nothing. I presume previous macOS versions did not register such hardware as ExpressCards. Ventura is only at fairly early beta stage so you may want to consider this a bug... If you delete the icon by holding [Command] whilst dragging the icon out of the menu but it keeps coming back at subsequent reboot, I've no idea how to remove it permanently if there's no option in Systems Settings to that effect. Good luck. -
Please specify your computer model and its specs. Ideally, publish those in your signature like most people do.
-
You should also remove these kexts found in the original pack you got from Github: IOGraphicsFamily -> can't imagine what this would do; a patched version used to be required many years ago to fix the garbled Apple logo at boot time but it's long been deprecated CPUFriend + CPUFriendDataProvider -> the data kext would be specific to the OP's i5-8265U and should therefore be re-generated for your own CPU. Then, of course, update all other kexts to latest version.
-
Yup, just download latest OC version and make your own EFI using the guidance posted at Dortania. All required kexts are known by now, the E6440 is an old Haswell laptop with all fitted hardware fully documented. Tons of threads about this model on the forum too.
-
Seeing what you currently inject for iGPU properties, did you try the settings recommended in the Whatevergreen User Manual instead? Probably a good starting point as an alternative to this which clearly is incorrect: And experiment with other framebuffers such as 0x3EA50009 to begin with.
-
Please post your laptops spec, ideally add them in signature. Several people encountered difficulties with Whiskey Lake models/platforms.
-
For your signature: click on your account name at top of forum Window, then go to Account Settings->Signature. About your graphics setup: Strange that you opted for MBP15,2 (a Coffee Lake model) on your Kaby Lake/HD620 laptop when you'd be expected to use MBP14,1 (a Kaby Lake model)l. I invite you to try it out. KBL framebuffer 0x59160000 certainly is correct for KBL HD620 and your connector patches are all good though con0's is not required since you inject the exact same thing as what's natively defined in the framebuffer. You correctly swap connector's type for HDMI and DP given that, in the vanilla FB, con1 is DP and con2 is DP: 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 You could also experiment with KBL FB 0x591B0000 (it's the recommended one for KBL HD620). It requires patching con1 alldata to same as FB 0x59160000 or you won't get HDMI output of course: 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 -> Needs to be patched to 01050900 ... 03060A00 00040000 87010000 -> can stay as is afaik, no need to patch to 0204... I've never seen anyone injection a pci-asm-default value for an iGPU. Did you try HDMI output without injecting this parameter? Where did you get the idea to inject a different framebuffer-flags value from? How did you choose the value?
-
Indeed, once you increase DVMT to 64MB or 96MB in BIOS, the fbmem + stolenmem patches become irrelevant and even counter productive since they usually aim to reduce the default values of the selected framebuffer so that the sum of them remains below 32MB. In your case, it looks like 64MB is the max value you can set for DVMT pre-allocated memory. May be you can experiment with DVMT total values (256/128/Max).
-
Did you check the default DVMT settings of your 7480? Under macOS, DVMT must usually be set to 64MB or 96MB to obtain 4K output; afaik, you won't get it if DVMT is set to 32MB even if you patch the DVMT settings (fbmem + stolenmem) through properties injection. With DVMT set to 64MB or 96MB (BIOS mod through Grubshell, see our FAQ topic on the matter or my E7270 guide), I can get 4K @24-30Hz out of HDMI and 4K@60Hz out of mDP on my Skylake/HD520 E7270 laptop. Can't see why it'd be different on your 7480, unless it's the TB port that's causing the issue under macOS of course. Don't hesitate to post a zipped copy of your bootloader's EFI folder so that we can check your settings. Do post your system's specs in signature since they're are 6th gen and 7th gen 7480...
-
How can I remove an unwanted menu bar icon in macOS Ventura?
Hervé replied to Hecatomb's topic in The Archive
Sorry, don't understand what you mean. In Ventura, you hide or show such OS-related menu bar icons from System Settings->Control Centre. It's not an app icon that goes away once you close the app. If you've no options to hide/shows this icon in the Control Centre, I'm afraid you'll have to live with it. It'll only go if the hardware goes... I'm not 100% sure of this but this icon may appear due to some properties you inject in your bootloader's config. I'm thinking specifically about the "unknown" piece of hardware that's listed... You'd have to post a zipped copy of your bootloader's EFI for us to check this out. What's the issue of having the icon displayed anyway? -
How can I remove an unwanted menu bar icon in macOS Ventura?
Hervé replied to Hecatomb's topic in The Archive
No, it's not for an SD card. In Ventura, SD cards appear as memory card icons on the desktop just as with previous OS X/macOS versions. They're considered as storage devices, just like USB disks or USB keys: @Hecatomb This menu bar icon usually is for an ExpressCard (54 or 34). See this thread where ExpressCard USB3.0 controllers were discussed. Can't remember if he same applies to USB-c devices (other than USB-c disks/keys of course). Post a zipped copy of an extracted IOReg (using IORegistryExplorer App) and of a saved System Report. It's probably some other odd piece of hardware on the motherboard. I've recently read somewhere of recent Hackintosh computers that displayed the same behaviour; can't remember if these were desktops or laptops. Anyway, if you have no ExpressCard or PCIe hardware that would explain this, just see if you can disable the option that displays this in the menu bar from System Settings->Control Centre. -
I don't have them at hand, please use the forum Search facility. And, in case you had not noticed, we also have a dedicated section dedicated for full installation guides (only)...
-
To me, there are several things incorrect in your OC setup and I'd start by removing the following kexts from your config + kexts folder: CpuTscSync HibernationFixup Can't see why you'd need them. I never did. Some of your iGPU property injections appear quite odd to me too, but that's not something likely to prevent the laptop from shutting down, only cause issue with HDMI output. Most 7490 were fitted with 8th gen Kaby Lake R CPUs and therefore use MacBookPro15,2 SMBIOS. Your config shows you've opted for MacBookPro14,2 SMBIOS, i.e. a 7th gen Kaby Lake model. You need to post your system's specs, ideally add them in signature like most people do here.
-
Lobby section is for personal introduction. Moving this thread to appropriate Latitude 7000 Series support section. Please make every effort to post in the appropriate sections of the forum. By cooler, you mean the fan? There are several existing threads about the Latitude 7490 on our forum; read them up and check the various bootloader packs posted in them. Yours is probably incorrect but, until you actually post a zipped copy of it... who knows? I had that laptop for a couple of years and ran Mojave and Calalina on it; 'never had any issue of any kind with it as a Hackintosh, certainly not with shutting it down.
-
Released Jul 27th, 2022. Build 22A5311f. Ok on my Skylake/HD520 Latitude E7270 with exact same/unmodified Clover r5148 setup previously used for 13.0 beta 3. Status recap: graphics acceleration with some minor defects brightness control touchscreen HDMI output mini-DP output audio (incl. HDMI & DP audio) LAN wireless & Bluetooth (BCM9460CS2) touchPad USB ports sleep & wake SD card reader
-
Ace! What's new compared to the existing guides and existing EFI/bootpacks such as those posted by Jake Lo here?
-
E6440 (Opencore): HDD does not show in disk utility
Hervé replied to Saqer1111's topic in The Archive
@Saqer1111 Click on View button at top left corner and select View all devices. What kind of disk do you have in that E6440? Regular SATA-III 2.5" HDD? SATA-III 2.5" SSD? mSATA SSD in mSATA slot? You'll have to set disk mode to AHCI in BIOS or it just won't work. Are you using a full vanilla USB installer or a distro which may be missing files and drivers? There are several threads about the E6440 on the forum, I'm sure several of them provide copies of EFI folder you may be able to re-use, partially or fully.