Resume from sleep causes total Interent connectivity loss

This just started happening about a week ago. I used to be able to close the lid on my iBook, open it later and resume working online normally. Now when I open the lid or resume from sleep mode, the airport shows that it is connected, but I have no Internet access (server not found messages). I've tried turning the Airport off and on, but this doesn't seem to fix the issue. I have to totally restart the iBook to regain any Internet connectivity. Any ideas if this is due to a recent update? Anyone else having this problem? The most recent update I remember install was one for MS Office 2004, but it's not just affecting Entourage, no Interent apps will connect after sleeping.

Hi Kib,
I've had the same exact problem intermittently for the entire time i've owned my ibook (1 year). The problem was intermittent enough that I never took it too seriously. But, just this morning it would appear my internet connection is permanently gone. No amount of restarting or renewing the DHCP will work. And, as in your case, airport indicates that it is "connected". Seems like a degenerative condition. I'm going to call apple and get some help. I just got apple care and I'm going to take full advantage of it, especially after all the trouble i had with my ibook display.

Similar Messages

Dell Inspiron 7537 - Resume from sleep causes various dmesg errors

Hi,
I'm getting various acpi and intel video driver errors upon resume from sleep. The system does come up and I haven't found any functional problems that this is causing. I think the acpi errors may just be causing some devices to drain more power than is necessary. I have tried various live CD's from Ubuntu, Sabayon, and Fedora and they all have these same symptoms. Can anyone help with this, particularly anyone with the same laptop model who may have fixed these issues?
Thanks,
D
[ 1766.046497] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[ 1766.046649] acpi MSFT1111:00: Cannot transition to power state D3cold for parent in (unknown)
[ 1766.046650] acpi INT33C2:00: Cannot transition to non-D0 state from D3
[ 1766.046651] acpi SYNA2393:00: Cannot transition to power state D3cold for parent in (unknown)
[ 1766.046652] acpi ELAN1010:00: Cannot transition to power state D3cold for parent in (unknown)
[ 1766.046654] acpi INT33C3:00: Cannot transition to non-D0 state from D3
[ 1766.046655] acpi INT33C0:00: Cannot transition to non-D0 state from D3
[ 1766.046656] acpi INT33C1:00: Cannot transition to non-D0 state from D3
[ 1766.046657] acpi INT33C4:00: Cannot transition to non-D0 state from D3
[ 1766.046658] acpi INT33C5:00: Cannot transition to non-D0 state from D3
[ 1766.046671] acpi device:28: Cannot transition to power state D3cold for parent in (unknown)
[ 1766.046672] acpi INT33C6:00: Cannot transition to non-D0 state from D3

I also bought a Dell Inspiron 15 7537 and I had the same problem as OP, but on Fedora 21 64-bit with Gnome 3.14. I haven't tried any other distros or DEs. However, both Arch and Fedora run systemd, so I think my solution work the same on both systems. I fixed it by doing the following steps:
1. Create a script that reloads the kernel module hid_multitouch.
$ sudo mkdir /opt/touchscreen-fix
$ cd /opt/touchscreen-fix
$ echo '#!/bin/sh
/sbin/rmmod hid_multitouch && /sbin/modprobe hid_multitouch' | sudo tee resume.sh
$ sudo chmod +x resume.sh
Executing this script after a resume will make the touchscreen work again. However, it will of course not run automatically after a resume.
2. Schedule the script to run after resume.
Create the systemd service file:
$ echo '[Unit]
Description=Fix touchscreen after resume
After=suspend.target
[Service]
Type=simple
ExecStart=/opt/touchscreen-fix/resume.sh
[Install]
WantedBy=suspend.target' | sudo tee /etc/systemd/system/touchscreen-fix.service
Enable it:
$ sudo systemctl daemon-reload
$ sudo systemctl enable touchscreen-fix
Done! And that's all! I'm not sure if you also might need to restart the computer for it to work.
To accomplish this I used the following resources:
https://wiki.archlinux.org/index.php/Po … leep_hooks
http://unix.stackexchange.com/questions … -at-resume
https://bugs.launchpad.net/ubuntu/+sour … omments/28
Last edited by MaTachi (2014-12-16 13:35:21)

T61 - WWAN does not connect when resuming from sleep mode

Hi.
I have a T61 with integrated WWAN, which works perfectly - except I use sleep mode a lot, and when i resume from sleep mode, WWAN doesn't connect, I always get the same error - IP configuration failed. If I restart my OS, WWAN works normally again.
So far i have tried on Windows XP, Vista 32, Vista 64 and Windows 7 32 bit - always the same!
I connect via Access Connections, maybe there is a known issue?
Thank you, B

