-
Posts
10026 -
Joined
-
Last visited
-
Days Won
561
Content Type
Profiles
Articles, News and Tips
Forums
Everything posted by Hervé
-
HP ProBook 6470b: power management and battery 1% DSDT patch - OpenCore
Hervé replied to Asfand Yr's topic in The Archive
Make sure you have NVRAM working properly. Brightness level can get stored there in order to be retained at next reboot. Same for audio volume level and things like that. -
HP ProBook 6470b: power management and battery 1% DSDT patch - OpenCore
Hervé replied to Asfand Yr's topic in The Archive
All attachments are present and available. I've just checked. -
Dell Inspiron N5110: no internal mic after wake (High Sierra)
Hervé replied to ita266's topic in The Archive
Clover config looks alright to me, except the choice of MacBook8,1 SMBIOS as opposed to MacBookPro8,1 for this older Sandy Bridge laptop. There's an extensive thread about the N5110 at InsanelyMac. Did you check it? -
Check your boot-args once in macOS: nvram -p | grep boot-args Delete the existing boot-args as/if appropriate.
-
HP ProBook 6470b: power management and battery 1% DSDT patch - OpenCore
Hervé replied to Asfand Yr's topic in The Archive
If you've already generated your CPU-specific power management SSDT, all you need to do is place/copy the .aml file to OC's EFI/ACPI folder and call it/declare it in the ACPI section of your OC config. You may then use apps such HWMonitor (provided with all recent/latest versions of FakeSMC) to check your CPU behaviour; alternatively, download and install Intel's own tool called Power Gadget. Re: audio, use AppleALC kext (it's a PlugIn of Lilu so it goes with it) and check the kext's wiki to get the list of layouts you may use for that codec. -
You appear to have a Micron 2200s SSD in that Latitude 7400. Those are known to be troublesome with macOS and you should consider replacing it. https://dortania.github.io/Anti-Hackintosh-Buyers-Guide/Storage.html
-
No, CPU model makes no difference to the OpenCore setup, except for graphics and SMBIOS settings if iGPUs differ. Post your specs in signature, you'll make everyone's life easier.
-
Check that your iGPU's 4K capabilities match that of the TV, especially the frequency (eg: 4K@24/30/60Hz.). If they don't match, you won't get 4K output. HDMI cable also needs to be of the right specs. And then, you must use the right config file settings too.
-
Please note that HDMI audio for Haswell iGPU normally requires: renaming of ACPI device B0D3 to HDAU injecting hda-gfx property to ACPI devices HDEF/HDA/IGPU, set to "onboard-1" injecting HDMI connector type 00080000 to HDMI output port/connector (usually con1) injection pipe value 0x12 to HDMI connector to 12 (or system will crash on HDMI cable plugging/unplugging) Check what you have in IOReg to begin with and adjust your bootloader config accordingly afterwards.
-
[Solved] Latitude 6230: stuck on Mojave installation
Hervé replied to balrzoz's topic in The Archive
Yes that's the adapter. We've got a fully detailed thread about this in the R&D->Wifi section. Look it up. If you want to verify the model of wireless card in your E6230, it could be simpler: losen the sole screw that holds the bottom cover and slide it out. You'll see the card in the corner of the laptop; you can't miss it! -
[Solved] Latitude 6230: stuck on Mojave installation
Hervé replied to balrzoz's topic in The Archive
Intel Ultimate-N 6300 is meant to be supported by the recently developed Intel wireless tools but I still recommend you opt for a fully supported Broadcom card or a real Apple Card with a mini-PCIe adapter (eg: BCM94360CD). That's what I use in my E62x0 laptops and never regretted it for a second. You get full and native Wireless + Bluetooth services, just like on a real Mac and never need to worry about it again. -
Yes, of course it is; you jut need the correct settings on your bootloader config.
-
[Solved] Latitude 6230: stuck on Mojave installation
Hervé replied to balrzoz's topic in The Archive
No need to switch to the other bootpack. As stated in the guides you simply need to generate your CPU-specific power management SSDT. Granted it may not have been explained well-enough, something I've now addressed. If you use the SSDTs for I provided for the CPUs stated in my guides, you'll indeed encounter issues. Anyway, assuming you're unable to generate your own SSDT, here it is. Just unzip and place inside your Clover's ACPI/patched folder. SSDT-PM_i5-3320M.aml.zip -
[Solved] Latitude 6230: stuck on Mojave installation
Hervé replied to balrzoz's topic in The Archive
Obviously just a typo that has now been attended for; thanks for pointing this out. We won't be able to make anything out of that KP screenshot unfortunately. Things that could be wrong, open thoughts really: dodgy RAM module or slot unsupported wireless card; please specify non-vanilla installation You should also post your specs in signature like most of us do. -
[Solved] Latitude 6230: stuck on Mojave installation
Hervé replied to balrzoz's topic in The Archive
All the info and data provided in the Mojave guide were accurate at the time of writing and remains so to date. Of course, numerous newer versions of Clover and numerous new versions of some of the kexts of the provided bootpack were released since. Whether you update those is entirely up to you but rest-assured that the provided pack will work perfectly with the provided Clover version for all versions of Mojave. Check your BIOS settings and adjust as per the recommended settings in case something differs. -
[Solved] Latitude 6230: stuck on Mojave installation
Hervé replied to balrzoz's topic in The Archive
-
Big Sur will run perfectly on Haswell/HD4400 Latitude E5440. It can take anything up to 1hr to complete its installation. Yes, it's quite long and normally requires up to 4 reboots after installation begins. Process has been detailed in our numerous guides like this one for my Haswell/HD4400 Toshiba laptop. There are several E5440/E6440 guides and/or threads on the forum that you can consult to reach your goal.
-
Several things to revise in your Clover config: CPU power management is all wrong: no need to drop CpuPm and Cpu0Ist tables with a Coffee Lake platform, those drops applied to Sandy & Ivy Bridge systems. In the same respect, remove Generate P States/C States, that applied to Core2Duo/1st gen Core CPUs. I'm quite surprised by the number of ACPI patches you've selected. Are you sure you need all of them? i5-8500 is indeed Coffee Lake with UHD630 iGPU so why did you select Kaby Lake iMac18,3 SMBIOS instead of iMac19,2? Change that. You appear to inject the correct device properties forUHD630 graphics but you only patched con0 and con2 connectors (i.e. video output ports). DP or HDMI audio require that the associated connector bet set to HDMI type 00080000. So, check in IOReg which port connects to your DP or HDMI screen and patch its type accordingly. In your config, only con0 is set to HDMI type. Clover chime, you should easily find out if you search a little better the Clover documentation. Hint: something to do with an audio module/driver... Strangely enough, no ACPI folder in the zipped EFI you posted so I'll assume you're not using any patched DSDT or SSDT. If you do, please post your full EFI. Given that you have a Pascal GTX1060 graphics card in your desktop, you are using the nVidia Web Driver, right?
-
Optiplex 7480 AIO: purple built-in screen when HDMI screen is connected
Hervé replied to marliwahoo's topic in The Archive
Try: adding property injection to set fbmem to 9MB switching SMBIOS to iMac19,2 -
And the Bluetooth module/card model would be ? For the rest, please consult our FAQ section where you'll find existing answers to your questions. As a general rule of thumb, you should always start there and by searching the forum before posting. You're also expected to post in the correct forum section... -> moving to E6xxx support section.
-
DW1550: want to know the way to make it work in Catalina
Hervé replied to DJKim's topic in The Archive
DW1550, like its M.2 counterpart DW1560, is based on Broadcom BCM4352 chip (pci14e4,43b1). As such, you should still be able to get it to work under Catalina and Big Sur with the good old recommended settings: https://osxlatitude.com/forums/topic/11138-inventory-of-supportedunsupported-wireless-cards-2-sierra-big-sur Last 3 x Broadcom chipsets officially supported by AirPortBrcmNIC in Big Sur are: BCM43602 (pci14e4,43ba) BCM4350 (pci14e4,43a3) BCM4360 (pci14e4,43a0) Catalina supported the same + the following additional 2 x Broadcom chipsets through AirPortBrcm4360: BCM4331 (pci14e4:4331) BCM43224 (pci14e4:4353) -
That's correct; see our BCM4350 article and guide for references and illustrations.
-
@davidfrei7as, indeed you should have been more cautious before purchasing the wrong card. Now you have 2 x unsupported Qualcomm Atheros cards! We've detailed this information specifically in our wireless cards inventories, starting in the 1st one back in 2018:
-
It depends in which country you are and what the default code of the card is set to.