Jump to content

12 posts in this topic

Recommended Posts

Buongiorno,

ho installato su diversi hardware la IATKOS ml2 10.8.2 

 

Non sono riuscito ad aumentare la risoluzione oltre 1024x768 su nessun hardware da me provato.

 

Ho provato con una INTEL HD2000, una ATI Radeon 3600 HD ma nulla

il resto funziona abbastanza bene, rete, audio sembra essere tutto ok ma per la risoluzione e per l'accelerazione video nulla.

Vorrei provare a comprare una scheda certificata,ma vorrei chiedere ai presenti se qualcuno è riuscito a cambiare la risoluzione e se le performance sono accettabili.

 

Grazie per l'aiuto

 

 

Share this post


Link to post
Share on other sites
Advertisement

Ciao, ho un paio di domande, perchè esposto così non si capisce bene se il problema è legato alle schede video (molto probabile) o a iAtkos (molto meno probabile).

Notebook o desktop?

Fai la lista dell'hardware completo, nel caso sia un notebook scrivi marca e modello preciso del NB

Share this post


Link to post
Share on other sites

a cambiare risoluzione non sarebbe un problema

e senza accelerazione un mac e come win in mod provvisoria

 

ma quelle video com Mlion non vanno

Share this post


Link to post
Share on other sites

Allora,

grazie anzitutto per le risposte.

 

Sto facendo le mie prove con un pc Assemblato I7 con 8 Gb di ram ed un hd 120 gb 

 

La scheda grafica integrata è una INTEL HD2000  ma sembra che non viene riconosciuta in quanto la ris. rimane a 1024 x 768 e l'accelerazione non c'è

Ho provato sullo stesso hardware una ATI HD3600 ma stesso risultato

Finalmente mi hanno prestato una NVIDIA con una NVIDIA GeForce GT 610 che viene riconosciuta e finalmente vedo il monitor ad alta risoluzione.

 

inizio a lavorare, mi ha riconosciuto sia la scheda di rete che la scheda sonora e la webcam integrata sul monitor (HP 2448) 

 

ho ancora 2 problemini

  1° non posso installar4e chamaleon per personalizzare alcune feature quali ad esempio il seriale che mi serve per eseguire teambviewer

  2° vorrei mappare alcuni tasti della tastira quale per esempio home, fine control ecc

 

potreste aiutarmi per cortesia?

Share this post


Link to post
Share on other sites

Preferenze di sistema-Sicurezza e privacy-togli il lucchetto e metti la spunta su "Dovunque", altrimenti non puoi installare programmi non "certificati"

Share this post


Link to post
Share on other sites

No Carbo, il mio problema purtroppo non è questo.

 

avevo già cambiato le policy di sicurezza come tu hai indicato. Il problema è che l'installazione di chamaleon viene completata, ma pur riavviando si attiva.

quindi tutti i parametri di configurazione non sono modificabili. E' come se il boot loader impostato nella installazione fosse non modificabile

 

vorrei precisare che:

nei vari post di soluzione vedo che bisognerebbe modificare un file chiamato SMBIOS.plist 

 

il punto è che io questo file non ce l'ho sul mio sistema quindi per esempio non posso inserire un codice seriale valido pert accedere ad apple store oppure per abilitare l'accesso ai server di teamviewer

 

Io ho installato la IATKOS ML2 con la versione 10.8.5.

Share this post


Link to post
Share on other sites

Buongiorno Carbo178,

 non ho chamaleon

 ho la cartella Extra nella root

 

non ho cambiato il boot loader che installa la iatkos ML2 non ti so dire se è clover e non so da dove posso desumerlo

 

Quello che ho cercato di fare, seguendo alcuni post su questo forum, e di installare chamaleon per vedere di risolvere alcuni problemini,

ma purtroppo non riesco ad attivarlo.

Non so se posso modificare i parametri tipo smbios.plist pur non avendo chamaleon.

 

Brancolo nel buio. 

se potessi darmi qualche info ti ringrazio in anticipo

Share this post


Link to post
Share on other sites

Nella schermata principale di Chameleon wizard trovi le info necessarie

Dimmi di più sul sistema, nome esatto della mobo e del processore, in modo da creare un smbios adatto

Schermata 2014-02-08 alle 09.51.17.png

Share this post


Link to post
Share on other sites

buonasera

queste sono le info del mio sistema:

=========

 

  Nome modello: iMac

  Identificatore modello: iMac12,1

  Nome processore: Intel Core i7

  Velocità processore: 3,39 GHz

  Numero di processori: 1

  Numero totale di Core: 4

  Cache L2 (per Core): 256 KBå

  Cache L3: 8 MB

  Memoria: 8 GB

  Versione Boot ROM: IM121.0047.B00

  Versione SMC (sistema): 1.30f3

  Numero di serie (sistema): SOMESRLNMBR

  Hardware UUID: 68081C0D-5B97-5ED3-86EB-F270873E744D

 

ATA SERIALE

Unknown AHCI Standard Controller:

 

  Fornitore: Unknown

  Prodotto: AHCI Standard Controller

  Velocità collegamento: 3 Gigabit

  Velocità link negoziata: 3 Gigabit

  Descrizione: AHCI Version 1.30 Supported

 

