Magic Mirror with Pi4 OS not working with Pi5

TomOMaley

That is what I get with pm2 logs --lines=20.
[TAILING] Tailing last 20 lines for [all] processes (change the value with --lines option)
/home/pi5/.pm2/pm2.log last 20 lines:
PM2 | 2025-03-17T20:06:56: PM2 log: Concurrent actions : 2
PM2 | 2025-03-17T20:06:56: PM2 log: SIGTERM timeout : 1600
PM2 | 2025-03-17T20:06:56: PM2 log: ===============================================================================
PM2 | 2025-03-17T20:06:56: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2025-03-17T20:06:56: PM2 log: App [mm:0] online
PM2 | 2025-03-17T20:57:48: PM2 log: Stopping app:mm id:0
PM2 | 2025-03-17T20:57:49: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2 | 2025-03-17T20:57:49: PM2 log: pid=1128 msg=process killed
PM2 | 2025-03-17T20:57:49: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2025-03-17T20:57:49: PM2 log: App [mm:0] online
PM2 | 2025-03-17T21:16:19: PM2 log: Stopping app:mm id:0
PM2 | 2025-03-17T21:16:19: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2 | 2025-03-17T21:16:19: PM2 log: pid=3621 msg=process killed
PM2 | 2025-03-17T21:16:19: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2025-03-17T21:16:19: PM2 log: App [mm:0] online
PM2 | 2025-03-17T21:20:13: PM2 log: Stopping app:mm id:0
PM2 | 2025-03-17T21:20:13: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2 | 2025-03-17T21:20:13: PM2 log: pid=4540 msg=process killed
PM2 | 2025-03-17T21:20:13: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2025-03-17T21:20:13: PM2 log: App [mm:0] online

/home/pi5/.pm2/logs/mm-error.log last 20 lines:
0|mm | [5164:0317/212015.666827:ERROR:gbm_wrapper.cc(74)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.666942:ERROR:gbm_wrapper.cc(257)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.667063:ERROR:gbm_wrapper.cc(74)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.667127:ERROR:gbm_wrapper.cc(257)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.669483:ERROR:gbm_wrapper.cc(74)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.671772:ERROR:gbm_wrapper.cc(257)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.672140:ERROR:gbm_wrapper.cc(74)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.672271:ERROR:gbm_wrapper.cc(257)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.672606:ERROR:gbm_wrapper.cc(74)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.672981:ERROR:gbm_wrapper.cc(257)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.673132:ERROR:gbm_wrapper.cc(74)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.674044:ERROR:gbm_wrapper.cc(257)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.674213:ERROR:gbm_wrapper.cc(74)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.674280:ERROR:gbm_wrapper.cc(257)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.674369:ERROR:gbm_wrapper.cc(74)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.674413:ERROR:gbm_wrapper.cc(257)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.674498:ERROR:gbm_wrapper.cc(74)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.674546:ERROR:gbm_wrapper.cc(257)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.674644:ERROR:gbm_wrapper.cc(74)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [5164:0317/212015.674691:ERROR:gbm_wrapper.cc(257)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)

/home/pi5/.pm2/logs/mm-out.log last 20 lines:
0|mm | [2025-03-17 21:20:15.575] [LOG] Connecting socket for: MMM-MoonPhase
0|mm | [2025-03-17 21:20:15.575] [LOG] Starting module helper: MMM-MoonPhase
0|mm | [2025-03-17 21:20:15.575] [LOG] Connecting socket for: MMM-FroniusSolar2
0|mm | [2025-03-17 21:20:15.576] [LOG] Connecting socket for: MMM-text-clock
0|mm | [2025-03-17 21:20:15.576] [LOG] Starting module helper: MMM-text-clock
0|mm | [2025-03-17 21:20:15.577] [LOG] Connecting socket for: mmm-systemtemperature
0|mm | [2025-03-17 21:20:15.579] [LOG] Starting node helper: mmm-systemtemperature
0|mm | [2025-03-17 21:20:15.580] [LOG] Sockets connected & modules started …
0|mm | [2025-03-17 21:20:15.697] [LOG] Launching application.
0|mm | [2025-03-17 21:20:16.212] [INFO] System information:
0|mm | ### SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 5 Model B Rev 1.1; virtual: false
0|mm | ### OS: platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.6.74+rpt-rpi-2712
0|mm | ### VERSIONS: electron: 32.3.3; used node: 20.18.1; installed node: 20.18.1; npm: 10.8.2; pm2: 5.4.3
0|mm | ### OTHER: timeZone: Etc/GMT-1; ELECTRON_ENABLE_GPU: undefined
0|mm | [2025-03-17 21:20:16.814] [INFO] Checking git for module: calendar_monthly
0|mm | [2025-03-17 21:20:16.829] [INFO] Checking git for module: MMM-MoonPhase
0|mm | [2025-03-17 21:20:16.839] [INFO] Checking git for module: MMM-FroniusSolar2
0|mm | [2025-03-17 21:20:16.855] [INFO] Checking git for module: MMM-text-clock
0|mm | [2025-03-17 21:20:16.863] [INFO] Checking git for module: mmm-systemtemperature
0|mm | [2025-03-17 21:20:16.871] [INFO] Checking git for module: MagicMirror

sdetweil

@TomOMaley OK, need to see more lines,

but

to get rid of some noise errors

edit the ~/MagicMirror/installers/mm.sh
and change npm start to
npm run start:wayland

then
pm2 flush
pn2 restart mm

wait a while, then pm2 logs --lines=50

TomOMaley

@sdetweil Hello Sam, in the installers/mm.sh, second line, I find: npm run start:x11 ; should I change this to npm start:wayland OR to npm run start:wayland ?
AND

then
pm2 flush
pn2 restart mm ! Is it pn2 OR pm2 ?

sdetweil

@TomOMaley

npm run start:wayland

good catch

npm start, is the only shortcut
all others require npm run

see the package.json
scripts
list for other npm run commands

TomOMaley

@sdetweil
Sorry, don not know, how to edit mm.sh. when I go to ~/MagicMirror/installers/mm.sh I get a long list but can not edit it. When I go to mm.sh via Datei Manager I get only this few lines:
#!/bin/bash

This file is still here to keep PM2 working on older installations.

cd /home/pi5/MagicMirror
DISPLAY=:0 npm start.
I have seen that in raspberry config > advanced options one can switch to wayland backends. Could that help here in any way? Sorry but my knowledge in Linux is not really exciting. Thanks for all your effort.

sdetweil

@TomOMaley

there it is

DISPLAY=:0 npm start

edit

nano is a terminal windows based
genie is a graphical editor
there lots of others

TomOMaley

@sdetweil ???

sdetweil

@TomOMaley you replace npm start
with npm run start:wayland

right?

you said you didnt know how to edit. how do you change config.js?

TomOMaley

@sdetweil can’t neither write nor do anything in mm.sh

TomOMaley

@sdetweil Thank you so far Sam. I give up and will use my Pi4 where everything runs smothly. It is much to time consuming and frustrating. When I have more time I think I try an MM installation manually from scratch. I really appriciate your help. Can I show my appreciation in any way ?