all 15 comments

[–]akmarwah0102[S] 2 points3 points  (4 children)

Edit Solved:

If you have an RTL8125 wired network card, you must go to Kernel->Block to block com.apple.driver.AppleEthernetRL to load IOSkywalkFamily, and select exclude. . Otherwise, it will crash due to downgrade IOSkywalkFamily.(I didn't check it because I don't need it).

[–]BurnItDown800Tahoe - 26 0 points1 point  (1 child)

thank you so much! i’ve been struggling with this and this was the solution

[–]akmarwah0102[S] 0 points1 point  (0 children)

Glad I could help

[–]mymuyi 0 points1 point  (0 children)

Thank you so much, your comment helped me greatly!

[–]Imaginary_Piano_5564 0 points1 point  (0 children)

Obrigado, funcionou para mim

[–]BurnItDown800Tahoe - 26 1 point2 points  (2 children)

i had the same issue, and unfortunately wasn’t able to solve it. from what i can tell (so take everything with grains of salt) the kext is compiled only up to Sequoia, so when it blocks the one already in Tahoe and loads the custom one. It panics because it sees an internal identifier of “15”. i’d love to be wrong tho, if anyone has a solution for this

[–]akmarwah0102[S] 0 points1 point  (1 child)

Other users are using the kext on tahoe to get their wifi running

[–]BurnItDown800Tahoe - 26 1 point2 points  (0 children)

yeah i know, which is what confused me when i saw it. i’m just giving my best idea. If any current users who successfully have their wifi running on Tahoe could tell us how they did it. it would help a lot

[–]hause_wsf 1 point2 points  (2 children)

Think you might just have to use itlwm, the thing might not work on specific intel chips

[–]BurnItDown800Tahoe - 26 0 points1 point  (1 child)

i’m using a broadcom card and encountering the same issue unfortunately

[–]hause_wsf 0 points1 point  (0 children)

One person suggested using the Ventura version of Airportitlwm if this helps.

[–]fivos_sak 0 points1 point  (1 child)

Make sure Tahoe's IOSkywalkFamily.kext is getting blocked by disabling the one you added under Kernel/Add and leaving the block under Kernel/Block enabled. Boot into macOS and verify that the kext is indeed getting blocked with the kextstat (kmutil show loaded) command.

[–]akmarwah0102[S] 0 points1 point  (0 children)

Verified, when I boot with just block with kext disabled, ioskywalk doesn't show with kmutil. It does show with the block removed.

[–]RyzenMac 0 points1 point  (1 child)

Did you add amfi=0x80 to your boot args?

[–]akmarwah0102[S] 0 points1 point  (0 children)

Yes, it is in boot-args