This bugs me as well. With the new Verizon software I just installed, it says "Adapter Disabled" when I resume from sleep.
I suspect a driver bug that needs to be adressed.
I use Vista Business 32bit, but had the same problem with XP.
Don Mannino

Ethernet not connecting when resuming from sleep/hibernate

I use my mac (Win7) in clamshell mode quite often, and I leave the cables connected (ethernet, power, display, etc). I have noticed since installing the 3.0 Boot Camp drivers that the ethernet connection is not recognized after resuming from sleep/hibernate. I need to disconnect the cable and re-plug it in for the system to recognize the network. Anyone else seeing this?

Look through Power Options for sleep and network. There should be sleep, low power, etc. And if possible, maybe you can manually update drivers from the vendor (not Apple). And if Windows or your update doesn't work as well, then you can just as easy use Device Manager and "rollback" the last driver upgrade - a great feature. Also, use those Create/Restore Check Points.
I use to have trouble, got tired of having this issue, and bought a new modem to replace my 5 yr old model. Problem gone. Same can happen regarding routers, sometimes a firmware update, but I had one router that had been superceeded by 4th generation and no firmware patch anymore.

Laptop Crashes when resuming from sleep

Hi
I am running a Macbook Pro with retina display. OS X 10.8.3 - Mountain Lion.
Model Name:          MacBook Pro
Model Identifier:          MacBookPro10,1
Processor Name:          Intel Core i7
Processor Speed:          2,3 GHz
Number of Processors:          1
Total Number of Cores:          4
L2 Cache (per Core):          256 KB
L3 Cache:          6 MB
Memory:          8 GB
Peripherals: Magic Mouse, Thunderbolt to gigabyte Ethernet connector
I use this machine while connecting to a network using an Ethernet cable at work. During the day, I leave the machine and it automatically goes to sleep and when I resume from sleep there does not seem to be any problems.
The problem is when I put the machine off to sleep before going home, and then when I resume the next day; the system crashes.
I have been searching high and dry for a solution. Some forums talk about the OS' bluetooth management having a bug, others talk about network unable to reconnect and even read something that talks about a wifi issue.
I cant pin point the root cause of the problem nor do I have a workaround. I have to shutdown every night.
It seems that this problem has been around for a while and it scares me that Apple has not released a fix for this issue.
What should I do to resolve this issue?

