GUI login not working with l4t-create-default-user-sh


I am using l4t-create-default-user-sh during development phase (Jetson Nano)
if I lock the session of the default user, I cannot log back in. It tells me that the password is wrong.
If I do not use the option automatic login, the screen stays black.

It is only happening with the GUI, in console mode I can log in.

can you please help me on that?

hello ffloj,

may I know which JetPack/L4T release version you’re working with?
you may also check the release tag, (i.e. $ cat /etc/nv_tegra_release) for confirmation.

Hi ffloj,

Please run “” script before flash image.

$ sudo ./ [-u <username>] [-p <password>] [-a] [-h]
$ sudo ./ -u nvidia -p nvidia
Then do full flash image on Jetson-Nano.

The GUI login is what you set username and password via script.

Thank you for the feedback.

after executing the script as you mentioned, I am generating a SD Image with script as I am using a SD jetson nano board.

$ cat /etc/nv_tegra_release
R32 (release), REVISION: 4.3, GCID: 21589087, BOARD: t210ref, EABI: aarch64, DATE: Fri Jun 26 04:38:25 UTC 2020

The board boots correctly but when I lock my session, I cannot log back in with my password.

hello ffloj,

may I know what’s the exactly steps, or the commands?

my goal is to spare me time during development and avoid the long process of Ubuntu configuration at first boot.
(Do you have another way to pre-configure the rootfs than with this script?)

From Linux_for_tegra folder I am executing:
$ sudo ./ -u nvidia -p nvidia -a
$ sudo ./tools/ -o nano-date +%Y%m%d_%H%M%S.img -b jetson-nano -r 300

from there an image is generated and I am flashing a SD card using balenaEtcher GUI.

The board is booting and I am automatically logged in.
from the desktop, I am locking the system.
I am now at the GUI login but entering the password nvidia doesn’t work

when doing CTRL-ALT-F3, I can enter my username and password successfully.

It might be related to user access issue with gdm.

I can also add that sudo is not working from the target console. I got the following answer
sudo /usr/bin/sudo must be owned by uid 0 and have the setuid bit set

the overall problem might come from creating the user and giving him the right access

Problem solved.
It was not related to script.
The problem comes from my rootfs. after starting from default rootfs, the problem did not occur.

thank you any way for your feedback