After the Windows 10 upgrade, the WOL capability stopped working and on checking the driver, it seems that during the upgrade process the driver was updated to I tried downgrading to the previously working driver but this has not resolved the issue. Once I did, that worked out perfectly. Having things work but with high packet loss suggests something like that often the connectors start to fail intermittently But these things do die sometimes. WOL is still not working apart from when the PC is in sleep.
|Date Added:||7 April 2016|
|File Size:||36.16 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
I know the ethernet works You can follow the question or vote as helpful, but you cannot reply to this thread.
And I did all the following steps: Please can you advise what else I can try or come up with a fix soon. Did this solve your problem? The problem appears to be that Microsoft have not implemented the driver with this property in their version.
Marvell Yukon 88E Ethernet Controller – Dead? – TR Forums
Etherjet us about your experience with our site. Tech support scams are an industry-wide issue where scammers attempt to trick you into paying for unnecessary technical support services.
Yes I’ve tried changing the cat cable over for no change in performance.
Hi Si, Thank etherneg for posting the query on Microsoft Community. Now I’ve only just realise that for the last 2 weeks I’ve been running on 88e88056 WLAN rather than my LAN as my Asus mobo has both a Marvell controller for ethernet and a realtek card for wireless which I often use both apartment does not have ethernet cabling in the ceiling yet, so I run the cable from one room to another.
I do appreciate your efforts and time.
NB – Also note Windows Firewall blocked my Magic packet sniffer from checking this was being received so I completely disabled this for testing still blocked even if I had setup an incoming connection for this – but once setup and re-enabled this does NOT interfere with turning my PC on via WOL. As the Windows official driver does not resolve this problem, is there anything else you etbernet suggest or do? Is there anything else I can try?
No registered users and 0 guests. Instead of mobo ethernet port end?
We will be happy to assist you. Thanks, Mike Thanks for this reply, in order for the 88ee8056 shutdown setting to appear I ended up using driver version Si Johns Replied on December 11, If you can’t solve the problem any other way, an add-in NIC would be the easiest way to stop etherner your hair out.
MikeZ Replied on October 29, With Windows 7, even when shut down, the LAN ehhernet stays active waiting for the magic packet. I have the lights on the ethernet card when the PC is suspended this means that the ethernet card is not totally powered off and I’m sure the 88e80566 packet reach the device but still no wake-up of the machine. Having things work but with high packet loss suggests something like that often the erhernet start to fail intermittently But these things do die sometimes.
This thread is locked. I have a mysterious case of the failing marvell yukon ethernet port on my asus p35 mobo Well still no word on a fix for this and really disappointed not to have heard anything from Marvell so called customer service.
The more recent Windows 8 driver which although it doesn’t say it in the title, is also for Windows Server R2did not have the setting so did not solve the problem.
Marvell Yukon 88e ethernet WOL not working since upgrading to – Microsoft Community
I have checked the power management for the Ethernet card and the allow this device to wake the computer is enabled. I have checked all of the other 88e8056 you mention but when the server is shut down I cannot use WOL.
Surely others must be suffering something similar? In reply to al’s post on February 5, Any help is very much appreciated. This does provide the settings you mention: It would be good for Microsoft to update their driver and make this property available.