Jump to content
fantomas1

Clover test and patches for Polaris GPU

279 posts in this topic

Recommended Posts

And one more thing. With WhateverGreen never turn on injection of ATI in the clover. Inject is evil. Use the properties in WhateverGreen

 

which are the properties in WhateverGreen that we can use?

Share this post


Link to post
Share on other sites
Advertisement

Polaris 12 = Lexa gpu

Clover work with him?

My hackintosh ever Give me this output

 

Dev os 0x699f1002

Set RadeonDeInit=YES in config.plist.

What is a market name of your card?

Share this post


Link to post
Share on other sites

My card is one Asus radeon rx550

A lot of fórum say that is one polaris 12 but when i search i discover one thing

Is a lexa chipset.

The id is 699f and i dont found notinhg in the kext with this id.

Look the clover source of Clover 4330 for this gpu the id is 67EF.

But my gpu dont load kext and stay with 5mb of ram

Share this post


Link to post
Share on other sites

My card is one Asus radeon rx550

A lot of fórum say that is one polaris 12 but when i search i discover one thing

Is a lexa chipset.

The id is 699f and i dont found notinhg in the kext with this id.

Look the clover source of Clover 4330 for this gpu the id is 67EF.

But my gpu dont load kext and stay with 5mb of ram

You may set FakeID=0x67EF1002 and FixDispaly=YES

Share this post


Link to post
Share on other sites

I tried this and it did not work

I also tried all fakeids from AMD and none made the board to be loaded.

no kext is loaded

 

I try fakeid and load vbios and nothing

FakeID will work only with DSDT FixDisplay.

Share this post


Link to post
Share on other sites

RX 550 don't work in macOS at all... 

 

True, I tested it over and over but nothing worked, fake ID, edit of every possible info.plist for controller and accelerator kexts + HW kexts, added vbios to Clover ROM folder and Load vBios.   Nothing got more than Display status 7mb.   It has half the CUs of the RX 560, lower ram frequency and lower GPU frequency.    It just would not take no matter what I tried in High Sierra and HS betas as well.    Maybe if someone rewrote the controller and accelerator + HW kexts for the card it would work but that would be a very large project for a little card.     

Share this post


Link to post
Share on other sites

Update:   There is a new version of the RX 550 that has the device ID 0x67FF1002 but it is very specific as far as a brand and model number.    I will try to find it and link it later.   It has the RX 560 ID but has lower Compute Units count so it may work.    

This is it a Sapphire RX 500 based on Polaris 21 similar to RX 560.

https://www.techpowerup.com/241121/sapphire-intros-radeon-rx-550-graphics-cards-with-640-stream-processors

Edited by Gigamaxx

Share this post


Link to post
Share on other sites
13 minutes ago, telepati said:

Guys, is RX 560 working with 10.13.4 or not? I just recently ordered it. If it's not working I will cancel my order? 

It wil work

Share this post


Link to post
Share on other sites
1 minute ago, telepati said:

Probably it will deliver tomorrow which setting should I need?

If you are going to use WhateverGreen you won't be needing anything, just lilu and the WhateverGreen kexts. make sure to use the latest versions.

Share this post


Link to post
Share on other sites

Hi Folks,

 

I have a Dell T3500 with a Xeon W3690 and a Gigabyte Radeon RX 560 Gaming OC 4G running under High Sierra 10.13.6.

 

Unfortunately any attempt to upgrade to Mojave, boot its installer, or indeed install the "Security Update 2018-003 10.3.6" fails, reporting a failure to access the GPU card.

 

A verbose boot using "-v debug=0x8 serial=1" bootargs allows me to log the output to another machine. It can been seen in the log extract below that there is an attempt to access a register at 0xc0500198 and Googling this number has led me to this thread, specifically HERE. I've tried running the RadeonDump2 utility, but I just get all zeroes under 10.13.6, however that number is clearly still lurking in there somewhere!

 

I have the GPU card named PSX1 as per the recommendation HERE as I have SMBIOS set to MacPro5,1. Setting to any other name doesn't have any effect.

 


