Jump to content
ErmaC

Clover General discussion

21,153 posts in this topic

Recommended Posts

15 hours ago, arsradu said:

 

Not that I know of. I mean, there shouldn't be any significant changes that would cause boot issues... But if you could provide more information on what happens exactly, that might help. Maybe a boot log. You could boot in verbose mode and see where does it get stuck. You might need to update your drivers, in case you haven't already. So...there could be multiple issues. But I personally haven't encountered such issues. So...maybe you can also upload your Clover folder for a deeper analysis? You can remove the serials from your config.plist/smbios.

 

Also, I think it might help a lot to know which hardware are you using. Could you, please, update your signature to include this information?

Thanks arsadu, i made updates to my signature. Here is attachment of my current EFI folder (for Dell Vostro from signature with intel HD 620 graphics). I am trying to boot from external SSD attached to USB (It boots up fine with clover 4798, but problematic with latest version 4862)

 

14 hours ago, iCanaro said:

with mojave 10.14.4beta the kernel has been changed and to start it it is necessary to at least clover 2.4_4862 

 

My version of Mojave is 10.14.2 (but similar situation is happening on desktop with update 10.14.3 i.e. boot not possible after clover update)

 

I've made attempts to make screenshots with my phone, but it happens really fast so i don't know if screens are usable to conclude something. Also i have attached my efi folder.

 

Thank you for help.

Regards

BootSCR01.jpg

BootSCR02.jpg

BootSCR03.jpg

BootSCR04.jpg

BootSCR05.jpg

BootSCR06.jpg

BootSCR07.jpg

BootSCR08.jpg

EFI.zip

Share this post


Link to post
Share on other sites
Advertisement
2 hours ago, ktwist said:

Thanks arsadu, i made updates to my signature. Here is attachment of my current EFI folder (for Dell Vostro from signature with intel HD 620 graphics). I am trying to boot from external SSD attached to USB (It boots up fine with clover 4798, but problematic with latest version 4862)

 

 

My version of Mojave is 10.14.2 (but similar situation is happening on desktop with update 10.14.3 i.e. boot not possible after clover update)

 

I've made attempts to make screenshots with my phone, but it happens really fast so i don't know if screens are usable to conclude something. Also i have attached my efi folder.

 

Thank you for help.

Regards

 

 

 

BootSCR04.jpg

 

EFI.zip

Kernel panic VoodooHDA

Edited by HmO

Share this post


Link to post
Share on other sites
9 minutes ago, HmO said:

Kernel panic VoodooHDA

Dam :) that was fast HmO... thank you very very very much

Edited by ktwist

Share this post


Link to post
Share on other sites
2 minutes ago, ktwist said:

Dam :) that was fast HmO... tahnk you verry verry verry much

 

If you can, I would suggest trying AppleAlc.kext + Lilu.kext. That would be an option. Also, in case you want to continue using Voodoohda, which you definitely can, maybe check if it's up to date.

 

Aaand, just in case there is an actual Clover issue, that might have been fixed from the latest official build to the latest available, you can give the attached one a try. See if it still occurs. But you should probably start with fixing the VoodooHDA issue first.

Clover_v2.4k_r4870.zip

Share this post


Link to post
Share on other sites

#Question:

I have 2 config*.plist files:

1. config.plist, it has KextToPatch: A=Enable

2. config_2.plist, with KextToPatch: A=Disable

 

config.plist will be used by default upon Clover boot. When I change it on "Options - Configs" to config_2.plist; can we make KextToPatch value using last changed (config_2.plist) instead of current boot'ed one? (at least, this is what I got on r4870, a bug?). Thanks.

Edited by Badruzeus

Share this post


Link to post
Share on other sites

in 2019, i tested snow leopard installation with latest clover. i still like a snow leopard in 2019.

641646779_2019-02-0211_53_36.thumb.png.36f132f4b74fd5758077982d23eee50b.png

824886483_2019-02-0211_53_56.thumb.png.1787ad41eb679b9ecc747c7e7e85f0d6.png

 

