Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 11/07/19 in all areas

  1. 2 points
  2. 2 points
    Try this bootpack, file patched from your Origin folder Replace into /EFI/Clover Replace your wifi with a DW1560 E470_Catalina.zip
  3. 2 points
    Last update: 06 Nov 2019 Here are BIOS settings that are known to work on the 7490 (8th gen CPU with Intel UHD620 graphics) under Mojave. These settings were tested and verified with BIOS 1.8.0, 1.9.3, 1.10.0, 1.11.0 and 1.12.2. General . Boot Sequence: * Boot List Option = UEFI (-> Boot Sequence list will be set accordingly) . Adanced Boot Options: * Enable Legacy Option ROMs = On (required to boot legacy external devices such as USB media or SD cards) * Enable Attempt Legacy Boot = On . UEFI Boot Path Security: * Never (or whatever other value) System Configuration . Integrated NIC = Enabled . SATA Operation = AHCI . Drives: * SATA-2 = On * M.2 PCIe SSD-0 = On . SMART Reporting: * Enable SMART Reporting = On or Off . USB Configuration: * Enable USB Boot Support = On * Enable External USB Port = On . Dell Type-C Dock Configuration: * Always Allow Dell Docks = On . USB PowerShare: * Enable USB PowerShare = On . Audio: * Enable Audio = On * Enable Microphone = On * Enable Internal Speaker = On . Keyboard illumination: * Bright = On (or any desired value) . Keyboard Backlight on AC: * Any desired setting . Keyboard Backlight on Battery: * Any desired setting . Unobtrusive Mode: * Enable Unobtrusive Mode = Off . Miscellaneous Devices: * Enable Camera = On * Secure Digital (SD) Card Boot = On * Enable Secure Digital (SD) Card = On * Secure Digital (SD) Card Read-Only Mode = Off Video . LCD Brightness = Whatever settings you prefer Security . Admin Password = not set (or whatever) . System Password = not set (or whatever) . Internal HDD-0 PW = not set (or whatever) . Strong Password = Off . Password Configuration = default settings . Password Bypass = Disabled . Password Change: Allow Non-admin Password Changes = on . Non-Admin Setup Changes = Off . UEFI Capsule Firmware Updates = On . TPM 2.0 Security = Off or On with whatever desired settings . Absolute(R) = whatever desired settings . OROM Keyboard Access = Enable . Admin Setup Lockout = Off . Master Setup Lockout = Off . SMM Security Mitigator = Off Secure Boot . Secure Boot Enable = Disabled . Secure Boot Mode = Deployed Mode . Expert Key Management: * Enable Custom Mode = Off * Custom Mode Key Management = PK Intel Software Guard Extensions . Intel SGX Enable = Software Controlled . Enclave Memory Size = not configurable Performance . Multi Core Support = All . Intel SpeedStep = Enabled . C-States control = On . Intel TurboBoost = Enabled . HyperThread Control = Enabled Power Management: . AC Behavior: * Wake on AC = Off . Enable Intel Speed Shift Technology = On . Auto On Time = Disabled . USB Wake Support * Enable USB Wake Support = On or Off * Wake on Dell USB-c Dock = On or Off . Wireless Radio Control: * Control WLAN radio = Off * Control WWAN radio = Off . Wake on LAN/WLAN = Disabled . Block Sleep = Off . Peak Shift = Off . Advanced Battery Charge Configuration = Off . Primary Battery Charge Configuration = Express Charge (or any other choice) . Type-C Connector Power = 7.5 or 15 Watts POST Behavior . Adapter Warnings = Enabled . Keypad (Embedded) = Fn Key Only . Numlock Enable = Enabled . Fn Lock Optio: * Fn Lock = On * Lock Mode Disable/Standard = On . Fast Boot = Minimal . Extend BIOS POST Time = 0 seconds (or any other choice) . Full Screen Logo = On or Off . Warnings and Errors = Prompt on Warnings and Errors . MAC address Pass-Through = Passthrough MAC address Virtualization Support: . Virtualization = Enabled . VT for Direct I/O = Off (otherwise use Chameleon/Clover option dart=0) . Trusted Execution = Off Manageability . USB Provision = Off . MEBx Hotkey = Enabled Virtualization Support . Virtualization = Enabled . VT for Direct I/O = Disabled . Trusted Execution = Off Wireless . Wireless Switch: * WWAN = On * WLAN = On * GPS (on WWAN Module) = On * Bluetooth = On
  4. 1 point
    1. What you need? >Hardware< a) Lenovo ThinkCentre M58p ebay (testet with CPU: E7-Series, E8-Series, Quad-Core-series ) b) Asus NVIDIA GeForce GTX 650 1GB ebay (works with GeForce 710 as well) c) SanDisk 120GB SSD amazon d) 8GB USB Stick >Software< MacBook,iMac or Hackintosh EFI & Kext from olarila Mojave 10.14 Installer ( Download from Store or ISO from somewhere else and copy it into /Application) Clover_v2.4k_r4919.pkg Clover_Configurator Clover Pack for ThinkCenter m58p 2. Create USB-Installer Mojave 10.14 You have several possibilities to install Mojave 10.14.6 on MBR-Disk. In case you want to install Mojave on HFS+, you will need to create an USB stick with this patch from insanelymac a) Create MBR USB-Stick with Mojave sudo /Applications/Install\ macOS\ Mojave\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/USB b) Run Clover and select: [x] Install Clover in ESP - Bootloader [x] Install boot0af in the MBR (see attachment) the rest will be selected automatically After Clover is installed an EFI-Partition will created and mounted c) Open the EFI-Partition and replace the EFI-Folder with the https://gofile.io/?c=WKacvH 3. Install Mojave on Lenovo a) BIOS-Setup: AHCI should be enabled b) Run Install Mojave from USB-Stick created above c) Follow the installation until the end, then you will need to replace the following file with one from HighSierra (otherwise you will get kernel panic) /System/Library/UserEventPlugins/com.apple.telemetry.plugin 4. Update to 10.14.6 a) Download the 10.14.6 Combo Update from the Apple Homepage b) Install it and reboot 5. Works Graphics (full acceleration; I am using 3 monitors) Sounds (thx to VoodooHDA all works very well) GigabitLAN 6. What needs improvement and I will need some help from you guys: + Shutdown + Restart + I dont use an DSDT ( dont know if we need to patch that ) + SSDT most probably if possible
  5. 1 point
    I can also confirm DW1820A works for E7470.
  6. 1 point
    Hi all, After countless hours of work, I have an almost functional system. My Dell 5490 specs are: Kabylake-R i7-8650 Intel UHD620 16Gb RAM 512 SSD ALC256 USB-C Intel Wifi I2C Trackpad What works: Intel UHD620 Battery Indicator Sound (speakers, microphone, headphones) Wifi (Had to remove Intel and installed a Broadcom one) Bluetooth Airdrop USBs, both A and C Webcam VGA HDMI (With no sound yet) Trackpad (touch click, gestures, no physical buttons yet. Acceleration is not as good as Magic Trackpad is) What does not works: SD card reader (I don't use this) Mouse pointer, or nipple, or whatever its name is (I don't use it) System Definition is MacBook Pro 15,2. I need your help with: - HDMI sound - Trackpad buttons and acceleration. - Any other refinement and inconsistency you see on my configuration. THANKS! CLOVER.zip
  7. 1 point
    10" notebooks usually are very low-end and, as such, made of low-end hardware components that are not usually compatible with macOS.
  8. 1 point
    Catalina bootpack will run just fine on Mojave. But your question was to get system to automatically boot after time out, so you enter the name of your HDD, not version of MacOS your running. I hope that is clearer.
  9. 1 point
    Give this a try, replace contents into /EFI/Clover Vostro_3446.zip
  10. 1 point
    All necessary kexts are found in my E7470 bootpack for Catalina but is backward compatible https://osxlatitude.com/forums/topic/9179-dell-latitude-e7x70-clover-uefi-only/?tab=comments#comment-95548 For Wifi: Lilu.kext, AirportBrcmFixup.kext, FakePCIID.kext, FakePCIID_Broadcom_WiFi.kext For Bluetooth: BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext, and BrcmPatchRAM3.kext // Goes into /L/E Repair permissions and rebuild cache
  11. 1 point
    Which MacOS are you running?
  12. 1 point
  13. 1 point
    Just switch your layoutid in your config file from 13 to 11 should fix the audio issue Also good idea to update Lilu.kext, AppleALC.kext and Whatevergreen.kext. Your version of Clover can / should be updated too
  14. 1 point
    @leaf389 can you post your Config file? Try layout-id =11 + AppleALC.kext @ghostinthemirror Try this Config config-HDMI.plist.zip
  15. 1 point
    Since Thursday, I did not use my hackintosh. Now, I've just turn it on and for my surprise, everything is working fine. I did not do anything different, just can't understand what is going on. Sound is ok - internal speakers and internal microphone. Brightness, keyboard shortcuts also.
  16. 1 point
    I have a Lenovo Thinkpad E470 and I need some help with post-install. Lenovo Thinkpad E470 Processor: Intel Core i5-7200U (Kaby Lake) Bios: R0DET99W (1.99 ) Memory: 12GB (4+8) Graphics: Intel(R) HD Graphics 620 Wifi: Qualcomm Atheros QCA9377 (interface NGFF M2) Ethernet: Realtek PCIe GBE Family Controller IDE Controller: Intel(R) 6th Gen Core Processor Family Platf I/O SATA AHCI Controller SD Card Reader: BayHubTech Integrated MMC/SD controller Motherboard chipset: Intel Sunrise Point-LP, Intel Kaby Lake-U HDD: WDC WD5000LPLX-08ZNTT0 (500 GB, 7200 RPM, SATA-III) Trackpad: Synaptics Pointing Device Keyboard: Japanese PS/2 Keyboard (106/109 teclas Ctrl + Eisuu) Áudio: Conexant CX20753/4 @ Intel Sunrise Point-LP PCH - High Definition Audio Controller [C1] (codec: 14F15111h / 17AA505Bh) Intel Kaby Lake HDMI @ Intel Sunrise Point-LP PCH - High Definition Audio Controller [C1] (codec: 8086280Bh / 17AA505Bh) I have followed initially the guide below (it helped me a lot). Thank you guys for this @Max.1974 @Jake Lo!!!! After a successful Catalina installation, I've used the CLOVER folder from the guide but it never boots up. So, I did a clean install and used a config.plist from RehabMan. So far, so good (er, more or less). During the boot I can see lots of ACPI errors. I'm writing this message from the Lenovo E470 itself I've buy a SSD and I'm just waiting for it. Meanwhile, I'm trying to make it (almost) perfect. What's working: network - only cabled (ethernet) keyboard - although it is a ABNT2, I'm using it as a US International trackpad - not as good as I need - sometimes the click is not working trackpoint - works but not the buttons video - activated and using an external monitor through HDMI screen brightness (with keyboard keys too) SD Card Reader However, some things are not working: sound - only through headphones - using layout 15 (have tried all possible layouts) battery - not showing status wifi - not using - maybe I buy some wireless card in the future (also have 2 different usb dongles to test) Here is my current CLOVER folder and also codec_dump I made using Linux. I want to make it fully functional and learn some new tricks during the journey. I also want to make a more detailed guide to help other people. Any help is welcome. codec_dump-0.txt.zip CLOVER.zip
  17. 1 point
    I have a Lenovo Thinkpad T470S with an Intel Core I5 7th Gen 2.7MHz, Intel HD620 Graphics, and 16GB. Here is my Clover folder that is in my EFI folder. It is based on the work of Max.1974 and Jake Lo's work at the above post. Everything works but the battery indicator and the screen dimming. Still working on that, but they are relatively minor things still to wrap up. This file should give folks a good jump start. I will post an update once I get the last two things running. Special thanks to Max.1974 for the post above for the E470 and how detailed he got, including Bios settings to use. CLOVER.zip
  18. 1 point
    Follow my Clover guide here Make sure to set BIOS to UEFI enabled / Legacy Option Roms enabled/ AHCI enabled / Secure Boot disabled Use attached files as the bootpack after you had install Clover per Guide Replace file contents into /EFI/Clover E5540_Catalina.zip
  19. 1 point
    You've got no patched DSDT and, in your Clover config, you've selected ACPI patch "InjectDarwin" instead of "InjectDarwin7". The former sets the OS to Win XP when the latter sets the OS to Win7, i.e. what you need to activate USB3.0 controller support. That or you patch your DSDT to simply inject DSDT alongside Windows Vista ("Windows 2006") or Windows 7 ("Windows 2009").
  20. 1 point
    try this, replace Config and add kext to kexts/Other usb.zip
  21. 1 point
    You should consult our Wifi list and here That model is poorly supported. Further more I don't know if your particular system has whitelisting for wifi devices. @Max.1974 recommended a Lenovo model wifi card so you might have to verify for yourself. I know some models like T470/T480 does not have whitelisting for Wifi devices.
  22. 1 point
    That's right - all working with layout 3. And for my surprise, I got a bonus bluetooth working !!!! I've bought a DW1707 that will arrive tomorrow.
  23. 1 point
  24. 1 point
    Nothing to worry about those ACPI errors; you may just need some additional tuning re: DSDT/ACPI patching
  25. 1 point
    Yo Jake, cuz u seem to be the goat here. do u have any complete guide to hackintosh catalina on a e5540 been trying but i only can get the configs for mojave and of course they differ. any help would be appreciated! thanks!
  26. 1 point
    Sure but you'll lose the track stick as well. Remove ApplePS2Mouse.kext plugin in ApplePS2Controller.kext Reboot
  27. 1 point
    Heya! After a lot of playing around with ASUS acpi tables I have finally come up with a SSDT that will work nearly on all ASUS laptops (Haswell or above) for reading FAN RPM, CPU TEMP and also Custom Controlling FAN. I do not have hardware below Haswell so can't test. If someone get's it working using this SSDT on machines prior to haswell. Let me and others know. Background Info: The system FAN is generally controlled by the embedded controller (EC) but there are methods in ACPI that can let you read and control your system FAN. As you might know, ASUS machines are the best for hackintosh as they have the best written ACPI code. Like, if it was HP instead of ASUS you would have to acquire a mutex object. Write a value to the EC and then release the object. But in ASUS machines there is a method that takes arguments and does this job automatically. Still. There are multiple methods in our DSDT that allow us to read and control system FAN. For example to read FAN speed, there are two ways. If you observe, the FAN speed is at offset 0x93 of EC (Use RWEverything to find out) So, when we search for Offset 0x93 in the DSDT we get a result like this: Offset (0x93), TAH0, 16, // TAH0 stands for FAN1 TAH1, 16, // TAH1 stands for FAN2 (in case your laptop has 2 fans) TSTP, 16, // TSTP stores current fan value in some bytes Note: Instead of using RWEverything if you have a look at method TACH you can see that it stores the values in TAH0 and TAH1 depending upon the Args supplied. So, searching for TAH0 or TAH1 we can see that they are located at offset 0x93 So, now we can read the value from these registers in some units and then we will have to use some formula to convert that unit to RPM. In order to find that formula, if you have a look at Method TACH in dsdt, you will see: Method (TACH, 1, Serialized) { Name (_T_0, Zero) If (ECAV ()) { While (One) { _T_0 = Arg0 If ((_T_0 == Zero)) { Local0 = TAH0 Break } ElseIf ((_T_0 == One)) { Local0 = TAH1 Break } Else { Return (Ones) } Break } Local0 *= 0x02 If ((Local0 != Zero)) { Divide (0x0041CDB4, Local0, Local1, Local0) Return (Local0) } Else { Return (Ones) } } Else { Return (Ones) } } So, we know that we have to store the value from TAH0 or TAH1 (depends on Arg0) and then we have to multiply it by 2 and then we have to divide it by 0x0041CDB4 (4312500) to get the value in RPMs. Once we know that, we could write a simple ACPI code to return the value in RPMs like: // GRPM means get RPM Method (GRPM, 0) { // Store value in Local0 Local0 = \_SB.PCI0.LPCB.EC0.TAH0 // If local0 is not equal to 0 If (Local0 != 0){ // Multiply by 2 Local0 = Local0 * 2 // Divide by 4312500 Divide (0x0041CDB4, Local0, Local1, Local0) } // Return the value Return (Local0) } As you can see this is very expensive method. But what we learned here is, If we execute method TACH with Arg0 as 0 (Zero) it will give us the speed in RPM of FAN 1. Similarly, if we use Arg0 as 1 (One) it will return the value in RPM for FAN 2 My laptop only has one FAN so, I can execute method TACH like, \SB.PCI0.LPCB.EC0.TACH(0) // Using Arg0 as Zero for FAN 1 And it will give me FANs RPM, so, instead of reading from EC and converting bits to RPM this is more preferable. Also, EC bytes may change while patching DSDT so it is a good idea to use dynamic methods so that a single SSDT could work for all machines. One such example is, If you use ACPIBatteryManager then you will have to convert 16bits registers to 8bits. And then, to use that "reading RPM from EC method you will have to create a new method to combine 2 8 bits registers to 1 16 bit like, // JEBR = Join 8 bit registers Method (JEBR, 2) { Return ((Arg0 | (Arg1 << 8))) // Arg0 and Arg1 will be 8Bit register 1 and 2 respectively (AH00, AH01) } Now moving to FAN control, If you have a look at method QMOD in DSDT: Method (QMOD, 1, NotSerialized) { If ((Arg0 == Zero)) { Return (Zero) // If arg0 is Zero. Terminate by returning 0 } If ((Arg0 == One)) { ^^PCI0.LPCB.EC0.ST98 (QFAN) // Hmm, ST98 is somewhat related to FAN control } If ((Arg0 == 0x02)) { ^^PCI0.LPCB.EC0.ST98 (0xFF) // Okay, ST98 again.. Something is interesting } Return (One) } Now, if you look at ST98 you can see: Method (ST98, 1, Serialized) { If (ECAV ()) // Checked if EC is available, will you write to it? { Acquire (MU4T, 0xFFFF) // Oh! So you are acquiring a mutex object CMD = 0xFF EDA1 = 0x98 EDA2 = Arg0 // Oh, so you did write Arg0 in EDA2 (Located in EC01 OperationRegion) ECAC () Release (MU4T) // Released it here, you did write something to the EC for sure Return (Zero) } Return (Ones) } Now, we can understand that, method QMOD (Quiet Mode?) Takes 1 argument that could be (0, 1 or 2). We can eliminate 0 as when we pass Arg0 as 0 it simply returns. Interesting are args 1 and 2 When using 1 it passes Arg0 to ST98 as QFAN's value (Hmm.. What is this QFAN) When using 2 it passes Arg0 to ST98 as 0xFF (255) (Oh wait! according to ACPI spec, 255 is max allowed FAN value.) Gotcha! We can use ST98 and pass it an arg ranging between 0x0 (0) to 0xFF (255) where 0 is for FAN off and 255 is for Max allowed or auto. But, why is there a QMOD method then? There might be some good reason for that. So, we will not invoke ST98 directly but will use the modus operandi of method QMOD Like, we will first store that max allowed FAN value in QFAN Then, we will invoke QMOD with Arg0 as 1 (One). Which will invoke ST98 for us hence, setting the max allowed speed for FAN. So, the ACPI code for this would be: Method (SETR, 0) { QFAN = 200 // Suppose we want to use max allowed value as 200 // Now we can call QMOD with Arg0 as 1 QMOD (1) } Now we know what to do. We now just need to write a method that can calculate the CPU temperature and then set FAN RPM accordingly. This is when you will use my SSDT-FAN How to implement: Requirements: FakeSMC kext along with sensors installed at /L/E or /S/L/E (DO NOT INJECT USING CLOVER) ACPIPoller.kext HWMonitor for monitoring CPU Temp and FANS My SSDT-FAN.aml Installation: Place SSDT-FAN.aml to /EFI/CLOVER/ACPI/patched (If using sorted order make sure you add SSDT-FAN to it) Install ACPIPoller to /L/E or /S/L/E (not both and definitely do not inject using CLOVER) Configuration: You can set "Name (UCFC, One)" to "Name (UCFC, Zero)" in my SSDT-FAN in case you want to use default FAN control method as provided by your OEM. My SSDT will only provide FAN RPM reading and CPU Temp reading.Achievements: Default scaling that ASUS provided was from 2200RPM to 2900RPM (Fan spinning fast without use) I managed to bring scale it from 255RPM to 5026RPM (Fan turns off if temp Temp rarely goes above 53˚C (Went up to 68 earlier) Technicalities: As we know know how to implement custom fan control using various methods in our DSDT we can't really use them as is in real life scenarios as FAN will literally be dancing. You might have observed that temperature keeps fluctuating a few degrees every second while you are working on something. Moreover, we need an automated method that can read and set FAN RPM. So, my SSDT calculates average temperature and then also waits for 2 seconds (to handle fluctuation) before increasing the RPM and waits for 5 seconds (to let CPU cool) before lowering RPM. You can edit this timeout by editing "Name (FCTU, 2)" for FanControlTimeoutUp and "Name (FCTD, 5)" for FanControlTimeoutDown. Method to calculate average accredited to RehabMan as he wrote the code first. There is only one known way to calculate average in maths. LOL. If you want to know how it is implemented, read this code: Note: This code is a part of my single optimizer SSDT project for ASUS laptops (Means, I am working on a single SSDT that you could place in your CLOVER/ACPI/patched and will have everything working without patching DSDT. You can customize SSDT using Device ANKD (A Nick's Device) like you can configure this SSDT to use custom FAN control or not). You can have a look at WIP code here // SSDT for FAN readings and custom FAN control for ASUS laptops // Copyright, black.dragon74 <www.osxlatitude.com> // Please configure the options in Device ANKD before compiling this SSDT DefinitionBlock("SSDT-FAN", "SSDT", 2, "Nick", "AsusFan", 0) { // Declare externals External (\_SB.QFAN, FieldUnitObj) External (\_SB.ATKD.QMOD, MethodObj) External (\_SB.PCI0.LPCB.EC0.ECAV, MethodObj) External (\_SB.PCI0.LPCB.EC0.ECPU, FieldUnitObj) External (\_SB.PCI0.LPCB.EC0.ST83, MethodObj) External (\_SB.PCI0.LPCB.EC0.ST98, MethodObj) External (\_SB.PCI0.LPCB.EC0.TACH, MethodObj) // Create a Nick's device to take care of this SSDT's configurations Device (ANKD) { Name (_HID, "ANKD0000") // Required. DO NOT change Name (UCFC, 1) // Set this to 0 if you don't wanna use my custom FAN control } // Create devices required by FakeSMC_ACPISensors Device (SMCD) { Name (_HID, "FAN0000") // Required, DO NOT change // Add tachometer Name (TACH, Package() { "System FAN", "FAN0" }) // Add CPU heatsink Name (TEMP, Package() { "CPU Heatsink", "TCPU" }) // Method to read FAN RPM (tachometer) Method (FAN0, 0) { // Check is EC is ready If (\_SB.PCI0.LPCB.EC0.ECAV()) { // Continue Local0 = \_SB.PCI0.LPCB.EC0.ST83(0) // Method ST83 acquires mutex and writes value to EC. O stands for FAN 1, Use 1 for FAN 2 If (Local0 == 255) { // If ST83 is 0xFF (Max fan speed) terminate by returning FAN RPM Return (Local0) } // Else, Get RPM and store it in Local0 Local0 = \_SB.PCI0.LPCB.EC0.TACH(0) // Method TACH in DSDT returns current FAN RPM in 100s, Arg0 as 0 is for FAN 1, for FAN 2, use Arg0 as 1 } Else { // Terminate, return Zero Local0 = 0 } // Return 255, 0 or Fan RPM based on conditionals above Return (Local0) } // Method to read CPU temp (CPU Heatsink) Method (TCPU, 0) { // Check if EC is ready If (\_SB.PCI0.LPCB.EC0.ECAV()) { // Then Local0 = \_SB.PCI0.LPCB.EC0.ECPU // EC Field storing current CPU temp Local1 = 60 // From DSDT If (Local0 < 128) { Local1 = Local0 } } Else { // Terminate, return Zero Local1 = 0 } // Return final CPU temp. ACPISensors take care of unit conversion. Return (Local1) } // Custom FAN table by black.dragon74 for ASUS laptops based on RehabMan's idea // Quietest fan operation yet coolest CPU. // Scaling from values as low as 255 RPM to values as high as 5026 RPM (That's great!) // Scaling that ASUS provided was from 2200 RPM to 2900 RPM (Duh!) // Temperatures. 0xFF means if temp is above 52C, let bios take control of things(auto). Name(FTA1, Package() { 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 0xFF, }) // Fan speeds. 255(0xFF) is max/auto, 0(0x00) is for fan off Name(FTA2, Package() { 0, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 110, 120, 130, 140, 160, 185, 205, 225, 245, 250, 255 }) // Time out values Name (FCTU, 2) // RPM Up Name (FCTD, 5) // RPM Down // Table to keep track of past temperatures (to track average) Name (FHST, Buffer() { 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }) // Size should match the count of above FTA1 and FTA2 package Name (FIDX, 0) // current index in buffer above Name (FNUM, 0) // number of entries in above buffer to count in avg Name (FSUM, 0) // current sum of entries in buffer // Keeps track of last fan speed set, and counter to set new one Name (FLST, 0xFF) // last index for fan control Name (FCNT, 0) // count of times it has been "wrong", 0 means no counter // Method to control FAN wrt TEMP // Name in ACPIPoller.kext's Info.plist should be FCPU with HID FAN0000 Method (FCPU, 0) { // If UCFC is set to 0, terminate If (\ANKD.UCFC == 0) { Return (0) } // If EC is not ready, terminate If (!\_SB.PCI0.LPCB.EC0.ECAV()) { Return (0) } Local5 = \_SB.PCI0.LPCB.EC0.ECPU // Current temperature of the CPU Heatsink If (Local5 < 128) { Local0 = Local5 // Store temperature in Local0 } Else { Local0 = 60 // As per BIOS } // calculate average temperature Local1 = Local0 + FSUM Local2 = FIDX Local1 -= DerefOf(FHST[Local2]) FHST[Local2] = Local0 FSUM = Local1 // Local1 is new sum // adjust current index into temperature history table Local2++ if (Local2 >= SizeOf(FHST)) { Local2 = 0 } FIDX = Local2 // adjust total items collected in temp table Local2 = FNUM if (Local2 != SizeOf(FHST)) { Local2++ FNUM = Local2 } // Local1 is new sum, Local2 is number of entries in sum Local0 = Local1 / Local2 // Local0 is now average temp // table based search (use avg temperature to search) if (Local0 > 255) { Local0 = 255 } Local2 = Match(FTA1, MGE, Local0, MTR, 0, 0) // calculate difference between current and found index if (Local2 > FLST) { Local1 = Local2 - FLST Local4 = FCTU } else { Local1 = FLST - Local2 Local4 = FCTD } // set new fan speed, if necessary if (!Local1) { // no difference, so leave current fan speed and reset count FCNT = 0 } else { // there is a difference, start/continue process of changing fan Local3 = FCNT FCNT++ // how long to wait depends on how big the difference // 20 secs if diff is 2, 5 secs if diff is 4, etc. Local1 = Local4 / Local1 if (Local3 >= Local1) { // timeout expired, so start setting new fan speed FLST = Local2 // Method 1 (Recommended) // Store custom fan value from table in Local5 Local5 = DerefOf(FTA2[Local2]) // Set QFAN value to that of Local5 \_SB.QFAN = Local5 // Execute QMOD with Arg0 as 1(One) to set FAN's max allowed speed to that of \_SB.QFAN \_SB.ATKD.QMOD(1) // End Method 1 // Method 2 (Works but not recommended) Uncomment the line below to use this (remember to comment lines in method 1) // \_SB.PCI0.LPCB.EC0.ST98 (DerefOf(FTA2[Local2])) // End Method 2 // Reset FAN count (Required in either methods) FCNT = 0 } } Return (1) // Return something as this is a requirement of a ACPI Method } } } Moment of joy: Problem Reporting: Attach proper problem reporting files. See How to generate proper problem reporting files Note: If you see FAN RPM = 255 and hear a lot of noise from FAN it means your FAN is running at it's maximum speed. Regards ACPIPoller.zip SSDT-FAN.zip
  28. 1 point
    Bronxteck recently reminded us of links Apple publish in relation to creating bootable installers for OS X and macOS from El Capitan 10.11, so here's a link to the related main page: https://support.apple.com/en-us/HT201372 Very useful as a replacement to the old AppStore method that allowed registered users to re-download an OS X/macOS installation package if they had already done so in the past. 12GB required for USB keys/flash disks. Whilst the information is obviously meant for Apple Mac computers, it's nevertheless 100% relevant to the 1st phase of creating USB installers for Hackintosh computers, the 2nd phase being the necessary installation of the bootloader (Enoch, Clover or otherwise).
  29. 1 point
    https://www.digitaltrends.com/computing/how-to-clone-a-hard-drive/
  30. 1 point
    yes you can backup your OS's but i am not sure of what third party tool can handle APFS other then apples disk utility. you can clone existing partitions back to a new drive after partitioning the new drive respectively. sometimes its simpler to use a third party app like clonzilla or carbon copy cloner or similar.
  31. 1 point
    The files here uses hot patching, so it's not BIOS dependent like my earlier bootpacks.
  32. 1 point
    Just updated BIOS to A20 and all is working perfectly with Cover patches and patched A19 DSDT. This being said try and adjust your Clover config with Clover configurator app to compare: ACPI config remove PluginType Add Drop SSDT CpuPm Add Drop SSDT Cpu0Ist
  33. 1 point
    @kup1 No kext is needed, just follow instructions here to inject the device https://osxlatitude.com/forums/topic/7346-applesdxc-driverdsdt-patch-for-o2-micro-sd-card-readers/?do=findComment&comment=87652
  34. 1 point
    Last update: 09 Oct 2019 This 2nd inventory comes to complement our original one created back in 2013 and that has been modified to cover wireless cards under Mac OS X/OS X, from Snow Leopard 10.6 to El Capitan 10.11. This new list will provide the same for macOS versions given that it's getting complicated to keep everything under a single text table and Apple has been increasingly dropping support for some cards since the introduction of macOS Sierra in 2016. I invite everyone to bring his/her own contribution and it'll be added to the list. This post will be updated as contributions come along in order to keep the list under control. Hardware specifications can be verified here: http://wikidevi.com/wiki/Main_Page Note: OOB = Out of the Box /!\ Sierra 10.12 dropped support for old Broadcom BCM431x and BCM4321 cards. There is no workaround, they have to be replaced. /!\ /!\ Mojave 10.14 dropped support for Atheros cards. The workaround is to install the Atheros40 kext from an earlier release like High Sierra 10.13.6, i.e. copy to /L/E + repair permissions + rebuild cache. /!\ 10.13.6_AirPortAtheros40.kext.zip /!\ Catalina 10.15 dropped support for BCM4322 (14e4:432b) chip. AirPortBrcm4331 plugin kext of IO80211Family kext was abandoned. This affects cards such as DW1510. Workaround is to replace Catalina's IO802Family kext by Mojave's (or High Sierra's) in /S/L/E. /!\ 10.14.6_IO80211Family.kext.zip /!\ Catalina 10.15 no longer supports injection or caching of High Sierra's AirPortAtheros40 kext. Instead, the whole IO80211Family kext must be replaced by High Sierra's in /S/L/E. /!\ 10.13.6_IO80211Family.kext.zip Unsupported: Vendor Model Format Ven-Dev Chip Rate Si HS Mj Ca OOB Kext (driver) Atheros AR5BXB6 Mini PCIe 168c-001c AR5424 A/B/G N N N N - - AzureWave AW-CB161H ½Min PCIe 10ec-8821 RTL8821AE A/B/G/N/AC N N N N N N N - - AzureWave AW-CB209NF NGFF/M.2 10ec-8821 RTL8821AE A/B/G/N/AC N N N N N N N - - AzureWave AW-CB210NF NGFF/M.2 14e4-43ec BCM4356 A/B/G/N/AC N N N N N N N - - Dell DW1390 Mini PCIe 14e4-4311 BCM4311 B/G N N N N - - Dell DW1395 Mini PCIe 14e4-4315 BCM4312 B/G N N N N - - Dell DW1490 Mini PCIe 14e4-4312 BCM4311 A/B/G N N N N - - Dell DW1505 Mini PCIe 14e4-4328 BCM4321 A/B/G/N N N N N - - Dell DW1397 ½Min PCIe 14e4-4315 BCM4312 B/G N N N N - (=DW1395) Dell DW1501 ½Min PCIe 14e4-4727 BCM4313 A/B/G/N N N N N - - Dell DW1503 ½Min PCIe 14e4-4727 BCM4313 A/B/G/N N N N N - - Dell DW1504 ½Min PCIe 14e4-4727 BCM4313 B/G/N N N N N - - Dell DW1530 ½Min PCIe 14e4-4359 BCM43228 A/B/G/N N N N N - - Dell DW1540 ½Min PCIe 14e4-4359 BCM43228 A/B/G/N N N N N - - Dell DW1701 ½Min PCIe 14e4-4727 BCM4313 B/G/N N N N N - - Dell DW1704 ½Min PCIe 14e4-4365 BCM43142 B/G/N N N N N - - Dell DW1810 NGFF/M.2 168c:0042 QCA9377 A/B/G/N/AC N N N N - (=QCNFA435) Dell DW1820 NGFF/M.2 168c:003e QCA6174A A/B/G/N/AC N N N N - (=QCNFA344A) Intel All - - - - N N N N - No exception! Qualcomm QCNFA435 NGFF/M.2 168c-0042 QCA9377 A/B/G/N/AC N N N N - - Qualcomm QCNFA344A NGFF/M.2 168c-003e QCA6174A A/B/G/N/AC N N N N - - Ralink RT5390 ½Min PCIe 1814-539b RT5390 B/G/N N N N N - - Supported: Vendor Model Format Ven-Dev Chip Rate Si HS Mj Ca OOB Kext (driver) Atheros AR5B91 Mini PCIe 168c-002a AR9281 B/G/N Y Y * * Y * See above for Mojave Atheros AR5BXB72 Mini PCIe 168c-0024 AR5418/5133 A/B/G/N Y Y * * N patch Atheros40 Atheros AR5BXB92 Mini PCIe 168c-002a AR9280 A/B/G/N Y Y * * Y - Atheros AR5BXB112 Mini PCIe 168c-0030 AR9380 A/B/G/N Y Y * * Y - Atheros AR5B22 Mini PCIe 168c-0034 AR94621 A/B/G/N Y ? * * N FW + Atheros40 patch Atheros AR5B93 ½Min PCIe 168c-002a AR9283 B/G/N Y Y * * Y - Atheros AR5B95 ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * N DSDT/Atheros40 patch Atheros AR5B97 ½Min PCIe 168c-002e AR9287 B/G/N Y Y * * N DSDT/Atheros40 patch Atheros AR5B195 ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * N (=AR5B95+BT3.0) Atheros AR5B197 ½Min PCIe 168c-002e AR9287 B/G/N Y Y * * N (=AR5B97+BT3.0) Atheros AR5BHB92 ½Min PCIe 168c-002a AR9280 A/B/G/N Y Y * * Y - Atheros AR5BHB112 ½Min PCIe 168c-0030 AR9380 A/B/G/N Y Y * * Y - Atheros AR5B125 ½Min PCIe 168c-0032 AR94851 B/G/N Y ? * * N FW + Atheros40 patch Atheros AR5B225 ½Min PCIe 168c-0032 AR94851 B/G/N Y ? * * N FW + Atheros40 patch AzureWave AW-NB037H ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * N (=AR5B195) AzureWave AW-NB048H ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * N (=AR5B195) AzureWave AW-NB290H ½Min PCIe 14e4-4357 BCM43225 B/G/N Y Y Y ? N DSDT/Brcm4360 patch AzureWave AW-CE123H ½Min PCIe 14e4-43b1 BCM4352 A/B/G/N/AC Y Y Y Y N DSDT/Brcm4360 patch AzureWave AW-CB160H ½Min PCIe 14e4-43a0 BCM4360 A/B/G/N/AC Y Y Y Y Y - Dell DW1502 ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * Y (=AR5B95) Dell DW1506 ½Min PCIe 168c-0032 AR94851 B/G/N Y ? * * N (=AR5B125) Dell DW1510 ½Min PCIe 14e4-432b BCM4322 A/B/G/N Y Y Y * Y - Dell DW1515 ½Min PCIe 168C-002a AR9280 A/B/G/N Y Y * * Y (=Atheros xB92) Dell DW15202 ½Min PCIe 14e4-4353 BCM43224 A/B/G/N Y Y Y Y Y/N MBA5,2/Brcm4360 patch Dell DW1550 ½Min PCIe 14e4-43b1 BCM4352 A/B/G/N/AC Y Y Y Y N DSDT/Brcm4360 patch Dell DW1601 ½Min PCIe 168c-0034 AR94621 A/B/G/N/AD Y Y ? ? N (=AR5B22) Dell DW1702 ½Min PCIe 168c-002b AR9285 B/G/N Y Y ? ? N (=AR5B195) Dell DW1703 ½Min PCIe 168c-0032 AR94851 B/G/N Y Y ? ? N (=AR5B225) Dell DW1705 ½Min PCIe 168c-0036 AR95651 B/G/N Y Y ? ? N FW + Atheros40 patch Dell DW1560 NGFF/M.2 14e4-43b1 BCM4352 A/B/G/N/AC Y Y Y Y N DSDT/Brcm4360 patch Dell DW1707 NGFF/M.2 168c:0036 AR95651 B/G/N Y Y ? ? N FW + Atheros40 patch Dell DW1802 NGFF/M.2 168c-0034 AR94621 A/B/G/N Y Y ? ? N (=AR5B22) Dell DW1820A3 NGFF/M.2 14e4-43a3 BCM43503 A/B/G/N/AC Y Y Y Y N DSDT patch/injection Dell DW1830 NGFF/M.2 14e4-43ba BCM43602 A/B/G/N/AC Y Y Y Y Y - Asus USB-N10 USB 2.0 0b05-1786 RTL8188SU B/G/N ? ? ? ? N RealTek's v2.0.1 Asus USB-AC51 USB 2.0 0b05-17d1 MT7610U A/B/G/N/AC ? ? ? ? N Asus's driver CSL Nano V.2 USB 2.0 0bda-8176 RTL8188CUS B/G/N ? ? ? ? N RealTek's v2.0.1 D-Link DWA-121 A1 USB 2.0 2001-3308 RTL8188CUS B/G/N ? ? ? ? N RealTek's v2.0.1 Lafalink LF-D10 Nano USB 2.0 148f-7601 MT7601 B/G/N ? ? ? ? N Ralink's v4.2.9.10 Lafalink LF-D12 Nano USB 2.0 148f-5370 RT5370 B/G/N ? ? ? ? N Ralink's v4.2.9.2 NetGear WNA3100M USB 2.0 0846-F001 RTL8192CU B/G/N ? ? ? ? N Realtek's v2.0.1 On-Nwrks N300 USB 2.0 0846-F001 RTL8192CU B/G/N ? ? ? ? N Realtek's v2.0.1 Tenda W522U USB 2.0 148f-3572 RT3572 A/B/G/N Y Y ? ? N TP-Link/Ralink TP-Link TL-WN725N v2 USB 2.0 0bda-8179 RTL8188EUS B/G/N Y Y Y ? N TP-Link's driver TP-Link TL-WN723N v3 USB 2.0 0bda-8179 RTL8188EUS B/G/N Y Y Y ? N TP-Link's driver TP-Link TL-WN823N v1 USB 2.0 0bda-8178 RTL8192CU B/G/N Y Y Y ? N TP-Link's driver TP-Link TL-WN823N v2 USB 2.0 2357-0109 RTL8192EU B/G/N Y Y Y ? N TP-Link's driver TP-Link TL-WN823N v3 USB 2.0 ????-???? ???? B/G/N ? ? Y ? N TP-Link's driver Asus USB-AC56 USB 3.0 0b05-17d2 RTL8812AU A/B/G/N/AC ? ? ? ? N Asus's driver Asus PCE-AC66 PCIe x1 14e4-43a0 BCM4360 A/B/G/N/AC Y Y Y Y Y - Asus PCE-AC68 PCIe x1 14e4-43a0 BCM4360 A/B/G/N/AC Y Y Y Y Y - TP-Link TL-WN781ND v1 PCIe x1 168c-002b AR9285 B/G/N Y Y * * N DSDT/Atheros40 patch TP-Link TL-WDN4800 PCIe x1 168c-0030 AR9380 A/B/G/N Y Y * * Y - TP-Link Archer T9E PCIe x1 14e4-43a0 BCM4360 A/B/G/N/AC Y Y Y Y Y - NB: Patching means adding the PCI ids of the listed card to the Info.plist file found inside the listed kext. In rare cases, binary patching may also be necessary. For some cards, DSDT Patching can be a suitable and permanent alternative to kext patching (no need to repatch a kext after OS X updates and upgrades or new installations). For instance, in the case of the Atheros AR5B95 card (chip AR9285 168c,2b), adding compatibility with a chip known to be supported OOB such as AR9380 168c,30 or AR9280 168,2a (as found in the vanilla Atheros40 kext) in a _DSM method for the identified DSDT device does the trick once and for all since it'll make the OS load the associated kext: Device (<YourDevice>) // Identified wireless device through IORegistryExplorer (usually: ARPT) { ... ... ... Method (_DSM, 4, NotSerialized) // Device Specific Method for the wireless card { Store (Package () { "model", Buffer (0x1E) { "Atheros AR5B95 b/g/n Wireless" }, "device_type", Buffer (0x08) { "AirPort" }, "built-in", Buffer (One) { 0x00 }, "name", Buffer (0x10) { "AirPort Extreme" }, "AAPL,slot-name", Buffer (0x09) { "Internal" }, "compatible", // Declares compatibility with a device Buffer (0x0B) { "pci168c,30" // PCI id of device supported OOB } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } ` In the same respect, in the case of the Broadcom BCM4322x cards (e.g.: chip BCM43225 14e4,4357), adding compatibility with a chip known to be supported OOB such as BCM94360 14e4,43ba or 14e4,43a0 (as found in the vanilla AirPortBrcm4360 kext) in a _DSM method for the identified DSDT device does the trick once and for all since it'll make the OS load the associated kext: Device (<YourDevice>) // Identified wireless device through IORegistryExplorer (usually: ARPT) { ... ... ... Method (_DSM, 4, NotSerialized) // Device Specific Method for the wireless card { Store (Package () { "model", Buffer (0x23) { "AzureWare AW-NB290H b/g/n Wireless" }, "device_type", Buffer (0x08) { "AirPort" }, "built-in", Buffer (One) { 0x00 }, "name", Buffer (0x10) { "AirPort Extreme" }, "AAPL,slot-name", Buffer (0x09) { "Internal" }, "compatible", // Declares compatibility with a device Buffer (0x0B) { "pci14e4,43a0" // PCI id of device supported OOB } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } ________________ 1 AR946x (168c,34), AR9485 (168c,32) and AR9565 (168c,36) work to some degree (i.e. not 100%) with alternative (re-written) Atheros40 driver as posted at InsanelyMac by Chunnann. Further patching facility posted here. These cards appear very poorly supported to plain unsupported from High Sierra. They are NOT recommended. 2 DW1520 (14e4,4353) is known to suffer from frequent and repeated wireless disconnections when plugged into mini PCIe-only slot and built-in Bluetooth is enabled. This may even lead to wireless turning off. This has been noticed on Dell Latitude E6x20 and E6x30. Wireless works Ok once built-in Bluetooth is disabled in BIOS or, as stated by wl_michael, if the card is fitted into combo PCIe/USB slot such as WWAN. 3 DW1820A and other BCM4350-based cards are not all supported. See our BCM4350 guide for these cards. * See top of post for Mojave and Catalina
  35. 1 point
    Catalina Catalina Guide Bootpack - HD5500 Only Replace into /EFI/Clover after you install Clover E7450_Catalina.zip - For Discrete Model Also add this to /EFI/Clover/ACPI/Patched SSDT-Disable-DGPU FYI, kexts in bootpack might be outdated Make sure to 1st upgrade kexts found under /EFI/CLOVER/kexts/Other if you encounter issue Common links for new kexts: https://github.com/vit9696/Lilu/releases https://github.com/vit9696/Lilu/blob/master/KnownPlugins.md https://bitbucket.org/RehabMan/ Follow Post Install above under Sierra Guide UPDATES Catalina 10.15.1 (19B88) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: INSTALL LATEST CLOVER / UPDATE KEXTS PRIOR TO UPDATE REPAIR PERMISSIONS AND REBUILD CACHE
  36. 1 point
    are they salty? salty ones don't work as well as non salty ones.
  37. 1 point
    Target macOS release: Mojave 10.15.x This is a Clover-based installation using the well-known/well documented vanilla method detailed below: Working: full graphics acceleration on Intel UHD620 iGPU, including brightness control (with Lilu v1.3.8 + WEG v1.3.2) multi-display with HDMI OOB, including HDMI-to-DVI adaptation (HDMI-to-VGA not successful) audio, including HDMI, microphone input and headset output (with AppleALC v1.3.9 & layout 11 + CodecCommander v2.7.1) GigEthernet LAN connection (with IntelMausiEthernet 2.4.0 kext) wireless and bluetooth with any compatible card (a DW1820A in my case) left and right USB ports (with Hackintool-generated USBPorts) integrated webcam (OOB) CPU power management sleep (Lid, Energy Saver settings, Apple menu, Fn-Insert, PWR button) & wake (Lid, PWR button) battery management (with ACPIBatteryManager v1.90.1) keyboard (with VoodooPS2Controller v1.9.2) touchpad (with VoodooI2C v2.1.4 + VoodooI2CHID v1.0), including tap-to-click (mandatory in PrefPane settings), scroll & zoom, rotate or other multi-finger gestures. On occasions, won't work until system is rebooted one or several times. Not working: RTS525a microSD card reader Touchpad buttons TrackPoint Not tested: DP over USB Type-C display output 1) 10.15 USB installer creation Using a USB key of 8GB minimum, create a Catalina USB installer through the following Terminal command: sudo <path>/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of Catalina installation package (eg: /Applications if freshly downloaded) <USB key> = name of formatted USB volume (eg: USB_8GB) 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 ApfsDriverLoader AptioMemoryFix AudioDxe DataHubDxe FSInject HFSPlus SMCHelper Human Interface Devices Ps2MouseDxe UsbMoueDxe File system Drivers Fat Additional Drivers NvmExpressDxe PartitionDxe Themes (optional) Install Clover Preference Pane (optional) you may use version r5093 attached below: Clover_v2.5k_r5093.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 7490 Catalina Clover pack below to the EFI/Clover folder: 7490_Catalina_Clover_Pack.zip 7490_Catalina_Clover_Pack_#2.zip 2) 10.15 installation boot the Catalina USB installer at the Clover main menu, select the "Install macOS Catalina" 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 Catalina installation through Disk Utility as/if required on 1st reboot, boot off the USB installer and select the freshly created "macOS install from <target Catalina partition>" repeat this until this partition is no longer offered and only the target Catalina partition is left to boot Reboot the target Catalina partition via your USB installer 3) Post-installation tuning Once the target Catalina partition has booted, complete the 1st boot configuration tuning Once at the desktop, install Clover bootloader on the Catalina 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 Catalina partition/disk Open this EFI partition and transfer the files & folders from the above Latitude 7490 Catalina Clover pack to the EFI/Clover folder You may then reboot and verify that Catalina boots off your disk through Clover Edit: 02 Nov 2019: - - - - - - - - - - - - Revised Clover pack #2: DW1820A properties injection commented out (only required for those who have such a card, in which case, remove the # character)
  38. 1 point
    Hey Folk - here goes first post I have lurked for a number of years and built a number of hackintoshes in the past but recently started looking at getting Mojave installed on my Dell Precision 7510. The specs are as follows: Intel(R) Xeon(R) E3-1505M v5(Quad Core 2.80GHz, 3.70GHz Turbo, 8MB 45W, w/Intel HD Graphics P530) Nvidia Quadro M1000M w/2GB GDDR5 Samsung 950 ProNVMe Drive Samsung 850 Pro 2 TB SSD At the moment I have Ubuntu and data stored on these 2 drives so the M2 interface has been disabled in the BIOS and the 2 TB SSD has been replaced with a new Samsung 860 1TB QVO SSD I am planning on purchasing a Broadcom Wifi card (any advise on what to get appreciated). I have been trying to build this all pretty slowly and understand all steps involved but been struggling to actually do this and have reverted to using an EFI\CLOVER folder that I found on a TM thread (#54). I tried for quite a few hours last night to build up my own EFI\CLOVER from scratch however could never quite get things booting. Not ideally what I wanted to do but I am sure this EFI\CLOVER might be a good starting point. I have disabled the dGPU using modified version of Dell_E6540_UEFI_eGPU_configurator_by_nando4 so I am now trying to get the IGPU P530 working. At the moment "No Kext Loaded" is shown however I have tried setting the AAPL,ig-platform-id to a supportable 191b from the actual 191d This seems to show in IOReg but something is not working or I'm missing something. I've attached EFI and IOReg - any help appreciated nickelnoff-precision7510-200819.zip
  39. 1 point
    Slight change - found the following - Seems to provide me with all working USB ports ! Thanks @Jake Lo Just to confirm P530 is still trouble: To double confirm here is fresh EFI.zip and IOReg. nickelnoff-precision7510-200819-new.zip
  40. 1 point
    Hi all, have been playing around with the driver to see if I can get firmware upload in Mojave to work on my dw1820a without needing windows to upload the firmware. It seems to be working ok , but am still testing to see if it works consistently. Attaching the kexts if anyone else would like to try with their dw1820a. These need to be uploaded to /EFI/CLOVER/Kexts/Other. Make sure you don't have any equivalent kexts in /L/E or /S/L/E. Let me know if you have any success. BrcmBluetoothInjector.kext.zip BrcmFirmwareData.kext.zip BrcmPatchRAM2.kext.zip
  41. 1 point
    Last update: 16 Apr 2019 EDP being in semi-permanent revamp, here are full packs for the Latitude D620/D630 series. The packs do not require any subsequent EDP tuning at all, they provide everything required to obtain a fully working system (CPU power management, graphics, LAN, audio, keyboard, trackpad), non-OOB wireless, bluetooth and any other devices excluded of course. However, some manual tuning for proper Sleep/Wake operation is required: setting hibernation mode to plain old sleep and deleting any eventual sleep image file. This is done through the following Terminal commands upon final OS X installation: sudo pmset -a hibernatemode 0 sudo pmset -a hibernatefile /dev/null sudo rm -f /var/vm/sleepimage Vanilla support stops at Lion 10.7.5 for all Intel GMA based models and the D620 nVidia due to GPU support limitations. For those systems, ML may be installed and tuned back to 32bit operation through MLPF hack. Look at the Dell installation guides forum subsection for MLPF'ed ML guides and packs. It's not 100% bug-free though... Only the D630 nVidia supports vanilla installation of Mountain Lion, Mavericks, Yosemite, El Capitan, Sierra and High Sierra (Sierra & HiSie only with Penryn CPUs). For all models, read the Performance tuning thread for CPU + GPU tuning if required but the FakeSMC kext included in the packs below brings it all. D620 GMA950 LoRes (WXGA 1280x800): D620_GMA950_LoRes_10.6.8_Pack.zip D620_GMA950_LoRes_10.7.5_Pack.zip D620 GMA950 HiRes (WXGA+ 1440x900): D620_GMA950_HiRes_10.6.8_Pack.zip D620_GMA950_HiRes_10.7.5_Pack.zip D620 nVidia Quadro 110M (all res): D620_NV110m_10.6.8_Pack.zip D620_NV110m_10.7.5_Pack.zip D630 GMA X3100 LoRes (WXGA 1280x800): D630_X3100_LoRes_10.6.8.zip D630_X3100_LoRes_10.7.5_Pack.zip D630 GMA X3100 HiRes (WXGA+ 1440x900): D630_X3100_HiRes_10.6.8.zip D630_X3100_HiRes_10.7.5_Pack.zip D630 nVidia Quadro NVS 135M (all res): D630_NV135m_10.6.8_Pack.zip D630_NV135m_10.7.5_Pack.zip D630_NV135m_10.8.5_Pack.zip D630_NV135m_10.9.5.zip D630_NV135m_10.10.5_Pack.zip D630_NV135m_10.11_Pack.zip D630 nVidia Quadro NVS 135M (all res) + Penryn CPU: D630_NVS135m_10.12_and 10.13_Pack.zip NB: MyHack highly recommended for installation of Snow Leopard, Lion, Mountain Lion and Mavericks. Use myHack v3.3.1, except for SL which requires v3.1.2 (there's a bug related to SL in v3.3.1). For Yosemite and beyond, we recommend manual USB installer creation using instructions that have been detailed in numerous guides posted here. NB: For Chameleon-based Yosemite installations (i.e. no Clover or otherwise), not all kexts load from /E/E. Eg: VoodooHDA + HDADisabler or lspcidrv. In such cases, copy the kexts to /L/E, repair permissions and rebuild the cache with the following Terminal commands: sudo chmod -R 755 /Library/Extensions sudo chown -R 0:0 /Library/Extensions sudo touch /Library/Extensions sudo kextcache -Boot -U / Update to Chameleon r2468 is recommended for proper hardware support such as good CPU detection. Chameleon-2.3svn-r2468.pkg.zip NB: For Enoch-based Yos/EC/Sierra installations (recent Enoch versions such as r2795 and beyond for instance), you may use a kernel.plist file in /Extra with parameter KernelBooter_kexts set to Yes to load kexts from /E/E directly. Those kexts will not natively be considered for prelinked kernel/kext cache generation so boot time will be a little slower. To maximise boot time, you can either move kexts from /E/E to /L/E or copy them from /E/E to /L/E and set KernelBooter_kexts to No. You will then repair permissions and rebuild the cache as detailed above. Sierra can only be installed on D630 nVidia models fitted with a Penryn FSB800 C2D CPU (e.g.: T6xxx, T8xxx, T9xxx). Enoch-rev.2839.pkg.zip
  42. 1 point
    Dell DW1820A expected to work OOB under Yosemite and El Capitan, having been successfully configured under High Sierra & Mojave.
  43. 1 point
    Hi Jake, Got quite bit further on the t470s - System is now fully functional, battery status, wifi, trackpad. System works solid. Got some tips from the Max 1974 thread and a few other members of the community that you helped out - Only real issue I'm having would be battery life - battery drains really quickly from a full charge - approx 1 hour. Is there any tricks to get this better? I installed the intel power gadget and could not see any resources hog that would indicate as such. Hoping you could take a look at my debug files and offer any assistance (again) if you could. Many thanks in advance Dan debug_30561.zip
  44. 1 point
    If anyone is still having problems with this the brightness function on the arrow keys of my E6230 works fine by patching the BRT6 method in the DSDT. This looks like it should be applicable to most Latitude models as many use the same brightness control method. Open your DSDT source file in MaciASL, click Patch, paste the code below in the top section and click apply.
  45. 1 point
    Fitted the Mojave SSD of the E6220 in my D630 and added the necessary modifications for MBP7,1 model: patched PlatformSupport plist (already in place for MBP8,1 SMBIOS on E6220) posted above installation of nVidia kexts/pack from High Sierra 10.13.6 to /S/L/E 10.13.6_nVidia_kexts.zip replacement of Mojave's /S/L/UserEventsPlugins/com.apple.telemetry.plugin by High Sierra 10.13.6's version com.apple.telemetry.plugin.zip The results are similar to what's achieved on the E6220 with HD3000: full graphics acceleration with minor defects (more visible in light mode than dark one). Other than the above small graphics limitations, D630 appears fully functional (sleep/wake, LAN, wifi, WWAN, audio, dGPU throttling/AGPM, etc.)
  46. 1 point
    sorry, my mistake the 1 screw is for E6220. You'll have to remove all the screws on the bottom except the 2 besides the dock connector.
  47. 1 point
    Added AzureWave AW-CE123H combo Wifi ac/BT 4.0 1/2 mini-PCIe card.
  48. 1 point
    Hello all, This topic will cover how to enable the SD Card reader in the Latitude E6410. The information below try to describe my Latitude E6410 configuration: 2.4GHz Intel Core i5 4GB 1067 Ghz DDR3 NVS 3100M 512 MB (1440x900) BIOS version A13 This information worked for me in Mavericks and Mountain Lion. PLEASE, BACKUP YOUR MEMORY CARD BEFORE TRYING THIS PROCEDURE. I CAN'T GUARANTEE IF THE DATA WILL BE SAFE AFTER YOU TEST WITH THE INFORMATION DESCRIBED BELOW. First, you need to find out the "Vendor ID" and the "Device ID" of your SD card controller. I used the "System Info" tool from El Coniglio and Oldnapalm. Another way to get this info is using the "lspci" command in the terminal: (you need to have the "lspcidrv.kext" in S/L/E) localhost:/ piglesias$ lspci -nn | grep SD pcilib: 0000:01:00.0 64-bit device address ignored. pcilib: 0000:01:00.0 64-bit device address ignored. 04:00.0 SD Host controller [0805]: Ricoh Co Ltd MMC/SD Host Controller [1180:e822] (rev 03) In my case, the SD card reader has the Vendor ID = 1180 and the Device ID = e822, as you can see in red above. With this information in hands, you can edit the "Info.plist" file from VoodooSDHC.kext (version 1.1.2b1). VoodooSDHC.kext.zip - Edit the file "VoodooSDHC.kext/Contents/Info.plist": In order to edit the Info.plist file, you can use any text editor. In my case, I used "vim". Inside the "Info.plist" file, search for the string "IONameMatch". You will find something like this: <key>IONameMatch</key> <array> <string>pciVVVV,DDDD</string> </array> Replace the "VVVV" by the Vendor ID and the "DDDD" by the Device ID you got from your hardware. Copy the VoodooSDHC.kext to /System/Library/Extensions and then repair the permissions and rebuild the S/L/E cache with your preferred tool. I used Kext Wizard. Reboot the machine in order to load the VoodooSDHC.kext. After the reboot, insert the SD card and check inside the Finder. Let me know if it works for you. Troubleshooting: Check if the VoodooSDHC.kext loaded. Type in the command line: localhost:~ piglesias$ kextstat | grep VoodooSDHC 53 0 0xffffff7f80b1e000 0x4000 0x4000 org.voodoo.VoodooSDHC (1.1.2b1) <15 11 5 4 3 1> If not loaded, check the /var/log/system.log file and try to find the reasons why the "VoodooSDHC.kext" didn't load. Check the session "OSBundleLibraries" in the bottom of "VoodooSDHC.kext/Contents/Info.plist". There you will see the dependencies of the kext. Verify if you satisfy all the dependency versions with your installed kexts. Another way to check if your kexts are satisfying the "VoodooSDHC.kext" dependencies, you can try in the command line: localhost:~ piglesias$ kextlibs -undef-symbols /System/Library/Extensions/VoodooSDHC.kext For x86_64: com.apple.iokit.IOStorageFamily = 1.9 com.apple.kpi.iokit = 13.0 com.apple.kpi.libkern = 13.0 com.apple.kpi.mach = 13.0 2 symbols not found in any library kext: __ZN9IOService19_RESERVEDIOService0Ev __ZN9IOService19_RESERVEDIOService1Ev In my case, these last two symbols not found, don't disturb the kext to be loaded.
  49. -1 points
    what i meant to say, when I try move the cursor with the trackpad by swiping it with my finger tip it doesn't move.
  50. -1 points
This leaderboard is set to Amsterdam/GMT+01:00
×
×
  • Create New...