Jump to content

[Help] Upgrade High Sierra (to??)


126 posts in this topic

Recommended Posts

22 hours ago, antuneddu said:

馃檲https://drive.google.com/file/d/1f67-O0cb_hcTfrAZmLOSto8bKgTazsWT/view?usp=sharing

after you edited the plist... double check with the validator

I did, is everything correct? I attach the screens

ACPI.png

string.png

KernelCpu.png

Debug.png

clover validator gives me out this:

image.thumb.png.ea591a2f917314a4c88c38e09a6eff88.png

Edited by Montelli
Link to comment
Share on other sites

ok perfect:

image.png.cdb225ecd4b9492e000afb471a7b7077.png

now I copied my CLOVER> ACPI> patched folder to the new Clover and included the one mentioned by Slice

the kext I left only those present in the clover 5150 folder
and I configured Booter and Kernel Quirks with updated cloverconfigurator

I double checked the plist with clovervalidator and it's all Ok

I chose my USB Uefi, I entered in clover, but when I start macos high sierra it hangs at the apple without a bar and without anything else:

image.thumb.jpeg.5f78b79ff7dc6c3baf67de469342ef2b.jpeg

I wait your response, Thank you

Edited by Montelli
  • Sad 1
Link to comment
Share on other sites

1 hour ago, Montelli said:

ok perfect:

image.png.cdb225ecd4b9492e000afb471a7b7077.png

now I copied my CLOVER> ACPI> patched folder to the new Clover and included the one mentioned by Slice

the kext I left only those present in the clover 5150 folder
and I configured Booter and Kernel Quirks with updated cloverconfigurator

I double checked the plist with clovervalidator and it's all Ok

I chose my USB Uefi, I entered in clover, but when I start macos high sierra it hangs at the apple without a bar and without anything else:

image.thumb.jpeg.5f78b79ff7dc6c3baf67de469342ef2b.jpeg

I wait your response, Thank you

Next step is to produce boot log.

Set in config

Boot->Debug=true

and try to boot the system. It will be very slow, wait 10 minutes and then look into /EFI/CLOVER/misc. There should be new ***.log file. Upload it here for me to look.

Link to comment
Share on other sites

On 11/26/2022 at 3:25 PM, Montelli said:

attached the log file

thank you聽:)

BOOTX64.EFI.log 82.62 kB聽路聽3 downloads

I can propose that the hang at fix usb ownership because you have external ASMedia聽 USB3 controller.

Try to switch off USB handoff in BIOS if possible.聽

Or switch off FixOwnership in config.plist but then you will encounter a stop at "waiting for root...".

Try to insert your USB stick into USB2 port on motherboard not into ASMedia.

The better way if your EFI folder will be in internal SATA drive then booting process will not depend on USB.

If not help then wait until聽 I will prepare a clover version doing no FixOwnership on ASmedia controller.

Link to comment
Share on other sites

10 hours ago, Montelli said:

as you can imagine I had inserted a 3.0 pendrive in a 3.0 usb port in front of the case...

now I used a 2.0 pendrive directly in the 2.0 usb port of the motherboard and unfortunately it did not boot anyway ...
I attach the .log file

Thank you

2022-11-28_18-49_BOOTX64.EFI.log 84.01 kB聽路聽1 download

Same. Be ready to test new Clover.

Link to comment
Share on other sites

kind slice, I extracted this zip file, and replaced CLOVERX64 in EFI/CLOVER/CLOVERX64.EFI
but in the zip there was only that and I didn't find a bootx64 file to replace in efi/boot/bootx64.efi...

however I booted from usb 2.0 but unfortunately the system didn't boot

I attach the .log file

I wait your response thank you

2022-11-30_17-48_BOOTX64.EFI.log

Link to comment
Share on other sites

12 hours ago, Montelli said:

kind slice, I extracted this zip file, and replaced CLOVERX64 in EFI/CLOVER/CLOVERX64.EFI
but in the zip there was only that and I didn't find a bootx64 file to replace in efi/boot/bootx64.efi...

however I booted from usb 2.0 but unfortunately the system didn't boot

I attach the .log file

I wait your response thank you

2022-11-30_17-48_BOOTX64.EFI.log 84.21 kB聽路聽1 download

Expected... No, no, no....

Make a copy of the file CLOVERX64.efi. There will be second file. Rename it to BOOTX64.EFI.

Copy it to your bootable EFI聽 replacing existing BOOTX64.EFI.

Link to comment
Share on other sites

11 hours ago, Montelli said:

Ok sorry for delay, now I copied the same file you put above, into /EFI/CLOVER/CLOVERX64.EFI and the same into /EFI/BOOT/BOOTX64 but here renaming it to BOOTX64
but unfortunately the system didn't boot
I attach the log file

Thank you

ps. the time day of pc is wrong聽but i just did it now

2022-11-30_19-07_BOOTX64.EFI.log 84.38 kB聽路聽0 downloads

But I see wrong commit

0:110 聽0:000 聽Starting Clover revision: 5150 (master, commit ee4d7a61b) on American Megatrends EFI

It must be at least聽4a3b16 or even聽ff1681ad

It means you booted not same Clover as I upload for you.

Link to comment
Share on other sites

1 hour ago, Montelli said:

Your video shows correct action but I see wrong revision again

0:107 聽0:000 聽Starting Clover revision: 5150 (master, commit ee4d7a61b) on American Megatrends EFI

I will upload to you new version at the evening.

Anyway try to switch off XHCI handoff (or something similar) in BIOS.

Link to comment
Share on other sites

Definitely agree with @bronxteck聽. I had this problem with my Dell Latitude E6410. 聽I ended up abandoning use of a bootable USB and had to do all of my EFI debugging by editing EFI on the SSD. 聽Since my Dell Latitude E6410 has an aux bay, I was able to have a backup EFI on the SSD in the aux bay which saved me when I screwed up the EFI in my primary drive bay.

Link to comment
Share on other sites

25 minutes ago, Montelli said:

but efi folder and macos are in nvme and cloover boot in eufi from nvme...
Anyway...but if it doesn't boot from internal efi how do I access the efi folder again?

I would however try disabling the XHCI handoff first

Try to switch off "Legacy USB support".

I see in your log good Clover version but you started HighSierra?

142:095  0:113  GetOSVersion: 10.13.5 (17F77)

Is it too old for such hardware?

Also try temporary disable some kexts except Lilu+VirtualSMC.

I can also propose use one kext FakeSMC instead.

Link to comment
Share on other sites

the version I have is high sierra 10.13.5 and I thought I'd give it other try, I took the efi folder that I use for high sierra and put it in the usb and so it boot... at this point I think there is something wrong with the new cloover? because with the usb it actually starts if I use the high sierra efi... in all this I disabled the Legacy USB support and tried again with the new cloover but it didn't boot... I attach the log file

2022-12-05_11-22_BOOTX64.EFI.log

to disable kexts, just leave VirtualSMC and Lilu in Other folder?

Edited by Montelli
Link to comment
Share on other sites

 Share

×
×
  • Create New...