ACPI doesn't detect closed lid until other acpi event

Basically I have the same problem as described in this thread:
https://bbs.archlinux.org/viewtopic.php?id=121224
No solution is posted so I bring this up again.
As said when I close the lid, acpi doesn't detect it not in the acpi.log neither with acpi_listen. When I insert the battery, acpi immediately detects the closed lid and my laptop goes in suspend as it's supposed to.
This happens with a WM + acpi + laptop-mode-tools, in Xfce and in Gnome. KDE however works fine.
The logs when I close the lid and then insert the battery:
acpi.log
Jan 21 20:51:31 localhost acpid: client 1254[0:1000] has disconnected
Jan 21 20:51:31 localhost acpid: client connected from 1254[0:1000]
Jan 21 20:51:31 localhost acpid: 1 client rule loaded

I can tell with the lid closed because of which lights are on.
Anyway, I don't see anything interesting at all in the logs. This is so weird.
EDIT: I'm thinking that it might be conflicting kernel modules. For example I have phc-intel and acpi-cpufreq. Plus I'm using the CK kernel. So when I get home today, I'll first try removing phc-intel, then acpi-cpufreq, then I'll try stock kernel.
Last edited by pogeymanz (2011-06-22 17:32:56)

Similar Messages

KDE: Laptop only sleeps when closing lid every other time

Hello all,
I'm running KDE 4.14.1 on an older Toshiba Satellite laptop. In the KDE System Settings, I've told it to sleep when closing the lid and this works - but strangely only every other time I close the lid. It will work once, then I open the lid and it powers up just fine. Then I close it again and the screen just turns off but the laptop stays fully powered.
Any ideas what might be going on? It consistently only sleeps every other time when I close the lid (the other times it just turns the screen off).

Take a look at /etc/systemd/logind.conf
Is systemd also trying to manage this?

My MacBook Pro 13.3inch (Late 2011) doesn't detect earphones.

My MacBook Pro 13.3inch (Late 2011) doesn't detect earphones being plugged in after I installed Mountain Lion. If I reboot, it works but after a few unpluggings and more plugins, it doesn't detect them anymore until I reboot. Help please.

This may or may not fix your problem.
Try a NVRAM reset.
Try a SMC reset.
If neither work, you're just going to have to take your unit into your local Apple Store or AASP and see if you've a hardware issue.
Good luck,
Clinton

MacBook (Lion) doesn't sleep even after closing lid

Is anyone experiencing this as well? I have encounter the same problem a few times now. My macbook would have it's fan keep running even when the lid is closed. Isn't it strange? I haven't had this problem before in Snow Leopard.
In snow leopard, even when the fan is running at 6200rpm, as soon as I close the lid. My macbook would be quiet almost instantly. However, with Lion my fan and processor would keep running. Anyone else? any idea?

Hey Pascale,
I am not sure if you have fixed this but I had the same problem and found some advice from another website...
http://www.adeepbite.com/lion-seems-having-insomnia-it-doesnt-sleep-easily/
All I had to do was turn off my "internet sharing" (System preferences -> Sharing -> Internet Sharing (uncheck) )
and presto, no more closing lid problems.
If your internet sharing wasn't the issue then I don' t know what is.
Cheers

Hey guys i have the newest macbook air and i recently bought a magic mouse and my macbook doesn't detect it i already tried switching it on and off and all that other stuff. Any help??

Hey guys i have the newest macbook air and i recently bought a magic mouse and my macbook doesn't detect it i already tried switching it on and off and all that other stuff. Any help??

when you have the same issue after the SMC reset:
put new batteries in the MM (even if the others are not empty), turn Bluetooth off then on again on the MBA, take all USB connections out (if any), delete the pairing of the MM and re pair the MM.

Mountain Lion doesn't detect displays on startup

I use my MacBook Pro extensively in clamshell mode, and when I did this in Lion, the integrated screen would stay off whenever I turned onb the computer because the lid was closed. However, in Mountain Lion, the screen stays on despite the fact that the lid is closed. Is there anyway to force my Mac to detect displays on start up?

Go to Sys Prefs > Displays > (hold Option) and a "Detect Displays" button will appear at the bottom right. The problem for me it's that even though a display is connected and I managed to get the button to show up, it still didn't detected the display until I unplugged and oplugged back again from the thunderbolt port.

Waking up a closed lid 2011 MBP