Here is the latest panic log as requested:
Mon May 20 09:22:22 2013
panic(cpu 4 caller 0xffffff80234b7e95): Kernel trap at 0xffffff7fa4bf7064, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000000000010, CR3: 0x000000003e75f00e, CR4: 0x00000000001606e0
RAX: 0x0000000000000001, RBX: 0xffffff80f4ea7000, RCX: 0xffffff8038dc1000, RDX: 0xffffff81138aba38
RSP: 0xffffff81138abb60, RBP: 0xffffff81138abb60, RSI: 0x0000000000000000, RDI: 0x0000000000000000
R8: 0x0000000000000000, R9: 0x00000000000003ff, R10: 0xffffffffffffffff, R11: 0x00000000ffffffff
R12: 0xffffff80f4ea7000, R13: 0x0000000000000000, R14: 0x0000000000000002, R15: 0x0000000000000000
RFL: 0x0000000000010246, RIP: 0xffffff7fa4bf7064, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000010, Error code: 0x0000000000000000, Fault CPU: 0x4
Backtrace (CPU 4), Frame : Return Address
0xffffff81138ab800 : 0xffffff802341d626
0xffffff81138ab870 : 0xffffff80234b7e95
0xffffff81138aba40 : 0xffffff80234cd4dd
0xffffff81138aba60 : 0xffffff7fa4bf7064
0xffffff81138abb60 : 0xffffff7fa4be0d64
0xffffff81138abbb0 : 0xffffff7fa4be0cba
0xffffff81138abbd0 : 0xffffff7fa4bbc7ae
0xffffff81138abc00 : 0xffffff7fa3acb3a0
0xffffff81138abc40 : 0xffffff7fa3acb30f
0xffffff81138abc60 : 0xffffff7fa3ad075c
0xffffff81138abcf0 : 0xffffff7fa3ac8e50
0xffffff81138abd20 : 0xffffff7fa3b19b8b
0xffffff81138abd70 : 0xffffff8023832e7b
0xffffff81138abdc0 : 0xffffff80238634f7
0xffffff81138abe30 : 0xffffff8023497fef
0xffffff81138abe80 : 0xffffff8023420aed
0xffffff81138abeb0 : 0xffffff8023410448
0xffffff81138abf00 : 0xffffff802341961b
0xffffff81138abf70 : 0xffffff80234a5dd6
0xffffff81138abfb0 : 0xffffff80234cdd43
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa3abf000->0xffffff7fa3af6fff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa3a81000
         com.apple.NVDAResman(8.1)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fa3b16 000->0xffffff7fa3e23fff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa3a81000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7fa3b02000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa3abf000
         com.apple.GeForce(8.1)[A15BB65E-3501-340F-87CB-2FD2BAD33E35]@0xffffff7fa4bb9000 ->0xffffff7fa4c85fff
            dependency: com.apple.NVDAResman(8.1.0)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fa3b 16000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7fa3b02000
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa3a81000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa3abf000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
12D78
Kernel version:
Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64
Kernel UUID: Kernel_UUID
Kernel slide:     0x0000000023200000
Kernel text base: 0xffffff8023400000
System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F)
System uptime in nanoseconds: 37416231729
last loaded kext at 11253530868: com.apple.filesystems.autofs          3.0 (addr 0xffffff7fa4e19000, size 45056)
loaded kexts:
com.apple.filesystems.autofs          3.0
com.apple.driver.AudioAUUC          1.60
com.apple.iokit.IOBluetoothSerialManager          4.1.3f3
com.apple.driver.AGPM          100.12.87
com.apple.driver.ApplePlatformEnabler          2.0.6d1
com.apple.driver.X86PlatformShim          1.0.0
com.apple.driver.AppleMikeyHIDDriver          122
com.apple.driver.AppleHDAHardwareConfigDriver          2.3.7fc4
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.driver.AppleHDA          2.3.7fc4
com.apple.driver.AppleUpstreamUserClient          3.5.10
com.apple.iokit.IOBluetoothUSBDFU          4.1.3f3
com.apple.driver.AppleMikeyDriver          2.3.7fc4
com.apple.driver.AppleBacklight          170.2.5
com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.1.3f3
com.apple.GeForce          8.1.0
com.apple.driver.AppleIntelHD4000Graphics          8.1.0
com.apple.driver.AppleMCCSControl          1.1.11
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.AppleSMCPDRC          1.0.0
com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
com.apple.driver.AppleSMCLMU          2.0.3d0
com.apple.driver.AppleLPC          1.6.0
com.apple.driver.AppleMuxControl          3.3.0
com.apple.driver.ApplePolicyControl          3.3.0
com.apple.driver.AppleIntelFramebufferCapri          8.1.0
com.apple.nvidia.NVDAStartup          8.1.0
com.apple.driver.AppleUSBTCButtons          237.1
com.apple.driver.AppleUSBTCKeyEventDriver          237.1
com.apple.driver.AppleUSBTCKeyboard          237.1
com.apple.driver.AppleFileSystemDriver          3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.BootCache          34
com.apple.driver.XsanFilter          404
com.apple.iokit.IOAHCIBlockStorage          2.3.1
com.apple.driver.AppleUSBHub          5.5.5
com.apple.driver.AppleSDXC          1.4.0
com.apple.iokit.AppleBCM5701Ethernet          3.6.0b1
com.apple.driver.AirPort.Brcm4331          614.20.16
com.apple.driver.AppleAHCIPort          2.5.1
com.apple.driver.AppleUSBEHCI          5.5.0
com.apple.driver.AppleUSBXHCI          5.5.5
com.apple.driver.AppleEFINVRAM          1.7
com.apple.driver.AppleSmartBatteryManager          161.0.0
com.apple.driver.AppleRTC          1.5
com.apple.driver.AppleACPIButtons          1.7
com.apple.driver.AppleHPET          1.8
com.apple.driver.AppleSMBIOS          1.9
com.apple.driver.AppleACPIEC          1.7
com.apple.driver.AppleAPIC          1.6
com.apple.driver.AppleIntelCPUPowerManagementClient          196.0.0
com.apple.nke.applicationfirewall          4.0.39
com.apple.security.quarantine          2
com.apple.driver.AppleIntelCPUPowerManagement          196.0.0
com.apple.kext.triggers          1.0
com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.5
com.apple.iokit.IOSerialFamily          10.0.6
com.apple.driver.DspFuncLib          2.3.7fc4
com.apple.iokit.IOAudioFamily          1.8.9fc11
com.apple.kext.OSvKernDSPLib          1.6
com.apple.iokit.IOSurface          86.0.4
com.apple.iokit.IOBluetoothFamily          4.1.3f3
com.apple.iokit.AppleBluetoothHCIControllerUSBTransport          4.1.3f3
com.apple.nvidia.gk100hal          8.1.0
com.apple.NVDAResman          8.1.0
com.apple.iokit.IOAcceleratorFamily          30.14
com.apple.driver.AppleSMBusController          1.0.11d0
com.apple.driver.IOPlatformPluginLegacy          1.0.0
com.apple.driver.X86PlatformPlugin          1.0.0
com.apple.driver.AppleSMC          3.1.4d2
com.apple.driver.AppleSMBusPCI          1.0.11d0
com.apple.driver.IOPlatformPluginFamily          5.3.0d51
com.apple.driver.AppleBacklightExpert          1.0.4
com.apple.driver.AppleGraphicsControl          3.3.0
com.apple.driver.AppleThunderboltEDMSink          1.1.8
com.apple.driver.AppleThunderboltEDMSource          1.1.8
com.apple.driver.AppleThunderboltDPOutAdapter          1.8.9
com.apple.driver.AppleHDAController          2.3.7fc4
com.apple.iokit.IOHDAFamily          2.3.7fc4
com.apple.iokit.IONDRVSupport          2.3.7
com.apple.iokit.IOGraphicsFamily          2.3.7
com.apple.driver.AppleThunderboltDPInAdapter          1.8.9
com.apple.driver.AppleThunderboltDPAdapterFamily          1.8.9
com.apple.driver.AppleThunderboltPCIDownAdapter          1.2.6
com.apple.driver.AppleUSBMultitouch          237.3
com.apple.iokit.IOUSBHIDDriver          5.2.5
com.apple.driver.AppleUSBMergeNub          5.5.5
com.apple.driver.AppleUSBComposite          5.2.5
com.apple.driver.AppleThunderboltNHI          1.6.3
com.apple.iokit.IOThunderboltFamily          2.2.6
com.apple.iokit.IOEthernetAVBController          1.0.2b1
com.apple.iokit.IOUSBUserClient          5.5.5
com.apple.iokit.IO80211Family          522.4
com.apple.iokit.IONetworkingFamily          3.0
com.apple.iokit.IOAHCIFamily          2.3.1
com.apple.iokit.IOUSBFamily          5.5.5
com.apple.driver.AppleEFIRuntime          1.7
com.apple.iokit.IOHIDFamily          1.8.1
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          220.2
com.apple.kext.AppleMatch          1.0.0d1
com.apple.security.TMSafetyNet          7
com.apple.driver.DiskImages          345
com.apple.iokit.IOStorageFamily          1.8
com.apple.driver.AppleKeyStore          28.21
com.apple.driver.AppleACPIPlatform          1.7
com.apple.iokit.IOPCIFamily          2.7.3
com.apple.iokit.IOACPIFamily          1.4
com.apple.kec.corecrypto          1.0

