Airport drops when lid closes

Hey all,
I'd really appreciate your help on this, I can't figure out if it's a normal defect of the MBA or just my model....I just got my ACD and I couldn't figure out why the network was constantly dropping when my 4 year old powerbook found it just fine. Then I realized when the lid is closed, or almost closed, the network completely drops even though the computer runs just fine (with my display, external keyboard and mouse). I can't figure this out. Something in the hinge is turning off the airport card?
Thanks in advance.

Sorry about the sidetracking, was trying to correct the information that the other poster added (in two posts) that you can't use the MBA with it closed so others would not think that was true.
The closed lid may be interfering with the WiFi antenna or placing the antenna in a position where something is in the way that can block the signal. Other possibility is closing the lid is causing a problem with a short/loose connection due to a defect. To eliminate the first, move the arrangement of your monitor, etc. For the second you'd need to have it serviced.

Similar Messages

Wireless Connection drops when I close my Macbook

I recently hooked up Airport Express as my wireless router - supporting a Macbook, iPhone 4S, iPad, an HP printer and a Nintendo Wii. I thought everything was fine, and then I noticed that the connection seems to drop when I close the lid of my MacBook (was watching a movie streaming on the Wii through Amazon Instant Video, and noticed the video stopped every time I shut my MacBook). Any suggestions to alleviate this?
(have not tested yet to see if WiFi on the iPhone or iPad are affected by shutting down the MacBook)
(Environment is a one bedroom apartment, no walls between the Express and the Wii)

Did u solve ur problem, im having the same issue!! and its getting me mad LOL

Urgent: Shut down when lid closes problem

My Mabook pro / mid 2010 / Yosemite 10.10 shuts down when lid closes. This is new in the last few days, not after any system updates. It wont restart after lid opens again, unless repeatedly holding down power button for long periods. Strangely, the sleep light is on before I open the lid, but once lid is open, it's completely off.
Does anyone know the cause and/or fix for this? I'm really worried it's the beginning of the end, and I rely on this machine for work and need to travel in a few days! Thanks in advance for any trouble shooting tips.

Just to clarify; when I say "this is new" I mean the problem, not the laptop.

Firefox volume sharply drops when lid is closed.

I've got a Sager laptop running Windows 7 Home Premium. I'm was trying to listen to music, but every time I closed the lid The volume dropped around 75%. Before anyone asks in my power setting closing the lid does nothing. So I did some looking, in the volume mixer it shows the upper arrow (where the volume was) grayed out and a solid arrow down a decent way. When I close it again, as long as the you didn't click on Firefox's bar the volume stayed constant, but if you moved the solid arrow the grayed arrow vanishes and next time you close the lid it drops again. I've tested it with IE and Chrome, but the problem only happens with Firefox. I'm using firefox 11.0 with the following plug-ins: * NPRuntime Script Plug-in Library for Java(TM) Deploy
* Next Generation Java Plug-in 1.6.0_24 for Mozilla browsers
* Shockwave Flash 11.1 r102
* Pando Web Plugin
* Adobe PDF Plug-In For Firefox and Netscape 10.1.2
* The plug-in allows you to open and edit files using Microsoft Office applications
Thanks in advance.

Turns out the issue was a power settings issue. Turning off all settings for standby and disabling standby when closing the lid resolves this issue.

Shutting off when lid closes

I just bought a 13 inch MBP yesterday. I know macbooks are supposed to sleep when the lid is closed by default. But a few times when I opened the lid, the computer had appeared to turn completely off. The indicator light on the front was steady when the lid was closed, not blinking like I believe it is supposed to be when sleeping.
Any ideas?

1. Within 14 days of purchase of an Apple product, you can either return it or exchange it for a new one.
2. You have 90 days of free tech support from Apple from the date of purchase.
     AppleCare: 1-800-275-2273.
