New answers tagged

1

Did you buy the SD card with NOOBS, or build your own? I got burned a few weeks ago trying to build my first RaspberryPi. Turns out the NOOBS / Raspbian SD card must be formatted as FAT32, which means that card cannot be bigger than 64GB. A larger card will look fine on a PC, but show no activity when plugged into the Raspberry Pi (one steady led on most ...


1

No WiFi boot is not supported and most likely will never be either. It's way to complex to fit inside a bootloader.


1

For the new Pi4, the boot flow got some changes as the old bootcode.bin moved from sdcard or /boot to internal 512KB EEPROM more : Pi4 Bootflow


0

This error also shows up on the Raspberry Pi 4 platform if the firmware drivers are corrupt or missing. An easy fix would be to reinstall them. sudo apt update sudo apt install firmware-brcm80211 --fix-broken All Raspbian versions come with this driver - and many others. See apt search ^firmware-* for all available firmware drivers. Earlier versions of ...


0

Last weekend I took a project to build myself a nice Pi powered NAS. Everything worked perfectly, but as I saved my changes to /etc/fstab and rebooted all hell broke loose. The Pi would simply not boot up. I run almost all my Pis in a headless enviroment so I had to get hold of our TV and a keybaord to see what was going on. Lo and behold, there it was, The ...


3

I was successful adding a line like this to my /boot/config.txt: # increase power for display config_hdmi_boost=4 Please see Video options in config.txt - Raspberry Pi Documentation. You need to reboot after that change.


0

The answer may be much, much simpler than people think. All I had to do to solve the same symptom was to plug the HDMI cable into the other HDMI port on the pi! See NOOBS stuck at rainbow screen - Raspberry Pi 4 I should add that I'm unfamiliar with the Pi 2. Does it also have two HDMI ports like the Pi 4?


1

2020-02-07 answer: You can get the serial number with: rpi ~$ cat /sys/firmware/devicetree/base/serial-number 10000000cd0297b1 So the command to call chromium on the command line with serial number resulted in: rpi ~$ chromium-browser --incognito --noerrdialogs http://url.com?sn=$(cat /sys/firmware/devicetree/base/serial-number)


2

Not direct an answer to your question but maybe a help to examine what's going on with the bootloader. The Raspberry Pi 4B has an EEPROM now where you can set a debug flag BOOT_UART=1 as described at Pi4 Bootloader Configuration. Then the boot loader will output low level debug information to the serial debug console on pins GPIO 14 and 15 so you need a USB ...


1

The same issue happened to me today, so I started finding a solution and found your question. This post helped me https://www.raspberrypi.org/forums/viewtopic.php?t=34061. Open your config.txt file from the boot and the below lines. config_hdmi_boost=4 hdmi_force_hotplug=1 Try the alternate HDMI port. It worked for me.


1

It works (at least in 2019) But there are two ID on a partition, the UUID and the PARTUUID wich are different. You can find them with the blkid command. On my system, this gives : $ blkid /dev/sdb1 /dev/sdb2: LABEL="root" UUID="ba0d4dc4-18e9-42ff-81e6-077510abdb79" TYPE="ext4" PARTLABEL="primary" PARTUUID="3c8e2158-0bec-445b-9fa0-0d b302c2384c" $ The ...


0

Put the SD Card (what you called sim card) into the card adapter that you have used to flash the image. Then mount the first partition of it if not already mounted automatically. Then create a new file wpa_supplicant.conf on the mounted directory with the correct settings, unmount it and boot the SD Card in your RasPi. The wpa_supplicant.conf file will be ...


0

To verify your problem I have done a plain installation from scratch using the smallest image. Here is what I've done: Downloaded Raspbian Buster Lite 2019-09-26 onto a PC with Debian operating system. Compared checksum pi ~$ sha256sum 2019-09-26-raspbian-buster-lite.zip a50237c2f718bd8d806b96df5b9d2174ce8b789eda1f03434ed2213bbca6c6ff 2019-09-26-raspbian-...


9

There's a service that run only on the first boot, then disables itself. It's a Debian SysV style script in /etc/init.d, resize2fs_once. It does this: log_daemon_msg "Starting resize2fs_once" ROOT_DEV=$(findmnt / -o source -n) && resize2fs $ROOT_DEV && update-rc.d resize2fs_once remove && rm /etc/init.d/...


4

It's not clear from your question what you observed, but it might be because it gets booted twice the first time, once to resize the file system and again to start up "for real."


0

Pi do not use a "simm" card (whatever that may be). You can put a wpa_supplicant file on the first partition of the SD Card and it will replace the old file.


1

The debug messages you are asking about are on a stage where only the boot loader is running but not even the kernel is loaded. So there is no chance to have logging to a file because there is nothing what managed it. But you can enable the boot loader to output messages to the serial debug console. For this you need an USB to TTL (RS232) serial cable. An ...


2

You set DefaultDependencies=false. This is a hard condition and I would not do it because you have to define all needed dependencies by yourself. With man systemd.service you will find: Default Dependencies The following dependencies are added unless DefaultDependencies=no is set: • Service units will have dependencies of type Requires= and After= ...


Top 50 recent answers are included