X220 very slow reconnecting to WiFi when resuming from sleep

So my X220 with the Intel 6205 card is having issues reconnecting to WiFi when resuming from sleep or hibernation. It takes about a minute for it to do so, though occasionally it will reconnect right away. Maybe 1 out of 20. When doing a cold boot or restart, it connects immediately upon the desktop showing up.
This was not always the case, in fact when I first got my X220 in June, I have not had this issue.... In fact, I don't know when it started happening, but it was maybe a couple months ago. I just thought it was my old router going bad. Well I got a new router, and it still happens. I have the latest Intel WiFi drivers from Lenovo, and I even tried downgrading to the previous driver from Intel's site. Still the same problem. I tried setting a default profile in access connections, and that does not help. In fact, it behaves the same way if I totally uninstall access connections as well. In fact I tried this on three different brand routers, and I can reproduce it on all of them (Asus, Netgear & TP-Link) so I think this is not a router issue. Other devices in the house reconnect right away with no issues (iPhone 4, PS3, Mac desktop, Dell laptop).
I currently have BIOS 1.24, but this was happening with 1.21 and 1.23 as well. My X220 originally came with 1.16, and I haven't updated it until 1.21. Unfortunately I don't remember that far back, if the problem started occuring then.
There was a brief discussion about this in another thread, but it went nowhere so perhaps this will get more attention. At least one other user reported the same issue.
Here's a clip of exactly what happens. When i press the button or open the lid from sleep, the windows wifi icon will start spinning for a few seconds, then turn into an X. then only about a minute later, does it quickly connect to the wifi and I have full signal. Manually clicking on the icon and selecting the access point does not speed up the process. It will only connect when it wants to, about a minute after resuming from sleep/hibernation.
http://youtu.be/dmboeA7HBgg
| X220 i7-2620M | 12.5" IPS | Intel 520 Series 180GB Main SSD | Mushkin 120GB mSATA SSD | 8GB RAM | Intel 6205 WiFi | BT | Win7 Pro 64 SP1 |
Solved!
Go to Solution.

