Im so very frustrated with this small computer. I had it working for a week and been trying to fix it for over a year. I’ve read many threads and potential solutions, put many days into this thing and it’s really getting to me, because I know exactly what I did wrong, but apparently there is now way to fix it. So what I did wrong, I mounted the drive to an nonexist. So now it always tries to boot to this nonexistent mount directory. I’ve tried reflashing it, but that doesn’t work, it seems like it works takes a bunch of time and then it just doesn’t. Every time it fails I see this stupid mount name. Weeks ago I could get into the boot options, but I guess I f that up as well since I can’t get into it anymore. Tried connecting an external drive with Ubuntu but can’t launch from it since I can’t change the boot order. How can it be possible that I can’t access boot options anymore? It was within one session, at the beginning it worked, then suddenly it didn’t anymore. I put it aside for a week, and it still doesn’t work.
Are you using devkit or with custom carrier board?
Any device connected on your board?
Which JetPack SW you flashed via the SDK manager from a Ubuntu host PC?
Please dump the serial console log from UART and attach it here.
What kind of external drive? Can you mount it on another computer to edit or examine? If so, what is in the “/boot/extlinux/extlinux.conf” (you could post a copy of that here in the forum)?
There are several places a mount point might be listed, and one type of flash might fix part of that, but not the other part. With an external drive you would normally use an initrd flash.
Depending on circumstances there might be a pointer on the module itself, and that might get flashed; or the initrd might get changes; or the external device might get changes; or a combination. Maybe it is booting to the eMMC which then chain boots to external via initrd. Maybe it is then booting to the missing device. Somewhere in that chain you have to remove the bad mount point spec, but it won’t necessarily be clear where that is, and flash methods might just change a pointer without editing the final boot target (and that final boot target might be what then redirects to nothing).
Actually, what @kayccc just mentioned for serial console, is the way to know what it is actually doing in terms of where it is getting information. That plus the external device’s extlinux.conf (there is also an eMMC version of it) would go a long way to making sure it has been told the correct boot chain.
Note: On any extlinux.conf which you can access make sure you remove the word “quiet” before getting the log. If you can’t do that, then just report what you can get as a log.
i am using a devkit, with nothing conected accept the host computer during flash. Im using the most up to date version flashing from ubuntu 18.04.
the external drive i was trying out was just an ubuntu system. Its on an external ssd plugged straight into the the jetson.
It seems you are using Jetpack 5.1.3(R35.5.0).
22:53:47.300 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_AGX_XAVIER_TARGETS: *** The target t186ref has been flashed successfully. ***
22:53:47.300 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_AGX_XAVIER_TARGETS: Reset the board to boot from internal eMMC.
..
22:54:54.636 - info: NV_L4T_NVIDIA_NSIGHT_PERFSDK_HOST_COMP@host: [ Package Install Finished Successfully ]
From the SDKM log you shared, it has been flashed and the packages installed successfully.
For the devkit, could you refer to the following instruction to capture the serial console log for further check?
NVIDIA Jetson Xavier - Serial Console (ridgerun.com)
Are you connecting a USB-SSD or NVMe SSD on Jetson?
im using the ssd inside the jetson. I shared a picture as well on the drive. but both options dont work. its still trying to go for that wrong mount even after it apperently flashed successfully.
Does the external drive (SSD) have boot content on it? If the image was created by you, and not by JetPack/SDKM, then it is likely incomplete.
Your right I did not install it over skd manager. I uploaded another picture I got to a new error i havent seen yet. I also uploaded the minicon output. the more i Play with it the more i think there is some issue with the integrated ssd.
You should be able to save your minicom log file and directly attach it to the forum thread. That might show more information. If you can, plug the SSD in to another Linux computer just to see if it shows up.
Do you mean NVMe SSD since I can’t find your picture on your drive?
You can just upload the log and information on this forum topic.
I would like to check the full serial console log from the devkit after it has been flashed successfully.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.