Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. Hi everyone, I have an HP Probook 450 G5 (specs in signature) and I cannot boot into macOS when updating the bios from 01.09.01 to anything more recent (at the time of writing 01.11.01). I have a dual boot in a dual ssd configuration (NVMe: windows; SATA SSD: macOS, clover in SATA SSD). The only way to have macOS is to downgrade to 01.09.01. In this pic you can see the verbose during boot. I followed @Jake Lo guide of the 840 G3 to install Catalina but I just wanted to keep the whole system updated Is there any issue with VoodooPS2 kext? Should I use the ApplePS2 instead? Any hint will be appreciated Thanks!
  3. Hi, After having installed a few browsers in crostini i noticed that links now open in firefox - eg. when clicking on a link in Geary. To fix this, this is what you wanna do: Popup a crostini console and type: unset BROWSER xdg-settings set default-web-browser garcon_host_browser.desktop sudo xdg-settings set default-web-browser garcon_host_browser.desktop Credits:
  4. Today
  5. You can start with my Clover guide for Catalina here Use the attached files for bootpack, content goes into /EFI/Clover after you have install Clover If you want to dual boot, make sure to partition the drive after format, set the partition for Windows to MsDos Fat, MacOS to Journal Extended 3350_Catalina.zip
  6. Thanks for you answer; here is my specs : CPU Intel Core i5 5200U @ 2.20GHz 55 °C Broadwell-U 14nm Technology RAM 4,00 Go Single-Channel DDR3 (11-11-11-28) Motherboard Dell Inc. 09YKXP (SOCKET 0) Graphics Generic PnP Monitor ([email protected]) Intel HD Graphics 5500 (Dell) Storage 298GB TOSHIBA MK3255GSX (SATA ) 36 °C Optical Drives No optical disk drives detected Audio Realtek High Definition Audio BIOS Brand Dell Inc. Version A08 Date 29/08/2016 Keyboard standard PS/2 Vendor DLLK Location Mobile 5th Generation Intel Core Premium SKU LPC Controller - 9CC3 Dell Touchpad Device Kind Mouse Vendor DLL Location Mobile 5th Generation Intel Core Premium SKU LPC Controller - 9CC3 if it is compatible , where could i start ? i have absolutely 0 idea how the installation works, thank you very much for your help.
  7. Hey Extremeagile, Thank you for your detailed and thorough information! I forgot to tell you in my first post, that I was using OpenCore 0.5.8. Unfortunately, using Herve's bootpack or Swung0x48's (Link) would render my Trackpad to be undetectable under macOS (I hadn't examined the issue thoroughly though, as I was in a hurry then). I might try to create my own Clover Bootloader this weekend and see if it solves the problem. As for the OpenCore bootloader side, I have tried everything you listed above: from trying different version (all I2C release below v2.2 would not work with the Trackpad), to only use XOSI patch/hotpatch, etc... Weirdly enough, only the XOSI patch is necessary for the Trackpad to "work". If I remove XOSI patch and only use the GPIO pinning patch, the Trackpad wouldn't be detectable (unlike yours). Moreover, in IOReg, I don't see any children under VoodooI2CControllerDriver, unlike your IOReg on Clover (This could be the issue, like you said. Maybe VoodooI2C is not well-performed under OpenCore? Specifically OC 0.5.8?). Later today I'll open up an issue on the VoodooI2C Github. You might wanna check it out . Thanks a lot for your reply! (And sorry for any grammar mistakes/shortage, English is my second language.) Update: I have opened an issue on VoodooI2C Github, check it out if you can! Update 2: I am now able to boot up Herve's bootpack. The bundled VoodooI2C didn't work, so I updated to the latest release and it works, but it would occasionally cut off while dragging or using the cursor, which is more frustrating (the buggy and jumpy trackpad bug dissapeared though). Under IOReg I can't see my Trackpad and the GPIO pin listed like yours (which is weird, given that the trackpad worked, maybe under Polling mode?). I have attached my Clover EFI below. EFI.zip
  8. Post full system's spec. I think you could try using 3550's files found in our forum. Yes, you can do dual boot, best to install MacOS first and than Windows 10. Make sure to format disk to GUID / Extended Journal. Is it safe? You be the judge...
  9. hello , i'm amazed finding such a high quality forum dedicated for hackintosh and latitude, as a new user , i have a few questions that i hope you can help me out. i did use the search tool and difnt find anything about dell latitude 3350, isn't it compatible with mac os ? (although i think 3350 is a ripoff of 3340 with just the upgrade of the cpu) also, can i dual boot mac os and windows 10 ? and is it safe to use hackintosh ? ,thanks in advace !
  10. Yesterday
  11. Hey Fuzeless, Are you using OpenCore as I was, or Clover or some other bootloader? I've resorted to using clover for the timebeing as I'm exhausted with trying so many different options and getting nowhere. The trackpad works perfectly under clover using the bootpack I linked to previously. OpenCore is another story entirely. I have tried so many different configurations at this point, such as different versions of I2C and I2CHID; +- XOSI +- GPIO +- XOSI + GPIO + various hotpatches of GPIO and XOSI +- Mojave OS +- Catalina OS +- transplanting the SSDT-I2C.aml file from Hervé's bootpack. Since my first post I attempted GPIO pinning the trackpad. According to the guide it is already very-well-pinned but I made some edits to the DSDT file to remove extra entries in XCRS section so that "Return (ConcatenateResTemplate (SBFB, SBFG))" was the only return statement. Also tried patching the dsdt with the three recommended patches but the laggy trackpad behaviour was still the same. Weirdly, if I pull-up the trackpad in IORegExplorer, while booted with clover, it lists values under gpioIRQ and gpioPin (see screenshot). These properties are not defined under OpenCore, even with the custom DSDT for GPIO pinning + patches. This seems relevant. If you're still experiencing issues then maybe it is worthwhile testing Herve's bootpack to see if that resolves the problem?
  12. Hi! I have the same Latitude 7490 (i5-8350u variant) and experienced the same buggy, jumpy, delayed trackpad (I'm on 10.15.5 btw). Have you got any updates about your situation? Btw, how did you get the trackpad working without XOSI? I've pinned and patched my GPIO following the VoodooI2C documentation but can't use my trackpad without XOSI rename. Thanks a lot and have a great day/night!
  13. Thank you, Hervé. I think the problem is the way I have them configured... I mean, iGPU alone works fine. dGPU alone works fine (assuming I don't enable iGPU in BIOS, or if i'm using a "headless" connection in config). So I'd say they work ok separately. Just not in this configuration. Anyway, thank you very much for sharing your opinion.
  14. Well, it would seem that there is something missing or incorrect with regards to your Sapphire RX580 graphics card config then, not the HD4600 iGPU. I'm afraid I won't be of much help on that front since my hands-on experience with AMD cards is most limited. I only ever kept the old ATI Radeon HD X1300 of my old C2D Vostro 200 desktop Hackintosh for a short time back in 2012/2013 given that it was last supported in Snow Leopard. I then replaced the card by an nVidia model for subsequent OS X/macOS versions.
  15. Hey Hervé, So, after what you said yesterday about hanging at gIOScreenLockState, I thought I'd try a couple more things. And some of them are really interesting, and if you have the time, I'd really appreciate your opinion. So, first of all, the issue does not occur if I'm using only the iGPU (and being plugged into it, too). The issue seems to occur if I'm not actually plugged into the iGPU, but into the dGPU. And it could be why gIOScreenLockState is hanging. As you said, it's probably trying to figure out what to do. It does boot correctly after that, it's just that it also increases the boot time by a lot! Also, something else I found interesting. So, I don't add a specific value for VRAM in Device Properties. For as far as I understood, you only need ig-platform-id and (maybe) device-id. But only the first one will actually make a difference. So I thought: ok, let's try to boot into Windows and see how is my iGPU recognised. This is from Dxdiag as you can see. And this is from display properties. What I found interesting is the amount of memory. So...now I'm confused. Should it be..2048MB VRAM instead of 1536MB? Which value do I want from those? :)) For as far as I know, changing the amount of VRAM doesn't really make any difference. It's only cosmetic. But I'm just asking. Also, as I said, even without setting that, it still works fine, but only when I'm physically connected to the iGPU. Now, you would probably say: just use headless connector and only use the dGPU. Well, yeah, but that's the thing. For FV2 issue to be solved I need the iGPU with framebuffer. Otherwise it's like it's not even there. So, to resume: 1. with framebuffer and connected to the iGPU -> all good 2. with framebuffer and connected to the dGPU -> lag (no matter if it's set to Integrated Graphics first in BIOS, or dedicated graphics + "multi monitor"). As long as I'm not physically connected to it, lag. 3. without framebuffer and connected to the iGPU -> can't boot into the OS, computer restarts when attempting second stage boot. Makes sense. 4. without framebuffer and connected to the dGPU -> all good, but also can't have FV2 second stage boot correctly, since that seems to work only with FB. And I think the FCPX doesn't work either in this configuration. I might be wrong. So, looking forward to your opinion. Thank you very much!
  16. We recently posted an article about Realktek PCIe card readers (click on Home to get there) and there is also a dedicated thread about them in the Card Readers section. Please refer to that. Of course, without an SD card, you won't be able to do/test much thereafter... NB: quoting messages as a reply facility is not appropriate nor desired. Please use the Reply box available at the bottom of each thread. Thank you.
  17. Sir Please Can you guide me which MacOS X support as per my laptop hardware. I am asking you that because i not able to find it anywhere. I tried many time with different method like colver and opencore (error : OC:Watchdog status is 0) and i face error every time. So if you can guide me i am very thankful to you sir. Sir if you want any information regarding my laptop i can provide you.
  18. UPDATE: - Brightness is working for Fn+F11 and Fn+F12 after replace IGPU on your SSDT-BRT6.aml to GFX0. Any clue for disable brigthness on Fn+S/Fn+F6 (decrease) and Fn+B(increase) ? - Card reader is show on PCIe Hackintool, should I add to device properties?
  19. Hi Jake, Thanks for your attention and apreciated. test your SSDT but Brightness not working on mine. herewith the log : maybe must patch GFX0 to IGPU how to check SD Card? I don't have SD Card for testing.
  20. For Brightness: Add SSDT-BRT6.aml and replace your SSDT-OC-XOSI.aml with mine and add patch to ACPI Comment: BRT6,2 to BRTX,2, with SSDT-BRT6.aml Find = 14204252 543602 Replace = 14204252 545802 For SDCard reader, add Sinetek-rtsx.kext to Kernel E7270_Brightness&SDCard.zip
  21. in mine sleep not reallly working good, if too long sleep it goes black screen. not yet touching more for the sleep function coz usually I'm shuting down my Laptop if not use it. my graphic is working properly, I'm forget to get set normal after patch using hackintool (2048 MB) but is OK on mine. on Cinebench get 714 for CPU and 331 for single core. Is good result or not? My system using 1 TB NVMe Patriot P300, 16 GB PC2133 and 4 OS (Catalina, Mojave, WIn 10 and Ubuntu DDE). How to enable Fn+F11 and Fn+F12 ? until today can't get work for it. And what kext for enabling Realtek SD Card reader?
  22. @oegoeh Tested your OC files on my E7270 without touchscreen. I disabled all the I2C stuff pertaining to the touchscreen Issues: Sleep shuts down computer and encounter KP error message when started up again which means sleep isn't working. Is it working for you? Graphics has a hazy color //fixed it by removing AAPL,GfxYTile and AAPL00,override-no-connect patches from Device Properties I was able to enable Brightness control with Fn+F11 and Fn+F12 Also added kext to enable Realtek SD Card reader I have been able to put together some files and have sleep working on my E7270 and E7470 if it doesn't work for you either.
  23. Last week
  24. 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 folder 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).
  25. It is set up...I would say correctly, yes. Unless I'm missing something. The iGPU (+ the dGPU) are correctly recognised, with the right amount of VRAM in System Report -> Graphics. Not sure what else should I be looking for... I mean, you're the expert in iGPUs here. :))
  26. Oook... Kexts folder... As I told you, you have 2 Ethernet kexts. Please, remove IntelMausi.kext and IntelMausiEthernet.kext, download the one above, and place it in Clover/kexts/Other. Also, make up your mind. Are you using FakeSMC or VirtualSMC? :)) You should not be using both. So please, remove VirtualSMC from your kexts, for now. Let's use FakeSMC. You're using a bunch of kext (probably normal for a laptop). I can't help you with those, since I don't know exactly what they do, or if you really need them. Drivers folder... Again, make up your mind. You want FakeSMC or VirtualSMC? If you want FakeSMC, then please, remove VirtualSMC.efi from your drivers. Also, you're disabling VboxHfs in config, but you don't even have it in your drivers folder... So...what are you disabling? ACPI/patched folder... About sound...we can discuss that after we get your computer booting. Looks like you're using some custom SSDT but also AppleALC kext... Which I'm not sure are supposed work together. So...maybe try without the SSDT and let AppleALC do its job. You can just place that SSDT-ALC292.aml outside the /patched folder, if you don't want to delete it. Also, you've got a LOT of SSDTs... Do you need all of those? I see some of them which seem to be for renaming USB (from EHC1 to EH01 and EHC2 to EH02)? I could be wrong. But...if that's what they're for, that can be easily achieved from config (and it looks like you already set it there, too!)... I think one place is enough! No need to do it from SSDT and also, config. Also, you seem to be using a patched DSDT along with (probably also) patched SSDTs. Which is never a good idea. Either you put everything in one patched DSDT and basically make sure everything you need IS already included there. Ooor...you just add your custom SSDTs for the stuff you need and let the original DSDT do its job. In this particular case, I don't even know what to recommend you... See? This is exactly why you don't just download EFIs without understanding what's inside them. Personally I would move that DSDT out of the way, as well and test without it. Config.plist... About the iGPU, looks like you're adding device properties (including AAPL,ig-platform-id) from config. So...do you still need ig-platform-id in Graphics and Inject Intel ON? I'm not sure... I'd say probably not, but again, it could be a laptop thing. Also, in config -> System Parameters, if you don't load your kexts from S/L/E, you can set Inject Kexts to Yes instead of Detect. And, to be honest, I would recommend using all your custom kexts from EFI, rather than L/E or S/L/E. Why? Because you tend to forget about them, and then you'll have duplicated kexts and not knowing where do they come from. So...keep it all in EFI. It's a lot easier to manage, in my opinion. Once you're done making these changes, try again. About OC...I'm not using it on a laptop, but I think it does work. However, it's a lot different than Clover. And...I would suggest reading and understanding everything before diving nose first into it. Cause it might hurt. If, however, you wanna give it a try, a few things I wanna tell you: 1. know your hardware! This is incredibly important. Especially on a laptop! Laptops are notoriously harder to hackintosh, due to their different hardware and implementations. 2. make a backup of your current, working EFI folder! 3. when you're done with that, make ANOTHER backup to the first backup, and then one more, just for good measure. I'm not kidding. Well, ok, I'm half kidding. But believe me. You're gonna thank me later. Make sure you always have a working USB drive you can boot from. 4. take your time to read! This is not gonna be a walk in the park. You need time and patience. With that being said, here's an awesome guide to get you started. It's still a very technical text, but it's a lot easier to read and understand than other similar documents on OC. 5. OC doesn't have an installer. And I'm not sure if it will. Maybe some day. But until then, everything you do is directly operating inside that EFI folder. If you still wanna do it, I wish you good luck!
  27. Did you setup your config correctly for HD4600 iGPU? Because the hanging at gIOScreenLockState messages usually means that graphics are not initialising and system keeps retrying.
  1. Load more activity
  • Popular Contributors

  • Member Statistics

    • Total Members
      93439
    • Most Online
      7298

    Newest Member
    jsauce454
    Joined
  • 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.
      10.15.3_boot.efi.zip
      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:
      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).
        • 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...