[AGPM Controller] build gpuDict by GPU PSX1.
IOConsoleUsers: time(0) 0->0, lin 0, llk 1, 
IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0
GTrace EDncablnicrtio -point 5
Invalid Register Offset: 0xc0500198 >= 0x40000.
Invalid Register Offset: 0xc0500198 >= 0x40000.
Invalid Register Offset: 0xc0500198 >= 0x40000.
--> [2:0:0] !!! Failed to read register 0xc0500198..
FATAL ERROR : ATIController failed to access PCI device [2:0:0]!
--> [2:0:0] !!! Failed to read register 0x12480..
FATAL ERROR : ATIController failed to access PCI device [2:0:0]!
--> [2:0:0] !!! Failed to read register 0x12480..
FATAL ERROR : ATIController failed to access PCI device [2:0:0]!
--> [2:0:0] !!! Failed to read register 0x12488..
FATAL ERROR : ATIController failed to access PCI device [2:0:0]!
--> [2:0:0] !!! Failed to read register 0x1248c..
FATAL ERROR : ATIController failed to access PCI device [2:0:0]!
--> [2:0:0] !!! Failed to read register 0x1257c..
FATAL ERROR : ATIController failed to access PCI device [2:0:0]!
--> [2:0:0] !!! Failed to read register 0x1257c..
FATAL ERROR : ATIController failed to access PCI device [2:0:0]!
--> [2:0:0] !!! Failed to read register 0x400..
FATAL ERROR : ATIController failed to access PCI device [2:0:0]!

 

I'm using the attached SSDT file which successfully sets the frame buffer to be Acre, but I need to patch the DVI connector with the following.

 


                        <dict>

                                <key>Comment</key>

                                <string>ATI Connector patch for DVI</string>

                                <key>Disabled</key>

                                <false/>

                                <key>Find</key>

                                <data>BAAAAAQCAAAAAQMAAAAAAAAAAwUAAAAA</data>

                                <key>InfoPlistPatch</key>

                                <false/>

                                <key>Name</key>

                                <string>AMD9500Controller</string>

                                <key>Replace</key>

                                <data>BAAAABQCAAAAAQEAAAAAABAABAUAAAAA</data>

                        </dict>

 

My attempts to resolve this, including using Lilu/WEG have been recorded HERE which hasn't really led anywhere, but this thread looks more promising.

 

Does anybody have any idea what's setting the 0xc0500198 register address and how I might fix this to allow me to upgrade to Mojave.

 

Thanks,

 

Steve

 

SSDT-AMD-Acre.aml

Share this post


Link to post
Share on other sites
13 hours ago, apianti said:

Do you have CSM disabled? Because that region of memory is where traditionally the legacy video rom is placed.

No, this is MMIO radeon register. I used some of them in RadeonMonitor.kext.

#define	CG_CI_MULT_THERMAL_STATUS		0xC0300014
#define		CI_ASIC_MAX_TEMP(x)			((x) << 0)
#define		CI_ASIC_MAX_TEMP_MASK		0x000001ff
#define		CI_ASIC_MAX_TEMP_SHIFT		0
#define		CI_CTF_TEMP(x)				((x) << 9)
#define		CI_CTF_TEMP_MASK			0x0003fe00
#define		CI_CTF_TEMP_SHIFT			9

@Steve Evans

If you are famous with C++ then you can look details in HWSensors3 project. The link is in my signature.

About the register 0xc0500198 I have no information.

I may propose that for access to it a program should get MMIO address which is different for different Radeon families and use indirect register access which can be found in RadeonMonitor.

All of this are for Developer not for user.

Share this post


Link to post
Share on other sites
8 hours ago, Slice said:

No, this is MMIO radeon register. I used some of them in RadeonMonitor.kext.


#define	CG_CI_MULT_THERMAL_STATUS		0xC0300014
#define		CI_ASIC_MAX_TEMP(x)			((x) << 0)
#define		CI_ASIC_MAX_TEMP_MASK		0x000001ff
#define		CI_ASIC_MAX_TEMP_SHIFT		0
#define		CI_CTF_TEMP(x)				((x) << 9)
#define		CI_CTF_TEMP_MASK			0x0003fe00
#define		CI_CTF_TEMP_SHIFT			9

 

 

There is no way that is the actual register address offset as that would mean that the MMIO region is around ~3GB, as 0xC0300014 is 3224371220 bytes, which is not possible. You are making an assumption that is incorrect as I looked at the code and you read from 0x1AC0 + register offset. Because:

IOReturn ATICard::HawaiiTemperatureSensor(UInt16* data)
{
	UInt32 temp, actual_temp = 0;
	for (int i=0; i<1000; i++) {  //attempts to ready
		temp = (read_smc(CG_CI_MULT_THERMAL_STATUS) & CI_CTF_TEMP_MASK) >> CI_CTF_TEMP_SHIFT;
		if ((temp >> 10) & 1)
			actual_temp = 0;
		else if ((temp >> 9) & 1)
			actual_temp = 255;
		else {
			actual_temp = temp & 0x1ff; //(temp >> 1) & 0xff;
			break;
		}
		IOSleep(10);
	}
	
	*data = (UInt16)(actual_temp & 0x1ff);
	//data[1] = 0;
	return kIOReturnSuccess;
}