Normally when a laptop running windows tries to connect to a network, it may also seek to identify certain components on the network, for example, asking the router "Who are you?". In your case, maybe the config are corrupted because the network address entries are messed up. Queries send out to the network come back with no replies, and the computer waited for the default time till timeout and it gives up.
Try this one at a time, reboot, or try all at once and reboot
TCP/IP stack repair options for use with Vista or 7.
Start, Programs\Accessories and right click on Command Prompt, select "Run as Administrator" to open a command prompt.
Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log
Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log
Reboot the machine.

Airport Card turned off when resuming from sleep - New since 10.6.6

I use safe sleep regularly, as I use my laptop at both work and home. Ever since the update to 10.6.6 though, I have had to manually turn my Airport connection back on after resuming from sleep.
Previously, although it was unreliable about connecting to a preferred network (an unrelated, but equally frustrating issue*) at least it would remain on. Now I've had to add the icon to my Menu bar just so I don't have to dig into System Preferences every single time I reawaken my laptop.
Does anyone know why this is happening, and if there is anything I can do to prevent it? I apologize if this has been asked before, but when I searched I was unable to find anything.
*This issue is unrelated and not the focus of my post, but if you happen to know about it I would absolutely appreciate your input.
When resuming from sleep, despite being between 5-20 feet from my preferred router I will often receive a dialog asking me to select from a list of SSIDs and enter a password even though that information is already saved. Then, once I complete this information Airport doesn't actually connect and the only way to resolve the issue is to turn Airport off and then back on. After this, it will automatically connect with no problems and remain connected until I put the computer into Sleep mode again.

Maybe check in your keychain and verify the password saved is correct for your wireless router?
Do you broadcast the network name?
Could you describe "unreliable about connecting to a preferred network"?
Is "use secure virtual memory" checked in the Security preference pane? If so try unchecking that maybe? If it's a hibernation issue sometimes that could cause weirdness.

Slow LAN Networking Speeds after Resuming from Sleep

I use my mac mini as a HTPC running Plex. I have it connected to my Windows media server with 802.11n. Works fine but sometimes after resuming from sleep the network speed drops off to an unacceptable level (from 72 Mb/sec to 5 Mb/sec). Disconnecting and reconnecting doesn't help. Switching to G doesn't help. Only restarting the mini restores the connection to full speed.
None of my Windows clients on the same network have any troubles.
Thoughts?

Looks like Plex might be causing the problem. I always have plex running and it appears as though if Plex makes a request for a file on the share before OS X is done re-mounting it after sleep, it kills the whole process.
Shouldn't the OS be robust enough to handle a situation like this?

Update to 10.6.8 - system hang (mouse issue) after resume from sleep

I am on older
MacBook Pro3.1
Intel Core 2 Duo
2.6GHz
Run on 10.6.8 almost flawelessly. Shortly after upgrade to 10.6.8 system started to hang periodically after resuming from sleep. Symptoms are that it stops responding to mouse (be it touch pad or USB mouse). Keyboard seems to be ok but system doesn't seem to be fully functional. I am able to ssh from the other computer and 'shutdown -r now' after reboot system seem to be ok until next resume from sleep. What interesting though is that this problem newer manifests then I am using external monitor.

Found problem. It was due to magic mouse that I left on. I carry this mouse in the laptop bag but rarely use it. Last time I used it (around the same time I install the update) I left it on in the bag. It was apparently disconnecting/connecting on its own and by some reason sometimes was breaking touch pad and other usb mouse connected to laptop, as soon as I switched magic mouse off broblem was fixed

X120E Touchpad inoperable after resuming from sleep

