I just know this is how I finally got these images to boot. Using startx seems to require a run manager and one rdm (or something like that) seems to be installed.
#CANT CONNECT TO PI UNLESS L BOOT AND RUN STARTX ON PI CODE#
Maybe someone can explain this parameter and why the imagers are putting out a code that appears to hang up the Raspberry Pi 4B boot process. If you can ssh into the Pi using Putty and the Pis IP address then sudo nano /etc/rc. So I edited the config.txt and changed the dtoverlay entry as follows and the boot process continued and I was up and running on the new images: dtoverlay=vc4-fkms-v3d However, I noticed in the working build I had this entry had the letter “f” in front of the “kms” part. The Raspberry PI Imager is putting the dtoverlay parameter in the config.txt file like this: dtoverlay=vc4-kms-V3d I don't know the reason it's this way for you, only something you might look at and try. And one by one I changed the settings until I found the one problem entry. So I began comparing the entries in the config.txt on the new burns to the working burn.
The easiest way to set up the SD card is to use NOOBS. Luckily I still had an SD card with a working distro on it. The Raspberry Pi requires the operating system to be loaded onto an SD card before it will start up. I did that and the App does not start until i remove that line, because it would cause a back.
I am using the Raspberry PI Imager as well as Balena Etcher but had this black screen not booting condition on my Raspberry PI 4B no matter which distribution I burned. The official Steam Link Raspberry Pi support page is here.
0 kommentar(er)