IOReturn ATICard::ArcticTemperatureSensor(UInt16* data)
{
  UInt32 temp, actual_temp = 0;
  for (int i=0; i<1000; i++) {  //attempts to ready
    temp = (read_ind(CG_CI_MULT_THERMAL_STATUS) & CI_CTF_TEMP_MASK) >> CI_CTF_TEMP_SHIFT;
    if ((temp >> 10) & 1)
      actual_temp = 0;
    else if ((temp >> 9) & 1)
      actual_temp = 255;
    else {
      actual_temp = temp & 0x1ff; //(temp >> 1) & 0xff;
      break;
    }
    IOSleep(10);
  }

  *data = (UInt16)(actual_temp & 0x1ff);
  //data[1] = 0;
  return kIOReturnSuccess;
}
#define INVID(offset) OSReadLittleInt32((mmio_base), offset)
#define OUTVID(offset,val) OSWriteLittleInt32((mmio_base), offset, val)

UInt32 ATICard::read_smc(UInt32 reg)
{
  UInt32 r;
  OUTVID(SMC_IND_INDEX_0, (reg));
  r = INVID(SMC_IND_DATA_0);
  return r;
}


UInt32 ATICard::read_ind(UInt32 reg)
{
    //	unsigned long flags;
	UInt32 r;
    //	spin_lock_irqsave(&rdev->smc_idx_lock, flags);
  OUTVID(mmSMC_IND_INDEX_11, (reg));
  r = INVID(mmSMC_IND_DATA_11);
    //	spin_unlock_irqrestore(&rdev->smc_idx_lock, flags);
	return r;
}
OS_INLINE
UInt32
OSReadLittleInt32(
    volatile void               * base,
    volatile UInt                 offset
)
{
    return *(UInt32 *)((UInt8 *)base + offset);
}

OS_INLINE
void
OSWriteLittleInt32(
    volatile void               * base,
    volatile UInt                 offset,
    volatile UInt32               data
)
{
    *(UInt32 *)((UInt8 *)base + offset) = data;
}

The MMIO region is usually of size 0x40000, which means the register offset cannot be more than 0x3FFFF. The only reason this seems to be working is because the legacy video rom is always present in the region 0xC0000000, which is not guaranteed if CSM is disabled. You appear to actually be accessing register 0x1AD4 from region at 0xC0300000.

 

EDIT: Or you are reading 0x200 + register offset, which is 0x214 from 0xC0300000.

Edited by apianti

Share this post


Link to post
Share on other sites

This is indirect access

UInt32 ATICard::read_smc(UInt32 reg)
{
  UInt32 r;
  OUTVID(SMC_IND_INDEX_0, (reg));
  r = INVID(SMC_IND_DATA_0);
  return r;
}

And there is no restriction to value of (reg).

Share this post


Link to post
Share on other sites
On 12/21/2018 at 4:37 PM, apianti said:

Do you have CSM disabled? Because that region of memory is where traditionally the legacy video rom is placed.

Apologies for the slow response; I became a grandfather for the first time on 19th Dec and have consequently been distracted somewhat from tech. issues! :)

 

The [ur=https://www.dell.com/support/home/uk/en/ukbsdt1/drivers/driversdetails?driverid=cn9vg]A17 BIOS[/url] on this machine lacks a CSM setting.

Share this post


Link to post
Share on other sites
On 12/23/2018 at 8:13 PM, Slice said:

This is indirect access


UInt32 ATICard::read_smc(UInt32 reg)
{
  UInt32 r;
  OUTVID(SMC_IND_INDEX_0, (reg));
  r = INVID(SMC_IND_DATA_0);
  return r;
}

And there is no restriction to value of (reg).

 

It's interesting that this is an indirect access. I'd not appreciated that.

 

@slice

Note though, from my log quoted above that we have:

Invalid Register Offset: 0xc0500198 >= 0x40000

@apianti

The driver is thus expecting the register to fall within the MMIO region which is stated above to usually be of size 0x40000. It's as if the driver is erroneously applying some register offset range checks that should only be applied to direct, not indirect accesses.

 

But why should the driver be attempting such an access on my system when other people are using the RX560 on Mojave without issue?

 

Thanks,

 

Steve

Share this post


Link to post
Share on other sites

@Slice

I'm not sure what indirect access has to do with anything. Indirect access means that a register contains the address of another address to use for a read or write, direct access means a register contains the address itself. Absolutely nothing to do with the fact that you should be reading the location of the memory mapped region from the BAR of the PCI configuration space and using the offset of the register into that region not some random huge offset from another memory location, why even bother with the small offset that that macro provides at all and just read directly from that memory location? It would save a call and an addition instruction at least. But, you should be reading register offsets 0x1AD4 and 0x214 respectively for those registers from the region that is provided in the configuration space. There is no reason to assume that address is the correct address as the memory mapped region could be placed anywhere, especially with multiple devices.

 

@Steve Evans

The problem is most likely you have a patch or something that is creating these offsets and the code is checking to make sure that the register offset is actually within the region. Its not erroneous, it is correct as it will cause a segfault or gpfault otherwise. Most likely the drivers just being worked on more and they made it more secure to prevent malicious code from taking advantage of this.

Share this post


Link to post
Share on other sites

This is AMD logic. I think 0xc0500198 contains address + flags.

The message 

Invalid Register Offset: 0xc0500198 >= 0x40000

means that the driver uses direct access instead of indirect that is may be if the driver mistaken about Radeon family.

Some families requires direct access and other indirect.

Share this post


Link to post
Share on other sites

@apianti

I understand indirect vs direct register access. I’ve been developing real-time embedded software since the 80s :) I’ve also written PCI bus drivers (I ported Windows NT to PowerPC and had to add an understanding of PCI bridges as at the time Microsoft assumed a single bus!) and dealt with BARs etc., so I understand why there’s a range check against a 256k byte window.

 

