Jump to content

fabiosun

Recommended Posts

Just updated to Ventura without a single issue, tried a fresh install which worked fine including wifi / BT / 2.5G network and just updated my main drive also without any issue.

 

Attached my EFI, @fabiosun feel free to add to OP. (boots Monterey and Ventura flawless only removed audio files from Resources to limit filesize)

(I did a small tweak to the SSDT-TRX40-USB-Port_R88.aml initial version by @Rocket88 and now have all my USB (including front USB-C) working fine and also sleep is working without an issue.)

 

Thanks all for sharing your results and tweaks with this community.

 

EFI OC 0.8.5 Rox67er.zip

  • Thanks 1
  • Ok 1
  • +1 2
Link to comment
Share on other sites

On 10/21/2022 at 6:33 PM, fabiosun said:

@trx40 and also all others  AMD users 🙂

What does it happen to your rig if you press for a click your case power button?

 

here happens this:

 

image.thumb.png.99c8c87e872b62a9f88fb6005838c710.png

Did you need a tweak for this? Mine does not respond to the power button at all.

Link to comment
Share on other sites

20 hours ago, shrisha said:

Guys, I can't boot into safe mode. Holding shift in OC canopy menu selecting disk, just showing apple URL and kick back to selecting menu. Is there anything  have to be adjusted in config.plist? Thank you.

Is anybody know what could be a cause of this?

Edited by shrisha
Link to comment
Share on other sites

On 10/27/2022 at 1:05 PM, Lorys89 said:

For a complete log put this kext and this bootarg 

 

https://github.com/acidanthera/DebugEnhancer
And the bootarg msgbuf=1048576

@Lorys89By adding the kext, AppleIGB.kext and DebugEnhancer.kext

This changes the behavior of my configuration,

Intel I210 modules are not even detected by Ventura anymore.

When I turn off it causes the hack to restart with the Kernel Panic logo...

I tried the command but it fails.

I entered the bootarg msgbuf=1048576

Here is the result in the terminal :

Spoiler

[    2.225085]: igb: start()
[    2.225165]: igb: initEventSources() ===>
[    2.225244]: igb: MSI interrupt could not be enabled.
[    2.225246]: igb: Error initializing event sources.
[    2.225247]: igb: Failed to initEventSources()
[    2.226842]: igb: start()
[    2.229221]: igb: initEventSources() ===>
[    2.229317]: igb: MSI interrupt could not be enabled.
[    2.229319]: igb: Error initializing event sources.
[    2.229321]: igb: Failed to initEventSources()
[    9.525729]: igb: start()
[    9.527501]: igb: start()

 

Link to comment
Share on other sites

@Lorys89

Nothing has changed except the numbering of the last two lines of the report.

 

Spoiler

[    2.209904]: igb: start()
[    2.210042]: igb: initEventSources() ===>
[    2.210133]: igb: MSI interrupt could not be enabled.
[    2.210135]: igb: Error initializing event sources.
[    2.210136]: igb: Failed to initEventSources()
[    2.211652]: igb: start()
[    2.211685]: igb: initEventSources() ===>
[    2.211996]: igb: MSI interrupt could not be enabled.
[    2.211998]: igb: Error initializing event sources.
[    2.211999]: igb: Failed to initEventSources()
[   15.147184]: igb: start()
[   15.180226]: igb: start()

 

Edited by Arrakis
Link to comment
Share on other sites

  • Support Team
3 minuti fa, Arrakis ha scritto:

Nothing has changed except the numbering of the last two lines of the report.

 

  Nascondi Contenuti

[    2.209904]: igb: start()
[    2.210042]: igb: initEventSources() ===>
[    2.210133]: igb: MSI interrupt could not be enabled.
[    2.210135]: igb: Error initializing event sources.
[    2.210136]: igb: Failed to initEventSources()
[    2.211652]: igb: start()
[    2.211685]: igb: initEventSources() ===>
[    2.211996]: igb: MSI interrupt could not be enabled.
[    2.211998]: igb: Error initializing event sources.
[    2.211999]: igb: Failed to initEventSources()
[   15.147184]: igb: start()
[   15.180226]: igb: start()

 

I sent the log to dev

  • +1 1
Link to comment
Share on other sites

On 10/28/2022 at 2:00 PM, Rox67er said:

Just updated to Ventura without a single issue, tried a fresh install which worked fine including wifi / BT / 2.5G network and just updated my main drive also without any issue.

 

Attached my EFI, @fabiosun feel free to add to OP. (boots Monterey and Ventura flawless only removed audio files from Resources to limit filesize)

(I did a small tweak to the SSDT-TRX40-USB-Port_R88.aml initial version by @Rocket88 and now have all my USB (including front USB-C) working fine and also sleep is working without an issue.)

 

Thanks all for sharing your results and tweaks with this community.

 

EFI OC 0.8.5 Rox67er.zip 3.46 MB · 7 downloads

 

Rad, been having a lot of issues going to Ventura with my ASRock TRX40 Creator machine.
Are you saying BT/WIFI (the Intel AX200 on the board) works flawlessly, without itlwm/airportitlwm and bluetooth kexts, or have you replaced the wifi/bt module?

Link to comment
Share on other sites

1 hour ago, 23d1 said:

 

Rad, been having a lot of issues going to Ventura with my ASRock TRX40 Creator machine.
Are you saying BT/WIFI (the Intel AX200 on the board) works flawlessly, without itlwm/airportitlwm and bluetooth kexts, or have you replaced the wifi/bt module?

I have replaced the onboard wifi / BT with an Apple compatible one. Details below:

 

Link to comment
Share on other sites

24 minutes ago, Rox67er said:

I have replaced the onboard wifi / BT with an Apple compatible one. Details below:

 

 

Ah, gotcha. I did that and then swapped back, as the WiFi in that module is extremely slow compared to AX200 or AX210... Stable bluetooth was nice though...

Link to comment
Share on other sites

1 hour ago, fabiosun said:

Hi @Cosmin Batica

could you post a photo before it reboots (adding -V in your bootarg)

have you tried to install with Ethernet cable disconnected?

 

This efi boots with previous Os in your pc?

Yes, I will post a photo right now. I tried with ethernet disconnected, the same result.

 

I doesn't try to boot actual Big Sur installation with this EFI... Update: it doesn't boot.

 

 

Ventura_Boot_Error_1.jpg

Edited by Cosmin Batica
Link to comment
Share on other sites

  • Supervisor

@Cosmin Batica

 

this was your previous working EFi updated with new patches and Ppencore stuff 

try it and post photo of your hang and debug txt

it should also work with your Big Sur installation

 

your opencore debug txt is weird in one MMIO (it is correct in your config..but it gives skip 0 on debug txt

You do not have to change any bios parameter in your motherboard till a solution is found to boot again

I used a limited set of kext for now (no wifi/BT and ethernet) in Ventura and in Monterey ethernet could be a pain for many trx40 users

 

Cosmin EFI Asus ROG Strix TRX40 E-Gamming.zip

have you added NVME disk in your previous working rig?

 

Link to comment
Share on other sites

  • Supervisor
11 hours ago, Cosmin Batica said:

Yes, I will post a photo right now. I tried with ethernet disconnected, the same result.

 

I doesn't try to boot actual Big Sur installation with this EFI... Update: it doesn't boot.

 

 

Ventura_Boot_Error_1.jpg

 

if my previous updated EFi produces this same error

try to add SSDT-EC in your ACPI folder and overwrite your config .plist with attached one

Archive.zip

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • There are no registered users currently online
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.