MM loading all modules is taking 2-3 minutes.

sdetweil

@plainbroke said in MM loading all modules is taking 2-3 minutes.:

I have seen reference to this before but am either brain dead or my google search is failing me.
0|mm | MESA-LOADER: failed to open kms_swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
0|mm | failed to load driver: kms_swrast
0|mm | MESA-LOADER: failed to open swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
0|mm | failed to load swrast driver
0|mm | [875:0114/170050.541663:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
0|mm | [875:0114/170113.661954:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
0|mm | [875:0114/170115.296236:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!

no… that is the GPU driver stuff… usually not enabled in /config.txt in 2.26 we disable using the gpu by default to turn off these messages (instead of leaving it on in 2.25 and prior)

plainbroke

@sdetweil
I am still on 2.24 so I can use MMM-RTSPStream, also still on Jesse for the same reason.
Should I run this to remove swap file?
sudo swapoff -a -v
sudo rm /swapfile

sdetweil

@plainbroke so, I would be carefull… newer code doesn’t run on jesse and gosh knows what you have now…

4 OS releases back (2017), stretch , buster, bullseye, now bookworm
https://en.wikipedia.org/wiki/Raspberry_Pi_OS

so, you have an 8gig machine, but can only use 2gig (32bit OS)

plainbroke

@sdetweil
Sorry it is buster, it is the last one that allows the rstp modules I like so much…
Linux MM 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux

sdetweil

@plainbroke said in MM loading all modules is taking 2-3 minutes.:

armv7

32bit

aaarch64 is 64 bit

plainbroke

@sdetweil
Can I load the 64bit version without reloading all my MagicMirror modules ect?
I tried this :

cd ~/MagicMirror
export external_browser=midori
export ELECTRON_DISABLE_GPU=1
DISPLAY=:0 npm start

sdetweil

@plainbroke you have to use my start script to make Midori work, after you install it

change the package json {“start” line to {“start1”

then add a new start line

{"start":"./run-start.sh"},

and download the run-start.sh from my script repo, and put it in the MagicMirror folder, mark it executable
chmod +x run-start.sh

plainbroke

@sdetweil
Which one of the package.json files the one before MagicMirror folder or the one in the MagicMirror folder?

sdetweil

@plainbroke in the MagicMirror folder

there should not be one in the folder before

plainbroke

@sdetweil
Well I removed the package.json and packagelock.json from the folder MagicMirror sets in and ran your upgrade script and my MM loaded a whole lot faster and only time will tell if it is totally fixed or not…
I appreciate your patients dealing with this issue.
I will definitely add it to my saved stuff.
I would like to try to use a different browser and see if it fixes a few other issues since I am using a 32 bit OS.