Gigabyte X670e Aorus Master - Problems with Install Boot

[Caldir]

Hi i did ryzentosh 6 years ago...
which kext should i use for GPU Tahoe whatevergreen.kext or NootRX.kext?
Something wrong with my CPU Mapping ?

 

[Edhawk]

Use SMBIOs for MacPro7,1, the iMacPro1,1 isn't supported in Tahoe.

You don't need most of those boot arguments. Remove these.

keepsyms=1 debug=0x100 igfxonln=1 alcdelay=1000 log_buf_len=8388608

Unless there is something really relevant updated for your system, which you can't do without, I would recommend sticking with your current Bios. It works, so leave it be until you actually need what the new Bios is offering.

 

[Caldir]

Use SMBIOs for MacPro7,1, the iMacPro1,1 isn't supported in Tahoe.

You don't need most of those boot arguments. Remove these.

keepsyms=1 debug=0x100 igfxonln=1 alcdelay=1000 log_buf_len=8388608

Unless there is something really relevant updated for your system, which you can't do without, I would recommend sticking with your current Bios. It works, so leave it be until you actually need what the new Bios is offering.

Thanks tomorrow i will Map again

Maybe Perplexity can help me i will send them everything i know about my mappings let us see

EDIT: Ya, Sir.

don't need this Boot Args i will try Tahoe MacOS Installer with -v
I almost can install fresh with Boot Stick from Tahoe it , the Update was an Issue dont know why ...

 

[Caldir]

Small Update New Error from Tahoe Install, it is kind of weird.
Because under sequoia the EFI runs almost flawless unless the USB Mapping.
Here is a screenshot from the Problem

 

[Edhawk]

The most common issue when looking to install Tahoe is an over populated /EFI/OC/Kexts folder. The trick is to disable or delete any kexts that are not essential to getting Tahoe installed. A Kexts folder contain just these Kexts might be what you need to use.

• Lilu.kext
• VirtualSMC.kext
• AppleMCEReporterDisabler.kext
• USBPorts.kext or USBMap.kext that has been updated to work with Tahoe.
  • USBToolBox.kext & UTBMap.kext won’t work in Tahoe, as the UTBMap configuration lacks the new port name and number requirement for Tahoe.
  • The methods for generating either of other two USB kexts have been updated in their respective Application/Script so they will work with Tahoe.
  • You just need to make sure if you are using Sequoia that you use one of the two methods to generate a new kext based on your current configuration.
• Ethernet kext (whichever one you need for your motherboard)
• WhateverGreen.kext version 1.7.1d7, see link below.

https://www.tonymacx86.com/threads/success-with-whatevergreen-kext-1-7-1d7-and-ota-update-clean-install-recovery-mode-of-tahoe.332725/#post-2431597

I would also recommend using this Kernel patch when running a fresh/clean installation of Tahoe. As it prevents the installer from implementing FileVault encryption on your macOS drive. As this would result in you not being able to sign in to your account on the macOS login screen.

How to Disable FileVault During a Fresh Installation (Clover & OpenCore)

Thanks to @Slice @LockDown and @luxinhaus for perfect patch for Clover And @Luchina for Opencore video tutorial on Youtube. This tutorial aims to disable FileVault during installation or updates using patch key in Clover and OpenCore through a kernel patch, simply by adding the following keys: Cl...

www.insanelymac.com

Hope this helps.

 

[Caldir]

it works for now some tests then I know about benchmark scores.
Sometimes i got a Black screen, but next time it boots wellt

now it boots after 1 boot loop, kind of weird

-v -amfipassbeta agdpmod=pikera alcid=1

EDIT New Boot Arg Seems to work flawless:

-v agdpmod=pikera alcid=1

By the way... how is this mapping ?

Now get some Boot issues on Tahoe, sometimes in works / Black Screen or reboot
Nothing change use old EFI and New one's doenst matter

EDIT2: Maybe cuz i wanna update the system ? Something broken inside the macOS ?
Should i Reinstall ?

 

[Caldir]

It's inexplicable to me why these various errors are occurring.

I boot with an EFI that worked perfectly before, but now it doesn't.

Sometimes, after selecting the USB drive in the boot menu, nothing happens, and the system jumps straight back to the boot menu.

Another phenomenon is a black screen after almost everything has finished running. I started with -v boot arg, so I couldn't identify any errors.

Another issue occurs after almost everything has finished running: a restart.

