Jump to content
Kogen Mantis

Lenovo ThinkPad T420 with UEFI Only

4,160 posts in this topic

Recommended Posts

hmm. ok. well it seems to work for many of us on T420. if i use the built-in EDID i get lots of glitches and buffer hangs. as soon as i use/inject this EDID - zero glitch - zero hangs.  sorry it does not work for you.

Share this post


Link to post
Share on other sites
Advertisement

hmm. ok. well it seems to work for many of us on T420. if i use the built-in EDID i get lots of glitches and buffer hangs. as soon as i use/inject this EDID - zero glitch - zero hangs.  sorry it does not work for you.

can you send me your clover config plist for boot?

Share this post


Link to post
Share on other sites

@AJ 

 

1)  /.IAbootfiles  or something like this is created by the installer on the OS partition you were upgrading by the Install OSX.app ...  if you have HFSplus.efi vs Vboxhfs.efi in your clover drivers folder, then clover can boot from this installer bundle upon reboot. (just like a real mac)

 

since you aborted the install process by not restarting using this bundle, you can get rid of this folder now.

 

2) the installer will create (or update) the recovery partition - which is a 650MB partition on your OS HD. ( i would keep this.)

Thank you guys. I have deleted the .IABootfiles and the "Install Mavericks from..." is no longer there, good.

 

And for the recovery partition, it is actually there. The problem is that it doesn't boot, it complains about the AppleHDA kext. I'm trying to install the modified kexts to the BaseSystem.dmg that is in the recovery partition to see if I can boot from it. It would be useful in case of problems.

I used the following command from terminal to enable debug mode in Disk Utility and view/mount hidden partitions from the debug menu:

defaults write com.apple.DiskUtility advanced-image-options -bool true

 

Once mounted, I have converted the read-only .dmg into a read-write, applied the custom kexts using Kext Wizard, then converted .dmg into a compressed .dmg, and replaced the BaseSystem.dmg into the Recovery Partition. It almost boots now... still looking at it...

Share this post


Link to post
Share on other sites

@aj - there is a much easier way to boot recovery partition!!! it is essentially the same thing as the USB installer - which requires extra kexts.

 

so stop at clover GUI

use clover shell to rename OEM so it's not in play for this and boot recoveryHD using the top level config.plist which will inject (custom) kexts from 10.9 

 

shell commands
 

map fs0

fs0:

cd /EFI/CLOVER

mv OEM OEM.NU

exit

Share this post


Link to post
Share on other sites

@aj - there is a much easier way to boot recovery partition!!! it is essentially the same thing as the USB installer - which requires extra kexts.

 

so stop at clover GUI

use clover shell to rename OEM so it's not in play for this and boot recoveryHD using the top level config.plist which will inject (custom) kexts from 10.9 

 

shell commands

 

map fs0

fs0:

cd /EFI/CLOVER

mv OEM OEM.NU

exit

hehe, that seems easier... indeed... I will try it...

Share this post


Link to post
Share on other sites

take 2 on EDID HD3000 fix.

 

OK this theory is working in practice!  Theory: bogus panel size was the culprit

 

I changed just the panel size from 309x174 to 310x174. I can't get a glitch/hang on 10.8.5 or 10.9.0 using this edited EDID info.

It was NOT sync sizes as i originally thought - that attempt eventually hung.

 

tetonne - your EDID seems to be 309x173? maybe if i gen one that has 310x174 for 1366x768 resolution? i will post a new one test EDID later.

i noticed these EDIDs (mine too) specify a max size to be 310x170 but the panel was set to be only 309mm... it stands to reason the max cannot be bigger than the panel!

 

more info from revised post             #629            

Share this post


Link to post
Share on other sites

take 2 on EDID HD3000 fix.

 

OK this theory is working in practice!  Theory: bogus panel size was the culprit

 

I changed just the panel size from 309x174 to 310x174. I can't get a glitch/hang on 10.8.5 or 10.9.0 using this edited EDID info.

It was NOT sync sizes as i originally thought - that attempt eventually hung.

 

tetonne - your EDID seems to be 309x173? maybe if i gen one that has 310x174 for 1366x768 resolution? i will post a new one test EDID later.

i noticed these EDIDs (mine too) specify a max size to be 310x170 but the panel was set to be only 309mm... it stands to reason the max cannot be bigger than the panel!

 

more info from revised post             #629            

@tluck "EDID seems to be 309x173?" I don't know (don't understand in fact)

send me the new edid when it's created, i'll test and feed back. :)

Share this post


Link to post
Share on other sites