also 

I could not imagine the day that bootchime and Snow Leopard installation video would come together. But recently, thanks to Goldfish64 and Slice, Things I have just imagined in the past have happened recently. Like Old Mac, I felt like a real Mac from the bootchime. After listening to the bootchime, when I listened to the music that came with the installation video, I was able to revive the impression when I first used the Mac. Thank Goldfish64 and Slice again.

 

 

Share this post


Link to post
Share on other sites

Is there away to disable Clover GUI completely and still have bootchime start when the Apple Logo starts? This way to me would make hacks identical to real Macs.   

Nevermind, figured it out. Works like a charm.

Edited by Pavo

Share this post


Link to post
Share on other sites
1 hour ago, Badruzeus said:

#Question:

I have 2 config*.plist files:

1. config.plist, it has KextToPatch: A=Enable

2. config_2.plist, with KextToPatch: A=Disable

 

config.plist will be used by default upon Clover boot. When I change it on "Options - Configs" to config_2.plist; can we make KextToPatch value using last changed (config_2.plist) rather than current boot'ed one? (at least, this is what I got on r4870, a bug?). Thanks.

 

Hmm...that sounds like a bug to me... I mean, if you selected a different config for booting, it should take all the elements of that config into account, right? I mean, that would make sense to me. Otherwise, what would be the point of switching to another config, if you're still getting some of the elements of the initial one upon booting? Are you saying it takes kext-to-patch from config1 rather than config2? Did I get that right?

Edited by arsradu

Share this post


Link to post
Share on other sites
4 minutes ago, arsradu said:

 

Hmm...that sounds like a bug to me... I mean, if you selected a different config for booting, it should take all the elements of that config into account, right? I mean, that would make sense to me. Otherwise, what would be the point of switching to another config, if you're still getting some of the elements of the initial one upon booting? Are you saying it takes kext-to-patch from config1 rather than config2? Did I get that right?

 

Yeah, for example with IntelHD 1st gen; KextToPatch related to GFX Framebuffer only, it has more than 5. I usually boot from config1 with Fake IntelGFX, disabled Framebuffer patches to reach Desktop. Once AppleIntelHDGraphics*.kext are installed; I need using another config w/o Fake IntelGFX and FB patches enabled.. hopefully, w/o rebooting mach to apply.

Share this post


Link to post
Share on other sites
11 minutes ago, Badruzeus said:

 

Yeah, for example with IntelHD 1st gen; KextToPatch related to GFX Framebuffer only, it has more than 5. I usually boot from config1 with Fake IntelGFX, disabled Framebuffer patches to reach Desktop. Once AppleIntelHDGraphics*.kext are installed; I need using another config w/o Fake IntelGFX and FB patches enabled.. hopefully, w/o rebooting mach to apply.

 

I'm a bit confused here. :)) After reaching Desktop, why not use the same config.plist, edit the Fake IntelGFX information and enable FB patches? And what do you mean by "hopefully without rebooting Mac to apply"? Don't you need to reboot to switch to config2 anyway?

 

Anyway, if you selected another config from Clover GUI options....it still sounds like a bug to me if it doesn't take into account all the information from that config. But I'm probably missing some information here.

Edited by arsradu

Share this post


Link to post
Share on other sites

Clover has been like that since before. It doesnt refresh the screen when you switch from config to config2. But nevertheles, switching works when you boot it.

Edited by ellaosx

Share this post


Link to post
Share on other sites
5 hours ago, arsradu said:

 

If you can, I would suggest trying AppleAlc.kext + Lilu.kext. That would be an option. Also, in case you want to continue using Voodoohda, which you definitely can, maybe check if it's up to date.

 

Aaand, just in case there is an actual Clover issue, that might have been fixed from the latest official build to the latest available, you can give the attached one a try. See if it still occurs. But you should probably start with fixing the VoodooHDA issue first.

Clover_v2.4k_r4870.zip

 

 