Hello. I just bought the new 2011 17" MBP. I bought an external Viewsonic monitor connected via a DVI adaptor. I also have an Apple USB extended keyboard connected to it and a Magic Mouse.
When I close the lid, the MBP goes to sleep. I cannot wake it up, using the keyboard or mouse. I have to lift the lid for it to wake up. I would like to use the MBP with my external monitor with the lid closed.
Can anyone help?

I wouldn't be surprised if you run into this issue:
http://discussions.apple.com/thread.jspa?threadID=2770324
Basically, my new 2011 13" MBP does not detect the external monitor using DVI.
If your mac doesn't detect the display, and you'd close the lid, it will sleep.
Does your mac detect the display before you close it?
Perhaps you are experiencing another instance of incorrect DVI behavior with the Thunderbolt port.
Contact apple support to alert them to the issue.

10.5.2 wake/sleep and closed-lid problems

As of 10.5.2 my MBP no longer works correctly in closed lid mode using a hardware
setup that previously worked flawlessly. After plugging in power and video, plugging
in the USB keyboard seems to wake the system, but no video. I then must open the
lid, unplug the USB and video and try to get the system to respond. I often must cycle
the power to reset the system--very disturbing to do that.
Also as of 10.5.2, I have had to power-cycle the machine when it has refused to wake
in open-lid mode and this weekend I the entire machine froze (no mouse movement,
no expose, etc) in the middle of work using a graphics-intensive program and I had
to reboot by cycling the power.
A friend also reported similar issue in which the system would not respond after the
screensaver became active.
Are others seeing problems like these? I am beginning to suspect that the post-10.5.2
graphics update has problems.

I just wiped my HD and reinstalled everything besides the Graphics Update. I can now close the lid of my MBP and use my external monitor alone. The Graphics Update had made that impossible.
Further, I am in the habit of putting my MCP to sleep and putting it in a backpack in the morning, meeting friends for breakfast, and re-awakening it at the office. When I did get to my office, I found (as another user had on another thread) that the MBP, even closed, had woken itself up and was hot as heck. I am uncertain that sleep will work properly under 10.5.2, but I know that the display wackiness of the Graphics Update was driving me nuts. I will not install it until Apple fixes it.
I looked around for awhile for a way to uninstall the Graphics Update, but could not find it...I suspect it exists somewhere.
The 10.5.2 Combo update (343MB download) DOES NOT include the Graphics Update, and at this time, I seem quite ok with everything else updated.

Closed Lid Operations Wont Work

I am a big fan of the closed lid with external mouse, keyboard, and display (minimize spill risks in college dorm room). I just got a new macbook pro after 4 great years with my g4 powerbook and I cannot get the new machine to work with the lid closed. I have tried working with both displays then closing it, but it won't wake up. I tried putting it to sleep and attaching the external display but it doesn't wake up. The for either if I try to open the machine to use it normally the built in display, keyboard, and trackpad are non-responsive and so are all my external items. Has anyone else had this problem or any ideas on what could be going on.

Jonathan , I am experiencing the same exact problems with my Macbook Pro 15 inch. I first started noticing about a month ago that the computer was getting unusually HOT to the touch , and after one day I set the lid down, when I tried to open it back up, it remained on , but no screen, and unresponsive. I have had to restart it everytime since then. It also now takes a lot longer than usual to reboot. I hope the people at Apple resolve this soon, because this is WAY too expensive to be having these problems on a new machine Ive only had for 5 months.

EXTERNAL HDD NOW DISAPPEARS WHEN USING MY MBP IN CLOSED LID MODE

I have an 15" MBP 2.53 running Snow Leopard, which installed fine. When I go to use it with my Apple 24" Display and my external hard drive, the external HDD disappears when I go into closed lid mode.
The finder freezes too, and I can no longer enter into Time Machine.
The external HDD does show up in disk utility, however.

and please ... STOP SHOUTING!
It doesn't make your message any more relevant or increase the motivation to help you. To be honest, it makes you look like a moron, if anything.
Cheers,
Jazz

IChat and Closed-Lid Mode

