stefy20026
Posts: 5
Joined: Sun Nov 20, 2016 9:27 pm

displaylink

Thu Nov 09, 2017 10:19 am

Hi, raspberry Pi 3 b i have a displaylink uga device is it possible to have hdmi and another screen working on same time?
i can run 1 hp screen from usb2hdmi (via displaylink) and i can get a console with ctrl+alt F1 etc... using another monitor lg as console, setting xorg.conf this way:

Code: Select all

Section "Device"
# USB DisplayLink video, framebuffer 1
  Identifier "uga"
  driver "fbdev"
  Option "fbdev" "/dev/fb1"
  Option "ShadowFB" "off"
EndSection

Section "Monitor"
# Secondary monitor. 1280x1024
  Identifier "HP"
EndSection

Section "Screen"
  Identifier "secondary"
  Device "uga"
  Monitor "HP"
EndSection
Bus 001 Device 006: ID 17e9:0360 DisplayLink 


what i would like to try 2 screens running X
here is description of 2 monitors, running X on notebook

Code: Select all

ls /sys/class/drm/*/edid | xargs -i{} sh -c "echo {}; parse-edid < {}"
/sys/class/drm/card1-DVI-I-1/edid
Checksum Correct

Section "Monitor"
	Identifier "HP 23xi"
	ModelName "HP 23xi"
	VendorName "HWP"
	# Monitor Manufactured week 7 of 2014
	# EDID version 1.3
	# Digital Display
	DisplaySize 510 290
	Gamma 2.20
	Option "DPMS" "true"
	Horizsync 24-94
	VertRefresh 50-76
	# Maximum pixel clock is 170MHz
	#Not giving standard mode: 1920x1080, 60Hz
	#Not giving standard mode: 1280x720, 60Hz
	#Not giving standard mode: 1280x1024, 60Hz
	#Not giving standard mode: 1440x900, 60Hz
	#Not giving standard mode: 1600x900, 60Hz
	#Not giving standard mode: 1680x1050, 60Hz
	Modeline 	"Mode 0" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync -vsync 
EndSection
/sys/class/drm/card2-DP-1/edid
Partial Read... Try again
/sys/class/drm/card2-HDMI-A-1/edid
Checksum Correct

Section "Monitor"
	Identifier "2D FHD LG TV"
	ModelName "2D FHD LG TV"
	VendorName "GSM"
	# Monitor Manufactured week 1 of 2015
	# EDID version 1.3
	# Digital Display
	DisplaySize 510 290
	Gamma 2.20
	Option "DPMS" "true"
	Horizsync 30-83
	VertRefresh 56-75
	# Maximum pixel clock is 150MHz
	#Not giving standard mode: 1152x864, 75Hz
	#Not giving standard mode: 1280x720, 60Hz
	#Not giving standard mode: 1280x800, 60Hz
	#Not giving standard mode: 1280x1024, 60Hz
	#Not giving standard mode: 1440x900, 60Hz
	#Not giving standard mode: 1400x1050, 60Hz
	#Not giving standard mode: 1600x900, 60Hz
	#Not giving standard mode: 1680x1050, 60Hz

	#Extension block found. Parsing...
	Modeline 	"Mode 16" 74.25 1280 1336 1472 1650 720 721 726 750 +hsync +vsync 
	Modeline 	"Mode 0" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync -vsync 
	Modeline 	"Mode 1" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync 
	Modeline 	"Mode 2" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
	Modeline 	"Mode 3" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace
	Modeline 	"Mode 4" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
	Modeline 	"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
	Modeline 	"Mode 6" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync
	Modeline 	"Mode 7" 74.250 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
	Modeline 	"Mode 8" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
	Modeline 	"Mode 9" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
	Modeline 	"Mode 10" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
	Modeline 	"Mode 11" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
	Modeline 	"Mode 12" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace
	Modeline 	"Mode 13" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
	Modeline 	"Mode 14" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace
	Modeline 	"Mode 15" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
	Modeline 	"Mode 17" 74.25 1920 2008 2052 2200 540 542 547 562 +hsync +vsync interlace
	Modeline 	"Mode 18" 74.25 1920 2448 2492 2640 540 542 547 562 +hsync +vsync interlace
	Modeline 	"Mode 19" 148.50 1920 1936 2492 2640 1080 1084 1089 1125 +hsync +vsync 
	Option "PreferredMode" "Mode 16"
EndSection
/sys/class/drm/card2-LVDS-1/edid
Checksum Correct
I need an xorg.conf that allow me to run both monitors, if is possible.

thanks you!

stefy20026
Posts: 5
Joined: Sun Nov 20, 2016 9:27 pm

Re: displaylink

Sat Nov 11, 2017 11:40 am

All tutorial talk about Device fbturbo but i get a green screen only using fbdev

Code: Select all

Section "Device"
# RPi builtin video, framebuffer 0
  Identifier "rpi"
  driver "fbdev"
  Option "fbdev" "/dev/fb0"
  Option "SwapbuffersWait" "True"
  Option "ShadowFB" "off"
EndSection

Section "Device"
# USB DisplayLink video, framebuffer 1
  Identifier "uga"
  driver "fbdev"
  Option "fbdev" "/dev/fb1"
  Option "ShadowFB" "off"
EndSection

Section "ServerLayout"
  Identifier "HDMI"
  Screen 0 "ScreenHDMI"
EndSection

Section "ServerLayout"
  Identifier "UGA"
  Screen 0 "ScreenUGA"
EndSection

Section "Screen"
  Identifier "ScreenHDMI"
  Device "rpi"
  Monitor "LG"
EndSection

Section "Screen"
  Identifier "ScreenUGA"
  Device "uga"
  Monitor "HP"
EndSection


Section "Monitor"
# Primary monitor
  Identifier "LG"
EndSection

Section "Monitor"
  Identifier "HP"
EndSection
i can have 2 screen running only using mpv movie.mp4 on 1 screen and in the other i run a normal

Code: Select all

 startx -- -layout UGA 
is the way i run the displaylink screen1, now thanks to h264_omx acceleration i can watch movie and browse with firefox (maybe is a bit heavy) on the screen0 im writing, because mpv works without X runnin .

i wonder if i can get some tip about why using fbturbo i cant get a secondary screen to run.

This is the Xorg.0.log

Code: Select all

[    32.637] 
X.Org X Server 1.19.5
Release Date: 2017-10-12
[    32.637] X Protocol Version 11, Revision 0
[    32.638] Build Operating System: Linux 4.10.0-1-ARCH armv7l 
[    32.638] Current Operating System: Linux alarmpi 4.9.59-1-ARCH #1 SMP Sun Oct 29 20:24:30 UTC 2017 armv7l
[    32.638] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  root=/dev/mmcblk0p2 rw rootwait console=ttyS0,115200 console=tty1 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=ttyS0,115200 elevator=noop cma=256M
[    32.639] Build Date: 13 October 2017  02:06:59PM
[    32.639]  
[    32.639] Current version of pixman: 0.34.0
[    32.640] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    32.640] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    32.641] (==) Log file: "/home/alarm/.local/share/xorg/Xorg.0.log", Time: Sat Nov 11 09:43:36 2017
[    32.645] (==) Using config file: "/etc/X11/xorg.conf"
[    32.645] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    32.646] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    32.657] (==) ServerLayout "default"
[    32.657] (**) |-->Screen "screen" (0)
[    32.657] (**) |   |-->Monitor "LG"
[    32.658] (**) |   |-->Device "vga"
[    32.658] (**) |-->Screen "screen1" (1)
[    32.658] (**) |   |-->Monitor "HP"
[    32.658] (**) |   |-->Device "uga"
[    32.658] (EE) Screen primary doesn't exist: deleting placement
[    32.658] (==) Automatically adding devices
[    32.658] (==) Automatically enabling devices
[    32.659] (==) Automatically adding GPU devices
[    32.659] (==) Automatically binding GPU devices
[    32.659] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    32.675] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[    32.675] 	Entry deleted from font path.
[    32.676] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[    32.676] 	Entry deleted from font path.
[    32.676] 	(Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[    32.677] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[    32.677] 	Entry deleted from font path.
[    32.677] 	(Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[    32.677] (==) FontPath set to:
	/usr/share/fonts/misc/,
	/usr/share/fonts/TTF/,
	/usr/share/fonts/OTF/
[    32.677] (==) ModulePath set to "/usr/lib/xorg/modules"
[    32.677] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    32.680] (II) Loader magic: 0x69ff00
[    32.680] (II) Module ABI versions:
[    32.680] 	X.Org ANSI C Emulation: 0.4
[    32.680] 	X.Org Video Driver: 23.0
[    32.680] 	X.Org XInput driver : 24.1
[    32.680] 	X.Org Server Extension : 10.0
[    32.683] (++) using VT number 1

[    32.684] (--) controlling tty is VT number 1, auto-enabling KeepTty
[    32.693] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[    32.696] (II) xfree86: Adding drm device (/dev/dri/card0)
[    32.699] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
[    32.700] (II) no primary bus or device found
[    32.700] 	falling back to /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1:1.0/drm/card0
[    32.701] (II) LoadModule: "glx"
[    32.709] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    32.780] (II) Module glx: vendor="X.Org Foundation"
[    32.780] 	compiled for 1.19.5, module version = 1.0.0
[    32.780] 	ABI class: X.Org Server Extension, version 10.0
[    32.780] (II) LoadModule: "fbdev"
[    32.782] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    32.785] (II) Module fbdev: vendor="X.Org Foundation"
[    32.785] 	compiled for 1.19.3, module version = 0.4.4
[    32.785] 	Module class: X.Org Video Driver
[    32.785] 	ABI class: X.Org Video Driver, version 23.0
[    32.785] (II) FBDEV: driver for framebuffer: fbdev
[    32.785] (WW) Falling back to old probe method for fbdev
[    32.785] (II) Loading sub module "fbdevhw"
[    32.785] (II) LoadModule: "fbdevhw"
[    32.786] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    32.789] (II) Module fbdevhw: vendor="X.Org Foundation"
[    32.789] 	compiled for 1.19.5, module version = 0.0.2
[    32.789] 	ABI class: X.Org Video Driver, version 23.0
[    32.789] (II) FBDEV(0): using /dev/fb0
[    32.789] (II) FBDEV(1): using /dev/fb1
[    32.789] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[    32.790] (II) FBDEV(0): Creating default Display subsection in Screen section
	"screen" for depth/fbbpp 24/32
[    32.790] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[    32.790] (==) FBDEV(0): RGB weight 888
[    32.790] (==) FBDEV(0): Default visual is TrueColor
[    32.790] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[    32.790] (II) FBDEV(0): hardware: BCM2708 FB (video memory: 8100kB)
[    32.790] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[    32.790] (**) FBDEV(0): Option "ShadowFB" "off"
[    32.790] (**) FBDEV(0): Option "fbdev" "/dev/fb0"
[    32.790] (II) FBDEV(0): checking modes against framebuffer device...
[    32.790] (II) FBDEV(0): checking modes against monitor...
[    32.790] (--) FBDEV(0): Virtual size is 1920x1080 (pitch 1920)
[    32.791] (**) FBDEV(0):  Built-in mode "current"
[    32.791] (==) FBDEV(0): DPI set to (96, 96)
[    32.791] (II) Loading sub module "fb"
[    32.791] (II) LoadModule: "fb"
[    32.791] (II) Loading /usr/lib/xorg/modules/libfb.so
[    32.797] (II) Module fb: vendor="X.Org Foundation"
[    32.797] 	compiled for 1.19.5, module version = 1.0.0
[    32.797] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    32.798] (II) FBDEV(1): Creating default Display subsection in Screen section
	"screen1" for depth/fbbpp 16/16
[    32.798] (==) FBDEV(1): Depth 16, (==) framebuffer bpp 16
[    32.798] (==) FBDEV(1): RGB weight 565
[    32.798] (==) FBDEV(1): Default visual is TrueColor
[    32.798] (==) FBDEV(1): Using gamma correction (1.0, 1.0, 1.0)
[    32.798] (II) FBDEV(1): hardware: udldrmfb (video memory: 4052kB)
[    32.798] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[    32.798] (**) FBDEV(1): Option "ShadowFB" "off"
[    32.798] (**) FBDEV(1): Option "fbdev" "/dev/fb1"
[    32.798] (II) FBDEV(1): checking modes against framebuffer device...
[    32.798] (II) FBDEV(1): checking modes against monitor...
[    32.798] (--) FBDEV(1): Virtual size is 1920x1080 (pitch 1920)
[    32.798] (**) FBDEV(1):  Built-in mode "current"
[    32.798] (==) FBDEV(1): DPI set to (96, 96)
[    32.798] (II) Loading sub module "fb"
[    32.798] (II) LoadModule: "fb"
[    32.799] (II) Loading /usr/lib/xorg/modules/libfb.so
[    32.799] (II) Module fb: vendor="X.Org Foundation"
[    32.799] 	compiled for 1.19.5, module version = 1.0.0
[    32.799] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    32.799] (==) Depth 24 pixmap format is 32 bpp
[    32.810] (==) FBDEV(0): Backing store enabled
[    32.817] (==) FBDEV(0): DPMS enabled
[    32.817] (==) RandR enabled
[    32.818] (==) FBDEV(1): Backing store enabled
[    32.818] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.818] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.818] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.818] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.818] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.818] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.818] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.818] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.818] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.819] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.820] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (EE) FBDEV(1): FBIOPUTCMAP: Device or resource busy
[    32.821] (==) FBDEV(1): DPMS enabled
[    32.821] (==) RandR enabled
[    32.866] (II) AIGLX: Screen 0 is not DRI2 capable
[    32.866] (EE) AIGLX: reverting to software rendering
[    34.025] (II) IGLX: enabled GLX_MESA_copy_sub_buffer
[    34.030] (II) IGLX: Loaded and initialized swrast
[    34.030] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    34.030] (II) AIGLX: Screen 1 is not DRI2 capable
[    34.030] (EE) AIGLX: reverting to software rendering
[    34.038] (II) IGLX: enabled GLX_MESA_copy_sub_buffer
[    34.042] (II) IGLX: Loaded and initialized swrast
[    34.042] (II) GLX: Initialized DRISWRAST GL provider for screen 1

Geeviz
Posts: 77
Joined: Tue May 28, 2013 7:40 pm
Location: Holland, Groningen

Re: displaylink

Thu Nov 28, 2019 10:17 am

that is funny.

I am struggling with two screens and cannot get it to work yet... my xorg looks like below. when i delete the xorg the normal standard hdmi screen pops on... with xorg only the 7 inch usb touch works... i want to have (mirrored, or extended) screens on both..

Section "Device"
Identifier "DisplayLinkDevice"
driver "fbdev"
Option "fbdev" "/dev/fb1"
Option "ShadowFB" "off"
EndSection

Section "Monitor"
Identifier "monitor"
Option "DPMS"
EndSection

Section "Screen"
Identifier "screen"
Device "DisplayLinkDevice"
Monitor "monitor"
EndSection

Section "ServerLayout"
Identifier "default"
Screen 0 "screen" 0 0
screen 1 "bigscreen" RightOf "screen"
InputDevice "touchscreen" "CorePointer"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
EndSection

Section "InputDevice"
Identifier "touchscreen"
Driver "evdev"
Option "Device" "/dev/input/by-id/usb-e2i_Technology__Inc._USB_Touchpanel"
Option "DeviceName" "touchscreen"
Option "ReportingMode" "Raw"
Option "SendCoreEvents" "On"
Option "Calibrate" "1"
Option "MinX" "1754"
Option "MaxX" "64067"
Option "MinY" "62314"
Option "MaxY" "1240"
Option "SwapAxes" "1"
Option "TransformationMatrix" "1 0 0 0 -1 1 0 0 1"
EndSection

Section "InputClass"
Identifier "calibration"
MatchProduct "e2i Technology, Inc. USB Touchpanel"
Option "Calibration" "1754 64067 62314 1240"
Option "SwapAxes" "1"
Option "InvertY" "true"
Option "TransformationMatrix" "1 0 0 0 -1 1 0 0 1"
EndSection

Section "Device"
Identifier "default"
driver "Modesetting"
Option "kmsdev" "/dev/dri/card0"
EndSection

Section "Monitor"
Identifier "default"
EndSection

Section "Screen"
Identifier "bigscreen"
device "default"
monitor "default"
EndSection
I am in the house :lol:

hippy
Posts: 6562
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: displaylink

Thu Nov 28, 2019 10:46 am

I got DisplayLink plus HDMI working on my 3B using the guide at -

http://multi-seat.com/raspbian-dual-monitors

Code: Select all

sudo apt-get install libxinerama-dev   if not already installed
fbset -i -v -fb /dev/fb0               this and ...
fbset -i -v -fb /dev/fb1               to find lowest colour depth
sudo nano /boot/config.txt             to force colour depth
sudo nano /etc/X11/xorg.conf           using example at link
sudo reboot                            make the magic happen
My /etc/X11/xorg.conf was -

Code: Select all

Section "Device"
Identifier "Raspberry Pi BCM2708"
Driver "fbturbo"
Option "fbdev" "/dev/fb0"
Option "ShadowFB" "off"
EndSection

Section "Device"
Identifier "displaylink"
Driver "fbturbo"
Option "fbdev" "/dev/fb1"
Option "ShadowFB" "off"
EndSection

Section "Screen"
Identifier "screen0"
Device "Raspberry Pi BCM2708"
EndSection

Section "Screen"
Identifier "screen1"
Device "displaylink"
EndSection

Section "ServerLayout"
Identifier "default"
Screen 0 "screen0" 0 0
Screen 1 "screen1" RightOf "screen0"
Option "Xinerama" "on"
EndSection
Haven't had it set up that way for a while now and it may have changed for Buster.

Geeviz
Posts: 77
Joined: Tue May 28, 2013 7:40 pm
Location: Holland, Groningen

Re: displaylink

Thu Nov 28, 2019 6:46 pm

After the last tweak (last post above this) i have a blank screen at both... so net even desktop environment yet..
I am in the house :lol:

hippy
Posts: 6562
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: displaylink

Fri Nov 29, 2019 12:05 am

Geeviz wrote:
Thu Nov 28, 2019 6:46 pm
After the last tweak (last post above this) i have a blank screen at both... so net even desktop environment yet..
Same here I am afraid. Sorry about that; I guess it's a bug with Buster.

With the above setup on a 3B, which used to work for me, on booting I see the scrolling boot text on the main HDMI monitor, the DisplayLink monitor is showing green as expected. As soon as it switches to desktop the HDMI goes black with an occasional flash of mouse cursor, the DisplayLink display flashes between green and black.

Both "dtoverlay=vc4-fkms-v3d" and "dtoverlay=vc4-kms-v3d" commented out in config.txt.

Geeviz
Posts: 77
Joined: Tue May 28, 2013 7:40 pm
Location: Holland, Groningen

Re: displaylink

Fri Nov 29, 2019 4:12 pm

It is somehow possible, but how?

there are several pages and workarounds but mostly either the linuxversions are different, or it is not for usb displaylink..
maybe this is possible:

1) a script to turn off / bypass xorg .conf when hdmi is connected and the usb screen is not connected

2) vise versa. when usb is connected that it runs xorg.conf

3) dual screen in xorg.conf to have both screens on.
I am in the house :lol:

hippy
Posts: 6562
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: displaylink

Fri Nov 29, 2019 7:25 pm

Geeviz wrote:
Fri Nov 29, 2019 4:12 pm
It is somehow possible, but how?
No idea. Your early experiments seemed to deliver somewhat better results than I am getting with a configuration which previously worked. Until whatever is broken gets fixed I have no idea where we stand on getting DisplayLink to work as desired. I wouldn't waste my time trying to make it work when something seems broken.

Return to “Beginners”