3. For
    A portable Mac doesn't appear to respond properly when you close or open the lid.
    Reset SMC. http://support.apple.com/kb/HT3964
    Choose the method for:
    "Resetting SMC on portables with a battery you should not remove on your own".

Laptop shuts down when lid closes

My 15" powerbook has been acting up the last few days ever since I downloaded the last group of updates. When I close the lid to put it to sleep the entire computer shuts down. When I open it and start it up it gives me the message that the computer was unexpected shut down. Any ideas?

Sorry, then I have to give up
Hopefully an other user can provide more assistance to you.
I would give Apple a phone call and ask for support, since it seems to be affiliated with the replacement battery (at least I would state so to get support).

Disconnects when lid closes

I was curious if there is a setting that when you close the lid to your laptop that it doesn't disconnect you from being on-line?? When i re-open the top my AIM and internet is logged off..
Mac Book Mac OS X (10.4.8)

When you close your screen, your computer is essentially sleeping. So the harddisks stop. Meaning no data transfer at all..
If you want, get lucky and buy a new macbook that doesnt sleep when you close the lid. haha. mine did that. but i got it fixed.

Restarts when lid closes

Sometimes when I close the lid in battery mode I here the TA DA! and I open the monitor and here the OS X is booting up like on a restart. It does not happen all the time. Any ideals what could be causing this? I leave my power settings in the Normal mode.

