Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. Did you try gibMacOS? It has versions for both Windows and Mac. You just need the Windows version, of course. For editing the config.plist, you can use ProperTree. If you don't want to use gibMac to add Clover to the USB drive, you can use cvad's BDU instead. So, you can use gibMacOS to make the installer and BDU to add the bootloader. ProperTree if you need to edit the config.plist. Unfortunately I don't have much experience with laptops. And I don't have a Dell Latitude 3350. But the process should be pretty much the same. At least to get you booting. For Wifi, BT, trackpad, brightness control and other wonders, you might need extra kexts or SSDTs. But the idea is to get you booting first. To me, it's still easier to do it from MacOS itself (even if it's virtualised) than Windows. But that's probably just me. So, to make the USB drive, you don't actually need the latest and greatest MacOS. So...you can try to download an already made vmdk with let's say Sierra or something (again, it doesn't need to be the latest version). You can try this one just as an example. If that doesn't work, you can try to google virtual disk image macos. One of them should work. After that, you have a lot of options for creating and managing the USB installer. You can either download the installer App directly from the App Store, or use dosdude1's Catalina Patcher (you don't actually need the "patcher" part of it, just to download you the installer). After that you can use the Terminal to format the USB drive and put the installer onto it using Apple's own createinstallmedia method. I mean, the possibilities are endless. And for the Clover part of the USB drive, since you're on MacOS environment, you can use Clover Configurator to both download Clover and manage the config.plist file So, as you wish. You've got a lot of options.
  3. Just install Clover and copy the Clover folder over from the USB
  4. Installation performed correctly! Can you tell me a guide for booting directly from hard disk?
  5. Hi I want to ask if on this laptop I'm able to run airplay. Dell specs: CPU: Haswell Intel Core i7-4600u dual core 4th gen IGPU: Intel Graphics HD 4400 Ram: 16GB DDR3 SSD M-SATA: 256GB Bios: A28 Mac Os: Catalina 10.15.4 efi from here https://osxlatitude.com/applications/core/interface/file/attachment.php?id=26442 wifi card: BroadCom BCM4352 BCM94352HMB
  6. Here's my EFI. Its not fully optimised as mentioned it has some smaller issues to iron out, but that's for another thread I suppose. Lets see if this helps with native-like trackpad first, and maybe a separate thread just 7490 running OpenCore to fix the rest of the issues we may have. PS: Here a list of things that do not work yet, which I have tested: Touchpad Buttons (No hope) Micro SD Card Reader (Disabled on purpose as it kernel panics on Wake) Sleep (Device sleeps fine, but upon wake system freezes) SideCar (only works on wired mode) Fn Speciality Keys (not fully mapped for brightness yet. I believe one of the Kext is conflicting) Everything else works very well EFI OC059 10.15.5.zip
  7. Yesterday
  8. This display is 4k... my girlfriend has only this TV with HDMI (I use DisplayPort to HDMI cable). With your suggested adding the problem still remain. Edit: I deleted -v and reinserted -cdfon and seem installation starts
  9. what's the resolution of your display? try adding to boot arg -cdfon
  10. Connected via DisplayPort, now we are in the situation attached
  11. guys i'm really desperating ... i downloaded a vanilla catalina beta , when i try to extract the ".hfs" 7zip always shows up an error at the end, its the same error no matter what version of catalina (olarilla , niresh , vanilla) @arsradu I do not own a mac, so i can't use any of the methods of clover mac, and the virtuallbox bugs alot its impossible to use, i have to do it 100% on windows, and i downloaded a vanilla .dmg beta " v10.15.b6 (19A536g)" I didn't find any good tutorial about doing this for catalina in windows, the most of it if for high sierra and it didn't work as i mentionned before.
  12. I am trying to figure out how to change the Framebuffer Memory in order to try and fix the KP but i ccouldn't find out what values to use, I saw this on WEG Github : https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md but couldn't find how to reverse, the bits correctly ( no standard reversing onmine could do the trick ), and didn't find how to get the initial values that they are using in the examples. these are the recommended framebuffers for laptop from the WEG GH : 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 03060A00 00040000 87010000 are the initial values one fo the last 3 lines ? To be clear i am already using the 32Mb patch (the one set up by default in the rehabman repo of config.plists). I also didn't find how to change the DVMT value in bios and i don't have windows to really try the extraction method from here : would assuming the DVMT is set by default to 39Mb and changing to that in the clover framebuffer memory, damage my hardware or it would spit out an error ?
  13. If you mean flagged as in checked, that means it's been dropped...hence table droppings. You should try dropping these 3 patches: SSDT-4x0G4k, SSDT-FANREAD, and SSDT-IGPU. I would probably drop the 1st one 1st
  14. Into Option, at boot, there was only 1 OEM SSDT flagged. The patched ones were not flagged, so I supposed they were not in use. Disabling the OEM SSDT the system still freezes at the same time. Now I revert to 01.09.01, because it seems to be the only way to have macOS running on this machine
  15. For what i know, it's downloading the original image from Apple. So that's good. And it should also offer the possibility to add Clover or OC to it. Give it try.
  16. You are a really magician! Installation started! WOOOOOOOOW! Little problem: in the middle of loading bar the the installer disappear and the screen goes off... Here the video: https://mega.nz/file/iPQ3XCQA#_UsHTRsT0CUc04NmHZYSA53Wr-LAEchPgEU8dyekBy8
  17. Last week
  18. When I updated my ASUS to the latest 10.15.5 update, it broke the touchscreen and touchpad. I then updated VoodooI2C.kext and VoodooI2CHID.kext to version 2.4.3 and the touchscreen worked perfectly (click, select, gestures, everything!), but the touchpad still didn’t work. I then backed out VoodooI2C.kext to version 2.3 and kept version 2.4.3 of VoodooI2CHID.kext and now both the touchscreen and touchpad work perfectly. I finally have everything on the touchscreen working along with a working touchpad!
  19. Try booting without the SSDT* in the patched folder by going into Option at boot
  20. Give this a try, replace contents into /EFI/Clover overwrite if asked 3040_Catalina.zip
  21. Reply to @muttonhead411 Yes totally onboard with the idea to get a little community going. I came across a blog post which listed the 7490 as its top recommendation for hackintoshing. If people took that advice there must be many more of us. What sleep related issues have you being experiencing? I haven't had the occasion to verify what is/ isn't working yet beyond what's obvious so haven't picked up on any other issues yet (not tested ports, audio out etc). So on booting back into OpenCore this evening - after having used Clover for the last week - I was surprised to discover that my trackpad doesn't work at all anymore under OpenCore (despite making no changes). Even with XOSI & GPIO; XOSI config patch,; DSDT patches etc. So damn strange. Also tried your suggested .config patches but that didn't work either. Any idea of what could be going on? Could you share your OC folder with us? Or give a detailed guide of how you got the trackpad working and what kind of issues you experienced along the way?
  22. Reply to @Fuzeless: Nice work getting everything figured out under Clover If you’re still having trouble compiling your DSDT (and need it for some reason (Fn key remapping for example), the following may be of some assistance: I too, experienced some errors when compiling my DSDT in MacIASL (was following the OC wiki on Dortania.) By using an alternate fork of MacIASL, and disassembling the DSDT .aml file to a .dsl file, I managed to get it to compile without errors (key points below and detailed instructions at RehabMan’s laptop DSDT patching guide No I haven’t found that the right-hand section of my palm-rest heats up under MacOS. The machine seems to run cooler under OSX and is definitely much quieter than under Windows - the fan noise was insane with Win10. Key points for compiling DSDT file: Use clover boot loader to dump your DSDT (by pressing the F4 key at the boot screen). [I already dumped by DSDT under Win10 but figured this method might give a cleaner DSDT file]. Install RehabMan’s fork of MacIASL to Applications folder [this version seems to perform differently to the acidanthara release recommended by the Dortania OC wiki]. I can’t find a link to it but have attached the file to this post. Install iasl tools to /usr/bin Copy iasl tools to the MacIASL.app directory in Applications Disassemble your DSDT.aml file from clover. No need for -da option. No need for refs.txt Open the resulting .dsl file in MacIASL and try to compile. You should only get 3 errors. Replace the “If (LEqual (PM6H, One))” section with the amended one as explained in the guide Try to compile -> 1 error remaining -> Rename XTBT and add the XTB2 method before XTBT Now you can compile. Remember to save the error free dsdt as a .dsl file (patches can be applied to this). RehabMan-MaciASL-2018-0507.zip
  23. I've executed the procedure, unfortunately problem still remain.
  24. I've seen this when installing Calatina 10.15.4 with older version of Clover, but from your log file, it shows you're running latest v5118. Did you replace the entire clover from another source after install Clover? Go ahead and reinstall Clover on top, it won't overwrite the Config, ACPI or Kexts folders. It'll just update the drivers. Then try again.
  25. The original device name in original DSDT.aml is still EC0 (searching for PNP0C09), so no change occurred in Embedded Controller name with bios 01.11.01. Any other possibilities?
  1. Load more activity
  • Popular Contributors

  • Member Statistics

    • Total Members
    • Most Online

    Newest Member
  • Our picks

    • Released May 26th, 2020.
      Build 19F96.
      Seems safe to install on our Hacks. Ended up with a macOS could not be installed on your computer error message on the Latitude E6230 and 7490 laptops due to bless tool being unable to set the boot disk. But these are like false alarms because the Catalina partitions of those Hacks remained bootable and were properly updated to 10.15.5. The macOS Install Data folders in /System/Volumes/Data, however, had to be manually removed to get rid of the temp partition so, clearly indicative of a minor problem in fully completing the update at the end of the process.
      As for 10.15.4, refresh Lilu + WEG kexts and Clover to latest available versions (v1.4.4, v1.3.9 and r5118 at time of writing) before initiating the macOS update. If you cache your kexts from /L/E (or /S/L/E), remember to also update the kexts in the E/C/k/O of your EFI partition as the temporary update partition boots only with kexts injection.
      Security Update 2020-003 for High Sierra 10.13.6 and Mojave 10.14.6 released too (build 17G13033 and 18G5053).



      • 0 replies
    • A few of us with old C2D/C2Q platforms (mostly desktop) experienced CMOS reset since updating to 10.15.4.
      During troubleshooting, the issue was pinpointed to 10.15.4's new boot.efi file (located in /S/L/CoreServices) which, as many of us noticed, was displaying some new info when booting in verbose mode.
      Initially, replacing 10.15.4's boot.efi file with that of an earlier Catalina release or even an earlier macOS version was found to get rid of the problem without adverse affect on booting Catalina 10.15.4. However, this only worked for Hackintosh systems running Clover, not for systems running OpenCore.
      File ownership needs to be re-adjusted to root:wheel upon replacement:
      sudo chown 0:0 /S*/L*/CoreServices/boot.efi  
      Following further troubleshooting with vit9696, telepati and a few others, vit9696 worked out a temporary workaround for OpenCore in the form of a 5-bytes NVRAM variable wake-failure set to 00 00 00 00 00. All details and explanations are available here.
      For Clover users, this workaround alternative to replacing boot.efi can implemented as follows in Terminal:
      sudo nvram wake-failure=%00%00%00%00%00 Of course, this needs NVRAM to be working properly on the target Hack. For Hacks with no natively-supported NVRAM, it is required to install EMUVariableUEFI.efi Clover module + RC scripts on the Catalina boot volume. Once the variable is set and the system rebooted to take it into account, no more CMOS reset on rebooting from 10.15.4.
        • Thanks
        • Like
      • 1 reply
    • 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:
      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).
        • Like
      • 1 reply
    • A few things are required to successfully run macOS Catalina on a Hackintosh, whether through a new/fresh installation of a direct upgrade from a previous OS X/macOS version/release.
      1/ Laptops Embedded Controller:
      Since beta #5, macOS Catalina requires Embedded Controller (EC)-related patching for many laptops. It's therefore important to check your Embedded Controller device (aka "PNP0C09" id) in DSDT/ACPI and apply the mandatory device renaming to "EC" in Clover's config (or directly in DSDT), failing what, Catalina will never boot.
      Most Dell laptops since the era of the Latitude E4x00/E5x00/E6x00 range have an Embedded Controller device called "ECDV" in DSDT; in Clover, the necessary ACPI device renaming is as follows:
      Description: Changes ECDV to ECFind:  45434456Replace: 45435F5F Other known names for the Embedded Controller include "H_EC" or "EC0". If you find no Embedded Controller device in ACPI, this patch is not necessary.
      2/ Clover:
      Clover needs to be at a minimum version supporting Catalina. Versions r503x, r504x and r505x are generally Ok. At the date of general release of Catalina, we recommend using Clover r5093 as the minimum version. Clover versions are available off Dids' Github repo.
      3/ Add-on kexts:
      Lilu and associated plugins also need to be at versions updated for Catalina. At time of writing, we recommend the following minimum versions, all available off Acidanthera's Github repos:
      Lilu v1.3.8 Whatevergreen v1.3.3 AppleALC v1.4.2  
        • Thanks
        • Like
      • 0 replies
  • Create New...