hello friends I'm a happy X120E user and a tech [pc's, mac's, lans, etc] - I do all sorts of tasks with my x120e and its been great. I recently "upgraded" my SSD so a fresh new install of Windows 7 was in order. After updating everything I have a problem I did not experience previously at all - not once in 3 years of use.
Upon resuming from sleep [and as far as I can remember this only occurs when resuming on battery], the touchpad/cursor is inoperable, frozen in the centered position, and I have found no way to 'wake' it. I finally have to shutdown/restart to get things functioning again. Keyboard works fine, but not touchpad or trackpoint [either/both].
maddeningly, its not consistent in this. sometimes it works, sometimes it does not.
I have seen the same issue with, and without, the supplied Lenovo Ultranav driver installed.
Question: in the X120E implementation, is the touchpad a PCI bus device or a USB device? I see no power plan options [i.e. "Advanced" >"Allow this device to wake the computer"] available via Device properties. There are no pointer/mouse/touchpad options whatsoever under Power Plan Settings.
Will Fn+F8 enable/disable the touchpad on this notebook? or,... should it?

No. Powering off and on again didn't work. My drive is a Seagate 750GB internal SATA drive in a Vantec NexStar-3 external enclosure. I don't think it is a driver issue. After the device removal error it won't mount on my PC or my Mac via FireWire or USB.
What I need to know is if there is some way to connect to the drive and make it mount with other software, using some kind of keystroke during startup, or maybe through terminal or something. I can't even try to repair the drive because it won't show up in disk utility.

Windows explorer + other windows applications crashing regularly at resume from sleep and hibernate

Good evening,
I have a Thinkpad W510 (4319-29G) running Windows 7 Pro 64bit. The system is loaded with the latest software and drives from Lenovo including BIOS 6NET74WW (1.34), upgrade was done Dec 7th (windows update performed Dec 15th).
The machine has
- 8Gb RAM
- nVidia Quadro FX880M, driver version is 8.17.12.5896, 7-9-2010 and video card BIOS is 70.16.5f.0.b
- dual harddrives,
- one Seagate Momentus XT 500Gb (ST95005620AS) FW rev SD23 in the main location with C: and some other partitions
- one Hitatchi 320 Gb (HTS723232L9SA60) FW rev FC4ZC50B in the bay.
- Intel Centrino Advanced-N 6200 AGN, driver version 13.3.0.24, 7-14-2010
- Intel 82577LM Gigabit Network Connection, driver version 11.5.10.1030, 7-22-2010
Recently I have experienced crashes of multiple windows components at resume from sleep and hibernate.
It seems to happen when swithing location (from work to home) and thus switching from docking station with wired network connection to no dock and wireless network connection (dont know if this has any bearing but anyway).
In the event viewer I typically have some 6-12 application errors logged. Sample output from event viewer is:
Log Name: Application
Source:Application Error
EventID:1000
Level:Error
Logged:2010-12-15 20:30:02
Task category100)
Keywords: Classic
Computer: xxxxxxx (my computername)
Then for each application the following detailed data is written in event viewer in the general tab:
#1
Faulting application name: rundll32.exe_nview64.dll, version: 6.1.7600.16385, time stamp: 0x4a5bc9e0
Faulting module name: nview64.dll, version: 6.14.10.13527, time stamp: 0x4c35752f
Exception code: 0xc0000005
Fault offset: 0x00000000000f0786
Faulting process id: 0x115c
Faulting application start time: 0x01cb9bd59882f1f6
Faulting application path: C:\Windows\system32\rundll32.exe
Faulting module path: C:\Program Files\NVIDIA Corporation\nView\nview64.dll
Report Id: b606b17d-0881-11e0-be39-00a0c6000000
#2
Faulting application name: taskhost.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: nview64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c35752f
Exception code: 0xc000041d
Fault offset: 0x00000001800bb350
Faulting process id: 0x10c0
Faulting application start time: 0x01cb9bd5694caebe
Faulting application path: C:\Windows\system32\taskhost.exe
Faulting module path: nview64.dll
Report Id: b6ae8cb2-0881-11e0-be39-00a0c6000000
#3
Faulting application name: sidebar.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc9e1
Faulting module name: nview64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c35752f
Exception code: 0xc000041d
Fault offset: 0x00000001800bb350
Faulting process id: 0x6f0
Faulting application start time: 0x01cb9bd5986a397a
Faulting application path: C:\Program Files\Windows Sidebar\sidebar.exe
Faulting module path: nview64.dll
Report Id: b6bd0bd9-0881-11e0-be39-00a0c6000000
#4
Faulting application name: Explorer.EXE, version: 6.1.7600.16450, time stamp: 0x4aebab8d
Faulting module name: nview64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c35752f
Exception code: 0xc000041d
Fault offset: 0x0000000008c3b350
Faulting process id: 0x1210
Faulting application start time: 0x01cb9bd569d9ae8e
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: nview64.dll
Report Id: b6d21ac7-0881-11e0-be39-00a0c6000000
#5
Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: nview64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c35752f
Exception code: 0xc000041d
Fault offset: 0x00000001800ba570
Faulting process id: 0x11c4
Faulting application start time: 0x01cb9bd569aa125c
Faulting application path: C:\Windows\system32\Dwm.exe
Faulting module path: nview64.dll
Report Id: b72bfbe8-0881-11e0-be39-00a0c6000000
#6
Faulting application name: rundll32.exe_PWMTR64V.DLL, version: 6.1.7600.16385, time stamp: 0x4a5bc9e0
Faulting module name: nview64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c35752f
Exception code: 0xc000041d
Fault offset: 0x00000001800bb350
Faulting process id: 0x1450
Faulting application start time: 0x01cb9bd59995023a
Faulting application path: C:\Windows\system32\rundll32.exe
Faulting module path: nview64.dll
Report Id: b7e4521b-0881-11e0-be39-00a0c6000000
It seems that a module "nview64.dll" is always the first application to crash. I suspect this has something with graphics to do.
I dont know if this event triggers the following crashes or if it is so that the display is initialized before the other programs.
After all crash diagnostic messages have been shown windows explorer restarts and also other applications restart but a lot of system tools in the system tray are gone so a cold start is needed to restore all tools again.
I really would appreciate any help and suggestions how to fix this really annoying issue.
Thanks, Anton

