Jump to content

Intel I225-V on Ventura


MacAbe
 Share

60 posts in this topic

Recommended Posts

On 6/20/2022 at 9:26 PM, MacAbe said:

I'm not a professional like you to write a guide 😔, but if anyone needs help or would like test it, feel free to write here 🙂 and will be help as I can 👍

 

I don't meant a guide, I mean a SSDT for fixing the header data of the controller: Here's the Header data used in the custom firmware https://github.com/5T33Z0/Gigabyte-Z490-Vision-G-Hackintosh-OpenCore/blob/main/I225-V_FIX.md#technical-backgroud

 

I will check my backup of the firmware for the original header and then paste that.

 

Differences left= stock firmware, right = custom. I removed the MAC Address):

 

Diff01.png.f131db5b01958b074989390d45dafd2d.png

 

Diff02.png.46015c23da99aa809759820227e28a20.png

 

Diff03.thumb.png.e5eb4a1b54f732c2570a02dd6d6551f3.png

 

Text stock firmware (xxxx = MAC Address):

1		xxxx xxxx xxxx 0520 FFFF 1045 FFFF FFFF
2 		FAFA 0125 602F E000 1458 15F3 8086 8200
3 		80A2 0905 47F0 0001 E4A4 0040 2400 FFFF
4 		3F7D 3000 5A0A 0C00 0508 0000 8203 8427
5 		2004 0584 0000 FFFF 0601 805D 0010 0098
6 		1C68 003C 8000 0701 0000 0097 1000 05F8
7		0100 4000 1332 4003 7EA3 401C FFFF 0119
8		2A19 DE1C 004A FFFF 0094 0430 FFFF B1E8
9		80FD 00FB 014B 8000 371A 8039 0000 0000
10 		2939 0403 8002 9002 0000 FFFF 0019 0000

36		0000 C018 2A4D 1CAA FFFF FFFF FFFF FFFF

255		8082 81FC FFFF FFFF FFFF FFFF FFFF FFFF

Text custom fw:

1.		xxxx xxxx xxxx 0D20 FFFF 1045 FFFF FFFF
2.		FAFA 0125 602F E000 1458 15F3 8086 8200
3.		8022 0905 47F0 0001 E4A4 0040 2400 FFFF
4.		3F7D 3000 5A0A 0C00 0508 0000 8203 8427
5.		2004 0584 0000 FFFF 0681 805D 0010 0098
6.		1C68 003C 8000 0701 0000 0097 1000 05F8
7.		0100 4000 1332 4003 7EA3 401C FFFF 0119
8.		2A19 DE1C 004A FFFF 0094 0430 FFFF B614
9.		807D 007B 0150 8000 371A 8039 0000 0000
10.		2939 0403 FFFF 9002 0000 FFFF 0019 0000

36.		0000 FFFF FFFF FFFF FFFF FFFF FFFF FFFF

255.		8002 80FC FFFF FFFF FFFF FFFF FFFF FFFF

 

Edited by 5T33Z0
Link to comment
Share on other sites

@MacAbe Thanks for the SSDT. For me, Ethernet is working from Catalina to Ventura with the custom fw alone. Bu it might help @Irish_Man and @bluebyte since they both have issues with the I225-V.

 

In general, once the header is fixed, the controller can attach to the .dext driver without issues and use that as well, which is a requirement for macOS Ventura. But if the header is wrong as it is in the stock firmware, trying to attach to the .dext driver causes a kernel panic.

 

