Sleep issues with 1.5 - console info attached

adk1889 · 05-23-2010, 05:17 PM

I'm experiencing problems with my macbook not waking from sleep properly with the 1.5 driver. I've noticed that if I make the macbook sleep then wake after only a minute or two, things work fine but I get the following in my console log:

5/23/10 1:00:10 PM com.displaylink.usbnivolistener[51] 2010-05-23 13:00:10.213 DisplayLinkManager[3456:903] (00603550.374)-[DLDistributedNotificationCenter stream:handleEvent:] stream error: Error Domain=NSPOSIXErrorDomain Code=57 UserInfo=0x60e510 "The operation couldn’t be completed. Socket is not connected"
5/23/10 1:00:10 PM com.displaylink.usbnivolistener[51] 2010-05-23 13:00:10.217 DisplayLinkManager[3456:903] (00603550.382)-[DLDistributedNotificationCenter stream:handleEvent:] Server did die - reconnecting
5/23/10 1:00:10 PM com.displaylink.usbnivolistener[51] 2010-05-23 13:00:10.217 DisplayLinkManager[3456:903] (00603550.389)-[DLDistributedNotificationCenter stream:handleEvent:] reconnected.
5/23/10 1:00:10 PM com.displaylink.usbnivolistener[51] 2010-05-23 13:00:10.230 DisplayLinkManager[3456:903] (00603550.374)-[DLDistributedNotificationCenter stream:handleEvent:] stream error: Error Domain=NSPOSIXErrorDomain Code=57 UserInfo=0x60e510 "The operation couldn’t be completed. Socket is not connected"
5/23/10 1:00:10 PM com.displaylink.usbnivolistener[51] 2010-05-23 13:00:10.230 DisplayLinkManager[3456:903] (00603550.382)-[DLDistributedNotificationCenter stream:handleEvent:] Server did die - reconnecting
5/23/10 1:00:10 PM com.displaylink.usbnivolistener[51] 2010-05-23 13:00:10.230 DisplayLinkManager[3456:903] (00603550.389)-[DLDistributedNotificationCenter stream:handleEvent:] reconnected.

Notice that the messages repeat. Seems to me that this may be a partial symptom--I'm still able to wake properly (when sleep occurs for only a minute or two).

When I leave my macbook for a few hours or overnight, then I can only wake my non-displaylink screen, and the cursor is missing. I can work around this by unplugging the displaylink device, putting the macbook to sleep with alt-command-eject key, then waking again with the space bar, then reconnecting the displaylink device when the other screens have come up. I've noticed that the console log shows my repeated errors that are somewhat different:

5/22/10 6:19:58 PM DisplayLinkUserAgent[146] (00307e90.382)-[DLDistributedNotificationCenter stream:handleEvent:] Server did die - reconnecting
5/22/10 6:19:58 PM DisplayLinkUserAgent[146] (00307e90.389)-[DLDistributedNotificationCenter stream:handleEvent:] reconnected.
5/22/10 6:19:58 PM DisplayLinkUserAgent[146] (00307e90.374)-[DLDistributedNotificationCenter stream:handleEvent:] stream error: Error Domain=NSPOSIXErrorDomain Code=57 UserInfo=0x301800 "The operation couldn’t be completed. Socket is not connected"
5/22/10 6:19:58 PM DisplayLinkUserAgent[146] (00307e90.382)-[DLDistributedNotificationCenter stream:handleEvent:] Server did die - reconnecting
5/22/10 6:19:58 PM DisplayLinkUserAgent[146] (00307e90.389)-[DLDistributedNotificationCenter stream:handleEvent:] reconnected.
5/22/10 6:19:58 PM DisplayLinkUserAgent[146] (00307e90.363)-[DLDistributedNotificationCenter stream:handleEvent:] Server did die - reconnecting
5/22/10 6:19:58 PM DisplayLinkUserAgent[146] (00307e90.370)-[DLDistributedNotificationCenter stream:handleEvent:] reconnected.
5/22/10 6:19:58 PM DisplayLinkUserAgent[146] (00307e90.374)-[DLDistributedNotificationCenter stream:handleEvent:] stream error: Error Domain=NSPOSIXErrorDomain Code=57 UserInfo=0x301800 "The operation couldn’t be completed. Socket is not connected"
5/22/10 6:19:58 PM DisplayLinkUserAgent[146] (00307e90.382)-[DLDistributedNotificationCenter stream:handleEvent:] Server did die - reconnecting

Can you figure out what the problem is from these error messages?

I've had this device for some time and it worked perfectly when I was running Mac OS X 10.5 and some other driver version. I do remember that I had a similar problem when I first bought the device but I think I had downloaded an updated driver to fix it originally. After installing Mac OS X 10.6 with the 1.5 driver the sleep problems have come back.

Any help would be appreciated.

Chris

adk1889 · 05-28-2010, 12:13 PM

I just installed 1.6 beta 2 driver and after an overnight sleep the macbook didn't hang. I'll keep my fingers crossed that something was fixed.

adk1889 · 06-16-2010, 09:13 AM

Problem with sleep hanging is back, even with 1.6 B2.

Pawel · 09-29-2010, 04:18 PM

We are happy to inform that there is a new 1.6 Beta 3 driver available for download from here.

This release has fixed a GUI freeze issue when resuming from sleep on some systems.

Regards

Pawel · 09-30-2010, 03:54 PM

This issue has been discussed here.

05-28-2010, 12:13 PM	#2
adk1889 Junior Member Join Date: May 2010 Posts: 4	Might be fixed in 1.6 driver I just installed 1.6 beta 2 driver and after an overnight sleep the macbook didn't hang. I'll keep my fingers crossed that something was fixed.

06-16-2010, 09:13 AM	#3
adk1889 Junior Member Join Date: May 2010 Posts: 4	Didn't solve problem Problem with sleep hanging is back, even with 1.6 B2.

09-30-2010, 03:54 PM	#5
Pawel Moderator Join Date: Aug 2010 Posts: 214	Duplicate This issue has been discussed here.

09-29-2010, 04:18 PM	#4
Pawel Moderator Join Date: Aug 2010 Posts: 214	We are happy to inform that there is a new 1.6 Beta 3 driver available for download from here. This release has fixed a GUI freeze issue when resuming from sleep on some systems. Regards