Jump to content


Popular Content

Showing content with the highest reputation since 02/21/19 in all areas

  1. 3 points
    Hi all, I am very excited to finally hack this world famous GPU mining motherboard and pleased to share with you all the clover bootpack. Specifications Asrock H81 BTC Pro Ver 2.0 4th Gen 3.5 GHz i3-4330 8 GB DDR3 1600 MHz Memory Intel Graphics HD 4600 HDMI output on 24-inch LED Monitor (1920 x 1080) Clover Bootpacks Catalina Support for Mac OS Catalina 10.15.1 (Clover 5070) CLOVER-10.15.1.zip Support for Mac OS Catalina 10.15 (Clover 5070) CLOVER-10.15.zip Support for Mac OS Catalina 10.15 Beta (19A471t) (Clover 4945) CLOVER-10.15 Beta (19A471t).zip Mojave Support for Mac OS Majave 10.14.6 (Clover 4945) CLOVER-10.14.6.zip Support for Mac OS Majave 10.14.5 (Clover 4934): CLOVER-10.14.5.zip Support for Mac OS Majave 10.14.4 (Clover 4910): CLOVER 10.14.4.zip Support for Mac OS Mojave 10.14 Beta 4 18A326h (Clover 4586): CLOVER 10.14 Beta 4.zip Support for Mac OS Mojave 10.14 Beta 18A293U (Clover 4517): CLOVER 10.14 Beta.zip High Sierra Support for Mac OS High Sierra 10.13.6 (Clover 4635) CLOVER 10.13.6.zip Support for Mac OS High Sierra 10.13.4 (Clover 4428) CLOVER-V4.zip Support for Mac OS High Sierra 10.13.2 (Clover 4360) CLOVER-V3.zip Support for Mac OS High Sierra 10.13.1 (Clover v4293) CLOVER-V2.zip Support for Mac OS High Sierra 10.13.1 (Clover v4293) with Intel Graphics: CLOVER-Intel.zip Support for Mac OS High Sierra 10.13.1 (Clover v4293) with ATI Graphics: CLOVER-ATI.zip Credits goes to Jake Lo and Bronx Teck Notes on Mac OS Catalina 10.15.1 (1) Everything works (2) Updated Whatevergreen.kext to latest version Notes on Mac OS Catalina 10.15 (1) Everything works (2) Updated clover, efi drivers & kexts to latest version (3) Swapped from FakeSMC to VirtualSMC Notes on Mac OS Catalina 10.15 Beta (19A471t) (1) Everything works (2) Whatevergreen.kext requires graphics injection from Clover Notes on Mac OS Mojave 10.14.5 (1) Everything works (2) Mac OS 10.14.5 Update Installer now complaints "Cannot Find Installer Resources". A very crude workaround is to remove all other hard drives except for the Mac OS hard drive. Let me know if anyone find a solution to this without having to open the casing each time we want to update. Notes on Mac OS Mojave 10.14.4 (1) Everything works (2) Whatevergreen.kext now autodetects the graphics card. Make sure no graphics injection is done in Clover. Notes on Mac OS Mojave 10.14 Beta 4 18A326h (1) Everything works (2) Updated from Mac OS Majave 10.14 Beta 18A293U via Software Update in the System Preference. Notes on Mac OS Mojave 10.14 Beta 18A293U (1) Everything works including sleep. (2) Dedicated GPU Radeon Pro 560 not displaying on monitor. May need to wait for WhateverGreen.kext to be updated with support for this Mac OS version. Notes on Mac OS High Sierra 10.13.1 (1) Everything works including sleep. (2) Updated all kexts to latest versions (3) Added IntelGraphicsFixup.kext and Shiki.kext (4) Combined all ATI & Intel GPU configs & kexts into single bootpack for multi GPU support (5) For those that need to update 10.13 to 10.13.1, you will need to install the latest clover (version 4293 is the one I used). If there are error messages, you may try to remove EmuVariableUefi-64.efi from Clover EFI temporarily, clear NVRAM using sudo nvram -c in terminal, download the update directly from apple website and install. Notes on Mac OS High Sierra 10.13.2 (1) Everything works including sleep. (2) Updated all kexts to latest versions (3) For those updating from 10.13.1 to 10.13.2, you will need to install the latest clover and lilu including plugins (or download latest bootpack above) as well as download and install the update directly from apple website. Updating via App Store doesnt seem to work for me as I get the mkpg not found error message after reboot. Notes on Mac OS High Sierra 10.13.4 (1) Everything works including sleep. (2) Updated all kexts to latest versions (3) For those updating from an earlier version of 10.13 to 10.13.2, you will need to install the latest clover and lilu including plugins (or download latest bootpack above) as well as download and install the update directly from apple website. The OS X installer will reboot several times. Notes on Mac OS High Sierra 10.13.6 (1) Everything works including sleep. General Notes (1) The UEFI Bios does not detect Clover EFI natively. For first boot into Mac OS, you will need to boot Clover EFI using the Installer USB. In order to add Clover EFI into UEFI Bios, you will need to manually add it using the Clover UEFI shell using the following command:- (a) bcfg boot add 3 fsX:\EFI\CLOVER\CLOVERX64.EFI "Clover" (You will need to replace X with the location of your Clover EFI partition. This is shown in the list when you first enter the UEFI shell) (b ) Lastly, do bcfg boot mv 3 0 to move the Clover boot order to the first. (2) I found that this motherboard is very compatible with Mac OS and patched DSDT / SSDT is not required. Notes on Mining (1) As all you miners know, this motherboard can take up to six (6) GPUs, I have yet to test additional GPU on the PCIEx1 slots. At the moment, the single GPU that i'm using is installed on the PCIEx16 slot. I will test it once I have opportunity to get additional GPU. In the mean time, for those miners who already have this motherboard in their rig and are already using Windows or Linux, Mac OS may be a good OS to try since some miners (like ethereum's ethminer) are also released for Darwin and both NVIDIA and ATI have provided drivers for their latest GPUs. This does open up a good possibily of using Mac OS for GPU mining! (2) I was able to use the dedicated RX560 GPU for both as primary display as well as for mining. However, it causes the system to slow down and created artifacts when I rebooted / shutdown. I was able to make the system more stable by using the integrated HD4600 GPU as primary display and the dedicated RX560 GPU for mining. In order to use both integrated GPU and dedicated GPU, both Intel and ATI need to be injected by Clover. In the case of ethereum miner, ethminer was able to recognized all GPU but I only selected the RX560 for mining. This made the system more stable. (3) [10-11-2017] I just installed a third old AMD Radeon HD 7750 GPU on the first PCIEx1 slot and am very happy to see that Mac OS recognized it straight away. In the case of ethereum miner, ethminer was able to recognized all GPU. Attached pictures below:- (4) One of my main concern is I am still not able to get HWMonitor to show GPU temperature which is very important to monitor the current health of the GPUs. We would not want the GPU to overheat due to unforeseen reasons. Let me know if you are able to solve this issue. (5) During my discussion with crew member Rhyker, we were discussing on ways to tune the GPU from within Mac OS. As you know, currently the manufacturer only provide tuning software for Windows and to a limited extend Linux. We were thinking of running Windows under a virtual machine to access the GPU tuner to tune the GPUs. However, based on my last attempt, accessing native GPU from a virtual machine is still not possible although there are projects that are attempting to do this. Let me know if this idea is workable. Let me know if the clover bootpack works for you. CLOVER-10.15.zip
  2. 2 points
    Here is a full CLOVER folder for Catalina for the E5470/E5570 CLOVER.zip
  3. 2 points
    @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
  4. 2 points
    @MrJonesIII Download AppleALC.kext + Lilu.kext and place into /EFI/Clover/kexts/Other In Config file, change Devices/Audio, change Inject from 1 to 5, under ACPI, enable FixMutex
  5. 2 points
    The release version also has layout-id 21, so should work too. https://github.com/acidanthera/AppleALC/releases
  6. 1 point
    Try add to boot arg bpr_probedelay=200 bpr_initialdelay=400 bpr_postresetdelay=400 More info here Others seems to have more luck with older version. Issue has been around for a while now.
  7. 1 point
    Don't need the patch, it's already named "EC" Just update the kexts primarily Lilu.kext and Whatevergreen.kext and AppleALC.kext
  8. 1 point
    your synaptics touchpad should work with the included kext. maybe try copying it to /L/E and cache it VoodooPS2Controller.kext
  9. 1 point
    @mefflecakes It's basically the same as a 7040. There's a bootpack I created flowing around in the forum. Just follow the basic Catalina/Mojave installation.
  10. 1 point
    you have to edit the info.plist inside the trackpad kexts manually.
  11. 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 his thread on the E470 and how detailed he got, including Bios settings to use.
  12. 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.
  13. 1 point
    Yes, should work for HS as well.
  14. 1 point
    Fn+B will work. For F11 and F12 to work, you need to install VoodooPS2Controller.kext but it's not very functional for this model
  15. 1 point
    If you cannot disable the nVidia card and/or can only run on it, you'll be limited to High Sierra since that's the last version with Web Drivers available. GTX 1070 is Pascal and that's only supported with Web Driver; no such driver since Mojave and there won't be (you can Google for the whole story between nVidia and Apple). You'd only be able to run Mojave or Catalina on the Intel iGPU and have the nVidia chip disabled through DSDT/SSDT patching in order to save battery life. Then Catalina needs renaming of the Embedded Controller ACPI device and you're not doing that. See our thread entitled Minimum requirements for Catalina. It's pinned to the Our Picks column on the forum main page.
  16. 1 point
    Dear Marco, I managed to install Catalina and it works without problems, I attach screenshots for review or analysis. Now I must test the operation in production mode, I'll tell you what's new. regards, TeroRERO
  17. 1 point
    Hello awesome people, I have taken a lot from this community, this is the time to give something back. As we all know that BTFirmwareUploader.kext stopped working for some reasons after spending countless hours on this issue I finally came to a workaround. Not that this workaround is temporary, our awesome developer of the kext will find a fix for this for sure. UPDATE (2017-11-22) (Recommended) :- Hey guys, as you all might have noticed, all the workarounds mentioned below are not working properly since the macOS 10.13.1 incremental update. So, this got me investigating this issue further and I'm happy to say that I have finally come out with a proper fix. This process is a bit complicated but read on, once you set things up, working Bluetooth is just 3-4 clicks away. While I was busy investigating this issue, I came to the conclusion that Apple has changed a lot of stuffs in IOUSBHostDevice in macOS High Sierra. The developer of the BTFirmwareUploader is working on it (results are delayed due to his personal life problems). Let's first understand how Bluetooth firmware uploader works in *NIX based systems. A few bluetooth devices have the firmware required for bluetooth embedded in them and hence they are not problematic, but a lot of devices rely on firmware uploader to function properly. You can have a look at ath3k.c file in Linux kernel tree to get the idea of how the firmware is uploaded to the device. Cutting the nerd stuff out, here is the process in short, the system powers up the bluetooth device, the firmware uploader detects that the device is powered on and then it sends(uploads) the firmware in buffers. If you look in Apple Menu > About this Mac > System Information > Bluetooth you can see our device is recognized properly (look at vendor and product ids) but is not pairing to any other peripheral because of the missing firmware. So, in order to fix bluetooth,we have to upload the firmware to the bluetooth device, there is more than one way to do it. The simplest would be using a FirmwareUploader kernel extension (which doesn't seem to be working in our case) The second option is, Booting into Linux/Windows and then cold warm booting (cold warm booting means booting macOS without powering down the machine, like on linux, power menu > restart) to macOS. What this does is, when we boot Linux/Windows the appropriate firmware is uploaded to the device and due to the way BT devices work, they don't lose the firmware until the device is not powered off. So, this would get the BT device working in macOS as the only thing missing was proper Firmware and now we have it loaded in our bluetooth device by booting other OS. This would work fine on macOS 10.13, but sadly, in macOS 10.13.1 when we boot the operating system (hot boot/cold boot) it resets the Bluetooth device. Hence, we lose our uploaded firmware. The method we are going to use is based on the above method except we won't be losing our firmware until we restart or put our machine to sleep. This is how it works, we boot linux (you may try with windows) in a virtual machine and share our bluetooth device (exclusively to guest OS, i.e. Disconnecting the device from macOS and connecting it only to Virtual Machine). What this will do is, as soon as we connect our device to Linux VM the Linux kernel will upload the required firmware in our BT device. Then, we will disconnect the device from VM and connect it to macOS (Hot plugging works fine, thanks to USB). Technically, we uploaded the firmware, switched the connection from VM to Host OS(macOS) without powering off the device. So, we still have the firmware, this is what we wanted, right? Okay, enough talking, let's do it. Prerequisites :- Linux bootable ISO (You can download one here) A VM software (I used VMware Fusion, you may try with VirtualBox). On a second note, VirtualBox should not be the preferred VM Software on a hack as it tends to cause issues with proper functioning of USB controller in macOS) Patience and little bit of your gray matter. Remove any existing Firmware Uploader and then reboot by rebuilding caches. How to do it :- I am going to explain the entire process by assuming that you are using VMware Fusion. First up, open VMware Fusion and press Cmd + N or File > New to create a new virtual machine. Select Custom Virtual machine. In the next screen select Linux > Ubuntu 64-Bit Click on Next and then Finish the setup by saving the virtual machine to your desired location. You will see that upon finishing the process VMware will boot the virtual machine, but we don't want to boot it just yet (have to change a few configuration settings). So, select Virtual Machine > Shut Down from the Menu Bar (Confirm the prompt that you want to shut down) Now let's get to changing settings. Click the settings gear icon in your virtual machine window, it looks like, Upon clicking it you will get a new window. Select the CD/DVD (SATA) pref in it. Now, check the box saying "Connect CD/DVD Drive" Now, if you look below you will see an option like, Click on the popup menu and select "Choose a disc or disc image" and then select your Linux bootable ISO file. So, upon changing the above settings that section should look like, Now click on "Show All" at the top to go back to the main pref pane. Now we need to change settings of Bluetooth devices. Select "USB & Bluetooth" pref in the main window. Upon clicking it you will see a screen like this, Now that you have unchecked the "Share BT Devices with Linux" you will see a new device popup in the above list, like, Now, click on "Show All" on the top again to go back to the main pref pane. Now we just need to change boot order to boot our live ISO image. Click on "Startup Disk" and then in the next pref pane, select CD/DVD and click Restart, like, Upon clicking restart, you will see that the VM boots up and you get GRUB menu like, Select "Try without installing". Yes, we don't even have to install the OS for real. We are pretty much done here, just a few last steps. Once the virtual machine boots up you have to click on Settings Gear at the top of your VM window once again. Now select "USB & Bluetooth" option. In that, check the box in front of your BT Module's name You will see that BT icon in the macOS's Menu Bar turns to device not available and a new BT icon appears in your Linux VM's Menu Bar. Once you do that, wait for 4-5 seconds, Then uncheck the box in front of your BT controller. You will see that device disappears from Linux Menu Bar and reappears in macOS menu bar. That's it, mission accomplished. We still have firmware in the device. As a result, Bluetooth will work perfectly. You can now close the VM. VMware will save the machine state for you. You can use bluetooth as long as you don't put your machine to sleep or restart. If you lose bluetooth functionality after sleep/restart worry not, like I said, once you set things up, the fix is a few clicks away. How to resume BT after sleep/restart :- Open VMware and resume your Linux VM Click on Settings gear in VM window Select "USB & Bluetooth" Connect device and then disconnect after 4-5 seconds (i.e. Tick the box in front of your BT module's name and untick it) Close the VM (Save VM state as it will result in much quicker fix) Voila! You have BT working! Note: If you lose your Bluetooth Device after sleep (i.e. No Bluetooth section in macOS SYSTEM PREFERENCES or under SYSTEM INFORMATION > BLUETOOTH) it is due to wrong USB configuration. Report with proper problem reporting files. See How to generate proper problem reporting files Make sure you don't have any Firmware Uploader kext installed as that might interfere with this workaround. This workaround wil only work if your BT device is showing up in SYSTEM INFORMATION > BLUETOOTH This workaround will also work for devices not supported by BTFirmwareUploader.kext Hope that helps! UPDATE (2017-10-29) (Deprecated) :- While some debugging sessions with the developer of the kext I found out a better method to have BTFirmwareUploader up and running smoothly as long as you don't cold boot macOS (shut down and then power on) Note: It too will only work if the kext worked for you before upgrading to High Sierra. Steps to follow:- Install the kext to /S/L/E and reboot. (DO NOT SHUTDOWN, RESTART) Upon booting back up, open terminal and type the following:- sudo rm -rf /S*/L*/E*/BTFirmware* Now reboot (DO NOT SHUTDOWN AND BOOT BACK UP), Click Apple Menu and Restart.That's it, now as long as you don't cold boot (power off and boot macOS) bluetooth will work for you. Once you cold boot, repeat these steps again. I'm sure the developer will soon come out with a FIX for this. OLD METHODS (NOT RECOMMENDED, TRY IF THE ABOVE DOESN'T WORK FOR YOU) :- Note: This method will only work for those who can turn toggle bluetooth using the Fn keys on their laptop. There is also a way for those who can't toggle bluetooth from the keyboard. That will be covered later in this guide. My Hardware:- QCA AR9565 Wi-Fi (0x168c, 0x0036) QC Atheros 4.0 Bluetooth (0x13d3, 0x3423) The BluetoothFirmwareUploader.kext attached to this post has been modified to work ONLY with this hardware. If you had working bluetooth before macOS HighSierra you need that BluetoothFirmwareUploader.kext, If you don't have the above mentioned hardware please DO NOT download the attached KEXT. METHOD 1 (FOR THOSE WHO CAN TOGGLE BLUETOOTH) Download the attached script. Open terminal and type:- open $(echo $HOME) Copy your previously working BluetoothFirmwareUploader.kext in the newly opened Finder window. Place the downloaded script on desktop and then go back to terminal and type, cd ~/Desktop chmod a+x ./fix_blue* Run the script as root user. Go to the terminal and type sudo ~/Desktop/fix_blue* Follow the onscreen instructions and you will be done. METHOD 2 (For those who can't toggle bluetooth) Note: You need to have working sleep. This is mandatory. Copy you previously working BluetoothFirmwareUploader.kext on the DESKTOP. Open terminal and type the following:- cd ~/Desktop sudo chmod -R 755 BluetoothFirmwareUploader.kext sudo chown -R root:wheel BluetoothFirmwareUploader.kext sudo kextload BluetoothFirmwareUploader.kext Once done, put you laptop to sleep. Once it's sleeping, wake it up. Open terminal and type:- sudo kextunload -p ~/Desktop/BluetoothFirmwareUploader.kext Once done, put your laptop to sleep again. Once sleeping wake it up. That'd be all. After waking up you can go to System Prefs > Bluetooth and connect to your devices. General Notes:- You can use bluetooth even after you reboot. Once you shut down and then open macOS again, you need to follow the above METHOD 1 or METHOD 2 again. Developers, @Hervé, @Bronxteck, @EMlyDinEsH please look into a permanent fix for this issue. I'm all ready for testing and stuffs. If someone comes with some problems regarding to the above mentioned steps please post your queries here. I'll try my best to help you out. BTFirmwareUploader.kext.zip fix_bluetooth_13d3_3423.sh.zip
  18. 1 point
    Use Hackintool.app to recreate a new USBPort.kext
  19. 1 point
    Yup, I guess you did not set DualLink to 1 as advised above, did you?
  20. 1 point
    It's a total mess. In your EFI, should only be Boot, Clover, and Apple folder. Remove everything else. Now replace the contents below into /EFI/Clover. This replaces your Config file and ACPI folder. Your kexts/Other folder look good, just need to upgrade the following kexts: Lilu.kext, Whatevergreen.kext and AppleALC.kext https://github.com/vit9696/Lilu/releases https://github.com/vit9696/Lilu/blob/master/KnownPlugins.md Important: Make sure you have a bootable USB handy in case something not working right, you can use it boot your system to fix the issue. E5540.zip
  21. 1 point
    What version of Clover do you try to install and how & where? What options did you select? Please specify details. Jake listed the necessary steps in his generic guide available here. Did you follow it?
  22. 1 point
  23. 1 point
    NO longer need to modify DVMT but you do need to set BIOS according to the guide. UEFI/AHCI/Secure boot off (most important) The patch if for NVMe drives mentioned, you SSD is not an NVMe, so you could ignore it.
  24. 1 point
    Ok, I downloaded the latest driver for DW1820A I could find on Dell's web site here (Win7 64bit for XPS 9350, dated May 2019). I extracted the firmware 1707 for our 0A5C:6412 DW1820A device: BCM4350C5_003.006.007.0095.1707_v5803.hex.zip All you need to do then is: copy the uncompressed .hex firmware file to the Resources folder of BrcmFirmwareRepo kext to supersede current version 1703 (=v7 c5799) update the key for device 0a5c_6412 in Info.plist file of BrcmPatchRAM2 kext After repairing permissions and rebuilding the cache, I can now connect to my JBL USB speaker without issues: This firmware version 1707 (which equates to v7 c5803) seems to be quite old (dated December 2015) but works Ok nevertheless. I'll try and lookup for a more recent firmware than that one. Edit: reverted to uncompressed .hex firmware file.
  25. 1 point
  26. 1 point
    I put a photo in the hidden area of my reply here. I attached 2 photos below too. I can't explain the reason though, I just followed some threads elsewhere when I was configuring.
  27. 1 point
  28. 1 point
    It's a Fermi card (GF104). https://www.techpowerup.com/gpu-specs/geforce-gtx-460.c265 I've no personal experience with that model but, afaik, like many other Fermi cards (eg: GT610, GF108), it does not work beyond El Capitan.
  29. 1 point
    No, no, no; look this up in IORegistryExplorer.
  30. 1 point
    Moved from Guides section to Support! Please ensure you use the correct section for all future posting. K3100M is Kepler and is therefore expected to work OOB. K2200M is Maxwell and requires the nVidia Web Driver. It's therefore only supported up to High Sierra. You also have to take the potential issue of Optimus into account (unsupported on Hackintoshes).
  31. 1 point
    @Tritius My USBs started working with the updates Jake Lo gave me. I have attached a copy of my EFI of my laptop from the EFI itself of the laptop, maybe it will help. If it works out, I highly recommend throwing a donation towards Jake Lo for finalizing, they are awesome! Good luck! E6530-EFI.zip
  32. 1 point
    Everything work except the wireless
  33. 1 point
    As far as I know, that card will definitely cause trouble until the property injection is done (or the other older alternatives such as removing the BrcmNIC Plugin kext).
  34. 1 point
    Re: audio, please refer to my previous post and what you've done... Did you install or inject the kexts as advised? Did you try the various layouts?
  35. 1 point
    Mojave patcher tool is for unsupported platforms. The X1 Carbon 3rd gen meets all the technical requirements for Mojave, so, afaik, no need for the patcher.
  36. 1 point
    Hi all! I am currently using Mojave and the VoodooPS2Controller and the Trackpad works well but I don't have any gesture. I tried to use the ApplePS2SmartTouchPad kext and gestures works (Only the 4 fingers tho) but the clicks are not ok and it's unusable for that. My friend has a T480S with an Elan trackpad and that kext works very well on his laptop. My trackpad is a Synaptics one and i read that is supported one the ApplePS2 kext. I tried already to change some plist values of the kext without success. Can someone help me to have a fully functional trackpad? Thanks in advance EDIT: I tried the VoodooPS2 and SSDT-KBD.aml from the Clover folder of the following post but I think is the same from mine VoodooPS2 (trackpad ok but no gestures).
  37. 1 point
    @M0CRT How did you get Mirone to come out of retirement? There's no existing ALC289 kexts, not even Mirone's AppleHDA Patcher.
  38. 1 point
    I finally managed to get audio working! It's probably that the latest versions of the Lilu and AppleALC kexts don't accept the legacy injection for the layout-id anymore. I found the following information I used Hackintool in order to generate the necessary code to copy and paste into the existing config.plist (removing the placeholders with hashes which were in there from Rehabman's config.plist) and I now have audio!
  39. 1 point
    @hcardoso483, you should have a look at the Bootloaders section of the forum where dual-booting is fairly largely covered, including for Win10.
  40. 1 point
    Strange thing... Before, when I was trying all layouts, 13 was not working. Now it works, but I have to check it everything working properly. I will let You know. But for now, thanks a lot for your help
  41. 1 point
    Click on View and select. 'Show All Devices" Then click on the root of drive to format
  42. 1 point
    Try the tools/layouts specified in the Keyboard Layout-related threads in the Keyboard section of the forum.
  43. 1 point
    I can see 4G DW5811e Snapdragon device is connected to USB port. But I newer tried to use it. I will try it next week, cause I am curious now. I'll let you know.
  44. 1 point
  45. 1 point
    @Hervé well yes i have/had the HPET fix in place... but thank you! your post put me on the right track. now everything seem to work. I removed FakePCIID_XHCIMux kexts and went with RehabMan's standard USBInjectAll.kext. Then the "Bluetooth HCI" shows up (before and after sleep) in the USB list. but was missing 3 SuperSpeed ports. Bluetooth seems to show up HS10 so fixed up a custom Injector and have all the ports! Now everything seems to work: Display: LCD (with brightness), External DP and HDMI Audio (speaker, mic) Intel Bluetooth Wifi - with 2nd card - Atheros Sleep/Wake USB3 - 4 external ports. [email protected] /Extra/OSX-build/Systems/Dell $ ioreg -l|grep "\-o HS" | | | +-o [email protected] <class AppleUSB20XHCIPort, id 0x10000029d, registered, matched, active, busy 0 (0 ms), retain 10> | | | +-o [email protected] <class AppleUSB20XHCIPort, id 0x10000029e, registered, matched, active, busy 0 (8889 ms), retain 16> | | | +-o [email protected] <class AppleUSB20XHCIPort, id 0x10000029f, registered, matched, active, busy 0 (0 ms), retain 10> | | | +-o [email protected] <class AppleUSB20XHCIPort, id 0x1000002a0, registered, matched, active, busy 0 (0 ms), retain 10> | | | +-o [email protected] <class AppleUSB20XHCIPort, id 0x1000002a1, registered, matched, active, busy 0 (268 ms), retain 15> [email protected] /Extra/OSX-build/Systems/Dell $ ioreg -l|grep "\-o SS" | | | +-o [email protected] <class AppleUSB30XHCIPort, id 0x1000002a2, registered, matched, active, busy 0 (0 ms), retain 13> | | | +-o [email protected] <class AppleUSB30XHCIPort, id 0x1000002a3, registered, matched, active, busy 0 (0 ms), retain 13> | | | +-o [email protected] <class AppleUSB30XHCIPort, id 0x1000002a4, registered, matched, active, busy 0 (421 ms), retain 18> | | | +-o [email protected] <class AppleUSB30XHCIPort, id 0x1000002a5, registered, matched, active, busy 0 (0 ms), retain 13> posted EFI here: https://github.com/tluck/Dell-M4800-Clover
  46. 1 point
    Hi there, As some of you may or may not know - OSXL is currently looking into integrating a cryptocurrency - the reason behind this is many - but mostly to have fun - and to allow developers and people who help - to be rewarded for the hard work they do. Unlike other sites that generate their own currency we will most likely go with a coin/token that already is out there - and we are studying a few like: XRP, Kin, Bos, Rise and ETN Today my attention fel to a new: Initiative Q. They are running a campaign - if you head over and signup you will get a bunch of coins for free - so head over and signup and let me know what you think: Link: https://initiativeq.com/invite/HV_cnzp77 Also, if you have any experince with crypto - like development - drop me a message about joining our crypto team.
  47. 1 point
    Steps to change the DVMT value (Done on Windows or WinPE) /!\ Warning, some files in attachment will show as infected, you'll need to disable your antivirus temporarily Use at your own risk! 1) Universal BIOS Backup ToolKit 2.0.exe - to backup the BIOS (i.e. DellInc.-A07.rom) 2) UEFITool.exe to find the module labeled SetupPrep (not Setup as per FireWolf’s guide) and extract the PE32 image section (setup.bin) Update: For Dell Only: Search with this GUID then extracting the PE32 body under it would be faster /easier than finding the module per guide 899407d7-99fe-43d8-9a21-79ec328cac21 3) Universal IFR Extractor.exe to extract setup.bin to a readable text file 4) Use notepad to search for “DVMT” in the text file i.e. for the E7450, 2 were found at 0x432 and 0x433 but only 0x432 needs to be changed to 0x3 5) Format an USB drive to fat32 and create a folder name EFI 6) Download the EFI Shell and extract the Boot folder to EFI folder (EFI/Boot/bootx64.efi) 7) Boot system with the USB and select UEFI Boot At the grub prompt, enter these commands, hit enter after command, then exit and reboot i.e. setup_var 0x432 0x3 To verify if the value was updated, just enter setup_var 0x432 and hit enter, the value will be listed More detailed instruction in attachment /!\ Alternatively, just use Lilu.kext + IntelGraphicsDVMTFixup Whatevergreen without having to mess with the BIOS https://github.com/vit9696/Lilu/releases https://github.com/vit9696/Lilu/blob/master/KnownPlugins.md https://github.com/BarbaraPalvin/IntelGraphicsDVMTFixup/releases https://github.com/acidanthera/WhateverGreen/releases DVMT_Tools.zip
  48. 1 point
    Those issues and limitations are already clearly posted on Chunnann's original thread at InsanelyMac (see from post #21); let's not unnecessarily duplicate info here, it's best to report issues to Chunnann directly in at IM. The above facility is a mere adaptation of Chunnann's work posted here. For the record, only AR946x cards appear to run at decent speeds to date. NB: Re: macOS versions, you obviously meant 10.13 and 10.12 (not 10.3 and 10.2)
  49. 1 point
    Dev Micky1979 @IM just released a new Enoch boot file r2851 that includes a number of fantastic new developments, including on-the-fly kernel + kexts patching facility. This allows similar mods to what was restricted to Clover until now. Ace! http://www.insanelymac.com/forum/topic/231075-chameleon-23svn-official-pkg-installer-binaries/page-204?do=findComment&comment=2376053
  50. 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.
This leaderboard is set to Amsterdam/GMT+01:00
  • Create New...