New answers tagged

1

Here are a few things to try based on several threads that I found regarding video related Pi 4 boot issues. Update the firmware in the eeprom but make sure you have backups of anything important and stable power. Problems are rare but can have issues up to and including bricking the Pi. Be careful and make sure that you understand the process. sudo apt ...


0

Looks like I tried too many complicated solutions, because I could not get it to work with systemd. An easy sulation that works is adding the two commands to /etc/rc.local above the "exit 0" line. "cd /opt/pygame_prototype" "/usr/bin/python3 pg.py" This file is run with root rights at the end of the login process.


0

The sd's come with some software installed by the manufacturer which the Pi OS install program doesn't/can't clear properly. So just format the SD's before you start using the official 'SD Association SD Card Formatter' software from here https://www.sdcard.org/downloads/formatter/ Once the disk is properly formatted, then go ahead and install your OS etc...


0

According to this Github issue (this is for RPi4, but as long as you have recent versions of bootcode.bin & start.elf the same config.txt parameters should apply) you are correct and uart_2ndstage=1 should enable UART debugging for both Second Stage bootloader (bootcode.bin) and GPU firmware (start.elf): Setting uart_2ndstage=1 causes the second-stage ...


0

Running sudo dhcpcd command helped - network settings were refreshed and connection established automatically after the command completes.


0

Solved on AskUbuntu Stack - Ubuntu Core & Raspberry Pi Zero 2 W Solution (taken from https://qengineering.eu/install-64-os-on-raspberry-pi-zero-2.html) created rpi-zero-2-w.dtb from bcm2710-rpi-3-b.dtb file (copy) modified config with [pi0] kernel=uboot_rpi_3.bin RPi Zero 2 W is now booting OK


0

It could be that you have the same issue as this guy here: Two 'burnt' HDMI ports on two Raspberry Pi 3B+s one after the other Burnt out HDMI port because of newest Raspian OS. So you would have a display which does not turn on on the PI. Check this https://pimylifeup.com/headless-raspberry-pi-setup/ how to setup a headless PI (all done offline on ...


0

I tried looking up some information for you to help. But, according to this reference: config.txt It says: If you are seeing HDMI issues (speckling, interference) then try 7. Very long HDMI cables may need up to 11, but values this high should not be used unless absolutely necessary. So, in other word, try this: Change: config_hdmi_boost=9 To: ...


0

I can confirm that the missing .txt file needs to be included in the initramfs image. You can confirm this by reloading the driver once the system has fully booted and all the firmware files are available: # rmmod brcmfmac # modprobe brcmfmac This got the wlan0 device appearing for me, and dmesg reported the firmware having loaded correctly. But of course ...


0

I solved my problem by doing a couple of things. First of all, my drive had been formatted as an HFS+ drive, so I suspect that that played a factor in preventing the RPi from booting correctly, and secondly I was using the UUID instead of the PARTUUID. What I did to make it work: Repartitioned the drive to take full advantage of the space Formatted the ...


Top 50 recent answers are included