Hot answers tagged

5

I found what I believe was the cause, and it now appears to be fixed. Since this machine has a battery-backed RTC on it, fake-hwclock had been uninstalled long ago. When looking at the dump from 'journalctl -xb' I noticed the timestamps were all from several months back (about the time the machine was made, perhaps), and then didn't jump to the present ...


3

Yes, they are mutually exclusive and the change is permanent. https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md


2

Ok, so I finally fixed it (thanks to everyone) :) I deleted everything in /boot, replaced it with the contents of my backup, and added the kernel modules from my backup to /lib/modules. It entered me into emergency mode, then I did the sequence: apt-get update apt-get remove raspberrypi-kernel apt-get install raspberrypi-kernel reboot Now, I have the ...


2

I don't know what a CrowPi is or what version of Raspbian it is based on. The config.txt file explains WHY the pins are outputs. It contains:- # SPi Related configuration dtoverlay=spi1-3cs This sets GPIO 16, 17, 18 as outputs Name: spi1-3cs Info: Enables spi1 with three chip select (CS) lines and associated spidev dev nodes. The gpio pin ...


2

To run the script in the foreground as PI user on startup, type the following commands in terminal to create a file run.desktop in ~/.config/autostart cd ~/.config/autostart nano run.desktop Now, paste the following code in run.desktop: [Desktop Entry] Exec=lxterminal -e "/home/pi/Desktop/run.sh" Type=Application Save the file by pressing CTRL + O and ...


2

Your SDCard probably doesn't have the firmware/bootcode for a 3B+, or it's a NOOBS SDCard. If it's NOOBS forget it, write a new card with plain Raspbian Buster 2019-07-10. If it's not NOOBS then stick the SDCard back in your RPi3B Run sudo apt update, sudo apt -y dist-upgrade then sudo poweroff Try that back in the 3B+. If it doesn't work put it back in ...


1

Relevant scripts / config files are hidden inside the boot ramdisk image, initrd. This file is XZ-compressed, this is why grepping it doesn't reveal anything. Once extracted and mounted, you'll find /etc/systemd/system/keybow.service which starts /usr/bin/keybow


1

No. (Although this depends on what you mean by mutually exclusive - booting or setting OTP bit.) You don’t say which model Pi you have; the instructions to set the OTP bit only apply to the Pi3. The OTP bit is set by default on the Pi3B+ (as vcgencmd otp_dump | grep 17: shows) but it boots from SD Card if no device is detected within 5 seconds.


1

This is not a problem covered by The Boot Problems Sticky I suggest you try removing the SD Card - where the green LED should blink 4 times alternating with long solid green. If not you probably have a hardware problem.


1

If you booted unmodified Raspbian and it stuck at rc-local.service then your Raspberry Pi or your SD Card is broken. Try another RasPi or another SD Card. Use another flash program. Verify checksum of the downloaded Raspbian image.


1

Personally I would recommend starting with a fresh image. Backup the current image of your sd card to your computer (google how if you need help) you can always go back to it. With a fresh image you will be sure not to have any other weird artifacts such as you already have with the pdf. As for the pdf itself, are you sure it's being displayed at boot, or ...


1

Just download a new OS (which will have changed since whatever you are using) and install it. Seeing as you don't know what is on it there is nothing to lose. See https://www.raspberrypi.org/downloads/raspbian/


Only top voted, non community-wiki answers of a minimum length are eligible