XW6400 WOL problems

Hi everyone.
New to this forum.
I have recently bought a used XW6400, very pleased with the spec and performance.
However, I have been having a problem with the WOL option.
I'm using a small app called Wake UP, this works fine, no problems waking up the PC from my iPad on my own LAN.
Likewise with TeamViewer.
But, trying to wake up the PC from outside my own LAN only works while the PC has been running for a while, in other words while it is warm inside, if I leave it switched off for a couple of hours (and sometimes shorter) it won't wake up.
I then have to wake it up from my own LAN again.
I'm using DynDns.org, I don't see that as the problem as everything works fine when the PC is warm.
I've been in the electronics maintenance business nearly all my life, and this makes me think that maybe there are faulty capacitors causing the problem, there are 3 capacitors that have bulged a bit, I'm just wondering if they are tied in to the power supply for the NIC, which is the intergrated Broadcom Extreme Gigabit ethernet device.
The 3 capacitors in question are very close to the memory fan connector, and has a small torodial choke nearby.
If anyone has any ideas about this problem, I would be most grateful.
Rgds Bob (UK)

Hi Paul.
Thanks for that.
I would like to know what those 3 capacitors do, it looks like a small DC to DC regulator but not sure.
It might turn out that that area isn't linked to the NIC power requirement at all. in which case I'm barking up the wrong tree :-)
Is the NIC 3.3v fed from a motherboard regulator circuit, or is it fed from the main high amperage (18A) part of the main power unit?
That would help me pinpoint the problem more quickly.
Does anyone know what that small circuit area does (3 caps and a small choke) near the memory fan connector?
Rgds Bob (UK)

Similar Messages

Q180 WOL Problem

Looking to use my Q180 as a media center so Wake On Lan needs to work for me. This is my second Q180. The first unit I bought had no DVD drive but WOL worked perfectly fine. My other PCs and my Xbox could wake the Q180 from sleep by sending a magic packet. I returned that one to get one that had the DVD drive. For some reason WOL will not work on this unit. I thought it was my Xbox but I tried 2 other computers and they could not wake the unit. I went into device manager and checked the NIC card to make sure power management allowed WOL, which it did. Not sure if there's something wrong with the NIC in my unit but I need a solution soon or else I need to send it back. Any input would be helpful. Thanks.
Solved!
Go to Solution.

Hello nsainfreek and welcome to community,
As I understand you want to have Wake on Lan feature for the remote login.
By default the desktop comes with Wake on lan option as enabled, you can check in BIOS.
If then also you face some issue then you can try these steps.
1. Open Network and Sharing Center (click the Start button, type Network and Sharing in the Start Search box, and press Enter).
2. Click the Change adapter settings link in the upper left of the navigation pane.
3. Right click the network connection you want to enable/disable power management support on and click Properties.
4. Click Configure.
5. On the Power Management tab, check or clear the Allow the computer to turn off this device to save power check box.
      When checked, power management is enabled on the network adapter.
      When cleared, power management is disabled on the network adapter.
6. You can enable Wake on LAN for all wake methods or just enable magic packet WoL:
      To enable Wake on LAN for all methods, check the Allow this device to wake the computer check box.
      To enable Wake on LAN for magic packet only, check the Allow this device to wake the computer check box and then check Only allow a magic packet to wake the computer check box.
7. Click OK.
Configuring Wake on LAN settings using the command line
You can use the netsh command to force the operating system to wake on ARPs, and NS on a per network adapter basis—but only for computers that are joined to a domain.
To force a network adapter to wake on ARP and NS
1. Open a command prompt with administrator privileges. (click the Start button, type Command Prompt in the Start Search box, right click Command Prompt, and click Run as Administrator.)
2. Type netsh interface ipv4 show interfaces. This will list all of the available network interfaces; note the index (labeled Idx) of the network adapter you want to modify.
3. To force the network adapter to wake on ARP and NS type netsh interface ipv4 set interface [index] forcearpndwolpattern=enabled. If successful, OK will be returned.
4. To revert to system default type netsh interface ipv4 set interface [index] forcearpndwolpattern=disabled. If successful, OK will be returned.
Kindly try this and let us know.
Best Regards,
Tanuj
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution".! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Problems with wol for multiple workstations

I right click machines and they will wake up individually. but if I
high-light those same machines and right click , and wakeup not all will
come on. and it is intermittent one this time and a different next. any
ideas

Darrell,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at
http://support.novell.com.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://support.novell.com/forums)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

I will Paypal you $100 if you can resolve this Port Forward problem

