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 &&
I was successful adding a line like this to my /boot/config.txt:
# increase power for display
Please see Video options in config.txt - Raspberry Pi Documentation.
You need to reboot after that change.
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:
The following dependencies are added unless DefaultDependencies=no is set:
• Service units will have dependencies of type Requires= and After= ...
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 ...
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 ...
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.
Try the alternate HDMI port. It worked for me.
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 ...
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
You can get the serial number with:
rpi ~$ cat /sys/firmware/devicetree/base/serial-number
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)