And finally, sometimes the system gets stuck on AHCI.

I still absolutely don't understand why everything worked before.

It's driving me crazy. Even Sequoia doesn't work anymore.

The EFIs were newly created, and some were old. I'm starting to think the motherboard might actually be faulty. An alternative would be to buy a used Asus board and try it out on a test bench. Otherwise, switch completely to macOS, as updates for Tahoe will also cease.

EDIT: TRY different Bios now is F38 dec. , also try now 41 - NVME Reset. Sometimes i tink the EFI change be it self or Memory is not clean somehting like that.

 

[Edhawk]

Changing the Bios, without checking to see if the system DSDT.aml needs new or different patches isn’t a good thing to do.

Using the verbose boot argument (-v) can on some systems lead to a kernel panic, depends on what else has been enabled, I.e. Realtek Ethernet port/kext rings a bell.

Have you looked into copying the EFI folder from your USB Installer to the EFI Partition on the macOS drive? As that is how I and most Hackintosh users setup their Hacks, once they have macOS installed. See this Dortania page for details.

Moving OpenCore from USB to macOS Drive | OpenCore Post-Install

The more you change things from their original working version the more likely you are to introduce new problems.

 

[Caldir]

Update:

I’m dealing with a very sporadic kernel panic / boot instability issue on my AM5 Hackintosh, and I’m trying to narrow down the cause.

My system:

• AM5 Hackintosh
• macOS booting via OpenCore
• NVMe SSDs:
  
  • Samsung 9100 2TB
  • Samsung 970 EVO 1TB
• SATA SSD:
  
  • SanDisk 500GB SATA SSD
• I also use NVMeFix.kext

The problem does not happen all the time. It appears randomly, and I first suspected an AHCI / SATA issue.

What I found so far:

• CrystalDiskInfo shows the SanDisk SSD as healthy:
  
  • 97% health
  • 37°C
  • no reallocated blocks
  • no CRC errors
• CHKDSK in Windows also reports no file system problems and no bad sectors.
• However, my boot logs show repeated AHCI messages like:
  
  • COMRESET did not proceed
  • WaitForLinkPresent
  • EnablePortOperation returned: 0xE00002D6
• These messages seem to point to a SATA link / port / controller issue rather than a bad file system.

My main question:
Could an unstable SATA/AHCI device or port also cause kernel panics or boot problems in macOS, even if the SSD itself looks fine in SMART and CHKDSK?

At this point I’m wondering whether:

• the SATA cable is bad,
• the SATA port on the board is unstable,
• the SanDisk SSD is causing the issue only under certain conditions,
• or this is something else related to the Hackintosh setup.

Any ideas or suggestions would be appreciated.

Thanks!

 

[Edhawk]

These are all valid points.

• the SATA cable is bad, yes this is a possible cause,
  • I would replace the cable but also check its replacement is firmly seated in the motherboard SATA port and connected to the SSD
• the SATA port on the board is unstable,
  • The only way to know if the SATA port is to blame is to try all the other ports with the new SATA cable, to see if the issue is removed by using an alternative SATA port.
• the SanDisk SSD is causing the issue only under certain conditions,
  • This is the least likely but still possible. not sure how you would test this theory.
• or this is something else related to the Hackintosh setup,
  • Could be an issue with the AMD SATA Controller. I know of a couple of users who had issues with the AMD SATA controller on their Gigabyte motherboards, with no resolution to the issue. I was using a similar board (Asus not Gigabyte) with the same SATA controller but had no AHCI or SATA issues.

If you are using the SanDisk SSD for macOS, I would remove the two Samsung NVME drives and see if the issue occurs when they are not connected to the system.

Personally I would remove the two Samsung drives whatever, as neither are 100% compatible with macOS and these are more likely to cause issues, even if not used as the macOS drive.

Western Digital or SanDisk NVMe drives are the most compatible with macOS, as they use a compatible NVME controller to that used by Apple in their Intel Macs. I use WD SN570, SN580, SN770, SN850X drives in my hacks with no issues. The SanDisk 5100 and 7100 drives use similar NVME controllers and are known to work well with macOS. Do not look at the WD/SanDisk 8100 PCIe 5.0 x 4 drive as it uses an incompatible controller.

Do not use a PCIe 5.0 x 4 NVME drive, as none of them have a macOS compatible NVME controller (Phison, Silicon Motion & Phoenix controllers) as far as I can tell from my research.