Multiboot in Clover

[alisudo]

Hi, I installed Linux, Windows and macOS on my laptop. The problem is when I boot to windows from clover, I get no audio output. But when I boot directly from EFI boot entry (bios menu), everything is fine. Also booting is slow from Clover, But windows boots normal when I choose it from bios menu. I guess the clover applies some patches to all operating systems.

I couldn't start linux from Clover either. I followed this guid to boot Arch Linux, But it didn't work. I chainloaded Grub that is meant to load Arch Linux. But it wouldn't boot. I think this is because of the same problem I faced with windows. clover doesn't boots other OSes "vanila".

How can I boot to OSes other than macOS as if I chose it from bios efi entry, without applying patches to DSDT, etc?

 

[UtterDisbelief]

Hi, I installed Linux, Windows and macOS on my laptop. The problem is when I boot to windows from clover, I get no audio output. But when I boot directly from EFI boot entry (bios menu), everything is fine. Also booting is slow from Clover, But windows boots normal when I choose it from bios menu. I guess the clover applies some patches to all operating systems.

I couldn't start linux from Clover either. I followed this guid to boot Arch Linux, But it didn't work. I chainloaded Grub that is meant to load Arch Linux. But it wouldn't boot. I think this is because of the same problem I faced with windows. clover doesn't boots other OSes "vanila".

How can I boot to OSes other than macOS as if I chose it from bios efi entry, without applying patches to DSDT, etc?

Hi there.

Interesting ...

If all your OS's are UEFI then each puts its own code in the EFI partition of a GPT/GUID disk. For example take a look and you'll see a Microsoft sub-folder in there. Each one puts its own boot-code on the partition and this can cause confusion. It is always safer to install to separate physical drives, but you can't do this easily on a laptop. Booting using the BIOS selector is safest.

No, Clover doesn't apply patches to Linux and Windows, although once loaded it can prevent BIOS RTC. The problem you have of audio not working is not necessarily caused by Clover because the modern way we configure macOS audio is with a kext - AppleALC - and this is injected by Clover after the drive is selected, so it shouldn't affect Windows or Linux.

However, as you say, you get audio in macOS but not in Windows when you swap, so something is happening and I suspect it is more to do with hardware or the laptop BIOS, rather than Clover. For example, you often find that wi-fi will not work in macOS after you have been running Windows. The way around this is to simply turn-off wi-fi from the menu-bar, then turn it back on again. This might be related to NVRAM or simply an area of non-volatile RAM in the wireless, or in your case audio, chipset.

 

[alisudo]

Thank you @UtterDisbelief, for your answer. You're right, `kext` patches would be applied after booting macOS.
I can boot windows either from bios boot menu or from Clover. the latter will cause some problems (slow startup and audio issues, I noticed for now) but the former method is quite fine. These two methods are only different in the way I boot Windows. So the issue has to be the way Clover is booting Windows.

 

[UtterDisbelief]

Thank you @UtterDisbelief, for your answer. You're right, `kext` patches would be applied after booting macOS.
I can boot windows either from bios boot menu or from Clover. the latter will cause some problems (slow startup and audio issues, I noticed for now) but the former method is quite fine. These two methods are only different in the way I boot Windows. So the issue has to be the way Clover is booting Windows.

Fair enough

In that case when you get to the Clover menu move the cursor to the Options menu and disable all the injections and patches. Press Spacebar the drive menu and again, deselect the preselected items.

Boot your Windows drive. It should be, hopefully, as if you booted from BIOS.

Once confirmed you can add back the settings one at a time until you discover the one causing the problem with audio.