Doesn't Work At All - Kext doesn't load

[skevy]

Originally Posted by raminf

Running Snow Leopard 10A432. Did as suggested by skevy and copied the two files from the 1.1.3beta to the bundle folder. Rebooted. Still didn't recognize the monitor, but now the console shows a constantly expanding (like, 10+/second) list of errors. Tried plugging directly into MBPro USB port as well as through a powered D-Link hub. No difference.

Going to uninstall it until a proper update shows up.

Here are the console messages:

8/17/09 11:37:19 AM kernel USBF: 442.199 [0x7c8c800] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 2 of hub @ location: 0xfd830000)
8/17/09 11:37:20 AM DisplayLinkUserAgent[273] (00306510.118)-[DLDistributedNotificationCenter initAs:withName:] Could not create Client object.
8/17/09 11:37:21 AM com.apple.launchd[1] (com.displaylink.usbnivolistener[500]) Exited with exit code: 1
8/17/09 11:37:21 AM com.apple.launchd[1] (com.displaylink.usbnivolistener) Throttling respawn: Will start in 5 seconds
8/17/09 11:37:21 AM DisplayLinkUserAgent[273] (00113280.118)-[DLDistributedNotificationCenter initAs:withName:] Could not create Client object.
8/17/09 11:37:22 AM DisplayLinkUserAgent[273] (00306540.118)-[DLDistributedNotificationCenter initAs:withName:] Could not create Client object.
8/17/09 11:37:23 AM DisplayLinkUserAgent[273] (00113280.118)-[DLDistributedNotificationCenter initAs:withName:] Could not create Client object.
8/17/09 11:37:24 AM DisplayLinkUserAgent[273] (00306520.118)-[DLDistributedNotificationCenter initAs:withName:] Could not create Client object.
8/17/09 11:37:25 AM DisplayLinkUserAgent[273] (00306510.118)-[DLDistributedNotificationCenter initAs:withName:] Could not create Client object.
8/17/09 11:37:26 AM com.apple.launchd[1] (com.displaylink.usbnivolistener[502]) Exited with exit code: 1

[snip]

Are you running in x86_64 mode? I got these errors when I wasn't running in 32 bit.

[raminf]

Just double-checked. My 2.5-yo MBPro is a Core2Duo but the Model ID is MacBookPro2,1. I believe it needs to be at least MacBookPro4,1 to run in 64-bit mode. Doing a 'uname -m' returns 'i386' instead of 'x86_64.' Also 'About This Mac' under Sofware shows 64-bit Kernel and Extensions=No.

So I'm guessing Snow Leopard on this machine is pretty much stuck in 32-bit ice-age

Not sure what else to do to get DisplayLink drivers going. Any suggestions appreciated.

[skevy]

I think the best solution would be to release a version of this driver that has all the files included. You would think they would have installed this driver on a test machine and gave it a quick run through sometime between August 7th (when the beta program was announced) and 17th. I realize we're all fairly tech savvy users here - this being a beta and all. But to have to hack the driver to get it to work at all??? That seems kind of ridiculous to me.

[Admin]

Originally Posted by raminf

Just double-checked. My 2.5-yo MBPro is a Core2Duo but the Model ID is MacBookPro2,1. I believe it needs to be at least MacBookPro4,1 to run in 64-bit mode. Doing a 'uname -m' returns 'i386' instead of 'x86_64.' Also 'About This Mac' under Sofware shows 64-bit Kernel and Extensions=No.

So I'm guessing Snow Leopard on this machine is pretty much stuck in 32-bit ice-age

Not sure what else to do to get DisplayLink drivers going. Any suggestions appreciated.

Yes, I'm afraid that our current beta driver does not support 64-bit versions of Snow Leopard. At present we are focussing on developing a 32-bit solution, with a view to developing a 64-bit version later in the year.

Originally Posted by skevy

I think the best solution would be to release a version of this driver that has all the files included. You would think they would have installed this driver on a test machine and gave it a quick run through sometime between August 7th (when the beta program was announced) and 17th. I realize we're all fairly tech savvy users here - this being a beta and all. But to have to hack the driver to get it to work at all??? That seems kind of ridiculous to me.

Yes we agree that although this is a beta program, having to hack the driver together is hardly acceptable! This release did go through some testing, and no install issues were observed, however a last minute change to the release triggered this problem. We have investigated people's feedback and now released a new beta driver that resolves this install issue, the driver (1.5b2) can be found here. Once again apologies for any inconvenience that was caused by the original release.