ST31000524AS:

 

  Capienza: 1 TB (1.000.204.886.016 byte)

  Modello: ST31000524AS                            

  Revisione: JC4B    

  Numero di serie:             9VPEE3X9

  Native Command Queuing:

  Lunghezza coda: 32

  Disco estraibile: No

  Unità amovibile: No

  Nome BSD: disk1

  Frequenza rotazionale: 7200

  Tipo supporto: Rotazionale

  Tipo mappa partizione: Master Boot Record (MRB)

  Stato S.M.A.R.T.: Verificato

  Volumi:

DATI:

  Capienza: 1 TB (1.000.202.043.392 byte)

  Disponibile: 829,54 GB (829.536.739.328 byte)

  Scrivibile: No

  File System: NTFS

  Nome BSD: disk1s1

  Punto di attivazione: /Volumes/DATI

  Contenuto: Windows_NTFS

  UUID Volume: EC25E722-043A-491E-92B4-6624CF01C2B5

 

 

  ID audio: 1

 

Altoparlante:

 

  Connessione: 1/8-Inch Jack

 

Uscita linea:

 

  Connessione: 1/8-Inch Jack

 

Uscita linea:

 

  Connessione: 1/8-Inch Jack

 

Microfono Interno:

 

  Connessione: Interno

 

Ingresso linea:

 

  Connessione: 1/8-Inch Jack

 

Ingresso linea:

 

  Connessione: 1/8-Inch Jack

 

Cuffie:

 

  Connessione: 1/8-Inch Jack

 

Uscita audio digitale ottico S/PDIF:

 

  Connessione: Uscita combinazione

 

NVIDIA GeForce GT 610:

 

  Modello Chipset: NVIDIA GeForce GT 610

  Tipo: GPU

  Bus: PCIe

  Larghezza Lane PCIe: x16

  VRAM (totale): 1024 MB

  Fornitore: NVIDIA (0x10de)

  ID dispositivo: 0x104a

  ID revisione: 0x00a1

  Revisione ROM: preset 75.19.55.00.02

  Monitor:

SAMSUNG:

  Risoluzione: 1920 x 1080 @ 50 Hz

  Profondità pixel: Colore 32 bit (ARGB8888)

  Monitor principale:

  Mirror: Spento

  Online:

  Rotazione: Supportata

  Interlacciato:

  Televisore:

 

ethernet:

 

  Tipo: Controller Ethernet

  Bus: PCI

  ID produttore: 0x10ec

  ID dispositivo: 0x8168

  ID fornitore sottosistema: 0x1043

  ID sottosistema: 0x8432

  ID revisione: 0x0006

  Ampiezza link: x1

  Nome BSD: en0

  Nome Kext: RealtekRTL81xx.kext

  Posizione: /System/Library/Extensions/RealtekRTL81xx.kext

  Versione: 0.0.90

 

 

 

=============================================

Chameleon 2.2svn (svn-r2258) [2013-08-22 21:23:21]

msr(392): platform_info 60012200

msr(396): flex_ratio 00080000

Sticking with [bCLK: 99Mhz, Bus-Ratio: 340]

CPU: Brand String:             Intel® Core i7-2600 CPU @ 3.40GHz

CPU: Vendor/Family/ExtFamily:  0x756e6547/0x6/0x0

CPU: Model/ExtModel/Stepping:  0x2a/0x2/0x7

CPU: MaxCoef/CurrCoef:         0x0/0x22

CPU: MaxDiv/CurrDiv:           0x0/0x0

CPU: TSCFreq:                  3392MHz

CPU: FSBFreq:                  99MHz

CPU: CPUFreq:                  3392MHz

CPU: NoCores/NoThreads:        4/8

CPU: Features:                 0x000002ff

Attempting to read GPT

Read GPT

Reading GPT partition 1, type C12A7328-F81F-11D2-BA4B-00A0C93EC93B

Reading GPT partition 2, type 48465300-0000-11AA-AA11-00306543ECAC

Read HFS+ file: [hd(0,2)/System/Library/CoreServices/SystemVersion.plist] 478 bytes.

Read HFS+ file: [hd(0,2)/Extra/org.chameleon.Boot.plist] 180 bytes.

Module 'Symbols.dylib' by 'Chameleon' Loaded.

Description: Chameleon symbols for linking

Version: 0

Compat:  0

Read HFS+ file: [hd(0,2)/Extra/modules/KernelPatcher.dylib] 31272 bytes.

Module 'KernelPatcher.dylib' by 'Unknown' Loaded.

Description: 

Version: 0

Compat:  0

Read HFS+ file: [hd(0,2)/Extra/modules/Keylayout.dylib] 13464 bytes.

Module 'Keylayout.dylib' by 'Unknown' Loaded.

Description: 

Version: 0

Compat:  0

Read HFS+ file: [hd(0,2)/Extra/modules/klibc.dylib] 44260 bytes.

Module 'klibc.dylib' by 'Unknown' Loaded.

Description: 

Version: 0

Compat:  0

Read HFS+ file: [hd(0,2)/Extra/modules/Resolution.dylib] 26528 bytes.

Module 'Resolution.dylib' by 'Unknown' Loaded.

Description: 

Version: 0

Compat:  0

Resolution:

 core proc identified

 Detected chipset/proc id (DRAM controller): 01008086

 VBios: nVidia

 Patching: BT_NVDA Edid not found or invalid - vbios not patched!

