Jump to content

Hervé

Administrators
  • Posts

    9184
  • Joined

  • Last visited

  • Days Won

    456

Hervé last won the day on October 19

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

8

Community Answers

  1. Ok, I've changed 1 permission; how about now?
  2. That's why I checked logged in and logged out. Made no difference. I've checked the forum/articles permissions settings and all appears in order. Tested again on my E7270: cleared Safari cache went to OSXL Home page can access both of there above articles
  3. There is a section entitled 3rd party apps or Bootloader (where you can write about OpenCore)
  4. Must be a problem at your end. Verified access from 3 x different Hacks under High Sierra/Big Sur/Monterey logged in and logged out, 2 x different Apple Macs (Ok, all 5 on same home network) and from 2 x different iPhones, each on a different 4G telco/network (wifi disabled). Not a single issue for the given pages. Try and clear your browser cache maybe.
  5. History revisited... Intel wireless cards have never been officially supported under OS X/macOS. For years they had no support at all and had to be replaced by Atheros or Broadcom cards there were compatible. See our FAQs section. A couple of years ago, developers worked again on writing drivers for Intel M.2 cards and published their work at the OpenIntelWireless site/repo. This work remains in "beta" stage afaik and, whilst it provides a degree of support for wifi operation, Bluetooth has little to no support as explained in their own FAQs which I invite you to read. If you want a Bluetooth/Wireless combo card that works, replace your Intel card with a compatible Broadcom-based one. See our inventories and various threads on the matter in this very Wireless forum section.
  6. 1. What SSDT-7450.aml? Maybe a single table where the patches of all the usual OC SSDT tables (EC, CPU PM, USB, PNLF, etc) are unified. 2. Not when you use add-on SSDTs only rather than a patched DSDT 3. an add-on SSDT made to that effect.
  7. Target macOS release: Monterey 12.x This is a Clover-based installation using the well-known/well documented vanilla method detailed below: Working: full QE/CI with HD520 graphics (with SKL layout 0x19160000) HDMI output OOB but built-in LCD goes off on 1st cable connection. With WEG boot arg igfxonln=1, LCD picture is recovered after closing then re-opening the LID and HDMI is on at 1st boot & after wake mDP output OOB full audio, including jack microphone input and headset output (with AppleALC kext & layout-id 11) HDMI audio (with SKL con1 connector-type patch) built-in Gigabit Ethernet (with IntelMausiEthernet kext) full CPU power management, including Turbo boost to 3.4GHz (with PlugIn type settings) sleep: Ok through Apple menu->Sleep, lid closure, power button, Fn-Insert and energy savings settings with hibernation mode set to 0 (sleep to RAM) and /var/vm/sleepimage file deleted. wake: Ok through lid opening and power button wireless & bluetooth with any compatible card/USB dongle battery management and monitoring (with ACPIBatteryManager kext) SD card reader (with Cholonan's Sineteck-rtsx kext) integrated webcam OOB keyboard backlight control OOB (for backlit models) audio volume control through Fn-F1/Fn-F2/Fn-F3 brightness control through Fn-F11/Fn-F12 touchpad basic features, incl. buttons (with Rehabman's VoodooPS2Controller kext) but not recognised in PrefPane USB3.0 ports (with Hackintool's generated USBPorts kext) Not Working: Touchscreen Not tested: SmartCard reader GeekBench v4.4.4 (64bit) gives the following rating: 1) 11.x USB installer creation Using a USB key of 16GB minimum, create a Monterey USB installer through the following Terminal command: sudo <path>/Install\ macOS\ Monterey.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of Monterey installation package (eg: /Applications if freshly downloaded) <USB key> = name of formatted USB volume (eg: USB_16GB) The process will take several minutes. Once completed: install Clover bootloader on the USB installer with the following customised settings: Clover for UEFI booting only Install Clover in the ESP UEFI Drivers Recommended drivers FSInject SMCHelper Human Interface Devices (optional) Ps2MouseDxe UsbMouseDxe FileSystem Drivers ApfsDriverLoader Memory fix drivers OpenRuntime Additional Drivers (optional) NvmExpressDxe PartitionDxe Themes (optional) BootLoaderChooser (optional) CloverConfigPlistValidator (optional) Install Clover Preference Pane (optional) you may use version r5141 attached below: Clover_r5141.pkg.zip once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the USB installer Clover Configurator.zip open this EFI partition and transfer/copy the files & folders from the Latitude E7270 Monterey Clover pack below to the EFI/Clover folder Clover_Pack_E7270_Monterey.zip 2) 11.x installation boot the Monterey USB installer at the Clover main menu, select the "Install macOS Monterey" partition (but don't press [ENTER]) press [SPACE], select -v verbose option in the menu, then choose to boot with the selected options proceed with installation, creating & formatting the target Monterey installation through Disk Utility as/if required on 1st reboot, boot off the USB installer and select the freshly created "macOS install from <target Monterey partition>" repeat this until this partition is no longer offered and only the target Monterey partition is left to boot Reboot the target Monterey partition via your USB installer 3) Post-installation tuning Once the target Monterey partition has booted, complete the 1st boot configuration tuning Once at the desktop, install Clover bootloader on the Monterey partition/disk with the customised settings listed above Once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the Monterey partition/disk Open this EFI partition and transfer the files & folders from the above Latitude E7270 Monterey Clover pack to the EFI/Clover folder You may then reboot and verify that Monterey boots off your disk through Clover Please note that: Clover config of the pack contains HDMI-audio SKL framebuffer patch. Clover config of the pack contains disabled settings for DW1820A wireless card. Enable or remove as appropriate.
  8. My guide does not actually provide anything with regards to Wifi cards except pre-configured but commented out (i.e. inactive/disabled) properties injection for DW1820a. No way to guess what wireless card people may have in their E7270, hence why that very part is left blank and the guide stipulates [working] "wireless & bluetooth with any compatible card/USB dongle". You need to adjust your setup according to the card fitted to your own E7270, something your IOReg shows as an Intel card Wireless-AC 8260(8086:24f3) @1C,0: Follow the process required for such Intel cards as linked right above by Jake Lo.
  9. No Jake, you must have confused host processor (of the machine on which I generated the table, i.e. my E6230) with the target processor (the OP's i3-3110M): Store ("host processor........: Intel(R) Core(TM) i7-3540M CPU @ 3.00GHz", Debug) Store ("target processor......: i3-3110M", Debug) The table I posted is correct, the target CPU settings are identical to those of the table you posted (and generated on an i3-3110M). I simply used Pike R Alpha's generator with the relevant optional parameter as per the script's own help info, i.e.: ./ssdtPRGen.sh -p i3-3110M
  10. Post an IOReg extract taken from apps such as IORegistryExplorer. See our FAQ section...
  11. What do you mean by "system itself is not shutting down the camera" ? Do you see the Webcam in SysInfo->Hardware->USB section or in IOReg? If you don't, you need to revisit your USB ports settings: remap the ports again or possibly adjust your bootloader ACPI patches (eg: XhciPortLimit, renaming of EHCx devices). The USBPorts_E7440 may need to be regenerated for Monterey. Try it anyway. Also, why apply an ACPI patch that renames ECDV to EC when you inject an SSDT-EC.aml patched table that defines a separate EC device?
  12. There is a dedicated thread for the E6220 BIOS settings pinned at the top of this very section; 'pretty sure your E6420 will have the same set of parameters. Make sure to use there latest BIOS, just in case. I you also look into my E6220 Mojave guide, you'll notice there's no need for a patched DSDT and that a small set of add-on patched SSDT tables does suffice. This is of course transposable to High Sierra.
  13. The CPU power management SSDT has nothing to do with the verbose info displayed by OpenCore. It's a problem with your OC config list that does not meet the arrangements expected for the given version. Can happen if you use OCC too to build our config. I know it's a real pain in the a*se with OpenCore but you have to make sure your config is aligned with the requirements and the expectations of the OC version and some of those change from one version to the other according to the decisions made by the devs.
  14. EFI partitions do not exist by default on a raw/reinitialised USB key. It usually is created by bootloaders such as Clover (or older bootloaders before). Since you do not have any EFI partition on the device, you may manually create it and format it FAT32. Or, if you find the associated process not within your grasp, install Clover temporarily on the USB key. Once you wipe out the contents of the EFI partition created by the Clover installer, you'll have an empty EFI partition to play with.
×
×
  • Create New...