Believe me when I tell you, If you are the person who fixes this problem, I will GLADLY Paypal you $100.
This is so unbelievable. Short story is, after 12 hours of paid support through Support RIX, 6 hours with TWC support, and 4 different modems there isn't a single person in these groups that can get ports forwarded on my Linksys E4200 router.
I am running a fresh copy of windows 7 with all updates and no anti virus installed. I purchased a Motorola ARRIS SURFboard modem 200 series DOCSIS 3.0 so I have no double router issues. Before I was using the TWC moden/routers in bridge mode.
I have no problem setting a static IP or configuring port forwarding. It doesn't matter if I have windows firewall on or off. I can't get an outside port checking website that can verify an open port.
I am trying to play Battlefield 4 using the port forwarding request they provide.
If I run a local port check program on my computer it will confirm the ports open. Ok, Fair enough. They tell me the outside port checking utilities will say the port is closed unless I am running the program that uses these open ports.
SO I run the game and check and it always says port closed. One of the ports I want to open is 80. It has to be open to get internet anyway but it still shows closed using the online port checking websites.
I connected the computer to the modem. No router. I keep getting ports closed or filtered when I check through 6 different port checking sites. Leads me to think their is some kind of block in the ethernet card software.
Its a Realtek PCIe GBE Family controller with a driver date of 8/26/2014. Latest one I could find.
I think its an ethernet card filter. Just my thoughts. Here is the current adapter card settings.
Advanced settings on Ethernet card
Auto Disable Gigabit/ Disabled
Flow Control/ RX & TX Enabled
Green Ethernet/ Enabled
Interrupt Moderation/ Enabled
IPv4 Checksum Offload/ RX & TX Enabled
Jumbo Frame/ Disabled
Large send Offload v2 (IPv4)/ Enabled
Large Send Offload v2 (IPv6)/ Enabled
Network address/ You can check the box for Value and add one. Currently its checked to Not present
Priority & VLAN/ Enabled
Receive buffers/ 512
Receive Side Scaling/ Enabled
Shutdown Wake-on-Lan Enabled
Speed and duplex/ Auto Negotiation
TCP Checksum Offload (IPv4)/ RX & TX Enabled
''''''''''''''''''''''''''''''''''''''(IPv6)/ RX & TX Enabled
Transmit buffers/ 128
UDP Checksum Offload (IPv4) RX & TX Enabled
'''''''''''''''''''''''''''''''''''''''(IPv6) RX & TX Enabled
Wake on Magic Packet/ Enabled
Wake on Pattern match/ Enabled
WOL & Shutdown Link Speed/ 10 Mbps First
I used a port tester downloaded from PCWinTech.com v3.0.0. It says the ports are open. When I close port 80 it says port 80 is closed. My problem is nothing outside my network can confirm an open port. It always states port closed.
The game I am playing is Battlefield-4. I have played all of the campigns without any problem but once online it crashes. The BF-4 community says I need to open 5 single ports and 5 port ranges. This is what I am trying to do.
We have tried an ARRIS router modem, a Ubee router modem (both in bridge mode) and are now using a motorola modem. All with the same problem. We checked the ports during game play and they all say closed.
I will post pictures of my current router settings.

What model router do you have?
What Firmware version is currently loaded?
What region are you located?
What is your current model ISP modem your using now?
What ISP Modem service link speeds UP and Down do you have?
Check cable between Modem and Router, swap out to be sure. Link>http://en.wikipedia.org/wiki/CAT6 is recommended.
Check ISP MTU requirements, Cable is usually 1500, DSL is around 1492 down to 1472. Call the ISP and ask.
http://kb.linksys.com/Linksys/ukp.aspx?vw=1&docid=88e63d78588142e6bb68e22d7faf2046_Configuring_the_M...
Router and Wired Configurations
Setup DHCP reserved IP addresses for all devices ON the router. This ensures each devices gets its own IP address when turned on and connected, eliminates IP address conflicts and helps in troubleshooting and maintain consistency for applications that need to connect as well as mapped drives.
Ensure devices are set to auto obtain an IP address.
If http://en.wikipedia.org/wiki/Ipv6 is an option on the router, select Local Connection Only.
If you set up port forwarding, disable uPnP and test.
When you check for port status, you have to be actively using the port before you scan check as you may get a false negative if your not using the port. If your using the port then check the status, you should get an accurate result.
I would try using Port Range Triggering instead of PF and set up the port as follows for your PC that your gaming with:
0 thru 65535. A bit less hassle to set up then all those different port rules.
PC 3rd Party Security Software Configurations
Turn off all anti virus and firewall programs on PC while testing. 3rd party firewalls are not generally needed when using routers as they are effective on blocking malicious inbound traffic.
Turn off all devices accept for one wired LAN PC while testing.
Disable any downloading client software managers, i.e. Torrents or similar.

No WOL in Windows 7

I am running Boot Camp 3.1 with Windows 7 64bit on my iMac 27" (2.8 GHz Quad-Core). Everything runs fine so far, except Wake On LAN. When Win7 goes to sleep I can wake it up once, but after the next sleep it cannot be turned on again with a magic packet. I've tried that under OS X and this works without any problems. I found out that if I change any parameter in the advanced tab of the "Broadcom NetXtreme Gigabit Ethernet" device properties the driver will be reloades with the result that I can wake it up once again. I assume that this is a problem with the network card driver, but installing the latest from the Broadcom website did not work.
I'd really like that to work, because I'd like to have the iMac sleep while I don't use it. So any help is very appreciated!

My macbook pro has the same nic driver like my imac - but with the macbook wol is working perfect. So this is a little confusing and I'm not sure if this is a driver issue. Anyway I have a solution that works. The thing is, that wol only works one time after startup/standby but when you disable and enable the adapter its working again. So look for devcon (microsoft device control under console cmd) in 64 bit version. Do “devcon find =net” and look for your nic. Write a batch file like the following but chage the parameter with your nic:
C:\Devcon.exe disable "@PCI\VEN14E4&DEV_1684&SUBSYS_168414E4&REV10\4&27724676&0&00E0"
C:\Devcon.exe enable "@PCI\VEN14E4&DEV_1684&SUBSYS_168414E4&REV10\4&27724676&0&00E0"
Start this batch (taskplanner) during wakeup – that’s it.
Mike

Problem instaling Subscriber in netware cluster

Hello.
I am using ZSM 7.0.1 installation program and trying to install only
subscriber functinality on a cluster OES Netware with Sp5.
The installation says it goes successful in the 2 logfiles that comes up
after the installation but when I try to offline and then online the
cluster-volume with the ZSM7 installed on it it goes into comatose because
the zfs.ncf is missing in the zenworks folder on the volume. I can not find
the file on any other volume on the server. I also have the ZDM701 installed
on the server before I install ZSM701 on it. The ZDM701 install was totaly
fine and it works great. The only ZDM701 services installed on the server on
the same volume is WOL, Import and Removal.
So my question is, how am I supose to get the right files and folders into
the cluster and to get it work. It should not be a problem.
Does anyone no what to do.
Thanks
Best regards Jonas Rydstrom

ZSM is supported on a cluster, you have to choose though to have either a
single cluster resource installed with ZSM or installing in on the
individual nodes. In this case it looks like Jonas installed ZSM on a
cluster resource, that's supposed to work, not sure why zfs.ncf isn't there.
Ron
"Jared Jennings" <[email protected]> wrote in message
news:Jv_4i.5587$[email protected]..
> Jonas Rydstrm,
>
>>OK, can you be more specific about what is not supported. I was succesful
>>installing both ZDM701 and ZSM701 Distributor, Subscriber and database on
>>a
>>single server to specific zenworks volume and the services on that server
>>seems to run fine.
>
> It is not supported to run individual subscriber objects on cluster nodes.
> The only portion of ZFS that is supported in a cluster environment is the
> distributor object.
>
> So, you are correct in that you can run ZFS, ZFD, and the database on a
> non-clustered server.
>
> You can also run ZFD on a clustered resource. The ZFD 7.0 with SP1 install
> correctly installed all the files to the clustered volume so that the
> services could load and fail-over with the information being consistent.
> All ZFD services load from \\clusteredvolume\public or
> \\clusteredvolume\system etc.
>
> ZFS supports clustered environments, but the clustered resource that loads
> the distributor code, cannot send distributions to subscriber objects
> representing nodes in the cluster, nor can it send to the clustered
> subscriber object that does exist and represents the clustered zfs
> resource.
>
> --
> Jared Jennings - Data Technique, Inc.
> Novell Support Forums Sysop
> My Blog and Wiki with Tips, Tricks, and Tutorials
> http://jaredjennings.org

G31M3 V2 OnBoard LAN - WOL works Intermittantly

I've set up G31M3 V2 mainboard using on board LAN (Realtek RTL8139/810X) to wake on lan via internet/cable router from the power off mode.
When I shut down the target (remote) computer I can restart within a few minutes using a 'magic packet' (so I assume all router port forwarding and LAN settings are correct). But, if I leave that target computer switched off for half hour or more I can no longer start it using the 'magic packet'.
I'm guessing that charged capacitors are allowing the restart after short power off time but are discharging and preventing activation via LAN after a period of time.
This would mean that power is not being supplied to LAN when computer is shut down. Is there a setting in BIOS that I'm failing to see that ensures power remains applied to LAN board when computer is shut down (but still plugged into power) Could it be my actual Power Supply?
I have wake on PCI-E & wake on PCI (PME#) enabled in bios.
Any thoughts?

Last year I lost interest in this problem after getting nowhere. Now I'm keen again to try to get WOL working on my computer.
I've re-read this thread and everything I wrote initially is still the case and the problem.
The last reply I had was from 'Cronnin' suggesting checking bios setting.
As I stated in my original question/problem I have enabled 'wake on PCI-E', 'wake on PCI (PME#)' in bios and tried with one or the other enabled and with both enabled.
1: The computer starts from 'shut down' S1 mode via a 'magic packet' if I send the 'magic packet' within a few minutes of shutting down, therefore I assume all addresses, port-forwarding, wol bios settings etc are correct
BUT
2: Sending exactly the same 'magic packet' after the computer has been shut down for 1/2 hour or more will not turn it on.
The thing that I still think points to the problem is the fact that the green led on the onboard LAN NIC goes off when the computer is shut down (S1 mode). It also goes off when 'S3' mode is selected in bios.
Incidently, in both those shut down modes the 'num lock' led on the keyboard is still on so I gather the PSU is still supplying 5V to the mainboard.
I'm leaning to the idea that the problem is a fault with the motherboard or on-board NIC. Does anyone have any other suggestions?
Thanks in anticipation.
Agathosthenes

Mac Pro sleeps after being woken up by WOL

Hi Folks
In order to wake up my Mac Pro on demand, I have set up Wake Over LAN (WOL) over the network and enabled "wake for network access" at System Preferences > Energy Saver on the Mac Pro. Now I am able to wake up the machine from my local router or across the Internet, but just wake up for a little while only.
The issue is, after the Mac Pro is being woken up by WOL for about 30 seconds, the machine always goes into sleep mode again for no reason. During the short alive period, the virtual machines running on the Mac Pro are pingable but the monitors are not on and the replaying YouTube video has no audio.
However, if I click the mouse or press the keyboard, the Mac Pro can be woken up as expected: the monitors are powered on, YouTube video is audible, all VMs are pingable too.
Why does my Mac Pro get woken up this way? How to fix it?
Thanks heaps in advance.
Regards,
B

> Now I am able to wake up the machine from my local router or across the Internet, but just wake up for a little while only.
From my local router, I use below way to wake up the Mac Pro.
I can also wake up the Mac this way over the Internet.
For your information, I can successfully wake up other WOL enabled Windows machines this way on the same network with no problem.
As mentioned, both ways can only wake up the Mac Pro for about 30 seconds, then machine will automatically sleep again though at System Preferences I have set the computer to sleep after "3 hrs" or "never", as shown below.
What I expect is just to make the Mac Pro back to work the same way like I locally press the keyboard or click the mouse, not to automatically sleep again in seconds.
Any thought please? Thanks!
R C-R wrote:
bengmugenr wrote:
The behavior is normal when clicking the mouse or pressing the key to wake the Mac, the issue only occurs when trying to wake via WOL. Never thought the same wake process could have different results.
Please explain specifically how you are trying to WOL, what you want to accomplish by doing so, & how long you think whatever it is you want to accomplish should take.
Also, what VM's are you running & by what method do they run (like via Parallels or whatever).

ZENworks Imaging & Image Safe Data Problems

Hi All,
I'm in the preparation stage of a Windows 7 rollout to 4000 desktops. So far we've packaged up 200 applications/bundles and tested them against our image, everything on that front is fine.
Our new ZENworks 11.3.2 server is being now being used to deploy our old Windows XP images (created in ZfD7), I'm using hardware rules to do this and it's working perfectly.
When I use the hardware rules to deploy our new Windows 7 Image it will image once as expected. The PC then boots, a powershell script will build the hostname from the model and serial number, join the domain, install the ZCM agent and all looks good.
The problem comes later when I try to image the machines again, we get "no work to do". After some reading I assume this is because of the Image Safe Data.
I've tried a things so far but seem to be getting inconsistent results, basically each time I PXE the machine I want the machine to use the hardware rule to pull down the image.
The only way I have found that seems to work,is to clear the Image Safe Data and delete the "Novell ZENworks Image-Safe Data Service" after the agent has been installed (as part of my build script). This seems like overkill to me and I'm sure I'm missing something. Help!
Any help/guidance would be much appreciated!
Thanks
Carl

Often the just use the ZCC to tell the device to Apply the Assigned Image and then upon reboot it will just apply the image.
Some often script this with WOL so that every morning at 3am all of their lab devices will re-image.
Also you don't want to "Delete" the ZISD Service, it is better to configure the Default ZCM Agent Settings to install that service if you do not want it.
Otherwise, it will come back.
You may also be able to make configure the ZCM Imaging Menu to Always show when PXE Booting.
Then you could manually select an image to restore, regardless of the state of the ZENworks Image Safe Data.
Originally Posted by carlhanson
Thanks for the reply Craig.
We haven't used an "Imaging Scripts", we've only used the "ZENworks Image" bundle category.
It seems to be working the way we want now, although I'm still not entirely happy with the changes we've had to make...
Added C:\Program Files\Novell\ZENworks\bin\preboot\ZISWIN.EXE -WIPE to the HKLM\..\Run registry key.
Deleted the "Novell ZENworks Image-Safe Data Service" service.
I'm not sure how this will effect client machines in the future when we update the Agent.
When other customers reimage a machine which is already registered in ZENworks, do they push out images from the console?

Xw6400 fails to detect SSD

Hello
I fitted a Samsung SSD to my xw6400, after updating the BIOS and applying the BIOS settings outlined elsewhere. I never did manage to get AHCI Mode actuivated, even after doing a complete reinstall of Windows 8 and 8.1, but the performance boost is quite good enough without it.
My concern is that sometimes when I restart the machine from Windows, it will fail to detect the SSD, which is the system drive. It doesn't happen often and it's not a big deal anyway, since, if I switch off and on again, it does always discover it at power-on. This may prove to be a problem, though, if I'm away from home and need to access the machine remotely. Of course, I could avoid it by switching off Windows automatic updates before I leave home, but the problem is being old, so I will probably forget.
Does anyone have any ideas how I can remedy this?
Thanks in advance.

Hi:
If you are using a SATA III SSD, this may be the problem...
http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay/?javax.portlet.begCach...
I had the same thing happen to me on my dc7800 CMT when I installed a SATA III WD mechanical hard drive.
When I put the HP 1 TB Seagate hard drive from my HP 8200 Elite into the dc7800, it worked just fine as did the WD SATA III drive in my 8200 Elite.

802.1x and WOL issues

OK here is the deal. We use 802.1x with ACS as the Radius server. We also use WOL to wake computers for patching and remote use. We cannot get rid of WOL or 802.1x. We also cannot have ports assigned to our Data VLAN since that would, in the eyes of the auditors, allow unauthorized devices on the VLAN. We use a "Sleep" VLAN and then use ACS policies to assign the authenticated device to the proper VLAN. We also have VOIP with the computers connected to them. Here is the actual issue we are having. It seems that on some switches even with sleeping computers the "Sleep" VLAN is down/down or up/down. If there is at least one computer that is asleep and not behind a phone everything works fine. It looks like an issue with the phone and enhanced CDP. We are looking for a way to have the "Sleep" VLAN always up/up even without devices connected. We have been tossing around ideas like having a loop so that STP runs for that VLAN, connecting a layer 3 interface to a layer 2 interface on the same switch, even connecting a phone on every access switch and placing it in the "Sleep" VLAN. We are looking for better ideas.
Thanks.

Hello,
I suspect your problem is the fact that you're using self-signed certificates, but you haven't installed and trusted the root cert that issued them. The reason the phone can't validate the certificate is because it doesn't trust the issuer (or you don't have all of the certificates in the chain if you have intermediate CAs). That's also the problem with your Mac client forcing you to hit 'Accept' each time you authenticate - it doesn't trust the root CA. You should be able to talk to your IT folks to get a copy of it to import and trust (the certificate itself isn't secret).
1. Once you have the certificate, import it into your Mac's keychain and set the appropriate trust settings.
2. You should use the iPhone Configuration utility to create a profile to install the certificates onto the phone. On the Credentials tab hit '+' and browse to the location of the root certificate you got from IT. Once it's part of the profile you can then setup the Wi-Fi settings as needed.
This can get tricky, depending on the configuration your IT staff has in place. They should be amenable to providing you the same information they'd provide a Windows client (hopefully). Do you know what kind of EAP type you're using on your network? From the log the client is negotiating PEAP, which I assume is correct.
You'll need to get the certs ironed out before this will work reliably.

Thinkpad S540 possible BIOS bug concerning WOL

I have had a Thinkpad S540 for a few months, and have it installed as dual boot Windows 8.1 and arch linux. After completely shutting the machine down from linux I found that the battery would be down to around 70% charge after three days unused, and decided to investigate this problem since it was not reasonable for a new battery to lose charge at anything like this rate.
By chance I came across a piece of information concerning the issue of disabling WOL (Wake on LAN) on the network interface, since I had seen one report that by default WOL is enabled and this requires power to be going to the network interface even when shut down in order to be able to respond to magic packets to start the machine up when it is shut down.
First I checked the BIOS WOL setting and found it was set to "AC only" by default. So I changed it to disabled. This machine has the latest available BIOS version 1.54.
However on investigating this after rebooting in linux I found that
# cat /sys/class/net/enp3s0/device/power/wakeup
enabled
# ethtool enp3s0 | grep Wake-on
Supports Wake-on: pumbg
Wake-on: g
So WOL was still enabled despite it being set to disabled in the BIOS!
I learned that I can make sure that in arch linux the WOL setting can be changed to set to disabled after bootup by using a udev rule:
# cat 70-disable_wol.rules
ACTION=="add", SUBSYSTEM=="net", KERNEL=="enp3s0", RUN+="/usr/bin/ethtool -s enp3s0 wol d"
Then rebooting the machine I checked the WOL setting and it really is disabled now:
# ethtool enp3s0 | grep Wake-on
Supports Wake-on: pumbg
Wake-on: d
# cat /sys/class/net/enp3s0/device/power/wakeup
disabled
So I then ensured that the battery was 100% charged and shut down the machine and left it two and a half days - rebooting this morning the battery was still at 100% charge and no longer discharges unnecessarily when the machine is switched off, so this is a clear indication of a bug in the BIOS for the WOL setting - it is still enabled despite the BIOS saying it is disabled!
How do I report this to Lenovo so that they can fix the BIOS and release a new one that is working?
I am aware of other users with different Thinkpads who seem to have the same problem, so this may be more widespread an issue than just on the S540.
It is also not just an issue with the battery running down when fully shut down but will likely also be a problem for a machine in suspend mode since the network interface may be consuming a watt or so of power when in suspend, which will again run the battery down at an unacceptable rate.
I cannot imagine any use case where it would be necessary to have WOL enabled on a laptop that is mostly going to be used mobile - so having the default setting to AC only enabled, and having a BIOS bug enabling it when it is explicitely disabled is a serious problem.

Anyone running windows in the same laptop can check the same issue of battery drain due to WOl being enabled by default - in the Device Manager under the network card, opening the settings menu for the ethernet wired card the default for Wake-on-LAN on my computer was set to enabled. This can be changed to disabled, and you may need to also disable the setting for Wake on Magic Packet. Also in the Power Management tab it is possible to uncheck the settings for "Allow this device to wake the computer" and "Only allow a magic packet to wake the computer"
In my laptop these were all set to enabled by default.

Question about WOL (Wake on LAN) Unicast method

Hi, We are trying to get WOL working here on our enterprise network using the Unicast method. It seems that this method depends on the machine you wish to wake having an entry in the router/switch ARP cache. The problem is that this cache
times out rather quickly by default and the suggestion was to increase this timeout setting so the entry stays in the cache longer when the device goes offline. Our WAN guys are saying that is a bad idea and can cause all kinds of issues if we set this
to say 12-24 hours. How is everyone else using Unicast WOL dealing with this issue?

A few corrections and notes:
- Yes, unicast WoL traffic requires the system to be in the ARP cache of the final layer-3 device. This has nothing to do with WoL though. This is a requirement for *all* unicast traffic. That's simply how ethernet works.
- Subnet-directed broadcasts aren't less secure. They can however be exploited enabling certain types of DoS attacks most notably the Smurf attack. This can be easily and reliably mitigated as mentioned though.
- "Both methods require routers to forward UDP packets from your site server." This is a deceptive statement at best. In Unicast, the traffic is transmitted just like all other traffic on the network and requires nothing special on the network
side and no configuration of any "forwarding". Only with subnet-directed broadcasts is the network required to "forward" traffic.
- While a consideration, DHCP is usually not a factor with desktops unless you have a ridiculously short lease time. With laptops, same story unless they actually change subnets but then there's nothing you can really do about that. This is why I recommend
setting the heartbeat to at least once a day if not more often however.
Finally, do you know about Peer wakeup in 2012 SP1 and R2? Peer wakeup is much more reliable. You generally use unicast with peer wakeup but it overcomes the ARP cache limit.
Jason | http://blog.configmgrftw.com | @jasonsandys

[SOLVED] Notebook temperature problem

Hi everyone,
I use Arch Linux (i686) since 2008 on different machines. But my Acer 8935G Notebook is giving me headaches for some time now.
I bought it one year ago and Arch Linux ran nearly out of the box (ALSA drivers took some time, but that's done). In spring I noticed, that the computer is getting hotter than it did before (Idle: 70° Celsius / 158° Fahrenheit). In Windows Vista, I get idle temperatures around 40° C (104° F). And before spring, I got temps booting Linux around 50° C (122° F), which was absolutley okay and worked for me.
I didn't change system settings or configurations, and I tried some possible solutions, because I thought, maybe it's a kernel problem, but that's just a wild guess.
What I did so far:
- trying alternate kernels (BFS, CK, ZEN)
- tried different cpufreq settings (dynamic cpu scaling is working -> cpufreq-info)
- undervolting via intel-phc (no changes in temperature at all)
- tried powertop
none of that worked.
I have to say, that's not just a Arch Linux-related problem, other distributions give me the same problems (PCLinuxOS 2010, Linux Mint KDE 4.4).
My question so far is - has anybody experienced similar problems and found a solution for it?
Thanks in advance for the help - I'll really appreciate it.
PowerTOP 1.13 (C) 2007 - 2010 Intel Corporation
Sammle Daten für 30 Sekunden
Ihre CPU unterstützt folgende C-Status:C1 C2 C3 C4 C5 C6
Ihr BIOS meldet folgende C-Status:C1 C2 C6
Cn Verweildauer
C0 (Prozessor läuft) ( 5,0%)
zyklisches AbfraC1 mwait 3,0ms ( 0,0%)
C1 mwait 0,5ms ( 0,0%)
C2 mwait 2,6ms (20,9%)
C6 mwait 4,4ms (74,0%)
P-States (Frequenzen)
Turbo-Modus 3,2%
2,67 GHz 0,2%
2,14 GHz 0,3%
1,60 GHz 1,2%
800 MHz 95,1%
Aufwachen pro Sekunde : 248,2 Intervall: 30,0s
Keine ACPI Stromverbrauch-Schätzung verfügbar
Häufigste Ursachen für das Aufwachen:
31,8% ( 88,3) [kernel scheduler] Load balancing tick
28,4% ( 79,0) PS/2 keyboard/mouse/touchpad interrupt
8,7% ( 24,1) [iwlagn] <interrupt>
8,4% ( 23,4) [extra timer interrupt]
3,9% ( 10,9) [Rescheduling interrupts] <kernel IPI>
3,3% ( 9,0) plasma-desktop
2,6% ( 7,2) [kernel core] hrtimer_start (tick_sched_timer)
2,3% ( 6,5) chromium
1,4% ( 4,0) [kernel core] usb_hcd_poll_rh_status (rh_timer_func)
1,4% ( 3,8) X
1,3% ( 3,7) [TLB shootdowns] <kernel IPI>
1,2% ( 3,2) knotify4
0,9% ( 2,5) [acpi] <interrupt>
0,8% ( 2,2) mysqld
0,5% ( 1,5) [i915] <interrupt>
0,4% ( 1,2) [ahci] <interrupt>
0,4% ( 1,1) kwin
0,4% ( 1,0) knemo
0,3% ( 1,0) [kernel core] iwl_bg_monitor_recover (iwl_bg_monitor_recover)
0,2% ( 0,5) virtuoso-t
0,2% ( 0,5) hald-addon-stor
0,2% ( 0,5) [kernel core] __enqueue_rt_entity (sched_rt_period_timer)
0,1% ( 0,3) gpg-agent
0,1% ( 0,3) [Function call interrupts] <kernel IPI>
0,1% ( 0,2) kslowd000
0,1% ( 0,2) kded4
0,1% ( 0,2) init
0,1% ( 0,2) akonadiserver
0,1% ( 0,2) flush-8:16
0,1% ( 0,2) flush-8:0
0,1% ( 0,2) bdi-default
0,0% ( 0,1) konsole
0,0% ( 0,1) nepomukservices
0,0% ( 0,1) [kernel core] bdi_arm_supers_timer (sync_supers_timer_fn)
0,0% ( 0,1) akonadi_control
0,0% ( 0,1) kslowd001
0,0% ( 0,1) crond
0,0% ( 0,1) sensors
0,0% ( 0,0) [kernel core] cfq_completed_request (cfq_idle_slice_timer)
0,0% ( 0,0) hald
0,0% ( 0,0) [kernel core] neigh_timer_handler (neigh_timer_handler)
0,0% ( 0,0) [kernel core] neigh_add_timer (neigh_timer_handler)
0,0% ( 0,0) [kernel core] sk_reset_timer (tcp_delack_timer)
0,0% ( 0,0) rpcbind
An audio device is active 100,0% of the time:
hwC0D0 Realtek ALC889
Ein USB Gerät ist 100,0% der Zeit aktiv:
USB Gerät 1-2 : FingerPrinter Reader (Generic)
Suggestion: Enable Device Power Management by pressing the P key
Vorschlag: Aktivieren Sie USB-Autosuspend für Nicht-Eingabegeräte inden Sie die U-Taste betätigen
Vorschlag: Erhöhen Sie die "VM dirty writeback time" von 5,00 auf
15 Sekunden durch: echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
Dadurch belasten die VM Hintergrundaktivitäten die Festplatte weniger.
Deaktivieren Sie mit folgendem Befehl die "Wake-On-Lan" Funktion:
ethtool -s eth0 wol d
"Wake-On-Lan" hält die Physikalische Netzwerkverbindung aufrecht.
Vorschlag: Aktivieren Sie das SATA ALPM link power Management mit: echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
oder durch betätigen der S-Taste.
Vorschlag: Aktivieren Sie mit folgendem Befehl die WLAN Stromsparfunktionen:
iwconfig wlan0 power timeout 500ms
Dadurch verringert sich die WLAN-Geschwindigkeit etwas, spart aber Strom.
Vorschlag: Aktivieren Sie mit folgendem Befehl die HD-Audio Stromsparfunktionen:
echo 1 > /sys/module/snd_hda_intel/parameters/power_save
oder übergeben Sie dem Modul den Parameter power_save=1.
Suggestion: Enable the CONFIG_PCIEASPM kernel configuration option.
PCI Link Powermanagement (ASPM) allows the hardware to go to low power mode
automatically when a PCI-E device is idle.
aktuelle "USB suspend" Statistiken
Name des aktiven Gerätes
100,0% USB Gerät 3-1 : BCM2046 Bluetooth Device (Broadcom Corp)
100,0% USB Gerät 2-7 : HD Video WebCam (SuYin)
100,0% USB Gerät 2-6 : A309 (AVerMedia)
100,0% USB Gerät 1-2 : FingerPrinter Reader (Generic)
0,0% USB Gerät usb8 : UHCI Host Controller (Linux 2.6.35-ARCH uhci_hcd)
0,0% USB Gerät usb7 : UHCI Host Controller (Linux 2.6.35-ARCH uhci_hcd)
0,0% USB Gerät usb6 : UHCI Host Controller (Linux 2.6.35-ARCH uhci_hcd)
0,0% USB Gerät usb5 : UHCI Host Controller (Linux 2.6.35-ARCH uhci_hcd)
0,0% USB Gerät usb4 : UHCI Host Controller (Linux 2.6.35-ARCH uhci_hcd)
100,0% USB Gerät usb3 : UHCI Host Controller (Linux 2.6.35-ARCH uhci_hcd)
100,0% USB Gerät usb2 : EHCI Host Controller (Linux 2.6.35-ARCH ehci_hcd)
100,0% USB Gerät usb1 : EHCI Host Controller (Linux 2.6.35-ARCH ehci_hcd)
Runtime Device Power Management statistics
Name des aktiven Gerätes
Devices without runtime PM
09:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
06:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5784M Gigabit Ethernet PCIe
02:00.2 Mass storage controller: O2 Micro, Inc. Device 8130
02:00.1 SD Host controller: O2 Micro, Inc. Device 8120
02:00.0 FireWire (IEEE 1394): O2 Micro, Inc. Device 10f7
01:00.1 Audio device: ATI Technologies Inc RV710/730
01:00.0 VGA compatible controller: ATI Technologies Inc Device 9488
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge
16 more devices without runtime PM ommitted
Recent audio activity statistics
Name des aktiven Gerätes
100,0% hwC0D0 Realtek ALC889
Recent SATA AHCI link activity statistics
Active Partial Slumber Device name
Last edited by ewigkeit (2010-09-27 16:31:13)

Thanks TigTex,
but I can safely say, the temperature problem is real. It's not just a false sensor, because of the heat, the metal-case of the laptop is generating. It really gets uncomfortable when working on that hot case (hands on the hot machine and typing - after a while you can order your hands "well done" *sigh*). Because of that, I switched to an external keyboard, but that's not really a solution. The weird thing is, that the temperature problem didn't exist at the beginning - and it doesn't exist on Windows. And it's also not a cleaning problem - I clean my machine regularly (because I hate dust, generally ).
I can also say, that the fan is working - and it's working also dynamicaly (gets louder, when the machine gets hotter).
I checked the CPU sensors on Windows with Core Temp regularly (runs automatically in system tray at boot).
The machine ran 20 minutes (after 1h I get around 70° C / 73° C / 73° C):
$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +67.0°C (crit = +106.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +61.0°C (high = +105.0°C, crit = +105.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +59.0°C (high = +105.0°C, crit = +105.0°C)
@litemotiv
$ dmesg |grep iwlagn
iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
iwlagn: Copyright(c) 2003-2010 Intel Corporation
iwlagn 0000:09:00.0: enabling device (0000 -> 0002)
iwlagn 0000:09:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwlagn 0000:09:00.0: setting latency timer to 64
iwlagn 0000:09:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54
iwlagn 0000:09:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
iwlagn 0000:09:00.0: irq 47 for MSI/MSI-X
iwlagn 0000:09:00.0: loaded firmware version 8.24.2.12
Xorg.0.log (using x86-video-intel):
[ 18.630] (II) intel(0): Integrated Graphics Chipset: Intel(R) GM45
[ 18.630] (--) intel(0): Chipset: "GM45"
I will check for powersaving features, thanks for the hinch.

WOL possible for C5180 or other printer

I have a C5180 all-in-one and I was wondering if it was possible to turn the device on with a Wake-on-lan call? That way if my printer is in an other room I can turn it on from any pc.
Do other all-in-one devices have this possibility?

If the printer is off, then no. But if it's in sleep mode, then the WOL should work. And AFAIK, there's no printer that can be turned on in any other way than using the On/Off button.
Make it easier for other people to find solutions, by marking my answer with \'Accept as Solution\' if it solves your problem.
Click on the BLUE KUDOS button on the left to say "Thanks"
I am an ex-HP Employee.

XW6400 WOL problems

Similar Messages

Maybe you are looking for