CD Drive On Resume From Sleep

So i am new to macs as this is my first one. I am very pleased with my macbook, it runs at a normal temperature, and no discoloration so far. But i did notice that when I resume from sleep mode that my CD drive makes a weird sound. It kind of sounds like when you first put a cd into an old cd player and everything adjust? Is this normal? Its not really annoying. But it scares me that something might be broken.
Thanks,
David
Macbook   Mac OS X (10.4.7)  

Yes it's normal and yes it can be a little annoying. Basically what is happening is that when you come out of sleep your CD/DVD drive gets powered back up again which causes it to do it's usual checks which includes making the noises.

Similar Messages

  • Black screen on resume from sleep using open source AMD/ATI driver

    When waking from sleep using systemctl suspend or pm-suspend , I am presented with a black screen. I can still open programs, type, etc. but cannot see what I am doing. I usually just wind up rebooting from whatever terminal I had open, but again I can't see what I am typing. Upon reboot, the screen starts back up again. Everything else seems to resume from sleep just fine, it's just the screen that won't turn back on.
    I came from Ubuntu and had this same problem there. However, I only had this problem when using the open source xf86-video driver; when using the proprietary drivers, I was able to suspend/resume just fine. So it seems this problem is specific to the open source drivers.
    If I'm using an external monitor, my external monitor will resume just fine after waking from sleep, but the laptop screen will not.
    Googling around shows this is a common problem with AMD/ATI cards, and after a lot of attempts and failures I'm interested in knowing if anyone else has solved this problem.
    What I've tried so far (without success):
    -various quirks included with pm-utils to turn on dpms after resume
    -xrandr after resumption from sleep
    ==xrandr --output LVDS --off (If used without suspending (so while the screen still works) this seems to crash Gnome the first time around, but Gnome automatically restarts. If used a second time, it completely blanks the screen and requires a reboot)
    ==xrandr --output LVDS --mode 1600x900
    -xset dpms force on or xset dpms force off after resumption from sleep
    -vbetool dpms off and vbetool dpms on results in error message "Real mode call failed"
    -scripts using vbetool or xrandr when resuming from sleep
    -switching between virtual consoles and gnome using alt-ctrl-fn-f1 and alt-ctrl-fn-f2 keys
    My setup:
    -HP Envy dv7
    -UEFI dual-boot with Windows 8
    -AMD Radeon HD 7640G
    -xf86-video-ati 1:7.2.0-1 driver
    -Gnome DE using GDM login manager
    Thank you.
    EDIT: I did try using the proprietary drivers for a time, but found I couldn't adjust my brightness. At first I thought working suspension > adjustable brightness, but I quickly changed my mind after one night of trying to work on an unadjustable maximally bright screen.
    Last edited by broahmed (2013-11-23 02:18:57)

    Unfortunately I could not fix the problem so I wiped my system and loaded all new drivers before I found this posting.
    Is there a way to get the old ATI driver that works? The only one available on the ATI and Lenovo website is the latest one with the problem. I agree with you David, Lenovo should have fixed this problem already with ATI.
    John

  • 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 

  • I7 iMac with Bootcamp 3.1 and Windows7 64-bit won't resume from sleep

    When I try to resume from sleep, by clicking the magic mouse button, the screen comes up and I can move the mouse around but the bluetooth keyboard does not work and I can't launch any programs. Have to use the rear button to force a power off and restart.
    Is anyone able to resume from sleep okay and carry on using Windows 7? If so, any tips? Thanks in advance, very frustrating.

    I don't have an iMac, and it seems those have some design "issues" to say the least. I'd say yes, motherboard and/or firmware (UEFI or SMC, or both) could be buggy and at fault.
    Other than resetting SMC and running Apple Hardware Test, not sure what else or next to try.
    I've seen a number of BIOS updates out in the last months for my PC motherboards that have definitely improved sleep, S3, hibernation - EVGA, Gigabytes, and Intel - all X58 vs P55 (Lynnfield Core i5/7 LGA 1156) the iMac uses.
    http://anandtech.com/cpuchipsets/showdoc.aspx?i=3634
    http://en.wikipedia.org/wiki/IntelCorei5
    First I switched to Windows Vista/7, then I switched to build-my-own and custom parts. Love the looks of iMac, came close at one point, but I prefer the specs, options, and configure for my own needs in hard drives, graphics over cool factors.
    The iMac even in 2008 when it came with Penryn 64-bit processors never got 64-bit Vista/Boot Camp drivers, and that was why I didn't buy iMac back then, just lack of support I guess, and not seeing the market and need (for a good solid Windows desktop machine by Apple).

  • 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.

  • Minor lag from GUI when resume from sleep

    Hey people!
    I've been on archlinux for a couple of months now and I have fixed bugs here and there but something I have just noticed yesterday (it would happen before but I couldn't say when it would occur) is that after my system resume from sleep (it's not slow, it takes 1 or 2 secs) gnome GUI is a bit slow and it doesn't stop till I reboot my pc (it doesn't occur until my pc resumes from sleep).
    It's not that bad but quite annoying. I don't really know how to approach that kind of problem. I think it would be related to something like "gnome is not completly reloaded when resume from sleep and there are some infinite loop going on"...
    I hope someone has a clue in here!

    hey, sorry to revive an old thread, but this was the only other person I could find with this issue.
    I had originally reinstalled power manager and the the pm driver because it wouldn't save any custom power settings. When I finally got it working, it wouldnt wake up from sleep just like the above user's issue.
    Machine is relatively new win7x64 install with all updates (lenovo updates too) installed.
    Would like to avoid a total reinstall if at all possible.

  • T61p: Vista - BSOD when resume from sleep / hibernate, casued by classpnp.sys

    I've got a T61p (Type: 6457) with preinstalled Vista, later upgraded with SP1. Everything worked like a charm, untill a week or so, when the BSOD appeared when either resuming from sleep or hibernation.
    I've checked the minidump, and it seems as the classpnp.sys is causing the trouble, however, I've yet not found a good solution to fix the problem (I'm close to doing a restore to factory install, but would like to avoid if possible
    Anyone?
    edit: typos
    Message Edited by birwi on 04-12-2009 06:38 PM

    There's an issue with your GPU, video driver or both...try running this for a while:
    http://freestone-group.com/video-card-stability-te​st.htm
    If there's an underlying problem, this test will reveal it. And when I say "a while" I mean for an hour or more...
    Please be advised that if your GPU is on its way out (I've had them fail on T60p due to VRAM corruption) this test might just finish it and push it over the edge. Proceed at your own risk.
    Good luck.
    Cheers,
    George
    In daily use: R60F, R500F, T61, T410
    Collecting dust: T60
    Enjoying retirement: A31p, T42p,
    Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
    Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

  • T60 Type 2623 Blue Screen on Resume from Sleep Mode problem solved - XP Pro

    I hope that this post ends some frustrations for some people.
    I hope that IBM deals with this issue by getting ATI to fix the video driver issue.
    After three months of tracking down blue screens when resuming from Sleep Mode and some lockups while working, I have identified the problem on my T60 Type 2623 running Windows XP-Pro and all service packs and updates.  The Sleep Mode resume issues were intermittant and it would be fine for a day or two and then reboot on Resume or reboot every time I used Resume for a while.  For months the Blue Screen would reboot and attempt to send the message to Microsoft using the logs, but the logs were always corrupted.  I disabled every driver that I could and the problem continued for months.
    The problem solution came about when I decided to try my Rhapsody Music account after many months of not using it.  I kept getting a message about DRM (Digital Right Management) being disabled and Rhapsody software could not self-fix this.  So I finally called Rhapsody and they spent over an hour with me trying to get Rhapsody to work.  The support person asked me about my computer and I noted that it was an IBM T60.  He then asked about my Video Card and I responded that it was an ATI Mobility Radeon X1300.  After a few minutes on hold he asked about my driver version which was 8.442.3-080103a1-057754C the set from January 31, 2008.  He noted that there is a known problem wit the 8.4 driver and it interferes with DRM.  He had me go to control panel Settings and Hardware and then roll-back the driver to the prior version.
    After a reboot, the DRM issue was solved and I soon discovered that my resume from Sleep mode no longer crashed.  In fact it has been fine and crash free for over a month now.  I have noted that the older driver can sometimes resize my screen to something like 600 X 800 if I close the lid under certain circumstances, but that is just a function key reset to get my normal desktop resolution back.  At least it is not a blue screen reboot with a corrupted log file.
    Message Edited by retro74 on 07-05-2008 08:50 AM
    Solved!
    Go to Solution.

    Unfortunately I could not fix the problem so I wiped my system and loaded all new drivers before I found this posting.
    Is there a way to get the old ATI driver that works? The only one available on the ATI and Lenovo website is the latest one with the problem. I agree with you David, Lenovo should have fixed this problem already with ATI.
    John

  • Mac Os X Lion Crashes after resuming from Sleep

    Hi Everybody, i'm experiencing an issue on my 13'' MBP Early 2011 (i5 processor, 4GB RAM, 750GB HD SATA). My MBP often got stuc after i resume from my monitor sleep. I'll explain it in a better way: After i resume from sleep, there's at first a black screen in which the mouse can move, after that the mouse becmes the classic loading wheel and it freezes copletely, remaining in this situation. I thought it was a screensaver compatibility issue, but the problem stand still after i uninstalled screensaver and deactivate the screensaver options. I think it's a problem with Lion with the HD, but i have no evidence of it. Can Anyone help?
    Thank you in advance,
    Daniele.

    Whenever someone comes to me with crashing and freezing on waking up I look at 3 things and typically in this order:
    (1) Hard drive - usually if it is the hard drive SMART has already given a warning if the drive is actually failing or running Disk Utility reveals problems - often problems that cannot be fixed. Also, when the crashes are related to the hard drive there may actuallly be nothing wrong with the drive and a simple erase and reinstall will fix it.
    (2) Software issues - the old trick of creating a new account and logging into it to see if the problem is in your account or global helps. Looking in console to see if there's an error message logged just before the crash can be instructive - or not. Often the crash occurs before an error is logged. Sometimes reinstalling the OS is the solution - that's where having a FireWire hard drive is helpful. I can just boot with it and see if the computer still crashes on waking. If not I know to reinstall the OS.
    (3) RAM - marginal and faulty RAM can be the culprit in many cases. The frustrating thing about RAM is that RAM tests seldom give false positives, if the test says you have bad RAM, you do. Unfortunately when the test reveals nothing wrong the RAM might still be defective, just not enough for the test to catch.
    However, past history has led me to put RAM at the top of the list after an OS upgrade. Marginal RAM has been the culprit of many crash on wake problems with previous OS upgrades. I especially recall Leopard and Snow Leopard being affected - at the shop where I sometimes work we did a lot of RAM warranty replacements after those two upgrades. And here at the support forum we saw lots of people complaining of crash on wake problems coming back and saying, "Yep, got my RAM replaced and all is well." So if any of you are like me and upgraded your RAM, if you have the original RAM sitting around swap it in and see if the crashes stop.

  • 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.

  • Touchpad and trackpoint problems, especially when resuming from sleep

    I am having persistent problems with the touchpad and trackpoint on my L530.  I prefer to use the trackpoint usually, and found that the touchpad was super-sensitive and caused the cursor to jump around during normal (touch) typing so I disabled the touchpad.  Next time the thinkpad resumed from sleep mode, the mouse was frozen.  Nothing would reactivate it.  I had to switch user, which temporarily fixed it, and then reactivate the touchpad. 
    If I try and change trackpad settings at any time other than directly after a reboot, the settings are greyed-out and I can't touch them. Right now, both trackpad and trackpoint are completely dead again, but I've plugged in a USB mouse and that seems to be working, so I've given up fiddling with it.  This will be a pain when I'm moving around with the laptop though!
    The OS is Windows 7.  Yesterday I went looking for the most recent driver, uninstalled the existing one (as per guidance) and installed the new driver.  No luck.  
    I've heard this is a common problem and apparently installing a generic driver works, but I'm not completely sure what to use.  Anyone know? 
    Oh, and I'm not sure if this is related, but quite often when I resume from sleep mode the keyboard is also dead.  However, if I switch user it comes back to life.  So annoying but not the end of the world.

    Thanks for posting this information in this forum. You just saved me a couple thousand dollars!
    Based on my experience if you want to get this problem fixed as soon as possible you need to do the following:
    1. www.apple.com/feedback
    2. Post a video of the problem on www.youtube.com
    3. Send www.apple.com/feedback a link to the video on youtube.
    4. Encourage others to visit your youtube video and to post their own.
    Good luck!

  • 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

  • Access Violation in aapltp.sys when resuming from sleep.

    Hello,
    *I have diagnosed an issue in the aapltp.sys (touch pad) driver included with the MacOS 10.6.2 DVD. This issue causes a illegal access to be performed by this driver when the computer resumes from sleep (I have never reproduced it when resuming from hibernate or during normal operation). This issue occurs about once in every 10 resume operations, with both Windows 7 and Windows Vista. I have not experimented other versions of the OS.*
    *The version of this driver included with 10.5.x DVD does not have this issue - this is a new regression.*
    *In summary, KeyMagic (another apple driver) running on a system thread calls the OS for a dispatch (FxDevice::Dispatch). This ends up being routed to aapltp. While executing, aapltp dereferences a memory position offseted from a register that contains NULL. This causes an Access Violation which escalates into a BugCheck.*
    *AFAIK Apple does not distribute driver symbols so I was unable to dig into the cause for the fault in this driver. I am appending some additional crashdump information that might be useful. If you require additional information, let me know. I can either provide you with the full crashdump of perform further analysis if you make the symbols available.*
    * Bugcheck Analysis *
    SYSTEMTHREAD_EXCEPTION_NOTHANDLED (7e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff88004a7ea74, The address that the exception occurred at
    Arg3: fffff88005134718, Exception Record Address
    Arg4: fffff88005133f70, Context Record Address
    Debugging Details:
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    FAULTING_IP:
    aapltp+ca74
    fffff880`04a7ea74 807e5b01 cmp byte ptr [rsi+5Bh],1
    EXCEPTION_RECORD: fffff88005134718 -- (.exr 0xfffff88005134718)
    ExceptionAddress: fffff88004a7ea74 (aapltp+0x000000000000ca74)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 000000000000005b
    Attempt to read from address 000000000000005b
    CONTEXT: fffff88005133f70 -- (.cxr 0xfffff88005133f70)
    rax=0000000000000000 rbx=0000000000000004 rcx=fffffa80057899e0
    rdx=0000057ffa876618 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88004a7ea74 rsp=fffff88005134950 rbp=fffffa8005789d50
    r8=fffff88004a7b140 r9=0000000000000000 r10=fffffa80056809e0
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000057ffa99e188 r15=0000057ffa99e188
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    aapltp+0xca74:
    fffff880`04a7ea74 807e5b01 cmp byte ptr [rsi+5Bh],1 ds:002b:00000000`0000005b=??
    Resetting default scope
    PROCESS_NAME: System
    CURRENT_IRQL: 0
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_PARAMETER1: 0000000000000000
    EXCEPTION_PARAMETER2: 000000000000005b
    READ_ADDRESS: 000000000000005b
    FOLLOWUP_IP:
    aapltp+ca74
    fffff880`04a7ea74 807e5b01 cmp byte ptr [rsi+5Bh],1
    BUGCHECK_STR: 0x7E
    DEFAULTBUCKETID: NULLCLASS_PTRDEREFERENCE
    LASTCONTROLTRANSFER: from fffff88000e52f90 to fffff88004a7ea74
    STACK_TEXT:
    fffff880`05134950 fffff880`00e52f90 : fffffa80`05661e70 0000057f`fa9443a8 fffffa80`056809e0 fffffa80`056bbc50 : aapltp+0xca74
    fffff880`051349b0 fffff880`00e5299f : 00000000`00000000 fffffa80`05661e70 fffffa80`056bbc50 fffffa80`056bbc50 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x4b8
    fffff880`05134a30 fffff880`00e51f98 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`05661fc2 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
    fffff880`05134aa0 fffff880`00e57558 : fffffa80`04e2fb00 fffffa80`05661e70 fffffa80`04e2fb00 fffffa80`05661e70 : Wdf01000!FxIoQueue::QueueRequest+0x2bc
    fffff880`05134b10 fffff880`00e41245 : fffffa80`05661e70 fffffa80`04160c30 fffffa80`04e8ea58 00000000`000f2008 : Wdf01000!FxPkgIo::Dispatch+0x37c
    fffff880`05134b90 fffff880`04a672f6 : fffffa80`04160c30 fffffa80`056bcc90 00000000`00000000 00000000`000007ff : Wdf01000!FxDevice::Dispatch+0xa9
    fffff880`05134bc0 fffff880`04a6660b : fffffa80`056bcc90 fffffa80`04e8c010 fffffa80`08897640 fffffa80`04e8ec20 : KeyMagic+0x32f6
    fffff880`05134c30 fffff800`03334166 : fffffa80`04e00040 00000000`00000080 fffffa80`03cd1740 fffffa80`04e00040 : KeyMagic+0x260b
    fffff880`05134d40 fffff800`0306f486 : fffff800`03209e80 fffffa80`04e00040 fffffa80`03ce6680 fffff880`0122ca90 : nt!PspSystemThreadStartup+0x5a
    fffff880`05134d80 00000000`00000000 : fffff880`05135000 fffff880`0512f000 fffff880`05134770 00000000`00000000 : nt!KxStartSystemThread+0x16
    SYMBOL_NAME: aapltp+ca74
    MODULE_NAME: aapltp
    IMAGE_NAME: aapltp.sys
    DEBUGFLR_IMAGETIMESTAMP: 49c7fb1c

    Thanks for posting this information in this forum. You just saved me a couple thousand dollars!
    Based on my experience if you want to get this problem fixed as soon as possible you need to do the following:
    1. www.apple.com/feedback
    2. Post a video of the problem on www.youtube.com
    3. Send www.apple.com/feedback a link to the video on youtube.
    4. Encourage others to visit your youtube video and to post their own.
    Good luck!

  • 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.

Maybe you are looking for