System boot loop after Multibeast

[Junaid6305]

I installed Catalina on my Dell Optiplex 5060 (Coffee Lake i7, 2X 8GB). The installation went fine and I restored from my old time machine backup (different hackintosh setup). I ran multibeast and just added
Clover UEFI Bootloader
Virtual SMC
System def iMac 14,2
Graphics - Intel HD 630 (coffee lake)

now I’m stuck in a boot loop but I can boot using my install USB. Also Ethernet, Wifi, bluetooth and sound doesn’t work and the VRAM is only 5MB.

 

[UtterDisbelief]

I installed Catalina on my Dell Optiplex 5060 (Coffee Lake i7, 2X 8GB). The installation went fine and I restored from my old time machine backup (different hackintosh setup). I ran multibeast and just added
Clover UEFI Bootloader
Virtual SMC
System def iMac 14,2
Graphics - Intel HD 630 (coffee lake)

now I’m stuck in a boot loop but I can boot using my install USB. Also Ethernet, Wifi, bluetooth and sound doesn’t work and the VRAM is only 5MB.

Hi there.

As you have copied your Hackintosh setup from a different machine, you need to review the kexts you installed for that build, in Library/Extensions. I assume the EFI partition on the Dell was completely empty before you ran Clover?

 

[Junaid6305]

Hi there.

As you have copied your Hackintosh setup from a different machine, you need to review the kexts you installed for that build, in Library/Extensions. I assume the EFI partition on the Dell was completely empty before you ran Clover?

I restored from my time machine backup then ran multibeast, but I also did run Beast Clean

 

[UtterDisbelief]

I restored from my time machine backup then ran multibeast, but I also did run Beast Clean

Okay ...

... those kexts in Library/Extensions - Lilu, Whatevergreen, AppleALC, USBInjectAll and AHCI-3rdParty-SATA - should be moved to EFI/CLOVER/kexts/Other (some may be there already). Once you've deleted them from L/E then rebuild your kexts caches using the Terminal command: sudo kextcache-i /

...and reboot.

 

[Junaid6305]

I

Okay ...

... those kexts in Library/Extensions - Lilu, Whatevergreen, AppleALC, USBInjectAll and AHCI-3rdParty-SATA - should be moved to EFI/CLOVER/kexts/Other (some may be there already). Once you've deleted them from L/E then rebuild your kexts caches using the Terminal command: sudo kextcache-i /

...and reboot.

In EFI/CLOVER/kexts/Other I’ve got only Lilu.kext and VirtualSMC.kext. The command “sudo kextcache-i” doesn’t work, it just says command not found

 

[Feartech]

I

In EFI/CLOVER/kexts/Other I’ve got only Lilu.kext and VirtualSMC.kext. The command “sudo kextcache-i” doesn’t work, it just says command not found

sudo kextcache -i /

 

[Junaid6305]

Okay ...

... those kexts in Library/Extensions - Lilu, Whatevergreen, AppleALC, USBInjectAll and AHCI-3rdParty-SATA - should be moved to EFI/CLOVER/kexts/Other (some may be there already). Once you've deleted them from L/E then rebuild your kexts caches using the Terminal command: sudo kextcache-i /

...and reboot.

Okay I managed to rebuild the kexts cache (https://www.tonymacx86.com/threads/rebuilding-kernel-cache-in-catalina.285643/) and I still have the same problem. Just reboots with the same error

 

[UtterDisbelief]

I

In EFI/CLOVER/kexts/Other I’ve got only Lilu.kext and VirtualSMC.kext. The command “sudo kextcache-i” doesn’t work, it just says command not found

My apologies. I made a typo and missed a space between the last "e" and the "-" from that command. It should have been : sudo kextcache -i /

... as @Feartech pointed out

On it's own, MultiBeast does not stop a system from booting, quite the contrary. It makes the destiation drive bootable. Something else is going on here.

Sorry to read nothing I'm suggesting is helping.

 

[Junaid6305]

M

My apologies. I made a typo and missed a space between the last "e" and the "-" from that command. It should have been : sudo kextcache -i /

... as @Feartech pointed out

On it's own, MultiBeast does not stop a system from booting, quite the contrary. It makes the destiation drive bootable. Something else is going on here.

Sorry to read nothing I'm suggesting is helping.

No probs. I’m going to try a clean install then run multibeast to see it that works. As you said before it’s possibly my time machine backup with drivers etc from my old setup that could be affecting this.

 

[Junaid6305]

My apologies. I made a typo and missed a space between the last "e" and the "-" from that command. It should have been : sudo kextcache -i /

... as @Feartech pointed out

On it's own, MultiBeast does not stop a system from booting, quite the contrary. It makes the destiation drive bootable. Something else is going on here.

Sorry to read nothing I'm suggesting is helping.

Right so I did a clean install then ran this Multibeast config. After I try boot from my SSD I just get a blank screen (doesn’t show bootloader) the system seems to be on as the caps lock lights still work but I’ve got no display output (I’m using VGA)