MMM Awesome Alexa installing snowboy.

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