Jump to content
ErmaC

Clover General discussion

19,684 posts in this topic

Recommended Posts

Advertisement
Posted (edited)

Guys I need your help, I'm trying to debug a problem and the only variables remaining are a custom kernel and clover. When I try to boot to high Sierra with a custom kernel with the latest clover it hangs with a "kextd stall [0]: AppleACPICPU" message while if I use the old 4392 the pc boots. I have the same kexts in /kext/others and the same efi files in driver64uefi. What am I missing? 

Edited by innerd

Share this post


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

Guys I need your help, I'm trying to debug a problem and the only variables remaining are a custom kernel and clover. When I try to boot to high Sierra with a custom kernel with the latest clover it hangs with a "kextd stall [0]: AppleACPICPU" message while if I use the old 4392 the pc boots. I have the same kexts in /kext/others and the same efi files in driver64uefi. What am I missing? 

Different config, different ACPI files.

Make preboot.log by F2 key with old and with new Clover and compare.

Share this post


Link to post
Share on other sites
Posted (edited)
8 hours ago, ellaosx said:

How come there is no AptioMemoryFix in the new package?

 

It wasn't included with newer packages anymore. That's kind of the idea. To stick to default Clover drivers. If you have AptioMemoryFix installed already, and you don't check for installation any of the other Memory Fix drivers (such as OsXAptioFix3Drv), it will be kept installed. If you choose one of them, AptioMemoryFix will be removed (and replaced with whichever AptioFix you choose) in order to avoid conflicts.

Edited by arsradu

Share this post


Link to post
Share on other sites
Posted (edited)
17 hours ago, Sherlocks said:

strangely i can't install only clover without terminal command. 

i'm still in Beta1. So it's working for me because of this? ... to night I'll update to Beta 3 and see what's.. Anyway I consider only the root volume ("/") and not if you install Clover from another partition as from Maojave the Catalina partition is read/write in Beta 1 ... can be this the problem?

 

17 hours ago, Sherlocks said:

also i have a question. previous clover package have checked default driver. there is no default driver in new package. is it right?

No, the installer activate them by default if Clover was never installed, i.e. if ../Library/Preferences/com.projectosx.clover.installer.plist doesn't exist. Due to the fact that I changed something at least once you have to mark chekboxes. Next run will be ok.

The proof is by deleting com.projectosx.clover.installer.plist and you will see them activated. Little price for this migration.

 

P.S. my system works very well without any of the "Recommended drivers", those who once was "Mandatory".

12 hours ago, ellaosx said:

How come there is no AptioMemoryFix in the new package?

You can see it in the Clover repository?

12 hours ago, daliansky said:

Xnip2019-07-09_11-48-05.thumb.png.1de176ce3798ddd3e03c41588c62d37a.png

Ask the developer of your script to update it. drivers64/drivers64UEFI are no longer in use. It's written just few posts ago.

9 hours ago, Slice said:

Missing drivers in ISO, only drivers-Off

Снимок экрана 2019-07-09 в 9.16.08.png

I'll fix it tonight, I didn't even tried it, sorry.

4 hours ago, arsradu said:

 

It wasn't included with newer packages anymore. That's kind of the idea. To stick to default Clover drivers. If you have AptioMemoryFix installed already, and you don't check for installation any of the other Memory Fix drivers (such as OsXAptioFix3Drv), it will be kept installed. If you choose one of them, AptioMemoryFix will be removed in order not to avoid conflicts.

Right! Also AptioMemoryFix is a fork of OsxAptioFix included and created in Clover. So later I'll port the changes... as soon as I have time.

Edited by vector sigma
typo

Share this post


Link to post
Share on other sites
Posted (edited)
20 minutes ago, vector sigma said:

Right! Also AptioMemoryFix is a fork of OsxAptioFix included and created in Clover. So later I'll port the changes... as soon as I have time.

 

That would be awesome!

 

No worries! As usual, no rush. Take your time. This needs to be done right, not fast. :)

 

Quote

 

No, the installer activate them by default if Clover was never installed, i.e. if ../Library/Preferences/com.projectosx.clover.installer.plist doesn't exist. Due to the fact that I changed something at least once you have to mark cheboxes. Next run will be ok.

The proof is by deleting com.projectosx.clover.installer.plist and you will see them activated. Little price for this migration.

 

 

I was also wondering what happened there. I installed 4983 on another machine with 4981 on it (so before the changes) and indeed, those mandatory drivers were not checked by default. This explains why. Thank you! I didn't know that. :)

 

Also, I can confirm they are checked when reinstalling 4983, or upgrading to 4985, for example. So, we should be ok moving forward. Nice job! :D 

Edited by arsradu

Share this post


