![]() ![]() The suggested test I mentioned in a previous comment unfortunately did not work. In the meanwhile I have installed ShareMouse on a Windows machine and a Mac. Granted, NOT the most convenient way to do this, but it does tell me the Mac is awake after a WOL, however the "user interface" isn't active yet. You're now in a "remote" Terminal on your sleeping Mac.Īnd press ENTER.Next you will have to enter your password (the username and password are the ones you use to login to your Mac the usual way).Ssh If this is the first time you do this, it will ask if you want to store the key fingerprint - enter "yes". On your Windows PC, open a Command Prompt and type (replace username and ip_address_mac):.Use miniWOL to send the magic packet (port 9) - you'll see the USB devices being powered again.Put your Mac to sleep and wait for the USB devices to power down.In System Preferences -> Sharing -> enabled " Remote Login" (this is wat is called SSH).So I got this to work, but it feels like toooo much, but it works: ![]() There is a statement to mimic "user" movement (mouse/keyboard) to prevent a machine from going to sleep (or maybe even wakeup the screen?) caffeinate -u -t 1 I did see something interesting, but it would be kind-a sad if we would have to go that route Still not the solution we're looking for of course, but it may get us close. Once your Mac went through all these steps, and the USB devices are finally on again, maybe moving the mouse to the other screen (even though you can't see it) may turn the monitor ON again? Moving the mouse doesn't do anything - screen remains black until I touch a key on the keyboard or a mouse button. USB devices are powered ON again (LEDs on keyboard ON), but the monitor remains black. Sleeping for 97 seconds - All OFF - USB devices go OFF again, external disk spins down, LEDs on keyboard OFF, fans OFF.Īfter that, when I send the WOL magic packet (port 9 and port 4343 have the same effect, so I'd stick with port 9): Sleeping for 45 seconds - USB devices are powered ON again and my external disk starts spinning (I assume some Time Machine activity). Sleeping for 17 seconds - USB devices are turned OFF (LEDs on my keyboard go OFF). Sleeping for 10 seconds - Cooling fans stop. Once the Mac wakes up again, it continues by printing the date and time again (soI can find those in the log) and show the "Magic packets" from the power management log.Īt sleep (0 seconds), the screen goes OFF, and the cooling fan keeps spinning for a few more seconds. Which prints the date and time, puts the Mac to sleep. So to get an idea what may be the issue, which I still haven't found, I use this Terminal statement: date pmset sleepnow date pmset -g everything | grep Magic Same as "Wake for network access" in the Energy Saver preferences." " womp - wake on ethernet magic packet (value = 0/1). On the other hand the man page of "pmset" states: Granted this is a help page, and when have those ever been helpful, but it doesn't mention WOL, which you'd assume would be needed for this to work. " Even in sleep mode, wakes to provide access to shared resources, such as shared printers or Music playlists." At least I'd assume that a WOL magic packet should tell the Mac to "wake up", even if it's not entirely asleep.Īnother thing that makes me wonder about WOL on a Mac, is the explanation of "Wake for network access": I did disable Power Nap on my Mac for that reason, but in the end it didn't make much of a difference.Īll-in-all I wouldn't expect this to matter. Since I'm not very knowledgeable on the "pmset" details, there could be conflicts with different kind of sleep modes the Mac may be using. When looking at the power management event with the code below, you'll see a lot of "sleep preventers". Note: port 9 WOL also do appear in the power management log.Ģ) I wonder when a Mac really goes to sleep. (even though nothing happened - my Mac remained dark) ![]() 22:19:25 +0100 WakeDetails DriverReason:Enet.MagicPacket - DriverDetails:Magic packet received You can see that the WOL packets (over port 4343) indeed arrive at the Mac. In an old post I did read someone using port 4343 for WOL which did trigger did show up in the power management log: pmset -g everything | grep Magic I've tested the default port (9), which didn't work, and the common alternative port (7), which didn't work either (same as on your setup). I didn't get any smarter here, except that (see end of this post) that Port 4343 seems to do something. So some observations I did while testing and searching for an answer Since the infor is getting a little out of hand, I (Hans) have started this forum topic. So this topic is a continued conversation on how to use miniWOL to wake up a Mac from sleep started by Ryan. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |