Yes, I can but it shows “gnome-initial-setup” window, not
LXDE.
Syslog after this problem attached.
syslog.txt (185.0 KB)
Can someone check if holding systemd in old version can prevent this issue?
sudo apt update
sudo apt-mark hold systemd
sudo apt upgrade
I want to be clear that I believe the source of my problems was an upgrade to Ubuntu 20.04. Nvidia should make sure this does not happen when using Jetpack because it is very easy to make this mistake.
IIRC, I received a message in the terminal after login that told me I could upgrade Ubuntu and that is why I did it (and that is why the xorg.conf file was corrupted).
I have tried these commands and after rebooting, I can’t find any problem, LXDE starts very normally.
Hello,
I have the same issue (oh really? just kidding) and I tried the three commands from WayneWWW.
Everything (update & upgrade) worked well and the Jetson booted to the Destop without any problems.
Next thing to come is an Ubuntu update (18.04) which is recommended now.
I want to confirm if the system wants you to upgrade to 20.04…? Actually, when running sudo apt-get upgrade, it shall not update the 18.04 to 20.04. Does the GUI tell you to upgrade to 20.04?
Hello,
so, I hae installed the recommended update (from the desktop, graphical installer).
It installed :
-Security Update : Ubuntu base
Ubuntu base:
-Free implementation if the OpenGL Api - DRJ modules
-Meas VA-APi video acceleration drivers
-Mesa VDPAU video acceleration drivers
The installation worked fine and the Jetson rebooted without problems to the desktop.
Okay, this all won’t to find the root cause of the problem, but perhaps it is a clue to hunt it down.
Hello,
yep, the version with is mentioned in the installer is :
Chnanges for licllvm10 version
Installed version none
Available version 1:10.0.0-4ubuntu1- 18.04.2
1:10.0.0-4ubuntu1- 18.04.2
and so on…
and no 20,04 is not mentioned at all only 18.04.
and additional to all of this a little more information.
I have set up my Jetson with :
jetson-nano-2gb-jp441-sd-card-image.zip (downloaded last week )
And my actual version reads now :
Ubuntu 18.04.5 LTS
Release 18.04 bionic
In my case this failed to prevent the issue…
I ran all 3 lines, it seems to work :). Thank you! Now is it better to turn off updates?
I believe the trick to hold systemd may only work if your syslog shows similar patterns as @qgb00021 has shared.
lightdm.service: Service hold-off time over, scheduling restart.
Nov 27 17:54:11 jetson-nano systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
Nov 27 17:54:11 jetson-nano systemd[1]: Stopped Light Display Manager.
Nov 27 17:54:11 jetson-nano systemd[1]: Starting Light Display Manager…
Nov 27 17:54:11 jetson-nano systemd[1]: Started Light Display Manager.
Nov 27 17:54:12 jetson-nano kernel: [ 18.949275] tegradc tegradc.0: blank - powerdown
In the log, these errors keep showing up and not able to launch lightdm correctly.
Hello @WayneWWW here is my syslog:
kind regardssyslog.docx (211.1 KB)
@WayneWWW Holding back systemd worked for me. As in, I used a freshly flashed image
sudo apt update
sudo apt-mark hold systemd
sudo apt upgrade
reboot
And the graphical UI started on boot as desired
I then unhold’ed systemd and did a sudo apt upgrade and reboot. The system would then not start the graphical interface.
(
Other notes:
I have not seen a prompt to upgrade to Ubuntu 20.04 and have not attempted to upgrade to Ubuntu 20.04.
Man seems to be broken. After the initial upgrade (with systemd held) I tried doing “man apt-mark”. Man couldn’t find any docs for me. Man for everything else was also not working. After unholding systemd and upgrading it, man was still not working. I’m reflashing and checking a fresh install to see if man is broken there too.
Console output from the upgrade of systemd is attached.
Doing the fb thing to unblank the screen did not help me with getting to the console with ctrl-alt-f1 to f6. I did see unblank in dmesg, but I still couldn’t get to a console.
)systemd_upgrade.txt (3.7 KB)
Yes, Ubuntu pops up a dialog box in Unity to ask if I want to upgrade from 18.04 to 20.04.
This is a very bad idea because there are clashes between official Nvidia packages and official Ubuntu packages. e.g. systemd for Ubuntu 20.04 contains /etc/systemd/sleep.conf which clashes with one of the Nvidia packages named “nvidia-l4t-init” which ALSO contains this file.
In Ubuntu “Software & Updates” there is an “Updates” section where there is an option of when to notify the user of a new Ubuntu version. Nvidia has this set as “For long-term support versions”, which means ALL of your users of the most recent 4GB SD card image (jetson-nano-4gb-jp441-sd-card-image.zip) might end up upgrading Ubuntu by mistake, and if they do this I guarantee they will have problems.
Basically, I am surprised you have not had more people contacting you to say they have got problems because they accidentally upgraded Ubuntu from 18.04 to 20.04.
@WayneWWW, here is an idea for solving release upgrade issues. Note that the file used to change whether release upgrades is here:
# dpkg -S /etc/update-manager/release-upgrades
ubuntu-release-upgrader-core: /etc/update-manager/release-upgrades
In that file the default is to allow and prompt via:
Prompt=lts
Changing this to not offer release upgrades:
Prompt=never
I’m not sure how one would replace “/etc/update-manager/release-upgrades” with another package when the original is owned by “ubuntu-release-upgrader-core”, but if that single file could be altered, and not allowed to be updated without updating the NVIDIA package for file release-upgrades, then LTS release upgrades would not be offered until NVIDIA allows it by updating the release-upgrades file from their own repository.
For everyone else: Just edit the release-upgrades file to “Prompt=never”.\
EDIT: Additionally, third party carrier board manufacturers could take advantage of this as well. This would be extensible to custom repositories.
You have to try these commands in fresh setup (re-flash, hold systemd and then run apt upgrade). If your systemd was already updated, then you cannot make it work by running these commands.
@jetsonnvidia, let me ask this again: what is the version of jetpack you are using?
I just checked the latest version and we already disabled the update by setting Prompt=never.
If you were trying to upgrade the system from rel-32.2.x to rel-32.4.x, then it may not work because the OTA upgrade is a new feature since rel-32.3.1. I cannot guarantee what would happen if you use release prior to rel-32.3.1.
You said your Xorg config has been overwritten and you could see 20.04 update in the prompt. However, these are not happened on other users’ device. Thus, we need to know your software version.
Here is my output of “cat /etc_old/nv_tegra_release”:
# R32 (release), REVISION: 4.4, GCID: 23942405, BOARD: t210ref, EABI: aarch64, DATE: Fri Oct 16 19:44:43 UTC 2020
Does this help?
You are right!!! Looks like this works for the moment… thank you!!
Hi @jetsonnvidia,
I meant… do you remember what was your previous version before you ran apt-get upgrade? You said this card has not gone through any upgrade for 1 years. But our OTA feature may not support some old release.
As for other users here, we have some result for this issue for far.
- This issue is due to lightdm greeter which is incompatible with new systemd
- If you are using gdm3, then you won’t have this issue.
- Every jetson platform has chances to hit this error if you are using lightdm. Not limited to nano-2gb.