AMD Motherboards - Wake on LAN not working w/ FM2A88M Extreme4+

Print Page | Close Window

Wake on LAN not working w/ FM2A88M Extreme4+

Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=5785
Printed Date: 10 May 2024 at 5:30pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: Wake on LAN not working w/ FM2A88M Extreme4+

Posted By: MurderousJess
Subject: Wake on LAN not working w/ FM2A88M Extreme4+
Date Posted: 04 Aug 2017 at 11:28pm

I have a FM2A88M Extreme4+ that I bought about two years ago. Until recently I left the system running all the time (NAS), but in an effort to cut my power bill, I decided to have the NAS put itself to sleep on a timeout, figuring that I could use WOL to wake it up if I needed to access it again.

The sleep part works fine, I'm using OpenMediaVault as the OS/distro and it handles the sleep mode fine (system goes to sleep, power light blinks). However, no amount of network activity to the system seems to wake it out of sleep mode; I have to poke the power button to wake it up.

I've gone into the BIOS and ensured that Wake on LAN was enabled (it was). I thought maybe it specifically was looking for the WOL magic packet, so I signed into my router (pfSense) and had it send the magic packet... no luck.
I've verified that the MAC address my router is sending to is correct
I've tried both the onboard NIC as well as two different series of Intel server grade NICs (ensuring I was using the correct MAC each time)

Any suggestions as to why WOL refuses to work would be greatly appreciated. Thanks!

-- MJ

Replies:

Posted By: wardog
Date Posted: 06 Aug 2017 at 5:23am

" rel="nofollow - Hmmm, WoL is a PITA to diagnose over the internet.

So you know that, let's start with:

Does OMV need to have a Listening Port designated in the config UI?

I ask that as you're having issues with both"types' of NIC, internal and add-on. Leading me to believe it's within OMV that is not letting the packet "in"