Problems when waking from long sleep periods

Suddenly this morning my iMac developed a problem when recovering from a long period of sleep. I'm having trouble finding a solution.
I have my iMac set to ask for password when it recovers from sleep or screen saver. When I woke my iMac this morning the password dialog box appeared at the top of the screen as a garbled mess. If I put my iMac back to sleep and then wake it again it usually solves the problem.
I don't want to turn password verification off. Has anyone seen this problem before? Any suggestions on what might be cause?

funkyblue:
I usually leave my Pismo on and allow it to sleep. I find that waking from sleep and general functioning of the computer works a lot better if from time to time (I do it at least weekly) I shut down the computer, start up in Safe Mode, log in, empty Trash and reboot normally. The emptying Trash part clears the font caches.
You should consider doing other maintenance procedures, if you don't already. Gulliver's Mac OS X System Maintenance has good ideas with linked resources.
Please do not hesitate to post back with further questions or comments.
Good luck.
cornelius

Similar Messages

Problem when waking from sleep

Hi all, my mbp has real problems when waking from sleep - I hear the dvd drive do something, the screen comes on but remains black, and then nothing else - no keys work, only holding the power button has any effect.
I have a screensaver password on.
Anyone heard of this before or have any ideas?
Thanks!

It might also be worth trying the following:
Reset PRAM and NVRAM: http://support.apple.com/kb/HT1379
Reset SMC: http://support.apple.com/kb/HT1411

Problems when waking from sleep with display

Okay, so I have a Dual 1.8 G5 with an upgraded ATI Radeon 9800 Pro graphics card that I've had in it for over a year now. I just bought a new monitor, a Viewsonic 22" widescreen LCD to replace the 17" viewsonic CRD I had. Now, i get occasionally some random noise or something when the computer wakes from sleep that disappears most of the time if I turn the monitor off and back on.
Now does anyone have a thought as to if this is a problem with the monitor (i.e. should I take it back) or a problem with the card.
Thanks

Paul Pardue-
How is the monitor connected to the card? Have you verified that all of your connections are secure?
What does the noise look like?
Luck-
-DaddyPaycheck

MBP won't boot without power adapter also problem when waking from sleep

Hi guys,
I have a MBP 2.8 GHz Intel Core 2 Duo with 4GB 1067 HHz DDR3
I have had this issue for a while now and done a lot of research to solve the problem, but not got anywhere...
I can't boot the mac without the magsafe attached. Also, I'm not sure it is a related issue, but if I close the lid on the computer, it goes to sleep fine, but when I lift the lid to begin working again, the screen is like an opaque white and I get a blocked loading bar at the bottom that takes an age to clear and then when the screen wakes up it take a while to become life again. I also had an issue with the motion sensor. When I moved it, It would send itself to sleep. The battery icon also displays an X in it and has done for a while.
To try and solve this I have:
• Reset the PRAM
• Reset the SMC
• Booted from disc and repaired permissions and made sure the disc was OK
• Bought an new official Apple battery
• And pretty much everything else I can think of and have read about.
A while a go (Whilst in warranty) I had a problem with the USB board thingy (The board that runs keyboard, tracker pad and USB etc). Not sure if that helps.
I am starting to think it is hardware (RAM maybe??).
Can anyone help??
Thanks in advance.

As an update...
I have now tried:
Erasing the HD and installing SL from scratch and then used Time Machine to put back my files and apps.
Guess what... No joy.
Can anyone actually help with this? I take it I am on my own in this 'Support' forum?
If anyone has any further suggestions that I might be able to try that would be wonderful. My head is getting quite sore now from banging it against the brick wall.
Thanks in advance

Problems when waking from sleep

I tried this in the iMac discussion and did not get a response so i thought I'd try here also.
Newest iMac (May 2011), base model, OSX Lion
Whenever my computer goes to sleep and i go to wake it up, it never wakes up right. My touch pad stops working correctly. I have to hit the power button to get it to reconnect and then it works fine with the cursor, but it doesnt recognize taps or multitouch...only clicks.
Also, when i launch a new app from the doc it doesn't bounce up and down. The dock light doesn't come on either (i have both of these set up and when i restart the computer they work correctly).
Microsoft Office Reminders also doesn't go away from the dock when i dismiss the reminder, it just sits there.
The other thing i've noticed is that when i "minimize" a window (i.e. safari browser with an active website) rather than 'hiding' in its icon on the desk it goes into the right side of the dock next to the trash can.
If i restart the computer or shut it down and then start from scratch everything works fine again.
This is driving me NUTS. Can anyone help?
Thank you!
PS I am running 10.7.3, but this was happening even before 10.7.3.