Read HFS+ file: [hd(0,2)/Extra/modules/uClibcxx.dylib] 85192 bytes.

Module 'uClibcxx.dylib' by 'Unknown' Loaded.

Description: 

Version: 0

Compat:  0

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/theme.plist] 2791 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/background.png] 2625144 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/logo.png] 51220 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_generic.png] 13788 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_generic_o.png] 20390 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_hfsplus.png] 14878 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_hfsplus_o.png] 20610 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_hfsraid.png] 15337 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_hfsraid_o.png] 21096 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_ext3.png] 15144 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_ext3_o.png] 21142 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_fat.png] 14340 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_fat_o.png] 21006 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_ntfs.png] 14237 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_ntfs_o.png] 20176 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_cdrom.png] 14188 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_cdrom_o.png] 20555 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_selection.png] 4703 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_scroll_prev.png] 2008 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_scroll_next.png] 2020 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_boot.png] 1975 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_verbose.png] 2155 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_ignore_caches.png] 2121 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_single_user.png] 2228 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_memory_info.png] 1486 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_video_info.png] 1550 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_help.png] 2178 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_verbose_disabled.png] 2080 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_ignore_caches_disabled.png] 2029 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_single_user_disabled.png] 2159 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_selection.png] 418 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/progress_bar.png] 1037 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/progress_bar_background.png] 1034 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/text_scroll_prev.png] 791 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/text_scroll_next.png] 798 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/font_console.png] 3499 bytes.

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/font_small.png] 8540 bytes.

Read HFS+ file: [hd(0,2)/Library/Preferences/SystemConfiguration/com.apple.Boot.plist] 232 bytes.

Read HFS+ file: [hd(0,2)/Extra/org.chameleon.Boot.plist] 180 bytes.

Read HFS+ file: [hd(0,2)/private/var/vm/sleepimage] 512 bytes.

header read size 200

Incorrect image signature

Loading Darwin 10.8

Loading kernel cache /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache

Read HFS+ file: [hd(0,2)/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache] 4096 bytes.

Read HFS+ file: [hd(0,2)/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache] 21098779 bytes.

kernel_patcher.c[534]: Patching 64bit XNU Kernel 12.2.0

Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; *patched-2050.18.24~1/RELEASE_X86_64

cpuid_patch.c[52]: Attempting to patch 64bit kernel for unknown cpu

cpuid_patch.c[115]: Panic call removed.

commpage_patch.c[87]: _commpage_stuff_routine patched.

lapic_patch.c[76]: lapic_init panic removed.

bootstrap_patch.c[167]: KLDBootstrap::readBooterExtensions() call injected into KLDBootstrap::readPrelinkedExtensions(void* section_64)

ACPI table not found: DSDT.aml

No DSDT found, using 0 as uid value.

Using PCI-Root-UID value: 0

No SMBIOS replacement found.

SMBus CmdReg: 0x3

Scanning SMBus [8086:1c22], mmio: 0xfb104004, ioport: 0xf000, hostc: 0x1

SPD[0] (size): 146 @0x50

Slot: 0 Type 24 4096MB (DDR3 SDRAM) 1333MHz Vendor=Kingston

      PartNo=99U5471-012.A00LF SerialNo=7F04B699

SPD[0] (size): 255 @0x51

SPD[0] (size): 146 @0x52

Slot: 2 Type 24 4096MB (DDR3 SDRAM) 1333MHz Vendor=Kingston

      PartNo=99U5471-012.A00LF SerialNo=6D04ABCE

SPD[0] (size): 255 @0x53

SPD[0] (size): 255 @0x54

SPD[0] (size): 255 @0x55

SPD[0] (size): 255 @0x56

SPD[0] (size): 255 @0x57

CPU is Intel® Core i7-2600 CPU @ 3.40GHz, family 0x6, model 0x2a

 

Type: 0, Length: 24, Handle: 0x0

BIOSInformation:

vendor: Apple Inc.

version:     IM121.88Z.0047.B00.1102091756

releaseDate: 11/06/2009

 

Type: 1, Length: 27, Handle: 0x1

SystemInformation:

manufacturer: Apple Inc.

productName: iMac12,1

version: 1.0

serialNumber: SOMESRLNMBR

uuid: A073E211-CB5B-D911-BDE4-14DAE9961D6B

wakeupReason: 0x6

skuNumber: To be filled by O.E.M.

family: iMac

 

Type: 2, Length: 15, Handle: 0x2

BaseBoard:

manufacturer: Apple Inc.

product: Mac-F4208DC8

version: Rev x.0x

serialNumber: MT7017156701645

assetTagNumber: To be filled by O.E.M.

locationInChassis: To be filled by O.E.M.

boardType: 0xA

 

Type: 3, Length: 21, Handle: 0x3

SystemEnclosure:

manufacturer: Chassis Manufacture

type: 3

version: Chassis Version

serialNumber: Chassis Serial Number

assetTagNumber: Asset-1234567890

 

Type: 4, Length: 42, Handle: 0x4

ProcessorInformation:

socketDesignation: LGA1155

processorType: 3

processorFamily: 0xBF

manufacturer: Intel

processorID: 0x206A7

processorVersion: Intel® Core i7-2600 CPU @ 3.40GHz

externalClock: 0MHz

maximumClock: 3392MHz