Using AppleALC + lilu and patching with FB Patcher i made sound to work on Dell Vostro on laptop speakers, but whenever i try to plug headphones in headphone jack, sound works for half a second and then stops.

 

 

Share this post


Link to post
Share on other sites
5 minutes ago, ktwist said:

 

 

Using AppleALC + lilu and patching with FB Patcher i made sound to work on Dell Vostro on laptop speakers, but whenever i try to plug headphones in headphone jack, sound works for half a second and then stops.

 

 

This doesn't belong in this thread, it belongs in 

 

Share this post


Link to post
Share on other sites
6 hours ago, Sherlocks said:

in 2019, i tested snow leopard installation with latest clover. i still like a snow leopard in 2019.

641646779_2019-02-0211_53_36.thumb.png.36f132f4b74fd5758077982d23eee50b.png

824886483_2019-02-0211_53_56.thumb.png.1787ad41eb679b9ecc747c7e7e85f0d6.png

 

also 

I could not imagine the day that bootchime and Snow Leopard installation video would come together. But recently, thanks to Goldfish64 and Slice, Things I have just imagined in the past have happened recently. Like Old Mac, I felt like a real Mac from the bootchime. After listening to the bootchime, when I listened to the music that came with the installation video, I was able to revive the impression when I first used the Mac. Thank Goldfish64 and Slice again.

 

 

How did you get this to work? I can't for the life of me get SL to boot.

Share this post


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

How did you get this to work? I can't for the life of me get SL to boot.

 

Make sure the drive is formatted HFS+ (there was no APFS when SL was launched), and that you also have either HFSPlus.efi or VBoxHFS.efi (added by Clover during installation) in your Drivers64 (legacy boot) or Drivers64UEFI (UEFI boot) folder.

Edited by arsradu

Share this post


Link to post
Share on other sites
On 2/2/2019 at 5:12 PM, Sherlocks said:

in 2019, i tested snow leopard installation with latest clover. i still like a snow leopard in 2019

 

also 

I could not imagine the day that bootchime and Snow Leopard installation video would come together. But recently, thanks to Goldfish64 and Slice, Things I have just imagined in the past have happened recently. Like Old Mac, I felt like a real Mac from the bootchime. After listening to the bootchime, when I listened to the music that came with the installation video, I was able to revive the impression when I first used the Mac. Thank Goldfish64 and Slice again.

 

That's awesome! I've only got one question: HOW? :))

 

Could you post a tutorial on how to achieve that? I couldn't even get it to boot into the installer. With FakeCPUId and everything. I get all kinds of errors. I started hackintoshing with Mavericks. And that worked pretty smoothly. I also did my best to do a little bit of research beforehand and pick up compatible components, and that definitely paid off, but even so, it went pretty smoothly and I've got very few issues to fix after that (mainly sound and ethernet). I couldn't imagine it would be so difficult to get older versions of Mac OS to boot. :)) Downgrading Clover didn't help either. 

 

Anyway, just so we don't spam this thread with stuff like this (since I'm not sure the errors are Clover related), would it be possible to create a new one with step-by-step on what to do to get it working? That would be awesome.

 

Anyway, getting that to work, to me is really impressive. Well done.

Edited by arsradu

Share this post


Link to post
Share on other sites
25 minutes ago, ellaosx said:

why not try it

He probably did try and was asking if it was possible to support. Afterall audio is currently a theme thing and no theme is loaded with fast boot.

Edited by Download-Fritz

Share this post


Link to post
Share on other sites
On 2/3/2019 at 6:35 AM, arsradu said:

 

Make sure the drive is formatted HFS+ (there was no APFS when SL was launched), and that you also have either HFSPlus.efi or VBoxHFS.efi (added by Clover during installation) in your Drivers64 (legacy boot) or Drivers64UEFI (UEFI boot) folder.

HFSPlus and are in my Drivers64 folder and I only have HFS+ drives on my system.

Share this post


Link to post
Share on other sites

