Jump to content
Kogen Mantis

Lenovo ThinkPad T420 with UEFI Only

4,162 posts in this topic

Recommended Posts

I´m getting occasional KP the last weeks, I never saw that frequent before with Hackintosh.

This is the backtrace:

 

*** Panic Report ***
panic(cpu 1 caller 0xffffff80003ff085): Kernel trap at 0xffffff8000836a6f, type 13=general protection, registers:
CR0: 0x0000000080010033, CR2: 0xffffff81dc581000, CR3: 0x000000000390a000, CR4: 0x00000000000626e0
RAX: 0x0000000000000015, RBX: 0x0000000000000015, RCX: 0xffffff801efd5480, RDX: 0x0000000000000000
RSP: 0xffffff81e68c3c00, RBP: 0xffffff81e68c3c40, RSI: 0xffffff8000c09570, RDI: 0xffffff801effe8c0
R8:  0x0000000000000000, R9:  0xffffff801effe880, R10: 0xffffff801effe8a0, R11: 0x0000000000000000
R12: 0xffffff801effe880, R13: 0xffffff801effe840, R14: 0x447373616c436174, R15: 0xffffff8000c09570
RFL: 0x0000000000010206, RIP: 0xffffff8000836a6f, CS:  0x0000000000000008, SS:  0x0000000000000000
Fault CR2: 0xffffff81dc581000, Error code: 0x0000000000000000, Fault CPU: 0x1, PL: 0, VF: 0
 
Backtrace (CPU 1), Frame : Return Address
0xffffff800014bc50 : 0xffffff80002e950c 
0xffffff800014bcd0 : 0xffffff80003ff085 
0xffffff800014beb0 : 0xffffff800029a543 
0xffffff800014bed0 : 0xffffff8000836a6f 
0xffffff81e68c3c40 : 0xffffff7f82a9b58d 
0xffffff81e68c3c80 : 0xffffff7f82a9c72a 
0xffffff81e68c3ca0 : 0xffffff7f82a9ca6b 
0xffffff81e68c3d30 : 0xffffff7f82a9cbfa 
0xffffff81e68c3d80 : 0xffffff7f82b90326 
0xffffff81e68c3e00 : 0xffffff7f82b90af0 
0xffffff81e68c3e40 : 0xffffff800089793d 
0xffffff81e68c3e80 : 0xffffff800089768e 
0xffffff81e68c3f10 : 0xffffff8000896c46 
0xffffff81e68c3f60 : 0xffffff800089865e 
0xffffff81e68c3fb0 : 0xffffff80002998f7 
      Kernel Extensions in backtrace:
         org.netkas.driver.FakeSMC(1443.0)[F4D6719F-5FF2-3417-8F1B-7CA64314D941]@0xffffff7f82a99000->0xffffff7f82ab1fff
            dependency: com.apple.iokit.IOACPIFamily(1.4)[4F7FB6AD-2498-3F71-827C-ED7AA4BF2511]@0xffffff7f80e1b000
         org.hwsensors.driver.ACPISensors(1443.0)[FC0EE82A-1514-3891-A0AF-6A7947B7EFDF]@0xffffff7f82b8f000->0xffffff7f82b9cfff
            dependency: com.apple.iokit.IOACPIFamily(1.4)[4F7FB6AD-2498-3F71-827C-ED7AA4BF2511]@0xffffff7f80e1b000
            dependency: org.netkas.driver.FakeSMC(1443)[F4D6719F-5FF2-3417-8F1B-7CA64314D941]@0xffffff7f82a99000
 
BSD process name corresponding to current thread: kernel_task

 

Boot args: slide=0 kext-dev-mode=1 rootless=0 

 

 

Does anybody have similar issues with a T420 Sierra recently?

I´ll try with my other T420, which usually has W10 installed, to rule out a hardware error, but I don´t think its the hardware.

 

Off topic:

Did any of you hear from René Trost maybe?

Many will know Rene as one of the kind admins over at OSX86.com / kexts.com or from other hackintosh forums. ;)

Share this post


Link to post
Share on other sites
Advertisement

@goodguess. seem like the ACPIsensor was the reason for KP? can remove it if you still have issues - its a non-essential  fakesmc plugin 

 

@somez - here is another idea to fix graphics issues with High Sierra. I was getting some black lines so I have reverted the Graphics Kexts to the Sierra versions. so far no issues.

