Hi,

I've been trying to get a driver into the kernel and hence need to compile it and the modules. After cloning the repo I followed it all (get sources, editconfig, compile kernel and modules and then copyimage.sh) and alas no new kernel and drivers. I double checked this as sure enough the kernel image had the same old file time and date stamp.

I then poked around a bit and it seems the github repo has a scripts folder with the same files in, well sort of ish as they're different sizes! Which ones should be used and should I be setting the $SOURCE_TARGET var so the scripts use a location that I want it to or should I be leaving that var blank (didn't exist before hand)?

Another thing I noticed is the symlink initrd.img in /boot is pointing to the file /boot/initrd.img-4.9.140-tegra, is that ok or should I be looking at sorting that out somehow?

Anyway, thanks for any help you're about to offer and for the hard work in creating and maintaining the scripts, I'm sure it's very much appreciated by a lot more people than care to say ;)

EDIT: Last question, how do I get the device tree updated in the boot partition, is there a script for that too?

Kind Regards,

Dan

Hi,
I update the jetpack 4.2 with L4T 32.1.0.
How can I modify this build to fit the new L4T.
Thanks a lot
gaosiy

Hi,
thank you so much for your great work.

Currently I'm trying to enable open-iscsi on NVIDIA Jetson Xavier AGX module, in order to use on it rancher/longhorn distributed storage.

The standard kernel isn't built with open-iscsi support, so I rebuilt it using the following kernel options:
CONFIG_CRYPTO=y
CONFIG_CRYPTO_CRC32C=y
CONFIG_ISCSI_TCP=m
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_LOWLEVEL=y
CONFIG_BLK_DEV=y
CONFIG_INET=y

I thoroughly followed your README and didn't see anything wrong

Kernel and modules build correctly, the board reboots fine with the new kernel, at least it seems so (see later...) but 'modprobe iscsi_tcp' fails:
blueadmin@BL-AGX01:/wdir/kernel/buildJetsonXavierKernel$ sudo modprobe iscsi_tcp
[sudo] password for blueadmin:
modprobe: ERROR: could not insert 'iscsi_tcp': Unknown symbol in module, or unknown parameter (see dmesg):
blueadmin@BL-AGX01:/wdir/kernel/buildJetsonXavierKernel$ dmesg | tail
[ 4021.062113] scsi_transport_iscsi: Unknown symbol bsg_request_fn (err 0)
[ 4423.947586] scsi_transport_iscsi: Unknown symbol bsg_setup_queue (err 0)
[ 4423.947789] scsi_transport_iscsi: Unknown symbol bsg_job_done (err 0)
bsglib should be included...
blueadmin@BL-AGX01:~/wdir/kernel/buildJetsonXavierKernel$ grep BSG /usr/src/kernel/kernel-4.9/.config
CONFIG_BLK_DEV_BSG=y
CONFIG_BLK_DEV_BSGLIB=y

Here's my Xavier AGX version:
blueadmin@BL-AGX01:~$ ./jetsonInfo.py
NVIDIA Jetson AGX Xavier [16GB]
L4T 32.6.1 [ JetPack 4.6 ]
Ubuntu 18.04.6 LTS
Kernel Version: 4.9.253-tegra
CUDA 10.2.300
CUDA Architecture: 7.2
OpenCV version: 4.1.1
OpenCV Cuda: NO
CUDNN: 8.2.1.32
TensorRT: 8.0.1.6
Vision Works: 1.6.0.501
VPI: ii libnvvpi1 1.1.12 arm64 NVIDIA Vision Programming Interface library
Vulcan: 1.2.70

Here are the available scsi related kernel modules:
blueadmin@BL-AGX01:~$ find /lib/modules/$(uname -r) -type f -name scs
/lib/modules/4.9.253-tegra/kernel/drivers/scsi/iscsi_tcp.ko
/lib/modules/4.9.253-tegra/kernel/drivers/scsi/libiscsi_tcp.ko
/lib/modules/4.9.253-tegra/kernel/drivers/scsi/scsi_transport_iscsi.ko
/lib/modules/4.9.253-tegra/kernel/drivers/scsi/scsi_transport_srp.ko
/lib/modules/4.9.253-tegra/kernel/drivers/scsi/libiscsi.ko

