Jump to content
Kogen Mantis

Lenovo ThinkPad T420 with UEFI Only

4,163 posts in this topic

Recommended Posts

@smith@@ - well here is a generated EDID 17" 1600x900 you could try. i took your EDID and then plugged in the timings from my EDID keeping your panel sizes for 17" .

 

00FFFFFFFFFFFF000DAF1917000000000513010380261678EA08059D5853972915505400000001010101010101010101010101010101F82A409A61840C30402A33007ED710000018000000000000000000000000000000000000000000FE003137222031363030783930300A0000000000000000000000000000000000000041

__________________________________________________________________________________________
EDID Block 0, Bytes 0-127
128 BYTES OF EDID CODE:
         0   1   2   3   4   5   6   7   8   9
      ________________________________________
  0  |  00  FF  FF  FF  FF  FF  FF  00  0D  AF
 10  |  19  17  00  00  00  00  05  13  01  03
 20  |  80  26  16  78  EA  08  05  9D  58  53
 30  |  97  29  15  50  54  00  00  00  01  01
 40  |  01  01  01  01  01  01  01  01  01  01
 50  |  01  01  01  01  F8  2A  40  9A  61  84
 60  |  0C  30  40  2A  33  00  7E  D7  10  00
 70  |  00  18  00  00  00  00  00  00  00  00
 80  |  00  00  00  00  00  00  00  00  00  00
 90  |  00  00  00  FE  00  31  37  22  20  31
100  |  36  30  30  78  39  30  30  0A  00  00
110  |  00  00  00  00  00  00  00  00  00  00
120  |  00  00  00  00  00  00  00  41
______________________________________________________________________
(08-09)  ID Manufacturer Name ________________  = CMO
(11-10)  Product ID Code _____________________  = 1719
(12-15)  Last 5 Digits of Serial Number ______  = Not Used
(16)     Week of Manufacture _________________  = 05
(17)     Year of Manufacture _________________  = 2009
(10-17)  Complete Serial Number ______________  = See Descriptor Block
(18)     EDID Version Number _________________  = 1
(19)     EDID Revision Number ________________  = 3
(20)     VIDEO INPUT DEFINITION:
         Digital Signal
         Non - VESA DFP 1.x Compatible                        
                        
(21)     Maximum Horizontal Image Size ________________    =  380 mm
(22)     Maximum Vertical Image Size __________________    =  220 mm
(23)     Display Gamma ________________________________    =  2.20
(24)     Power Management and Supported Feature(s):
         Stand-By, Suspend, Active Off/Very Low Power, 
         Preferred Timing Mode
         Display Type = R/G/B Color
(25-34)  CHROMA INFO:
         Red X - 0.613 Green X - 0.326 Blue X - 0.160 White X - 0.313
         Red Y - 0.344 Green Y - 0.590 Blue Y - 0.082 White Y - 0.329
(35)     ESTABLISHED TIMING I:
(36)     ESTABLISHED TIMING II:
(37)     Manufacturer's Reserved Timing:
           None Specified
(38-53)  Standard Timing Identification:
         Not Used
         Not Used
         Not Used
         Not Used
         Not Used
         Not Used
         Not Used
         Not Used
______________________________________________________________________
(54-71) Detailed Timing / Descriptor Block 1:
                  1600x900  Pixel Clock: 110.00 MHz
______________________________________________________________________
         Horizontal Image Size: 382 mm     Vertical Image Size: 215 mm
         Refreshed Mode: Non-Interlaced    Normal Display - No Stereo
 
Horizontal:
         Active Time: 1600 pixels          Blanking Time: 410 pixels
         Sync Offset: 64 pixels            Sync Pulse Width: 42 pixels
         Border: 0 pixels                  Frequency: 54.73 KHz
 
Vertical:
         Active Time: 900 lines            Blanking Time: 12 lines
         Sync Offset: 3 lines              Sync Pulse Width: 3 lines
         Border: 0 lines                   Frequency: 60.01 Hz
 
Digital Separate, Horizontal Polarity (-) Vertical Polarity (-)
 
 
______________________________________________________________________
(72-89) Detailed Timing / Descriptor Block 2:
 
         
 
 
______________________________________________________________________
(90-107) Detailed Timing / Descriptor Block 3:
 
         ASCII Data:
         17" 1600x900
 
 
