hi.
When I connect the J1010 to power, after the Nvidia screen appears, the original JetsonNano desktop does not appear and an error occurs.
The contents of the error are ‘Failed to start Hostname Service’, ‘Failed to start Configure USB flashing port for device mode’, ‘Failed to start Docker Application Container Engine’.
Then the desktop appears on a black screen with a few lines of text.
how do i solve it?
The prompt shows that boot stages succeeded, the Linux kernel loaded, and init (systemd for Ubuntu) ran. It even reached multi-user.target stage. The “failed” notes suggest a networking failure, and the port device mode might be related to the USB port emulated network device (if the service failed to load, then it might cause a chain of such messages, or USB might have its own issue).
To figure this out you really need a serial console boot log. Are you able to log in to the prompt which shows up? Does the USB keyboard work? Mostly that serial console log is needed.
Incidentally, the flash software won’t be exactly what NVIDIA provides. You have a third party carrier board, so it is highly likely it uses their device tree. Perhaps an update changed a device tree, which is something that could conceivably make parts of the hardware stop functioning (at least until the tree is fixed).
The boot log would narrow things down. A login would give you a chance to see log files and timestamps on some files. Even without a GUI the text mode prompt is quite useful.
Login works fine. This is the screen when I log in. I can enter commands on that screen. But I want the Jetson Nano wallpaper to appear.
Ok, this will get things further. First, is networking running? Typically, Wi-Fi only sets up upon GUI login, but wired is set up already at the stage you are at. I only ask because it can make it convenient to copy log files over scp. Also, if you plug in a micro-B USB cable to the micro-OTG USB connector, and the type-A end to a PC running Linux, then typically it will set up a virtual wired ethernet (the Jetson is IP address 192.168.55.1, the host would get address 192.168.55.100). Not all devices show with the following matter, but maybe you can comment if wired, virtual, Wi-Fi, so on, might be available for log copy:
ifconfig
Assuming the monitor is connected during boot, we’ll be interested in the serial console boot log. The serial terminal program you are using on your host PC has the ability to log everything. You’d want to start logging just prior to turning on power to the Nano. Then, after login, and running ifconfig, you could stop logging and post that log.
The other log is the X server log. This should tell you the proper log:
ls -ltr /var/log/Xorg.*.log | tail -n 1
The log file listed in that is most likely /var/log/Xorg.0.log. A copy of that is also needed.
For reference, your “uname -r” shows as 4.9.337-tegra, which means any module search path is at:
/lib/modules/4.9.337-tegra/kernel
(not useful right now, but the -tegra suffix implies the kernel is probably correct unless some customization took place)
Thank you for your kind reply.
But I’m new to coding so I didn’t understand your answer well.
Do you want the screen printed out by writing the ifconfig command?
When I wrote the “uname -r” command, the output was “4.9.337-tegra” as you said.
Yes, you can mouse copy and paste the output of “ifconfig”. Is networking available such that you could use a network command from a Linux PC? Windows with PuTTY would also work, but it isn’t even remotely as simple. Basically we want to find which log file is relevant (found with “ls -ltr /var/log/Xorg.*.log | tail -n 1”), and then get a copy of that file you can attach to these forums. The ifconfig part is something which can help determine if networking is functional (I need to see the actual output; the command does not do anything, but it does show what is running).
Note that the micro-USB connector is sort of a special case when it comes to networking. If that is working, then it can be used to get around the actual physical ethernet wired connector being needed. A Linux host PC would be the easiest to work with in getting that log, although a Windows system with PuTTY serial console (and also ssh/scp is available via PuTTY) would also work. Basically, a Linux PC is much simpler than using the GUI app.
I understood. Thank you for your always kind reply. Here is a picture of the screen output from writing the ifconfig command.
I don’t know for certain, but it looks like wlan0 might be Wi-Fi. This shows the Jetson can be reached at address 192.168.0.103. None of the other network interfaces even attempted DHCP (there were 0 bytes sent/received). usb0 should in theory be the virtual wired USB network, but it should have address 192.168.55.1, and it is missing, so something went wrong with virtual wired networking. Addresses can change, so verify the 192.168.0.103 address, and from your host PC, can you “ping 192.168.0.103”?
If so, then from a host PC you should be able to connect via:
ssh -Y 192.168.0.103
If that works, then scp can be used to copy files to the host PC. Using either serial console or serial console, verify (with the monitor connected to the Jetson) that the log file is Xorg.0.log:
ls -ltr /var/log/Xorg.*.log | tail -n 1
I assume it will show /var/log/Xorg.0.log. Then use scp (from the command line of your host PC) to copy this to your host PC. I’ll assume your login name is “ubuntu”, but adjust this to whatever your actual login name is:
scp ubuntu@192.168.0.103:/var/log/Xorg.0.log .
(the trailing space and ‘.’ are important)
This should copy that file to the location on the host PC where you run the command from (you could for example first “cd ~/Downloads” before running the scp command to put this in a more convenient location). Then attach that to the forum thread.
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.