Bios upgrade = WOL stopped working !

[Knight77]

Hello,

I was hoping to solve a problem related to the video card so I decided to upgrade bios of my MB
(z68 pro3-m ), this didn't solve the problem related to the video card (I am "patching" it in another way in the end) but now the WOL is not working anymore.

Windows and the network adapter have the same settings I had when it was working and in the BIOS I enabled WOL via Lan and PCI (cannot recall the exact name of the settings).

Just to be sure of trying everything I updated the drivers of the network adapter but nothing changed. I tried to leave the check on the settings “Allow the computer to turn off the device to save power” but didn't changed. Then I took it off, but again nothing changed. FYI it was selected when WOL was working.

Any ideas ? Someone suggested to clear CMOS data but I have not done it yet. I just tried to load the BIOS default settings.

Last note: the fixed IP I assigned to the PC is still the same and in this way is identified by the router. Another thing: I didn't check how it was before when it was working but now when the PC is in sleep mode (actually I use Asrock istantboot that is the same) behind the PC, where the ethernet cable is connected there is no light showing anything at all, when it's on well...it's actually blinking. Don't know if this is something relevant.

Thank you for the support and hope someone will provide some good idea.

 

[bill001g]

A PC does not have a IP when it is running WoL. Since there is no OS running and the motherboard itself has no concept of IP it only understand mac addresses.

What it looks for is a broadcast packet that contains its mac address repeated in a special pattern in the payload. The chips in the nic card do this themselves the main cpu is not involved.

You must send the packet to the broadcast address of the subnet, the IP is dependent on ARP information and the nic will not respond to ARP since it is not a OS.

Now microsoft has their own WoL that only works on microsoft OS and I am not sure how that works.

Most times when you have a WoL machine plugged into a switch you will see lights on the port because just the nic card is being powered in most cases.

 

[Knight77]

A PC does not have a IP when it is running WoL. Since there is no OS running and the motherboard itself has no concept of IP it only understand mac addresses.

What it looks for is a broadcast packet that contains its mac address repeated in a special pattern in the payload. The chips in the nic card do this themselves the main cpu is not involved.

You must send the packet to the broadcast address of the subnet, the IP is dependent on ARP information and the nic will not respond to ARP since it is not a OS.

Now microsoft has their own WoL that only works on microsoft OS and I am not sure how that works.

Most times when you have a WoL machine plugged into a switch you will see lights on the port because just the nic card is being powered in most cases.

Thanks for the reply. However it is not clear to me what's your solution. I tried to wake it with the usual apps I have on my phone that were already configured and always worked - until now.

 

[bill001g]

First you phone would have to connected to wireless. You would need to key in the mac address in the application.

This is generally a bios setting but you said it is on.

 

[Knight77]

First you phone would have to connected to wireless. You would need to key in the mac address in the application.

This is generally a bios setting but you said it is on.

Yes, phone and tablet are connected Wi-Fi to the same net. Indeed, when the PC is awake, I can start Kodi (ex xbmc) with the same WOL command. It's just that the WOL command doesn't work anymore to wake the PC when in standby....

 

[bill001g]

It almost has to be some stupid bios setting since that is what you changed I doubt the transmission devices is working different. Generally the issue with the ip/mac not working is when you attempt to send it from outside your network. It is a pretty simplistic thing you turn it on or off. They may have moved it to another location in the bios, you are just going to have to dig though the screens until you find it. It generally like most things in the bios must be set on the special bios boot screens and not from inside windows. This used to be a really easy feature before microsoft got involved with their stuff.