Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 05/30/20 in all areas

  1. 2 points
    As @arsradu suggested, just update to latest Clover and update the kexts to the latest. If you have 3rd party kexts in /L/E make sure to update those as well, repair permission and rebuild cache. See if it still boots. If no issue, then continue upgrading. For sure you'll need a minimum of Clover v5107 to boot 10.15.4. I would recommend just upgrading to the latest v5118 at the time of writing this.
  2. 1 point
    Correct, with WEG and FB patch, they will bypass the error, but for that to work the FB kext must be cache for the FB patch to patch during boot. Usually with fakeID and / or -igfxvesa should be enough to get your installer to continue. You could try adding additional boot arg -disablegfxfirmware
  3. 1 point
    Still errorring out at graphics and seeing that -igfxvesa is not working, you could try going into Clover /Option/ graphics Injector and enable fakePCI / platform-ID = 0x12345678
  4. 1 point
    the boot arg from the screenshot is different from your Config file so not sure if you change it during boot or you're booting from another set of EFI files. From the KP, looks like it's related to graphics. Try boot with arg -igfxvesa As for your kexts, you can remove AppleBacklightFixup.kext (part of WEG now) Remove SMCHelper.efi from drivers/UEFI, you have VirtualSMC.kext. SMCHelper.efi is paired with FakeSMC.kext Once you're able to boot with -igfxvesa to complete the installation. rebuild cache. You should then be able to boot without that arg
  5. 1 point
    KP on KBL graphics framebuffer. Try -disablegfxfirmware boot arg during installation/upgrade.
  6. 1 point
    The techniques detailed there and in the linked guides applied to Intel framebuffers from Sandy Bridge to Broadwell. They ceased to apply to Intel framebuffers from Skylake onwards because Apple totally changed the way in which they define framebuffer layouts in the kexts. The connector types remain the same of course. If you want to change port types, you'll have to identify the connected ports in IOReg and patch them through Clover Device Properties injection for instance. By far, it's the easiest way to do it. You'll find examples in most packs available in the guides posted for Skylake/Kaby Lake/Kaby Lake Refresh/Coffee Lake Hackintoshes or those posts/threads were such patching was discussed. Here or here for instance. [email protected] translates to con0 [email protected] translates to con1 [email protected] translates to con2 etc. and the parameter you'll want to change for connector types will be type So, to change connector-type of [email protected]<x> to DVI, you'll inject: Key: framebuffer-con<x>-type Value: 04000000 Type: Data And activate framebuffer patching: Key: framebuffer-patch-enable Value: 01000000 (or just 1) Type: Data (or just Number)
  7. 1 point
    E7440 comes with an Alps touchpad, you'll need Dr. Hurt's version of VoodooPS2Controller. You can omit AppleBacklightFixup, it's been added to WEG for sometimes now. Omit BrcmFirmwareRepo, it's meant to be cache in /L/E, you already have BrcmFirmwareData.kext in clover kext. One or the other, not both. For audio, you can try the alc_fix linked in my E7440 guide here
  8. 1 point
    I'm sure you did, and I have a guess as to where you might have seen them. Having all the kexts in EFI/Clover/kexts/Other is easier to manage, and you can keep the system intact. Also, if I'm not mistaken, during the update, you rely entirely on the EFI partition. So...if you don't have your mandatory kexts there, you can't boot. Easy as that. Update: I don't know, man. I never had any issues having all the kexts in Clover/kexts/Other. Also, because of that, I have no such errors when I try to rebuild caches. And I don't wanna keep VirtualSMC/FakeSMC in EFI and everything else in other places. It's just not organised this way. And I tend to forget which kexts I have where. So I just have them all in one place. Easier this way.
  9. 1 point
    Basically, you're trying to cache VirtualSMC and it appears unsupported/incompatible with your Hack for whatever reasons (kext version, bootloader config, applied patches, etc.). I'd switch to FakeSMC instead (and ACPIBatteryManager of course). And you appear to have the same with WEG. You really need to update your add-on kexts to latest versions before you upgrade to Catalina! You're right to cache your kexts from /L/E.
  10. 1 point
    Source: http://matthewlewis.ca/disable-or-uninstall-synology-6-1-universal-search/ Synology DSM 6.1 has removed File Station from the core and swaps out the Search functionality from File Station into its own individual package. I’ve noticed some users (myself included) have been posting on forums and stated they no use for this package and did not want it installed, and it cannot be disabled or uninstalled via the Package Center. So here are some simple SSH commands (assuming you already have SSH is enabled in Control Panel / Terminal & SNMP) you can execute on your DiskStation to either disable or remove the package permanently. So login into your DiskStation with a ssh client such as PuTTy with your username and password followed by: sudo -i Enter in your account password, you should now be under the root account. To disable: synoservicecfg --disable pkgctl-SynoFinder To remove completely: synopkg uninstall SynoFinder And to logout of root account: logout You will have to logout and log back into the DSM to notice the package has been completely removed! How to stop and uninstall Universal Search? There's a lot of good, more advanced advice here, but the easiest way to do it for me was described on page 2 of this thread by quadcore: Control Panel =>Task Scheduler => Create => Triggered task => Under "General Tab" give the task a name of your choosing, and set "Event" to 'boot-up'. Under the "Task Settings" tab, in the "user-defined script" box, add: synoservice --disable pkgctl-SynoFinder synopkg uninstall SynoFinder (this is optional AK) Reboot, and observe in your Resource Monitor there isn't like 20 'synoelasticd' processes running. It works fine. I add the warning, you do this at your own risk.
  11. 1 point
    Forget about the laptop, have you seen the view? How can I get a house in the trees? I'd love that! I love nature. Anyway, yeah, congrats on the build. Looking good!
  12. 1 point
    Yeah, I remember reading about this system a year ago. Nice looking build though. Congratulations! Touchpad looks awesome. Does it come default like that?
  13. 1 point
    And don't forget the Embedded Controller patch as detailed in our promoted thread (see Our Picks column). Imperative for Catalina.
  14. 1 point
    Ok, let's confirm. You have these 3 kexts added to /L/E only and not in clover/kext/Other BrcmBluetoothInjector.kext BrcmFirmwareRepo.kext //make sure it's this and not BrcmFirmwareData.kext BrcmPatchRAM3.kext Run Hackintool again to rebuild the cache Reboot and check again. If it's still showing firmware 4096, then you have a caching issue.
  15. 1 point
    Where are you updating from? In theory, if everything is correctly configured, and if you're not upgrading from Yosemite to Catalina or some really old version of MacOS, then yeah...it should work pretty smoothly. What I would recommend is just making sure the following things are up to date: 1. Clover (here's the official place to download it from) 2. drivers and kexts (you can use Clover Configurator to update those) Also, before anything, copy your existing EFI folder to the EFI partition of a USB drive for safe keeping. This way, if anything happens with the Clover update, you still have a backup. When you're done updating Clover and kexts, before starting the upgrade to Catalina, try to see if you can still boot your current installation with updated files. If everything ok, download the update directly from your current version of MacOS, or make a bootable USB drive with Catalina on it and try to install it. In case the updated EFI folder is still ok, you can add that to your USB, as well.
  16. 1 point
    Not, they are the same. Remove BrcmFirmwareData.kext from /L/E You'll need to unlock Catalina's protection before running the repair permissions and rebuild cache, as you can see above, kexts were omitted. Read the FAQ to see how to unlock Catalina protection.
  17. 1 point
    so you now have BrcmBluetoothInjector.kext, BrcmFirmwareData.kext, BrcmPatchRAM3.kext in /Library/Extensions? Make sure it's BrcmFirmwareData.kext, and not BrcmFirmwareRepo.kext that goes into /L/E. Repair permission and rebuild cache went smoothly? Does firmware show a different # other than 4096?
  18. 1 point
    NB: No need to quote on your replies, just go to reply when you respond. Ok, now regarding BT. Go to system information, check Bluetooth. Look at the Firmware version. If it's 4096, then that mean the firmware kext is not loaded. If this is the case, then remove BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext, and BrcmPatchRAM3.kext from clover kext Add BrcmBluetoothInjector.kext, BrcmFirmwareData.kext, BrcmPatchRAM3.kext to /L/E instead. Repair permissions and rebuild cache. Check the firmware again Test BT again if firmware is anything but 4096.
  19. 1 point
    For wifi, add these kexts to clover kext Lilu.kext AirportBrcmFixup.kext For BT, add these kexts to clover kext BrcmBluetoothInjector.kext BrcmFirmwareRepo.kext BrcmPatchRAM3.kext
  20. 1 point
    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!
  21. 1 point
    While the EM7430 works with my kext. (I guess the product ID needs to be adjusted still). The EM7455 seems not. What I did: Wrote the kext for DW5811e / EM7411 according to the correct PID & VID attached above. Which after it appears on WANN section (location id show xxxxxxxx / 0 as others also have in their screen). Then with the correct APN the error shows: So I updated the firmware and all config settings using LIVE UBUNTU CD 18.04 with: https://github.com/danielewood/sierra-wireless-modems His autoscript is perfect for updating FW, configuring the whole card according to our needs & sets the PID/VID to generic to bypass any vendor locks. Whilst I updated the kext to reflect all MC/EM7455 cards PID/VID (Lenovo / DELL / Generic). Still the error "Network Connection ... " shows. Please also see the location difference: NOTE the firmware: SWI9X30C_02.08.02.00 r5428 CARMD-EV-FRMWR2 2016/01/06 20:38:53 While at!priid? shows the updated firmware: SWI9X30C_02.33.03.00_00_00_GENRIC So I manually check the connection using COM port: screen /dev/tty.wwan 115200 screen /dev/tty.wwan 115200 Which after I'm able to manually connect using at commands. Any ideas where to look? Perhaps it is the interface mapping? <key>InterfaceMapping</key> <dict> <key>0</key> <dict> <key>name</key> <string>wwanDM</string> </dict> <key>2</key> <dict> <key>name</key> <string>wwanGPS</string> </dict> <key>3</key> <dict> <key>name</key> <string>wwan</string> </dict> </dict>
  22. 1 point
    Hello! Installed Catalina 10.15.4 on my Latitude 5400 i7-8665U with UHD 620 Graphics after installation trackpad and right/left click are working fine. Installed clover and copied EFI then reboot, after reboot trackpad is not working. and I've also got a DW1560 wifi adapter, WiFi is working but I can't make the BT working. copied below kexts to /L/E using hackintool BrcmBluetoothInjector.kext BrcmFirmwareRepo.kext BrcmPatchRAM3.kext Please help. EFI folder attached. EFI.zip
  23. 1 point
    Generate P States and Generate C States are settings applicable to old C2D/C2Q/1st gen Core platforms only. They do not apply to Sandy Bridge platforms and beyond, including Broadwell platforms such as yours. In fact, if you call on these, you may find your CPU switching only between that low frequency you reported and the highest nominal frequency; all without Turbo boost and intermediate frequencies, which means CPU inefficiency and hammered performance. In order to enjoy proper CPU power management on your Broadwell Latitude laptops: either you apply/select/set/tick PluginType option in Clover ACPI section to which you may add Plugin Type=1. or you drop SSDT tables with ids CpuPm + Cpu0Ist in Clover ACPI section and generate your CPU-specific power management SSDT with Pike R Alpha's good old SSDT generator script; you'll then place the generated SSDT table in E/C/ACPI/patched folder. E7250/E7450 are fitted with low-power CPUs such as i5-5300U/i7-5600U and you should expect idle frequencies of 800MHz. If Intel datasheets do indeed indicate LFM frequencies as low as 500 or 600MHz, I'm pretty sure these are reserved for the programmable TDP-down/7.5W reduced power mode. In fact, if you download and install Pike R Alpha's complete tool and consult the data files for the Broadwell CPUs, you'll see this: # Broadwell mobile processor data. # gMobileBroadwellCPUList=( # # 5th generation Intel® Core™ i7 Processors (socket FCBGA1164) # i7-5950HQ,47,500,2900,3800,4,8 i7-5850HQ,47,500,2700,3600,4,8 i7-5750HQ,47,500,2500,3400,4,8 i7-5700HQ,47,500,2700,3500,4,8 # # 5th generation Intel® Core™ i7 Processors (socket FCBGA1168) # i7-5650U,15,800,2200,3100,2,4 i7-5600U,15,800,2600,3200,2,4 i7-5557U,28,800,3100,3400,2,4 i7-5550U,15,800,2000,3000,2,4 i7-5500U,15,800,2400,3000,2,4 # # 5th generation Intel® Core™ i5 Processors (socket FCBGA1168) # i5-5350U,15,800,1800,2900,4,4 i5-5300U,15,800,2300,2900,2,4 i5-5287U,28,800,2900,2900,2,4 i5-5257U,28,800,2700,3100,2,4 i5-5250U,15,800,1600,2700,2,4 i5-5200U,15,800,2200,2700,2,4 # # 5th generation Intel® Core™ i5 Processors (socket FCBGA1364) # i5-5350H,47,800,3100,3500,2,4 # # 5th generation Intel® Core™ i3 Processors (socket FCBGA1168) # i3-5157U,28,500,2500,2500,2,4 i3-5020U,15,500,2200,2200,2,4 i3-5015U,15,500,2100,2100,2,4 i3-5010U,15,500,2100,2100,2,4 i3-5005U,15,500,2000,2000,2,4 which lists CPU model, TDP, LFM, HFM, max Turbo, cores and threads. LFM frequencies of those CPUs fitted to our Latitude E7250/E7450 are therefore set at 800MHz, even though you may not encounter them much due to sustained minimum load under macOS. In the same respect, HD5500 iGPU of those processors typically clocks between 300 and 900/950Mhz. With regards to iGPU throttling, bear in mind that your Hackintoshes are not fitted with the same CPUs and iGPUs as those real Macs we fake them to be. For instance former are fitted with HD5500 GT2 iGPUs when latter are fitted with HD6000/Iris 6100 GT3 iGPUs. Not entirely the same thing...
This leaderboard is set to Amsterdam/GMT+02:00
×
×
  • Create New...