Rpi 4 and two monitors

[bhepler]

@sdetweil - I don’t know if that capability is in the Raspi display drivers. It’s always going to see the two monitors as two separate devices with unique desktops. If you click on the Identify button, it should show you a different number on each monitor.

The only thing I can think of that would treat two monitors as a single continuous desktop is the AMD Eyefinity tech.

[NathTheDude]

Thanks @sdetweil and @bhepler , could you point me in the direction of how I would display a seperate instance of MM each monitor? I know this would mean I would need to update/maintain two different MM’s but maybe that is a better option if I want to add various modules?

[sdetweil]

@bhepler said in Rpi 4 and two monitors:

I don’t know if that capability is in the Raspi display drivers. It’s always going to see the two monitors as two separate devices with unique desktops. If you click on the Identify button, it should show you a different number on each monitor.

well, that is stupid sh… , in this day and age you should be able to config the thing like u want…

I booted ubuntu on my desktop with has two displays and it made one big desktop by default…
can’t understand why raspi should be so dumb

[NathTheDude]

does this help

---

pi@MagicMirrors:~ $ tvservice --list
2 attached device(s), display ID’s are :
Display Number 2, type HDMI 0
Display Number 7, type HDMI 1
pi@MagicMirrors:~ $

[sdetweil]

@NathTheDude MagicMirror startup in the run-start.sh file sets DISPLAY=:0 for the primary display
I would guess that the second display is :1

so, do
export DISPLAY=:1
then npm start

see if it comes up on the second display

[NathTheDude]

@sdetweil na, no joy. I did try this yesterday also but was not sure I was looking in the right place. For the sake of it I tried using numbers 0 to 9, all with the same result. This for example:

npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /home/pi/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2020-02-04T21_33_32_894Z-debug.log

However if I reboot the RPI with run-start having the different value it will still display the MM on the first screen, this made me think that this script was not being used at the startup as I would expect it to fail and not display the MM - perhaps I am wrong.

[bhepler]

I wonder if we’re looking in the wrong place? Perhaps it’s how the MM process is calling Electron that determines where on the desktop the app appears.

[sdetweil]

@NathTheDude said in Rpi 4 and two monitors:

npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /home/pi/package.json
npm ERR! errno -2

you are doing npm start in the root, not in the MagicMirror folder…

[sdetweil]

@bhepler that is run-start.sh

~/MagicMirror/package.json

{
  "name": "magicmirror",
  "version": "2.10.1",
  "description": "The open source modular smart mirror platform.",
  "main": "js/electron.js",
  "scripts": {
    "start": "./run-start.sh",     // < ------   when u do npm start this happens

[sdetweil]

@NathTheDude run-start.sh is in the MagicMirror folder

actually the pm2 only on the 1st screen is understandable
as the script used by pm2 is installers/mm.sh

which does

DISPLAY=:0 npm start

and run-start does

# if DISPLAY is not set then set it
if [ -z "$DISPLAY" ]; then #If not set DISPLAY is SSH remote or tty
	export DISPLAY=:0 # Set by default display
fi

so I would just set export DISPLAY=:0
and the execute run-start.sh