currentClock: 3400MHz

serialNumber: To Be Filled By O.E.M.

assetTag: To Be Filled By O.E.M.

partNumber: To Be Filled By O.E.M.

 

Type: 7, Length: 19, Handle: 0x5

Type: 7, Length: 19, Handle: 0x6

Type: 7, Length: 19, Handle: 0x7

Type: 8, Length: 9, Handle: 0x8

Type: 8, Length: 9, Handle: 0x9

Type: 8, Length: 9, Handle: 0xa

Type: 8, Length: 9, Handle: 0xb

Type: 8, Length: 9, Handle: 0xc

Type: 8, Length: 9, Handle: 0xd

Type: 8, Length: 9, Handle: 0xe

Type: 8, Length: 9, Handle: 0xf

Type: 8, Length: 9, Handle: 0x10

Type: 8, Length: 9, Handle: 0x11

Type: 8, Length: 9, Handle: 0x12

Type: 8, Length: 9, Handle: 0x13

Type: 8, Length: 9, Handle: 0x14

Type: 8, Length: 9, Handle: 0x15

Type: 8, Length: 9, Handle: 0x16

Type: 8, Length: 9, Handle: 0x17

Type: 8, Length: 9, Handle: 0x18

Type: 8, Length: 9, Handle: 0x19

Type: 8, Length: 9, Handle: 0x1a

Type: 9, Length: 17, Handle: 0x1b

Type: 9, Length: 17, Handle: 0x1c

Type: 9, Length: 17, Handle: 0x1d

Type: 9, Length: 17, Handle: 0x1e

Type: 10, Length: 6, Handle: 0x1f

Type: 11, Length: 5, Handle: 0x20

Type: 12, Length: 5, Handle: 0x21

Type: 16, Length: 15, Handle: 0x22

Type: 18, Length: 23, Handle: 0x23

Type: 19, Length: 15, Handle: 0x24

Type: 17, Length: 28, Handle: 0x25

MemoryDevice:

deviceLocator: DIMM0

bankLocator: BANK0

memoryType: DDR3

memorySpeed: 1333MHz

errorHandle: ffff

manufacturer: Kingston

serialNumber: 7F04B699

assetTag: AssetTagNum0

partNumber: 99U5471-012.A00LF

 

Type: 18, Length: 23, Handle: 0x26

Type: 20, Length: 19, Handle: 0x27

Type: 17, Length: 28, Handle: 0x28

MemoryDevice:

deviceLocator: DIMM1

bankLocator: BANK1

memoryType: DDR3

memorySpeed: 1333MHz

errorHandle: ffff

manufacturer: Kingston

serialNumber: 6D04ABCE

assetTag: AssetTagNum1

partNumber: 99U5471-012.A00LF

 

Type: 18, Length: 23, Handle: 0x29

Type: 20, Length: 19, Handle: 0x2a

Type: 32, Length: 20, Handle: 0x2b

Type: 34, Length: 11, Handle: 0x2c

Type: 26, Length: 22, Handle: 0x2d

Type: 36, Length: 16, Handle: 0x2e

Type: 35, Length: 11, Handle: 0x2f

Type: 28, Length: 22, Handle: 0x30

Type: 36, Length: 16, Handle: 0x31

Type: 35, Length: 11, Handle: 0x32

Type: 27, Length: 14, Handle: 0x33

Type: 36, Length: 16, Handle: 0x34

Type: 35, Length: 11, Handle: 0x35

Type: 27, Length: 14, Handle: 0x36

Type: 36, Length: 16, Handle: 0x37

Type: 35, Length: 11, Handle: 0x38

Type: 29, Length: 22, Handle: 0x39

Type: 36, Length: 16, Handle: 0x3a

Type: 35, Length: 11, Handle: 0x3b

Type: 39, Length: 22, Handle: 0x3c

Type: 34, Length: 16, Handle: 0x3d

Type: 26, Length: 22, Handle: 0x3e

Type: 36, Length: 16, Handle: 0x3f

Type: 35, Length: 11, Handle: 0x40

Type: 26, Length: 22, Handle: 0x41

Type: 36, Length: 16, Handle: 0x42

Type: 35, Length: 11, Handle: 0x43

Type: 28, Length: 22, Handle: 0x44

Type: 36, Length: 16, Handle: 0x45

Type: 35, Length: 11, Handle: 0x46

Type: 27, Length: 14, Handle: 0x47

Type: 36, Length: 16, Handle: 0x48

Type: 35, Length: 11, Handle: 0x49

Type: 28, Length: 22, Handle: 0x4a

Type: 36, Length: 16, Handle: 0x4b

Type: 35, Length: 11, Handle: 0x4c

Type: 27, Length: 14, Handle: 0x4d

Type: 36, Length: 16, Handle: 0x4e

Type: 35, Length: 11, Handle: 0x4f

Type: 29, Length: 22, Handle: 0x50

Type: 36, Length: 16, Handle: 0x51

Type: 35, Length: 11, Handle: 0x52

Type: 29, Length: 22, Handle: 0x53

Type: 36, Length: 16, Handle: 0x54

Type: 35, Length: 11, Handle: 0x55

Type: 39, Length: 22, Handle: 0x56

Type: 41, Length: 11, Handle: 0x57

Type: 41, Length: 11, Handle: 0x58