$ ls -ld /Library/Extensions/AppleIntel*
drwxr-xr-x  3 root  wheel  96 Apr 14  2017 /Library/Extensions/AppleIntelHD3000Graphics.kext
drwxr-xr-x  3 root  wheel  96 Apr 14  2017 /Library/Extensions/AppleIntelHD3000GraphicsGA.plugin
drwxr-xr-x  3 root  wheel  96 Apr 14  2017 /Library/Extensions/AppleIntelHD3000GraphicsGLDriver.bundle
drwxr-xr-x  3 root  wheel  96 Apr 14  2017 /Library/Extensions/AppleIntelHD3000GraphicsVADriver.bundle
drwxr-xr-x  3 root  wheel  96 Apr 14  2017 /Library/Extensions/AppleIntelSNBGraphicsFB.kext
drwxr-xr-x  3 root  wheel  96 Apr 14  2017 /Library/Extensions/AppleIntelSNBVA.bundle

so to make these load instead of the standard ones, i edited the Info.plist and changed all the versions from 10.x.x to 100.x.x

$ kextstat |grep -i graph
   93   14 0xffffff7f824b1000 0x49000    0x49000    com.apple.iokit.IOGraphicsFamily (519.13) 0C5824DB-F0E8-3C89-90FF-32400837361C <12 7 5 4 3 1>
   99    0 0xffffff7f82531000 0x2e000    0x2e000    com.apple.driver.AppleIntelSNBGraphicsFB (100.0.2) 4651D99C-251F-319C-A742-FE237C8CD3A3 <93 12 11 7 6 5 4 3 1>
  120    3 0xffffff7f8293a000 0x9000     0x9000     com.apple.AppleGraphicsDeviceControl (3.18.44) 02233606-BC28-33FA-AB6F-7D86206B8394 <93 12 7 6 5 4 3 1>
  122    0 0xffffff7f82948000 0x63000    0x63000    com.apple.driver.AppleIntelHD3000Graphics (100.0.2) BF52C5F1-7F69-35F4-935F-3F5F237AC46C <93 12 7 5 4 3 1>
  128    1 0xffffff7f82bc0000 0x3000     0x3000     com.apple.driver.AppleGraphicsControl (3.18.44) 6EA0D4AD-6E3C-37F3-B2EA-13FE0F7B8545 <7 5 4 3 1>

Share this post


Link to post
Share on other sites

 

@goodguess. seem like the ACPIsensor was the reason for KP? can remove it if you still have issues - its a non-essential  fakesmc plugin 

 

@somez - here is another idea to fix graphics issues with High Sierra. I was getting some black lines so I have reverted the Graphics Kexts to the Sierra versions. so far no issues.

$ ls -ld /Library/Extensions/AppleIntel*
drwxr-xr-x  3 root  wheel  96 Apr 14  2017 /Library/Extensions/AppleIntelHD3000Graphics.kext
drwxr-xr-x  3 root  wheel  96 Apr 14  2017 /Library/Extensions/AppleIntelHD3000GraphicsGA.plugin
drwxr-xr-x  3 root  wheel  96 Apr 14  2017 /Library/Extensions/AppleIntelHD3000GraphicsGLDriver.bundle
drwxr-xr-x  3 root  wheel  96 Apr 14  2017 /Library/Extensions/AppleIntelHD3000GraphicsVADriver.bundle
drwxr-xr-x  3 root  wheel  96 Apr 14  2017 /Library/Extensions/AppleIntelSNBGraphicsFB.kext
drwxr-xr-x  3 root  wheel  96 Apr 14  2017 /Library/Extensions/AppleIntelSNBVA.bundle

so to make these load instead of the standard ones, i edited the Info.plist and changed all the versions from 10.x.x to 100.x.x

$ kextstat |grep -i graph
   93   14 0xffffff7f824b1000 0x49000    0x49000    com.apple.iokit.IOGraphicsFamily (519.13) 0C5824DB-F0E8-3C89-90FF-32400837361C <12 7 5 4 3 1>
   99    0 0xffffff7f82531000 0x2e000    0x2e000    com.apple.driver.AppleIntelSNBGraphicsFB (100.0.2) 4651D99C-251F-319C-A742-FE237C8CD3A3 <93 12 11 7 6 5 4 3 1>
  120    3 0xffffff7f8293a000 0x9000     0x9000     com.apple.AppleGraphicsDeviceControl (3.18.44) 02233606-BC28-33FA-AB6F-7D86206B8394 <93 12 7 6 5 4 3 1>
  122    0 0xffffff7f82948000 0x63000    0x63000    com.apple.driver.AppleIntelHD3000Graphics (100.0.2) BF52C5F1-7F69-35F4-935F-3F5F237AC46C <93 12 7 5 4 3 1>
  128    1 0xffffff7f82bc0000 0x3000     0x3000     com.apple.driver.AppleGraphicsControl (3.18.44) 6EA0D4AD-6E3C-37F3-B2EA-13FE0F7B8545 <7 5 4 3 1>

 