Paul Pardue-
How is the monitor connected to the card? Have you verified that all of your connections are secure?
What does the noise look like?
Luck-
-DaddyPaycheck

Display issues (application placement and background) when waking from lcd sleep

I hve three DVI displays connected to my Mac Pro running Lion. I regularly put my displays to sleep using a hot corner to lock my workstation. This was not a problem in Leopard or Snow Leopard; however, in Lion I have noticed several issues upon waking the workstation from sleep.
-One of the LCDs will have a grey backgroud instead of the wall paper set for it.
The lcd with the grey background seems to be determined by which lcd I place the dock in.
The background will come back if I logout, reset, or move the dock to a different screen
-The applications will not be located on the screens they where on when I put the displays to sleep
Sometimes they are all on one display or distributed across two displays (this is most common)
Rarely the applications will not be on the correct displays and they will have been resized.
I'm liking OSX Lion so far, but having to repeatedly fix these problems is becoming a serious pain. I have updated to the latest patch for OSX 10.7, but that did not change anything reguards to these problems. Does anyone know how to solve these problems?

Matteo : I guess it is a good sign that only 2 of us have reported this minor glitch here . . . I may experiment with switching to a different desktop pattern and / or screen saver to see if it persists . . . also, since installing SL I have only done Sleep and of course restarts after getting the 10.6.1 update and a few others so I need to do an actual Shut Down and later start up fresh and see what happens.

MacBook Pro Retina 2013 will freeze if waked from long sleep if left with open lid

Hello!
Have a strange problem.
My new MacBook Pro Retina 13 will not wake from sleep state if left with open lid for a long period of time. (8-12 hours)
Ship happens ONLY in this case and only if left with open lid.
Screen lights up, I see a user window with password invitation - but no mouse pointer is present and keyboard doesn't respond and the apple on the backside of the lid is light up even if I close the lid.
TimeCapsule backups are creted during sleep state, no other malfunctions detected during use - laptop funtions normally from any side except this problem

Solved.
https://discussions.apple.com/message/25858115#25858115

MacBook Pro freezes when waking from deep sleep

When I plug in my Mac to charge overnight and go to unplug it in the morning, it will make the sound it does with the CD drive and then it acts like it's coming on. the first time I use it after I've unplugged it, the screen will come on like normal and show the login screen, when it does I can't move the mouse or type my password in for a minute or two. after about 20 seconds, the screen turns off...however I can turn it back on by clicking the power button but most of the time it still won't let me enter my password or move the mouse around. I'm not sure what the problem is. but it's only been doing this since I've updated to Yosemite.

Try turning off "Allow Bluetooth devices to wake this computer" under the advanced section of the Bluetooth System Preferences. Hope this helps.

IMac loses connection to network when waking from sleep

Hi There,
We are a small mixed environment of Macs and PCs running on a Windows 2008 domain. One of 2 iMacs that now run Mountain Lion 10.8.5 is having problems when waking from sleep. One of our designers will go for lunch and the machine will sleep for about 30 to 40 minutes. Upon her return the iMac will kick her off of the 3 shares she usually logs into (2 are on Win2008 machines, and 1 is a MacPro running 10.6.8 Server).
If she has files open in any of the Creative Suite Apps, the app will crash and she will have to restart the whole machine. If no files are open then she can usually reconnect to the shares after a short while. Obviously I told her not to leave any files open, but its causing her some headaches.
Its also creating srv errors (id 2012) on our domain controllers, when she tries to wake her machine.
This Imac is a late 2009, and we have a 2011 model that has no issues at all. Both are set exactly the same.
I have reset SMC, Pram, and rebinded to the domain, and searched through these forums quite a bit to no avail.
Any thoughts or suggestions would be much appreciated.