I have the same problem... But, more often than not, if I close the lid while it's still "thinking" about shutting down, I get frozen in some weird zombie limbo, in which the computer is half-shut-down, but, like, frozen in sleep mode... and i have a **** of a time getting it to respond and restart. when i finally DO restart, i get a message saying it wasn't shut down properly. (tho: it WAS shut down properly. it's just this bizarre restart it does when i shut the lid.) would LOVE advice!

[SOLVED]laptop suspend when LID close, even set HandleLidSwitch=ignore

i've modify
HandleLidSwitch=ignore
systemctl restart systemd-logind.service
But when close LID, it suspend.
Then i click some key on keybord , it come back.
/var/log/everything:
Mar 21 11:20:59 localhost logger: ACPI action undefined: PNP0C0A:00
Mar 21 11:21:06 localhost dbus-daemon[317]: dbus[317]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.229" (uid=1000 pid=22838 comm="systemctl stop laptop-mode.service ") interface="org.freedesktop.systemd1.Manager" member="StopUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
Mar 21 11:21:13 localhost systemd[1]: Stopped Laptop Mode Tools.
Mar 21 11:21:15 localhost logger: ACPI action undefined: PNP0C0A:00
Mar 21 11:21:37 localhost systemd[1]: Reloading.
Mar 21 11:21:37 localhost systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited with exit status 1.
Mar 21 11:21:37 localhost [358276.901952] systemd-fstab-generator[22955]: Failed to create mount unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
Mar 21 11:21:47 localhost logger: ACPI action undefined: PNP0C0A:00
Mar 21 11:22:02 localhost logger: ACPI action undefined: PNP0C0A:00
Mar 21 11:22:23 localhost logger: LID opened
Mar 21 11:22:31 localhost systemd[1]: Starting Sleep.
Mar 21 11:22:31 localhost systemd[1]: Reached target Sleep.
Mar 21 11:22:31 localhost systemd[1]: Starting Suspend...
Mar 21 11:22:31 localhost logger: LID closed
Mar 21 11:22:31 localhost systemd-sleep[23159]: Suspending system...
Mar 21 11:22:32 localhost kernel: [358330.844138] PM: Syncing filesystems ... done.
Mar 21 11:22:32 localhost kernel: [358331.305611] PM: Preparing system for mem sleep
Mar 21 11:22:47 localhost kernel: [358331.412348] Freezing user space processes ... (elapsed 0.02 seconds) done.
Mar 21 11:22:47 localhost kernel: [358331.439427] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Mar 21 11:22:47 localhost kernel: [358331.452995] PM: Entering mem sleep
Mar 21 11:22:47 localhost kernel: [358331.453150] Suspending console(s) (use no_console_suspend to debug)
Mar 21 11:22:47 localhost kernel: [358331.466400] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
Mar 21 11:22:47 localhost kernel: [358331.749415] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Mar 21 11:22:47 localhost kernel: [358331.749546] sd 0:0:0:0: [sda] Stopping disk
Mar 21 11:22:47 localhost kernel: [358332.106062] i915 0000:00:02.0: power state changed by ACPI to D3hot
Mar 21 11:22:47 localhost kernel: [358332.242667] PM: suspend of devices complete after 497.619 msecs
Mar 21 11:22:47 localhost kernel: [358332.243146] PM: late suspend of devices complete after 0.473 msecs
Mar 21 11:22:47 localhost kernel: [358332.243658] xhci_hcd 0000:03:00.0: wake-up capability enabled by ACPI
Mar 21 11:22:47 localhost kernel: [358332.269361] ehci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
Mar 21 11:22:47 localhost kernel: [358332.282850] ehci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI
Mar 21 11:22:47 localhost kernel: [358332.309313] PM: noirq suspend of devices complete after 66.169 msecs
Mar 21 11:22:47 localhost kernel: [358332.309974] ACPI: Preparing to enter system sleep state S3
Mar 21 11:22:47 localhost kernel: [358332.310597] PM: Saving platform NVS memory
Mar 21 11:22:47 localhost kernel: [358332.317339] Disabling non-boot CPUs ...
Mar 21 11:22:47 localhost kernel: [358332.320383] smpboot: CPU 1 is now offline
Mar 21 11:22:47 localhost kernel: [358332.323050] smpboot: CPU 2 is now offline
Mar 21 11:22:47 localhost kernel: [358332.325460] smpboot: CPU 3 is now offline
Mar 21 11:22:47 localhost kernel: [358332.327433] ACPI: Low-level resume complete
Mar 21 11:22:47 localhost kernel: [358332.327483] PM: Restoring platform NVS memory
Mar 21 11:22:47 localhost kernel: [358332.328066] Enabling non-boot CPUs ...
Mar 21 11:22:47 localhost kernel: [358332.331542] smpboot: Booting Node 0 Processor 1 APIC 0x1
Mar 21 11:22:47 localhost kernel: [358332.355520] CPU1 is up
Mar 21 11:22:47 localhost kernel: [358332.358971] smpboot: Booting Node 0 Processor 2 APIC 0x2
Mar 21 11:22:47 localhost kernel: [358332.587540] CPU2 is up
Mar 21 11:22:47 localhost kernel: [358332.590984] smpboot: Booting Node 0 Processor 3 APIC 0x3
Mar 21 11:22:47 localhost kernel: [358332.605172] CPU3 is up
Mar 21 11:22:47 localhost kernel: [358332.610534] ACPI: Waking up from system sleep state S3
Mar 21 11:22:47 localhost systemd[1]: Time has been changed
Mar 21 11:22:47 localhost systemd[1]: systemd-tmpfiles-clean.timer: time change, recalculating next elapse.
Mar 21 11:22:47 localhost acpid: client 328[0:0] has disconnected
Mar 21 11:22:47 localhost systemd-sleep[23159]: System resumed.
Mar 21 11:22:47 localhost kernel: [358332.611098] i915 0000:00:02.0: power state changed by ACPI to D0
Mar 21 11:22:47 localhost kernel: [358332.661492] ehci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI
Mar 21 11:22:47 localhost kernel: [358332.688143] ehci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
Mar 21 11:22:47 localhost kernel: [358332.715055] sdhci-pci 0000:01:00.0: MMC controller base frequency changed to 50Mhz.
Mar 21 11:22:47 localhost kernel: [358332.741549] xhci_hcd 0000:03:00.0: wake-up capability disabled by ACPI
Mar 21 11:22:47 localhost kernel: [358332.741712] PM: noirq resume of devices complete after 130.745 msecs
Mar 21 11:22:47 localhost kernel: [358332.743008] PM: early resume of devices complete after 0.206 msecs
Mar 21 11:22:47 localhost kernel: [358332.743043] i915 0000:00:02.0: setting latency timer to 64
Mar 21 11:22:47 localhost kernel: [358332.743146] mei 0000:00:16.0: irq 46 for MSI/MSI-X
Mar 21 11:22:47 localhost kernel: [358332.743195] ehci_hcd 0000:00:1a.0: setting latency timer to 64
Mar 21 11:22:47 localhost kernel: [358332.743215] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
Mar 21 11:22:47 localhost kernel: [358332.743301] snd_hda_intel 0000:00:1b.0: irq 49 for MSI/MSI-X
Mar 21 11:22:47 localhost kernel: [358332.743481] ehci_hcd 0000:00:1d.0: setting latency timer to 64
Mar 21 11:22:47 localhost kernel: [358332.743508] ahci 0000:00:1f.2: setting latency timer to 64
Mar 21 11:22:47 localhost kernel: [358332.743611] iwlwifi 0000:02:00.0: RF_KILL bit toggled to enable radio.
Mar 21 11:22:47 localhost kernel: [358332.744213] mei 0000:00:16.0: wd: failed to find the client
Mar 21 11:22:47 localhost kernel: [358332.811881] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
Mar 21 11:22:47 localhost kernel: [358332.981624] usb 4-1.2: reset high-speed USB device number 3 using ehci_hcd
Mar 21 11:22:47 localhost kernel: [358333.061455] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 21 11:22:47 localhost kernel: [358333.061936] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359)
Mar 21 11:22:47 localhost kernel: [358333.061944] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._SDD] (Node ffff880149a55cf8), AE_NOT_FOUND (20120913/psparse-536)
Mar 21 11:22:47 localhost kernel: [358333.062035] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359)
Mar 21 11:22:47 localhost kernel: [358333.062041] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._GTF] (Node ffff880149a55d20), AE_NOT_FOUND (20120913/psparse-536)
Mar 21 11:22:47 localhost kernel: [358333.062591] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359)
Mar 21 11:22:47 localhost kernel: [358333.062599] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._SDD] (Node ffff880149a55cf8), AE_NOT_FOUND (20120913/psparse-536)
Mar 21 11:22:47 localhost kernel: [358333.062690] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359)
Mar 21 11:22:47 localhost kernel: [358333.062696] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._GTF] (Node ffff880149a55d20), AE_NOT_FOUND (20120913/psparse-536)
Mar 21 11:22:47 localhost kernel: [358333.062739] ata1.00: configured for UDMA/100
Mar 21 11:22:47 localhost kernel: [358333.074899] sd 0:0:0:0: [sda] Starting disk
Mar 21 11:22:47 localhost kernel: [358333.246448] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
Mar 21 11:22:47 localhost kernel: [358333.253820] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x3
Mar 21 11:22:47 localhost kernel: [358333.391539] restoring control 00000000-0000-0000-0000-000000000101/0/2
Mar 21 11:22:47 localhost kernel: [358333.391541] restoring control 00000000-0000-0000-0000-000000000101/1/3
Mar 21 11:22:47 localhost kernel: [358333.391543] restoring control 00000000-0000-0000-0000-000000000101/2/6
Mar 21 11:22:47 localhost kernel: [358333.391544] restoring control 00000000-0000-0000-0000-000000000101/3/7
Mar 21 11:22:47 localhost kernel: [358333.391545] restoring control 00000000-0000-0000-0000-000000000101/5/9
Mar 21 11:22:47 localhost kernel: [358333.693001] PM: resume of devices complete after 950.103 msecs
Mar 21 11:22:47 localhost kernel: [358333.694210] PM: Finishing wakeup.
Mar 21 11:22:47 localhost kernel: [358333.694214] Restarting tasks ... done.
Mar 21 11:22:47 localhost kernel: [358333.706265] video LNXVIDEO:01: Restoring backlight state
Mar 21 11:22:47 localhost logger: ACPI action undefined: PNP0C0A:00
Mar 21 11:22:47 localhost acpid: client connected from 328[0:0]
Mar 21 11:22:47 localhost acpid: 1 client rule loaded
Mar 21 11:22:47 localhost systemd[1]: Started Suspend.
Mar 21 11:22:47 localhost systemd[1]: Service sleep.target is not needed anymore. Stopping.
Mar 21 11:22:47 localhost systemd[1]: Stopping Sleep.
Mar 21 11:22:47 localhost systemd[1]: Stopped target Sleep.
Mar 21 11:22:47 localhost systemd[1]: Starting Suspend.
Mar 21 11:22:47 localhost systemd[1]: Reached target Suspend.
Mar 21 11:22:50 localhost logger: ACPI action undefined: PNP0C0A:00
Last edited by whille (2013-03-21 05:26:24)

