xfce crashes with xrandr command

Szymon · 02-02-2016, 10:23 AM

Hi arcasys,

I've checked the logs you've uploaded. Apparently, neither EVDI kernel module nor user mode daemon DisplayLinkManager shows any signs of presence. Could you check if you are able to successfully load the kernel module:

sudo insmod evdi

If not, it would be useful if you upload an output from the installer which may require reinstall:

sudo ./displaylink-driver-1.0.335.run uninstall
sudo ./displaylink-driver-1.0.335.run install

Regards,
Szymon

mlukaszek · 02-02-2016, 04:41 PM

I see this device is actually using in-box UDL kernel module - so, EVDI and DisplayLinkManager are not required to support those devices. What you see is generic xfce crash caused by screen layout change, most likely.
I don't see signs of failures in kernel trace, UDL looks fine. It would be interesting to see what was sent to Canonical when xfce crashed - you could peek into /var/crash and check if apport saved a crash file there. This can give you some hints.

Cheers,
Michal

arcasys · 02-03-2016, 11:58 PM

Unfortunately, I had the machine with the display for evaluation and had to return it to HP. However, they will contact me and I might get another machine for followup.
mlukaszek is right. The DisplayLink driver is not required for this type of display. Nonetheless I gave it a try before and the only effect was that the display showed up twice in the display configuration. The glitches with xfce and probably the framebuffer driver (my suspect) werre the same: no output and crashes.
HP is telling us it would work flawlessly with OpenSuse. I'll let you know ...

Thanks so far and regards,
Hans

02-02-2016, 10:23 AM	#1
Szymon DisplayLink Tech Support Join Date: Feb 2010 Posts: 270	Hi arcasys, I've checked the logs you've uploaded. Apparently, neither EVDI kernel module nor user mode daemon DisplayLinkManager shows any signs of presence. Could you check if you are able to successfully load the kernel module: sudo insmod evdi If not, it would be useful if you upload an output from the installer which may require reinstall: sudo ./displaylink-driver-1.0.335.run uninstall sudo ./displaylink-driver-1.0.335.run install Regards, Szymon Last edited by Szymon; 02-02-2016 at 10:24 AM. Reason: Post formatting

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

02-02-2016, 04:41 PM	#2
mlukaszek Senior Member Join Date: Feb 2010 Posts: 386	I see this device is actually using in-box UDL kernel module - so, EVDI and DisplayLinkManager are not required to support those devices. What you see is generic xfce crash caused by screen layout change, most likely. I don't see signs of failures in kernel trace, UDL looks fine. It would be interesting to see what was sent to Canonical when xfce crashed - you could peek into /var/crash and check if apport saved a crash file there. This can give you some hints. Cheers, Michal

02-03-2016, 11:58 PM	#3
arcasys Junior Member Join Date: Feb 2016 Posts: 2	Unfortunately, I had the machine with the display for evaluation and had to return it to HP. However, they will contact me and I might get another machine for followup. mlukaszek is right. The DisplayLink driver is not required for this type of display. Nonetheless I gave it a try before and the only effect was that the display showed up twice in the display configuration. The glitches with xfce and probably the framebuffer driver (my suspect) werre the same: no output and crashes. HP is telling us it would work flawlessly with OpenSuse. I'll let you know ... Thanks so far and regards, Hans