______________________________________________________________________
(108-125) Detailed Timing / Descriptor Block 4:
 
         
 
 
(126)    
(127)                       

Share this post


Link to post
Share on other sites
Advertisement

Dear Tluck

 

How to convert EDID hex format

 

00FFFFFFFFFFFF000DAF1917000000000513010380261678EA08059D5853972915505400000001010101010101010101010101010101F82A409A61840C30402A33007ED710000018000000000000000000000000000000000000000000FE003137222031363030783930300A0000000000000000000000000000000000000041

 

To format like below :

 

AP///////wANrxkXAAAAAAUTAQOAJxZ4CggFnVhTlykVUFQAAAABAQEBAQEB

AQEBAQEBAQEBgCVAgGCEGjAwIDUAftcQAAAYAAAAAAAAAAAAAAAAAAAAAAAA

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEw=

 

Thanks you Tluck

 

Share this post


Link to post
Share on other sites

Dear Tluck

 

How to convert EDID hex format

 

To format like below :

 

Thanks you Tluck

Done...

This is from plist editor pro :)

Thank you all

Share this post


Link to post
Share on other sites

Looks good @tluck.

I will try it later.

Unfortunately my sleep does not work well. I thought it's fixed but now it just freezes sometimes. Also after some sleeps my Touchpad/Trackpoint are getting in responsive. :/

Using an USB drive to boot does not look like a solution to me, I don't want to always carry it with me. :/

Share this post


Link to post
Share on other sites

 

@smith@@ - well here is a generated EDID 17" 1600x900 you could try. i took your EDID and then plugged in the timings from my EDID keeping your panel sizes for 17" .

 

00FFFFFFFFFFFF000DAF1917000000000513010380261678EA08059D5853972915505400000001010101010101010101010101010101F82A409A61840C30402A33007ED710000018000000000000000000000000000000000000000000FE003137222031363030783930300A0000000000000000000000000000000000000041

 

Thanks the same buddy, many appreciated ;)

Share this post


Link to post
Share on other sites

@vapayo

 

yeah the random sleep and wake issues seem to be attributed to pure UEFI boot. That's why i boot with MBR formatted USB when i need to rely on sleep. 

 

@smith@@ 

 

here is 2 more for a hp 17" 1600x900 - if you are interested

the first one has slight increase max panel size to 390 which is larger that what detailed size calls for - 382.

 

00FFFFFFFFFFFF000DAF1917000000000513010380271678EA08059D5853972915505400000001010101010101010101010101010101622A404061842A30302035007ED710000019000000000000000000000000000000000000000000FE003137222031363030783930300A0000000000000000000000000000000000000029

 

00FFFFFFFFFFFF000DAF1917000000000513010380261678EA08059D5853972915505400000001010101010101010101010101010101622A404061842A30302035007ED710000019000000000000000000000000000000000000000000FE003137222031363030783930300A000000000000000000000000000000000000002A

 

EDID Block 0, Bytes 0-127
128 BYTES OF EDID CODE:
         0   1   2   3   4   5   6   7   8   9
      ________________________________________
  0  |  00  FF  FF  FF  FF  FF  FF  00  0D  AF
 10  |  19  17  00  00  00  00  05  13  01  03
 20  |  80  26  16  78  EA  08  05  9D  58  53
 30  |  97  29  15  50  54  00  00  00  01  01
 40  |  01  01  01  01  01  01  01  01  01  01
 50  |  01  01  01  01  62  2A  40  40  61  84
 60  |  2A  30  30  20  35  00  7E  D7  10  00
 70  |  00  19  00  00  00  00  00  00  00  00
 80  |  00  00  00  00  00  00  00  00  00  00
 90  |  00  00  00  FE  00  31  37  22  20  31
