Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
29,866 posts in this topic

Recommended Posts

fusion71au
fusion71au
Posted
Posted

Clover r4295 build in High Sierra and Clover r4296 built in Sierra.

attachicon.gifScreen Shot 2017-11-10 at 3.11.16 pm.png

Why is Sierra's list alphabetised but High Sierra is not?

 

I think this happens if you compile Clover in High Sierra with APFS file system.  My compile of Clover r4293 in High Sierra with HFS+ file system (attached to post#15271) is in alphabetical order ...

 

post-846696-0-23543100-1510300585_thumb.png

  • Like 2
Link to comment
Share on other sites
Slice
Slice
Posted
Posted

i have strange behavior on High Sierra. I can't boot 10.13 os and installer, when aptiofixdrv2 start to override boot.efi the system shutdown and turn on.. No problem under sierra. Thanks in advance.

Change SMBIOS model

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

Yes same result

Your system maybe falled in hibernate mode.

I experienced your result before. I already reported this. But there was no way to resolved this issue.

https://sourceforge.net/p/hibernationfixup/discussion/general/thread/93f601f6/

 

So i had to format HS partition in windows. Then i can boot any os disk(usb installer/recovery/other os partition). Clover always read nvram file when get gui. Nvram always included hibernation info. So you never boot any macos disk/partiton.

 

Maybe you need to upload preboot.log in your system.

 

According to this situtation, i suggested nvram reset funtion to avoid it in gui.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Link to comment
Share on other sites
ruki250
ruki250
Posted
Posted

Your system maybe falled in hibernate mode.

I experienced your result before. I already reported this. But there was no way to resolved this issue.https://sourceforge.net/p/hibernationfixup/discussion/general/thread/93f601f6/

So i had to format HS partition in windows. Then i can boot any os disk(usb installer/recovery/other os partition). Clover always read nvram file when get gui. Nvram always included hibernation info. So you never boot any macos disk/partiton.

Maybe you need to upload preboot.log in your system.

According to this situtation, i suggested nvram reset funtion to avoid it in gui.

나의 LG-F800S 의 Tapatalk에서 보냄

thi is my log

preboot.log.zip

Link to comment
Share on other sites
ruki250
ruki250
Posted
Posted

Your system maybe falled in hibernate mode.

I experienced your result before. I already reported this. But there was no way to resolved this issue.https://sourceforge.net/p/hibernationfixup/discussion/general/thread/93f601f6/

So i had to format HS partition in windows. Then i can boot any os disk(usb installer/recovery/other os partition). Clover always read nvram file when get gui. Nvram always included hibernation info. So you never boot any macos disk/partiton.

Maybe you need to upload preboot.log in your system.

According to this situtation, i suggested nvram reset funtion to avoid it in gui.

나의 LG-F800S 의 Tapatalk에서 보냄

problem solved!!!! i've deleted nvram.plist from sierra and high sierra is boot up!! Thank you all!!!
Link to comment
Share on other sites
apianti
apianti
Posted
Posted

@Sherlocks, ruki250,

 

You should always have EFI shell! So, if using emulating nvram, delete all the nvram.plist from every volume, if not, use the nvram variable commands and remove any variables that might be used by clover/macOS. And Sherlocks, implement that nvram variable reset, then no issue, you can add it in the options menu or even as a tool, but if you add it as a tool, remember that it must not be added if tool scan is disabled.


@Slice, When you'll upload the latest version that has the AMD Wake Fix?

 

Do you mean for AMD CPUs or for new AMD radeon GPUs? Because if you mean the latter, you can build the newest revision yourself, there are tools to do it for you. just go back to clover forum index, and look into the build clover command topic. If you mean the former, I don't think that's a thing....

 

EDIT: Eh, here's the topic, not sure why I didn't just link it.

  • Like 1
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

@Sherlocks, ruki250,

 

You should always have EFI shell! So, if using emulating nvram, delete all the nvram.plist from every volume, if not, use the nvram variable commands and remove any variables that might be used by clover/macOS. And Sherlocks, implement that nvram variable reset, then no issue, you can add it in the options menu or even as a tool, but if you add it as a tool, remember that it must not be added if tool scan is disabled.

I'm not friendly use EFI shell command. So i didn't use it to remove nvram.plist file in apfs partition. Like you said, EFI shell solution is one for my issue.

I will try to implement nvram reset in gui.

 

Thanks

 

나의 LG-F800S 의 Tapatalk에서 보냄

  • Like 1
Link to comment
Share on other sites
apianti
apianti
Posted
Posted

good, noob question, How to let Clover auto detect and boot Linux partitions on different disks than mac disks?

 

If they are installed in EFI mode then their grub loaders should be detected from the EFI partition, from the disk installed on. If not then you need to make sure that you have kernel scan enabled, and also VBoxExt2.efi or VBoxExt4.efi filesystem driver in clover drivers folder.

Link to comment
Share on other sites
Tusskan
Tusskan
Posted
Posted

If they are installed in EFI mode then their grub loaders should be detected from the EFI partition, from the disk installed on. If not then you need to make sure that you have kernel scan enabled, and also VBoxExt2.efi or VBoxExt4.efi filesystem driver in clover drivers folder.

Well, I've been trying with no results. I'll research it later. I've VBoXEX2.efi driver and put it into drivers64 folder and ticked Kernel and Linux from Entries, it detect nothing.

Link to comment
Share on other sites
JorgeMax
JorgeMax
Posted
Posted

With the new build 4297 and added the key "RadeonDeInit", I no longer need the kext "WhateverGreen.kext".

My Radeon HD 7850 "wakes up" from "sleep", just needed the aforementioned kext because of that problem.
 
Thanks to Vit9696, Mieze and Slice for this Clover review
  • Like 1
Link to comment
Share on other sites
apianti
apianti
Posted
Posted

Well, I've been trying with no results. I'll research it later. I've VBoXEX2.efi driver and put it into drivers64 folder and ticked Kernel and Linux from Entries, it detect nothing.

 

Are you legacy booting? Are your linux installs also legacy? Did you install the legacy bootloader for each on the partition and not the MBR? Because you should get legacy entries for them unless you've disabled legacy scan? Also are you sure its not an Ext4 partition? Linux hasn't used Ext2/3 for a few years now, like almost ten. Plus I don't know what you mean by ticked Kernel and Linux from Entries, that sounds more like you tried to create a custom entry, when it will automatically find kernels if the kernel scan is not disabled, it's enabled by default. So you just need the filesystem driver to be able to see the kernels on the volume and make sure that the correct scans are enabled (they are all enabled by default, so maybe you disabled them).

 

 

 

With the new build 4297 and added the key "RadeonDeInit", I no longer need the kext "WhateverGreen.kext".

My Radeon HD 7850 "wakes up" from "sleep", just needed the aforementioned kext because of that problem.
 
Thank you Slice

 

 

You should probably be thanking vit9696 and Mieze as well.

  • Like 1
Link to comment
Share on other sites
JorgeMax
JorgeMax
Posted
Posted

Are you legacy booting? Are your linux installs also legacy? Did you install the legacy bootloader for each on the partition and not the MBR? Because you should get legacy entries for them unless you've disabled legacy scan? Also are you sure its not an Ext4 partition? Linux hasn't used Ext2/3 for a few years now, like almost ten. Plus I don't know what you mean by ticked Kernel and Linux from Entries, that sounds more like you tried to create a custom entry, when it will automatically find kernels if the kernel scan is not disabled, it's enabled by default. So you just need the filesystem driver to be able to see the kernels on the volume and make sure that the correct scans are enabled (they are all enabled by default, so maybe you disabled them).

 

 

 

You should probably be thanking vit9696 and Mieze as well.

 

Sorry, I just edited and gave the credits to them too

Link to comment
Share on other sites
apianti
apianti
Posted
Posted

Sorry, I just edited and gave the credits to them too

 

Nothing for which to be sorry. You're good, just letting you know that it was really those two, slice just incorporated their ideas into clover. That's why open source communities are great. Clover is built off the previous stuff, as new stuff will be built off clover.... Mad props though for your thanking of them, those're far and few between, and it makes us feel appreciated.  :wink_anim:

  • Like 3
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

problem solved!!!! i've deleted nvram.plist from sierra and high sierra is boot up!! Thank you all!!!

0:658  0:010  Loading nvram.plist from Vol 'Sierra' - loaded, size=2759

0:660  0:000   Adding Key: IOHibernateRTCVariables: Size = 44, Data: 41 41 50 4C 01 00 00 00 7B B6 6E E8 2B 43 E0 1D 60 09 A6 80 1A AD 45 6C 97 C4 0E 07 50 3A 65 28 43 8E 58 F3 04 F4 EA 68 21 3C 94 83 

0:660  0:000   Adding Key: boot-image: Size = 56, Data: 02 01 0C 00 D0 41 03 0A 00 00 00 00 01 01 06 00 00 17 03 12 0A 00 00 00 00 00 00 00 04 04 18 00 34 00 37 00 34 00 39 00 32 00 30 00 30 00 30 00 30 00 00 00 7F FF 04 00 
0:660  0:000   Adding Key: Boot0082: Size = 82, Data: 01 00 00 00 4A 00 00 00 02 01 0C 00 D0 41 03 0A 00 00 00 00 01 01 06 00 00 17 03 12 0A 00 00 00 FF FF 00 00 04 01 2A 00 02 00 00 00 28 40 06 00 00 00 00 00 B0 85 F9 06 00 00 00 00 03 88 C4 E2 5C 34 87 4A 9C 51 D9 5E 1E 5A 0E DF 02 02 7F FF 04 00 
0:660  0:000   Adding Key: BootNext: Size = 2, Data: 82 00 
 
because of these key, you got instant reboot with osxapitiofix message. it's same as my issue.
it means that hibernation mode is not properly work in your system.
Link to comment
Share on other sites
apianti
apianti
Posted
Posted

 

0:658  0:010  Loading nvram.plist from Vol 'Sierra' - loaded, size=2759

0:660  0:000   Adding Key: IOHibernateRTCVariables: Size = 44, Data: 41 41 50 4C 01 00 00 00 7B B6 6E E8 2B 43 E0 1D 60 09 A6 80 1A AD 45 6C 97 C4 0E 07 50 3A 65 28 43 8E 58 F3 04 F4 EA 68 21 3C 94 83 

0:660  0:000   Adding Key: boot-image: Size = 56, Data: 02 01 0C 00 D0 41 03 0A 00 00 00 00 01 01 06 00 00 17 03 12 0A 00 00 00 00 00 00 00 04 04 18 00 34 00 37 00 34 00 39 00 32 00 30 00 30 00 30 00 30 00 00 00 7F FF 04 00 
0:660  0:000   Adding Key: Boot0082: Size = 82, Data: 01 00 00 00 4A 00 00 00 02 01 0C 00 D0 41 03 0A 00 00 00 00 01 01 06 00 00 17 03 12 0A 00 00 00 FF FF 00 00 04 01 2A 00 02 00 00 00 28 40 06 00 00 00 00 00 B0 85 F9 06 00 00 00 00 03 88 C4 E2 5C 34 87 4A 9C 51 D9 5E 1E 5A 0E DF 02 02 7F FF 04 00 
0:660  0:000   Adding Key: BootNext: Size = 2, Data: 82 00 
 
because of these key, you got instant reboot with osxapitiofix message. it's same as my issue.
it means that hibernation mode is not properly work in your system.

 

 

He was trying to install or boot High Sierra when it appears that he had hibernated Sierra without resuming. So yeah that was probably not going to work...

  • Like 1
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

He was trying to install or boot High Sierra when it appears that he had hibernated Sierra without resuming. So yeah that was probably not going to work...

Yes. We need to remove these key. Ex. Nvram reset feature in gui without manual process in other os(windows or something).

 

나의 LG-F800S 의 Tapatalk에서 보냄

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...