You are still using acpid. That is triggering the suspend, not logind.
Edit: Also use [ code ] [ /code ] tags (without the spaces) for things like your logs. Hit the "quote" button if you are more of a visual learner.
This is how you use code tags.
Last edited by WonderWoofy (2013-03-21 03:38:53)

Airport dropping when i connect Airdisk

I have been using Airport extreme for some time now with a Lacie 1TB drive attached. It had been working fine until the other day.
First my hardrive was flashing. found out the drive was corrupted. So i reformatted using a local connection to my iMac. and when i tried to reattach that is when problems started. My AEBS started rebooting. Went from flashing amber to solid green for about 2 seconds and then rebooted. It is stucked in that mode unless i either turn off airdisk drive or pull USB cord.
any help will be appreciated.

Thanks for the reference article. I will go over it as I have been looking for soemthing like that a while ago without success (even the Apple Support Centre could not give me such a good reference document).
When I located my 2 relays, I used a software that was picking (and measuring the quality of) the different signals as I was moving from one room to another. Basically, the quality of the signal of the 2 remotes was equivalent to the one of the main base station. I thought that was pretty good. Maybe I should redo that with Netspot to check again this a still the case.
As I mentioned, everything worked fine until I incorporated other devices (ATV and Airplay). (Actually, I now remember I had a problem sometimes even without ATV or Airplay connecting my iPhone. I thought then it was a problem with the iPhone and was just restarting my modem to solve it)
I will go over the article you kindly sent me and see if I have missed something.
Thanks again!
Francois