100  |  36  30  30  78  39  30  30  0A  00  00
110  |  00  00  00  00  00  00  00  00  00  00
120  |  00  00  00  00  00  00  00  2A
______________________________________________________________________
(08-09)  ID Manufacturer Name ________________  = CMO
(11-10)  Product ID Code _____________________  = 1719
(12-15)  Last 5 Digits of Serial Number ______  = Not Used
(16)     Week of Manufacture _________________  = 05
(17)     Year of Manufacture _________________  = 2009
(10-17)  Complete Serial Number ______________  = See Descriptor Block
(18)     EDID Version Number _________________  = 1
(19)     EDID Revision Number ________________  = 3
(20)     VIDEO INPUT DEFINITION:
         Digital Signal
         Non - VESA DFP 1.x Compatible                        
                        
(21)     Maximum Horizontal Image Size ________________    =  380 mm
(22)     Maximum Vertical Image Size __________________    =  220 mm
(23)     Display Gamma ________________________________    =  2.20
(24)     Power Management and Supported Feature(s):
         Stand-By, Suspend, Active Off/Very Low Power, 
         Preferred Timing Mode
         Display Type = R/G/B Color
(25-34)  CHROMA INFO:
         Red X - 0.613 Green X - 0.326 Blue X - 0.160 White X - 0.313
         Red Y - 0.344 Green Y - 0.590 Blue Y - 0.082 White Y - 0.329
(35)     ESTABLISHED TIMING I:
(36)     ESTABLISHED TIMING II:
(37)     Manufacturer's Reserved Timing:
           None Specified
(38-53)  Standard Timing Identification:
         Not Used
         Not Used
         Not Used
         Not Used
         Not Used
         Not Used
         Not Used
         Not Used
______________________________________________________________________
(54-71) Detailed Timing / Descriptor Block 1:
                  1600x900  Pixel Clock: 108.50 MHz
______________________________________________________________________
         Horizontal Image Size: 382 mm     Vertical Image Size: 215 mm
         Refreshed Mode: Non-Interlaced    Stereo
 
Horizontal:
         Active Time: 1600 pixels          Blanking Time: 320 pixels
         Sync Offset: 48 pixels            Sync Pulse Width: 32 pixels
         Border: 0 pixels                  Frequency: 56.51 KHz
 
Vertical:
         Active Time: 900 lines            Blanking Time: 42 lines
         Sync Offset: 3 lines              Sync Pulse Width: 5 lines
         Border: 0 lines                   Frequency: 59.99 Hz
 
Digital Separate, Horizontal Polarity (-) Vertical Polarity (-)
 
 
______________________________________________________________________
(72-89) Detailed Timing / Descriptor Block 2:
 
         
 
 
______________________________________________________________________
(90-107) Detailed Timing / Descriptor Block 3:
 
         ASCII Data:
         17" 1600x900

Share this post


Link to post
Share on other sites

Artifact with both last. I m starting to think that problem is efi emulation. It s only explanation.

Share this post


Link to post
Share on other sites

Hey,

 

after some time off from clover (happily running 10.8.4 on my x220 with chameleon) I was reading whether the UEFI boot issues with mute button and sleep were fixed, but I can see it is not the case.

 

@tluck: if you don't want to use a usb stick you can change your gpt to a hybrid disk and then use MBR clover from disk. unfortunately gpt windows won't work (gpt windows does not like hybrid MBR) in this setup so you need to use MBR windows as well (don't have windows at all currently).

 

I just had a look at your DSDT and will compare it with mine. Do you remember which changes were needed to make it compatible to AppleACPIPlatform.kext? I didn't find it mentioned in the comments.

 

Thanks and keep up the good work ;-)

Share this post


Link to post
Share on other sites

