My console is being flooded with DisplayLink messages

[MickM]

Hi,

Every couple seconds I'm seeing several lines being output to my console that indicate some kind of DisplayLink issue. Does anybody out there recognize what's going on?


11.1005 6:02:05.190 AM com.apple.launchd: (com.displaylink.usbnivolistener[36501]) Bug: launchd_core_logic.c:4692 (24984):2
11.1005 6:02:05.273 AM com.apple.launchd.peruser.501: (com.displaylink.useragent[36502]) Bug: launchd_core_logic.c:4692 (24984):2
11.1005 6:02:05.274 AM com.apple.launchd.peruser.501: (com.displaylink.useragent[36502]) posix_spawn("/System/Library/Extensions/DisplayLinkDriver.kext/DisplayLinkAgent/DisplayLinkUserAgent", ...): No such file or directory
11.1005 6:02:05.274 AM com.apple.launchd.peruser.501: (com.displaylink.useragent[36502]) Exited with code: 1
11.1005 6:02:05.274 AM com.apple.launchd.peruser.501: (com.displaylink.useragent) Throttling respawn: Will start in 5 seconds
11.1005 6:02:10.193 AM com.apple.launchd: (com.displaylink.usbnivolistener[36503]) Bug: launchd_core_logic.c:4692 (24984):2
11.1005 6:02:10.278 AM com.apple.launchd.peruser.501: (com.displaylink.useragent[36504]) Bug: launchd_core_logic.c:4692 (24984):2

[MickM]

I forgot to mention I'm using a 17" 2010 MacBook Pro running 10.7.1 and (in case it matters) I do NOT currently have an external monitor hooked up to the laptop that needs DisplayLink. I do, however, have a regular external monitor attached via mini displayport.

[EddieMa]

Wow, I just checked my console, and I'm also flooded despite having no external displays connected.

-- Eddie

2007 MacBook Core 2 Duo; Snow Leopard 10.6.8; DisplayLink Driver 1.6.

[MickM]

Anybody got a fix for this? Seriously, every couple seconds I get a console entry from this software!! Is anybody working on 1.7b5?

[ChristianP]

Anybody got a fix for this? Seriously, every couple seconds I get a console entry from this software!! Is anybody working on 1.7b5?


Sorry for the late answer. This messages are generated by the DisplayLink daemon, that is automatically respawn if for any reason quits.
In your case it seems that a file is not found. Have you partially removed the driver? Could you please check if the DisplayLink kernel extension is available? Just type in a terminal:
ls -al /System/Library/Extensions/DisplayLinkDriver.kext
and
ls -al /System/Library/Extensions/DisplayLinkDriver.kext/DisplayLinkAgent/DisplayLinkUserAgent

Thanks

[MickM]

It seems stuff is there:

------------------------------------------------------------------------------------------------------------------ 07:48:13
mmueck@Mick-Muecks-Computer:~$ ls -al /System/Library/Extensions/DisplayLinkDriver.kext
total 0
drwxr-xr-x 4 root wheel 136 Oct 26 22:23 .
drwxr-xr-x 257 root wheel 8738 Nov 2 08:00 ..
drwxr-xr-x 5 root wheel 170 Sep 8 04:28 Contents
drwxr-xr-x 16 root wheel 544 Sep 8 04:28 DisplayLinkAgent
------------------------------------------------------------------------------------------------------------------ 07:48:20
mmueck@Mick-Muecks-Computer:~$ ls -al /System/Library/Extensions/DisplayLinkDriver.kext/DisplayLinkAgent/DisplayLinkUserAgent
-rwxr-xr-x 1 root wheel 50136 Sep 8 04:28 /System/Library/Extensions/DisplayLinkDriver.kext/DisplayLinkAgent/DisplayLinkUserAgent

[ChristianP]

Ok, the files seem correctly installed. I would suggest to uninstall the driver, repair file permissions (using DiskUtility) and reinstall the driver.
If the problem persists, could you please use the debug tool here http://www.displaylink.com/support/ticket.php?id=269 and post the output file. Thanks