Jump to content

asapreta

Members
  • Content Count

    127
  • Joined

  • Last visited

  • Days Won

    1

asapreta last won the day on June 23

asapreta had the most liked content!

Community Reputation

4 Neutral

About asapreta

  • Rank
    Geek

Hackintosh Specs

  • CPU
    i5 9500F
  • Motherboard
    Gigabyte Z390 Gaming X
  • GPU
    RX 570 4 GB

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Just a question: is it normal not to have the Volume slider available to control it under HDMI (via RX570 from the rig below)? thanks!
  2. Eu realmente tenho visto que está havendo um stress meio exagerado para o sistema que nem é final para rodar nas máquinas. Acho que como está, tendo boot com o OC já é um grande avanço. Ontem mesmo nos testes tive problemas em mudar as kexts e tentar atualizar o OC. Perdi o boot. Muito possivelmente por desconhecimento do OC. O que fiz, deixei para lá, já que consegui bootar com minha DSDT. Depois vejo como atualizar as Kexts/OC sem dar pau. Não é meu sistema de uso diário, então não tem prioridade. Obrigado pelo suporte.
  3. Blz, aparentemente está tudo ok. Adicionei o alcid=1 para ter o som da placa mãe nas configs e foi. Só tenho uma dúvida, vejo que muita gente tem falando para não usar o WhateverGreen.kext e uma outra flag na boot string porque elas ficaram desnecessárias. Acho que são as: -lilubetaall e vsmcgen=1, isso confere? A minha está assim: -v -lilubetaall keepsyms=1 debug=0x100 vsmcgen=1 alcid=1 E as KEXTs atualizadas pelo comando de recompilar tem duas que são mais antigas eu acho que estão na pasta PREMADE, e mantive elas a USBInjectAll.kext e a XHCI-unsupported.kext. Como você montou a pasta premade num config parecido com o meu, devem ser necessárias.
  4. Okay, vou comparar aqui, compilar os kexts e testar. Muito obrigado pelo suporte, até para um sistema que nem é o de uso diário, ainda em beta. Deixa eu tirar apenas uma última dúvida, naquela pasta EFI premade para a instalação USB que está disponivel para download, tem um SSDT, removo ele ao usar a minha DSDT?
  5. Vou tentar aqui. No caso é usar o DSDT do Catalina e ajustar a pasta EFI para o Big Sur?
  6. Tem como o mestre fazer um para esse meu Big Sur? Eu já postei o sendme no tópico das requisições de DSDT. Agradeço desde já.
  7. Hi Mald0n, I couldn't do it before, here is the sendme.zip from my Big Sur "installation" for fine tunning as I am using your EFI from the z390 M gaming Board and I have the Z390 Gaming X one. https://www.sendspace.com/file/zdedla I noticed while the script was running these errors while grabbing the IOREG stuff: Saving IOReg... IOREG dump failed. Retrying by increasing delays... Increased delay by x2 times. Retrying... IOREG dump failed. Retrying by increasing delays... Increased delay by x3 times. Retrying... IOREG dump failed. Retrying by increasing delays... IOREG dump has failed 3 times. Dumping generic IOREG report instead. No matching processes belonging to you were found I ran IOReg and saved it, attached to the post, if needed. Thanks admin’s iMac.ioreg.zip
  8. Acho que o pessoal anda meio "estressado" para rodar o sistema que nem é final mas enfim... Talvez seja para estar preparado para Setembro. Aqui como disse rolou bem a instalação via USB, conseguir ativar o audio da placa-mãe com a DSDT de outro post sobre o Big Sir da Z390M Gaming na minha Gaming X e aparentemente tudo funciona. Talvez mais pro futuro possa ter um fine tune do DSDT específico para essas Z390 Gaming X pois, por desconhecimento, acho que tem vários erros reportados durante o boot, como por exemplo: 2020-07-10 09:27:24.277654-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Exception: AE_NOT_FOUND, 2020-07-10 09:27:24.277654-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Exception: AE_NOT_FOUND, 2020-07-10 09:27:24.278333-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) During name lookup/catalog 2020-07-10 09:27:24.278334-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) During name lookup/catalog 2020-07-10 09:27:24.278922-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/psobject-310) 2020-07-10 09:27:24.278922-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/psobject-310) 2020-07-10 09:27:24.288899-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error: 2020-07-10 09:27:24.288900-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error: 2020-07-10 09:27:24.289173-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) Method parse/execution failed 2020-07-10 09:27:24.289173-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) Method parse/execution failed 2020-07-10 09:27:24.289849-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [\] (Node ffffff801410b780) 2020-07-10 09:27:24.289850-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [\] (Node ffffff801410b780) 2020-07-10 09:27:24.290460-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) , AE_NOT_FOUND 2020-07-10 09:27:24.290461-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) , AE_NOT_FOUND 2020-07-10 09:27:24.290781-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/psparse-632) 2020-07-10 09:27:24.290781-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/psparse-632) 2020-07-10 09:27:24.301038-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error: 2020-07-10 09:27:24.301038-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error: 2020-07-10 09:27:24.301312-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [\_SB_.PCI0.XHC_.RHUB.SS07] 2020-07-10 09:27:24.301313-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [\_SB_.PCI0.XHC_.RHUB.SS07] 2020-07-10 09:27:24.301922-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) Namespace lookup failure, AE_NOT_FOUND 2020-07-10 09:27:24.301922-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) Namespace lookup failure, AE_NOT_FOUND 2020-07-10 09:27:24.302806-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/dswload2-274) 2020-07-10 09:27:24.302806-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/dswload2-274) 2020-07-10 09:27:24.312958-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) 2020-07-10 09:27:24.312958-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) 2020-07-10 09:27:24.322554-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) No Local Variables are initialized for method ["\" ] 2020-07-10 09:27:24.322555-0300 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) No Local Variables are initialized for method ["\" ] Até vou deixar o trecho maior do log anexado caso seja do interesse para análise. E como sempre a comunidade rapidamente deu recursos e conseguiu vencer as dificuldades para a instalação do novo sistema que tem um boot completamente novo. boot log.rtf.zip
  9. Tento rodar os comandos do começo mas recebo essa mensagem de erro mesmo com o Xcode 12 instalado: xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance cp: ./Release/Lilu.kext: No such file or directory cp: ./Release/Lilu.kext: No such file or directory cp: ./Release/Lilu.kext: No such file or directory cp: ./Release/Lilu.kext: No such file or directory cp: ./Release/Lilu.kext: No such file or directory cp: ./Release/Lilu.kext: No such file or directory cp: ./Release/Lilu.kext: No such file or directory cp: ./Release/Lilu.kext: No such file or directory cp: ./Release/Lilu.kext: No such file or directory cp: ./Release/Lilu.kext: No such file or directory cp: ./Release/Lilu.kext: No such file or directory cp: ./Release/Lilu.kext: No such file or directory cp: ./Release/Lilu.kext: No such file or directory cp: ./Release/Lilu.kext: No such file or directory cp: ./Release/Lilu.kext: No such file or directory ##### !!! START BUILD FILES !!! ##### xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance ##### !!! DONE !!! ##### [email protected] Desktop % E o line tools também está instalado. O que poderia ser? << EDIT:>> Acho que corrigi forçando usar o Xcode direto com esse comando: sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
  10. Restarted then I saw the Big Sur drive and selected it.
  11. Instalou aqui. Usei a imagem USB e a pasta efi para as séries 100/200/300... Do primeiro post já que tenho uma z390 Gaming X. Mas reparei umas coisas. Limpei a nvram e iniciei a instalação. Até aí tudo bem, rolou uma parte que mostra até uns 3 minutos e rebootou e fez a segunda parte que leva bem mais tempo. Rebootou. Achei estranho que não apareceu o drive para bootar. Tinha o macosInstaller. Tentei rodar (achando que era uma parte final) e ficou muito, mas muito tempo (e eu já havia lido que tem partes que podia demorar muito e esperei. Mas ficou num lugar que muita gente fica travada: Forcing CS_RUNTIME for entitlement... Resolvi ver se na bios a porta serial estava desativada, porque li relatos que o "travamento" nesse ponto seria isso, mas nem achei essa opção na versão nova da minha bios. Tinha antes. Rebootei e para minha surpresa apareceu o HD e consegui ir para a parte de configurar o Big Sur. Ou seja, acho que está instalado. A única diferença que percebi é que o áudio da placa mãe não funciona, e funciona na versão RESTORE do Big Sur. Já estou voltando somente pelo HD com a mesma pasta que usei no pendrive. De repente é bobeira o som. EDIT: Usei o DSDT que tem aqui no fórum para a Z390M Gaming (mesmo a minha sendo a Z390 Gaming X), fazendo a entrada também no config.plist além de copiar o arquivo para a pasta ACPI e voltei a ter o som da Placa Mae. Acho que agora seria um fine tune desse DSDT mas como é um Beta, pode-se esperar. Obrigado Mald0n por prover o USB e arquivos.
  12. Now I got it, thanks! Will try later and report what happened.
  13. It will be a silly question, but the Olarila Big Sur image now is a Bootable USB one? Then, After install I use the pre-made EFI folder for my Coffee Lake setup?
  14. Hi Mald0n, I couldn't do it before, here is the sendme.zip from my Big Sur "installation" for fine tunning as I am using your EFI from the z390 M gaming Board and I have the Z390 Gaming X one. https://www.sendspace.com/file/eebhtm I noticed while the script was running these errors while grabbing the IOREG stuff: Saving IOReg... IOREG dump failed. Retrying by increasing delays... Increased delay by x2 times. Retrying... IOREG dump failed. Retrying by increasing delays... Increased delay by x3 times. Retrying... IOREG dump failed. Retrying by increasing delays... IOREG dump has failed 3 times. Dumping generic IOREG report instead. No matching processes belonging to you were found I ran IOReg and saved it, attached to the post, if needed. Thanks admin’s iMac.zip
×
×
  • Create New...