Gigabyte X670e Aorus Master - Problems with Install Boot

Caldir

Member
AMD OS X Member
Jan 7, 2026
34
0
6
Germany
CPU:
Ryzen 9 9950x
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 ?
 

Attachments

  • WhatsApp Image 2026-01-09 at 19.42.58.jpg
    WhatsApp Image 2026-01-09 at 19.42.58.jpg
    246.2 KB · Views: 15
  • config.plist
    config.plist
    65.6 KB · Views: 3
  • EFI.zip
    EFI.zip
    7.8 MB · Views: 3
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.
 
  • Like
Reactions: 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 :D, the Update was an Issue dont know why ...
 
Last edited:
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
 

Attachments

  • WhatsApp Image 2026-04-17 at 18.44.44.jpeg
    WhatsApp Image 2026-04-17 at 18.44.44.jpeg
    99.1 KB · Views: 3
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.

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.


Hope this helps.
 
  • Like
Reactions: 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 O.o

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
 

Attachments

Last edited:
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.