Read the statement by Michael Teeuw here.
dri3 extension not supported
-
i get this error right from a fresh install
Pi 3B Ver2
Rasp Pi OS 64bit (not lite per install instructions) and from raspberypi.com site directly, verified hashI went through the manual install steps for MM.
it starts but i get this error. is it important?
Any idea what this is?
I cant seen to find anything about it on either the MM forum or the RaspPi forum.The only reference to dri3 seems to be with display drivers? the first message after “npm run start” returned :
> magigmirror@2.20.0 start > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.jsPerhaps i need to go to 32-bit (but not lite, per install instructions) ?
-
@leftyleo yeh, 64 bit os not ready.
that error is a video driver problem.
you ‘might’ be able to fix this by disabling use of the gpu.
edit package.json and change
"start": "DISPLAY=\"${DISPLAY:=:0}\" ./node_modules/.bin/electron js/electron.js",to
"start": "DISPLAY=\"${DISPLAY:=:0}\" ./node_modules/.bin/electron --disable-gpu js/electron.js", -
@sdetweil
that cleared the error thank you–if you think i should switch to 32-bit Raspian i will do that as well
the Raspian desktop is slightly outside (larger than) the monitor screen, but the MM is displayed well inside the borders so if i get it all set on this monitor i will stick to this one.
-
@leftyleo no switch just understand there are still flaky things… some modules w binaries most likely won’t work, pir, any gpio stuff…
-
@sdetweil - ok i was incorrect - i am still getting that error but with the default config (less the ‘compliments’ module) the MM still works - so maybe it is not an issue
– i tried two other modules and cant get them to work
such as MMM-JEOPARDY - I saw posts in other threads and it is exact but something isnt right.- i will work on it some more, search threads before making a new question. I have to be sure it isnt something i just mis-optioned, typo… need to look at it tomorrow with fresh eyes
-
@leftyleo many modules suffer from this
https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-later -
@sdetweil i just hope to get mostly basic stuff weather, clock, google calendar , change the background from black… that kind of stuff.
-
@leftyleo yeh but jeopardy isn’t in the list u just gave,. lol
-
@sdetweil -LOL- thought i would start simple… Jeopardy works now. going to try to relocate it , and loose that image. (Sorry, Alex)
I am sure there are lots of options that i cant locate.
The hunting for the answers before asking is part of my learning challenge. -
@leftyleo not to hijack this thread. But since you were thinking of going from 64 to 32 bit os…
I am getting the same error on a fresh sd card on a rpi 3B with buster 32bit installed. It has manually installed MagicMirror, node, etc., no extra modules, just the config sample copied to be config.js.
…
[05.09.2022 20:19.03.191] [LOG] Starting node helper for: newsfeed
[05.09.2022 20:19.03.192] [LOG] Sockets connected & modules started …
[05.09.2022 20:19.05.030] [LOG] Launching application.
[2092:0905/201909.167187:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[2132:0905/201909.521340:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[2106:0905/201909.609131:ERROR:command_buffer_proxy_impl.cc(126)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
… -
@kayakbabe -
No problem - that was on topic
I actually tried going to 32 and i believe i am back to 64 but i will need to recheck
-i get the same error on both, even with sdetweil’s recommendation above to add the --disable-gpu switchat least whatever was hanging up MM , it is working now
and i am banging my head against modules and minor CSS to add backgroundIt can be frustrating but it is fun to search for possible solutions and experiment and learn
-
@leftyleo what module problems?
-
@kayakbabe said
I am getting the same error on a fresh sd card on a rpi 3B with buster 32bit installed. It has manually installed MagicMirror, node, etc., no extra modules, just the config sample copied to be config.js.
…
[2092:0905/201909.167187:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[2132:0905/201909.521340:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[2106:0905/201909.609131:ERROR:command_buffer_proxy_impl.cc(126)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
…I did more digging and I am not sure if this is the right solution for a Raspberry Pi 3B running Buster
I followed the instructions on this page [https://www.raspberryconnect.com/projects/35-games/142-trying-out-opengl-on-raspberry-pi-3] and the viz_main and gpu memory buffer and other stuff disappeared. I’m now playing with the different settings in the raspi-config and going to up the split memory. I tried first with settings it to 128 , half of what they recommended, cause I’m just contrary my mama says. And MagicMirror does seem to run more smoothly than with the default buster install. BUT the pi is much worse at multi tasking now. I can’t have very many chromium windows going at once. So, i’m going to play with the video setttings more. I know I won’t be running chromium when the mirror is running. But if I put a lot of modules into the magic mirror… it would stress the pi too.Anyway, perhaps this info will help you.
Note: on the last buster install, the raspi-config advanced options and performance options are a little different location in the menu than described in this article.
Kelly
-
@kayakbabe you can run raspi-config from the terminal window
-
@kayakbabe - been a bit out of sorts lately and havent had a chance to get back to MM after a new linux install. But finally all good there
–the MM still runs with the dri3 error for now. Perhaps it wont make any difference. Just one of those glitches. I thought it was why i could not boot. but it was (of course) an error i introduced in the config.js which i couldnt find and had to back track to the default and try again. Sure it is a little frustrating - but it is also how I learn ; by making mistakes.
–Now back to MM - I do not currently have a specific module issue. I want to have mostly basic stuff - like clock, Google calendar, weather - at least to start. I dont think i will need much else, i hope
I appreciate the help
Thanks everyone -
Still strange that this dri3 not supported seems an enigma .
–i.ll keep an eye on it when MM starts up
Maybe it is a PI3B issue - i would think that is more likely and not a MM issue
–i am going back to the PRI forum to search and / or post the question there -
ok havent worked on this in a couple weeks. well i have to re-image the card- the OS boot fails so badly that it goes to CLI prompt.
hardly had anything so starting from scratch again — but thats Not a MM issue --its a RPI issue
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login