EDIT: The SSDT seems to be injected correctly (although I can't tell if the data is coming from the custom fw or the SSDT), but it's identical:

 

832672099_Bildschirmfoto2022-06-22um13_22_30.thumb.png.5fdd216a23757333beae99109b2fb42c.png

Edited by 5T33Z0
  • Thanks 1
Link to comment
Share on other sites

51 minutes ago, MacAbe said:

@5T33Z0 Here is one, i took the data from mine, so test first with boot-arg e1000=0 under Monterey and see if AppleIntelI210Ethernet.kext loads and let us know if works !

 

SSDT-I255Ethernet.aml.zip 1.12 kB · 4 downloads

 

Good Luck 

Thank you,

I tried it on Ventura but it reboots after a minute. On Monterey I have working Ethernet without SSDT

Link to comment
Share on other sites

@5T33Z0 @MacAbe 

 

Progress: 

 

1. I tried the .plist. I changed to iMac20,1. Ethernet is "red dot and It freezes after 5 min with Ethernet cable connected.

2. Added SSDT-I255Ethernet.aml (ethernet cable disconnected), .aml is loaded, no freezes. 

3. Aml is loaded, connected Ethernet cable and Ethernet gets "yellow dot (Self-Assigned IP), no internet. After 5 minutes, Ethernet dot is red again and after 10-15 seconds goes back to yellow and stays there. No internet.

 

Link to comment
Share on other sites

Hello guys,

@Irish_Man I have the same problems with cable and Freeze. Yesterday I got my I225 working with the EFI of @5T33Z0, but the WLAN&Bluetooth (Fenvi) had malfunction.

I have tried many constellations. No success.

I am using Monterey. 

On Big Sur both works without problems. Also my 10GB-LAN-Card.

 

Edited by bluebyte
Link to comment
Share on other sites

@5T33Z0 No, it is your FW data not from my SSDT as I see On the Screenshot. Did you test it with boot-arg or without?

 

@Irish_Man again my ssdt need boot-arg: e1000=0 so that AppleIntelI210Ethernet.kext connect to ethernet and not the other e1000 driver. That was my Goal, In addition, you need to integrate the kext from post #2 into Ventura.

Edited by MacAbe
  • Thanks 1
Link to comment
Share on other sites

Ok, added AppleIntelI210Ethernet.kext, added SSDT-I255Ethernet.aml and e1000=0 boot-arg and I got this :)

It's working. Can some of you guys shed some light on us about what's going on here to make it work? I didn't think it will.

Will have to wait to see if there is any freeze or something but it looks good so far.

@5T33Z0 @MacAbe @Cyberdevs, thank you guys for all your work. Without guys like you we wouldn't be able to fix any sh*t :)

 

1779839752_ScreenShot2022-06-22at19_34_04.thumb.png.6484efe9c4e6efe2450ddef2c2d1708d.png

Edited by Irish_Man
  • Like 3
  • Haha 1
Link to comment
Share on other sites

Congrats. Now I think you don't have custom firmware on your controller. It's the only explanation which makes sense.

 

How it works:

  • SSDT fixes Controller header data on stock firmware
  • .kext injects the .kext driver missing from macOS Ventura
  • boot-arg makes the I225-V attach to kext driver instead of the .dext driver

 

 

Edited by 5T33Z0
  • Haha 1
Link to comment
Share on other sites

3 hours ago, 5T33Z0 said:

Congrats. Now I think you don't have custom firmware on your controller. It's the only explanation which makes sense.

 

How it works:

  • SSDT fixes Controller header data on stock firmware
  • .kext injects the .kext driver missing from macOS Ventura
  • boot-arg makes the I225-V attach to kext driver instead of the .dext driver

 

 

Tnx for explanation and you might be right about the firmware. 

 

So, the story goes like this...

As @5T33Z0 suggested to make a backup of current firmware and compared it to both, the original one and the modded one.

I found out that it doesn't match to either one. Have no idea how's that even possible.

The only explanation I found reasonable is that, since I was the first one who flashed the firmware, I have different firmware than all of you.

That could be because the modded version I was using was sent to me by Badbrain via DM.

First few versions didnt work quite well so I tried several of them until it was working.

Now I have to find the modded one that you guys were using so I can compare it with the one that I have.

 

 

 

  • Haha 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...