Monitor Remains Black

valvalis · 08-17-2009, 03:43 PM

Just installed the new 1.5b1 driver. The system failed the first time (threw an error about improper registration of the kext). I uninstalled and reinstalled and it installed the second time without any errors.

The monitor / DisplayLink adapter is still unrecognized. I'm using an EVGA UV+ (UV16) adapter.

Admin · 08-17-2009, 03:57 PM

Quote:

Originally Posted by valvalis

Just installed the new 1.5b1 driver. The system failed the first time (threw an error about improper registration of the kext). I uninstalled and reinstalled and it installed the second time without any errors.

The monitor / DisplayLink adapter is still unrecognized. I'm using an EVGA UV+ (UV16) adapter.

Hi, can you please provide more information as outline in this post.

tysonedwards · 08-17-2009, 04:10 PM

I am experiencing the same issue under Mac OS X 10.6 (10a432).

I was doing some tests, and I see that in System Profiler, the DisplayLink Card is showing the following:

Product ID: 0x014a
Vendor ID: 0x17e9 (DisplayLink (UK) Ltd.)
Version: 0.03
Serial Number: 014A-109792
Speed: Up to 480 Mb/sec
Manufacturer: DisplayLink
Location ID: 0x24100000
Current Available (mA): 500
Current Required (mA): Unknown (Device has not been configured)

The console is also scrolling the following messages at 5 second intervals:

8/17/09 10:08:56 AM com.apple.launchd.peruser.501[92] (com.displaylink.useragent[366]) posix_spawn("/System/Library/Extensions/DisplayLinkDriver.kext/DisplayLinkAgent/DisplayLinkUserAgent", ...): No such file or directory
8/17/09 10:08:56 AM com.apple.launchd.peruser.501[92] (com.displaylink.useragent[366]) Exited with exit code: 1
8/17/09 10:08:56 AM com.apple.launchd.peruser.501[92] (com.displaylink.useragent) Throttling respawn: Will start in 5 seconds
8/17/09 10:08:56 AM com.apple.launchd[1] (com.displaylink.usbnivolistener[367]) posix_spawn("/System/Library/Extensions/DisplayLinkDriver.kext/DisplayLinkAgent/USBNivoListener", ...): No such file or directory
8/17/09 10:08:56 AM com.apple.launchd[1] (com.displaylink.usbnivolistener[367]) Exited with exit code: 1
8/17/09 10:08:56 AM com.apple.launchd[1] (com.displaylink.usbnivolistener) Throttling respawn: Will start in 5 seconds

Please see the attached Information Log from the Mac Debug Tool.

As well, this was a clean installation of 10a432 rather than an upgrade from a previous version. The previous DisplayLink drivers had not been installed.

Edit: I have tested on both x86_64 (my previous kernel) and i386.
After rebooting to i386 did not have everything immediately work, I tested uninstalling and re-installing, and have still had no success. Same error messages.

raminf · 08-17-2009, 04:40 PM

Running 10A432 Snow Leopard. Installed driver and rebooted. Screen remains dark.

As to the requested DisplayLink Information.zip file, I'm happy to send it directly to tech support but 've got an issue with posting it to a public forum.

After running the utility (in "Basic" mode) and looking at the System Profile.txt output file it generates it appears that it includes a lot of information that can be potential security risks. There's a full list of network connections, router info, profile settings that include "Password ID" values, whether ports require authentication or not, etc. Not sure why this all needs to be included in the display information (or posted up here).

In "Full Mode" there's even more data that people may not want to splatter over the Interwebs -- like apps installed, shared folders, etc.

Suggest you modify the diagnostic tool to not include such data, especially public IP values, MAC addresses (that can be faked to get around router security), usernames, password-related keys, UUID data, Bluetooth addresses, DHCP settings, etc.

Like I said, I don't have an issue sending this privately -- especially if it helps solve the driver issue.

w3woody · 08-17-2009, 05:12 PM

I'm also seeing the same problem: after installing on MacOS 10.6 build 10A432 I get...nothing.

I've attached the DisplayLink information file. I've also attached the output of my Installer Log.

In my system log I'm seeing the following message every 5 seconds or so:

8/17/09 10:08:01 AM com.apple.launchd[1] (com.displaylink.usbnivolistener) Throttling respawn: Will start in 5 seconds
8/17/09 10:08:01 AM com.apple.launchd.peruser.501[204] (com.displaylink.useragent[533]) posix_spawn("/System/Library/Extensions/DisplayLinkDriver.kext/DisplayLinkAgent/DisplayLinkUserAgent", ...): No such file or directory
8/17/09 10:08:01 AM com.apple.launchd.peruser.501[204] (com.displaylink.useragent[533]) Exited with exit code: 1
8/17/09 10:08:01 AM com.apple.launchd.peruser.501[204] (com.displaylink.useragent) Throttling respawn: Will start in 5 seconds

