DisplayLink Forum

DisplayLink Forum (https://displaylink.org/forum/index.php)
-   CLOSED: Mac 1.5 Release (https://displaylink.org/forum/forumdisplay.php?f=7)
-   -   1.5b{3-4}: MacBook sleep takes a long time due to DisplayLink (https://displaylink.org/forum/showthread.php?t=118)

steverod 10-06-2009 04:46 PM

1.5b{3-4}: MacBook sleep takes a long time due to DisplayLink
 
Hi:

I have a MacBook (late 2006) running 10.6.1 and have been using a DisplayLink adapter for about 6 months, at one site (the MacBook gets used at 2 different sites, plus home; only 1 of the 3 locations has the DisplayLink card). The 1.5 beta drivers are working fairly well, EXCEPT...

Sleep takes a very long time, and 'pmset -g log' reports, consistently:

* Domain: applicationresponse.timedout
- Message: Kernel DisplayLinkUserA com.apple.powermanagement.applicationresponse.time dout 30000 ms
- Time: 10/6/09 9:12:36 AM PDT
- Signature: DisplayLinkUserA
- UUID: A4A349B3-A903-4BAE-8934-76B421985360
- Result: Noop
- Response time (ms): 30000

While there are other applications with "slowresponse" messages (and those are on the order of 400 ms), the "timedout" is only generated by the display link code.

A 30 second sleep time is not the end of the world, but it is really annoying.

By the way, I'm continually amazed at how *well* this works. Good job!

Patrick 10-08-2009 09:11 AM

Quote:

Originally Posted by steverod (Post 405)
Hi:

I have a MacBook (late 2006) running 10.6.1 and have been using a DisplayLink adapter for about 6 months, at one site (the MacBook gets used at 2 different sites, plus home; only 1 of the 3 locations has the DisplayLink card). The 1.5 beta drivers are working fairly well, EXCEPT...

Sleep takes a very long time, and 'pmset -g log' reports, consistently:

* Domain: applicationresponse.timedout
- Message: Kernel DisplayLinkUserA com.apple.powermanagement.applicationresponse.time dout 30000 ms
- Time: 10/6/09 9:12:36 AM PDT
- Signature: DisplayLinkUserA
- UUID: A4A349B3-A903-4BAE-8934-76B421985360
- Result: Noop
- Response time (ms): 30000

While there are other applications with "slowresponse" messages (and those are on the order of 400 ms), the "timedout" is only generated by the display link code.

A 30 second sleep time is not the end of the world, but it is really annoying.

By the way, I'm continually amazed at how *well* this works. Good job!


Hello Steve,

thanx for posting this issue. I'll look into it as I haven't had problems here - are you using a USB Hub ?

Regards Patrick

Patrick 10-08-2009 09:45 AM

It seems that for some reason the UserAgent sometimes can't connect to the WindowServer when going to sleep. I've put a workaround in, that should fix this issue. Will be in the next release.


Regards Patrick aka Jolly

steverod 10-09-2009 09:49 PM

Thanks!

I *am* using a hub (the DisplayLink chip is in a Kensington Dock with Video, I forget the model number but it has a USB hub/Ethernet/sound/etc and supports 1280x1024 VGA graphics out).


All times are GMT. The time now is 11:43 AM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.