Hey tluck,

 

Thanks for still trying to fix this. Could you give me more details on the steps how to do this? I get the idea, but not sure how to do it.

 

Thank you.

Share this post


Link to post
Share on other sites

Hello, what's the app shown on the thread thumbnail?e6e5380ce5a2273765b2569792c11274.jpg

 

Sent from my Redmi 3S using Tapatalk

Share this post


Link to post
Share on other sites

I'm trying to get my T420 running Higher Sierra stable but after being logged in for about 20 minutes (and usually when I'm not actively doing anything), the OS would lock up but my mouse would still be usable; I wouldn't be able to click on anything though. It sometimes turned into the spinning beach ball but would otherwise be non-functional.

 

Anyone else run into a similar issue? I'm not sure how to log the crash if this is indeed a crash but I can post logs if someone could tell me how to record it. Any suggestions?

Share this post


Link to post
Share on other sites

I'm trying to get my T420 running Higher Sierra stable but after being logged in for  about 20 minutes (and usually when I'm not actively doing anything), the OS would lock up but my mouse would still be usable; I wouldn't be able to click on anything though. It sometimes turned into the spinning beach ball but would otherwise be non-functional.

 

Anyone else run into a similar issue? I'm not sure how to log the crash if this is indeed a crash but I can post logs if someone could tell me how to record it. Any suggestions?

You are not alone, but we have no idea why is this happening so far :(

Share this post


Link to post
Share on other sites

@Somez: Have you tried booting into safe mode? One of the articles I came across through googling my console errors show resolution when they just boot into safe mode and then back into normal mode. It did seem to resolve that particular error for me; I'm still testing to see if it freezes.

 

I don't know much about macs except as a normal users on a regular MBP; this is my first go-round with a hackintosh so forgive me for probably some stupid suggestions.

 

For another one of my console errors, I came across this (below); not sure if that is causing issues with kexts.

 

User-Approved Kernel Extension Loading

macOS High Sierra 10.13 introduces a new feature that requires user approval before loading newly-installed third-party kernel extensions (KEXTs). When a request is made to load a KEXT that the user has not yet approved, the load request is denied. Apps or installers that treat a KEXT load failure as a hard error will need to be changed to handle this new case.

 

https://developer.apple.com/library/content/technotes/tn2459/_index.html

Share this post


Link to post
Share on other sites

I haven’t tried booting into safe mode yet. I’m waiting for updates to come out, hoping they will eventually solve this problem.

 

I’m also not an expert of hackintoshing. I’d used many Macs before and in fact we’ve just bought an Air to my wife as it was on sale in Hungary. However buying another one for me as a hobby does not justify the price so I stick with the T420.

 

In fact I just basically follow the instructions here created by tluck. He is the expert and the heart of this topic :) “Unfortunately” as I understand so far he does not suffer from the freezing issue which obviously makes finding the root cause and the fix harder.

 

I’m also considering the option to do a clean install of high sierra because my existing installation is an upgrade from Sierra.

Share this post


Link to post
Share on other sites

@Somez: Booting into safe mode is pretty easy so I would suggest trying that before the clean install; however, a clean install is often a good idea if I've learned anything from my Windows days. Here is the article that gave me the safe mode suggestion: http://brettterpstra.com/2017/10/20/have-you-tried-rebooting/

 

For what it is worth, my freeze problems have seem to disappear after trying safe mode. Fingers crossed!

Share this post


Link to post
Share on other sites

Hi, I need your help.

yesterday I had to reinstall High Sierra on my T420. All is working fine with the latest Clover.zip package. But after wake from sleep my power led and sleep led on the cover keeps flashing.

Everything else works fine after sleep. I need to reboot, of course, for both leds to stop flashing.

 

Do you have ideal what can cause that? I have disabled hibernation and removed sleep image (hibernate mode set to 0).

OK I think I found the problem. For many years I had installed external disk in CD Bay instead of CD Drive. When I put CD Drive back, or just remove the external drive from CD Bay, led behaves as it should. So something is not right with the external drive sitting in the cd bay, then.

Edited by jus12

Share this post


Link to post
Share on other sites

@jus12 - hmm. strange - there is fix in the DSDT that address this issue - reset LED upon wake from sleep. so i dont know why it would still flash? i presume you have the custom DSDT in place?

Share this post


Link to post
Share on other sites

@jus12 - hmm. strange - there is fix in the DSDT that address this issue - reset LED upon wake from sleep. so i dont know why it would still flash? i presume you have the custom DSDT in place?

 

Hi tluck, thanks for the update. Well, it is strange. I have been using your packages for years now with a great success. I have never created dedicated DSDT. I was always using yours. For my W520 I had created one but not for T420.