Link to post
Share on other sites
16 hours ago, vector sigma said:

OsxAptioFix3 was working until Mojave for me, but just few minutes ago I tested it in Catalina and it fail. Need a fix  (@Slice)

 

 

I need more information what is the fail.

Meanwhile AptioMemoryFix chooses slide value automatically while Fix3 uses value from user and default one is zero.

May be for Catalina zero value is not the best and you have to choose something like slide=128.

Share this post


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

i'm still in Beta1. So it's working for me because of this? ... to night I'll update to Beta 3 and see what's.. Anyway I consider only the root volume ("/") and not if you install Clover from another partition as from Maojave the Catalina partition is read/write in Beta 1 ... can be this the problem?

 

No, the installer activate them by default if Clover was never installed, i.e. if ../Library/Preferences/com.projectosx.clover.installer.plist doesn't exist. Due to the fact that I changed something at least once you have to mark cheboxes. Next run will be ok.

The proof is by deleting com.projectosx.clover.installer.plist and you will see them activated. Little price for this migration.

 

in beta3, still not works to install clover.

162252181_2019-07-099_47_12.png.9d6a7dfd1ce1e060e4e5a1c06618ddc4.png

 

after remove /Library/Preferences/com.projectosx.clover.installer.plist

i can get default driver. thanks a lot

1587922019_2019-07-099_47_06.png.7f896e646246f83187a5524be54718b8.png

 

Share this post


Link to post
Share on other sites

suggestion

old package makes drivers64UEFI and drivers64 folders.

it's useful when sort folders by name.

now folder name is

BiosDrivers 

UEFIDrivers

 

if sort folder by name, BiosDrivers is second, UEFIDrivers is last.

can we consider like before?

example DriversBIOS OR DriversUEFI.

Share this post


Link to post
Share on other sites

If sort by name then Bios.. will be first, UEFI... will be second.

DriversBIOS ans DriversUEFI will be sorted exactly the same.

Share this post


Link to post
Share on other sites
Posted (edited)
38 minutes ago, Sherlocks said:

suggestion

old package makes drivers64UEFI and drivers64 folders.

it's useful when sort folders by name.

now folder name is

BiosDrivers 

UEFIDrivers

 

if sort folder by name, BiosDrivers is second, UEFIDrivers is last.

can we consider like before?

example DriversBIOS OR DriversUEFI.

 

Yeah, I was thinking of that, too.

 

Ooor...another idea, maybe put them both under a global Drivers folder.

 

For example:

Drivers

    - BIOSdrivers

    - UEFIdrivers

 

Also, maybe a bit of cleanup on the BIOS drivers side would be nice to have, as well. For consistency. We're still mentioning "64-bit" in the installer for the BIOS drivers. Apparently I've missed that, too, since I'm only booting UEFI.

 

956001966_Screenshot2019-07-09at16_37_03.png.a2ee65209a64813ec18f77bda5b6034c.png

 

 

19 minutes ago, Slice said:

If sort by name then Bios.. will be first, UEFI... will be second.

DriversBIOS ans DriversUEFI will be sorted exactly the same.

 

Yeah... I think he's referring to the fact that, with the new naming, since Drivers folders are separate, when you look under Clover folder, you'll see BiosDrivers at the beginning of the "list" and UEFIdrivers somewhere at the end. They won't be one after the other anymore.

 

676328046_Screenshot2019-07-09at16_56_38.png.723b0a6beb11bc0aa8ec15d843a2f559.png

 

But if we add them both under Drivers, then they will be, since they will be the only two sub-folders in that folder. :) 

Edited by arsradu

Share this post


Link to post
Share on other sites
6 minutes ago, Slice said:

Yes, agree

Should be


drivers
-- BIOSdrivers
-- UEFIdriver
-- off

As well as in ISO and in PKG.

 

Hi @Slice

 

I don't try r4985. What about Clover installation on existing EFI Folder into Hard Disk or USB pen drive.

Share this post


Link to post
Share on other sites
16 minutes ago, Slice said:

Yes, agree

Should be


drivers
-- BIOSdrivers
-- UEFIdriver
-- off

As well as in ISO and in PKG.

it's redundant, why not:

drivers
-- BIOS
-- UEFI
-- off

?

I mean a tree, subfolders... if we talk for the same thing

Share this post


Link to post
Share on other sites

I am testing.

1.

Why installer said me

Theme 'cesium' (defined in config.plist) not found !
Using default theme 'embedded'

?

No. the theme is present!

2.

The installer kills folders "drivers64" and drivers64UEFI. Ok, as expected. But in this case I can't boot with older Clover. For example to search an mistake.

3. 

Clover installation doesn't depend on "Install on ESP". It does this even without the flag. 

