fusion71au Posted November 10, 2017 Share Posted November 10, 2017 Clover r4295 build in High Sierra and Clover r4296 built in Sierra. Screen 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 ... 2 Link to comment Share on other sites More sharing options...
pico joe Posted November 10, 2017 Share Posted November 10, 2017 hmm .. make sense .. Launchpad in HS with apfs also not alphabetical order Link to comment Share on other sites More sharing options...
PMheart Posted November 10, 2017 Share Posted November 10, 2017 hmm .. make sense .. Launchpad in HS with apfs also not alphabetical order Just considering "App Store" is always after "iTunes" at LP, not only under HS... Sorry, off-topic. Link to comment Share on other sites More sharing options...
ruki250 Posted November 10, 2017 Share Posted November 10, 2017 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. Link to comment Share on other sites More sharing options...
Slice Posted November 10, 2017 Share Posted November 10, 2017 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 More sharing options...
ruki250 Posted November 10, 2017 Share Posted November 10, 2017 Change SMBIOS model My smbios model is imac18,2 and had worked before Link to comment Share on other sites More sharing options...
Sherlocks Posted November 10, 2017 Share Posted November 10, 2017 My smbios model is imac18,2 and had worked beforeHow about recovery mode? Same result? 나의 LG-F800S 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
ruki250 Posted November 10, 2017 Share Posted November 10, 2017 How about recovery mode? Same result? 나의 LG-F800S 의 Tapatalk에서 보냄 Yes same result Link to comment Share on other sites More sharing options...
Sherlocks Posted November 10, 2017 Share Posted November 10, 2017 Yes same resultYour 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 More sharing options...
ruki250 Posted November 10, 2017 Share Posted November 10, 2017 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 logpreboot.log.zip Link to comment Share on other sites More sharing options...
Tusskan Posted November 10, 2017 Share Posted November 10, 2017 @Slice, When you'll upload the latest version that has the AMD Wake Fix? Link to comment Share on other sites More sharing options...
ruki250 Posted November 10, 2017 Share Posted November 10, 2017 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 More sharing options...
apianti Posted November 10, 2017 Share Posted November 10, 2017 @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. 1 Link to comment Share on other sites More sharing options...
Sherlocks Posted November 10, 2017 Share Posted November 10, 2017 @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에서 보냄 1 Link to comment Share on other sites More sharing options...
Slice Posted November 10, 2017 Share Posted November 10, 2017 @Slice, When you'll upload the latest version that has the AMD Wake Fix? As usual at Friday. Link to comment Share on other sites More sharing options...
Tusskan Posted November 10, 2017 Share Posted November 10, 2017 As usual at Friday. good, noob question, How to let Clover auto detect and boot Linux partitions on different disks than mac disks? Link to comment Share on other sites More sharing options...
apianti Posted November 10, 2017 Share Posted November 10, 2017 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 More sharing options...
Tusskan Posted November 10, 2017 Share Posted November 10, 2017 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 More sharing options...
JorgeMax Posted November 10, 2017 Share Posted November 10, 2017 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 1 Link to comment Share on other sites More sharing options...
apianti Posted November 10, 2017 Share Posted November 10, 2017 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. 1 Link to comment Share on other sites More sharing options...
JorgeMax Posted November 10, 2017 Share Posted November 10, 2017 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 More sharing options...
apianti Posted November 11, 2017 Share Posted November 11, 2017 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. 3 Link to comment Share on other sites More sharing options...
Sherlocks Posted November 11, 2017 Share Posted November 11, 2017 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 More sharing options...
apianti Posted November 11, 2017 Share Posted November 11, 2017 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... 1 Link to comment Share on other sites More sharing options...
Sherlocks Posted November 11, 2017 Share Posted November 11, 2017 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 More sharing options...
Recommended Posts