No network, can't edit settings- Solved

[J Lamp]

So this is a new one, I've managed to update to Tahoe (after I figured out the new USB kext settings) but I can't get sound or network.

 

Sound I will leave for another time (internal, was working fine in Sequoia)

 

Network, when I try to edit any settings they immediately change back to their default (changing the adapter name switches back, changing from DHCP to manual address switches back to automatic) almost as quick as I can enter the new settings

 

I have done the usual deletion of the plist files, no luck. I tried First Aid on the drive in case it was a permissions thing, no luck. I have removed and recreated the "Services" in the network settings.

 

This is on my x299 rig with the Intel network built in (IntelMausi) and the ACQ-107 also. 

 

Clover ver 5163, I have also tried reseting nvram, none of the usual fixes seem to work.

 

Any thoughts?

Edited September 22, 2025 by J Lamp

[J Lamp]

Weird issue, the x299 board has two Intel network interfaces onboard. I only use one, so I have the second one turned off in the bios. This has worked fine for years, till Tahoe.

 

For whatever reason, deactivating the first port in the bios and switching to the second solved the problem. Windows of course doesn't care, so as far as I am concerned the problem is solved.

 

I switched from AppleALC to VoodooHDA for audio. I don't like having to lower the SIP settings, but I think it's easier than opening up the system partition to install an older AppleHDA. The sound with Voodoo is not as good, when I run a speaker "test" in audio midi setup, noise test for the left speaker produces noise somewhat from the right speaker as well. Testing the right speaker is fine. I don't really care about that, this is mostly for system sounds and the odd video. I have audio interfaces for when it matters, they work fine. It doesn't look like there's going to be an AppleHDA fix any time soon. In that regard Tahoe is a set backwards.

 

I had to apply the nvram settings for Bluetooth again, but that solved it;

 

(Terminal, I'm using Clover)

sudo nvram bluetoothInternalControllerInfo=%00%00%00%00%00%00%00%00%00%00%00%00%00%00

sudo nvram bluetoothExternalDongleFailed=%00

 

As I changed from my original smbios of iMacPro to MacPro to get the update I found out that I had to remove WEG to get the installer to run, otherwise it would panic in the first installer stage after the first reboot. Sequoia didn't seem to mind it with the RX6600, but with Tahoe it was a complete no go.

 

I'm having app activation issues with a bunch of software since the upgrade. I'm slowly getting that sorted out.

 

Overall I'm not so crazy about Tahoe so far,  it seems to be a bit of a let down for what's going to be my final mac os version.

 

 

[fspkwonx86]

i posted somewhere in the tahoe post installation AppleHDA Guide , the same applies to AppleALC.kext just follow the instructions

intel mausl resetting might be a quirk of the actual driver.................

if i've experienced this on my dell laptop (r.i.p.) then i would think i would have experienced this

just unplug the coord and have your static ip on both ends see where it says advanced click

it and go to hardware set to manually configure the MTU.. this may apply to DHCP also,

in DHCP in the ADVANCED menu try selecting manual and entering your static IP IPV6 if you need it...