Maybe I missed it but can someone explain the need for FSInject and SMCHelper? I forgot to install them the last time and my machine boots and works just fine? Are they unnecessary for non-UEFI mobos? Or is it just not needed for High Sierra?

 

Also, not sure if this is really a needed fix but...when I got to install Clover, UEFI drivers are check by default and no BIOS drivers are checked even though the installer has "Clover EFI 64-bits BiosBlockIO" checked by default. So I assume the installer knows this is a legacy BIOS install.

 

I always have to uncheck the UEFI drivers and check the BIOS drivers I need.

Share this post


Link to post
Share on other sites
21 minutes ago, pkdesign said:

Maybe I missed it but can someone explain the need for FSInject and SMCHelper? I forgot to install them the last time and my machine boots and works just fine? Are they unnecessary for non-UEFI mobos? Or is it just not needed for High Sierra?

 

Also, not sure if this is really a needed fix but...when I got to install Clover, UEFI drivers are check by default and no BIOS drivers are checked even though the installer has "Clover EFI 64-bits BiosBlockIO" checked by default. So I assume the installer knows this is a legacy BIOS install.

 

I always have to uncheck the UEFI drivers and check the BIOS drivers I need.

 

FS-Inject: is responsible for kext injection from Clover folder

SMCHelper: Restores SMC keys left in NVRAM by FakeSMC.

 

Now wether or not they're required for non-UEFI motherboards..., that I don't know. But since they're both under Drivers64UEFI, my guess is that they might not be...? Although...in order to boot, you still need FakeSMC, right? Which still needs to be injected from Clover/kexts. So...I really don't know.

 

Also, what you're describing looks more like a missing feature, maybe, more than a bug. But if my theory is correct and none of the Drivers64UEFI files is necessary for legacy booting...then, I guess there's just a matter of checking whether or not Clover Legacy is selected, before displaying UEFI drivers.

 

I don't know. I could be talking stupid. So don't take my word for it. Maybe someone has a better idea and understanding of what's going on in this case and whether or not those UEFI drivers should be checked when selecting Legacy booting. I personally haven't used that in a veeeery long time.

