Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Different /boot configuration file location depends on Raspberry Pi hardware or variant of OS?
开云体育Hello Everyone,As I continue to learn Raspberry Pi OS Bookworm (Debian 12), I'm finding a strange inconsistency and I think it either depends on: ?? a) the hardware I'm using or the use of Raspberry Pi OS Lite (No GUI) vs Raspberry Pi OS Desktop (GUI) ?? b) different versions of Rpi-OS images where they are making changes mid-release I'm curious if anyone can confirm this on your setups: ?? Raspberry Pi 4 with 4GB of RAM running Bookworm Lite (No GUI) ????? -- ????? cat /etc/os-release ????? -- ????? PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" ????? NAME="Debian GNU/Linux" ????? VERSION_ID="12" ????? VERSION="12 (bookworm)" ????? VERSION_CODENAME=bookworm ????? ID=debian ????? HOME_URL= ????? SUPPORT_URL= ????? BUG_REPORT_URL= ????? -- ????? Shows all config files in /boot are symlinks to /boot/firmware/.? That makes things backwards compatible: ??????? -- ? ?? ??? ls -la /boot/*.txt ??????? lrwxrwxrwx 1 root root 20 Oct? 9 20:39 /boot/cmdline.txt -> firmware/cmdline.txt ???? ? ? lrwxrwxrwx 1 root root 19 Oct? 9 20:39 /boot/config.txt -> firmware/config.txt ??????? -- ????? Here is what is in the new /boot/firmware directory for config files ??????? -- ??????? ls -la /boot/firmware/*.txt ??????? -rwxr-xr-x 1 root root? 132 Oct? 9 21:00 /boot/firmware/cmdline.txt ??????? -rwxr-xr-x 1 root root 1364 Oct 27 17:39 /boot/firmware/config.txt ??????? -rwxr-xr-x 1 root root? 145 Oct? 9 20:57 /boot/firmware/issue.txt ??????? -- Now compare that to a Raspberry Pi 5 with 8GB RAM running Bookworm Desktop (GUI enabled): ?? $ cat /etc/os-release ?? -- ?? PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" ?? NAME="Debian GNU/Linux" ?? VERSION_ID="12" ?? VERSION="12 (bookworm)" ?? VERSION_CODENAME=bookworm ?? ID=debian ?? HOME_URL= ?? SUPPORT_URL= ?? BUG_REPORT_URL= ?? -- ?? $ ls -la /boot/*.txt ?? -rw-r--r-- 1 root root 92 Feb? 5 18:49 /boot/cmdline.txt ?? -rw-r--r-- 1 root root 91 Feb? 5 18:49 /boot/config.txt ?? lrwxrwxrwx 1 root root 18 Dec? 4 21:04 /boot/issue.txt -> firmware/issue.txt ????? These configuration files only contain text like: ? ? ???? -- ? ? ? ?? DO NOT EDIT THIS FILE ???? ? ? The file you are looking for has moved to /boot/firmware/config.txt ? ? ???? -- ?? The new REAL location of these files is now ONLY in /boot/firmware.. ?? -- ?? $ ls -la /boot/firmware/*.txt ?? -rwxr-xr-x 1 root root? 132 Feb? 5 18:57 /boot/firmware/cmdline.txt ?? -rwxr-xr-x 1 root root 1315 Feb 14 12:45 /boot/firmware/config.txt ?? -rwxr-xr-x 1 root root? 145 Dec? 4 21:04 /boot/firmware/issue.txt ?? -- By NOT making /boot/cmdline.txt a symlink to /boot/firmware/cmdline.txt, this BREAKS backwards compatibility with various tools, documentation, etc.? I'm curious if anyone knows WHERE and WHY this is happening? --David KI6ZHD |
开云体育Dave,?? Checked RPi5 bookworm 64, RPi4 bookworm 64, CM4 bookworm 64 with essentially the same results except for the ls -la /boot/*.txt .? RPi4 & CM4 /boot/*.txt reported issue.txt, but RPI5 did not. ?? ls -la /boot/firmware/*.txt had identical results on all.? All systems up to date AFAIK. Bill KC9XG On 2/18/2024 1:26 PM, David Ranch
wrote:
Hello Everyone, |
开云体育Look at the dates of the 2 image files.? Are they the same or different?? I noticed the image I downloaded dated October or November 2023 had the symlinks.? The latest image has the /boot/*.txt files with the disclaimer in them and are no longer symlinks.? This is a direct copy of what Debian did.? Why Debian changed it I have no clue.? You could always delete the /boot files and create symlinks there to the /boot/firmware files
Get
On Feb 18, 2024, at 11:27, David Ranch <rpi4hamradio-groupsio@...> wrote: Hello Everyone, |
to navigate to use esc to dismiss