Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/boot is moving to /boot/firmware #3089

Closed
lurch opened this issue Aug 30, 2023 · 13 comments · Fixed by #3105 or #3107
Closed

/boot is moving to /boot/firmware #3089

lurch opened this issue Aug 30, 2023 · 13 comments · Fixed by #3105 or #3107
Assignees
Labels
bookworm 🐛 Issue with Bookworm linked pull request Has a linked Pull Request that will close the issue.
Milestone

Comments

@lurch
Copy link
Contributor

lurch commented Aug 30, 2023

So all references to /boot/config.txt and /boot/cmdline.txt will need updating to /boot/firmware/config.txt, /boot/firmware/cmdline.txt, etc. etc.

EDIT: But only for Bookworm, Bullseye will continue to use /boot/config.txt, /boot/cmdline.txt etc.

@lurch lurch added the bookworm 🐛 Issue with Bookworm label Aug 30, 2023
@lurch lurch added this to the Bookworm milestone Aug 30, 2023
@aallan
Copy link
Contributor

aallan commented Sep 4, 2023

@nathan-contino For bookworm labelled issues you'll need to check out the bookworm branch and work on there. Both @lurch and @jehlers42 are also working on the branch for push/pull as you go rather than waiting to do big commits otherwise you're going to run into merge conflicts.

@fti-sfuke
Copy link

Hi @lurch @aallan
Thank you for the update.

I've downloaded the 64-bit RPiOS 'Bookworm' from here: https://raspi.debian.net/tested-images/
Below are the environment details:

root@rpi4-20230612:/boot# 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="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
root@rpi4-20230612:/boot# uname -a
Linux rpi4-20230612 6.1.0-9-arm64 #1 SMP Debian 6.1.27-1 (2023-05-08) aarch64 GNU/Linux
root@rpi4-20230612:/boot# 

I've noticed that there's no configuration-related content in the /boot/firmware/config.txt file. It only contains the following details:

root@rpi4-20230612:/boot/firmware# cat config.txt
# Do not modify this file!
#
# It is automatically generated upon install or update of either the
# firmware or the Linux kernel.
#
# If you need to set boot-time parameters, do so via the
# /etc/default/raspi-firmware, /etc/default/raspi-firmware-custom or
# /etc/default/raspi-extra-cmdline files.

# Switch the CPU from ARMv7 into ARMv8 (aarch64) mode
arm_64bit=1

enable_uart=1
upstream_kernel=1

kernel=vmlinuz-6.1.0-9-arm64
# For details on the initramfs directive, see
# https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=10532
initramfs initrd.img-6.1.0-9-arm64
root@rpi4-20230612:/boot/firmware# ls
bcm2711-rpi-400.dtb	  bcm2837-rpi-cm3-io3.dtb   fixup4.dat	  fixup_x.dat			   start4.elf	 sysconf.txt
bcm2711-rpi-4-b.dtb	  bcm2837-rpi-zero-2-w.dtb  fixup4db.dat  initrd.img-6.1.0-9-arm64	   start4x.elf	 user-data
bcm2711-rpi-cm4-io.dtb	  bootcode.bin		    fixup4x.dat   raspi-config_20121028_all.deb    start_cd.elf  vmlinuz-6.1.0-9-arm64
bcm2837-rpi-3-a-plus.dtb  cmdline.txt		    fixup_cd.dat  raspi-config_20121028_all.deb.1  start_db.elf
bcm2837-rpi-3-b.dtb	  config.txt		    fixup.dat	  start4cd.elf			   start.elf
bcm2837-rpi-3-b-plus.dtb  fixup4cd.dat		    fixup_db.dat  start4db.elf			   start_x.elf

I'm interested in modifying the RP4 configuration via the config.txt file that is mention in below:
We've successfully configured all of these operations on the Buster Raspi 32-bit OS.

# 3 Boot Options
#   B2 Wait for Network at Boot
#   B3 Splash Screen
#   P1 Camera
#   A6 Screen Blanking
#   A8 GL Driver
#   AA Pi 4 Video Output


raspi-config nonint do_boot_wait        1           # Disabled
raspi-config nonint do_boot_splash      1 '||' true # Disabled
raspi-config nonint do_wifi_country     $RASPI_WIFI_COUNTRY
raspi-config nonint do_camera           0       # Enabled
raspi-config nonint do_spi              0       # Enabled
raspi-config nonint do_i2c              0       # Enabled
raspi-config nonint do_serial           1       # Login & IF Disabled
raspi-config nonint do_onewire          0       # Enabled

raspi-config nonint do_memory_split     $RASPI_GPU_MEM
raspi-config nonint do_audio            $RASPI_AUDIO_OUTPUT
raspi-config nonint do_blanking         1       # Disabled

Could you kindly advise where I can locate this information in Bookworm?

@aallan
Copy link
Contributor

aallan commented Sep 4, 2023

I've downloaded the 64-bit RPiOS 'Bookworm' from here: https://raspi.debian.net/tested-images/

That isn't Raspberry Pi OS, that's a stock Debian image.

@fti-sfuke
Copy link

@aallan Thanks for reply.

Raspberry Pi OS Debian12 ( Bookworm ) is not yet available on the official Raspberry Pi website (https://www.raspberrypi.com/software/operating-systems/).

And I have been unable to found a Raspberry Pi OS Debian 12 testing image.
Could you kindly provide guidance on where I might obtain it? or should I wait for official Raspberry Pi OS release ?

Is it not possible to achieve the above-mentioned operations on a stock Debian image?

@aallan
Copy link
Contributor

aallan commented Sep 4, 2023

Could you kindly provide guidance on where I might obtain it? or should I wait for official Raspberry Pi OS release ?

We are currently working internally towards a Bookworm release for Raspberry Pi.

It is not yet available publically.

@lurch
Copy link
Contributor Author

lurch commented Sep 4, 2023

Is it not possible to achieve the above-mentioned operations on a stock Debian image?

That's a question for the maintainers of the image you're using 🙂

Raspberry Pi OS is based on Debian, but with many changes; in a similiar way that Ubuntu is based on Debian, but with many changes.

@lurch
Copy link
Contributor Author

lurch commented Sep 9, 2023

Reopening, because of #3105 (comment)

@lurch
Copy link
Contributor Author

lurch commented Sep 11, 2023

Thanks @nathan-contino

@lurch lurch closed this as completed Sep 11, 2023
@flatsiedatsie
Copy link

Out of curiosity: why was this done/needed? It's causing a lot of work to fix hardcoded references to /boot/ .

@JamesH65
Copy link
Contributor

I believe its an upstream Debian change.

@ncopa
Copy link

ncopa commented Nov 27, 2023

I believe its an upstream Debian change.

Do you have any references on why upstream debian did this change?

EDIT: found some good references. Apparently upstream debian believe downstream Raspbian broke things:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055901#45

https://salsa.debian.org/debian/raspi-firmware/-/merge_requests/33#note_443953

@hhlocsync
Copy link

how to edit config.txt ?
/boot/firmware/config.txt -> i edited but it not working

@lurch
Copy link
Contributor Author

lurch commented Mar 3, 2024

@hhlocsync It sounds like your question is better suited to the forums https://forums.raspberrypi.com/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment