PDA

View Full Version : "Manufacturing Test Mode" After 2.5 driver update


David_Mac_User
02-02-2016, 07:00 PM
I've been using a Sabrent USB-3DV since June 2014 with my macbook pro and recently upgraded the OS from 10.9 to 10.11. After upgrading the OS, I downloaded and installed the 2.5 Driver from displaylink to get 10.11 support. After rebooting the mac failed to recognize the USB display.
Digging into System Information, the adapter now shows as
Manufacturing Test Mode:

Product ID: 0xc300
Vendor ID: 0x17e9 (DisplayLink (UK) Ltd.)
Version: 0.01
Serial Number: 00000000-000000
Speed: Up to 480 Mb/sec
Manufacturer: DisplayLink
Location ID: 0x14100000 / 9
Current Available (mA): 1000
Current Required (mA): 2
Extra Operating Current (mA): 0


I'm not sure how to recover the device. Looks like the firmware update bricked it...

Any suggestions?

Carlo
02-03-2016, 08:57 AM
Hi,

The device enumerates but it is stuck in recovery mode.

Before trying anything can you please follow the instructions in http://support.displaylink.com/knowledgebase/articles/755301-how-to-report-mac-os-x-issues-to-displaylink and send us the debug information?
It would be really useful to us.

Have you already tried installing a different version of the drivers? It's possible that the FW upgrade process would unstuck with an intermediate step. You could install 2.4 for example, connect the device and if everything is fine try 2.5 again.
Please make sure to use the 2.5 final version (2.5 (68993)).

Kind regards,
Carlo

David_Mac_User
02-12-2016, 07:55 PM
I tried downgrading to 2.4 before upgrading to 2.5. It didn't seem to have an effect.

I've attached logs from 2.4 and 2.5 that hopefully will help out.

Carlo
02-16-2016, 09:06 AM
I tried downgrading to 2.4 before upgrading to 2.5. It didn't seem to have an effect.

I've attached logs from 2.4 and 2.5 that hopefully will help out.

Thank you,

It looks tricky, something we haven't seen before. Needs more investigation. Will be back as soon as I have news.

Best regards,
Carlo

Carlo
03-02-2016, 02:15 PM
Hi David,

We could not find a way to explain this kind of issue without damaged hardware being part of the problem.

Can you please open a ticket at http://support.displaylink.com mentioning this forum post? My colleagues will follow up from there.

Kind regards,
Carlo