MMM Awesome Alexa installing snowboy.

[Ameyalgudkar]

@sdetweil

there.
and if there’s a way to run it on 4.19 then how do I downgrade?

[sdetweil]

@Ameyalgudkar no idea… i see the latest images are all at kernel 5.4

https://www.raspberrypi.org/downloads/raspberry-pi-os/

[Ameyalgudkar]

@sdetweil If you could make a copy of your image file or if you have it saved on your disk maybe?
could you upload it to google cloud or something?

[sdetweil]

@Ameyalgudkar see the chat messages I sent you

[A Former User]

@sdetweil :

I confirm new update of RPI are now in 5.4.x kernel

bugs@debian:~/MagicMirror/modules$ ssh pi@192.168.X.XX
pi@192.168.X.XX's password: 
Linux Raspberry 5.4.51-v7l+ #1333 SMP Mon Aug 10 16:51:40 BST 2020 armv7l

I have not see :)
my npm library can make the build of @bugsounet/snowboy

pi@Raspberry:~/MagicMirror/modules/MMM-Spotify $ npm install @bugsounet/snowboy
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported

> @bugsounet/snowboy@1.6.2 install /home/pi/MagicMirror/modules/MMM-Spotify/node_modules/@bugsounet/snowboy
> bash scripts/installer.sh

make : on entre dans le répertoire « /home/pi/MagicMirror/modules/MMM-Test-Blank/node_modules/@bugsounet/snowboy/build »
  CXX(target) Release/obj.target/snowboy/lib/snowboy.o
  SOLINK_MODULE(target) Release/obj.target/snowboy.node
  COPY Release/snowboy.node
  COPY /home/pi/MagicMirror/modules/MMM-Test-Blank/node_modules/@bugsounet/snowboy/lib/node/binding/Release/node-v64-linux-arm/snowboy.node
  TOUCH Release/obj.target/action_after_build.stamp
make : on quitte le répertoire « /home/pi/MagicMirror/modules/MMM-Test-Blank/node_modules/@bugsounet/snowboy/build »

[@bugsounet/snowboy] Do you want to execute electron rebuild ? [Y/n]
Your choice: y
✔ Rebuild Complete

> @bugsounet/snowboy@1.6.2 postinstall /home/pi/MagicMirror/modules/MMM-Test-Blank/node_modules/@bugsounet/snowboy
> tsc -p tsconfig.json

+ @bugsounet/snowboy@1.6.2
added 187 packages from 137 contributors and audited 190 packages in 107.058s

4 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

after official version, i don’t know…
it’s always been a bit boring to do a build correctly…

@Ameyalgudkar:
I see in the error log it’s an x64 build…

In MagicMirror requirement it’s specified to download the lasted version of raspbian with desktop

The official website is https://www.raspberrypi.org/ and on the download page there no x64 version
So you use a beta version with … beta bugs and Complex Module of MagicMirror don’t support x64 version.

Best way ?
Like windows and others OS you can’t transform x64 to 32bits (and 32bits to x64 too)
so best way is reinstall OS with 32bits version

@bugsounet

[sdetweil]

@Bugsounet he is doing on pi, System Linux 5.4.51-v7l+ < — v7l

i am going to test ubuntu pi 64 bit tomorrow.

couldn’t wait…

fix

need to install libcblas

sudo apt-get install libatlas-base-dev

then both my installations using snowboy correctly rebuilt… on ubuntu 64 on pi4.

[A Former User]

ah… that’s why my library have no problem for installing :)
I force it to install with installer lol :)

nedeed dependencies

[Ameyalgudkar]

@Bugsounet said in MMM Awesome Alexa installing snowboy.:

@Ameyalgudkar:
I see in the error log it’s an x64 build…
so best way is reinstall OS with 32bits version

I am indeed running the 32bit Raspberry Pi OS latest from the official downloads, and not any beta versions.
I don’t know why the installer is running it in x64.

[Ameyalgudkar]

Also now I am facing this problem where, no matter what I do, RPI4 does not take any other sd card boot image and boot that particular system.
For instance, My 32gb with working MM and RPI OS 32bit, boot up without any problem.
But then, I tried booting with a older build of RPI OS, Ubuntu(https://ubuntu.com/download/raspberry-pi) 32bit for Pi4.

Both tried on different sd cards with 8gb/32gb and also reformatting it several times and everything.

I feel just so exhausted doing all this and thinking of returning my RPI4 if it has so may issues.

[A Former User]

internal firmware :) (eeprom)