I am continuing to work on this issue, and have tried a number of things based on searching here and elsewhere.
And Lucky Me, I have been able to replicate this behavior on one of other Macs (imac 2011, on 10.8.5). I also see errors on 2 separate Windows file servers on the domain (Event ID: srv 2012).
Below I am posting what seems to be the relevant area of the log.
Nov 14 11:48:04 PrePressMac2 kernel[0]: Wake reason: EHC1
Nov 14 11:48:04 PrePressMac2 kernel[0]: Previous Sleep Cause: 5
Nov 14 11:48:04 PrePressMac2 kernel[0]: The USB device HubDevice (Port 1 of Hub at 0xfd000000) may have caused a wake by issuing a remote wakeup (2)
Nov 14 11:48:04 PrePressMac2 kernel[0]: 18323.795216: setDISASSOC from ATH_INTERFACE_CLASS disconnectVap
Nov 14 11:48:04 PrePressMac2 kernel[0]: 18323.795224: switchVap from 1 to 1
Nov 14 11:48:04 PrePressMac2 kernel[0]: The USB device Keyboard Hub (Port 3 of Hub at 0xfd100000) may have caused a wake by issuing a remote wakeup (3)
Nov 14 11:48:04 PrePressMac2 kernel[0]: The USB device Apple Keyboard (Port 2 of Hub at 0xfd130000) may have caused a wake by issuing a remote wakeup (3)
Nov 14 11:48:04 PrePressMac2 kernel[0]: HID tickle 117 ms
Nov 14 11:48:04 PrePressMac2 kernel[0]: TBT W (1): 0 [x]
Nov 14 11:48:04 PrePressMac2.local WindowServer[90]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
Nov 14 11:48:04 PrePressMac2.local WindowServer[90]: Created shield window 0x1e1 for display 0x003f003d
Nov 14 11:48:04 PrePressMac2.local WindowServer[90]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
Nov 14 11:48:04 PrePressMac2.local WindowServer[90]: Created shield window 0x1e2 for display 0x003f003e
Nov 14 11:48:04 PrePressMac2.local WindowServer[90]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
Nov 14 11:48:04 PrePressMac2.local WindowServer[90]: Created shield window 0x1e3 for display 0x003f003f
Nov 14 11:48:04 PrePressMac2.local WindowServer[90]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
Nov 14 11:48:04 PrePressMac2.local WindowServer[90]: Created shield window 0x1e4 for display 0x003f0040
Nov 14 11:48:04 PrePressMac2.local WindowServer[90]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
Nov 14 11:48:05 PrePressMac2 kernel[0]: AppleBCM5701::selectMedium - autoselect, any duplex, EEE allowed, flow control allowed
Nov 14 11:48:05 PrePressMac2 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link down on en0
Nov 14 11:48:06 PrePressMac2.local KernelEventAgent[47]: tid 00000000 received event(s) VQ_NOTRESP (1)
Nov 14 11:48:06 PrePressMac2.local KernelEventAgent[47]: tid 00000000 type 'smbfs', mounted on '/Volumes/PrePress', from '//aconti@GAIA/PrePress', not responding
Nov 14 11:48:06 PrePressMac2.local KernelEventAgent[47]: tid 00000000 found 1 filesystem(s) with problem(s)
Nov 14 11:48:10 PrePressMac2 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,0321,0de1,0300,c5e1,7800]
Nov 14 11:48:12 PrePressMac2.local configd[19]: network changed: v4(en0+:192.168.1.184) DNS+ Proxy+ SMB+
Nov 14 11:48:12 PrePressMac2.local SophosAntiVirus[67]: reloading scheduled scans...
Nov 14 11:48:12 prepressmac2.cutpasteandprint.net configd[19]: setting hostname to "prepressmac2.cutpasteandprint.net"
Nov 14 11:48:12 prepressmac2.cutpasteandprint.net digest-service[1048]: label: default
Nov 14 11:48:12 prepressmac2.cutpasteandprint.net digest-service[1048]:           dbname: od:/Local/Default
Nov 14 11:48:12 prepressmac2.cutpasteandprint.net digest-service[1048]:           mkey_file: /var/db/krb5kdc/m-key
Nov 14 11:48:12 prepressmac2.cutpasteandprint.net digest-service[1048]:           acl_file: /var/db/krb5kdc/kadmind.acl
Nov 14 11:48:12 prepressmac2.cutpasteandprint.net digest-service[1048]: digest-request: uid=0
Nov 14 11:48:12 prepressmac2.cutpasteandprint.net rpcsvchost[1049]: sandbox_init: com.apple.msrpc.netlogon.sb succeeded
Nov 14 11:48:12 prepressmac2.cutpasteandprint.net digest-service[1048]: digest-request: init request
Nov 14 11:48:12 prepressmac2.cutpasteandprint.net digest-service[1048]: digest-request: init return domain: CPP server: PREPRESSMAC2
Nov 14 11:48:12 prepressmac2 kernel[0]: Sandbox: sandboxd(1050) deny mach-lookup com.apple.coresymbolicationd
Nov 14 11:48:12 prepressmac2.cutpasteandprint.net sandboxd[1050] ([1049]): rpcsvchost(1049) deny file-read-data /private/var/root/Library/Preferences/ByHost/.GlobalPreferences.037506C4-0B10-5 70D-A7B6-B3B8F7AE0CC6.plist
Nov 14 11:48:12 prepressmac2.cutpasteandprint.net sandboxd[1050] ([1049]): rpcsvchost(1049) deny file-read-data /private/var/root/Library/Preferences/.GlobalPreferences.plist
Nov 14 11:48:13 prepressmac2.cutpasteandprint.net nsupdate[1055]: krb5_sendto_context is called on main thread, its a blocking api
Nov 14 11:48:13 prepressmac2.cutpasteandprint.net nsupdate[1055]: gss_init_sec_context is called on main thread, its a blocking api
Nov 14 11:48:13 prepressmac2.cutpasteandprint.net nsupdate[1056]: gss_init_sec_context is called on main thread, its a blocking api
Nov 14 11:48:14 prepressmac2.cutpasteandprint.net nsupdate[1057]: krb5_sendto_context is called on main thread, its a blocking api
Nov 14 11:48:14 prepressmac2.cutpasteandprint.net nsupdate[1057]: gss_init_sec_context is called on main thread, its a blocking api
Nov 14 11:48:14 prepressmac2.cutpasteandprint.net nsupdate[1058]: gss_init_sec_context is called on main thread, its a blocking api
Nov 14 11:48:15 prepressmac2.cutpasteandprint.net nsupdate[1060]: krb5_sendto_context is called on main thread, its a blocking api
Nov 14 11:48:15 prepressmac2.cutpasteandprint.net nsupdate[1060]: gss_init_sec_context is called on main thread, its a blocking api
Nov 14 11:48:16 prepressmac2.cutpasteandprint.net nsupdate[1061]: gss_init_sec_context is called on main thread, its a blocking api
Nov 14 11:48:17 prepressmac2 com.apple.launchd[1] (com.apple.smb.preferences): Throttling respawn: Will start in 5 seconds
Nov 14 11:48:17 --- last message repeated 2 times ---
Nov 14 11:48:17 prepressmac2.cutpasteandprint.net nsupdate[1063]: krb5_sendto_context is called on main thread, its a blocking api
Nov 14 11:48:17 prepressmac2.cutpasteandprint.net nsupdate[1063]: gss_init_sec_context is called on main thread, its a blocking api
Nov 14 11:48:18 prepressmac2.cutpasteandprint.net nsupdate[1067]: gss_init_sec_context is called on main thread, its a blocking api
Nov 14 11:48:18 prepressmac2.cutpasteandprint.net netbiosd[92]: name servers down?
Nov 14 11:48:19 prepressmac2.cutpasteandprint.net nsupdate[1068]: krb5_sendto_context is called on main thread, its a blocking api
Nov 14 11:48:19 prepressmac2.cutpasteandprint.net nsupdate[1068]: gss_init_sec_context is called on main thread, its a blocking api
Nov 14 11:48:19 prepressmac2.cutpasteandprint.net nsupdate[1069]: gss_init_sec_context is called on main thread, its a blocking api
Nov 14 11:48:22 prepressmac2.cutpasteandprint.net digest-service[1048]: digest-request: uid=0
Nov 14 11:48:22 prepressmac2.cutpasteandprint.net digest-service[1048]: digest-request: init request
Nov 14 11:48:22 prepressmac2.cutpasteandprint.net digest-service[1048]: digest-request: init return domain: CPP server: PREPRESSMAC2
Nov 14 11:48:22 prepressmac2.cutpasteandprint.net KernelEventAgent[47]: tid 00000000 received event(s) VQ_NOTRESP (1)
Nov 14 11:48:22 prepressmac2 kernel[0]: smb_iod_reconnect: Reconnected share PREPRESS with server GAIA
Nov 14 11:48:32 prepressmac2.cutpasteandprint.net ManagedClient[1077]: ODUGetMCXRecordWithCache(): record unique ID for 'PrePressMac2' not set
Nov 14 11:48:32 prepressmac2.cutpasteandprint.net ManagedClient[1077]: ODUGetMCXRecordWithCache() Accessing network user record from Active Directory not allowed because no authentication information was supplied.
Nov 14 11:56:25 prepressmac2 com.apple.launchd.peruser.1997381720[389] ([0x0-0x4a04a].com.adobe.InDesign[630]): Exited: Terminated: 15
Nov 14 11:56:34 prepressmac2.cutpasteandprint.net spindump[1100]: Saved hang report for Adobe InDesign CS5.5 version 7.5.3.333 (7530) to /Library/Logs/DiagnosticReports/Adobe InDesign CS5.5_2013-11-14-115634_PrePressMac2.hang
This is from the 2011 iMac, and I see something very similar to this on the 2009 machine.
I continue to think this is a software issue related to 10.8.5 and Adobe CS (CS5 on the 2009 machine and CS 5.5 on the 2011) as this appears to have come up only since the recent update.
Any help would be appreciated.

