Read the statement by Michael Teeuw here.
Failed Update
-
@sdetweil All is OK. I am so grateful for all of your assistance. In my opinion, what you performed was alchemy or witchcraft. I’ve been attempting to identify the problem and have made multiple unsuccessful attempts. An old picture I had from a few months ago was my saviour. My wife was becoming tired of my futile attempts at updating.
You have brought me happiness and protected me from madness. That’s a significant victory. -
@DarkV before you jump off the bridge! try this
sudo apt-get remove nodejs npm -y hash -r
make sure gone
which nodethen
sudo apt-get install nodejs:armv7l
node -v -
@sdetweil I don’t know what happened, but the reply is above. Many thanks
-
@DarkV cool… i didn’t expect that it, i’m glad!!
-
@sdetweil I did this
sudo apt-get remove nodejs npm -y
hash -r
which node
which nif which n response with empty then do
sudo apt-get install n
once n responds then
sudo n 20.8.0 --arch armv7l
hash -r
node -vThen both scripts and it went through!
-
@DarkV said in Failed Update:
–arch armv7l
awesome… it was that sneaky little --arch parm…
fixing upgrade script now . sorry for your troubles
-
@sdetweil No worries, thanks you for your time
-
@DarkV any chance you still have the os image file you are running
the info says (from the upgrade.log)
6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye
only one I can find online says
6.1.21-v7+trying to test fix for the problem you encountered.
if you still have the image file can you give me its name…
also, what pi is this, 3 or 4?
thanks| edit: was able to make one
| install bullseye armhf
| edit /boot/config.txt
add
arm_64bit=1then u will boot 64bit kernel, (seen with uname -a, aarch64)
Linux raspberrypi4 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
and have 32 bit runtime (seen with file /bin/bash
/bin/bash: ELF 32-bit LSB executable
-
@sdetweil
Sam, I did an update yesterday and found Node 20.8 not working on my raspbian bullseye install.
I had an issue mentioned by someone else here before referring a missing GLIBCXX_3.4.26 file.
I needed to purge and install node 18.x. Then it worked.
Possible that this happens for more users with Raspbian
Bullseye.
I see your upgrade script requests Node 20.8.
Not sure if that may be an issue for other people as well? -
@lavolp3 can u send me the ~/MagicMirror/installers/upgrade.log
so I can see what happened…
same userid at gmail