upgrade to 2.4.1problems and solutions

[richland007]

@mykle1 Nope no luck that did not do it. Disabling “updatenotifications” had no effect
wth?? i am not getting it i had to go through hell to update to the new version and now i am stuck with this problem
What else can i do
Denis

[richland007]

If i do a npm rebuild or npm install under MagicMirror in the initial run meaning if you npm start it says something like;
MESA Loader failed to start lgr
… or something to that nature 2 times than it loads just fine and it does not happen the second time that you restart the MM
i think it has to do with the settings on the Open GL when you tweak the Rpi settings
Denis

[lavolp3]

@richland007 said in upgrade to 2.4.1problems and solutions:

i think it has to do with the settings on the Open GL when you tweak the Rpi settings
Denis

A lot of people recently had issues with OpenGL.
Do you only get a black sceen? Turn OpenGL off then. You don’t need it necessarily. For me it worked again afterwards. Still thinking about how to be able to activate OpenGL.

And: If you need help, it is better to get into more detail first hand.

[richland007]

Yes it is confirmed that it is Open GL fault if you follow Raspberry Pi configuration changes here: Configuring the Raspberry Pi the real driver does not work at all the display just stays black …
and with the fake driver option magic mirror will run on server mode only .

If you take out the Open GL driver the mirror will run as it is supposed to but you will see a spike in cpu usage from around 20% with the fake kms driver to over 75% with the regular Rpi driver.

How do we solve this and has anyone else had this issue other than me and @lavolp3 ??

Thank you
Denis

[richland007]

Another thing i have noticed is that configuring the settings to Disable WiFi Power Save on Rpi 3 (Stretch) will brake automatic connection to the router in a weird way … meaning after a reboot the Rpi will associate itself to a wireless network that you have previously signed on to but there is no internet access … you have to manually disconnect from the network and connect back on for internet to start working !!! which is definitely not ideal for a automatic run of raspberry pi !!

Has anyone else had this issue??

D