So all files I'm using as they are in your packs.

 

So I have tried to use DSDT files from previous (working) builds. But no change. Latest HS maybe have changed something? I'm running now 10.13.3.

Edited by jus12

Share this post


Link to post
Share on other sites

I would really appreciate if someone here can give the steps for downgrading from High Sierra to Sierra on T420. Should I reformat system partition and when should I do it? There are a lot of questions actually, I cannot afford experiments because T420 is the only one computer I have at the moment... Thanks everyone for help.

Share this post


Link to post
Share on other sites

@rollitab - For the T420, an OS downgrade is under the constraints or process as a real mac. so you can follow the recipes posted in a variety of locations. but most seem to involve  an erase, (clean full) install and restore of data/apps

 

what issues are you seeing with High Sierra. ?

 

somez is seeing some issues - but does  not seem to be the BRSYNC/Hang problem common with HD 3000 - seems to be a different issue. 

But on one of my systems I had some gfx/hangs with BRSYNC/VRSYNC - but since I have reverted the graphics kexts to the Sierra versions, so far so good.

 

sleep/wake ok for me. LED power light goes from slow on/off during sleep to on for wake - moon icon on lid switches to battery icon for wake.

Edited by tluck

Share this post


Link to post
Share on other sites

@tluck, I've just noticed that the LEDs on the outside of my LCD does not work. Let's stop investigating my issue because something is odd here. I'll do a backup and then a clean install from scratch hoping the issue will go away.

Share this post


Link to post
Share on other sites

OS sierra.

 

I reinstalled the system couple months ago and finally want to connect to an external monitor.

 

The DP port on the side is not working?!!... The VGA works fine but I got some shadows.

 

I did appy the patch in the clover and use 8.1 as system. What did I do wrong?

 

Thanks

 

The second issue I found is there is no USB wake up on this laptop. Lenovo website says press the bottom is the only way to wake up the laptop. Is that true?

Share this post


Link to post
Share on other sites

@fireROR -

 

odd, the DP on my system works? i use the DP to connect to my HP monitor. what happens when you attach the DP cable? it should flash and recognize something attached?

 

not sure about USB wake. i have not tried it.  i use BT mouse and keyboard.

Share this post


Link to post
Share on other sites
On 28.2.2018 at 4:53 PM, tluck said:

But on one of my systems I had some gfx/hangs with BRSYNC/VRSYNC - but since I have reverted the graphics kexts to the Sierra versions, so far so good.

 

Could you please describe more detailed how to do this.

Thanks in Advance

Share this post


Link to post
Share on other sites
On 3/3/2018 at 6:52 PM, tluck said:

@fireROR -

 

odd, the DP on my system works? i use the DP to connect to my HP monitor. what happens when you attach the DP cable? it should flash and recognize something attached?

 

not sure about USB wake. i have not tried it.  i use BT mouse and keyboard.

 

Just nothing. Doesn't matter boot with DP or plugin after boot. No signal at all.

The VGA port will not put the monitor into sleep. Not sure what was wrong.

My LCD screen is 1080p but it should not relate to this issue, (I have to use another inject to get intel video card working)

Share this post


Link to post
Share on other sites

Running Sierra, should i update to high sierra? howse the stability?

Share this post


Link to post
Share on other sites
4 hours ago, zalien said:

Running Sierra, should i update to high sierra? howse the stability?

I'm having constant freezes after every like 30 minutes, but most of the people does not suffer from this since I have not seen any complaints from others.

Share this post


Link to post
Share on other sites

well on High Sierra, I have 2 T420 systems. One has an AUO LCD display and has freezes. and the other has LG LCD display (replaced the original AUO) and works great.

 

Share this post


Link to post
Share on other sites