I found something very interesting in iChat 4.0.8 and Leopard 10.5.7. I run my MBP in closed-lid mode with an external Apple Cinema Display. When in iChat, I cannot do audio chats at all - i.e. no sound input with either of my external interfaces (Apogee Duet via FireWire and Mbox 2 Mini via USB). Of course video doesn't work at all, as the built-in iSight is not accessible. If I open the MBP display, they both work normally. As soon as I close the display, wake the MBP and run in closed-lid mode, I cannot get any input whatsoever. The devices work normally in QuickTime Player Pro, Soundtrack Pro, Logic Pro, Pro Tools, etc. In either mode there IS an input level in System Preferences > Sound as well. I even tried to "trick" the system by using Audio Hijack Pro and Soundflower, but the issue remains. No combo of settings in the Sound preference pane and iChat preferences will allow a signal input.
Anyone else running a MacBook or MacBook Pro in closed-lid mode? Does this issue happen on your Mac as well?
VERY strange,
C

Well...Snow Leopard seems to have fixed this issue.

Using a selector to detect closed socket channel.

Basically our app uses one thread to perform a select on multiple socket channels. When a socket is closed (either remotely or locally) the server app needs to unregister the client (so we need to detect closed channels). We've been using blocking IO previously (no dramas), but now we're dealing with many connections/clients we need to rework it as we're getting excessive amounts of threads. Anyway, that's just background.
Here's the problem we're getting, I have boiled it down to the following.
SocketChannel channel = SocketChannel.open();
channel.connect(socketAddress); // for the test this is localhost.
// this make sure socket is open, remote end just echos, waits 3 seconds and closes the socket.
channel.write(ByteBuffer.wrap("testLocalSocketClose\n".getBytes()));
channel.configureBlocking(false);
Selector selector = Selector.open();
LOG.fine("registering channel");
channel.register(selector, SelectionKey.OP_READ, channel);
LOG.fine("closing channel");
channel.close();
LOG.fine("waiting...");
int i = selector.select();
// this never happens (or it does very rarely)
LOG.fine("selector woke with " + i + " selected");I would have expected the selector to return the selection key of the dead channel. Given that it doesn't and this scenario is possible (channel closing just after a read operation but before another select is called - in separate threads obviously). How can we reliably detect/be informed that the channel has been closed?
(I saw somewhere someone mention adding the OP_WRITE to the key, I have tried this as well and it makes no difference).
Many Thanks.
Bob.

