Is the jetson header version correct?

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

The jetson information used is as follows.

uname -a

Linux 5.10.104 #1 SMP PREEMPT Mon Oct 2        4 19:42:41 CST 2022 aarch64 aarch64 aarch64 GN        U/Linux

The installed headers version information is as follows.

# /usr/src$ ls

linux-headers-5.10.104-tegra-ubuntu20.04_aarch64  nvidia

sudo apt install nvidia-l4t-kernel-headers

Reading package lists... Done
Building dependency tree
Reading state information... Done
nvidia-l4t-kernel-headers is already the newest version (5.10.104-tegra-35.1.0-20220810203728).
0 upgraded, 0 newly installed, 0 to remove and 221 not upgraded

The headers file name is linux-headers-5.10.104-tegra-ubuntu20.04_aarch64, not linux-headers-5.10.104, I want to ask if the headers are installed correctly.

3

hello 1102796251,

that doesn’t looks correct, please check uname -a dumped by reference platform.

$ uname -a
Linux ubuntu 5.10.104-tegra #1 SMP PREEMPT Wed Aug 10 20:17:07 PDT 2022 aarch64 aarch64 aarch64 GNU/Linux

may I know how you flash your target?
for example, are you using SDKManager to install Jetpack release image?

4

Using the attached flashing process, the result is

~/lttng-modules-2.12.10$ uname -a
Linux 5.10.104-tegra #1 SMP PREEMPT Wed Nov 2 14:30:30 CST 2022 aarch64 aarch64 aarch64 GNU/Linux

L4t.pdf (291.1 KB)

For the following results, the main reason is that I used a custom kernel method.

uname -a
Linux 5.10.104 #1 SMP PREEMPT Mon Oct 2        4 19:42:41 CST 2022 aarch64 aarch64 aarch64 GN        U/Linux

In step 3.5 in the attachment, I took the following process.

cd $KERNEL_SOURCE # kernel-5.10
make DEFCONFIG_PATH=arch/arm64/configs tegra_defconfig

**make ARCH=arm64 O=＄TEGRA_KERNEL_OUT tegra_defconfig**
**make ARCH=arm64 O=＄TEGRA_KERNEL_OUT menuconfig => Goto "General architecture-dependent options" and Select "Kprobes" as "*"**
**make ARCH=arm64 O=＄TEGRA_KERNEL_OUT CROSS_COMPILE=aarch64-buildroot-linux-gnu- -j16**
**kernel-5.10$ find OUT_KERNEL/ |grep -i "kprobe*.o"**
**OUT_KERNEL/kernel/trace/.trace_kprobe.o.d**
**OUT_KERNEL/kernel/trace/trace_kprobe.o**
**OUT_KERNEL/kernel/trace/.trace_kprobe.o.cmd**

make savedefconfig
cp -v defconfig arch/arm64/configs/tegra_defconfig
make mrproper

The above process is mainly to change CONFIG_KPROBES=y in /proc/config.
But the above process seems to result in a kernel version of 5.10.104.

Is there any problem with the above process?

5

Was this installed as part of a package? What do you see from:
dpkg -S /usr/src/linux-headers-5.10.104-tegra-ubuntu20.04_aarch64

If it is a package, then it should be this:
linux-headers-5.10.104-tegra

But it appears something misnamed either then location or the package as:
linux-headers-5.10.104-tegra-ubuntu20.04_aarch64
(perhaps this would be the name if on a cross-architecture install? not sure)

So far as package names go, if this is from a package, and if this is not for cross-platform install to a PC instead of the Jetson (or perhaps even if it is), then you might be able to work around this via:

cd /usr/src
sudo ln -s linux-headers-5.10.104-tegra-ubuntu20.04_aarch64 linux-headers-5.10.104-tegra

(this creates a symbolic link which is an alias for what the name should be)

7

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