Ploddles

@Xsario

I purchased a new drive to try a fresh Tahoe install. To start with it was continually rebooting just like yours did.

However, I finally got it installed and working with the attached EFI.

EFI.zip

All the BIOS versions work for me. I think the only relevant difference between our systems is that you have the additional network card installed. If possible, it may be worth trying the install without the card in your machine.

To create the USB kext, you need to download and run CorpNewts script, which can be downloaded from GitHub, https://github.com/corpnewt/USBMap. 

You can run it from Sonoma or Sequoia.

@Xsario, try this instead of USBMap.kext.

USBMapDummy.kext.zip

All I can think of now is it may be the usb mapping. When I get home this afternoon I’ll upload a dummy one you can try. 

4 hours ago, Xsario said:

@Ploddles, 
I am using version 3304 on my system. Could you share your BIOS settings with me? I may have made a mistake in some BIOS settings. 🙂

Sure.

First I do the Load Optimised Defaults (on the Exit screen).

Memory I set at 5400

Press F9 (search option) type CONTEXT and Enable both values

Save & Exit

I haven't played with changing the Memory settings but that works fine for me - I could try other settings but I don't think it would make much difference.

@Xsariowhat BIOS version are you on? I’m using the latest without any problems. 

Thanks @fabiosun, that USB Network controller works great.

@fabiosun

I mapped them using CorpGhost's script.

23 minutes ago, Xsario said:

I tried the config you shared, and this time it didn't reset, but it got stuck on a black screen. 

Try re-enabling Whatevergreen text. 

@Xsario, try this.

config.plist.zip

Thanks @fabiosun  

May I ask which one works?

I tried a few different ones but couldn’t get any of them to work. 

Here is my latest EFI, booting Tahoe and Sequoia.

Recently, whenever I access the internet my machine is freezing/crashing when connected at 1000BaseT. When connected at 100BaseT it works fine. I do not know if that is an issue with my PC or something else but it doesn't happen in Windows and I can't figure out what is wrong with it.

Can you let me know if this happens to you with this EFI.

If yours is currently working fine with your original EFI, can you post it so I can try that and see if it solves my problem. I can then work forward from there if it works OK on mine in Sequoia.

efi.zip

I have an updated efi. I’ll post it tonight when I get home. 

@Xsario

I've redone the USBMap.kext as I hadn't fully done it earlier, just enough to get it working.

This should be the full version for all the ports.

USBMap.zip

On 9/30/2025 at 9:05 PM, Xsario said:

Hi Ploddles, 

I apologize for missing your message. Yes. I want to try macOS Tahoe on my system. Can you share your EFI with me?

And what BIOS version are you using?

BIOS 3304

The site won't let me upload the EFI so 

HERE

is a link to download it.

@Xsario

Are you planning on trying macOS Tahoe?

If so, my latest EFI lets me boot both Sequoia and Tahoe.  Both the onboard ethernet card and wifi seem to work fine as well. I haven't tried audio as I need to get some new speakers and a microphone, during a recent move they seem to have gone missing!!

I don't have any Thunderbolt devices so when I did the USB mapping I left the USB-C/Thunderbolt ports alone so you would probably have to redo the mapping if you use those ports.

I will post the EFI here if you are going to try Tahoe.

That was quick, thanks very much.

On 7/6/2025 at 9:40 AM, fabiosun said:

Hi to both 🙂

I have always my old x670 WE hero for wife's pc 🙂

i do not touch anymore that pc 😉

however it is possible it would work with old acpi patches. if no, post dsdt on amd discord or here and Corpghost will help you as usual with new patches

 

Hi @fabiosun,

I've just updated to the latest BIOS 3205 hoping it may fix a few issues I am having with Tahoe. Sequoia seems to work fine at the moment but even after the latest update Tahoe is wonky. 

In Tahoe, I have no network card showing at all and my NVMEe drives are very weird. 1 of them will not show at all in System Information and another appears most of the time but sometimes won't show up. The 3rd shows all the time. Even though I can see 2 in System Information I cannot see any of the volumes, 1 of them is Sequoia the other Windows. Nor can I mount either of the EFI partitions on those drives. The one that show all the time is the Windows one.  It will also only allow me to install Tahoe on an old spinning hard disk, not an NVMe or SSD. I have ordered a new, different make, NVMe drive to try that.

I have had a look at the AMD discord run by CorpGhost but couldn't see the best place to ask for help with the ACPI patches. I have attached below the DSDT I have extracted with the debug version of Opencore. 

When you get a chance, could you please pass it on to CorpGhost to do his magic stuff and point me to it on Discord.

Thank you for all your help, now and in the past.

Regards,

DSDT.aml.zip

@Xsario

I updated to that BIOS and everything is still working fine as far as I can tell.

It does take a little while as it also updates other firmware as well, eg the thunderbolt chip.

I still haven't managed to get to install the Tahoe beta yet but I'm getting closer - probably something silly I have in my config.

3 hours ago, Xsario said:

Hi @fabiosun @Ploddles, 

There is a new bios for the X670 hero. Are you using this bios? If so, is there a patch we need to do in EFI?

Hi @Xsario,

I haven't tried it yet. I think @fabiosunhas updated his motherboard to the latest Hero so isn't in a position now to try it. If you try it first can you update here if all is well.

Have you tried Tahoe yet? I can't get mine to boot to the installer even with the latest kexts, OC and patches. I get the prohibit sign and screen corruption during part of the installation and it either freezes or reboots in a loop.

Has anybody got this working with the new Tahoe?

I updated to the latest Opencore 1.0.5, and the latest kexts, but still cannot get past the usual [EB|LOG:EXITBS:START] followed by the Data & Time. Maxkernel set to 24.99.99 for all kexts

Beta 5 update runs fine.

That updated kext solves the issue, thank you.

Are there any advantages using that rather than AppleIntelI210Ethernet.kext?

8 hours ago, fabiosun said:

@Ploddlestry to adapt this config.plist to yours

if you use 2124 BIOS for ASUS you could use it as is (NO DSDT but some ACPI patches added)

I use also a different kext for our ethernet card (check also bootarg)

config.plist.zip 7.74 kB · 1 download

Thank you my genius friend. I now have it working as it should.

The kext you use for the ethernet card (AppleIGC.kext) does not work for me. If I enable that kext and disable AppleIntelI210Ethernet.kext my system just hangs at a black screen. If I disable both of those kexts the same thing happens, I just get a black screen. Enabling AppleIntelI210Ethernet.kext (with the e1000=0 boot arg) and it works again, but ethernet speed is only 10% of what it should be - but that is better than nothing.

The AppleIGC.kext I have is V1.5 dated 14 June 2024.

I will experiment with a few things over the weekend.

7 hours ago, fabiosun said:

Have you upgraded to AMD beta kernel patches?

could you post your config.plist?

Here is the config.plist. As far as I am aware I have all the patches.

config.plist.zip