IBook no longer asking for a password when waking from sleep or screensaver

My iBook was fine until I installed the Security Update 2006-002 via software update. After the "required" reboot (reboot #1) everything functioned as normal.
On a subsequent reboot (#2) and several other reboots trying to correct the problem (#3-#5) I've found that my iBook no longer asks for a password when coming out of the screensaver, or when waking from sleep.
Yes, I have checked the security pref panel every time and have ensured the checkbox is checked. I even Sudo'd the panel just to be sure.
I downloaded the aforementioned security update and re-applied it. It corrected the problem during the same "required" reboot (#1), but after rebooting the computer a 2nd and 3rd time the problem has came up again.
I wish my iBook wasn't sick! Thanks, I tried searching as best as I could to see if this is a repost.
iBook G4 1.2 Mac OS X (10.4.5) All updates via Software Update
iBook G4 1.2 Mac OS X (10.4.5)

I don't have a specific fix but this generalized fix seems to take care of most problems for me. Download Cocktail, Onyx or MainMenu then run Rebuild Launch Services database, the maintenance (cron) scripts, clean all caches then Repair Permissions and restart.
To test it don't keep restarting, that's extra wear and tear on the computer, just put it to sleep and wake it or log out then back in.
If that doesn't work get Disk Warrior and rebuild the directory.
And if that doesn't work do an archive and install then one big upgrade.
But don't go past running one of those three utilities until you see if someone has a better fix for you. It might be as simple as trashing a preferences file.

Workaround for the problem of ultrabay HDD ejecting when waking from sleep

After trying every possible "solutions" with no luck for the problem of the second hard drive always ejecting/disconnecting when waking from sleep in my T530, I've decided to create my own workaround.
This is by no means a definitive solution but a nice workaround that uses little resources on the machine.
The idea is to simply let a program runs constantly from the second hard drive. That way, when the HDD tries to disconnect, Windows is not allowing it and then it stays allways connected.
To make it more thansparent I decided to create a Windows service that starts when Windows boot and stops when Windows shutdown.
This Windows service is very lightweight : it does absolutely nothing and just waits indefinitively.
The trick is that it just have to be started from the second hard drive.
Here is a link to the Windows service, 32-bit and 64-bit, with the source code and scripts to install/uninstall.
Just install it anywhere on the second hard drive (D: in my case).
https://docs.google.com/file/d/0BxusNBl7tTO-Y3J5VDB3d2lQRzg/edit?usp=sharing
Works perfectly for me on my T530 with Windows 7 Pro x64.

Hmm, I have no problem with Ultrabay ejecting HDD when waking from sleep mode. At first, I went down the same
route as you did. For the first few days when I received my T530 I kept an .iso file from Ultrabay HDD always mounted.
But then I disabled all power saving options within Windows and Lenovo Power Manager and it seems to work fine.
Works both with Windows 8 (64-bit) and Windows XP Professional (32-bit).
T530: i7-3630QM, 4 GB DDR3-1600, NVS 5400M, 2x 500GB 7200RPM, 9-cell, HD+ 1600x900, Backlit US, WinXP Pro
L430: i3-2370M, 4 GB DDR3-1600, HD 3000, 320GB 7200RPM, 6-cell, HD 1366 x 768, Win7 Home Premium 64-bit

IMac G5 Dies When Waking From Sleep

I have a Rev A iMac G5 I bought in 2004. Recently it started doing some weird stuff when waking from sleep. After looking at some of the other posts, I think this is going to be repetitive, but I thought I would see if anyone had any suggestions
After either putting the computer to sleep or letting it go to sleep, it will frequently die after the mouse has been clicked to wake it up. I have tried resetting both the SMU and PRAM as well as repairing disk permissions and repairing the disk. None of this has seemed to help. Occasionally, I get lucky and am able to wake it from sleep normally, but this doesn't happen often. After it dies following the mouse click, I can unplug it and then plug it back in and it will start up normally. Interestingly, it will start up from shutdown normally as well as restart normally. Additionally, as long as it doesn't go to sleep, I think you can typically use it as long as you want and it won't quit.
Today, I took the back cover off and messed around with it for awhile. The diagnostic LED behavior seems odd to me. LED #1 comes on when it is plugged into the outlet. When following Apple's instructions for troubleshooting a computer that won't start up, mine does fine because as I said it will start up normally if you unplug it and then plug it back in. Because of this, I set my computer to go to sleep quickly with inactivity. Although it did wake normally at least once, it died numerous times. The irregularity seems to occur with LED #2. One time it "died", I believe LED #2 actually remained lit and something seemed to still be working based on noise. However, the green light for the "caps lock" button wouldn't come on. Other times LED #2 would go out when it died after pushing the mouse with it asleep. During these times, I could push the internal power button and LED #2 would briefly light up, but nothing more than that would happen. On more than one occasion I would then push the SMU reset button and then push the internal power button again at which point LED #2 would fail to come on at all. After pushing the power button (and occasionally pushing the SMU button again) what seemed to be a random number of times, the computer would all the sudden start up normally again.
My top 3 guesses are a failed power supply, failed logic board, or exhausted PRAM battery (I have never changed it). The first two may be a bit to pricey for me to consider replacing. If they are the problem, I may just settle for setting the computer to never sleep. Does this sound like it could be caused by the PRAM battery going out?
Any advice would be greatly appreciated!
Message was edited by: Joshua213

My bad on not reporting back sooner. Indeed, replacing the PRAM battery did not fix the problem. The situation seems odd to me as I was able to sometimes wake the computer from sleep without it quitting while others times it dies. It does fine as long as it doesn't go to sleep. I can start it up and shut it down with no problems; additionally, it appears to do fine even when left on for long periods of time as long as it doesn't go to sleep. To be correct it doesn't seem to so much be the state of "sleeping", but the act of trying to wake it up from sleep. I don't think ventilation is a problem.
What I have done is just set it to not sleep. We just shut it down once in awhile. Rather than forking out the money, I think I will just use this work around as long as it continues to work.

Since updating to Lion the iMac won't recognise the external hard drive (maxtor) when waking from sleep mode,

Hi All, Since updating to Lion, my imac won't recognise the ext HDD (Maxtor) when waking from sleep mode, I have tried another port, diisc utility (Ext HDD not listed in here) but nothing works. I now find that I have to restart the imac to get the drive recognised..which is fine until the imac goes into sleep mode then I lose the drive and have to restart etc etc.....anyone suffering same issue. The Ext Drive worked perfectly until the upgrade..

Thanks for this, and apologies for delay in replying...in between seeing your post I backed up the ext hdd to another mac and used the disc utility to erase and repair and then re mounted the ext hdd. OK. I have then tested the ext hdd being recognised when waking from sleep mode a few times and everything appears to be fine. If this doesn't work (long term) I will follow the instructions as you have suggested....
I now have a new problem with my HP printer (Photosmart Plus) which is not being recognised by a new wireless router..Ok whilst the router is switch on and I have reconfigured the printer..but when the router is switched off overnight and then switched back on...I get a 'printer is not connected' message and have to go through the re configure routine all over. I am minded to think this is a router problem as the same issue is happening to my wifes Mac Book Pro (which is only a few weeks old)...any suggestions..

My MBP doesn't remember my Time Capsule wireless network when waking from sleep

My MBP (OS 10.5.8) doesn't remember my Time Capsule wireless network when waking from sleep. Thus, every time my MBP wakes from sleep, I need to select the Airport icon in the upper menu bar, select "Join other network", enter SSID and password. This is very cumbersome. And, I never had this problem when I was using the ISP's provided wireless router/gateway/DSL modem. Adding the Time Capsule and using it to generate the wireless network has introduced this problem.
It appears that this problem has to do with the hidden SSID. I don't need the lecture on how hidden SSID provides no serious security benefit. That's why I have the WPA2 encryption. I'm interested in a solution that will allow the Time Capsule to generate the wireless network, maintain a hidden SSID, continue to use WPA2 encryption, but have my MBP recognzie and autoconnect to this network.
Solutions I've alread tried:
1. Open Network Preferences
2. Select Airport from left hand column (and ensure Airport is at top of that list)
3. Select Advanced
4. Delete all Preferred Networks.
5. Apply settings.
6. Restart computer
7. Return to Network Preferences and from Advanced page, manually add my network with hidden SSID and WPA2 password
This solution works fine as long as I don't take my computer elsewhere and connect to another network. As soon as my preferred networks list gets another network, my MBP stops finding my TC network. Since I take my laptop to a lot of places (it's a laptop, after all...) this is a problem.
As I say, prior to adding the TC on my network (and using it to generate the wireless network), my MBP had no problem keeping 50+ preferred network names/passwords in the Preferred Network list, but always automatically finding/connecting to my home network without the need to "Join other network." Thus, I assume the problem lies with the Time Capsule.
Any ideas?

LaPastenague, thanks for weighing in. Didn't know that the hidden SSID capability was not IEEE standardized, and thus different devices will handle hidden SSID differently. With my admittedly limited knowledge of how SSID/hidden SSID works, I'm still a little confused as to why my MBP would remember the generic router/gateway's hidden network, but struggle with the TC's hidden network.
To my knowledge, when an SSID is broadcast by a base station (Airport, wireless gateway, etc.), a connecting device (like a laptop, iPad, etc.) detects this broadcast--this would be a passive reception of this SSID signal.
When an SSID is hidden, the base station does not broadcast its identification. Rather, a connecting device must transmit the name, and when the base station recognizes the broadcast, the connection is made. That's what you do when you select "Join another network" and manually enter the SSID.
The idea with OS X's Network Preferences is that these steps, whether for hidden networks or broadcast SSIDs, become automated.
Where is the potential for a different chipset between the TC and the previously used wireless router/gateway to alter this functionality? Shouldn't the selection of an SSID by the MBP to broadcast to seek for a base station be a function solely on the MBP? And once broadcast by the MBP, the TC should detect and reply?
Basically, the MBP can connect to the hidden TC manually just fine. The MBP can connect to the old setup automatically just fine. The MBP cannot connect to the TC automatically. Aren't these automatic connection functions solely on the MBP?
I'll try un-hiding the network and re-verifying that the problem is exclusively with the hidden network.
Z

Detect display when waking from sleep?

Is there any way to force the display detection when waking from sleep? I find that if the mini wakes before the monitor is on, i get a blank screen. When the monitor is on before waking, everything is normal.
I have the DVI-Detective, and the problem is actually worse when using it -- nothing is detected when waking up, no matter if the display is on or not.
My specs:
OS 10.5
C2D, 2Ghz - 2GB RAM
Sharp Aquos 52inch
All standard HD resolutions work fine - it's just now a matter if figuring out how to force the mini to detect the display...
Surely there must be a way to do this?

Great that you got it working. It seems what is happening when the TV is switched off is that the Mac can no longer see the EDID data. Basically, it's the same as if a hot-unplug event had occurred from OS X's perspective. The mini thinks the TV's video cable has been unplugged, so it thinks it is running headless, which of course it is not. And for some reason not completely clear to me, when the TV's power is restored, a hot-replug event is not triggered and the mini still thinks it's running headless. Maybe you are right that it is removed from the list of connected devices for good. But it isn't supposed to work like that.
The DVI Detective is the right tool for the job in cases like this, so it's good you have one and it's good you got it working. I agree it would be nice if there was more override control within OS X for times like this when things go wrong. But if more TV and 2nd/3rd tier monitor makers paid more attention to computer plug-and-play, then these things would work right in the first place. Your TV is in violation of the plug-and-play standard because the standard calls for the host (Mac mini in this case) to be able to power the ROM and I2C bus within the TV even if the TV is in a powered down state. Clearly your TV isn't doing this.

Problems when waking from long sleep periods

Similar Messages

Maybe you are looking for