[sdetweil]

@Bugsounet doesn’t the newer system apply the firmware update automatically?

see here for the firmware test and update procedure
https://www.raspberrypi.org/documentation/hardware/raspberrypi/booteeprom.md

[Ameyalgudkar]

@sdetweil I tried the boot recovery mentioned in the link, but no luck with that. Still gets stuck in boot and with a red light. no green light. should I try to get a replacement for my device?

[sdetweil]

@Ameyalgudkar I would guess yes

[A Former User]

and Recovery ?

[sdetweil]

@Ameyalgudkar this procedure to verify and then fix

Is the bootloader working correctly?
To check that the bootloader is working correctly, turn off the power, unplug everything from the Raspberry Pi 4, including the SD card, and then turn the power back on. If the green LED blinks with a repeating pattern then the bootloader is running correctly, and indicating that start*.elf has not been found. Any other actions imply that the bootloader is not working correctly and should be reinstalled using recovery.bin.

Recovery image
If the Raspberry Pi is not booting it's possible that the bootloader EEPROM is corrupted. This can easily be reprogrammed using the Raspberry Pi Imager tool which is available via the raspberrypi.org downloads page.

Using the recovery image will erase any custom configuration options, resetting the bootloader back to factory defaults.

Updating the bootloader
Bootloader updates are instigated during a normal apt update, apt full-upgrade cycle, this means you will get new features and bug fixes during your normal updates.

Bootloader updates are performed by the rpi-eeprom package, which installs a service that runs at boot-time to check for critical updates.

To update your system, including the bootloader:

sudo apt update
sudo apt full-upgrade
sudo reboot

and the bootloader recovery process is documented on the imager page, right?
https://www.raspberrypi.org/downloads/

[sdetweil]

@Ameyalgudkar I also uploaded a fixed do-install.sh which loads the dependency listed before as part of the install

I have run it on three different machines and it works correctly

[Ameyalgudkar]

@sdetweil yes thats the one.
Also I just checked there are few parameters in that config that I have slightly different than default. Even after flashing the default recovery.img it did not get changed. So I will do it manually and check if it works.

[Ameyalgudkar]

@sdetweil sorry to say, but nope it does not work on mine. the same snowboy installation error.

[sdetweil]

@Ameyalgudkar u have to boot the sd card you imaged from the recovery file, right?

[Ameyalgudkar]

@sdetweil So, what I was trying to do is update my eeprom as I was getting the error at boot. and so I did the bootloader factory reset as the steps mentioned

If your Raspberry Pi 4 will not boot, it is possible that the SPI EEPROM has become corrupted. To check, remove the SD card, disconnect the device from power, then reconnect it. If the green LED does not flash, this indicates that the EEPROM has become corrupted.

Raspberry Pi Imager provides an easy way to fix this problem, by automatically preparing an SD card that will reprogram your Raspberry Pi 4’s EEPROM:

Find an SD card that is empty, or does not contain any data you want to keep; it will be completely erased of all data during this process.
Download Raspberry Pi Imager for your operating system from the list near the top of this page.
Click “CHOOSE OS” and select “Misc utility images” then “Pi 4 EEPROM boot recovery”.
Insert an SD card, click “CHOOSE SD CARD”, select the card you have inserted, then click “WRITE”.
Once the SD card is ready, insert it into your Raspberry Pi 4 then connect the Raspberry Pi to power.
Once complete, the green LED will blink rapidly in a steady pattern. Disconnect the device from power. Now you can remove the recovery SD card, insert your usual SD card, and resume using your Raspberry Pi.

that fixed the issue with eeprom not being corrupted.

But later checking the current eeprom I noticed, for some reason the default bootloader I have in Raspberry Pi’s eeprom has been set as such for every new boot I had to short the Global_EN with ground to boot the Pi.

Even that being done it did not boot the new sd card’s no matter what. (So my guess right here is its cause of the makeshift power adaptor I am using which is converting 12v dc to 5v dc)
At this point I’m starting to hate these newer RPI4’s already.

Edit- so there was actually some issue with my SD cards not being flashed properly, now I have enabled the USB boot with the latest eeprom, and the PI boots normally. will get a good sd card reader.