Extlinux.conf content is not readable

Hello
i wanted to check/edit the content of /boot/extlinux/extlinux.conf
but the data is not readable

device: xavier-nx emmc + nvme
secure boot enabled
disk encryption enabled

flashing steps

sudo ROOTFS_ENC=1 BOARDID=3668 BOARDSKU=0001 FAB=300 BOARDREV=B.0 \
  ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash \
  -u $XKEYS/rsa_priv.pem -v $XKEYS/SBK --user_key $XKEYS/usr_flash.key \
  -p "-i $XKEYS/ekb.key --user_key $XKEYS/usr_flash.key" \
  jetson-xavier-nx-devkit-qspi internal

sudo ROOTFS_ENC=1 BOARDID=3668 BOARDSKU=0001 FAB=300 BOARDREV=B.0 \
  ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash \
  -u $XKEYS/rsa_priv.pem -v $XKEYS/SBK --user_key $XKEYS/usr_flash.key \
  -p "-i $XKEYS/ekb.key --user_key $XKEYS/usr_flash.key" \
  --external-device nvme0n1p1 -S 220GiB \
  -c ./tools/kernel_flash/flash_l4t_nvme_rootfs_enc.xml \
  --external-only --append jetson-xavier-nx-devkit-emmc external


sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only

Hi HusamAlqaza,

Are you using the devkit or custom board for AGX Xavier?
What’s your Jetpack version in use?

Could you provide your /boot/extlinux/extlinux.conf for further check?

Please also share the result of the following command on your board.

$ cat /etc/nv_boot_control.conf
$ cat /etc/nv_tegra_release

Hello @KevinFFF
sorry the device is xavier nx not AGX
and yes we are using a custom carrier board from forecr https://www.forecr.io/
sure i will attach the /boot/extlinux/extlinux.conf file (changed the name to .log to be able to upload it )
extlinux.con.log (880 Bytes)

nvidia@nvidia:~$ cat /etc/nv_boot_control.conf
TNSPEC 3668-301-0003-B.0-1-2-jetson-xavier-nx-devkit-emmc-internal
COMPATIBLE_SPEC 3668-301---1--jetson-xavier-nx-devkit-emmc-
TEGRA_CHIPID 0x19
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0
nvidia@nvidia:~$ df -h
Filesystem              Size  Used Avail Use% Mounted on
/dev/mapper/crypt_root  216G   52G  153G  26% /
/dev/mapper/crypt_UDA   301M  2.1M  279M   1% /mnt/crypt_UDA
none                    7.4G     0  7.4G   0% /dev
tmpfs                   7.8G   20K  7.8G   1% /dev/shm
tmpfs                   7.8G   26M  7.7G   1% /run
tmpfs                   5.0M  4.0K  5.0M   1% /run/lock
tmpfs                   7.8G     0  7.8G   0% /sys/fs/cgroup
/dev/nvme0n1p1          380M   91M  265M  26% /boot
tmpfs                   1.6G   16K  1.6G   1% /run/user/120
tmpfs                   1.6G     0  1.6G   0% /run/user/1000
nvidia@nvidia:~$ cat /etc/nv_tegra_release
# R32 (release), REVISION: 7.1, GCID: 29818004, BOARD: t186ref, EABI: aarch64, DATE: Sat Feb 19 17:07:00 UTC 2022
nvidia@nvidia:~$

Do you have custom layout change for the rootfs?

Could your <Linux_for_Tegra>/rootfs/boot/extlinux/extlinux.conf from your host be readable?

what do you mean by custom layout ?

yes is readable

➜  Linux_for_Tegra cat rootfs/boot/extlinux/extlinux.conf
TIMEOUT 30
DEFAULT primary

MENU TITLE L4T boot options

LABEL primary
      MENU LABEL primary kernel
      LINUX /boot/Image
      INITRD /boot/initrd
      APPEND ${cbootargs} quiet

# When testing a custom kernel, it is recommended that you create a backup of
# the original kernel and add a new entry to this file so that the device can
# fallback to the original kernel. To do this:
#
# 1, Make a backup of the original kernel
#      sudo cp /boot/Image /boot/Image.backup
#
# 2, Copy your custom kernel into /boot/Image
#
# 3, Uncomment below menu setting lines for the original kernel
#
# 4, Reboot

# LABEL backup
#    MENU LABEL backup kernel
#    LINUX /boot/Image.backup
#    INITRD /boot/initrd
#    APPEND ${cbootargs}

partition layout change (i.e. the XML used to flash the board)

ah yes, we changed the num_sectors

<device type="nvme" instance="0" sector_size="512" num_sectors="488397168">

Isn’t extlinux.conf encrypted on the bootpartition when using Secureboot + Disk encryption?
On my encrypted Jetson AGX I also can’t read the contents of it.

Yes, it seems the expected result when you enable Secureboot and Disk Encryption.

Ok thanks,

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.