Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Matanel Sindilevich

  • Content count

  • Joined

  • Last visited

About Matanel Sindilevich

  • Rank
    InsanelyMac Protégé
  • Birthday 05/14/1980

Profile Information

  • Gender
  1. Lenovo ThinkPad T420 with UEFI Only

    @tluck Apparently, after upgrading to the latest Clover build b2428, the boot entries got in order, with only one entry for Windows. So maybe the double-icon for Windows was just a glitch of previous Clover builds. Did you install Windows prior to Mac OS? I did install Mac OS first, then installed Windows (both in UEFI mode, of course). In that scenario Windows boot loader would prevail and boot straight into Windows, instead of showing the Clover boot menu. Therefore, I had to copy CLOVERX64.efi from Clover to Microsoft folder as bootmgfw.efi, per this blog: http://www.tonymacx86.com/hp-probook/103945-dual-booting-w8-os-x-uefi-4.html. Wow, that is exactly what I needed -- an example of Clover installation options. I didn't see using RC scripts anywhere, though. Am I wrong? Basically, I learned the following is customized by you, whereas other stuff flows in untouched from Clover, correct? <ZIP file>/T420/EFI/CLOVER/ACPI/patched folder <ZIP file>/T420/EFI/CLOVER/kexts folder <ZIP file>/T420/EFI/CLOVER/OEM folder <ZIP file>/T420/EFI/CLOVER/config.1366x768.plist file And <ZIP file>/T420/EFI/CLOVER/config.1600x900.plist file As for ssdtPRgen-clover.sh it does generate two files: ssdt_pr.aml and ssdt_pr.dsl. But you only guide to copy the .AML one over. Why not both of them? It probably seems like a lot of questions. The reason is I am a newbie in this area and want to understand how things work. I have had a real iMac for 8 years up until recently, when its power module has died. Now trying to get Mac OS glory back with a backup hardware. My ultimate goal for now is trying to understand what is going on under the covers in Hackintosh and try to get a newer laptop model work with Mac OS -- Lenovo T440P. Now only I have a theoretical knowledge for auto-generation of DSDT's (by Clover) and SSDT's (by ssdtPRgen-clover.sh). But area of KEXT modification seems too unexplored now. Also the ease you guys exchange pieces of AML and DSL files for DSDT and SSDT... Just awesome.
  2. Lenovo ThinkPad T420 with UEFI Only

    Running ssdtPRgen-clover.sh requires an Internet connection. It tries to download iasl from GitHub. Sometimes, though, an Internet connection is unavailable. I haven't had Ethernet working until I installed the Ethernet KEXT to /S/L/E and then rebooted. But the course of the guide suggests you do the KEXT copying and running ssdtPRgen-clover.sh without rebooting the machine in-between. Also, no WiFi working. Does it mean the integrated Lenovo T420's wireless card is not supported in Mac OS X?
  3. Lenovo ThinkPad T420 with UEFI Only

    Thank you! Actually, I did install all the custom KEXT's into /S/L/E. I have used this Kext Utility app you have recommended. After I re-installed Mavericks fresh to check once again will the OEM folder work, I went on installing Windows as a dual-boot. Then, after an unidentified number of reboots Mac OS did pick up settings from OEM/<Product ID>. And, since all the custom KEXT's were in place in /S/L/E sound started to work for me! apparently, here is some "magic" in those reboots. Connecting a Lenovo desktop keyboard via USB, though will map keyboard modifier keys correctly. Will double-check the layout of that desktop keyboard to make sure it is same/different comparing to Lenovo T420's built-in keyboard. I will give a try to the new version of Clover config. I don't need to reinstall everything for that purpose, right? Just mounting the ESP partition and copying over files from the ZIP? Another question, if I may, I have two entries for booting Windows on the Clover boot screen. Only one of them would really boot into Windows, where another will just return to the Clover boot screen. I did a dual-boot by copying /Volumes/ESP/EFI/CLOVER/CLOVERX64.efi to be /Volumes/ESP/EFI/Microsoft/Boot/bootmgfw.efi, whereas renaming the original bootmgfw.efi to bootmgfw-orig.efi. Is this a way to remove/hide non-working boot entry in the Clover boot screen?
  4. Lenovo ThinkPad T420 with UEFI Only

    @tluck, thank you a lot for your guide (post #481) installing Mac OS X on Lenovo T420! One thing, though, that I couldn't get working is applying product-specific version/DSDT, as you described. What I did initially was renaming OEM/ProductID.1600x900 to OEM/4236AQ7. (This name is seen on a label on the bottom of my laptop: Product ID: 4236AQ7). But I had no sound (sound was supposed to be fixed by product-specific configurations, according to your guide). So I just copied the contents of the OEM/4236AQ7 folder over to the /Volume/ESP/EFI/CLOVER, replacing the generic config.plist (renamed at some point from config1600x900.plist) and the ACPI folder. This worked and sound system was identified by Mac OS. Another thing, is that hardware sound volume buttons are not synchronized with Mac OS's software sound volume control. When I change the volume with the hardware buttons -- the system volume control is kept at 100% volume. Physically, sound volume does change, though. The last issue I found, is inability of Mac OS to automatically set the Windows key to be the Command key, instead the Windows key would be treated as Alt, and Left Alt as Command key (I didn't check what Right Alt performs as, though). I solved by reassigning control keys in the keyboard preferences.
  5. Bootcd for intel Macs with Symantec Ghost,...

    Hi! This is an interesting CD image you are working with! Maybe you can answer this question: I am creating an ISO image with BootWizard from the Symantec Ghost Solution Suite 2.0.1, yet the image (an ISO file) when burned to a CD, would not bootstrap! Do you have an idea how to use this function correctly? Thank you!