X99 stuck on Catalina

[laudou]

I have two X 99 computers, both running Catalina 10.15.7 because I have never been able to install anything higher. One is a MSI = i7-5280. the other a Gigabyte with a Xeon cpu. All my attempts to install either Big Sur, Monterey or Ventura with Clover end up with the same sreen message. Am I wasting my time or is it possible to install Ventura on those two builds?

Thanks

DSC00584.JPG.zip

[MaLd0n]

check on intel site if ur processors is Brodwell-E or Haswell-E and use correct efi folder

https://www.olarila.com/topic/25111-hackintosh-efi-folders-for-all-chipsets-with-opencore-mod/

[laudou]

I tried with both Haswell adn Broadwell. No luck.

 

i7 5280K is Haswell E. I just made a new attempt with the X99 Haswell E efi folder and I got the exact same message I posted previously.

Edited October 11, 2022 by laudou

[MaLd0n]

post one photo in error screen

[laudou]

I did. I am getting the very same error message I posted previously.

DSC00584.JPG.zip

[MaLd0n]

is not olarila efi folder

[laudou]

If this is not an Olarila folder, I wonder what it is; I downloaded it from the Olarila download section. I picked X99 Haswell E. I sent you the error message that is displayed on my computer screen. Is this what you want or do you want something else?

I installed the OS with the Create Install Media command, then I added the Olarila EFI  folder. Did I do anything wrong?

I just created a new installation usb drive using Etcher, Olarila Ventura Beta 10 raw, and X99 Clover EFi. I ran it and I got the error displayed on the pic attached. Then I used Clover configurator and selected Haswell E fake cpuid and ran the installer again with exactly the same result shown on the pic attached,

 

IMG_0016.jpg.zip

Edited October 12, 2022 by laudou

[MaLd0n]

-Use USB2 port for easy installation with no remap USB
-Users with IGPU can use -igfxvesa bootarg for easy installation
-Delete old EFI folder and paste new. Don't use merge files
-Don't use Drag and Drop into EFI partition. Use Copy/Paste instead
-Reset NVRAM one time - with OpenCore use entry "Reset Nvram" / with Clover use F11 key on boot screen

[laudou]

Hi

I was never able to boot from the usb installer using either Haswell or Broadwell on both computers. However, using a workaround I was able to install Ventura on a SSD using a CoffeeLake computer and pasting the X99 Broadwell EFI folder on the SSD. This Ventura SSD boots perfectly witth the Gigbyte X99, Xeon Broadwell cpu.

Unfortunately, I had no luck using the same workaround with the MSI X99, i7-5280 which is a Haswell E type cpu. When trying to boot from the Ventura SSD with the X99 Haswelle EFI folder, I get the attached error.

Thanks for your kind assistance.

DSC00585.JPG.zip

[MaLd0n]

this folder is not from Olarila bro

check ur procedure for clean installation. disable csm, enable 4g deconding if have these option on bios/uefi

[laudou]

I don't understand why you keep saying that that folder is not from Olarila. I only use software found on your site. Besides I never dragged folders to a new location; I always deleted the EFI on the target SSD and pasted the new one. 

 

I'll make sure CSM is disabled and 4G decoding is enabled.

 

Thanks

[MaLd0n]

these errors is not from olarila efi folder

or u have other efi partition or u have bad nvram things. idk

[laudou]

A new attempt with Ventura installed on a SSD on which I pasted the X99 Haswell EFI. I got this error. Is this an Olarila EFI error?

IMG_0023.jpg.zip

[MaLd0n]

seem yes

try other fakecpuid

try some bios config

[laudou]

Hi

I tried all the fakecpuid availlable with Clover Configurator and none worked. The computer does not see the UIOS EFI partition on a Clover installation usb. I found out that when the computer starts to boot from the Open Core usb installation drive it eventually stops loading and reboots. If it is a wrong bios setting I have no idea which one it is. In your opinion, which component is giving me all this trouble: the cpu or the MSI SLI motherboard?

Thanks

Edited October 15, 2022 by laudou

[MaLd0n]

check MMIO in booter quirks

[laudou]

I checked "Devirtualiz MMIO" in boo quirks and I keep getting the same error.  The boot process starts up but then it stops as if the current was suddenly cut off and then gets back to the boot window.

Edited October 15, 2022 by laudou