Displaylink on Gentoo causes system freeze unless booting to Windows first

mlukaszek · 11-03-2016, 03:07 PM

Can you attach logs just from an attempt when it freezes? (i.e. rm -rf /var/log/displaylink/* first and then reproduce the problem)

This might be some bizarre timing issue. When you boot Windows, the firmware for the device is changed to whatever was part of the Windows driver. When you boot back to Linux, what's happening inside DLM first is making sure the firmware on a device is the one bundled with Linux driver. Since actual connection to evdi only happens after the FW is compatible, in a way this process introduces a slight delay before DLM attempts to connect to evdi, resulting in a new screen appearing, ready for use with X.

How is the DLM upstart/systemd service started on gentoo? In Ubuntu driver we ensure it's only started when X are up. Has this been properly ported to gentoo?

Cheers,
Michal

11-03-2016, 03:07 PM	#2
mlukaszek Senior Member Join Date: Feb 2010 Posts: 386	Can you attach logs just from an attempt when it freezes? (i.e. rm -rf /var/log/displaylink/* first and then reproduce the problem) This might be some bizarre timing issue. When you boot Windows, the firmware for the device is changed to whatever was part of the Windows driver. When you boot back to Linux, what's happening inside DLM first is making sure the firmware on a device is the one bundled with Linux driver. Since actual connection to evdi only happens after the FW is compatible, in a way this process introduces a slight delay before DLM attempts to connect to evdi, resulting in a new screen appearing, ready for use with X. How is the DLM upstart/systemd service started on gentoo? In Ubuntu driver we ensure it's only started when X are up. Has this been properly ported to gentoo? Cheers, Michal