@tluck, could you generate an EDID with that panel size for 1600x900? I tried all the EDIDs so far (except the one in post #629) and I'm still getting hangs and glitches (though rarely). I'm also on 1600x900.

Share this post


Link to post
Share on other sites

take 2 on EDID HD3000 fix.

 

OK this theory is working in practice!  Theory: bogus panel size was the culprit

 

I changed just the panel size from 309x174 to 310x174. I can't get a glitch/hang on 10.8.5 or 10.9.0 using this edited EDID info.

It was NOT sync sizes as i originally thought - that attempt eventually hung.

 

tetonne - your EDID seems to be 309x173? maybe if i gen one that has 310x174 for 1366x768 resolution? i will post a new one test EDID later.

i noticed these EDIDs (mine too) specify a max size to be 310x170 but the panel was set to be only 309mm... it stands to reason the max cannot be bigger than the panel!

 

more info from revised post             #629            

Can you generate a new edid for 1600x900? And explain which parts(number) to change?

Thanks i ll try

 

i have already tried your edid with 36AE10 but no luck, always glitch

Share this post


Link to post
Share on other sites

@honeywell - see post 629 ... and the clover bundle has this same working (for me ?!) EDID for 1600x900.  the OEM 1600.900 config.plist is set up to inject the EDID and i also put in the DSDT (for non-clover).

 

... i don't know why this particular EDID works for me (and others ) but not for all.  

 

if you are NOT injecting this EDID (with product 2e2) , then please run : ioreg -l |grep EDID and post the EDID - maybe we can make sense of it and get a working one. 

Share this post


Link to post
Share on other sites

@yum - i will look at this post.  but I already have LCD brightness (16 levels)

 

so i took at look at  your ioreg EDID dump. and the first thing i noticed is you have 1600x900 but its on a 17" vs 14" so here is an EDID that you could try that has the same info - but i tweaked the params slightly (changed) to match the values work for me but with proper sizing.

 

see 4 value changes on line 50

 

your EDID

post-954945-0-86085500-1383763286_thumb.png

 

new EDID to test - take string below and put in Clover config.plist

post-954945-0-81117500-1383763300_thumb.png

 

 

00FFFFFFFFFFFF000DAF19170000000005130103802716780A08059D58539729155054000000010101010101010101010101010101018025408060841A30302035007ED710000018000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004C

 

                          DDCTest For: CMO 
______________________________________________________________________
______________________________________________________________________
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  27  16  78  0A  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  80  25  40  80  60  84
 60  |  1A  30  30  20  35  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  00  00  00  00  00  00  00
100  |  00  00  00  00  00  00  00  00  00  00
110  |  00  00  00  00  00  00  00  00  00  00
120  |  00  00  00  00  00  00  00  4C
______________________________________________________________________
(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 ________________    =  390 mm
(22)     Maximum Vertical Image Size __________________    =  220 mm
(23)     Display Gamma ________________________________    =  2.20
(24)     Power Management and Supported Feature(s):
         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: 96.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: 128 pixels
         Sync Offset: 48 pixels            Sync Pulse Width: 32 pixels
         Border: 0 pixels                  Frequency: 55.56 KHz
 
Vertical:
         Active Time: 900 lines            Blanking Time: 26 lines
         Sync Offset: 3 lines              Sync Pulse Width: 5 lines
         Border: 0 lines                   Frequency: 60.00 Hz
 
Digital Separate, Horizontal Polarity (-) Vertical Polarity (-)
 
 
______________________________________________________________________
(72-89) Detailed Timing / Descriptor Block 2:
 
         
 
 
(126)    
(127)    
 

Share this post


Link to post
Share on other sites

 

00FFFFFFFFFFFF000DAF19170000000005130103802716780A08059D58539729155054000000010101010101010101010101010101018025408060841A30302035007ED710000018000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004C

 

i try it but with out surprise 1600 goes outside of my screen ;)

resolution is preferences/Screen are not as good as the one i have with 00FFFFFF FFFFFF00 06AF3C31 00000000 00140103 801F1178 0A10B697 58579226 1E505400 00000101 01010101 01010101 01010101 0101121B 56465000 23303020 360035AD 10000018 0000000F 00000000 00000000 00000000 00200000 00FE0041 554F0A20 20202020 20202000 000000FE 00585858 58585858 58585831 200A0023 

and /S/L/Display/Over.. config (see a previous post i send with my config (I use dualink 0)

@tluck could u please try your customize with the EDID i'm using ;)

DisplayVendorID-6af/DisplayProductID-313c

Share this post


Link to post
Share on other sites

@tetonne

- that EDID is only for YUM (or others) with 17" LCD 1600x900!

 

are you getting glitches or hangs with your default/built-in EDID? you have 1366x768 native LCD?

 

here one for you with just the panel size changed - for 14" 1366x768. from 309x173 to 310x174mm

 

00FFFFFFFFFFFF0006AF3C310000000000140103801F11780A10B597585792261E505400000001010101010101010101010101010101121B5646500023302616360036AE10000018000000000000000000000000000000000000000000FE0031333636783736380A2020202000000000000000000000000000000000000000A6  

 

 

                            Time:  13:33:08
                        Date:  Tue Nov 05, 2013
______________________________________________________________________
______________________________________________________________________
                        VIEWSONIC CORPORATION
                    EDID Version # 1,  Revision # 3
                          DDCTest For: AUO 
______________________________________________________________________
______________________________________________________________________
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  06  AF
 10  |  3C  31  00  00  00  00  00  14  01  03
 20  |  80  1F  11  78  0A  10  B5  97  58  57
 30  |  92  26  1E  50  54  00  00  00  01  01
 40  |  01  01  01  01  01  01  01  01  01  01
 50  |  01  01  01  01  12  1B  56  46  50  00
 60  |  23  30  26  16  36  00  36  AE  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  33  36  36  78
100  |  37  36  38  0A  20  20  20  20  00  00
110  |  00  00  00  00  00  00  00  00  00  00
120  |  00  00  00  00  00  00  00  A6
______________________________________________________________________
(08-09)  ID Manufacturer Name ________________  = AUO
(11-10)  Product ID Code _____________________  = 313C(<1)
(12-15)  Last 5 Digits of Serial Number ______  = Not Used
(16)     Week of Manufacture _________________  = 00
(17)     Year of Manufacture _________________  = 2010
(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 ________________    =  310 mm
(22)     Maximum Vertical Image Size __________________    =  170 mm
(23)     Display Gamma ________________________________    =  2.20
(24)     Power Management and Supported Feature(s):
         Preferred Timing Mode
         Display Type = R/G/B Color
(25-34)  CHROMA INFO:
         Red X - 0.590 Green X - 0.340 Blue X - 0.150 White X - 0.313
         Red Y - 0.345 Green Y - 0.570 Blue Y - 0.120 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:
                   1366x768  Pixel Clock: 69.30 MHz
______________________________________________________________________
         Horizontal Image Size: 310 mm     Vertical Image Size: 174 mm
         Refreshed Mode: Non-Interlaced    Normal Display - No Stereo
 
Horizontal:
         Active Time: 1366 pixels          Blanking Time: 70 pixels
         Sync Offset: 38 pixels            Sync Pulse Width: 22 pixels
         Border: 0 pixels                  Frequency: 48.26 KHz
 
Vertical:
         Active Time: 768 lines            Blanking Time: 35 lines
         Sync Offset: 3 lines              Sync Pulse Width: 6 lines
         Border: 0 lines                   Frequency: 60.10 Hz
 
Digital Separate, Horizontal Polarity (-) Vertical Polarity (-)
 
 
______________________________________________________________________
(72-89) Detailed Timing / Descriptor Block 2:
 
         
 
 
______________________________________________________________________
(90-107) Detailed Timing / Descriptor Block 3:
 
         ASCII Data:
         1366x768
 
 
______________________________________________________________________
(108-125) Detailed Timing / Descriptor Block 4:

Share this post


Link to post
Share on other sites

 

are you getting glitches or hangs with your default/built-in EDID? you have 1366x768 native LCD?

 

00FFFFFFFFFFFF0006AF3C310000000000140103801F11780A10B597585792261E505400000001010101010101010101010101010101121B5646500023302616360036AE10000018000000000000000000000000000000000000000000FE0031333636783736380A2020202000000000000000000000000000000000000000A6  

No glitches or hangs on my 1600x900 and 1376x768 with dualink 0 (dualink 1 doesn't work here)

but better customs are welcomed :)

 

I test the EDID provided 

my feed back here :

 

post-638501-0-90722100-1383768364_thumb.jpg

One more thing : Thanks tluck

Share this post


Link to post
Share on other sites

@tluck, thanks for your hard work on this, it's appreciated really.  I have the same edie like yum, i have controlled it by yum link in some previous post. I think that also laptop is probably same family with same screen 1600x900 on 17 inch. 

So i try your custom edie, i have past it directly in display/overrides and it is seen correctly but i have always artifacts, after 2-3 reboot or something of similar. Problem for me is still unsolved for now. I can try other if you have other ideas. I think that will be same for iim cause original edie is the same. 

But why all this is happen on clover instead on chameleon (and/or smcping daemon) there is not this artifacts problem?

Btw thanks 

Share this post


Link to post
Share on other sites

@Smith@@ - how are you injecting the EDID? i found that putting one in /S/L/Displays/Overrides does not actually override the built-in EDID! However, I found that if I put a new/different EDID in the DSDT or inject by clover then the system will use it. it seems that if the system can find one in the LCD hardware, it will use it versus use one in an Override file.

 

I have been trying to figure out what is special about the EDID that works for me versus the built-in. i don't know why my built-in EDID is glitchy but an alternative EDID is absolutely perfect. And i had glitches on Chameleon/MBR before i switched to Clover. 

Share this post


Link to post
Share on other sites

@tluck i think that your theory about override is right because with same edid in previous post, that for yum (my model is in fact exactly the same), if i override it in display/overrides and so in vanilla method, i see in profiler that name is correct (LCD HP in this case) but override is probably not complete, if instead use the same last edie in clover i have completely black screen after all loading verbose end screen begin always more bright, it throb, vibrates and then nothing.

 

So i think that i must try all from clover. Can you make a new edie for testing? ;)

 

Ed: i have another question, now i have injected original edid with clover. But The COMMENT in graphics setting, in this case i choose "GLITCHES?" is different from name in monitor profiler, i mean, name is taken always from original override in Display/Overrides. But i think that clover EDID is working cause with previous edid had black screen with original not. But about name is right? There should be also an override of COMMENT parameter from clover?

Share this post


Link to post
Share on other sites

@tluck i think that your theory about override is right because with same edid in previous post, that for yum (my model is in fact exactly the same), if i override it in display/overrides and so in vanilla method, i see in profiler that name is correct (LCD HP in this case) but override is probably not complete, if instead use the same last edie in clover i have completely black screen after all loading verbose end screen begin always more bright, it throb, vibrates and then nothing.

 

So i think that i must try all from clover. Can you make a new edie for testing? ;)

 

Ed: i have another question, now i have injected original edid with clover. But The COMMENT in graphics setting, in this case i choose "GLITCHES?" is different from name in monitor profiler, i mean, name is taken always from original override in Display/Overrides. But i think that clover EDID is working cause with previous edid had black screen with original not. But about name is right? There should be also an override of COMMENT parameter from clover?

Yup, it's same DV7 hp ;)  

 

@tluck, thanks so much for all help. I have done same smith@@ tries and result is the same. Now i'm starting to inject the edid directly from clover. I will test your other edid

Share this post


Link to post
Share on other sites

@Smith@@ and Yum

 

this is what you need to put in your config.plist - it this is a modified EDID (detailed timing section) but has the same product/vendor.

 

<key>Graphics</key>

<dict>

<key>Comment</key>

<string>HP 17" 1600x900</string>

<key>CustomEDID</key>

<data>

AP///////wANrxkXAAAAAAUTAQOAJxZ4CggFnVhTlykVUFQAAAABAQEBAQEB

AQEBAQEBAQEBgCVAgGCEGjAwIDUAftcQAAAYAAAAAAAAAAAAAAAAAAAAAAAA

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEw=

</data>

<key>DualLink</key>

<string>1</string>

<key>Inject</key>

<dict>

<key>Intel</key>

<true/>

</dict>

<key>InjectEDID</key>

<true/>

</dict>

Share this post


Link to post
Share on other sites

@Smith@@ and Yum

 

this is what you need to put in your config.plist - it this is a modified EDID (detailed timing section) but has the same product/vendor.

 

Graphics

Comment

HP 17" 1600x900

CustomEDID

AP///////wANrxkXAAAAAAUTAQOAJxZ4CggFnVhTlykVUFQAAAABAQEBAQEB

AQEBAQEBAQEBgCVAgGCEGjAwIDUAftcQAAAYAAAAAAAAAAAAAAAAAAAAAAAA

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEw=

DualLink

1

Inject

Intel

InjectEDID

 

In test, but i see already one artifact, but still in testing.  But before question, i should see this: HP 17" 1600x900 in System Preferences --> Monitor --> Colors ?

 

Or not, because seems that name is not override correctly..

 

Edit: artifacts again.. :(     but i don't understand about before question, if edie is override correctly

Share this post


Link to post
Share on other sites

Maybe chameleon and clover read something in different way. Common problem is artifacts on clover and more less (avoid totally with smcping daemon) on chameleon. If i can understand what is that "something", but honestly i have done practically every form of tries LOL

 

 

Can be also my 16 GB of ram, but i had the same problem also with 8. On mavericks then patch intel kext for "downgrade" gram is not work. It see for intel always 512 MB of ram

Share this post


Link to post
Share on other sites

No glitches or hangs on my 1600x900 and 1376x768 with dualink 0 (dualink 1 doesn't work here)

but better customs are welcomed :)

 

I test the EDID provided 

my feed back here :

 

attachicon.gifnull

One more thing : Thanks tluck

Can you post me your ML intel kext, frame buffer an hd3000? I am on mavericks but i want do a try..

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

  • 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.
       
       
×