I had a similar issue, as soon as a described even a little bit of it to warrenty support they sent someone to swap the board
It seems thats the only fix, its been fine since

Airport no longer works after resuming from sleep

I got a new MacIntel a month or so ago, and it has always done this, under 10.4.4 and now 10.5.5
When resuming from sleep, airport shows full strength for second, then the signal disappears. NOTHING in settings, reconnecting etc will get it to work again. (this is 'deep' sleep, not just the display turning off)
If you restart (restart not shut down), then when it comes back, airport is just gone - even the menu bar indicator. The computer now thinks it has no airport installed at all. No matter how many times you restart, there is no longer any airport.
If you shut down, wait a minute and restart, it works as normal.
Since airport is the only way I connect to the network, and I don't want to waste electricity, this is unacceptable and clearly a flaw.
I called tech support and they had me move airport to the top of the list, delete plists and other stuff, none of which made any difference. I'm thinking this is a low level system software fault, and I hope I don't have to take it back for a motherboard replacement.

I also have this problem, although, not very often.
I'm still running 10.4.4. This never happened with
prior versions. Rebooting is the only way to
correct the problem. Simply turning off Airport and
turning it back on does not help.
Thats interesting actually because I Never had any trouble on my G5 iMac of otherwise identical specification, on on intel. Hmm. I was thinking this was an intel issue.
Wonder if its a hardware problem (though I suspect not).

T440S OSD Brightness control failure after resume from Sleep

Hi,
I have owned a T440S since late 2013.
Relevant Details:
T440S
Model : 20AQCTO1WW
OS : Windows 7 professional (original installation by Lenovo)
Latest Drivers installed as of June 2014 - including HotKey and Power Management
HotKey ver : 8.30
Power Managment : 6.65.1
Since receiving this laptop, OSD birightness control has always failed to work, i.e. does not appear on the screen
when using the Fn+F5/F6 key combination nor does it control actual screen brightness AFTER FIRST resuming from sleep
mode.
Sequence of steps that demonstrates the above symptom:
1. OSD brightness works fine after reboot
2. Putting the machine to sleep (I do not use hibernate) for a duration longer than a few minutes
3. Open lid the first time, hit Fn to resume machine
4. Pressing Fn+F5/F6 key combo does not display the brightness slider nor does it control brightness
5. Closing the lid and opening it again, causes OSD brightness slider to flash brifely and is now fully functional
using Fn+F5/F6 keys
Your tech department should easily be able to re-create this issue on any stock T440S/Win7pro machine, as
I have seen others comment about this very issue across other T440/OS variants.
This very same behavior has been there since the beginning.
When is Lenovo going to FINALLY FIX IT ONCE AND FOR ALL?
Thx,
--Alon
Solved!
Go to Solution.

Try this hotfix:
https://support.microsoft.com/kb/2752407
W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen

Resume from Sleep / Hibernate issues