@miaumiau2 -  glad to have you back. Clover UEFI does have some quirks. Clover MBR is a different story - sleep and mute are fine. The ACPIplatform changes were about the Battery (as far as i canso i think if you look at _BIF etc for where i used the B1B2 function. i struggled with some really long strings (128 vs 8) so I had to hard code a few text strings for the manufacture, model, and battery type. 

 

usb is not a huge problem for me as i found a pretty compact USB - cruiser fit.

 

can you elaborate on how to convert a GTP to hybrid? do you mean put MBR instead of PBR? yeah i vaguely remember problems with windows when i was messing with this a while back. thanks.

Share this post


Link to post
Share on other sites

@tluck - Ok, will check if I find the battery stuff. currently I also have problems using rehabmans latest AcpiBattery so need to look at it anyways.

 

I used gdisk, you can install it in OSX, but I used http://gparted.sourceforge.net/livecd.php most of the time. See http://www.rodsbooks.com/gdisk/hybrid.html for general info on hybrid MBRs. As far as I recall, this is how Bootcamp makes a mac ready for Windows installation as well.

 

Once you have a hybrid mbr, you can install a MBR / PBR to it while keeping the disk in GPT and thus editable in DiskUtil.

 

Here is my layout. I actually did not manage to boot from /dev/disk1 where my main OSX resides so I boot via /dev/disk0 MBR -> /dev/disk0s1 PBR -> boot(Chameleon v2.2svn r2255)

 

post-1042507-0-62163400-1384383263_thumb.png

 

 

EDIT: oh and about going from pure GPT to hybrid, it is a non-destructive operation. Basically GPT fills the old MBR with a reserved data pattern, so that MBR tools don't damage any GPT disk. When having an hybrid, a valid MBR is added that points to the same partitions (but max 4, but OSX will still see all partitions as it uses the GPT, only MBR booted systems will see max 4). So you can safely add / remove the hybrid mbr without repartitioning, just Windows might because unbootable.

Share this post


Link to post
Share on other sites

my SMC_util3 -l
 

 

Num: b0=0 b1=0 b2=0 b3=21 size=4

#KEY [ui32] 33 (bytes 00 00 00 21)
FNum [ui8 ] 1 (bytes 01)
$Adr [ui32] 0 (bytes 00 00 03 00)
MSSD [si8 ] (bytes 05)
OSK0 [ch8*] (bytes 6f 75 72 68 61 72 64 77 6f 72 6b 62 79 74 68 65 73 65 77 6f 72 64 73 67 75 61 72 64 65 64 70 6c)
$Num [ui8 ] 1 (bytes 01)
REV [{rev] (bytes 01 68 0f 00 00 99)
RVBF [{rev] (bytes 01 30 0f 00 00 03)
RVUF [{rev] (bytes 01 30 0f 00 00 03)
ACID [ch8*] (bytes ba be 3c 45 c0 03 10 43)
DPLM [{lim] (bytes 00 00 00)
MSSP [si8 ] (bytes 05)
OSK1 [ch8*] (bytes 65 61 73 65 64 6f 6e 74 73 74 65 61 6c 28 63 29 41 70 70 6c 65 43 6f 6d 70 75 74 65 72 49 6e 63)
EPCI [ui32] 0 (bytes 05 b0 07 00)
RPlt [ch8*] (bytes 6b 36 32 00 00 00 00 00)
RBr [ch8*] (bytes 6b 36 32 00 00 00 00 00)
BEMB [flag] (bytes 01)
TZ0C [sp78] (bytes 34 00)
TC0D [sp78] (bytes 27 00)
TC1D [sp78] (bytes 28 00)
TCAD [sp78] (bytes 2e 00)
MlCP [fp88] (bytes 08 00)
CCPC [ui32] 24 (bytes 00 00 03 18)
PCPT [sp78] (bytes 07 69)
PCPC [sp78] (bytes 03 a0)
PCPG [sp78] (bytes 00 58)
TC0H [sp78] (bytes 34 00)
F0Ac [fpe2] 3234 (bytes 32 88)
F0ID [{fds] (bytes 01 00 04 00 53 79 73 74 65 6d 20 46 61 6e 00 00)
NTOK [ui8 ] 1 (bytes 01)
CLKT [ui32] 32 (bytes 00 01 13 20)
CLKH [{clh] (bytes 00 00 70 80 00 01 19 40)
F0Mx [ui16] 224 (bytes 60 e0)

SMC_util3.zip

Share this post


Link to post
Share on other sites

@Tetonne - did i miss something! ... what is the SMC_util info all about?

i don't think so truck ;)

i only share something i didn't know before

http://www.insanelymac.com/forum/topic/282794-darwindumper/

http://www.projectosx.com/forum/index.php?showtopic=2447&mode=linear

i share my information (without really understand them) cos i know some people will here lol

not sure it's important in fact cos i'm running a real mac under my T420 lol thanks to you and other great share found here :)

Share this post


Link to post
Share on other sites

 

no change. tried both edit 1 or edit 2.

 

 

Sep 27 11:50:05 localhost kernel[0]: AppleSmartBatteryManager::init: Initializing
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBatteryManager::probe: Probing
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBatteryManager::start: called
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBatteryManager: Version 1.40 starting
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBatteryManager: Battery Supported Count(s) 1.
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery: Using ACPI regular battery information method _BIF
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery::clearBatteryState: do_update = false
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery::rebuildLegacyIOBatteryInfo called
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery::pollBatteryState: path = 0x2
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery::pollBatteryState: path = 0x1
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBatteryManager::getBatterySTA called
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBatteryManager::setPowerState: which = 0x1
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery::setBatterySTA: battery_status = 0x1f
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBatteryManager::getBatteryBIF called
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBatteryManager::getBatteryBIF: validateObject return 0x0
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBatteryManager::getBatteryBIF: evaluateObject error 0xe00002bc
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBatteryManager::getBatteryBST called
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery::setBatteryBST: acpibat_bst size = 4
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery::setBatteryBST: fPowerUnit       = 0x0
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery::setBatteryBST: currentStatus    = 0x0
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery::setBatteryBST: fCurrentRate     = 0x0
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery::setBatteryBST: fCurrentCapacity = 0xa06e
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery::setBatteryBST: fCurrentVoltage  = 0x2f7a
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery::setBatteryBST: adjusted fCurrentRate = 0x0
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery::setBatteryBST: fAverageRate = 0x0
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery: Battery is charged.
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery::constructAppleSerialNumber called
Sep 27 11:50:05 localhost kernel[0]: AppleSmartBattery::rebuildLegacyIOBatteryInfo called
S

 

Hi,

 

Did you get it resolved. I have the same issue.

Do you have solution to this issue? Please let me know I the same problem

Share this post


Link to post
Share on other sites

@mdudnik

 

I don't understand what problem you are referring to?  as TimeWalker75a points out - that output is from the debug version of RehabMans Battery Manager kext that was extracted during the development of the T420 DSDT so we can use the Lion/MoutainLion/Mavericks AppleACPIPlatform.kext instead of the snow leopard rollback kext.

 

the answer is: yes. ... if the question is the DSDT fixed to work with the current AppleACPIPlatform and ACPIBatteryManager?


@TimeWalker75a

 

FWIW, since I have been booting CloverEFI from a MBR USB vs UEFI, I have had no problems with shutdown, sleep or random PS2 disappearance.  frankly, i don't know if the "SLPR" function fix is the key or not ... in _PTS, i added a bit toggle 1 for for modes mode 3, 4 and beyond the 0 for mode 5. ... this extra code certainly does not hurt! 

 

// tjl this is for sleep mode

            If (LEqual (Arg0, 0x03))

            {

                \VVPD (0x03)

                \TRAP ()

                Store (\_SB.PCI0.LPC.EC.ADP1._PSR (), \OCST)

                Store (0x01, SLPE)

                Sleep (0x10)

            }

 

// tjl this is for lid mode

            If (LEqual (Arg0, 0x04))

            {

                \_SB.SLPB._PSW (0x00)

                \TRAP ()

// tjl                \_SB.PCI0.LPC.TPM.CMOR ()

                \AWON (0x04)

                Store (0x01, SLPE)

                Sleep (0x10)

            }

 

// tjl this is for shutdown mode

            If (LEqual (Arg0, 0x05))

            {

                \TRAP ()

// tjl                \_SB.PCI0.LPC.TPM.CMOR ()

                \AWON (0x05)

// tjl - add 2 lines

                Store (0x00, SLPE)

                Sleep (0x10)

            }

Share this post


Link to post
Share on other sites
Hi community!

 

Trying to install 10.9 on Lenovo T530 (2392-4SG). I've disabled the discrete graphics so now HD4000 1920x1030 only. Added EDID into config.plist

I'm able to boot Clover (USB) and even get OS X Installer. The problem is the mouse cursor absent. Looks like HD4000 work wrong.

 

Thanks in advance if somebody may help me by any way.

 

Dmitry

Share this post


Link to post
Share on other sites

@dmitry Blinov - do you have VooddooPS2controller kext or other PS2 controller ? an external usb mouse can also work to get things installed. 

Share this post


Link to post
Share on other sites

@tluck - yes I have VoodooPS2controller and usb mouse (and touchpad) is really working, the problem with cursor only. Cursor is invisible  :blush:

(If it is important: I have not any DSDT.aml in the ACPI/Patched folder)

Share this post


Link to post
Share on other sites

@tluck - yes I have VoodooPS2controller and usb mouse (and touchpad) is really working, the problem with cursor only. Cursor is invisible  :blush:

(If it is important: I have not any DSDT.aml in the ACPI/Patched folder)

Try to boot with flag -x. You can also try to set the platform IG of framebuffer Capri to 3 or 4 (or try the other ones also). If this all does not work to get your system installed, remove the AppleInterFramebufferCapri.kext from your USB installer.(But keep ist, you will need it perhaps later on) For getting your system after install working with the HD4000 you need in any case the correct Capri platform IG.

 

Have fun.

Share this post


Link to post
Share on other sites

@dmitry - hmm. well did you try to look at system preferences/Accessibility/Display which you can change cursor size? 

Share this post


Link to post
Share on other sites

Try to boot with flag -x. You can also try to set the platform IG of framebuffer Capri to 3 or 4 (or try the other ones also). If this all does not work to get your system installed, remove the AppleInterFramebufferCapri.kext from your USB installer.(But keep ist, you will need it perhaps later on) For getting your system after install working with the HD4000 you need in any case the correct Capri platform IG.

 

Thanks, will try today (I hope)

 

@dmitry - hmm. well did you try to look at system preferences/Accessibility/Display which you can change cursor size? 

I don't think so, I still haven't OS X installed. Thanks anyway

Share this post


Link to post
Share on other sites

You can also try to set the platform IG of framebuffer Capri to 3 or 4 

 

 Yes!!!  Video at LCD now is working with platform 01660004  :thumbsup_anim:  Thanks a lot, styrian!

 

OS X 10.9 is installed, boot from USB stick still

 

System disk is SSD drive in Lenovo bay instead of DVD

 

Work:

  • HD4000 with all resolutions 
  • Built-in Ethernet
  • Built-in Webcam
  • Built-in Touchpad
  • USB mouse
  • iCloud
  • Messages

Doesn't work

  • Sound
  • Battery
  • Icon of SSD disk is yellow
  • Wi-Fi (it is ok, I understand why)

 

I guess first of all I have to install Clover to the system SSD. And next I should have a work with DSDT and/or kexts patching...

 

So can I ask you to help with my next steps?

 

 

Thanks again!

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 cvad
      Small tool to download, compile and build the latest Clover X64 package,
      possible include HFSPlus-64.efi.
       
       
       

      The script inside is editable.

       
      Enjoy...
       
      Many thanks to the comrade SunKi for help with creating the script.
       
       
       
       
       
      Best thanks - click "Rate File".
    • By gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  selezionate OsxAptioFixDrv-64
                             *  :Se nel vostro sistema è presente una scheda grafica (discreta) della serie 9xx nVidia selezionate OsxAptioFix2Drv-64 al posto di  OsxAptioFixDrv-64 *
      ** OsxAptioFix2Drv :E' necessario per poter impostare CsrActiveConfig= 0x3 **
      ***OsxAptioFix3Drv oppure AptioMemory --> (consigliato) devono essere usati su hardware Skylake o successivi perché permettono alla nvram di lavorare correttamente
           (mi raccomando o uno o l'altro)
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione
      nel caso guardate...
       Mojave in HFS 
       
       
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      apfs.efi-10.13-NoLog.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      apfs.efi-10.13.1-No_LOG.zip
      apfs.efi-10.13.2_No_Log.zip
      apfs.efi-10.13.3-No_Log.zip
      apfs.efi-10.13.4-No_Log.zip
      apfs.efi-10.13.5_No_Log.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip
    • 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.
       
       
×