DisplayLink Forum - View Single Post - Failing to wake up from sleep? Try disabling your screen saver.

aiyagari · 08-02-2010, 07:59 PM

There are two processes installed by the DisplayLink installation.

There is a LaunchDaemon com.displaylink.usbnivolistener loaded from the file /Library/LaunchDaemons/com.displaylink.usbnivolistener.plist

There is also a LaunchAgent com.displaylink.useragent loaded from the file /Library/LaunchAgents/com.displaylink.useragent.plist

Both must be running for it to work.

Do not just try to remove the driver with kextunload. It will crash. If you instead use launchctl to remove the controlling process of the driver, it goes away cleanly.

My procedure in the "solution" thread stops the daemon only on display sleep, and then restarts the daemon and agent on display wakeup (so the agent syncs properly with the new instance of the daemon)

I am wondering if you may have installed the DisplayLink drivers as "my user only" rather than "for all users". I must have installed it "for all users" given where the installation put the agent on my system (also MacBookPro i5 with 10.6.4). Still no crashes since I implemented this solution.

08-02-2010, 07:59 PM	#12
aiyagari Junior Member Join Date: Jun 2010 Posts: 12	There are two processes installed by the DisplayLink installation. There is a LaunchDaemon com.displaylink.usbnivolistener loaded from the file /Library/LaunchDaemons/com.displaylink.usbnivolistener.plist There is also a LaunchAgent com.displaylink.useragent loaded from the file /Library/LaunchAgents/com.displaylink.useragent.plist Both must be running for it to work. Do not just try to remove the driver with kextunload. It will crash. If you instead use launchctl to remove the controlling process of the driver, it goes away cleanly. My procedure in the "solution" thread stops the daemon only on display sleep, and then restarts the daemon and agent on display wakeup (so the agent syncs properly with the new instance of the daemon) I am wondering if you may have installed the DisplayLink drivers as "my user only" rather than "for all users". I must have installed it "for all users" given where the installation put the agent on my system (also MacBookPro i5 with 10.6.4). Still no crashes since I implemented this solution.