and here's the iscsi_tcp modinfo:
blueadmin@BL-AGX01:~$ modinfo iscsi_tcp
filename: /lib/modules/4.9.253-tegra/kernel/drivers/scsi/iscsi_tcp.ko
license: GPL
description: iSCSI/TCP data-path
author: Mike Christie [email protected], Dmitry Yusupov [email protected], Alex Aizman [email protected]
depends: libiscsi,libiscsi_tcp,scsi_transport_iscsi
intree: Y
vermagic: 4.9.253-tegra SMP preempt mod_unload modversions aarch64
parm: max_lun:uint
parm: debug_iscsi_tcp:Turn on debugging for iscsi_tcp module Set to 1 to turn on, and zero to turn off. Default is off. (int)

Thinking I missed some kernel options... or that I failed to install it on the boot dir:

• copied original Image to Image.backup
• launched copyImage.sh
• modifyied /boot/extlinux/extlinux.conf in order to keep an emergency fallback boot with older image

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}

• then reboot....
  in fact my running kernel says
  blueadmin@BL-AGX01:~$ uname -a
  Linux BL-AGX01 4.9.253-tegra #1 SMP PREEMPT Mon Jul 26 12:19:28 PDT 2021 aarch64 aarch64 aarch64 GNU/Linux

my new kernel's compil date should be semothing like MON Oct 11 12:xx:xx .....

Pls can you help me getting the new kernel booted in place of the older one?

Best regards
Flavio

PS
as per NVIDIA Kernel Customization Guide, the boot loader should load the given Image even if not signed ....

Hi

I am getting this error during the compiling. Would you please help me to resolve this issue?

/

usr/src/kernel/nvidia/drivers/video/tegra/dc/hdcp/hdmihdcp.c: In function ‘link_integrity_check’:
/usr/src/kernel/nvidia/drivers/video/tegra/dc/hdcp/hdmihdcp.c:1940:16: error: unused variable ‘nonce’ [-Werror=unused-variable]
unsigned char nonce[HDCP_NONCE_SIZE];
^~~~~
CC drivers/video/tegra/dc/edid_disp_id_ext.o
CC drivers/video/tegra/dc/edid_quirks.o
CC drivers/video/tegra/dc/dsi.o
CC drivers/video/tegra/dc/dsi_debug.o
cc1: all warnings being treated as errors
scripts/Makefile.build:335: recipe for target 'drivers/video/tegra/dc/hdcp/hdmihdcp.o' failed
make[4]: *** [drivers/video/tegra/dc/hdcp/hdmihdcp.o] Error 1
make[4]: *** Waiting for unfinished jobs....
scripts/Makefile.build:649: recipe for target 'drivers/video/tegra/dc' failed
make[3]: *** [drivers/video/tegra/dc] Error 2
scripts/Makefile.build:649: recipe for target 'drivers/video/tegra' failed
make[2]: *** [drivers/video/tegra] Error 2
scripts/Makefile.build:649: recipe for target 'drivers/video' failed
make[1]: *** [drivers/video] Error 2
Makefile:1104: recipe for target 'drivers' failed
make: *** [drivers] Error 2

I am new, I don't know how to modify the scripts used for JetPack 4.3.

I have successfully flashed my Xavier to 4.3 using SDKManager (L4T32.3.1 JetPack 4.3) - no issues, worked as expected.

Afterwards, I installed an SSD - (I moved /home and that's it, no kernel changes)

• Where are the sample programs? In your earlier videos, you showed oceanFFT. I found the source in /usr/local/cuda/samples/5_Simulations/oceanFFT/ but it's not built. My first goal is simply to run these samples and I don't see them. 4.3 seems to be very different (I flashed 4.1 in the past and had the demos)
• from /home (on my SSD) I cloned this buildJetsonXavierKernel project expecting I would see the build configuration and maybe turn on something like "build samples".
  • getKernelSources.sh appeared to download everything - no errors, but I didn't get graphic editor for .config
  • just to see if I messed things up, I ran makeKernel.sh it ran with no errors - successful message at the end
  • reboot no problem

I think my main questions here are

• were the sample programs built with the kernel when flashed from SDKManager?
• if not, how do I build them? (Did I mess things up moving my /home?)

Thanks for putting together these Youtube videos and github repos - I've been following your tips for years.