Type: 41, Length: 11, Handle: 0x59

Type: 139, Length: 94, Handle: 0x5a

Type: 13, Length: 22, Handle: 0x5b

Type: 131, Length: 6, Handle: 0x5b

AppleProcessorType:

ProcessorType: 0x701

 

Type: 132, Length: 6, Handle: 0x5c

AppleProcessorBusSpeed:

ProcessorBusSpeed (QPI): 0.0GT/s

 

Type: 127, Length: 4, Handle: 0x5d

 

Customizing SystemID with : a073e211-cb5b-d911-bde4-14dae9961d6b

efi_inject_get_devprop_string NULL trying stringdata

ACPI table not found: DSDT.aml

ACPI table not found: SSDT.aml

FADT: ACPI Restart Fix applied!

FADT: ACPI Restart Fix applied!

Errors encountered while starting up the computer.

Pausing 5 seconds...

Starting Darwin x86_64

Boot Args: boot-uuid=0FEC1694-6CA7-3D64-B151-5F8E67AC10F5 rd=*uuid 

Read HFS+ file: [hd(0,2)/Extra/Themes/Default/boot.png] 7377 bytes.

Share this post


Link to post
Share on other sites

Forse ho risolto.

Con Chamaleon Wizard ho creato un file SMBios.plist

l'ho salvato sul desktop

ho chiuso chamaleon ed ho copiato questo file nella cartella EXTRA

Riavviato

Ora Teamviewer funziona.

 

Grazie per l'aiuto a tutti

Share this post


Link to post
Share on other sites

Forse era un problema di permessi, sul mio pc mi capita sempre che dopo formattato devo modificare i permessi di alcuni file tipo il file o.c.b.p. perché se non lo faccio e modifico le impostazioni ed esco una volta che lo riapro mi ritrovo il file come prima.

Share this post