Hi all,
First time poster. I have a Helix and am running into a heap of resume from sleep (and hibernate) issues.
The sleep issues tend to happen overnight - I do not have this issue if I sleep the machine and then wake it up 5-10 minutes later (e.g. moving between meetings at work). However, when I attempt to wake the machine up in the morning, it fails to resume from sleep, and instead boots from scratch.
Typically, when the unit is in this state, the status led on the lid is rapidly blinking (which I believe means that it's trying to enter sleep) Since there is nothing in the Windows event log during the overnight period, I'm wondering whether it's trying to enter a deeper sleep mode and failing.
This happens every second day or so. Which is really frustrating as a tend to lose some work.
I tried enabling hibernate as a trial, to see if that would avoid the issue, but resuming from hibernate fails as well. At least I get a Windows event log entry for this (source: kernel-power. The unit fails to resume from hibernate with status 0xC000000D)
I have the September 10 BIOS update, and am running Windows 8.1 Enterprise (though I had the issue with Windows 8 as well).
Any ideas on how I can troubleshoot this?
Regards
AC

Windows 8: In Windows 8, the default shutdown behavior puts the system into hybrid shutdown (S4) and all devices are put into D3. Remote wake from hybrid shutdown (S4) or classic shutdown (S5) is completely unsupported. In Windows 8, NICs are explicitly not armed for wake in both the classic shutdown (S5) and hybrid shutdown (S4) cases because users expect zero power consumption and battery drain in the shutdown state. This behavior removes the possibility of spurious wakes when explicit shutdown was requested. As a result, Wake-On-LAN is only ever supported from sleep (S3) or hibernate (S4) in Windows 8.
Note that in Windows 8, hybrid shutdown (S4) stops user sessions but the contents of kernel sessions are written to hard disk. This enables faster boot.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa373229(v=vs.85).aspx
From the Helix User Guide:
•Slow blinking: The tablet is in sleep mode.
•Fast blinking: The tablet is entering hibernation mode or sleep mode.
That was my reason for clarifying if hybrid-sleep was enabled; since it's the default setting and you noted that the LED was blinking fast. Does the LED ever stop blinking fast?
There can/may be multiple log entries during a normal sleep operation, because "the system uses the lowest-powered sleep state supported by all enabled wake-up devices." If one of those devices wakes the system (this does not mean power on) then the logs will report the devices and will likely return to a another level of sleep, but this does not mean full power loss or empty logs.
If the system has successfully entered sleep state, then you should see the following message in System Event logs.
Event 42, Kernel - Power
This system is entering sleep.
Sleep Reason: Button or lid
When the system is successfully woke you will see a System Event Log similar to this:
Event 1, Power - Troubleshooter
The system has returned from a low power state.
Sleep time: 2013-10-08T01:42:25.XXXXXXXX
Wake time: 2013-10-08T05:53:21.XXXXXXXX
However, there will be other events in the logs after sleep and prior to this wake period, such as hardware device issues(My helix has Bluetooth device warnings, nfc driver warnings and some other nondescript hardware errors), kernel messages (about boot manager, boot options, etc.).
Have you changed the behavior of the power button?
You also can program the power buttons so that by pressing the power button you can shutdown the tablet or put it into sleep or hibernation mode. To achieve this, you need to change your power plan settings. To access power plan settings, do the following:
From the desktop, tap the battery status icon in the Windows notification area.
Tap More power options.
In the navigation panel, tap Choose what the power buttons do
Follow the onscreen instructions to configure settings.
Lastly, when you updated to Windows 8.1, did you format the whole C:\ (mSATA) drive?
Helix: 3697 CTO.
Thinkpad user since IBM. I do not work for Lenovo or any entity working for Lenovo.

Resume From Sleep Login UI Problem

I'll keep this short and sharp.
Previously, when I would resume my mac from sleep, it would make the screen look similar to the normal login screen. With things spread out and nicly formatted. With the menu bar showing the essentials like network, time, and battery in the upper left.
Now, when I resume from sleep a small window appears telling me I need to enter my password to "unlock the screen".
What would cause this? Any applications that I might have installed without being aware?
I have restarted 2/3 times, and I will continue to do so for a short while more, in the hope that it can help me.
Oh. This is after resuming from sleep only. When I get to the normal login screen after turning it on, it's fine, and just as normal.
Thanks in advance!
~Before (yesterday)
~After (today) after multiple restarts

Hi buddy,
Its really hard to say something about this I can only say that I cant notice this problem on my Windows installation.
By the way: Do you use the Windows version from Toshiba or your own Windows installation?
Theoretically it could be a problem of your Windows installation or HDD itself Are you able to test another HDD or Windows installation that you can make sure its not a software problem?

Resume from sleep causes total Interent connectivity loss

Similar Messages

Maybe you are looking for