Suspends only every second time when lid closed

Hello everybody, my problem is as the subject: to suspend I have to close usually the laptop lid twice.
I'm using kde, but I have also used years ago fluxbox, tweaking scripts and using laptop-mode (which is not running now). Thanks in advance for every idea where to look.
/etc/acpi$ cat handler.sh
#!/bin/sh
# Default acpi script that takes an entry for all actions
minspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq`
maxspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`
setspeed="/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed"
set $*
case "$1" in
button/power)
case "$2" in
PBTN|PWRF)
logger "PowerButton pressed: $2"
poweroff
logger "ACPI action undefined: $2"
esac
button/sleep)
case "$2" in
SLPB|SBTN)
echo -n mem >/sys/power/state
logger "ACPI action undefined: $2"
esac
ac_adapter)
case "$2" in
AC|ACAD|ADP0)
case "$4" in
00000000)
echo -n $minspeed >$setspeed
#/etc/laptop-mode/laptop-mode start
00000001)
echo -n $maxspeed >$setspeed
#/etc/laptop-mode/laptop-mode stop
esac
logger "ACPI action undefined: $2"
esac
battery)
case "$2" in
BAT0)
case "$4" in
00000000)
logger 'Battery online'
00000001)
logger 'Battery offline'
esac
CPU0)
*) logger "ACPI action undefined: $2" ;;
esac
button/lid)
case "$3" in
close)
logger 'LID closed'
open)
logger 'LID opened'
logger "ACPI action undefined: $3"
esac
logger "ACPI group/action undefined: $1 / $2"
esac
# vim:set ts=4 sw=4 ft=sh et:

I actually do not understand who comands at the end - this handler.sh or the settings in Kde-powermanaging, I guess it's the second, I did remove the actions for suspend on lid close time ago. I made a test now, when I change handler.sh and check "do nothing when lid close" in kde powersettings happens exact the same: performs suspend every second time only.
button/lid)
case "$3" in
close)
logger 'LID closed'
/usr/sbin/pm-suspend
open)
logger 'LID opened'
logger "ACPI action undefined: $3"
esac
Last edited by steff (2012-07-21 17:08:46)

Won't sleep when I close the lid - HELP!

A while ago, my iBook G4 1GHz was knocked off of a table. The display was smashed and the whole display assembly was destroyed. I bought a new (used) display assembly and installed it. Worked fine, but when I closed the lid, the iBook woudn't sleep. I checked the placement of the magnet in the top case and I reset the PMU. Still no sleep. So I contacted the company that sold me the display and got a different one. Still won't sleep when I close the lid. I checked all of the energy settings, reset the PMU and even tried to force sleep with a magnet from another broken iBook. Still no sleep when I close the lid. It will sleep when I choose sleep from the Apple menu (OS Tiger) and when it sits for a while with the lid open, but not when I close the lid. Any thoughts?

My original problem has not been solved. The iBook still won't go to sleep when I close the lid. I have checked out any possible software causes, and have ruled them out. I have checked to make sure no keys were being pressed when I closed the lid. I took a magnet from another iBook top case and ran it down the side of the display to try to force sleep. No effect. I don't have any Firewire or USB devices attached, to that's not it. Apple, this board, PBFixit.com, and my local Apple-affiliated repair center have no idea why I am having this problem. Two display assemblies have experienced this problem. The original display had been destroyed in a drop. Could some internal damage, like maybe to the logic board, result in such a problem? It's odd that I am the only person out there who has had this problem. Weird, to be sure.

MacBook restarts to blue background when the lid closes-only sometimes????

My Mac has done this periodically since six months after I've bought it. When I close the lid, I hear the restart tone and when I open it back up it's going through a restart process. Most of the time, it starts back up with a blue background (not the normal picture I have as my background) and I'm unable to drag and drop items from an open program to a folder or the desktop (unable to drag a picture from iphoto to the desktop). To remedy the situation, all I have to do is restart the computer normally and it returns to a normal desktop.
I called Apple and they first ad me do an archive and install, which I did with no results (the problem still occurred at least once a day) and then an erase and install which reduced the frequency of the problem but did not eliminate it. I also sent the computer in to the Apple Depot where the replaced the top case, the power management unit, and the heat sync but did nothing software wise. When I got the computer back, I again did an erase and install and the problem is still occurring a couple times a week.
Anyone have any idea on what's going on? Should I keep harassing Apple Care? Will it do any good? I'm about to buy 10.5, but will this fix it? Help!

Bump

My MBP shuts down or sleeps (?) when I close the lid

Hi
Forgive me if this is a stupid question, but I haven't been able to solve it on my own by investigating, asking others og reading this forum.
My MBP from late 2007 has recently started to shut down/sleep (or maybe even "hibernate" - not sure which is the right term) when I close the lid - meaning that when I open it, it *doesn't wake up automatically* like it used to. *I need to push the "on" button and it takes it a while to start up*. It doesn't start up from scratch; it shows the last screen shaded in a light grey tone - and it's takes quite a few seconds to get ready. As far as I recall, it "woke up" automatically before.
I haven't changed my preferences - and they are all set to "never", as my MBP is nerly always connected to the adaptor.
Any clues to what happened and how I can change it? It's really annoying!
Thanks,
Carina

