[SOLVED] Minisforum MS-01 Wake On Lan won't work

[michaltill]

Hello,

On my Minisforum MS-01 I can't get WOL to work. It seems that none of the LAN ports have lights on when the computer is turned off/suspended/anything. Not a blink.

In BIOS the WOL feature is enabled, Deep S5 is disabled.

I can't even decide if the fact that LAN ports don't blink when the PC is off is controlled by the pc itself or by the system (Proxmox VE).

Thanks

 

[michaltill]

EDIT: SOLVED.

Advanced > Onboard Devices Settings > Scroll Down to PCH-PCIE Port

I226-V NIC ASPM is the second option. Change from Auto to Disabled

ASPM is some power management feature that turns off the LAN ports.

 

[user007]

I have the same problems. I do not get it working . If I shutdown ms-01 the network card is also down, so I am not able to open intel amt.

Any solution?

 

[ember1]

I wonder the same thing.

I have disabled the ASPM and selected the wake on lan feature in bios, but it doesn't work.

with ethtool it also shows:

Supports Wake-on-g: g
Wake-on g: g

Is it because of sfp+ ?

 

[bithavoc]

these Minisforums are crap and don't work as servers, reporting worse for Minisforum UM890 PRO:
1. Wake On Lan(WOL) only works when it soft turns off via OS, it does not work on power loss.
2. Wake On AC is not even available on the Bios, only wake on lan and wake on rtc but none of them work properly.

 

[metlrise]

do you have any alternatives?

 

[randman]

these Minisforums are crap and don't work as servers, reporting worse for Minisforum UM890 PRO:
1. Wake On Lan(WOL) only works when it soft turns off via OS, it does not work on power loss.
2. Wake On AC is not even available on the Bios, only wake on lan and wake on rtc but none of them work properly.

I got an MS-01 (came with BIOS v1.26 out of the box). I got MeshCommander to work. Power Off works. KVM functionality works. But, what should be the pièce de résistance of vPro, Power On, does not work. I can use MeshCommander to power it off. However, once powered off, MeshCommander can't power it on (no "Power On" command. WOL doesn't work. I checked the back of my MS-01, and the LEDs for the vPro RJ45 port are off. I checked all relevant BIOS settings:

- all ASPM settings are Disabled,
- "Wake Up On LAN" setting is Enabled,
- "Deep S5" is Disabled

I followed this excellent vPro guide for other settings:

Step-by-Step Guide: Enabling Intel® vPro™ on Your Minisforum MS-01

Complete BIOS configuration guide to enable Intel vPro and AMT on the Minisforum MS-01 for remote KVM access using MeshCommander.

spaceterran.com

But, unfortunately, once MeshCommander powers off the MS-01, or, I power off the MS-01 from its front power button, the LEDs of the vPort RJ45 ethernet port turn off, and the MS-01 is no longer reachable.

I don't yet have an operating system installed in my MS-01. Someone said that if they power down the MS-01 via their operating system, they can remotely power it back on? But otherwise, it can't be powered on remotely? Can other people confirm that they get the same behavior : if the MS-01 is powered off via its front power button or via the Mesh Commander that its network interface can't be reached anymore?

For now, in the BIOS, I changed "Restore On AC Power Loss" from "Always Off" to "Always On". As a kludge, I can use a smart outlet that can be turned on or off in order to power on the MS-01. But not happy about having to do that... The one thing that I would have liked to get out of vPro, power on, doesn't work!

 

[randman]

I got an MS-01 (came with BIOS v1.26 out of the box). I got MeshCommander to work. Power Off works. KVM functionality works. But, what should be the pièce de résistance of vPro, Power On, does not work. I can use MeshCommander to power it off. However, once powered off, MeshCommander can't power it on (no "Power On" command. WOL doesn't work. I checked the back of my MS-01, and the LEDs for the vPro RJ45 port are off. I checked all relevant BIOS settings:

- all ASPM settings are Disabled,
- "Wake Up On LAN" setting is Enabled,
- "Deep S5" is Disabled

I followed this excellent vPro guide for other settings:

Step-by-Step Guide: Enabling Intel® vPro™ on Your Minisforum MS-01

Complete BIOS configuration guide to enable Intel vPro and AMT on the Minisforum MS-01 for remote KVM access using MeshCommander.

spaceterran.com