Share this post


Link to post
Share on other sites
12 minutes ago, Matgen84 said:

I don't try r4985. What about Clover installation on existing EFI Folder into Hard Disk or USB pen drive.

The package takes cares of the migration, and Clover will looks on old directories if new ones aren't found.

3 minutes ago, Slice said:

 

1.

Why installer said me


Theme 'cesium' (defined in config.plist) not found !
Using default theme 'embedded'

?

No. the theme is present!

not sure I did nothing for this. I'll take a look

Share this post


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

2.

The installer kills folders "drivers64" and drivers64UEFI. Ok, as expected. But in this case I can't boot with older Clover. For example to search an mistake.

Old Clover doesn't know that your drivers are in a new location, can't expect this. New Clover knows to search in old directories.

May be better to not 'move' but 'copy' and leave old ones for old Clover? .. anyway this happen only if you copy them manually otherwise an old installer will recreate them..

11 minutes ago, Slice said:

3. 

Clover installation doesn't depend on "Install on ESP". It does this even without the flag.

I'll take a look, but I've also did nothing for this. Let see..

Share this post


Link to post
Share on other sites
Posted (edited)

@Slice should we make the repository intentionally not compilable until new changes will be ready.. otherwise a lot of people will compile and use it in the meantime....

Edited by vector sigma

Share this post


Link to post
Share on other sites
Posted (edited)
38 minutes ago, vector sigma said:

it's redundant, why not:


drivers
-- BIOS
-- UEFI
-- off

?

I mean a tree, subfolders... if we talk for the same thing

 

I thought of that, too. :) 

 

The reason why I haven't mentioned it before is because it felt more confusing than the "longer" variant, for some reason.

 

So, whichever you guys decide. It's perfectly fine for me.

 

And...I don't think we need to close the repo. Otherwise people will start complaining about that! :))

 

Uhm..in my opinion, as long as this is still under development (there is no official release yet), it's everyone's obligation to take caution (meaning make a damn bootable USB drive, it's not that hard) so that they can boot back into the system in case they've tried a testing version and things didn't go quite the way they should. Or test on the actual USB instead of the main SSD.

 

When playing with fire, you need to wear protection. :))

 

That's just my opinion.

Edited by arsradu

Share this post


Link to post
Share on other sites
16 minutes ago, vector sigma said:

@Slice should we make the repository intentionally not compilable until new changes will be ready.. otherwise a lot of people will compile and use it in the meantime....

Heh, no. Those people have own responsibility on result. I will upload Release as soon as we decided finally what it should be.

Currently I booted with fresh installed 4985.

Share this post


Link to post
Share on other sites
49 minutes ago, Matgen84 said:

I don't try r4985. What about Clover installation on existing EFI Folder into Hard Disk or USB pen drive.

 

It will just rename 64-bit drivers folders and, on first install, you'll need to reselect your drivers. This is just when switching from versions older than 4983, to 4983 or above. On reinstall, all your previously selected drivers will still be there.

 

Also, if you use AptioMemoryFix, and you select one of the included OSXAptioFix drivers, AptioMemoryFix will be removed to prevent conflicts. If you don't choose anything, AptioMemoryFix will be kept.

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 metaphysician
      hi folks! i'm just checking for opinions here on a Clover based install of High Sierra. currently i can't boot directly from the internal drive on my hackbook, an ASUS ROG GL502-VS laptop (with the replaced WiFi card), though i can boot from the USB bootloader/installer

      i installed 10.13.6 fine using a prepared vanilla installer on HFS+ (not APFS), but my configuration is somewhat unusual. i have two drives. the first SSD has the Windows system, the second has two partitions with the 2nd partition holding the macOS system. when i ran Clover installer i could not use the UEFI option to copy to the EFI partition because it couldn't find one on that drive. so it installed the EFI folder on the root of the macOS partition instead.
       
      however, after a bit of tinkering around, i found out that there is an existing EFI partition on the primary drive called SYSTEM. it has a EFI folder and underneath that is a Windows folder, a Boot folder, and one called APPLE. i can mount this partition with Clover Configurator and copy files to it, but i don't know if this is a good or risky solution. i was thinking i would manually copy the CLOVER folder and the uefi64.boot file to this partition , making sure not to overwrite anything existing. using the UEFI setup, i can create a boot path from the SYSTEM partition to the Clover boot file, but i'm just curious if this is a useful solution or not, and i don't want to ruin the existing Windows 10 installation for sure. any advice appreciated!
    • By Slice
      OK, 4988 released.
      Now, @vector sigma, what have we do to update translations?
    • By fusion71au
      Clover r4989 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4989 for VMware.zip". Mount Clover-v2.4k-4989-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
×