Quote:
Originally Posted by cjellick
Same here! Except I'm using the D3100. The dock works for non-display peripherals like mouse and keyboard, but if I have a monitor attached, I see the same thing: primary display flashes like its trying to detect displays but then the external monitor doesn't appear and the primary display continues to flicker periodically.
HALP!
|
We are apparently seeing the pathology that is described in the thread starter entitled [Updated] DisplayLink Ubuntu driver with GPUs using modesetting X driver.
https://www.displaylink.org/forum/sh...ad.php?t=65364
I unloaded the new Displaylink driver that I had previously installed. I then fixed a bunch of problems associated with upgrading from 17.04 to 17.10. (These problems were specific to my development environment and probably of no interest to people in this forum. I probably did not have to unload the Displaylink driver, but I worry about interactions of new software especially when the new software is not working correctly. Uninstalling is easy enough.
Code:
sudo displaylink-installer uninstall
Then I rebooted because uninstall does not complete until there is a reboot.)
I then followed the instructions on the following web page.
http://support.displaylink.com/knowl...ticles/1181623
I created the file 20-displaylink.conf in the directory /usr/share/X11/xorg.conf.d/.
Because I prefer to use the current X software in so far as I can, I entered the 2nd workaround into the aforementioned configuration file.
Code:
Section "Device"
Identifier "DisplayLink"
Driver "modesetting"
Option "PageFlip" "false"
EndSection
The I rebooted just to make sure that my machine worked with the above configuration.
I am choosing vmlinuz-4.10.0-37-generic when I boot. The first time I tried to install the new Displaylink driver, I was unable to install it when I was running vmlinuz-4.13.0-16-lowlatency. In order to be able to chose the kernel, I updated the grub configuration by means of the /etc/default/grub file which I have included below. (I should note that when I first upgraded I had some difficulty in logging-in and had to experiment with the various login settings that are available in the login window (Ubuntu on Xorg, Unity, Window Maker). This problem may have resulted from idiosyncrasies in my development environment. The first time I tried to login to the upgraded system, there were four choices in the login settings: Ubuntu, Ubuntu on Xorg, Unity, and Window Maker. The Ubuntu choice seems to appear and disappear according to logic that I don't understand yet. I have had problems logging in with the Ubuntu login setting.)
The generic kernel worked with the new X configuration, I logged in, and installed the new Displaylink driver. The external HannStar display came on, but it was not primary. I had to experiment with settings to make the external display usable for my needs.
In 17.04 I could only enter the Display settings subsystem by first choosing change background. In 17.10 the whole settings subsystem has been changed, and I had to experiment with devices->displays settings and with Dock settings to make my external display behave acceptably.
The I rebooted, and my machine works with two displays. I am not completely happy because I am finicky and was accustomed to a particular 17.04 setup that no longer seems achievable or requires some more work to achieve.
The release notes below describes the newly redesigned display settings.
https://help.gnome.org/misc/release-notes/3.26/
Scaling configuration seems to work in the display settings if I rescale both displays.
The new display settings seem only to work properly when I chose the Ubuntu on Xorg login setting.
Unity and Window Maker don't seem to understand the new display settings configuration.
As far as I can tell so far, after the system has been upgraded to 17.10, the only way to logout of a session when using Ubuntu on Xorg is typing logout in the Activities entry panel. The Activities entry panel gives the ability to add a logout to the top panel. I installed the button and have tried using it to logout. After I have logged out by using the logout button, I have found the display subsystem can become confused. I can get it to reset itself to sanity by removing the USB3 cable and then plugging it back into the laptop.
-----------------------------------------------------------------
For those who have not booted a configuration that allows choice of kernel, I used the grub setup below for /etc/default/grub.
You probably only have to worry about the values of GRUB_HIDDEN_TIMEOUT_QUIET, GRUB_TIMEOUT, and GRUB_DEFAULT.
Follow the instructions below to change your own grub configuration.
/etc/default/grub
https://www.howtogeek.com/196655/how...ders-settings/
Code:
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=-1
#GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
GRUB_DISABLE_OS_PROBER=true