Edited by arsradu

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 rodrinico19
      Hola a todos, primero que nada estoy muy contento de a ver econtrado un foro de español sobre hackintosh.
      Mi problema consesite en que descargue unos drivers de esta pagina: https://github.com/chris1111/Wireless-USB-Adapter-Clover
      Seguí los pasos instale los kets en la carpeta EFI/CLOVER/OTHERS todo tal cual como dice ahi la instalación. luego segui los pasos de configurar la red dentro de configuracion del sistema etc.
      Lo cual el nombre me quedo en en0.
      El driver o kets funciona bien es reconocible por el S.O de hecho conecta la red, pero me dice que no tiene IP AUTO ASIGNADA Y LA OTRA QUE HAY UNA DESCONEXION A CADA RATO(como que desconectaras y conectaras el dispositvo usb a cada rato)
      Me gustaria que me ayuden con eso si es posible, Muchas Gracias!!
    • By Klaidonis
      I am making a minimal Clover build for the fastest boot possible with the boot6 file in legacy mode.
      While looking at the preboot.log, I noticed that there is a line without explanation (at 0:892). Apparently, whatever it is, the execution time of it is close to 2 seconds, more than 55% of the total logged boot time in the current configuration. This does not change whether I use USB 2 or USB 3 port.
       
      Is there a way to eliminate or speed up the above? Also, is there anything else you can suggest to improve the performance based on the below log file? Which moment in the boot process corresponds to the start time in preboot.log?  
      The last thing I would like to understand is the delay/timeout after the boot6 file has loaded, and the number 6 disappears from the screen. For about 2 seconds or slightly less, I can press any key, and then it will enter the BIOS-like interface from the boot6 file. Without further knowledge, it seems like those 2 seconds are just delay time, and only after that is CLOVERX64.efi actually started, which, I presume, is approximately when the preboot.log timer starts. So, if the aforementioned is correct, can I get rid of this delay as well? Note that I am using the boot1f32 file to chain-load boot6, which does not include the initial 2-second wait period for a keypress.
       
      === preboot.log ===
      0:100 0:100 MemLog inited, TSC freq: 2394459554 0:100 0:000 CPU was calibrated with ACPI PM Timer 0:100 0:000 LegacyRegion2: Chipset/proc: 0x0A048086 0:100 0:000 Next Generation Core processors (PAM 0x80-0x86) 0:100 0:000 Test PAM1=(0x41=90, 0x5a=90, 0x81=11, 0x91=00) at chipset 0A048086 0:100 0:000 , Install = Success 0:112 0:012 BiosVideoDriverBindingStart! 0:112 0:000 BiosVideoCheckForVbe 0:112 0:000 EdidOverride not found 0:121 0:009 Edid1+ 0:121 0:000 found Detail Timing 1920x1080 0:121 0:000 timing string after 0xFE:AUO 0:121 0:000 timing string after 0xFE:B156HAN01.2 0:122 0:000 0 1280x1024 attr=9B - ok, edid- 0:122 0:000 1 1024x768 attr=9B - ok, edid-, 1024x768, working, highest, pref=1 0:122 0:000 2 640x480 attr=9B - ok, edid-, 640x480, working 0:122 0:000 3 800x600 attr=9B - ok, edid-, 800x600, working 0:123 0:000 4 1920x1080 attr=9B - ok, edid+, working, highest, pref=4 0:123 0:000 BV new mode: 4 1920x1080 0:398 0:275 SetMode pref 4 (4) = Success 0:892 0:493 VGA Pci.Hdr.Command=6 - not enabled 2:623 1:731 2:623 0:000 Now is 21.02.2020, 13:03:21 (GMT) 2:623 0:000 Starting Clover revision: 5103 (master, commit 3f3b85da0) on CLOVER EFI 2:623 0:000 Build with: [Args: -D NO_GRUB_DRIVERS_EMBEDDED -t GCC53 | -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/sergey/src/CloverHackyColor/Conf -D USE_LOW_EBDA -a X64 -b RELEASE -t GCC53 -n 5 | OS: 10.14.6] 2:623 0:000 SelfDevicePath=PcieRoot(0x0)\Pci(0x1D,0x0)\USB(0x0,0x0)\USB(0x4,0x0)\HD(1,MBR,0x04944021,0x3F,0x3BC1042) @940C9698 2:623 0:000 SelfDirPath = \EFI\CLOVER 2:623 0:000 SimpleTextEx Status=Success 2:623 0:000 === [ Get Smbios ] ======================================== 2:623 0:000 Type 16 Index = 0 2:623 0:000 Total Memory Slots Count = 2 2:623 0:000 Type 17 Index = 0 2:623 0:000 SmbiosTable.Type17->Speed = 1600MHz 2:623 0:000 SmbiosTable.Type17->Size = 4096MB 2:623 0:000 SmbiosTable.Type17->Bank/Device = BANK 0 DIMM0 2:623 0:000 SmbiosTable.Type17->Vendor = Hynix 2:623 0:000 SmbiosTable.Type17->SerialNumber = 00000000 2:623 0:000 SmbiosTable.Type17->PartNumber = HMT451S6MFR6A-PB 2:623 0:000 Type 17 Index = 1 2:623 0:000 SmbiosTable.Type17->Speed = 1600MHz 2:623 0:000 SmbiosTable.Type17->Size = 8192MB 2:623 0:000 SmbiosTable.Type17->Bank/Device = BANK 2 DIMM1 2:623 0:000 SmbiosTable.Type17->Vendor = Kingston 2:623 0:000 SmbiosTable.Type17->SerialNumber = 5A060A8A 2:623 0:000 SmbiosTable.Type17->PartNumber = KHX1600C9S3L/8G 2:623 0:000 Boot status=0 2:623 0:000 Running on: 'Aspire V5-573G' with board 'Dazzle_HW' 2:623 0:000 === [ GetCPUProperties ] ================================== 2:623 0:000 CPU Vendor = 756E6547 Model=40651 2:623 0:000 The CPU supported SSE4.1 2:623 0:000 BrandString = Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz 2:623 0:000 The CPU supported turbo 2:623 0:000 MSR 0x35 20004 2:623 0:000 MSR 0xE2 before patch 1E008405 2:623 0:000 MSR 0xE2 is locked, PM patches will be turned on 2:623 0:000 MSR 0xCE 0008083D_F3011800 2:623 0:000 corrected FLEX_RATIO = 0 2:623 0:000 MSR 0x1B0 00000000 2:623 0:000 FSBFrequency = 71 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 MHz 2:623 0:000 MaxDiv/MinDiv: 24.0/8 2:623 0:000 Turbo: 27/27/27/30 2:623 0:000 Features: 0xBFEBFBFF 2:623 0:000 Threads: 4 2:623 0:000 Cores: 2 2:623 0:000 FSB: 100 MHz 2:623 0:000 CPU: 1700 MHz 2:623 0:000 TSC: 1700 MHz 2:623 0:000 PIS: 100 MHz 2:623 0:000 ExternalClock: 25 MHz 2:623 0:000 === [ GetDevices ] ======================================== 2:623 0:000 GOP found at: PcieRoot(0x0)/Pci(0x2,0x0)/AcpiAdr(0x80010100) 2:623 0:000 PCI (00|00:00.00) : 8086 0A04 class=060000 2:623 0:000 PCI (00|00:02.00) : 8086 0A16 class=030000 2:623 0:000 - GOP: Provided by device 2:623 0:000 - GFX: Model=Intel HD Graphics 4400 (Intel) 2:623 0:000 PCI (00|00:03.00) : 8086 0A0C class=040300 2:623 0:000 PCI (00|00:14.00) : 8086 9C31 class=0C0330 2:623 0:000 PCI (00|00:16.00) : 8086 9C3A class=078000 2:623 0:000 PCI (00|00:1B.00) : 8086 9C20 class=040300 2:623 0:000 PCI (00|00:1C.00) : 8086 9C10 class=060400 2:623 0:000 PCI (00|00:1C.02) : 8086 9C14 class=060400 2:623 0:000 PCI (00|04:00.00) : 168C 0034 class=028000 2:623 0:000 - WIFI: Vendor=Atheros 2:623 0:000 PCI (00|00:1C.03) : 8086 9C16 class=060400 2:623 0:000 PCI (00|05:00.00) : 10EC 5287 class=FF0000 2:623 0:000 PCI (00|05:00.01) : 10EC 8168 class=020000 2:623 0:000 - LAN: 0 Vendor=Realtek 2:623 0:000 PCI (00|00:1C.04) : 8086 9C18 class=060400 2:624 0:000 PCI (00|01:00.00) : 10DE 0FE4 class=030200 2:624 0:000 PCI (00|00:1D.00) : 8086 9C26 class=0C0320 2:624 0:000 PCI (00|00:1F.00) : 8086 9C43 class=060100 2:624 0:000 PCI (00|00:1F.02) : 8086 9C03 class=010601 2:624 0:000 PCI (00|00:1F.03) : 8086 9C22 class=0C0500 2:624 0:000 === [ GetDefaultSettings ] ================================ 2:624 0:000 Clover load options size = 0 bytes 2:624 0:000 CheckOEMPathExists tried EFI\CLOVER\OEM\Aspire V5-573G--00-00-00-00-00-00. Dir not exists 2:624 0:000 CheckOEMPathExists tried EFI\CLOVER\OEM\Aspire V5-573G. Dir not exists 2:624 0:000 CheckOEMPathExists tried EFI\CLOVER\OEM\Aspire V5-573G-1700. Dir not exists 2:624 0:000 CheckOEMPathExists tried EFI\CLOVER\OEM\Dazzle_HW. Dir not exists 2:624 0:000 CheckOEMPathExists tried EFI\CLOVER\OEM\Dazzle_HW-1700. Dir not exists 2:624 0:000 set OEMPath by default: EFI\CLOVER 2:637 0:012 EFI\CLOVER\config.plist loaded: Success 2:637 0:000 === [ GetListOfThemes ] =================================== 2:637 0:000 === [ Found config plists ] =============================== 2:637 0:000 - config.plist 2:637 0:000 === [ GetEarlyUserSettings ] ============================== 2:637 0:000 timeout set to 0 2:637 0:000 Custom boot CUSTOM_BOOT_DISABLED (0x0) 2:637 0:000 Default theme: embedded 2:637 0:000 === [ LoadDrivers ] ======================================= 2:637 0:000 === [ InitScreen ] ======================================== 2:637 0:000 Console modes reported: 4, available modes: 2:637 0:000 - [01]: 80x25 2:637 0:000 - [02]: 80x50 2:637 0:000 - [03]: 100x31 2:637 0:000 - [04]: 240x56 (current mode) 2:637 0:000 SetScreenResolution: 1920x1080 - already set 2:637 0:000 SetScreenResolution: 1920x1080 - already set 2:637 0:000 reinit: self device path=PcieRoot(0x0)\Pci(0x1D,0x0)\USB(0x0,0x0)\USB(0x4,0x0)\HD(1,MBR,0x04944021,0x3F,0x3BC1042) 2:637 0:000 === [ GetMacAddress ] ===================================== 2:637 0:000 === [ ScanSPD ] =========================================== 2:637 0:000 Scanning SMBus [8086:9C22], mmio: 0xB3619004, ioport: 0x5040, hostc: 0x1 2:656 0:018 Slot: 2 Type 24 8192MB 1600MHz Vendor=Kingston PartNo=KHX1600C9S3L8G SerialNo=050A0006000A080A 2:657 0:000 === [ GetAcpiTablesList ] ================================= 2:657 0:000 Get Acpi Tables List from RSDT: 2:657 0:000 - [00]: FACP ACRPRDCT len=268 2:657 0:000 - [01]: UEFI ACRPRDCT len=566 2:657 0:000 - [02]: FPDT ACRPRDCT len=68 2:657 0:000 - [03]: ASF! ACRPRDCT len=165 2:657 0:000 - [04]: HPET ACRPRDCT len=56 2:657 0:000 - [05]: APIC ACRPRDCT len=140 2:657 0:000 - [06]: MCFG ACRPRDCT len=60 2:657 0:000 - [07]: BOOT ACRPRDCT len=40 2:657 0:000 - [08]: LPIT ACRPRDCT len=148 2:657 0:000 - [09]: ASPT ACRPRDCT len=52 2:657 0:000 - [10]: DBGP ACRPRDCT len=52 2:657 0:000 - [11]: SSDT ACRPRDCT len=1337 2:657 0:000 - [12]: SSDT ACRPRDCT len=2776 2:657 0:000 - [13]: SSDT ACRPRDCT len=12013 2:657 0:000 - [14]: SSDT ACRPRDCT len=11433 2:657 0:000 - [15]: SSDT ACRPRDCT len=2230 2:657 0:000 Calibrated TSC Frequency = 2394459554 = 2394MHz 2:657 0:000 === [ GetUserSettings ] =================================== 2:657 0:000 === [ Found DSDT tables ] ================================= 2:657 0:000 === [ ScanVolumes ] ======================================= 2:657 0:000 Found 8 volumes with blockIO 2:657 0:000 - [00]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0) 2:659 0:001 Result of bootcode detection: bootable Linux (grub,linux) 2:659 0:000 - [01]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0) 2:660 0:001 Result of bootcode detection: bootable unknown (legacy) 2:660 0:000 - [02]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(1,GPT,8017BD66-1E24-4B31-8E09-BC49BECD6CC4,0x800,0x21330000) 2:661 0:001 Result of bootcode detection: bootable Windows (vista,win) 2:661 0:000 - [03]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,GPT,82F3B738-65E9-458E-B2F1-BB55D4F00885,0x21331000,0x3D0800) 2:663 0:001 - [04]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(3,GPT,E701DCD8-E3C5-4BFA-B61B-BFF4D80153FD,0x21701800,0x18C4F000) 2:664 0:001 - [05]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(4,GPT,4DB1239A-A9D7-4045-A162-7EF1B3A5913B,0x3A350C21,0x3A3B616E) 2:665 0:001 Result of bootcode detection: bootable Windows (vista,win) 2:665 0:000 - [06]: Volume: PcieRoot(0x0)\Pci(0x1D,0x0)\USB(0x0,0x0)\USB(0x4,0x0) 2:677 0:011 Result of bootcode detection: bootable unknown (legacy) 2:677 0:000 USB volume 2:677 0:000 USB volume 2:677 0:000 - [07]: Volume: PcieRoot(0x0)\Pci(0x1D,0x0)\USB(0x0,0x0)\USB(0x4,0x0)\HD(1,MBR,0x04944021,0x3F,0x3BC1042) 2:688 0:011 Result of bootcode detection: bootable unknown (legacy) 2:688 0:000 USB volume 2:688 0:000 USB volume 2:688 0:000 This is SelfVolume !! 2:688 0:000 PutNvramPlistToRtVars: nvram.plist not found 2:689 0:000 No AudioIoProtocols, status=Not Found 2:689 0:000 === [ InitTheme ] ========================================= 2:689 0:000 use daylight theme 2:689 0:000 using embedded theme 2:689 0:000 got embedded sound 2:689 0:000 Channels: 2 Sample rate: 8000 Hz Bits: 16 2:689 0:000 output to channel 0 with volume 70, len=25600 2:689 0:000 sound channels=2 bits=16 freq=8000 2:689 0:000 sound converted to 48kHz 2:689 0:000 not found AudioIo to play 2:689 0:000 sound play end with status=Not Found 2:690 0:001 Using embedded font: Success 2:691 0:000 theme inited 2:691 0:000 Chosen embedded theme 2:691 0:000 after NVRAM boot-args= 2:691 0:000 === [ Dump SMC keys from NVRAM ] ========================== 2:691 0:000 no AppleSMC protocol 2:691 0:000 Entry scan disabled 2:691 0:000 === [ AddCustomTool ] ===================================== 2:692 0:000 === [ GetEfiBootDeviceFromNvram ] ========================= 2:692 0:000 Default boot entry not found 2:692 0:000 DefaultIndex=-1 and MainMenu.EntryCount=4 2:973 0:281 GUI ready  
    • By Jancey
      I used this command: diskutil info disk0s2 | grep -i "Partition UUID" | rev | cut -d' ' -f 1 | rev

      But I accidentally removed the wrong disk and now my main windows drive is not appearing in the bootloader. I can't figure out how to get it back. I tried resetting my windows drive, but I kept getting an error. I also reset my mac and reinstalled Catalina.
    • By gengstapo
      @Hervé
       
      Im having similar issue with my HS setup, dell latitute 3480, i5-7200U
      Once the hdmi plugged in, the laptop display went blank, only could see the external tv
      But, when i put my laptop to sleep & wake up again, both screen got display (hdmi still connected)
      Even the hdmi could be plugged off & in (after sleep), the laptop display is fine
       
      What could be the culprit?
      Dell’s MacBook Pro IORegistry.zip
      config.plist.zip
    • By TomZanna
      Hi, I'm trying to install Mac Os Catalina on a HP 550-132NL.
      The system has:
      i7-6700
      RAM 12 GB
      GT 730
      LAN Realtek RTL8161
      ALC3863
       
      It passes the verbose phase but after the Apple logo goes away, it gets stuck on a grey screen and I can only move the pointer.
      Can I try to boot with the iGPU?
       
      origin.zip
      CLOVER_dGPU_USB_3.zip
×