Ah, ok. I thought that DisplayLink is just an option and you could alternatively use HDMI.
Since the “udlfb” driver for DisplayLink uses framebuffer fb1 you would have to edit “/usr/share/X11/xorg.conf.d/99-fbturbo.conf”:
sudo nano /usr/share/X11/xorg.conf.d/99-fbturbo.conf
and change
Option "fbdev" "/dev/fb0"
to
Option "fbdev" "/dev/fb1"
This didn’t work.
Where do I put all of this stuff that normally goes into /etc/X11/xorg.conf. This is what I did on my Linux box.
Section “Device”
Identifier “FBDEV 0”
Driver “fbdev”
Option “fbdev” “/dev/fb0”
EndSection
Section “Device”
Identifier “FBDEV 1”
Driver “fbdev”
Option “fbdev” “/dev/fb1”
EndSection
Section “Screen”
Identifier “HDMI”
Device “FBDEV 0”
Monitor “Monitor name 0”
EndSection
Section “Screen”
Identifier “UGA”
Device “FBDEV 1”
Monitor “Monitor name 1”
EndSection
Section “ServerLayout”
Identifier “Default Layout”
Screen 0 “HDMI”
Screen 1 “UGA” LeftOf “HDMI”
EndSection
Before adding / changing more files, please post the result of
cat /var/log/Xorg.0.log
Correct me if I’m wrong, but that seems to be a configuration for two displays (HDMI and DisplayLink). Do you strive for two monitors on your Pi, too?
This gives an option for both types.
Any chance you can provide the requested log?
According to MIMO, using the RPi 3 with USB Displays is said to be much easier as the required Kernel components are said to be part of the stock build. I did find that plugging in a Mimo Display into the RPI 3 did turn screen solid green. They say this is a sign that the display is recognized, and the driver is loaded. The green screen says that the Pi doesn’t know what to display on it.
The two frame buffers fb0 and fb1 are present in /dev. fb0 is said to be for the onboard RPI display port and when I plug in the MIMO fb1 appears indicating the USB display.
I tried various configurations including: /etc/X11/xorg.conf.d/60-plugable.conf and /etc/X11/xorg.conf. Neigher worked. The screen is still not displaying volumio, just green.
Section “Device”
Identifier “uga”
driver “fbdev”
Option “fbdev” “/dev/fb0”
Option “ShadowFB” “off”
EndSection
Section “Monitor”
Identifier “monitor”
EndSection
Section “Screen”
Identifier “screen”
Device “uga”
Monitor “monitor”
EndSection
Section “ServerLayout”
Identifier “default”
Screen 0 “screen” 0 0
EndSection
How to set (options udlfb fb_defio=1)
Is volumio running straight X?
Thanks.
Please: Post the requested log…, i.e. the result of
cat /var/log/Xorg.0.log
Has the Touch Display plugin been started?
volumio@volumio:~$ cat /var/log/Xorg.0.log
cat: /var/log/Xorg.0.log: No such file or directory
albumart.log boot.log btmp mpd.log wtmp
Touch Display is installed
Please start the plugin and post the result of
systemctl status -l volumio-kiosk.service
Touch Display
Failed: start volumio-kiosk.service: Error: Command failed: /usr/bin/sudo /bin/systemctl start volumio-kiosk.service Failed to start volumio-kiosk.service: Unit volumio-kiosk.service failed to load: No such file or directory.
Try uninstalling and reinstalling the plugin, please.
just did that. It says its active.
[ 38.295] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 38.295] (II) no primary bus or device found
[ 38.297] (II) LoadModule: “glx”
[ 38.307] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 38.381] (II) Module glx: vendor=“X.Org Foundation”
[ 38.381] compiled for 1.18.4, module version = 1.0.0
[ 38.381] ABI class: X.Org Server Extension, version 9.0
[ 38.381] (==) AIGLX enabled
[ 38.381] (II) LoadModule: “fbdev”
[ 38.384] (WW) Warning, couldn’t open module fbdev
[ 38.384] (II) UnloadModule: “fbdev”
[ 38.384] (II) Unloading fbdev
[ 38.384] (EE) Failed to load module “fbdev” (module does not exist, 0)
[ 38.384] (EE) No drivers available.
[ 38.384] (EE)
Fatal server error:
[ 38.384] (EE) no screens found(EE)
PRETTY_NAME=“Raspbian GNU/Linux 8 (jessie)”
NAME=“Raspbian GNU/Linux”
VERSION_ID=“8”
VERSION=“8 (jessie)”
ID=raspbian
ID_LIKE=debian
HOME_URL=…
SUPPORT_URL=…
BUG_REPORT_URL=…
VOLUMIO_BUILD_VERSION=“dd2a4339faaeb892c7f467e7dc8d424aefb0bd03”
VOLUMIO_FE_VERSION=“958dedc0edff114f244fa9acc70cf53089d9e5ae”
VOLUMIO_BE_VERSION=“307f91893fca011201acba9973e1c41bd3a0ad5d”
VOLUMIO_ARCH=“arm”
VOLUMIO_VARIANT=“volumio”
VOLUMIO_TEST=“FALSE”
VOLUMIO_BUILD_DATE=“Thu Sep 30 22:42:09 CEST 2021”
VOLUMIO_VERSION=“2.915”
VOLUMIO_HARDWARE=“pi”
VOLUMIO_HASH=“02ee61bb422c79b6e5c0b6d1847a78d9”
Please post the output of
ls -al /usr/lib/xorg/modules/drivers
ls -al /etc/X11/xorg.conf.d
ls -al /usr/share/X11/xorg.conf.d
ls -al /etc/X11
ls -al /dev/fb*
And also give
cat /var/log/Xorg.0.log
another try 
One thought comes to mind: Are one or all of the .conf files you mentioned still present in your system?
If so, I guess they probably contain driver "fbdev" in Section "Device" (in accordance with post 14). Try changing the driver from “fbdev” to “fbturbo”.
I would also assume that Option "fbdev" "/dev/fb0" has to be Option "fbdev" "/dev/fb1" when using DisplayLink.
/usr/lib/xorg/modules/drivers
-rw-r–r-- 1 root root 956 Dec 7 2016 fbturbo_drv.la
-rw-r–r-- 1 root root 46172 Dec 7 2016 fbturbo_drv.so
-rw-r–r-- 1 root root 59956 Nov 11 2016 modesetting_drv.so
/etc/X11/xorg.conf.d
-rw-r–r-- 1 root root 316 Oct 7 20:14 95-touch_display-plugin.conf
/usr/share/X11/xorg.conf.d
-rw-r–r-- 1 root root 1350 Nov 11 2016 10-quirks.conf
-rw-r–r-- 1 root root 788 Sep 30 2016 40-libinput.conf
-rw-r–r-- 1 root root 2747 Oct 28 2016 70-wacom.conf
-rw-r–r-- 1 root root 607 Dec 7 2016 99-fbturbo.conf
/etc/X11
-rwxr-xr-x 1 root root 709 Sep 25 2013 Xreset
drwxr-xr-x 1 root root 4096 Oct 7 20:04 Xreset.d
drwxr-xr-x 1 root root 4096 Oct 7 20:04 Xresources
-rwxr-xr-x 1 root root 3517 Sep 25 2013 Xsession
drwxr-xr-x 1 root root 4096 Oct 7 20:04 Xsession.d
-rw-r–r-- 1 root root 265 Sep 25 2013 Xsession.options
-rw-r–r-- 1 root root 601 Oct 7 20:07 Xwrapper.config
drwxr-xr-x 2 root root 4096 Oct 7 20:04 app-defaults
drwxr-xr-x 6 root root 4096 Oct 7 20:03 fonts
lrwxrwxrwx 1 root root 14 Dec 6 2016 openbox → …/xdg/openbox
-rw-r–r-- 1 root root 17394 Sep 25 2013 rgb.txt
drwxr-xr-x 2 root root 4096 Oct 7 20:04 xinit
drwxr-xr-x 2 root root 4096 Jun 6 2014 xkb
drwxr-xr-x 2 root root 4096 Oct 7 20:14 xorg.conf.d
drwxr-xr-x 2 root root 4096 Oct 7 20:04 xsm
/dev/fb*
crw-rw---- 1 root video 29, 0 Sep 30 20:42 /dev/fb0
Ok, no “custom” .conf files.
If I didn’t misread post #14 “fb1” appears if the MIMO display is connected by USB. As only “fb0” is showing up in /dev now I guess the display was not connected by USB. (?)
Did you try my suggestion after you reinstalled the plugin?