Search results

Both the missing "Wake for Network Access" and no Internet connection when booting to recovery are fixed. These 2 problems are related and caused by the AppleEthernetE1000 driver on I225-V. I copied the AppleIntelI210Ethernet.kext from Monterey to EFI/OC/Kexts folder and manually loaded it in...

I've tried to enable WiFi and the "Wake for Network Access" option appeared. But this only relates to WiFi and and Ethernet port LED is still off when sleep. Anyway, waking via WiFi interface doesn't work also.

Just rebooted to Ventura Recovery and tried to reinstall macOS, but a message saying "Internet connection is required to install macOS". Seems Recovery couldn't detect my Ethernet. However, if I boot to Monterey Recovery, I can reinstall macOS without any problem.

Glad that I'm not alone. It would be great to have more confirmation whether this is common to MSI boards. Another strange behaviour is when I boot to Ventura Recovery and try to reinstall macOS, I would get a message saying "Internet connection is required to install macOS". Seems Recovery...

Yeah, the LAN port is working perfectly. Do you have "Wake for Network Access" option in Ventura?

After upgrading from Monterey to Ventura, the "Wake for Network Access" option is missing under "Energy Saver". Does anyone still has this option in Ventura?

I had tried to delete the NetworkInterfaces.plist before, but it didn't make any difference. However, I just tried to load the itlwm module to enable WiFi and the "Wake for Network Access" now appeared. Unfortunately, the LEDs on the ethernet port is still off which means I can't wake it up...

My I225-V is working properly. Wake on LAN is enabled. The strange thing is when I boot to Monterey using a 2nd SSD, I have the "Wake for Network" access and it's working fine. The problem is the option is missing when I boot to Ventura. It's the same EFI folder that I used to boot to both...

Does anyone know how to get Wake on LAN to work from sleep? Under Ventura, the "Wake for network access" option in "Energy Saver" is missing.

I've just updated from Monterey 12.2 to 12.4. Afterwards, I'm having intermittent problems with screen recording. Sometimes when I clicked the Stop recording, I got an error message saying "Your screen recording can't be saved". Does anyone else encounter this problem?

I've noticed that the "Startup Disk" pane can modify the nvram variable "efi-boot-device" without disabling SIP. Does anyone know how it achieves this?

The modification of default boot volume will be done inside a program as many times as needed, so I can't disable SIP as it will break MacOS update. As I mentioned in the first post, I'm looking for an alternative approach to programmtically modify the default boot volume without disabling SIP...

I need to change the boot volume programmatically. Changing the Startup Disk pane manually is not an option for me.

I'm running Monterey 12.1 with OpenCore 0.7.6. I understand you can define the default startup volume in "System Preferences" -> "Startup Disk". However, I would like to programmatically change the default boot volume. I've tried to change the NVRAM variable "efi-boot-device", but this...

Congrats! I've the same m/b. To get wifi to work, install "itlwm" & "HelliPort" from OpenIntelWireless. Make sure to install the latest Alpha version, not the stable release. I haven't tried bluetooth on ax201 yet, not sure if it works or not. https://github.com/OpenIntelWireless/itlwm/...

@sonny362, with your config.plist, my Intel I225V didn't work. There is a problem with DeviceProperies entry for the interface. It should be changed to: <key>DeviceProperties</key> <dict> <key>Add</key> <dict> <key>PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)</key>...

I thought my USB flash drive corrupted, but it's not. A newly created USB drive resulted in the same boot loop. I've a few HDDs & SSDs already installed in the system with Windows, Ubuntu and an old Mojave with Clover bootloader. It seemed the system was confused by all these bootable EFI...

Thanks again for your help. The "prev-lang:kbd" is a nice touch. :lol: I was guessing it's Russian, but I could be wrong.

Well, I've already fixed the Russian by deleting the "prev-lang:kbd" string and reset the NVRAM again. I've finished the first stage of installation and the system auto-rebooted. Then, it tried to load the USB again but got into a boot loop. That means, the USB flash drive somehow got...

@sonny362, I've just tested your EFI folder and encountered the exact same problem. Then, I decided to try to reset NVRAM. Viola, the installer now launched successfully, but in Russian I think. Well, that's a big step forward. Now, I will try to install Monterey. @bootmacos, thanks for the...