I’m testing using the Mojave installer in preference to the latest security update to 10.13.6 to avoid tripping over anything in SLE. I’m trying to use a minimal Clover config to keep things simple.

 

The only reference I’ve ever found to 0xc0500198 is in this thread. I’m suspecting that my BIOS is performing some initialisation of the RX 560 card that Clover isn’t correcting, and MacOS doesn’t like.

 

@Slice

Can you please suggest some device IDs to try to explore your suggestion. Also, have you ever seen 0xc0500198 as reported earlier in this thread? Any idea what extra initialisation I could perform to reset the GPU to a better state for MacOS to handle?

 

Thanks,

 

Steve

 

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 ThatsMatt
      Salve, sono nuovo nel forum e mi serviva una mano nell'installazione dell' ultima versione di MacOs sul mio notebook HP Pavilion 15-ak112nl.
      Specifiche Tecniche: 
      CPU: Intel Core i7-6700HQ (2.60 / 3.50 GHz, 4 core, 6 MB CACHE L3). 
      Scheda Grafica: Intel HD Graphics 530 + NVIDIA GeForce GTX 950M 4 GB DDR3.
      Hard Disk: 1 TB SATA 5400 rpm.
      Ram: 8 GB DDR3L-1600.
      Audio: altoparlanti stereo Bang & Olufsen PLAY. 
      Rete: LAN 10/100, WLAN 802.11b/g/n, bluetooth 4.0 (Miracast).
      Grazie in Anticipo a chi mi risponderà
    • By Coddyx
      Hi,
       
      I followed the AMD OSX Vanilla Guide and managed to successfully build my first hackingtosh.
      Everything works great EXCEPT for my MSI - Radeon RX 580 8 GB GAMING X.
      I ran some benchmarks (and tried World of Warcraft) and I am getting ~50% of the performance I am usually getting in Windows 10.
      Unigine Heaven reports ~950 vs 1750 in Windows and World of Warcraft runs @ 30 fps lowest settings vs 60 fps ultra settings in Windows.
       
      Here are the kexts I am using:
      AppleALC Lilu NullCPUPowerManagement RealtekRTL811 VirtualSMC WhateverGreen  
      I should mention that this is an AMD hackingtosh running on Ryzen 5 1600 3.2 GHz 6-Core Processor.
       
      I read and I completely understand that I should not expect 100% performance. But I believe a 50% drop is out of the ordinary.
       
      If anyone has ideas on what I could try to up the performance it would be greatly appreciated.
       
      Thank you!
       
       
    • By fusion71au
      Clover r4961 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.14 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4961 for VMware.zip". Mount Clover-v2.4k-4961-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • 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  AptioMemory --> (consigliato) 
                               : Driver64UEFI  ApfsDriverLoader --> (consigliato) --> sostituisce l'uso del driver apfs.efi
                               : Selezionate l'altri driver come da successiva immagine,
       
      *Nota: Altri driver che si possono usare  al suo posto  sono:
       informazioni 
       
      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 può essere usato anche per effettuare aggiornamenti...
      nel caso guardate...
       Mojave in HFS 
       Oppure direttamente da usb  
       
      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
      Pacchetto-Fake+Sensors 6.26.1440.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip





       

×