Welcome!
When my MBP started that same behavior, I found that I had accumulated a huge list of wireless networks on my travels. Reviewing the system log, I found my computer was trying to connect to one, a hotel network to which I had connected weeks before and miles away.
Here's how I fixed it (I have 10.5.8, not 10.6, but the fix should be the same):
1) Open System Preferences and select "Network."
2) Be sure "Airport" is selected in the left side of that preference pane.
3) Click the "Advanced" button. If the next screen does not have the "Airport" tab selected, select it. There should be a window with a list of networks.
4) Use the + and - buttons below to remove any networks you have accumulated that are not needed. Example: on mine, I removed all but two networks--our home network and the one at a local museum where I volunteer.
5) Once you'd cleaned off the list to the bare necessities, uncheck the option labeled, "Remember any network this computer has joined." This will not prevent you from using other networks on later travels but will prevent them building up and creating problems.
That completely cured my wake-from-sleep problems. and other have said it worked for them, too.

My Macbook Air wouldn't go to sleep when I close the lid. I have tried to reset the SMC, but it didn't solve the problem.

Normaly it goes to sleep, when I close the Lid, but suddently this function stopped. That means that Mac'en still is running and become warm, during transport.
(Macbook Air 13 ", medio 2011, 1,7 core i5, 4 MB ram, 256 GB, iMac 22", Timecapsule 1 TB, Airport Express, 2 Iphone 4, 1 iPhone 3s, iPad2)

Test after each of the following steps that you haven’t already tried:
Step 1
 ▹ System Preferences ▹ Print & Scan ▹ Open Print Queue...
Check all printers for unfinished jobs. Deal with any you find.
Step 2
 ▹ System Preferences ▹ Energy Saver ▹ Power Adapter ▹ Wake for network access: uncheck. You may need to unlock the preference pane by clicking the lock icon in the lower left corner and entering your administrator password.
Step 3
 ▹ System Preferences ▹ Energy Saver ▹ Schedule… ▹ Start up or wake: uncheck
Step 4
Disconnect all wired peripherals except keyboard, mouse or trackball, and monitor, if applicable.
Step 5
Launch the Activity Monitor application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ If you’re running Mac OS X 10.7 or later, open LaunchPad. Click Utilities, then Activity Monitor in the page that opens.
Select All Processes from the menu in the toolbar of the Activity Monitor window, if not already selected. Enter “powerd” (without the quotes) in the "Filter" text field. Select the powerd process and click the Quit Process button in the toobar (stop-sign icon.) In the sheet that opens, click Force Quit. You’ll be prompted for your administrator password. The process will be relaunched immediately.
Step 6
Boot in safe mode and log in. The instructions provided by Apple are as follows:
Be sure your Mac is shut down.
Press the power button.
Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Note: If FileVault is enabled under Mac OS X 10.7 or later, or if a firmware password is set, you can’t boot in safe mode.
Safe mode is much slower to boot and run than normal. Don’t launch any applications at first. If sleep still doesn’t work properly, back up all data and reinstall the Mac OS. After that, if you still have the issue, make a “Genius” appointment at an Apple Store to have the machine tested.
If sleep now works as expected, go on to the next step.
Step 7
Still in safe mode, launch the usual set of applications that are running when you have the problem, including your login items, one at a time, testing after each one. Some applications may not work; skip them. You might be able to identify the cause of the problem this way.
Step 8
If sleep is still working after you’ve launched all the usual applications, reboot as usual (not in safe mode) and test again. If sleep still works, you’re done, at least for the moment.
If you still have the sleep issue after booting out of safe mode, post again.

Airport drops when lid closes

Similar Messages

Maybe you are looking for