Also, I should note that it does appear the DisplayLinkUserAgent file is missing from the DisplayLinkAgent folder within the .kext. I've attached a file list of the contents of that folder.

Hope this helps.

skevy · 08-17-2009, 05:21 PM

Quote:

Originally Posted by w3woody

I'm also seeing the same problem: after installing on MacOS 10.6 build 10A432 I get...nothing.

I've attached the DisplayLink information file. I've also attached the output of my Installer Log.

In my system log I'm seeing the following message every 5 seconds or so:

8/17/09 10:08:01 AM com.apple.launchd[1] (com.displaylink.usbnivolistener) Throttling respawn: Will start in 5 seconds
8/17/09 10:08:01 AM com.apple.launchd.peruser.501[204] (com.displaylink.useragent[533]) posix_spawn("/System/Library/Extensions/DisplayLinkDriver.kext/DisplayLinkAgent/DisplayLinkUserAgent", ...): No such file or directory
8/17/09 10:08:01 AM com.apple.launchd.peruser.501[204] (com.displaylink.useragent[533]) Exited with exit code: 1
8/17/09 10:08:01 AM com.apple.launchd.peruser.501[204] (com.displaylink.useragent) Throttling respawn: Will start in 5 seconds

Also, I should note that it does appear the DisplayLinkUserAgent file is missing from the DisplayLinkAgent folder within the .kext. I've attached a file list of the contents of that folder.

Hope this helps.

See this thread for a temporary fix until they release the driver with all the files included :-)

http://www.displaylink.org/forum/showthread.php?p=123

w3woody · 08-17-2009, 06:18 PM

Quote:

Originally Posted by skevy

See this thread for a temporary fix until they release the driver with all the files included :-)

http://www.displaylink.org/forum/showthread.php?p=123

The solution doesn't work for me since rebooting into a 32-bit kernel is not an option right now. But thanks for the pointer. :-)

skevy · 08-17-2009, 06:50 PM

Quote:

Originally Posted by w3woody

The solution doesn't work for me since rebooting into a 32-bit kernel is not an option right now. But thanks for the pointer. :-)

I see. I would assume that they actually have built the driver to work in 64 bit - but just forgot to include it. I would of course prefer to run the 64-bit kernel, but at this very moment my two extra monitors are more important :-)

tysonedwards · 08-17-2009, 07:46 PM

Given that we are missing multiple files from the package that are essential for it's installation and the driver's successful operation, it seems as though it's a safe bet that this version of the 1.5 driver is not what DisplayLink intended to release.

Admin · 08-18-2009, 11:26 AM

Quote:

Originally Posted by raminf

--8<--
As to the requested DisplayLink Information.zip file, I'm happy to send it directly to tech support but 've got an issue with posting it to a public forum.
--8<--

You can send you log files us via PM if you would prefer.

08-17-2009, 03:43 PM	#1
valvalis Junior Member Join Date: Aug 2009 Posts: 2	Monitor Remains Black Just installed the new 1.5b1 driver. The system failed the first time (threw an error about improper registration of the kext). I uninstalled and reinstalled and it installed the second time without any errors. The monitor / DisplayLink adapter is still unrecognized. I'm using an EVGA UV+ (UV16) adapter.

08-17-2009, 04:40 PM	#4
raminf Junior Member Join Date: Aug 2009 Posts: 4	Same problem here & issue with diag tool Running 10A432 Snow Leopard. Installed driver and rebooted. Screen remains dark. As to the requested DisplayLink Information.zip file, I'm happy to send it directly to tech support but 've got an issue with posting it to a public forum. After running the utility (in "Basic" mode) and looking at the System Profile.txt output file it generates it appears that it includes a lot of information that can be potential security risks. There's a full list of network connections, router info, profile settings that include "Password ID" values, whether ports require authentication or not, etc. Not sure why this all needs to be included in the display information (or posted up here). In "Full Mode" there's even more data that people may not want to splatter over the Interwebs -- like apps installed, shared folders, etc. Suggest you modify the diagnostic tool to not include such data, especially public IP values, MAC addresses (that can be faked to get around router security), usernames, password-related keys, UUID data, Bluetooth addresses, DHCP settings, etc. Like I said, I don't have an issue sending this privately -- especially if it helps solve the driver issue.

08-17-2009, 07:46 PM	#9
tysonedwards Junior Member Join Date: Aug 2009 Location: Salt Lake City, UT Posts: 15	Given that we are missing multiple files from the package that are essential for it's installation and the driver's successful operation, it seems as though it's a safe bet that this version of the 1.5 driver is not what DisplayLink intended to release.