May I suggest you look at your application and reassess; either it's wrong or it's your understanding of what our issue is.
Please try the simple test below.
WSADATA ws;
WSAStartup(0x0101, &ws);
SOCKET sock = socket(PF_INET, SOCK_STREAM, 0);
struct sockaddr_in server;
server.sin_family = AF_INET;
server.sin_addr.s_addr = htonl(INADDR_ANY);
server.sin_port = htons(9000);
cout << "binding" << endl;
bind(sock, (struct sockaddr *)&server, sizeof(server));
cout << "listening" << endl;
listen(sock, SOMAXCONN);
struct sockaddr_in client;
int client_size = sizeof(client);
memset(&client, 0, client_size);
cout << "accepting" << endl;
SOCKET clientSock = accept(sock, (struct sockaddr*)&client, &client_size);
// shutdown socket.
cout << "shutting down client socket" << endl;
shutdown(clientSock, SD_BOTH);
// setup select
FD_SET fd;
TIMEVAL tv;
FD_ZERO(&fd);
tv.tv_sec = static_cast<int>(6000);
tv.tv_usec = 0;
FD_SET(clientSock, &fd);
cout << "selecting" << endl;
int rc = select(0, &fd, NULL, NULL, &tv);
cout << rc << ", " << FD_ISSET(clientSock, &fd) << endl;
char msg[500];
if (FD_ISSET(clientSock, &fd)) {
     cout << recv(clientSock, msg, 500, 0) << endl;
     cout << WSAGetLastError() << endl;
cout << "closing" << endl;
closesocket(clientSock);Telnet to port 9000, you get the following output immediately:
binding
listening
accepting
shutting down client socket
selecting
1, 1
-1
10058
closing
The solution I posted previously re calling shutdownInput/Output in Java isn't correct however, I left OP_WRITE on by mistake, which always returns ready, my fault. Apologies.
Whatever the behaviour, it will be the same for Selector.select() as it is for select().
Clearly not.
Edited by: Bawb on 29-Jul-2011 07:01, I had left OP_WRITE on which was returning ready each time, when I realised and took it out I removed the shutdown code which made me think I hadn't sorted this. Apologies again.
Still reckon an RFE for OP_SHUTDOWN should be added to Java.
Thanks.

Using Front Row w/ Macbook in closed lid position (w/ Cinema Display) ?

Using Front Row w/ Macbook in closed lid position (w/ Cinema Display) -
Is it possible if I buy a remote, to use Front Row on a Macbook that is in the closed position?
I use a Macbook linked to an external cinema display (a brushed alum, slightly older 23" model - doesn't have built in iSight) - wondering if I can get some of the same functionality via remote and Front Row.
Do Macbooks even support the remotes? I would assume since they have a built in webcam/iSight they can accept infrared, or no?
Thanks!

I am using the IR remote with my MacBook Pro. That remote operates my LED Display when I do it thus:
Shut down Mac, connect display, and restart.
Close lid. Mac goes to sleep and display goes black.
Point IR remote at Mac (not too far away or too oblique an angle - see instructions for Remote) and click "Menu" button.
Mac wakes up, launches Front Row, and displays it on my 24 inch.
EZ Jim
Mac Pro Quad Core (Early 2009) 2.93Ghz w/Mac OS X (10.6.2) MacBook Pro (13 inch, Mid 2009) 2.26GHz (10.6.2)
LED Cinema Display G4 PowerBook 1.67GHz (10.4.11) iBookSE 366MHz (10.3.9) External iSight

Charging iPhone with closed lid on mbp

I've been researching, but found nothing this specific so far. Related links:
- http://support.apple.com/kb/HT1476 - This says it may or may not charge
- http://forums.mactalk.com.au/11/72536-snow-leopard-not-charging-iphone-while-lid -closed.html - This says it should work since Leopard and if it's not working to reset the SMC should fix it (I haven't tried yet): http://support.apple.com/kb/HT3964
- http://forums.macrumors.com/showthread.php?t=795007 This is not the same model, but for him it seems to not work anyway
- http://discussions.apple.com/thread.jspa?threadID=2126178 Suggests http://support.apple.com/kb/HT3131 for dealing with closed lid, but requires external display, among other things that don't come to this case (or so I guess)
To me, experience showed that closing the lid with the iPhone already connected works fine. I'm using a macbook pro 2009, as already hinted elsewhere. It's 13'' if that makes any difference.
But if I have the computer sleeping in the bag and want to just plug the iPhone for charging convenience, then it doesn't work. I have to remove it, open the lid, wait for charging to begin, then I can safely close, sleep, put it back on the bag, and it will be charging.
So I wonder how this is supposed to work, and if I can "fix" this behavior. Anyone knows?

I actually solved it on my own luck. Oddly enough, just need to remove and re-plug.
Here, this is a small chart:
1- Computer with lid open, up and running with energy - whatever AC or not.
normal behavior, everything as expected: plug in iPhone it starts charging.
2- Computer with closed lid, sleeping as blinking light indicate and plugged in AC power.
normal behavior, everything as expected: plug in iPhone it starts charging.
3- Computer with closed lid for long time, unplugged from AC power, no cables on it whatsoever.
plug in iPhone - nothing happens.
unplug it and plug in again in either port - it starts charging!
If you close the lid and don't wait it gets to sleep (that is, white blinking light - if you want to be sure, wait till the computer cools down, if it was hot - that's sleep mode) you'll get normal behavior right on the first plug time. The trick of plugging again seem to work always from my tests. So this is a undocumented feature that took me freaking long enough to uncover!
Now it's aight!

Screen Saver when calling and need to use the Keypad, the screen saver doesn't detect the phone has left the ear and blanks out the screen. Even ending a call is difficult as the screen blanks out within seconds

I have to use the Keypad a lot when making calls. Make the call, the Robot then asks to enter a number for a service, pull the phone down from the ear, the screen may light up for a second, but then the screen saver cuts in, blanking the screen out. Sometimes you hit the Home Key to awaken the sccreen, enter your number and then back to the ear to hear the next set of instructions. Back and forth just trying to enter the options is a pain. Sometimes even trying to end the call, the screen blanks out and you fight to try and end a call.
If I use the Speaker function the keypad works; the speakler phone is not alway appropriate.
It appears that the phone gyro, doesn't detect the phone has moved from the ear to the viewing angle. This wasn't an issue until recently and I can't remeber if it's the iPhone 5 or one of the updates. It definitly wasn't there earlier on, as I threw away an Windows 6.5 phone for the same problem.
I'm not sure if it's a hardware or software (design) issue.

It is not the gyro. This has everything to do with the iPhone's prioximity sensor.
Are you using a case that may be blocking or partially blocking the proximity sensor? If you are using the case, remove the case prior to the next call to see if the same occurs without the case.

ACPI doesn't detect closed lid until other acpi event

Similar Messages

Maybe you are looking for