Ryzen 7000 Testing

[PoMpIs]

If it's not working can you send another PCIe dump?

The sleep panic is because of the GPU, do you have WhateverGreen?

- ExtremeXT

Yes, now I take out another PCI Dump, give me a moment I'm in windows for the HWinfo report and every time I want to boot with one system or another I have to take out the NVMe and put it

I am not using WEG from the beginning in monterey, but I activate it and I will report if the sleep works.

I leave you in HWinfo report

 

[PoMpIs]

New PCIE Dump

PS: Sleep does not work either when using WEG, it restarts when waking up

I add the current EFI, it is stable the computer does not reboot or panic no matter what I do, the annoying thing is not having an internet connection of any kind and having to remove the NVMe to boot MacOS

 

[Edhawk]

Try using a USB to Ethernet adapter.

 

[hvv_]

Isn't that only for Aquantia NICs?

No, it has to do with all PCIe devices, including with a thunderbolt card.

 

[ExtremeXT]

New PCIE Dump

PS: Sleep does not work either when using WEG, it restarts when waking up

I add the current EFI, it is stable the computer does not reboot or panic no matter what I do, the annoying thing is not having an internet connection of any kind and having to remove the NVMe to boot MacOS

Can you get a dmesg log when not having e1000=0? Also try enabling IOMMU (SRV-IO)

No, it has to do with all PCIe devices, including with a thunderbolt card.

Are you sure? AFAIK there are AMD users who have I225-V working...

 

[Middleman]

Maybe the PCIRoot path set for the I-225V is wrong? We could have a look at what shows up in the PCI list in Hackintools and compare.

 

[Shaneee]

PCI dump shows it's a I225-LM not I225-V PciRoot(0x0)/Pci(0x2,0x1)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x0)/Pci(0x5,0x0)/Pci(0x0,0x0)

 

[ExtremeXT]

Maybe the PCIRoot path set for the I-225V is wrong? We could have a look at what shows up in the PCI list in Hackintools and compare.

It's not, the device ID got changed.

PCI dump shows it's a I225-LM not I225-V PciRoot(0x0)/Pci(0x2,0x1)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x0)/Pci(0x5,0x0)/Pci(0x0,0x0)

Isn't that because it got spoofed?

 

[PoMpIs]

Try using a USB to Ethernet adapter.

I do not have

Can you get a dmesg log when not having e1000=0? Also try enabling IOMMU (SRV-IO)


Are you sure? AFAIK there are AMD users who have I225-V working...

SRV-IO already tried it yesterday without e1000=0 ..

I tried all the ways, the i225v is not activated

Also if you look at the latest EFI I added, I modified an SSDT-i225 from

Intel I225-V on Ventura

www.insanelymac.com

But it doesn't work either, it comes out on PCI devices but it doesn't load the Kext

I'm going to look at the dmesg

 

[PoMpIs]

@ExtremeXT

Without e1000=0 it doesn't get to the desktop, it doesn't hang or reboot, I just get a black screen every time, even if I enable or disable IOMMU

And regarding FENVI, in verbose mode, this comes out:




EDIT: It's not a problem with e1000=0, it's IOMMU, if I activate it I always get a black screen.

So I can't boot in any way with SRV-IO active in monterey... I remember that in Ventura it did boot with that activated, but I didn't have a network either

 

[ExtremeXT]

@ExtremeXT

Without e1000=0 it doesn't get to the desktop, it doesn't hang or reboot, I just get a black screen every time, even if I enable or disable IOMMU

And regarding FENVI, in verbose mode, this comes out:

View attachment 7516


EDIT: It's not a problem with e1000=0, it's IOMMU, if I activate it I always get a black screen.

So I can't boot in any way with SRV-IO active in monterey... I remember that in Ventura it did boot with that activated, but I didn't have a network either

Try enabling DisableIOMapper in your plist and enable IOMMU.

 

[ExtremeXT]

@PoMpIs You might need to flash a different firmware.... Try the SSDT method.

Gigabyte-Z490-Vision-G-Hackintosh-OpenCore/I225-V_FIX.md at main · 5T33Z0/Gigabyte-Z490-Vision-G-Hackintosh-OpenCore

OpenCore EFI for running macOS on the Gigabyte Z490 Visison G with an Intel i9 10850K Processor. Supported macOS: Mojava to Tahoe - 5T33Z0/Gigabyte-Z490-Vision-G-Hackintosh-OpenCore

github.com

 

[PoMpIs]

Try enabling DisableIOMapper in your plist and enable IOMMU.

Well, now we are going to have a problem..

Activating SRV-IO in bios gives me a black screen when I get to the desktop....

But it is that now even if I deactivate it and leave it as before, it continues to give a black screen

 

[ExtremeXT]

Well, now we are going to have a problem..

Activating SRV-IO in bios gives me a black screen when I get to the desktop....

But it is that now even if I deactivate it and leave it as before, it continues to give a black screen

Add agdpmod=pikera to boot-args if you have WhateverGreen.

 

[PoMpIs]

@PoMpIs You might need to flash a different firmware.... Try the SSDT method.

Gigabyte-Z490-Vision-G-Hackintosh-OpenCore/I225-V_FIX.md at main · 5T33Z0/Gigabyte-Z490-Vision-G-Hackintosh-OpenCore

OpenCore EFI for running macOS on the Gigabyte Z490 Visison G with an Intel i9 10850K Processor. Supported macOS: Mojava to Tahoe - 5T33Z0/Gigabyte-Z490-Vision-G-Hackintosh-OpenCore

github.com

I already did that once on another board, but that's for i225v version 1 and 2... this already has v3, and on my Alder Lake it works perfectly... and also on the 5900x that has i225v version 2...

It seems strange to me that flashing an old firmware works... but for testing I can try

What a strange thing

 

[ExtremeXT]

I already did that once on another board, but that's for i225v version 1 and 2... this already has v3, and on my Alder Lake it works perfectly... and also on the 5900x that has i225v version 2...

It seems strange to me that flashing an old firmware works... but for testing I can try

What a strange thing

First try the SSDT method, it's the safest.

- ExtremeXT

 

[PoMpIs]

Add agdpmod=pikera to boot-args if you have WhateverGreen.

Of course, I did that when I activated WEG, I always do it

 

[ExtremeXT]

Of course, I did that when I activated WEG, I always do it

OK, disable DisableIOMapper and SR-IOV and try the SSDT method.

- ExtremeXT

 

[PoMpIs]

OK, disable DisableIOMapper and SR-IOV and try the SSDT method.

- ExtremeXT

The problem is now reverting the changes ( disable SRV-IO ). leaving the EFI as it was before, it keeps doing the same thing, I get a black screen when it goes to the desktop

 

[ExtremeXT]

The problem is now reverting the changes ( disable SRV-IO ). leaving the EFI as it was before, it keeps doing the same thing, I get a black screen when it goes to the desktop

Even when DisableIOMapper is Disabled? Try agdpmod=ignore maybe...