search

ryansheridan / macosx-nosleep-extension

Automatically exported from code.google.com/p/macosx-nosleep-extension
0 stars 0 forks source link

Does not work with Mountain Lion and no power cord #44

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
This extension does not seem to be working with Mac OSX Mountain Lion (10.8). 
Once the lid is closed (power cord UNPLUGGED) the system sleeps in 3-4 seconds. 
Different energy combinations have been tried with no results. Of course, the 
option "No Sleep with battery" has been ticked. I own a mid 2012 13" Macbook 
Air, and I have just upgraded the system from Lion to Mountain Lion.
Thank you.

Original issue reported on code.google.com by maiorcad...@gmail.com on 29 Jul 2012 at 10:58

GoogleCodeExporter commented 8 years ago 
Hi,

I'm on OSX 10.8 right now - the extension works good.
Show me your dmesg output.

--Pavel.

Original comment by integral...@gmail.com on 29 Jul 2012 at 11:03

GoogleCodeExporter commented 8 years ago 
Thanks for you answer, here is the output:

com_protech_nosleepextension: setting state: 1, for mode: 0 (battery-mode)
com_protech_nosleepextension: successfully started
com_protech_nosleepextension: setting state: 1, for mode: 0 (battery-mode)
PM notification timeout (pid 201, PCShowServerPMWr)
AirPort_Brcm43xx::powerChange: System Sleep 
en0: BSSID changed to 00:22:3f:62:a2:6e
wlEvent: en0 en0 Link DOWN virtIf = 0
AirPort: Link Down on en0. Reason 8 (Disassociated because station leaving).
en0::IO80211Interface::postMessage bssid changed
IOThunderboltSwitch(0x0)::listenerCallbackStatic - Thunderbolt HPD packet for 
route = 0x0 port = 12 unplug = 0
         0 [Time 1343560637] [Message Wake reason: EC.PME EHC1 (User)
AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance 
wake
Previous Sleep Cause: -113
The USB device HubDevice (Port 1 of Hub at 0x1d000000) may have caused a wake 
by issuing a remote wakeup (2)
en0: 802.11d country code set to 'X3'.
en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 
100 104 108 112 116 120 124 128 132 136 140
IOThunderboltSwitch(0x0)::listenerCallbackStatic - Thunderbolt HPD packet for 
route = 0x0 port = 12 unplug = 0
The USB device HubDevice (Port 8 of Hub at 0x1d100000) may have caused a wake 
by issuing a remote wakeup (3)
TBT W (2): 0x0100 [x]
The USB device Apple Internal Keyboard / Trackpad (Port 2 of Hub at 0x1d180000) 
may have caused a wake by issuing a remote wakeup (3)
AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: 
device was reinitialized
en0: 802.11d country code set to 'IT'.
en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 
100 104 108 112 116 120 124 128 132 136 140
MacAuthEvent en0   Auth result for: 00:22:3f:62:a2:6e  MAC AUTH succeeded
wlEvent: en0 en0 Link UP virtIf = 0
AirPort: Link Up on en0
en0: BSSID changed to 00:22:3f:62:a2:6e
en0::IO80211Interface::postMessage bssid changed
AirPort: RSN handshake complete on en0
en0: BSSID changed to 00:22:3f:62:a2:6e
com_protech_nosleepextension: setting state: 1, for mode: 0 (battery-mode)
IOThunderboltSwitch(0x0)::listenerCallbackStatic - Thunderbolt HPD packet for 
route = 0x0 port = 12 unplug = 0

I took just the last part after having set battery mode to 1.
Thanks a lot,

Davide

Original comment by maiorcad...@gmail.com on 29 Jul 2012 at 11:25

GoogleCodeExporter commented 8 years ago 
Are you using an external monitor?

--Pavel.

Original comment by integral...@gmail.com on 29 Jul 2012 at 12:15

GoogleCodeExporter commented 8 years ago 
Yes I am. The reason why I want to work with the lid closed is that I can fully 
operate on an external monitor. I can do so with the power cord plugged but not 
with that one unplugged.
Maybe, with an external monitor plugged, the system is forced to sleep?

Davide

Original comment by maiorcad...@gmail.com on 29 Jul 2012 at 12:19

GoogleCodeExporter commented 8 years ago 
Ohh, now is clear. This issue is not related to 10.8 update.

The main cause is external monitor. Good news that I know about the problem and 
it's already fixed and changes are committed. Bad news, the fix will be 
available in 1.3.1 version.

I'll try to release it during August.

Original comment by integral...@gmail.com on 29 Jul 2012 at 12:31

GoogleCodeExporter commented 8 years ago

Original comment by integral...@gmail.com on 29 Jul 2012 at 12:31

GoogleCodeExporter commented 8 years ago 
But anyway, thanks for the report!:)
--Pavel

Original comment by integral...@gmail.com on 29 Jul 2012 at 12:44