I don't plan on replacing the LCD, so I'm really considering the option to format and install Sierra. Especially that based on the comments almost nobody has reported the freezing issue with High Sierra and we have no clue about what is causing the freezes.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host
      Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. 
       
      The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg
       
      @colt2 HOW TO: Create a bootable El Capitan ISO for VMware
      @dsmccombs comment on faking Ivybridge Processor
      @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6
      @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
      VirtualBox Forum: Status of OSX on OSX
       
      Requirements
         Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X)    4GB or more RAM (2GB or more will be needed for OS X)    Hard Disk with at least 40GB free for Virtual Machine    Oracle VM VirtualBox v 5.0.34    Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75    16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC  
      Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes.  Note: you will need approx 16GB of free space on your hard disk for the script to complete.
       
       
       
      3.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 4.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
       
      Create an El Capitan Virtual Machine in VirtualBox
      1.  Open the VirtualBox program and click the "New" button to create a new VM.
       

       
      2.  Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version.  I named my Virtual Machine "El_Capitan", then clicked next...
       

       
      3.  Leave the Memory size at the recommended 2048 MB, then click next.
       

       
      4.  Choose to "Create a virtual hard disk now", then click the create button.
       

       
      5.  For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare.  Click next...
       

       
      6.  For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space).
       

       
      7.  On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger.  When you click the create button, you will now see your new VM in the VirtualBox main GUI.
       

       
      8.  Click the settings button on the Main Menu to tweak a few settings....
         a.  On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?)
       

       
         b.  On the System/Processor tab, you can increase the allocated CPU cores to 2
       

       
         c.  On the Display tab, you can increase the allocated Video Memory to 128MB
       

       
         d.  On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". 
       

       
      Navigate and select the El Capitan ISO we created earlier...
       

       
         e.  Click the OK button to finalise the VM settings.
       
       
      Patch El Capitan vbox configuration file with DMI Settings from a Mac
      1.  From the start menu, type cmd and click run as administrator to open an administrative command prompt. 
       

       
      2.  Choose a Mac Model similar to your host system, then type the following lines, followed by <enter>  after each line.  Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick...
       
      Eg iMac11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3.  Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors.  You can try from one of the following if this happens:

      To spoof Lynnfield i5 750 CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4.  Close the command prompt window.
       
       
      Installation of El Capitan
      We are now ready to start the El_Capitan Virtual Machine....
       



       
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

       
      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan.
       

       
      3.  Quit DU and choose Macintosh HD to install El Capitan on.
      4.  After 20-30 min (depending on how fast your system is), the installation will complete.  At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive.  The VM is now ready to reboot into OS X from the virtual hard drive.
      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
      7.  Finally, you will arrive at the El Capitan Desktop.
       

       
      8.  Network/internet and audio should work OOB but on my system, the sounds were distorted.  Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). 
       
       
      Customization with VBoxManage
      1.  You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt:
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
       
      Update:  For VirtualBox 5.2.x, the command for changing screen resolution has changed...
       
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution)
      eg
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2.  Adding serials and other SMBIOS details for the System Information Screen
      VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html.
       
      Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above).  Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free .
       

       
      UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51.
      UPDATE macOS High Sierra 17A365:  For macOS High Sierra, use CHSI.tool in post#73.
      UPDATE macOS Mojave Beta:  For macOS Mojave Beta, use CMJI.tool on page 4 of thread.
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
    • By fantomas1
      -----------------------------
      Mise à jour 12/07/2018
      -----------------------------
       
      La sortie de macOS 10.14 Beta m'oblige à mettre ce topic à jour. Plus de détails dans ce post.
       

       

       
      -----------------------------
      Mise à jour 09/06/2017
       
      -----------------------------
       
      La sortie de macOS 10.13 Beta m'oblige à mettre ce topic à jour. Plus de détails dans ce post.
       

       
       
       
      -----------------------------
      Mise à jour 15/06/2016
      -----------------------------
       
      Une petite mise à jour du topic pour confirmer le bon fonctionnement du patch à la volé de Clover (r3561) avec macOS Sierra.
       

       
       
       
      -----------------------------
      Mise à jour 24/08/2015
      -----------------------------
       
      ok, très bien,
       
      comme pour la HD6770, la nouvelle méthode du patch à la volé est de nouveau fonctionnel et avec les dernières versions de Clover.
       
      pour ma part, je suis sur El Capitan DB7 et Clover r3259
       

       
       
      par contre, je suis toujours obligé de m’aider de l’astuce avec FakeSMC pour que mes kexts soient toujours chargés, mais au moins cela marche.   
       
       
       
       
      et pour config.plist, cela donne ça :
       

       
       
      ceci est juste un exemple avec ma HD4830, il va de soi que vous devez mettre Device-ID de votre carte graphique !!!
       
       
       
       
       
      Salut à tou(te)s
       
      Comme certain(e)s le savent, les cartes graphiques dites "Exotiques" ne sont pas supportés par le système d'exploitation d'Apple.
      En sus d'ajouter l'identifient de la carte graphique (Device ID) dans l'Info.plist du ou des kexts concernés, il faut aussi interagir sur la partie "binaire" du kext par le biais du "patching".
       
      Dans notre cas, les cartes graphiques exotiques sont les cartes AMD (anciennement ATI) de la série HD 48xx, et plus précisément les HD 4830, HD4850, HD4870x2 et HD4890.*
       
      Donc le but est de faire fonctionner ces cartes graphiques de manière stable et fluide en activant QE_CI, chose nécessaire pour en profiter pleinement du système d'exploitation.
       
      * Juste avant de commencer, vous l'avez peut-être remarqué, la HD4870 n'est pas sur la liste suscitée et pour cause c'est que cette carte graphique est nativement supportée par le système d'exploitation d'Apple. Son Device ID est 0x94401002 que vous pouvez trouvé dans l'Info.plist des kexts concernés et c'est celui-ci que nous allons utiliser afin de le remplacer par le Device ID de notre carte graphique.
       
      ** Ce tuto est fait pour fonctionner sous OS X Mavericks, mais il doit fonctionner aussi avec les autres. La seule chose différente c'est l'adresse binaire à patcher.    
       
       
      Très bien, comme le titre le suggère, nous allons voir comment faire reconnaître ces cartes graphiques sous Clover et obtenir par la même un QE_CI activé et parfaitement fonctionnelle.
       
      Je vais utiliser ma Sapphire HD4830 512 MB GDDR3 PCI-E (comme cobaye    ) pour ce test et qui a pour Device ID 0x944c1002.
       
      Pour que ce test réussisse, nous allons donc utiliser ces 2 kexts, à savoir AMD4800Controller.kext (pour la partie QE) et ATIRadeonX2000.kext (pour la partie CI) et allons ajouter notre Device ID dans l'Info.plist. via le tweak "KernelAndKextPatches"
       
      Donc les valeurs à entrer dans notre config.plist sont celle-ci :
      <key>KernelAndKextPatches</key>     <array>         <dict>             <key>Name</key>             <string>AMD4800Controller</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>         <dict>             <key>Name</key>             <string>ATIRadeonX2000</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>     </array> Comme vous pouvez le voir, la clé "InfoPlistPatch" sert à injecter notre Device ID "uniquement" dans Info.plist, sans y toucher à la partie "binaire" de nos kexts. La clé "Find" a pour fonction de trouver le Device ID que l'on veut remplacer par le notre en utilisant la clé "Replace".
       
      Très bien, maintenant comme nous l'avons dit au début de ce tutoriel, ajouter notre Device ID n'est pas suffisant pour faire fonctionner pleinement notre carte graphique, il faut encore interagir sur la partie "binaire" de nos kexts. Dans notre cas, il va falloir agir uniquement sur un kext, çàd sur ATIRadeonX2000.kext et plus particulièrement sur ATIRadeonX2000.kext/Contents/MacOS/ATIRadeonX2000
       
      Et pour cela, nous allons faire comme ceci :
      <key>KextsToPatch</key> <array> <dict>     <key>Name</key>     <string>ATIRadeonX2000</string>     <key>Find</key>     <data>0F8394010000</data>     <key>Replace</key>     <data>909090909090</data> </dict> </array> Là nous pouvons voir que la clé "InfoPlistPatch" n'est pas utilisée et donc ces valeurs n'auront aucun effet sur l'Info.plist mais agiront uniquement au niveau de la partie "binaire". 
       
      Et voici les valeurs en leur forme complète que vous devrez ajouter dans votre config.plist
      <key>KernelAndKextPatches</key>     <array>         <dict>             <key>Name</key>             <string>AMD4800Controller</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>         <dict>             <key>Name</key>             <string>ATIRadeonX2000</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>         <dict>             <key>Name</key>             <string>ATIRadeonX2000</string>             <key>Find</key>             <data>0F8394010000</data>             <key>Replace</key>             <data>909090909090</data>        </dict>     </array> Très bien, maintenant il ne nous reste plus qu'à autoriser l'injection des kexts, sans quoi le patch ne fonctionnera pas. Et nous allons le faire via le tweak "InjectKexts" comme ceci :
      <key>SystemParameters</key> --> clé principale <dict>       <key>InjectSystemID</key>       <true/>       <key>InjectKexts</key> --> sous clé       <string>Yes</string> </dict>  
       
      Si certain(e)s d'entre vous préfèrent utiliser le logiciel "Clover Configurator" pour plus de facilité, voici comment entrer ces valeurs :
       
      Allez sur l'onglet "Kernel And Kext Patches" et faites comme ceci :
       
       
       
      *Ne faites pas attention sur le majuscule/minuscule, cela ne fait aucune différence
       
       
      Et pour injecter les kexts, aller sur l'onglet "System Parameters" et mettez l'option Inject Kexts sur Yes comme ceci :
       

       
       
      Voilà, vous n'avez plus qu'à enregistrer les ajustements, redémarrer votre pc et apprécier le résultat.
       
       
      MAIS ... seulement voilà ... il y a un problème ... 
       
      Quoi ? 
       
      Initialement, les kexts ne sont pas présents dans le kernelcache à cause de "OSBundleRequired=Safe Boot" (ils ne sont pas chargés en local par défaut mais en mode sans échec) et donc le patchage "à la volé" (on the fly) ne fonctionnera pas.
       
      Donc quoi, tout ça pour rien ?
       
      Non, bien-sûr, voici l'astuce pour remédier à cela :
       
      Dans un premier temps, il vous faut booter l'OS sans kernelcache. Si vous utiliser Clover Configurator, il vous suffit juste de cocher l'option "No Caches" dans l'onglet "System and Parameters" ou bien vous le faites directement dans votre config.plist :
      <key>SystemParameters</key> <dict>       <key>InjectSystemID</key>       <true/>       <key>InjectKexts</key>       <string>Yes</string>       <key>NoCaches</key>       <true/> </dict> Ceci aura donc pour effet de bloquer kernelcache et obliger boot.efi de charger le kernel et les kexts séparément. Clover et FSInject vont ensuite intercepter tous les chargements des kexts par boot.efi et changer "OSBundleRequired=Safe Boot" en "OSBundleRequired=Root" à la volé (on the fly) et forceront boot .efi à charger les kexts. Et ensuite dans un second temps, Clover va patcher l'Info.plist de ces deux kexts et la partie binaire de ATIRadeonX2000, kernel va les charger et ils seront rattachés à votre carte graphique.
       
      Une fois ceci fait (donc les kexts utilisés), il vous suffit de faire sudo touch /System/Library/Extensions. Ceci créera un nouveau kernelcache qui cette fois-ci contiendra vos kexts utilisés. Ensuite il ne vous reste plus qu'à redémarrer normalement (en décochant l'option No Caches dans Clover Configurator) et le patch fonctionnera à merveille.
       
       
      Oui, mais ... là aussi ...
       
      Quoi encore ?
       
      Seulement voilà, pour une raison ou une autre, il peut arriver que kernelcache se reconstruit tout seul et le patch "à la volé" ne fonctionne plus.
       
      Alors je fais quoi moi en attendant ?
       
      L'astuce la plus efficace pour le moment est d'injecter les infos de vos kexts à l'intérieur de l'Info.plist de FakeSMC.kext comme des IOKitPersonalities additionnels.
       
      ????Kézako????
       
      Ces infos vous les trouverez dans l'Info.plist de ces 2 kexts, sous IOKitPersonalities. Les voici :
       
      Pour AMD4800Controller.kext
      <key>Controller</key> <dict>         <key>ATY,Cardinal</key>         <dict>                 <key>aty_config</key>                 <dict>                         <key>CFG_NO_PP</key>                         <true/>                 </dict>          </dict>          <key>CFBundleIdentifier</key>          <string>com.apple.kext.AMD4800Controller</string>          <key>IOClass</key>          <string>AMD4800Controller</string>          <key>IOMatchCategory</key>          <string>IOFramebuffer</string>          <key>IOName</key>          <string>AMD4800Controller</string>          <key>IOPCIMatch</key>          <string>0x94401002 0x944a1002</string>          <key>IOProbeScore</key>          <integer>65050</integer>          <key>IOProviderClass</key>          <string>IOPCIDevice</string>         <key>aty_config</key>          <dict>                 <key>CFG_NO_PP</key>                  <false/>                  <key>CFG_PAA</key>                  <integer>0</integer>                  <key>CFG_USE_USCN</key>                  <false/>          </dict>          <key>aty_properties</key>          <dict>                  <key>PP_GFXClockGatingEnabled</key>                  <integer>1</integer>          </dict> </dict> Et pour ATIRadeonX2000.kext
      <key>ATIRadeonX2000</key> <dict>         <key>ATIEnableWideBlitSupport</key>         <true/> <key>ATIUseTearingWideBlit</key> <false/> <key>CFBundleIdentifier</key> <string>com.apple.ATIRadeonX2000</string> <key>GpuDebugPolicy</key> <integer>0</integer> <key>IOCFPlugInTypes</key> <dict> <key>ACCF0000-0000-0000-0000-000a2789904e</key> <string>ATIRadeonX2000GA.plugin</string> </dict> <key>IOClass</key> <string>ATIRadeonX2000</string> <key>IODVDBundleName</key> <string>ATIRadeonX2000VADriver</string> <key>IOKitDebug</key> <integer>0</integer> <key>IOMatchCategory</key> <string>IOAccelerator</string> <key>IOPCIMatch</key> <string>0x94001002 0x94011002 0x94021002 0x94031002 0x95811002 0x95831002 0x95881002 0x94c81002 0x94c91002 0x95001002 0x95011002 0x95051002 0x95071002 0x95041002 0x95061002 0x95981002 0x94881002 0x95991002 0x95911002 0x95931002 0x94401002 0x94421002 0x944A1002 0x945A1002 0x94901002 0x949E1002 0x94801002 0x95401002 0x95411002 0x954E1002 0x954F1002 0x95521002 0x95531002 0x94a01002</string> <key>IOProviderClass</key> <string>IOPCIDevice</string> <key>IOSourceVersion</key> <string>8.24.11</string> <key>IOVARendererID</key> <integer>16908288</integer> <key>sensor-properties</key> <array> <dict> <key>device_type</key> <data> Z3B1LXNlbnNvcg== </data> <key>location</key> <string>GPU</string> <key>name</key> <string>gpu-sensor</string> <key>polling-period</key> <data> AAAAAQAAAAA= </data> <key>reg</key> <data> AAAAAg== </data> <key>sample-period</key> <data> AAAAAACYmAA= </data> <key>sensor-id</key> <data> AAAABg== </data> <key>version</key> <data> AAAAAg== </data> <key>zone</key> <data> AAAAAg== </data> </dict> </array </dict>  
      Et voici donc l'Info.plist de FakeSMC.kext dans son intégrité, vous pouvez jeter un oeil, histoire de voir à quoi cela ressemble :
       
      FakeSMC_Info.plist.zip
       
      Et pour les moins casse-têtes, voici FakeSMC.kext modifié que j'utilise pour charger les 2 kexts :
       
      FakeSMC.kext.zip
       
       
      Voilà, avec ceci, vous n'aurez plus besoin de savoir si oui ou non les kexts sont dans le kernelcache.
       
       
      Crédits attribués à :
       
      netkas  pour son incontournable QE_CI Exotic patch (même s'il n'importe plus son support)
       
      Slice  & co. pour leur bébé nommé Clover
       
      dmazar  pour son astuce avec FakeSMC.kext   (pour plus d'info, voir ici)
       
      duffs (rarement ici, plus sur le site de netkas) pour son astuce de comment patcher la partie binaire avec Clover, ce fût lors de la sortie de OS X Mavericks DP1
       
      nyolc8  pour le support de QE_CI Exotic patch pour Mavericks
       
      fantomas1  pour ......... pour ... quoi déjà ? Ah ben non ... non ... pour rien ...
    • By Slice
      Now I want to add vector graphics support in Clover. See rev 4560 and later.
      It is not working yet but designers may begin to create Vector Themes.
      It supposed to consist of SVG elements and has design size. It will be rendered to any screen size scaled from design size.
       
      What application in macOS can create SVG graphics?
      Inkscape is not working in macOS 10.11+. Pity.
      LibreOffice Draw works with SVG but buggy.
      Boxy SVG cost 10$ but looks good enough. It creates the best in simplicity files and have more then enough features.
      Illustrator is good but expensive.
       
      How to improve SVG file?
      Clover has restricted support for SVG. It is your job to make compatible file and as small as possible to speedup rendering.
      Some helps:
      Help:Inkscape – From invalid to valid SVG Inkscape files
      From invalid to valid SVG Adobe Illustrator files
      From invalid to valid SVG files of other editors: BKchem, ChemDraw and CorelDRAW
      Help:Illustrator – Assistance with creating and saving SVG images in Adobe Illustrator that will pass W3C validation
      User:Quibik/Cleaning up SVG files manually
      Later I will write own instructions specific to Clover abilities.
       
      How to create SVG fonts?
      You can google to find ready-to-use SVG fonts.  I found some problems with too beaty fonts: slow rendering and overflow crash. Be careful.
      You can get ttf or otf fonts and convert them into svg by using online WEB services. Not a problem to google.
      But then I want to find a way to simplify the font to reduce a size and speedup rendering.
      You can create own font by FontForge It is opensource and available for Windows, Mac and GNU+Linux. It creates otf font which you can convert to svg font.
       
       
    • By ErmaC
      Please be advised that this is not a discussion topic.
       

      This topic is a "direct" line of communication between the Developers of Clover (Clover Team).
      Unless a Developer/Coder asks for more information, all the critical information of a post should be contained in the subject and first post.
      Every post will be responded to in some fashion before being locked.
       
       
       
       

      Invalid Posts
      Since we are strictly interested in issue reports on this topic, the following post/reply are likely to be deleted immediately:
      1. Discussion topic aka OFF-TOPIC (What do you all think?)
      2. Invalid issue reports
      3. Feedback / Suggestion threads.
      4. Posts requesting information about the bootloader.
      5. Posts made on other forums (Don't spam.)
      6. "Accomplishment" threads, threads to advertise screenshots unrelated to bug reports.
      7. Posts requesting status updates on existing issues.
       
       
×