But, unfortunately, once MeshCommander powers off the MS-01, or, I power off the MS-01 from its front power button, the LEDs of the vPort RJ45 ethernet port turn off, and the MS-01 is no longer reachable.

I don't yet have an operating system installed in my MS-01. Someone said that if they power down the MS-01 via their operating system, they can remotely power it back on? But otherwise, it can't be powered on remotely? Can other people confirm that they get the same behavior : if the MS-01 is powered off via its front power button or via the Mesh Commander that its network interface can't be reached anymore?

For now, in the BIOS, I changed "Restore On AC Power Loss" from "Always Off" to "Always On". As a kludge, I can use a smart outlet that can be turned on or off in order to power on the MS-01. But not happy about having to do that... The one thing that I would have liked to get out of vPro, power on, doesn't work!

I figured out my problem (can't power on MS-01). Earlier, my MS-01's vPro 2.5GbE Ethernet port was plugged into my Unifi USW-Aggregation switch's SFP+ port using an SFP+ to RJ45 adapter. This setup was working just fine for everything, except when it comes to powering on the MS-01. When using the SFP+ to RJ45 adapter, once the MS-01 is powered off (via Intel AMT https GUI, or MeshCommander, or the MS-01's power button), the LEDs of the vPro RJ45 port turned off. Ping failed, WOL failed. Of course, power on wasn't available.

Then, I moved the MS-01's vPort ethernet cable to another switch that had RJ45 (no SFP+ to RJ45 transceiver). Now, Power On works. If the MS-01 is powered off, the vPort RJ45's LED is still on. So, lesson learned: WOL/Power On don't work when using an SFP+ to RJ45 transceiver on an SFP+ port. I should have thought of that to begin with.

 

[randman]

Maybe this will help others: in my Unifi switch, 2.5GbE port does not work, but a 1GbE port in the same switch works. Details below.

With my Unifi USW-Enterprise-24-PoE switch, when using a 2.5GbE port, Intel vPro/AMT cannot power on the MS-01. I can use other MeshCommander functionality (remote desktop, power off, etc.), except Power Up. Once I power off the MS-01 using AMT or MeshCommander (either using "Power Down" or "Soft-Off"), I can no longer wake it up via AMT/MeshCommander. I can't even ping the MS-01. The vPro/AMT RJ45 port's link status LED is off.

However, if I use a 1GbE port on the same UnifiUSW-Enterprise-24-PoE switch, vPro/AMT can power it on. When the MS-01 is off, the MS-01's vPro/AMT's RJ45 link status LED blinks orange, and I can ping it just fine.

I tried many different settings to try to get the 2.5GbE port to work (including turning off auto-negotiate of the speed by manually setting it to1GbE and 100Mbps). No changes helped. I can only get AMT/vPro power on to work with a 1GbE port (on the same switch as the 2.5GbE port).

I also tested using the switch in my Unifi U6-Enterprise-IW, which has 1GbE ports. No
problem with that switch.

 

[et_phonehome_2]

I am not using the SP+ ports at all. The problem is that once the sleep settings is turned on for the computer, it will not awaken the LAN ports. The keyboard keystroke is unable type anything and I am lucky if I get a mouse click in to check Task Manager. The Task Manager show no disk i/O at all, the LAN adapter showed no IP addresses. The only way around this is to shutdown and power back up the machine. This is totally f**k up.

 

[TechUnsupport]

I'm not an expert on WOL or switch, but my understanding is that when the power is off the link between WOL supported switch and some NIC are connected at 10mbps. Maybe the switch that has problem with it won't support WOL isn't because those 2.5g port won't support 10m speed?

 

[joeribl]

I'm not an expert on WOL or switch, but my understanding is that when the power is off the link between WOL supported switch and some NIC are connected at 10mbps. Maybe the switch that has problem with it won't support WOL isn't because those 2.5g port won't support 10m speed?

Looks like you are correct. i225 and i226 links on 10Mbps when in S3,S4,S5. And most newer 2.5 or 10 Gb switches only support going down to 100Mbit.

 

[TechUnsupport]

I'm happy to report that my cheapo $60 XikeStor 8port 2.5G + one 10G SFP+ managed switch can auto all the way down to 10mbps. If you see the price above $60, blame TACO trade.


PS: I did try WOL on that port 7 and it works.