Link to post
Share on other sites
Guest
You are commenting as a guest. If you have an account, please sign in.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Slice
      As I see many novices in the forum ask "How to make my Radeon working? I have bad resolution, no QE/CI...." and so on. They come to the section and have no find an answer here because all Radeons are different and they don't know where else they read about this.
      I want to explain all steps needed for launching the Radeon family of videocards.
       
      Bootloader.
      I will speak about Clover because I maintain this bootloader to know recent hardware and modern OSX. Not sure if you will have the same result with other bootloaders. I am carefully checking the injecting of ATI card and correcting it times to times. I am also accessible for bug reports.
       
      OSX version.
      Older card require older system, newer cards require new system.
      ATIRadeon9000 is possible to launch under Tiger.
      ATIRadeonMobilityX1400 requires 10.5-10.6. See RadeonHD topic.
      As I see RadeonHD3xxx was successful only in 10.5
      For new AMDRadeonHD7xxx there must be 10.8.3+ system.
       
      DeviceID.
      This must be the first question before asking about the card.
      You may know the device-id from Windows->DeviceManger->VideoCard.properties->compatibleIDs
      You may boot into system in safe mode (key -x) and see system profiler
       
      And you may boot into Clover GUI, press F2 and get preboot.log. Find here something like
      2:709 0:000 PCI (00|01:00.00) : 1002 6758 class=030000 2:709 0:000 Found Radeon model=AMD Radeon HD 6670 Series It means my DeviceID=6758 (these are hex numbers)
      Then you must check that Apple's drivers support your DeviceID. If not then add it!
      For example HD7850 has DeviceID=6819. If we look into ATI7000Controller (AMD7000... in new systems) we find 6818 here but no 6819!
       
       
      I show you how to do this with terminal commands. Launch /Application/Utilities/Terminal.app. Type in opened window:
       
      cp /System/Library/Extensions/ATI7000Controller.kext/Contents/Info.plist ~/Desktop So you get a copy of the Info.plist on Desktop. Edit it with TextEdit. Change 68181002 -> 68191002.
      Don't edit this file directly in the system folder! 
      Then copy back by terminal. Don't use finder to copy kexts! They will have wrong permissions in this case.
      sudo cp ~/Desktop/Info.plist /System/Library/Extensions/ATI7000Controller.kext/Contents/ sudo rm -r -v /System/Library/Caches/com.apple.kext.caches/* Second command make sure next reboot the kext will use your edited info.plist.
      The same operation you must do with a kext AMDRadeonAccelerator or ATIRadeonX2000 or other one. Check all candidates if they contain such list of possible IDs and choose closest to you.
       
      FakeID
      Since Clover revision 1971+ you may just inject new DeviceID into DSDT instead of correcting kexts. See instruction here.
       
      GraphicsEnabler or Injector
      OSX needs to know some properties (Model name, Family, etc...) that must be somehow injected at boot time. Yes, also real Macs got DeviceProperties string from firmware.
      Alternatives:
      1. Set InjectATI=Yes in Clover (same as GE=y in Chameleon).
      2. Use custom string made with gfxutil. For whom who knows.
      3. Write _DSM into DSDT. You should know what to write.
      4. Use some kext like ATY_init.kext or Natit.kext. If you are sure that the kext is for your card namely.
      I want to say that all this methods make the same thing. Differencies in their tuning.
      The Clover do this automatically for most known cards at this moment.
       
      Connectors.
      As you may see to start HD5000-7000 some strange names used: Pithecia, Orangutan, Elodea... What are they?
      They are configs for framebuffer. Predefined configs how connectors are solded for cards used in real Macs. Strange but these configs rear coincide with PC card. Usually gurus make advice "choose a framebuffer that most appropriate for your card". The chances 1:10. In most cases you may find a FB name that gives you main monitor working. Or nothing at all.
      Great respect to bcc9 who gives us a method to correct one of config to be exactly for you. See here.
      My retelling for Clover is here
      Success example in the thread in posts 44-52
       
      Radeon Mobility
      I tested Clover's methods with two users having Mobility Radeon HD5470 and HD5650M. We found that full memory and QE/CI will be achieved if we set in Clover's config
      LoadVBios=Yes
      even thou no file with bios is provided. This is the key to make Radeon Mobility working!
      Other problem is bad gradients or artifacts. For this case Clover accept the key
      InjectEDID=Yes
      and sometimes you also need to inject CustomEDID.
      See Clover instructions for details.
       
      And my results.
      Gigabyte Radeon HD6670
      <key>Graphics</key> <dict> <key>GraphicsInjector</key> <true/> <key>InjectEDID</key> <true/> <key>FBName</key> <string>Ipomoea</string> <key>LoadVBios</key> <false/> <key>VideoPorts</key> <integer>3</integer> <key>PatchVBios</key> <true/> </dict> <key>KernelAndKextPatches</key> <dict> <key>KernelCpu</key> <false/> <key>ATIConnectorsController</key> <string>6000</string> <key>ATIConnectorsData</key> <string>000400000403000000010000120401050008000004020000000100001102040310000000100000000001000000000002</string> <key>ATIConnectorsPatch</key> <string>040000000403000000010000100001061000000010000000000100000000000100080000040200000001000012040403</string> VTX Radeon HD5570
      <key>Graphics</key> <dict> <key>PatchVBios</key> <false/> <key>FBName</key> <string>Baboon</string> <key>VideoPorts</key> <string>3</string> <key>GraphicsInjector</key> <string>Yes</string> <key>LoadVBios</key> <string>No</string> </dict> <key>KernelAndKextPatches</key> <dict> <key>Debug</key> <false/> <key>KernelCpu</key> <false/> <key>ATIConnectorsController</key> <string>5000</string> <key>ATIConnectorsData</key> <string>040000001400000000010000010201030008000000020000007100002205020110000000100000000001000000100002</string> <key>AppleRTC</key> <true/> <key>ATIConnectorsPatch</key> <string>040000001400000000010000010001040008000000020000007100002200020510000000100000000001000000000002</string> <key>AsusAICPUPM</key> <false/> <key>KextsToPatch</key> <array> <dict> <key>Name</key> <string>AppleAHCIPort</string> <key>Find</key> <data>RXh0ZXJuYWw=</data> <key>Replace</key> <data>SW50ZXJuYWw=</data> </dict> </array> </dict> See PatchVBios=No
      for this card "yes" leads to black screen. Use with precautions.
       
      A sample for Radeon R7 240
       
      UPDATE for ElCapitan.
      It seems has more problems. My HD6670 is not working in ElCapitan OOB unlike Mavericks.
      I had to set FakeID=0x67401002 as correspond to real iMac12,2 and set this model in SMBIOS section.
      It related to GraphicsPM or GraphicsControl.
      Look these kexts to decide what you can do for your configuration.
       
      HighSierra requires change these kexts by version from Sierra 10.12.6
      for Radeon HD6xxx
      AMDRadeonX3000.kext AMDRadeonX3000GLDriver.bundle IOAccelerator2D.plugin IOAcceleratorFamily2.kext .  for Radeon HD7xxx and up AMDRadeonX4000.kext AMDRadeonX4000GLDriver.bundle IOAccelerator2D.plugin IOAcceleratorFamily2.kext .    Black screen after wake problem resolved by follow method radeon_bios_decode.0.2.zip
      ati-personality.pl.0.15.zip
      ati-personality.pl.0.15a.zip
    • By blxkspell
      Hey!
      As I have 3 Monitors connected, my RX 570 gets arround 50°C while ideling/ web browsing etc. The problem is, that this temp is apparently just the threshold, when the fans start to spin. So the fans start spinning for a minute then they stop for a while again... This is very annoying for me as the rest of my hackintosh is nearly quiet (SSD, 120mm low RPM cpu fan, nearly silent PSU,...), especially when Im using the pc to revise for school. Does somebody know wether its possible to "change" the threshold till the fans start spinning? Like it would probably not be a problem for the gpu at all, if the temp rises to 55°C but therefore be soundless....
       
       
    • By 1Ale1
      Ciao a tutti, ultimamente ho deciso di mettermi al lavoro e fare un investimento a lungo termine comprando un fisso che ho assemblato pezzo dopo pezzo leggendo numerosi forum per essere bene informato sul miglior hardware che potessi ottenere per un Hackintosh ottimizzando al meglio i costi: ho finito così per comprare:
       
      Hardware:
       
       
      -Motherboard: Gigabyte Z390 Aorus Pro (Rev 1.0)
      -CPU: Intel i7 9700k raffreddato a liquido (CoffeLake)
      -GPU: AMD Radeon RX580 (avendo letto le eccellenti prestazioni a ottimo prezzo per MacOS)
      -RAM: 32GB DDR4 Crucial Ballistix Sport LT (4x8GB 3000MHz)
      -NVMe SSD Samsung 970 Evo 250GB M.2 dedicato solo a MacOS, nel secondo slot della Mobo M.2 avrei poi messo un Western Digital Blue da 250GB con Windows 10 su metà disco e per l'altra metà il Debian che sto utilizzando adesso
       
       
      Poi mi sono messo subito al lavoro per cercare di far partire questo benedetto MacOs su una macchina non ufficiale, ho tovato quindi questa guida su GitHub che era molto simile alla mia configurazione:
       
      https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md
       
      Dopo aver fatto partire una macchina virtuale per configurare la USB come comunemente viene fatto, scaricando l'applicazione e facendo il "burn/copia dei file" di macOS su pennetta esterna rendendola bootabile solamente da un pc ufficiale mac, sono passato alla configurazione di Clover (l'EFI installer, cartella che allegherò qui sotto, ma prima leggete il problema): Ho messo i driver necessari, mettendo quelli che lui menzionava sotto la sezione "building the usb installer"
       
      https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/building-the-usb-installer
       
       
      Install Clover for UEFI booting only
      Install Clover to the ESP
      Under Drivers64UEFI:
      AptioMemoryFix (the new hotness that includes NVRAM fixes, as well as better memory management) (che poi ho dovuto rimuovere, leggi sezione https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md#fixing-kernel-panics-at-rebootshutdown)
      VBoxHfs-64.efi (or HFSPlus.efi if available) - one of these is required for Clover to see and boot HFS+ volumes. If you see the option to enable it in the installer, make sure it's selected - if you don't see it in the installer, verify that one of them exists in the EFI -> CLOVER -> drivers64UEFI folder
      ApfsDriverLoader - (Available in Dids' Clover builds - or here) this allows Clover to see and boot from APFS volumes by loading apfs.efi from ApfsContainer located on block device (if using AptioMemoryFix as well, requires R21 or newer)
       
      applicando piccole modifiche a causa di un errore già riportato da questa persona che ha scritto la guida di GitHub di sostituire AptioMemoryFix-64 (dalla cartella EFI/EFI/CLOVER/driver64UEFI) con OsxAptioFix2Drv-free2000, questa infatti riportava  quanto segue dopo aver detto di aver sostituito AptioMemoryFix-64.efi con OsxaptioFix2Drv-free2000:
       
      "I am told that there are downsides (that I don't fully understand yet) to using OsxAptioFix2Drv-free2000, so do this at your own risk."
       
      Ho configurato poi il config.plist
       
      Come diceva lui, partendo da questo file: https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/config.plist-per-hardware/coffee-lake e applicando le modifiche che sotto ha descritto, del tipo:
       
      Open coffeelake_sample_config.plist with Clover Configurator (right click → Open With → Clover Configurator)   In SMBIOS: - Click the button with an up/down arrow (middle right). Chose iMac18,3. This is important since we'll be connecting our monitor to the RX580. The HDMI port on our motherboard is NOT yet working for Hackintoshes. - Make sure the serial number generated is an iMac (mid-2017) by clicking Model Lookup. - Ensure that Check Coverage reports that the serial is NOT valid. You don't want to use somebody else's serial number. - While you're here, copy your Board Serial Number to your clipboard. You'll need it soon.
      In Rt Variables: Paste your Board Serial Number in the MLB field. Set CsrActiveConfig to 0x0 which enables SIP for extra security. This should work just fine for a Vanilla Hackintosh install and is how genuine Macs ship. In Boot: Change the Custom Flags to: shikigva=40 uia_exclude=HS14 (this disables onboard Bluetooth since we'll be using an external Broadcom Wi-Fi/Bluetooth adapter) In ACPI: Click List of Patches and enable the following: Change GFX0 to IGPU In Devices: Set Inject to 16. Now to enable our headless iGPU, we need to fake the device id. To do so, Click Properties, select PciRoot(0x0)/Pci(0x2,0x0). Then, click the + button to add a property. Add the following: Property Key: device-id Property Value: 923E0000 Value Type: DATA Click the Export Configuration button (bottom left), then Save As config.plist. Copy your newly generated config.plist to /EFI/CLOVER/ on your bootable USB key.  
      Impostazioni BIOS
       
      E avendo settato nel BIOS le impostazioni che questa perona configliava all'inizio della guida,                       (N.B. la mia versione di Bios è l'ultima, F7 https://www.gigabyte.com/Motherboard/Z390-AORUS-PRO-rev-10#support-dl-bios) (a quanto risulta il giorno 7.01.2019)
       
      Load Optimized Default Settings Peripherals → USB Configuration → XHCI Hand-off : Enabled Chipset → Internal Graphics : Enabled (important for Quicklook/Preview) Please note that we will be using our internal GPU in headless mode only and this guide assumes that. This is how an iMac18,3 (what we're basing our build on) behaves. That's it! I literally didn't change anything else and it just worked.
       
      Anche per me ha funzionato. Comunque lui riportava ulteriori settaggi, aggiungendo:
       
      However, these are settings that are generally recommended. Your mileage may vary:
       
      BIOS → Fast Boot : Disabled BIOS → LAN PXE Boot Option ROM : Disabled BIOS → Storage Boot Option Control : UEFI Peripherals → Trusted Computing → Security Device Support : Disable Peripherals → Network Stack Configuration → Network Stack : Disabled Peripherals → USB Configuration → Legacy USB Support : Auto Peripherals → USB Configuration → XHCI Hand-off : Enabled (Extremely important) () Chipset → Vt-d : Disabled (non l'ho messo e parte a volte, quindi penso che se parte non ha una importanza così rilevante) Chipset → Wake on LAN Enable : Disabled (era già così) Chipset → IOAPIC 24-119 Entries : Enabled  
       
      Il sistema è partito e soltanto alcune volte dava il seguente errore:
       
      Error allocating 0x11996pages at 0x000000001d453000 alloc type 2
      Couldn't allocate runtime area.
       
      Credo che sia questo piccolo problema: la NVRAM.
      Non riesco bene a capire dove cercare per sapere con esattezza se è supportato nativamente o meno. Ho cercato di informarmi, voi potreste dirmi se è vero?
      Premendo poi Ctrl+Alt+Canc riavviavo e selezionando da Clover l'NVMe interno partiva senza dare questo errore, per cui il kernel non trova spazio perché la memoria Non Volatile ad accesso Randomico è troppo frammentata, come
       
      Questa guida riportava:
       
      Primo post:
      https://nickwoodhams.com/x99-hackintosh-solving-osxaptiofixdrv-allocaterelocblock-can-not-allocate-relocation-block/
       
      Post aggiornato nel 2016:
      https://nickwoodhams.com/x99-hackintosh-osxaptiofixdrv-allocaterelocblock-error-update/
       
      Mi sono letto tutto e ho capito che lui applicava anche delle modifiche al file: "Changes to OsxLowMemFixDrv-64.efi were simply editing 0x10000000 to 0x20000000."
       
      Ho quindi seguito il suo consiglio di mettere OsxAptiofix Emuvariable 64 e Test2-2016.efi (che lui aveva creato) ma il problema sembrava persistere, più raramente
       
      La mia cartella driver64UEFI di ora
       
      Dopo aver trovato una strada senza soluzoni anche lì mi sono rivolto a degli amici, e di questo errore ne ho parlato anche con utenti del gruppo Telegram "Hackintosh Italia" che sono stati e ancora sono molto gentili ad aiutarmi spiegandomi che si tratta di un problema di NVRAM, che nel mio caso, avendo installato questi .efi file nella cartella EFI/EFI/CLOVER/driver64UEFI (che ancora è cosi attualmente, oscillando tra couldnt allocate runtime area (anche dopo aver definitivamente staccato la corrente dopo aver spento il PC per capire se poteva aiutare) e a volta anche nessun errore)
       
       
      -ApfsDriverLoader-64.efi
      -DataHubDxe-64.efi
      -EmuVariableUefi-64.efi
      -FSInject-64.efi
      -HFSPlus-64.efi
      -NTFS-64.efi
      -NvmExpressDxe-64.efi
      -OsxAptioFix2Drv-free2000.efi
      -PartitionDxe-64.efi
      -UsbKbDxe-64.efi
       
      In più ho aggiunto gli RC Scripts (come mi è stato consigliato dai membri del gruppo telegram) sul disco interno in cui mac è installato.
       
      Togliendo quindi qualsiasi test.efi o test2- 2016.efi ed ascoltando chi ne sapeva di più. Ora mi trovo a dover affrontare diverse volte questo errore dovendo riavviare per risolverlo, cosa che mi fa dedurre che Osxaptiofix2 2000 sia un po' instabile nel pulire la NVRAM prima di avviare la macchina/ allo spegnimento di questa.
      Questo problema di couldnt allocate runtime area persiste sebbene prema F12 dalla schermata di Boot di Clover.
       
      Vi chiedo gentilmente una mano, inoltre mi è stato detto che siccome il sistema da:
       
      -"3.6 GHz unknown nella sezione "Processor"
      -non riconosce la RAM con un Vendor ID? (del tipo Ballistix dovrebbe essere?)
       
       
      Serve di rivedere il config.plist che ho creato, rivedere i DSDT e gli efi? sono a posto?, (mi hanno detto che gengik84 fare, ma accolgo volentieri l'aiuto di tutti) ,  vi mando una foto della schermata di "About this Mac" e della EFI in allegato. Quello che farò sicuramente mentre attendo vostre risposte è il downgrade da 10.14.3 Beta a 10.14.2, l'upgrade l'ho fatto pensando che magari avrei aggiustato qualcosa, ma l'errore come lo dava prima lo dà ora, non credo che questo cambi molto le cose in gioco. Comunque è meglio non essere in Beta per aggiustare gli errori.
       
       
      Grazie mille per essere arrivato a leggere fino a questo punto, lo apprezzo molto.
       
       
      Per la cartella EFI: sono 22MB zippati, in allegato non entrano...
       
      https://drive.google.com/open?id=106jXkDB0Id045lzIIzAn9F5MwnzWFv3X
       

       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       

       
       
       
       



    • By kamyar1979
      I have bought a 2nd hand AMD Radeon 7750 to fix my Mojave installation problems. Although the Vendor/Device Id is in AMD7000Controller.Kext, I get a black screen and with some changes a yellow screen. I can not find any useful information to fix that. All information are for High Sierra and older macOS versions. Is there any fix to resolve that? What if I buy an RX 650 for example?
×