Raspbian#RPi3 is unsuccessful to boot up with SenseHAT - raspberry-pi

My raspberry pi is installed with the latest raspbian image, and now I am trying to program my SenseHAT. The status is :
The firmware boots up successfully, the rainbow is displayed on the
screen and Sense HAT, and it proceeds.
The OS(up-to-date raspbian) start loading with the splash screen, but
it is stuck at somewhere when it says udisks2.service,
All the OS modules are installed,
I2C is enabled at /boot/config.txt
dt_overlay is configured at /boot/config.txt.
Anybody has faced this freezing problem before? My raspberry pi 3 and Sense HAT simply not getting along with each other.

Related

It is either cec-ctl or VLC, not both on Raspberry Pi 3 B+ Bullseye

My Node.js project utilizes CEC control and VLC where the app turns on the TV and chooses the HDMI port that the VLC video stream will be viewed on at a scheduled time.
Everything worked on Buster except that too many indeterminate crashes with segmentation faults occur with cec-client.
Since I am nearing a 'production' release, I thought it best to upgrade the OS to Bullseye and find a cec-client replacement. I found cec-ctl and made it asynchronous - ctl-cec works perfectly, everytime, no crashes. BUT, now VLC does not render anything, not even a black screen. Doing a 'ps' command during a time that a video should be playing, I can see that VLC is running.
What I tried: It turns out that changing the /boot/config.txt dtoverlay=vc4-fkms-v3d (Buster) to dtoverlay=vc4-kms-v3d (Bullseye) causes the problem. The Buster version of dtoverlay seems to be required for VLC to run, and The Bullseye version of dtoverlay is required for a /dev/cec0 to be created and used by ctl-cec.
All I can see from my inexperienced view is mutual exclusivity, but this doesn't feel like this is the final answer. Using both dtoverlay version (Buster/Bullseye) will brick the pi (speaking from the very recent experience of one not well-versed in dtoverlays).
I also tried: I Googled this problem to the extent of my search skills and have not been able to resolve this problem.
Any help is greatly appreciated!
Raspbian OS: Bullseye (Desktop)
Raspberry Pi 3 B+
App: Node.js based with ability to make config changes and set schedules via an external browser within the LAN.
The solution for my project, after days of Googling, turned out to be TOO simple (found here: https://www.reddit.com/r/archlinuxarm/comments/lg4z5u/no_hdmi_audio_via_alsa_on_raspberry_pi_400/):
sudo apt install pulseaudio
along with:
dtoverlay=vc4-kms-v3d
VLC and cec-ctl now work together perfectly on Raspberry Pi 3B+/Bullseye

Want to understand the different possibilities to autostart a program on a Raspberry Pi

I've a raspberry Pi with a actual Buster OS and a Rhasspy installation. Rhasspy requires a working audio environment, in my case a seeed Respeaker 2Mic-Pi HAT and a bluetooth speaker. Starting Rhasspy manually works without any problem, but all my attempts with a Buster light OS to start Rhasspy automatically didn't work. I tried to start Rhasspy with a cronjob #reboot, with rc.local and as a service but either the 2Mic-Pi HAT or the Bluetooth speaker didn't work. My final attempt was with a Buster Desktop installation. Same thing as with the light installation except when I start Rhasspy with a .desktop file that at least did the thing. So I want to know what makes the difference here compared with my unsuccessful attempts. Thanks in advance for a clarification... Jo

raspberry pi 4 onboard virtual keyboard AT-SPI: Couldn't connect to accessibility bus. Is at-spi-bus-launcher running?

I installed "onboard" as a virtual keyboard on the system. It looked much nicer and more useful than matchbox. I went into the settings and chose the auto open option when I edit the post. after that i restarted my raspberry pi. As it didn't come on automatically, I couldn't run it from the terminal or the menu normally. The error I get when I try to run it from terminal
Hej blackmamba,
I had the same issue with the on screen keyboard florence. After I installed at-spi2-core, it didn't crash anymore, though i could not get it to open automatically.
So I tried installing onboard and everything worked quiet well. Might be a hint..
regards, jarvis
Raspberry Pi B+
5.10.63 Kernel
Debian Buster 10
Waveshare 10.1" HDMI LCD Touch Display

Locked out, Raspberry Pi

I pulled my Raspberry Pi out from storage and have forgotten my username and password. I don't have access to a microSD reader at the moment. Is there any way I can simple reset the Pi to it's default? I have no important files on there, so I'm fine with wiping and starting over (as long as I still have Raspbian installed).
How would I go about wiping and starting over from the login screen?
I was able to wipe and start over by restarting (control-alt-delete) and hold down shift. I then installed Raspbian, which wiped the card and started the Raspberry Pi from scratch.

How do you get a waveshare 3.5 inch touch LCD to work with Raspbian Jessie?

I have a waveshare 3.5 inch touch LCD display and I m trying to get it working with the latest version of Raspbian A.K.A Raspbian Jessie. I followed futurice.com 's tutorial on getting it to work (tutorial is titled I'd like some LCD on my pi) and it worked on Raspbian Wheezy just fine. All I get now is a blank white screen. All help is greatly appreciated! (I must use the official Raspbian Jessie image without NOOBS from the Raspberry pi website.) I have a Raspberry Pi 2 Mobel B +.
From the product page:
Why the LCD doesn't work with my Raspbian? To use the LCD with the
Raspberry Pi official image, driver should be installed first. Please
refer to the user manual. However, for the first testing, you may want
to use our provided image directly. Why the LCD still doesn't work
with the Waveshare provided image? Make sure the hardware connection
is correct and connects fine. Make sure the image in TF card is burnt
correctly. The PWR will keep on and the ACT will keep blinking when
the Raspberry Pi starts up successfully, in case both of the two LEDs
keep on, it is possible that the image was burnt incorrectly OR the TF
card was in bad contact. Which power supply should I use? It is
strongly recommended to use a stand-alone 5V/2A power adapter, because
the PC's USB port might doesn't have enough power to support the Pi
and LCD. For more info, please check the wiki page
You can find more info on their wiki.
It sounds like you either need to use their Raspian image, or install the driver for this display on your existing Raspian install:
wget http://www.waveshare.net/w/upload/7/73/LCD-show.tar.gz
tar xvf LCD-show.tar.gz
cd LCD-show/
sudo ./LCD35-show